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

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

Ralph — Tue, 01 Aug 2017 06:29:43 GMT

Hi PiZi,

Thanks for your information.

I can debug SR3v1.1 now.

Updated MDK to lasted version eliminated the error 59 message.

To debug firmware, the bootloader has to be erased first. Just like you mentioned earlier.

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

Ralph — Tue, 01 Aug 2017 05:29:27 GMT

Hi. Thanks for the information.

I've updated the MDK-ARM to 5.24a and the error message is gone.

I still can't debug the SR3v1.1!

I can debug the bootloader now and can't debug fimrware.

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

Piotr Ziecik — Mon, 31 Jul 2017 10:15:06 GMT

Hi.

Look here: devzone.nordicsemi.com/.../

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

Ralph — Mon, 31 Jul 2017 08:13:31 GMT

The image is a screen shoot of keil window.

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

Ralph — Mon, 31 Jul 2017 08:04:39 GMT

Hi. Thanks for your response.

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

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

Best Regards,

Ralph

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

Piotr Ziecik — Mon, 31 Jul 2017 06:12:26 GMT

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.