dmitri wrote:Does the bootloader in your Atmega have an option to choose crystal frequency?
If it doesn't, then your bootloader is fixed at 20MHz and you either have to
a) (recommended) program it with a new bootloader which support crystal frequency selection using ISP cable and an LPT port on a PC
or
b) (not recommended) try to program it with a 16MHz firmware while using a 20MHz crystal and after successful programming change back to the 16MHz crystal
efbe wrote:dmitri wrote:Does the bootloader in your Atmega have an option to choose crystal frequency?
If it doesn't, then your bootloader is fixed at 20MHz and you either have to
a) (recommended) program it with a new bootloader which support crystal frequency selection using ISP cable and an LPT port on a PC
or
b) (not recommended) try to program it with a 16MHz firmware while using a 20MHz crystal and after successful programming change back to the 16MHz crystal
I did something else, I replaced the cristal again with the 20 MHz and could now up-date the Firmware.
The USB issue still remains. At least I can use the MIDI in / out again, untill I find out the other things.
\\dmitri wrote:It may, it may not work well. See my comments on the bootloader thread. I myself sometime experience issues with 'overclocked Atmega32/USB' combination, e.g. USB not being detected or MegaDrum restarts unexpectedly when doing two way sysex communication.
When I downclock to 16MHz I don't experience any such issues at all.
Users browsing this forum: No registered users and 195 guests