Skip to content

Modify the link address and default values ​​of EEPROM for V203 - #463

Open
TianpeiLee wants to merge 1 commit into
am32-firmware:mainfrom
TianpeiLee:fix_v203
Open

TianpeiLee wants to merge 1 commit into
am32-firmware:mainfrom
TianpeiLee:fix_v203

Conversation

@TianpeiLee

Copy link
Copy Markdown
Contributor

#462
The current AM32 Configurator cannot upgrade the firmware of V203.Testing revealed that when the bootloader reports a 64KB FLASH SIZE signature, the configurator recognizes it and processes it uniformly according to the base address 0x08000000, subtracting this base address from the address in the hex file. However, the V203's base address is linked using an offset of 0x0, causing the configurator to fail to upgrade the firmware for the V203's ESC.

Before it was modified, it would always get stuck on the screen below:
image

When capturing communication packets between the bootloader and configurator, the connection gets stuck after the handshake and then stops responding:
image

I was able to solve the problem by using the first two commands in the startup file to force the running PC to jump to the base address 0x08000000. There may be other solutions.

Once the modifications are complete, you can download and update the firmware normally:
image

Additionally, sending the default configuration now sets the beep tune section in the EEPROM to 0xFF. This eliminates the need to explicitly define ERASED_FLASH_BYTE as 0x39 in V203, otherwise the power-on startup tone will be incorrect. Therefore, I commented out the definition in targets.h.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant