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.

[Hoang]

Hi Yusuke, 

the current status: YES. We must use nRF91 DK to program fro THINGY:91 

Goodluck

Hoang Nguyen

[Hoang]

you can read more an ARMv8 programmer/debugger

[Yusuke]

Thanks a lot!

I have J-link and it should support Cortext M33
https://www.embitek.co.jp/product/jlink-compare.html

Can I use J-link to flash programs to Thingy:91?

[Yusuke]

With J-Link, I can flash the at_client hex file to Thingy:91, but it doesn't work on LTE Link monitor. why...

[Heidi-Irene Harvey Sollie]

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

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