Today I released v3 beta2 of picoboot. Like the last release of picoboot, it takes up only 256 bytes, which is the minimum bootloader size supported on the ATmega88 and ATmega168. This means picoboot will free up 256 bytes of flash if you currently use Optiboot. Without any potential benefit from reduced size, this release focused on robustness and speed.
The above screen shot shows reading the 16kB flash memory of an ATmega168 in 1.32 seconds. Using 500kbps instead of 250 will read the flash in under one second, and will read 32kB of flash from an ATmega328 in two seconds. Not only is it fast, it is reliable, with no errors using CH340G and CP2102 adapters under Windows, and PL2303HX adapters under Linux. So as long as your serial driver supports 250 or 500kbps and doesn't round them down to 230,400 and 460,800, you can have reliable and high speed uploading and verify of code on ATmega MCUs.
Earlier versions of picoboot supported a bootloader toggle mode, where resetting the MCU once entered the bootloader, and resetting again ran the application code. I designed this with boards that don't support the auto-reset functionality of the Arduino bootloader. However this turned out to be problematic with some boards that do have auto-reset, where picoboot could sometimes toggle out of bootloader mode when it was supposed to enter bootloader mode. With v3, picoboot now implements a timeout where it will wait for a few seconds and if no communication is received from avrdude, the bootloader will exit.
Like the previous versions, picoboot does not use the watchdog timer, and will not impact application code that uses the watchdog reset. To make picoboot useful for use with a standalone AVR on a breadboard, it does not rely on a user LED on PB5 to indicate bootloader activity. Instead, when the bootloader starts, it lowers the TXD line (PD1). This will light the RX LED on the attached serial adapter. If the bootloader times out, PD1 will be left floating before the bootloader exits.
My recommended baud rate for picoboot is 250kbps. This baud rate results in 0 timing error with the AVR USART when used with the common clock rates of 8, 12, and 16Mhz, as well as the less-common 20Mhz. The faster 500kbps also results in 0 timing error with the USART, however poor design of some serial adapters makes the higher speeds more susceptible to noise, particularly when long wires are used to connect to the AVR. I didn't encounter problems at 500kbps, but I was a bit surprised by how much noise I saw on my oscilloscope when testing a CP2102.
If you are using the Arduino IDE rather than the command line, I explained how to change the boards.txt file in my blog post about picoboot v1.
I plan to test v3 beta 2 for about a month, so expect the final v3 in early February. In addition to further testing on the mega168 and mega328, I'll test the mega88. If there is enough interest in a build for the mega8, I'll look into supporting it too.