Thanks for the link Coding Badly. I did follow that page, and also left a comment there a few days ago (awaiting moderation) about whether a 164/324/644 version of the Mighty software may be forthcoming.
I tried starting again from the beginning with the Sanguino bootloader, and it works as expected. Also, with just the bootloader, arduino pin 0 is blinking indefinitely. So I went back to try the same thing again with the "Calunium 644P (Stripboard)" bootloader and get the same result as before. ( "avrdude: stk500_recv(): programmer is not responding" on trying to upload a sketch).
Now, naturally I'm not so concerned about that since it's working with the Sanguino loader, but it could be useful to others if it was found out why Calunium isn't working for me. So to answer your questions :
-
I'm resetting by connecting pin D10 from arduino-as-ISP during bootloading, and by connecting reset pin to reset pin during sketch upload
-
I haven't seen any pins blink from the Calunium bootloader
As for the baud rate corresponding to what the bootloader uses, in the Calunium boards.txt I see the line "cal644p_strip_16.upload.speed=38400". But that would dictate both the bootloader's upload speed, and the
sketch upload speed, wouldn't it?
Finally, now that I've got it going on 644p, I'd love to also get it going on my 164p... it seems most of these projects focus on the 1284p and the 644p, but the 164p is about half the price of the 1284p where I live, and fine for those mainly interested in a DIP with more I/O and 2 UARTs, but not so concerned about more flash/sram/eeprom. Do you think it's possible to make a few number changes to the Sanguino 644p software to get it to support 164p? Or is it a lot more involved than that..
Thanks again