• State Verified Answer
  • Replies 12 replies
  • Subscribers 64 subscribers
  • Views 3305 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 228868
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

LTE link monitor does not work with nRF9160D DK. Why?

Yusuke

LTE link monitor does not work.

OS: Mac
SEGGER IDE: v4.16
place: Tokyo in Japan.

I set up the environment from scratch following Get Started Assistant v0.9.2, updated firmware to 0.7.0-15.alpha, and then activated SIM card.
I'm using v0.4.0 of nrf repository, the latest one.

It was weird that even though README.rst file explains I should run: pip install nrf9160_mdm_dfu-0.10.1+dev-py3-none-any.whl, but there is only nrf9160_mdm_dfu-0.10.0+dev-py3-none-any.whl, instead of nrf9160_mdm_dfu-0.10.1+dev-py3-none-any.whl. I installed nrf9160_mdm_dfu-0.10.0+dev-py3-none-any.whl.

After that, I built and run at_client program to a nRF9160DK and it was successful.

Finally, I installed LTE link monitor v0.9.1, but there is no response and always timeout happens. 

Can anyone give any advice? Thank you in advance.

Parents Reply Children
  • 0 in reply to Yusuke

    Good to hear that you figured it out! As your link says, the secure boot application has been changed into the secure partition manager (SPM). There is updated documentation here for the v0.4.0 release & here for the master branch. The SPM example should be run as a nrf9160_pca10090 board because it sets up the secure & non-secure partitions on flash & the at client application should be setup as a nrf9160_pca10090ns (non secure) board because it is located on the non-secure part of flash.

    Not sure why the UART is red. I have tested myself with the at client example from NCS v0.4.0 & the UART is green for me (i.e. flow control is enabled). Did you try pressing the reset button after you connected to your device in the LTE Link Monitor?

  • 0 in reply to Bjørn Kvaale

    I'm using Mac.

    It is weird that the commands below on nRF Connect SDK are not verified while I can build and run programs without problems.

    ・brew install cmake
    ・brew install python3
    ・pip3 install --user west

    This may cause UART issue. Do you have any advice?

Related