Hi,
I am trying to upload the an0003 bootloader (hex file) to a EFM32G222F128 via KEIL 5.36 (free version) and a ULINK2.
Here are my settings:
My guess is that there is some problem with the RAM for Algorithm part or the Connect and Reset settings.
I've tried changing the SWD clock but same results.
Any tips?
thanks
Try again with Connect and Reset Options in Options For Target - Debug - Settings set as follows:
The Connect: option set to under Reset
The Reset: option set to HW RESET
When I configure these options I get an SWD Communication Error.
What's the result after checking your ULINK2 Debug Adapter with our Troubleshooting Guide?
https://www.keil.com/support/man/docs/ulink2/ulink2_trblshooting.htm
Well it seems that ULINK2 is communicating with my target system as per the guide but I am getting the invalid rom table error when I try to flash the chip.
Also, based on the screenshots I provided, is my target device responding even to ULINK?
It seems that your debug connection is OK because the core of this device is detected by ULINK2 (see your screenshot). Unfortunately, I don't have this board to test a Flash download, so I can only give you some general hints:
You wrote: "My guess is that there is some problem with the RAM for Algorithm part"
No, I don't think so. This would be a different error message. uVision / ULINK2 tries to read the ROM Table of a device at the beginning of a debug session or Flash download. This ROM Table tells a debugger which debug features are present in the CoreSight implementation of this chip. These are standard memory read accesses and they obviously fail.The default 'Size' for the memory algorithm for this device is 0x00001000. In your picture, I see 0x00000800. You may want to change this and try again.