Possible SIGTRAP in Softdevice S140

RE: Possible SIGTRAP in Softdevice S140

patric — Fri, 27 Oct 2023 12:06:20 GMT

Issue was due bad ram in the MCU. Closing issue.

RE: Possible SIGTRAP in Softdevice S140

patric — Fri, 25 Aug 2023 10:27:44 GMT

Private issue has been created. 313592

RE: Possible SIGTRAP in Softdevice S140

Einar Thorsrud — Fri, 25 Aug 2023 09:35:25 GMT

Hi,

I see. None of that should explain why you see a difference in the buffer handling in the logger, though. How did you narrow down to the values of the pointers in nrf_memobj_alloc()? Could it be that you are missing something when debugging? First of all, I would suggest disablign optimization when debugging you have not done so. And as you wrote earlier that you had some problems with GDB (I know I do), perhaps it would be better to use a GUI debugger, like Segger Ozone? (note that you. need to change the Ozon configuration to start from address 0 as described in this post, or just attach to the running target if the issue does not occur immediately).

[quote user="patric"]Do you have a mail i could share the linker-scripts on?[/quote]

You can upload here (Insert -> Image/video/file) or make a new private case where you refer to this thread, and upload there if you do not want tos hare it publically.

RE: Possible SIGTRAP in Softdevice S140

patric — Fri, 25 Aug 2023 08:52:38 GMT

Hi,

bsp_board_init() has been changed to not use any led's or buttons as there are other devices connected, ie a empty function compared with components/boards/boards.c.

NRF_DFU_HW_VERSION has been changed.

New signing key for application image as been included.

Aligned ld linker-scripts to keep the rtt sections at the same place between both bootloader and application. We are using SEGGER_RTT_SECTION set to ".rtt" and then defining a

.rtt (NOLOAD) :
{
} > RAM

in the linker-script.

Of course using a external segger jlink on the custom board instead of the embedded jlink on the DK board. JMemExe, JLinkGDBServer and JLinkRTTViewerExe works as expected from what i can see.

During troubleshooting i did changed the linker-script to allocate a bit more ram for the SD.

RAM (rwx) : ORIGIN = 0x20008000, LENGTH = 0x38000

Do you have a mail i could share the linker-scripts on?

RE: Possible SIGTRAP in Softdevice S140

Einar Thorsrud — Fri, 25 Aug 2023 08:26:27 GMT

Hi,

What is the differences in the firmware you run on the DK (successfully) and the firmware you run on your custom board?

RE: Possible SIGTRAP in Softdevice S140

patric — Thu, 24 Aug 2023 10:24:59 GMT

The reason seems to be that nrf_memobj_alloc() in nrf_log_frontend_dequeue() returns NULL

This happens because

if (p_pool->p_cb->p_stack_pointer > p_pool->p_stack_base)
in
nrf_balloc_alloc() fails

p_stack_pointer = 0x20002953

p_stack_base = 0x2000926c

RE: Possible SIGTRAP in Softdevice S140

patric — Thu, 24 Aug 2023 09:05:21 GMT

This is not in the softdevice. After further digging, and handeling signals a bit better in gdb, this is happening during RTT logging backend init/first log within the bootloader.