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

How to install at_client to Thingy:91?

I got Thingy:91 and want to install at_client to it, but it doesn't work well.

What I did is

1. Check out a pull request  and update firmware referring to this link

2. Connect j-link and usb to Thingy:91.

3. Open LTE Link Monitor.

It always restarts and never accepts at command.

Any tips?

Parents Reply Children
  • Hi! First, you have to uncheck the "Auto device/port filter" option in the bottom right corner, see picture below. Then make sure you are connected to the correct COM port, the Thingy:91 has two. Then keep power cycling the device (switching it on and off), resetting LTE Link Monitor (CTRL + R) until you get a connection. 

    Could you provide the Log output if it still doesn't work when you try this?

    Best regards,

    Heidi

  • I think I did as you instruct, but it doesn't work out. 

    Could you tell me exact procedure in each step? What does "the keep power cycling the device (switching it on and off)" mean?

    Also, LTE Link Monitor communicates with device through USB, not J-Link, right?

    This is the log. I don't know why LTE Link Monitor uses USB Port1, even though I select Port 12 or 13..

    2019-09-09T01:35:52.437Z INFO Application data folder: C:\Users\yusuke.fukuhara\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
    2019-09-09T01:35:52.519Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
    2019-09-09T01:35:52.519Z DEBUG App path: C:\Users\yusuke.fukuhara\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
    2019-09-09T01:35:52.519Z DEBUG nRFConnect 3.2.0 is supported by the app (^3.2.0)
    2019-09-09T01:35:52.519Z DEBUG nRFConnect path: C:\Users\yusuke.fukuhara\AppData\Local\Programs\nrfconnect\resources\app.asar
    2019-09-09T01:35:52.519Z DEBUG HomeDir: C:\Users\yusuke.fukuhara
    2019-09-09T01:35:52.519Z DEBUG TmpDir: C:\Users\YUSUKE~1.***\AppData\Local\Temp
    2019-09-09T01:35:52.521Z VERBOSE Could not fetch serial number for serial port at COM1
    2019-09-09T01:35:55.382Z INFO Modem port is opened
    2019-09-09T01:35:55.388Z DEBUG modem >> AT+CFUN?\x0D\x0A

    Additionally, should I update firmware?

  • Hi, I think I misunderstood. To actually flash the at_client example to your Thingy:91, you have to use the Programmer application in nRF Connect. the LTE Link Monitor is a way to communicate with the modem after you have flashed the example. Is this what you're wondering? Have you flashed the thingy91_at_client.hex hex file to the Thingy:91?

     

    Yusuke said:
    What does "the keep power cycling the device (switching it on and off)" mean?

     This just means switch the Thingy:91 on and off while you're trying to connect.

     

    Yusuke said:
    LTE Link Monitor communicates with device through USB, not J-Link, right?

     Yes, correct.

     

    Yusuke said:
    Additionally, should I update firmware?

     Yes, you should upload the modem firmware to version 1.0.1.

  • >To actually flash the at_client example to your Thingy:91, you have to use the Programmer application in nRF Connect.

    When I flash a program to nRF9160 DK, I just build and run on SES. Do I have to use Programmer application on nRF Connect to flash it to Thingy:91? I used the Programmer application to upgrade modem firmware before. I never used it to flash a program.

  • Yes, to flash an already built .hex file you should use the Programmer application. To do this, connect the J-link cable to the thingy and the DK like in the picture.

     

    Then, select device "PCA10090". 

    Select "Add HEX file" and add the at_client example. Then select "Erase & write". When it's done, you can select "Read" to make sure the file was flashed. Then the at_client example should be running on your Thingy and you can use LTE Link Monitor to confirm by communicating with the modem using AT commands.

Related