This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cannot debug the multillink_central example (s120)

Hi nordics.

I am trying to do s120 multilink_central example.

However, this example doesn't work well, and I cannot debug central example.

-Environment-

board: nrf51822 DK (6310)

debugger: J-link lite.

sdk version : 6_1

softDevice version: s120_nrf51_2.0.0

--

First, I set the ROM1 start:0x1d000 , size 0x23000
and RAM1 start 0x20002000, size 0x2000 for s120.

image description

and, I set the J-link driver like this....

image description

And I found that I can program this example with nRFgo studio, but i can not download with "download button" in the uvision tool.

When I try to debug this, I get this error message.

image description

How can I solve this problem?

Parents Reply Children
  • Thanks Kristin.

    I set the port to the SW.

    So I can debug the example.

    However, I got error message "[APPL]: ASSERT: ..\main.c, 412, error 0x00002009"

    Even though, I change the IRAM1 start L 0x20002800 // size: 0x1800

    this is my memory area setting IROM1 : start : 0x1d000 size : 0x23000 IRAM1 : start : 0x20002800 size : 0x1800

  • You were able to program both softdevice and application into the chip? When do you get the assert? As soon as you start it up or do you see the example running for some time before it assert?

    Have you modified the code example to match the HW you have? The pin definition will be different from the default code compared to the nRF6310-DK setup. It seems like you are asserting in the Bond delete part.

  • @Asbjørn Thank you so much for replying to my question.

    I can program softdevice and application both. And, I get the assert error as soon as I start device up. And the error is from SOFTDEVICE_HANDLER_INIT

    I didn't modify the example code, and I using 6310-DK . do you mean should I change the pin definition eventhough this case?

  • As long as you use code examples for 6310, it should be correct. Make sure that you still are using the correct definitions in the options for target under the C/C++ tab. I'm pretty sure you do as long as the example is unchanged. If it asserts in the softdevice handler init it might be related to clock source used for the softdevice. What are you using there and are you sure that these clock sources are available? If you haven't tried it yet, please try to use the internal LFRCOSC 32 kHz to make sure that there 32 kHz source is available.

Related