The bootloader is the erasor-head, not the actual application 'FW', so even if the firmware is already erased your bootloader still shows 'ERASED'.el-dr wrote:Then I sent the 32_16_32 sysex file and the result was the same with the other MCU: it seems as if no sysex data arrived to the md. However, this cannot be the case, because the fw eraser can be rerun successfully at any time with both MCUs.
It should not be possible for the bootloader to erase itself (consider your government), but do check Dmitris' documentation for any updates.
Have you got the bootloader through the following programming stage yet?!
PS. To be clear on this point:
You can run a faster mCU with a slower crystal - just use the FW appropriate to the cyrstal speed.
IE. A 20MHz 644 with a 16MHz crystal needs 644_16_XX.syx
... but there is no 16MHz version of the 324 for some reason