• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 1866 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 209951
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

The nRF52840 stops working in the multilink example.

jwcheon

Hi,

In the multilink example, we are working on 4 links.
I have 8 devices.

In the test process, if you connect 4 units first and turn off the 4 units connected at the same time, 4 other units try to connect and then they die.

-------------------------------------------------- -------

<info> app: LBS central link 0x1 disconnected (reason: 0x13)
<info> app: Start scanning for device name Nordic_Blinky.
<info> app: LBS central link 0x3 disconnected (reason: 0x13)
<info> app: Start scanning for device name Nordic_Blinky.
<info> app: LBS central link 0x2 disconnected (reason: 0x13)
<info> app: Start scanning for device name Nordic_Blinky.
<info> app: LBS central link 0x0 disconnected (reason: 0x13)
<info> app: Start scanning for device name Nordic_Blinky.
<error> app: Fatal error
<warning> app: System reset
<info> app: Multilink example started.
<info> app: USBD CDC ACM example started.
<info> app: Start Dongle Mode: 0x1
<info> app: No USB power detection enabled
Starting USB now

-------------------------------------------------- ------

Can a connect packet and a disconnect packet be killed if they are twisted?

Parents
  • 0

    Hi Jiwoon,

    The disconnect reason 0x13 is "BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION " which is described as "Remote User Terminated Connection".

    If you receive this error on the Central side it is the Peripheral that is disconnecting. I would recommend that you debug the peripherals. I would also recommend that you turn on RTT logging and increase the default severity level for the logging. (this is done in sdk_config.h).

    So you have 8 nrf52840 DKs? (or custom boards?)

    What DKs run which example? (unmodified example?)

    Is it possible to give some steps in how this could be reproduced by others?

     

    Thanks,

    //Martin L

Reply
  • 0

    Hi Jiwoon,

    The disconnect reason 0x13 is "BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION " which is described as "Remote User Terminated Connection".

    If you receive this error on the Central side it is the Peripheral that is disconnecting. I would recommend that you debug the peripherals. I would also recommend that you turn on RTT logging and increase the default severity level for the logging. (this is done in sdk_config.h).

    So you have 8 nrf52840 DKs? (or custom boards?)

    What DKs run which example? (unmodified example?)

    Is it possible to give some steps in how this could be reproduced by others?

     

    Thanks,

    //Martin L

Children
  • 0 in reply to Martin Lesund

    Hi, Martin.

    I solved this problem.
    There were not eight other nrf52840 DKs, but there was a custom board.

    I could not figure out exactly what the problem was. But if you tell me how this happened,

    The NRF Board is dead when connecting devices 5, 6, 7, and 8 at the same time while releasing the bluetooth connection of devices 1, 2, 3 and 4 while connecting devices 1, 2, 3 and 4.

    Perhaps the disconnect will make the scan start and the scan start will start even when connect is made. The NRF Board seems dead because the scan start is restarted several times while trying to connect or disconnect.

    So, the way I solved was to fix the flag so that scan start does not restart many times.
    As a result, the NRF Board did not die at the same time as disconnecting four devices and connecting four devices.

Related
Terms of service