- Edited
K2AAE if you need an AT interface the at_client example is a good start. Also the firmware that comes shipped on the device (I sent you that HEX image earlier) allows you to issue AT commands.
west update v1.3.1 fails
Actually it wasn’t you but here’s the forum link: https://community.jaredwolff.com/d/76-issue-with-dfu-mode
jaredwolff I get the same, Not allowed to download, I logged out and back in but Not allowed to download.
I installed SDK v1.3.2, added the stuff to west.yml, edit the prj.conf and tried to build, it couldn’t find the board. v1.3.2/zephyr/boards/arm was missing the feather board, copied it from v1.4.1 and built the at software with no errors, installed and no AT response.
If anyone has installed the D:\ncs\v1.4.1\nrf\applications\serial_lte_modem OR D:\ncs\v1.4.1\nrf\samples\nrf9160\at_client
What modem firmware and bootloader and SDK and version of feather ?
What am I missing that I can’t get a bin (bootloader) or hex (jlink) image to work?
I installed bootloader V2 does that make a difference?
K2AAE man this forum does not way to play nice sometimes!
Here’s the direct link: https://community.jaredwolff.com/assets/files/2021-02-09/1612877102-515080-v2-010421-1502-mergedhex.zip
K2AAE If anyone has installed the D:\ncs\v1.4.1\nrf\applications\serial_lte_modem OR D:\ncs\v1.4.1\nrf\samples\nrf9160\at_client
What modem firmware and bootloader and SDK and version of feather ?What am I missing that I can’t get a bin (bootloader) or hex (jlink) image to work?
I installed bootloader V2 does that make a difference?
I think you’re trying too many things at one time. It’s hard to isolate what the problem is. I would erase the chip and re-flash the bootloader. Put it in bootloader mode and make sure you can talk to it using newtmgr. I’m assuming you’ve already used the newtmgr command successfully at some point?
Once you get the above, then you can move on to the next step which would be to build the at_client firmware and load it with newtmgr. Make sure you hit the reset button on the board after loading or issue the newtmgr -c serial reset command.
I’ll build the at_client .bin and .hex and share it here if you need to compare a working environment to what you have set up on your end.
- Edited
jaredwolff I couldn’t sleep last night so I plugged the nrf9160-dk in and using v1.4.99 build I built and ran everything that didn’t use LTE, worked great. I had already built everything in nfed but the SMS example with v1.4.1 but I must have screwed up the at and serial_lte_modem source some how in v1.4.1.
I used the pdk with your at merged.hex with nrfjprog –program merged.hex –chiperase
It happened so fast I thought something was wrong and used the nRF Connect programmer to look at the feathers memory, it was good. Shut off the PDK and used putty:
AT
OK
a first…
I guess I’ll figure out how to remove v1.4.1 (v1.3.1, 1.3.2 also) then install a clean version of v1.4.1 and add nfed with the current directions… Thanks for your help on this moving disaster I created!
I have the IMEI now.
K2AAE Nice! Glad to see you’re making some progress now. 
- Edited
Using a hologram SIM:
But on the git examples I get:
D:\ncs\v1.4.1\nfed>west init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers –mr main
FATAL ERROR: already initialized in D:\ncs\v1.4.1, aborting.
Note:
In your environment, ZEPHYR_BASE is set to:
D:\ncs\v1.4.1\zephyr
This forces west to search for a workspace there.
Try unsetting ZEPHYR_BASE and re-running this command.D:\ncs\v1.4.1\nfed>
I did find the modem FW at v1.2.3 now.
K2AAE you shouldn’t run west init twice. You can add nfed to the west.yml as per the setup instructions.
jaredwolff I found that:
https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers
I have the west.yml modified but forgot that the new way brings the git with west update
While I was trouble shooting a non existent problem I compared the UART in nfr9160-DK to the feather and noticed a CP2105 would mirror the UART setup of the DK for 1mm and 20¢.