Breakpoints not being hit

RE: Breakpoints not being hit

nrbrook — Thu, 08 Aug 2019 18:40:06 GMT

Breakpoints were not being hit because the debugger was connecting after execution had started and not resetting the target. Running

monitor reset
continue

Reset the application and my breakpoints were hit.

RE: Breakpoints not being hit

Susheel Nuguru — Thu, 08 Aug 2019 10:01:34 GMT

The root cause in this thread and here might be related.

RE: Breakpoints not being hit

nrbrook — Thu, 08 Aug 2019 09:52:53 GMT

No I've not done anything with the bootloader. Is the bootloader flashed as part of this? Or can I re-program a stock bootloader separately? If it would help I could send my project to you directly?

RE: Breakpoints not being hit

Susheel Nuguru — Wed, 07 Aug 2019 12:14:55 GMT

[quote user=""]I'm wondering if breakpoints are not being hit because they are not being offset by the softdevice length? In the output above a breakpoint is set at 0x000262DA, but the flash start is 0x00026000 and the soft device hex is >400kb.[/quote]

no offset is needed as the breakpoint is set at an absolute address and the debugger is not working with offsets here. If you look at the .map file, you can see the absolute address space the functions and data are occupying.

[quote user="nrbrook"]Here's what I get in Ozone when it occurs[/quote]

It seems to be a hardfault which is handled inside the softdevice. I am not sure why the hardfault has not been forwarded to the application. Have you happened to play with the bootloader or the vector table set functions?

RE: Breakpoints not being hit

nrbrook — Wed, 07 Aug 2019 12:03:45 GMT

Here's what I get in Ozone when it occurs

RE: Breakpoints not being hit

nrbrook — Wed, 07 Aug 2019 11:28:23 GMT

Thanks, I'm having difficulty connecting though.

File.NewProjectWizard();
Project.SetDevice ("nRF52832_xxAA");
Project.SetHostIF ("USB", "");
Project.SetTargetIF ("JTAG");
Project.SetTIFSpeed ("1 MHz");
Project.AddSvdFile ("$(InstallDir)/Config/CPU/Cortex-M4F.svd");
File path resolved: "$(InstallDir)/Config/CPU/Cortex-M4F.svd" was found at "/Applications/SEGGER/Ozone/Ozone.app/Contents/MacOS/Config/CPU/Cortex-M4F.svd"
File.Open ("/Users/nick/Documents/Repos/AirTurnFirmwareV2/cmake-build-debug-arm-none-eabi/src/AirTurnFirmwareProject_BT200.elf");
File.Open: completed in 400 ms
Debug.Start();
Device "NRF52832_XXAA" selected.
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Connection failed

I know it recognises the connected nrf52DK as it displays the license warning with the JLink serial number, and I can connect with JLinkExe.

Edit: Ahh, I was using JTAG instead of SWD.

RE: Breakpoints not being hit

Susheel Nuguru — Wed, 07 Aug 2019 11:02:31 GMT

This thread shows you how to start Ozone debugger

RE: Breakpoints not being hit

nrbrook — Wed, 07 Aug 2019 10:03:19 GMT

Are there any instructions for using Ozone with Nordic nRF52832?

RE: Breakpoints not being hit

Susheel Nuguru — Wed, 07 Aug 2019 09:54:20 GMT

I find Ozone more convenient than using GDB, can you give it a try to see if it gives you more information on call stack when you get the SIGTRAP?