How to install at_client to Thingy:91?

[Yusuke]

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?

[Hoang]

hi Yusuke, 

Have you tried to flash at_client.hex for your THINGY:91? 

You can try: 

Use nRF91DK and Connect the Thingy:91 to the nRF9160DK board’s “Debug out” port using a 10-pin JTAG cable. 

And, try to flash the: thingy91_at_client.hex

You can read more on this link

Hope it can help

Hoang Nguyen

[Yusuke]

Hi, Hoang, thank you for your comment.

Do I have to use nRF9160 DK board to flash at_client firmware to Thingy:91?

That's inconvenient.

[Yusuke]

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?

[Heidi-Irene Harvey Sollie]

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.

[Yusuke]

>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.

[Heidi-Irene Harvey Sollie]

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.

[Yusuke]

Hi, Heidi, Thank you so much! It works out!

Do I have to use Programmer App to flash hex file to Thingy:91? Is this procedure correct?

1. Code on SES and generate hex file

2. Open Programmer App and flash it to Thingy:91.

[Yusuke]

It worked right after I flashed but doesn't work after I switched off and on. So weird..

[Heidi-Irene Harvey Sollie]

Oh, no. Sorry if that was confusing. If you're writing your own program in SES then you can build and flash with SES, as long as the Thingy is connected to your nRF9160 DK. 

I just meant that when the only thing you have is the already built hex file (like the one I attached in one of my comments below), then using the Programmer App is easiest.

[Yusuke]

I'm still stuck in at_command issue. 

The program works and responds AT command inputs right after I flash it. However it doesn't work after I switch off and on or push reset button. Heidi, does your Thingy:91 works correctly with at_client?

[Heidi-Irene Harvey Sollie]

Yes, I know what you mean. When I switch mine on and off and connect to the same COM port, it usually takes a few tries before it works. Try turning it off and on and connecting a few times, and also trying CTRL + R in LTE Link Monitor to refresh. 

Side note: the button on the Thingy:91 is not a reset button. The thingy doesn't have a soft reset, so the only way to reset the device is switching it off and back on again. 

[Yusuke]

>the button on the Thingy:91 is not a reset button
I see. I misunderstood.

I switch it off and on, refresh LTE Link Monitor, and disconnect and connect USB. However it doesn't work.
No response, even though "AT+CFUN?" shows up.