Erased pages in main program

[Tigger777]

Did the older bootloader (without the options UART0/UART1/No Bootloader) automatically select which uart was the programming port? I've had devices running in the field for 3 years using optiboot, The issue appears to be only on devices I've programmed with a version from about 12 months ago. Earlier versions(2-3years ago) are running good, and the current devices also as i cannot simulate it on the oldest and newest code.

[MCUdude]

The "older" implementation always used UART0. Apart from this, nothing has changed.

Well, that's not entirely true either. With MiniCore, the default clock frequency for 8 MHz external has changed from 38400 to 57600.

[Tigger777]

Good day Hans, Thank you for your reply. The reason I asked, was because I have a product that ran without problems for 2 years using mightycore. I updated my software and released a new firmware update for my customer to load. After this, I had problems with EEPROM memory changing and also program memory pages being erased. I am convinced this had something to do with the bootloader and core versions mismatching. Almost like an interrupt vector misalignment. After updating the bootloader to the latest version the problem dissappeared. This only happend on power up, never while running. Regards Duane

…

On 27 May 2020, at 4:32 pm, Hans ***@***.***> wrote: The "older" implementation always used UART0. Apart from this, nothing has changed. Well, that's not entirely true either. With MiniCore, the default clock frequency for 8 MHz external has changed from 38400 to 57600. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD63ZJVRVZ6MQVACVCQCRL3RTTF2HANCNFSM4KREXOLA>.