CAN NOT GET AT COMMAND SAMPLE TO WORK

RE: CAN NOT GET AT COMMAND SAMPLE TO WORK

stevenminnick — Thu, 06 Jun 2019 14:35:09 GMT

But I would update the radio firmware to 0.7.0_29 from the same link. And update your GIT repos from the nordic playground to the latest. And open the AT Client project and build and compile that. Flash the merged.hex file.

If you want a hex file to playwith, I'll attach it here. Make sure you update the radio firmware first. And then flash this hex file with anything, either the commands I specified or the GUI.

devzone.nordicsemi.com/.../7317.merged.hex

RE: CAN NOT GET AT COMMAND SAMPLE TO WORK

stevenminnick — Thu, 06 Jun 2019 14:29:38 GMT

I made them by compiling 0.3.0 and renaming the output from the SES so I knew what the hex files are. The above was an example.

This only works with radio firmware

0.6.8-131.alpha https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

So don't keep going with this, but you can test and make sure it works.

devzone.nordicsemi.com/.../at_5F00_client.hex

devzone.nordicsemi.com/.../0172.Secure_5F00_Boot.hex

Rename the download files or the above commands to work as necessary.

RE: CAN NOT GET AT COMMAND SAMPLE TO WORK

anasal — Thu, 06 Jun 2019 13:19:27 GMT

Where I can get those Secure_Boot.hex and at_client.hex files?

RE: CAN NOT GET AT COMMAND SAMPLE TO WORK

stevenminnick — Thu, 06 Jun 2019 12:02:27 GMT

Also your talk about loading the Secure Boot sample makes me think you are on old code as well. Secure Boot has been renamed SPM or Secure Partition Manager. And there is new AT Client code that has the response to serial commands as an interrupt as opposed to being started from main.c.

So I would update your radio firmware to the latest, 0.7.0_29 is the latest as I type this. Update all the git repos, with west or git (follow the getting started example). Open the AT Client project and make sure you use the _NS for board name. And when you compile you will get a merged.hex. That will be the SPM and AT client and that should work too.

RE: CAN NOT GET AT COMMAND SAMPLE TO WORK

stevenminnick — Thu, 06 Jun 2019 11:52:16 GMT

If you loaded the secure boot sample and then uploaded the AT command sample, did you use the GUI programmer? Because both the secure boot and at command sample hex files have to be loaded simultaneously. And the GUI programmer can erase the whole chip and load what you program.

When looking at the LTE Link monitor, hit the reset button on the dev kit and make sure you see the secure boot stuff fly across the screen. If not, it's not on there. In your picture it says AT Host started but doesn't have the secure boot text before it (trust me when it's there you will see it. It's pages of text as it boots)

I would say secure boot is not on your device. When you programmed the AT client you erased the secure boot.

You can use the GUI programmer by loading BOTH the secure boot and AT client hex code files and then program. Or use the command line:

nrfjprog --eraseall -f nrf91
nrfjprog.exe --program Secure_Boot.hex --sectorerase -r -f nrf91 --verify
nrfjprog.exe --program at_client.hex --sectorerase -r -f nrf91 --verify

Then connect the LTE link monitor, hit the reset button on the dev kit, and check that you see all the secure boot stuff fly on the screen. AT commands should work.