Why can't I debug SR3 v1.1 in MDK-ARM ?

[Ralph]

Hi, I am porting my code from SR3 v1.0 to SR3 v1.1 now. I have a problem in debugging SR3 v1.1.

In SR3 v1.0, it's fine in MDK-ARM debug session. I can set break point or trace code's execution. But in SR3 v1.1, I can't set break point or single step trace the source code. The source code window and disassembly code window are irrelevant.

I've try the original SR3 v1.1 without my code. It's the same. I also ask someone else to debug SR3v1.1 with his MDK-ARM and it works. It seems that it's caused by something with environment setting!?

I just noted a error message when I try to enter debug session that I missed before. "error 59: invalid absolute module"

Anyone has idea about this?

[Piotr Ziecik]

Hi.

The SR3 for nRF52 v1.1 has support for firmware upgrade over Bluetooth. As result, the complete firmware consists of SoftDevice, Bootloader and the SR3 application. After every reset and wake up the bootloader is executed. Then application is started if it is valid. Otherwise the remote will stay in DFU mode.

I suppose that you cannot debug the application because the remote stays in bootloader (this is why you might see irrelevant disassembly).

I recommend checking if you can debug the application if there is no bootloader in the system. In order to remove the bootloader you should erase the chip (using nrfjprog with --eraseall switch) and then flash only SoftDevice and your firmware.

Update: Regarding error code. Maybe this will help you: www.keil.com/.../3692.htm Which version of Keil are you using? Could you post a screenshoot of the Keil window?

Best Regards, PiZi.

[Ralph]

Hi. Thanks for your response.

I've tried the following things and the results are the same.

1. Erase the chip and program the SoftDevice only with nRFgo Studio. Then, start a debug session in Keil-ARM. The result is NG.

2. Open the bootloader project. Rebuild and start debug session. The result is NG.

Best Regards,

Ralph