SES project from makefile project

[AshLabs]

Hi all.

My product locks up after a certain amount of time.
To resolve this, i need to debug it. Since it's a makefile project, i need to convert it to SES.

The project is a multiprotocol one. Combining Openthread with BLE.
I've started from an example, which i expanded upon.

So i've ported the includes and the defines over from the makefile to the SES project.
I've got it to compile, but the SVC_Handler() keeps getting called. This is called from the sd_softdevice_enable functioncall.
Normally it's crystal related. But my original makefile project works without an issue on this hardware, so i know for a fact that the crystal is okay.

The softdevice file is added to the extra file loading on debug, so the softdevice does get flashed inside the chip.

I've tried multiple RAM configurations and tried changing the OT_DATA location. But no improvement.

Any thoughts as to what could be the problem ?

Kind regards

[Edvin]

Hello,

Normally it's crystal related. But my original makefile project works without an issue on this hardware, so i know for a fact that the crystal is okay.

So the unmodified example runs fine, right? What did you add? Are you sure that none of the error handlers are catching an error? Do you see any log output? Did you try debugging? Could it be that it was not imported correctly to SES? Did you try to use Segger's tool: "Ozone" for debugging your makefile project?

Best regards,

Edvin

[AshLabs]

Edvin. Thanks for the reply!

I've abandoned the SES route. Converting the project to get it debugging in that fashion is not working out. Tried multiple times.

I've got Ozone working tho.

I get a hardfault. That is situated in the mac_frame.cpp section.
Getting to the origine of the fault is still something i need to do.

Any tips are always welcome!

[Edvin]

Do you halt the application before the hardfault? (breakpoint or pause the execution?)

Have you tried to capture a sniffer trace from the network to see what's going on at the time when the hardfault occurs? Any particular type of message that triggers it? 

I can't tell from your screenshots what the issue is. Does the log say anything before (or when) the hardfault occurs?

Is there some way for me to reproduce what you are seeing? Have you tried to run the same (ish) application on a DK? Are you using any peripherals? Sensors or something that use serial communication, for example. Have you tried disabling these to see if the behavior changes?

We are a bit short staffed now before/during Christmas. We expect a higher delay in answers until the beginning of January. I will be away until January 3rd, so unfortunately I will not have the time to look further into this before that. I am sorry for the inconvenience.

Best regards,

Edvin