LTE Link Monitor

cnoda

Hi,

I am testing the nRF6190-Feather (first time).
Below is the VS Code term output:

Executing task: zephyr-tools -b
Device found but failed to open: Operation not supported or unimplemented on this platform
Could not open device 10c4:ea60
Terminal will be reused by tasks, press any key to close it.
Executing task: newtmgr -c vscode-zephyr-tools image upload c:\Users\xxxxx\xxxx\nfed\samples\at_client\build\zephyr\app_update.bin -r 3 -t 0.25

114.29 KiB / 114.29 KiB [==============================================================================================================================================================================================================================================] 100.00% 16.04 KiB/s 7s
Done
- Terminal will be reused by tasks, press any key to close it.
- Executing task: newtmgr -c vscode-zephyr-tools reset
  Done

The second line is not very reassuring but given the rest succeeded, I assume the device is programmed.
When I connect to it via LTE Link Monitor, the serial port opens, but all AT commands time out.
On the left panel, UART | MODEM | UICC indicators are all red.

There’s an activated sim card installed on the device.

Any clue what may be missing? :

//Claro

jaredwolff

Hi Claro!

Are you using Windows? Currently the automatic bootloader function doesn’t work for Windows. 😥

Looks like the transfer did go through though. Sometimes you may have to hit the reset button yourself to check. You can use the Zephyr Tools: Serial Monitor and type commands in the terminal as well. An easy way to check is to run AT and you should get OK back immediately.

On the LTE link monitor side, make sure you’re connecting to the correct serial port. I’ve made that mistake more than once!

jaredwolff

Also, I should also add auto bootloader only works on v5 of the nRF9160 Feather and newer.

cnoda

Hi Jared,

Thanks, the automatic bootloader is not an issue.
I’m not shy with the RST button.
However, I don’t know which ver this one is.
Please see: https://ibb.co/FHL7nhm

I am in Win10 atm - and installed the SL CP210x driver.
Inside VS Code, the port speed that works (for programming) is 10000000.
I used the DM to adjust various SP param too.
And also tried Zephyr serial monitor, setting all to 115200 via Newtmgr.

The port is unresponsive.

I’d try in Ubuntu later. Is Win10 known as problematic for the sp?

//Claro

jaredwolff

cnoda ahh you’re on OG! You have version 1! BRD-0015-01.

It’s possible that the bootloader won’t run with the newer SDK samples. I have run into this in the past. Do you have a programmer/cable? Programming a more up-to-date bootloader will likely resolve this.

Otherwise I can send you a discount code to get a newer board.

cnoda

I have an nRF52840-DK, but the programming cable doesn’t work on the feather.
Ideally, I check that the SIM works and see the signal level and a public IP address assigned.
But, yes, all alternatives can be considered. What do you recommend?
//Claro

cnoda

I am looking at this: https://www.digikey.se/en/products/detail/tag-connect-llc/TC2070-IDC-NL/3986444

jaredwolff

TC2030-CTX-NL is the part you’d need. Digikey does not have it in stock.

https://www.tag-connect.com/product/tc2030-ctx-nl-6-pin-no-legs-cable-with-10-pin-micro-connector-for-cortex-processors

You’d also need a nRF91DK or nRF53DK to program the nRF9160 Feather. (nRF52DK doesn’t work unfortunately)

jaredwolff

I’m looking into some future options that may help with this so stay tuned on that front.

cnoda

How does one know which hw ver is this: https://www.digikey.se/en/products/detail/circuit-dojo/PASSY-NRF9160-FEATHER/13668137

jaredwolff

That’s V5. I know because I sent them there. 🙂

cnoda

Thanks, Jared. This is my more cost-effective, sustainable, and technically friendly solution. I’ll order it and see about the sp again with the new bootloader.

jaredwolff

Ok!