Ralph Doncaster

I also just pushed the fix for issue #3

dwprog.py is hard-coded to use FTDIInterface. It looks like you planned to support SerialInterface but either didn't finish or didn't push the changes. Regarding sending break, the simplest way is...

I just pushed a baud rate detector program: https://github.com/nerdralph/nerdralph/blob/master/autobaud.py With a Pl2303hx under Linux, it gets within 2-3% of the target baud rate.

I think I can improve it by looking for the baud rate where I read back 5 0xF0 characters, which would be 5x the target baud rate. Regarding speed, I...

I'm travelling, so I'll test it out when I am back. On Thu, Apr 12, 2018, 15:05 Matti Virkkunen wrote: > @nerdralph Would you mind giving this > version a...

I just tested it out, and there seems to be an intermittent bug in flashing. ``` Starting dwprog. Getting target device properties. Auto-detecting target device... Opening debugWIRE interface... Successfully opened...

Baud rate should be within 1%, as I verified with my scope. I tried a couple baud rates and will try a few more to make sure. The delay after...

The problem doesn't seem to be related to the baud rate. It seems to be related to tty (serial) error handling such as break and frame/parity errors. As you may...

I just pushed an improved autobaud.py. After finding the rough baud rate, it tries 1.5% changes until it finds the exact baud rate (within +- 0.75%). If you don't mind...

> > How do I tell arduino-cli to set certain flags? > > You can use `arduino-cli compile`'s `--build-properties` option to do things like: > > ``` > arduino-cli compile...