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

nRF9160 lte_ble_gateway sample problem on custom board

Hello:

I have nRF9160 SIP custom board. The pins on custom board almost the same as nRF9160DK.

I can run lte_ble_gateway sample on nRF9160DK without problem:

But there is error when run lte_ble_gateway sample on custom board:

I made two experiments to see problem on nRF52840 or nRF9160 on my customboard:

1. Erase nRF52840 and flash secure_boot + lte_ble_gateway to nRF9160 on nRF9160DK.

Erase nRF9160 and flash hci_uart to nRF52840 on my custom board.

Connect nRF52840 on my board to nRF9160 on nRF9160DK and the demo run without problem.

2. Erase nRF9160 and flash hci_uart to nRF52840 on nRF9160DK

Erase nRF52840 and flash secure_boot + lte_ble_gateway to nRF9160 on my custom board.

Connect nRF9160 on my board to nRF52840 on nRF9160DK and the demo run with the same problem as the picture above.

    Uart pin connect between nRF52840 and nRF9160 on custom board is the same as nRF9160DK.

    So I think there is problem with nRF9160SIP on my custom board.

One different I know between custom board and nRF9160DK is that there is no certificate file in my custom board.

Will this affect the lte_ble_gateway demo ?

I don't know the process of ble_lte_gateway on nRF9160SIP.

But I know that nRF52840 and nRF9160 can communicate through uart with the log: HW Variant: nRF52x (0x0002)

I just need to check they can communicate through uart(Pin 17, 18, 19, 21 on nRF9160 and 17, 20, 15, 22 on nRF52840).

Or can anyone suggest another demo to check that?

Thank you.

Parents
  • I can get the same error log after I esased nRF52840 on normal working nRF9160DK.

    So it seemed that there is problem with uart communication between nRF52840 and nRF9160 according to the error code.

  • Hi,

    If the nRF9160 and the nRF52840 is started at different times, the UART communication between them could get out of sync, and you will get this error. The error can also be seen using the nRF9160-DK under certain conditions. The workaround for the nRF9160-DK is to reset the chips at about the same time:

    1) Set the PROG/DEBUG switch to nRF52
    2) Push the reset button
    3) Set the PROG/DEBUG switch to nRF91
    4) Push the reset button

    Do you see this issue on the custom board, if you power up the nRF52840 and the nRF9160 at about the same time ?

    Note that we are currently working on a software solution for this issue.

Reply
  • Hi,

    If the nRF9160 and the nRF52840 is started at different times, the UART communication between them could get out of sync, and you will get this error. The error can also be seen using the nRF9160-DK under certain conditions. The workaround for the nRF9160-DK is to reset the chips at about the same time:

    1) Set the PROG/DEBUG switch to nRF52
    2) Push the reset button
    3) Set the PROG/DEBUG switch to nRF91
    4) Push the reset button

    Do you see this issue on the custom board, if you power up the nRF52840 and the nRF9160 at about the same time ?

    Note that we are currently working on a software solution for this issue.

Children
Related