Closed howels closed 2 years ago
Maybe related - the esc-configurator tool shows an incorrect EEPROM revision, which doesn't match the firmware reported in AM32's config tool or the file:
2022-08-05 @ 16:03:11 -- Done reading ESCs
2022-08-05 @ 16:03:11 -- Read ESC 4: KM55A_BUTTER - AM32, 243.16, Bootloader v1 (PB4)
2022-08-05 @ 16:03:11 -- Firmware mismatch! Flash: 1.89 vs. EEPROM: 243.16
2022-08-05 @ 16:03:11 -- Read ESC 3: KM55A_BUTTER - AM32, 243.16, Bootloader v1 (PB4)
2022-08-05 @ 16:03:11 -- Firmware mismatch! Flash: 1.89 vs. EEPROM: 243.16
2022-08-05 @ 16:03:11 -- Read ESC 2: KM55A_BUTTER - AM32, 243.16, Bootloader v1 (PB4)
2022-08-05 @ 16:03:11 -- Firmware mismatch! Flash: 1.89 vs. EEPROM: 243.16
2022-08-05 @ 16:03:11 -- Read ESC 1: KM55A_BUTTER - AM32, 243.16, Bootloader v1 (PB4)
2022-08-05 @ 16:03:11 -- Firmware mismatch! Flash: 1.89 vs. EEPROM: 243.16
Apparently the version number is in EEPROM, but esc-configurator is looking for a fixed location in the ROM and that is causing the issue because different MCU targets in AM32 use different memory locations for their data. The EEPROM version number should be used according to @AlkaMotors
Maybe the version number thing is different to the original issue - cannot flash local firmware. But it may be linked because this is a new target MCU I am trying to flash (GD E230).
OK, careful then. If the EEPROM layout changed then writing settings might create problems anyway. I am a bit surprised that you don't get a warning about they layout not being recognized...
Describe the bug Cannot flash AM32 local files
To Reproduce
Occurs whether attempting to flash all ESCs or individually. Had to use the AM32 local application to flash these local files.
File type and format checks out because I can flash these with the local AM32 tool.
Expected behavior Should flash the file or produce an error clearly stating why it's not possible (wrong MCU type etc)
Desktop (please complete the following information):
Log