You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have burn optiboot botloader from MCUdude MegaCore Optiboot Bootloader for my Arduino Mega 2560 using another arduino nano as isp.
I was able to upload the program using the python app. It is only "blink" program.
But the program is not running, then I checked using avrdudess (arduino nano as isp) to verify the program. Avrdudess even cannot detect the Atmega2560.
Sorry for my bad english.
The text was updated successfully, but these errors were encountered:
In fact, the bootloader will erase the flash page (256 bytes for the case of Arduino Mega2560) before writing to it. So whenever we try to flash the program in 128-byte chunk (which is the default defined in ArduinoRemote.py), the bootloader will erase the same flash page twice for every 256 bytes. In other words, for every two 128-byte chunks of hex transferred to bootloader, the first one will be erased before the second one being flashed.
Having identified this, I made a quick change in this branch. But unfortunately, I don't have an Arduino Mega with me so I couldn't test it out.
You may pull this feature branch and try it. Do remember to update the line below to 256.
I have burn optiboot botloader from MCUdude MegaCore Optiboot Bootloader for my Arduino Mega 2560 using another arduino nano as isp.
I was able to upload the program using the python app. It is only "blink" program.
But the program is not running, then I checked using avrdudess (arduino nano as isp) to verify the program. Avrdudess even cannot detect the Atmega2560.
Sorry for my bad english.
The text was updated successfully, but these errors were encountered: