I have been able to connect to the Golioth cloud servers even if it says the PSK and PSK_ID is incorrect. I think it might be using different values for checking than the actual crdentials.

@cwb the sample requires you load the appropriate PSK and PSK ID to the device secure key store. Did you do that? Also when it is loaded there you can safely ignore the messages about PSK being invalid.

https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers/tree/v2.4.x/samples/tracker#update-credentials-in-modem-one-time-only

Also you’re likely running on an old version of the modem firmware which is not compatible with 2.4.x. You’ll need to update it so it will work with your board.

Also the tracker firmware uses AT shell now. so you’ll need to prepend any AT commands with at

Ex:

at AT
at AT+CFUN=1

You will need to escape the % character if you use a command that utilizes it by typing two %%:

at AT%%CMNG

Thanks guys,

I followed the procedure for uploading the PSK so i will ignore that for now.

I’ll try the firmware upgrade. I am getting an error running the upgrade so will look at that in a couple of days when I’m back. interesting when I go to nRF programmer it won’t read the memory, I thought it was because it was a sparkfun board but now that the python script won’t work it might not be.

[Probes.com9] [ModemUARTDFU-com9] {
    "duration": 30009,
    "error_code": "Timeout",
    "message": "Image upload failed. Bad response from device",
    "operation": "upload_image",
    "outcome": "fail",
    "progress_percentage": 100
}
[Probes.com9] [ModemUARTDFU-com9] Error during image file upload. Upload returned an error.
[Probes.com9] [ModemUARTDFU-com9] Failed to program bootloader file
[Probes.com9] [ModemUARTDFU-com9] {"amountOfSteps":0,"description":"Starting modem boot loader","message":"Failed to program bootloader file\n","operation":"enter_programming_state","progressPercentage":0,"result":"fail","step":0}
[Probes.com9] [ModemUARTDFU-com9]
[Probes.com9] [ModemUARTDFUProbe] Failed to program DFU package
[HighLevel] Failed programming the device.
[Probes.com9] b'An error was reported by NRFJPROG DLL: -220 TIME_OUT. \n[Probes.com9] [ModemUARTDFU-com9] Error during image file upload. Upload returned an error.\n\textra: [Probes.com9] [ModemUARTDFU-com9] Failed to program bootloader file\n\textra: [Probes.com9] [ModemUARTDFU-com9] \n\textra: [Probes.com9] [ModemUARTDFUProbe] Failed to program DFU package\n\textra: [HighLevel] Failed programming 
the device.'
[Probes.com9] [ModemUARTDFUProbe] Uninitializing ModemUARTDFU probe at serial port com9.
[Probes.com9] [ModemUARTDFU-com9] Sending device reset request
[Probes.com9] [ModemUARTDFU-com9] Sending reset request to device.
[Probes.com9] [ModemUARTDFU-com9] Closing connection to mcuboot device
[Probes.com9] [ModemUARTDFU-com9] serial port com9 closed.
[Probes.com9] [ModemUARTDFU-com9] {
    "duration": 1,
    "error_code": "Ok",
    "operation": "close_uart",
    "outcome": "success",
    "progress_percentage": 100
}
[HighLevel] Done.
[HighLevel] Closing and freeing sub dlls.
Traceback (most recent call last):
  File "C:\Users\Admin\new-tracker\nfed\samples\mfw_update\update_modem.py", line 43, in <module>
    run(args.uart, args.firmware, args.baudrate)
  File "C:\Users\Admin\new-tracker\nfed\samples\mfw_update\update_modem.py", line 26, in run
    modem_dfu_probe.program(modem_firmware_zip)
  File "C:\Users\Admin\.zephyrtools\env\lib\site-packages\pynrfjprog\HighLevel.py", line 406, in program
    raise APIError(result, error_data=self.get_errors(), log=self._logger.error)
pynrfjprog.APIError.APIError: An error was reported by NRFJPROG DLL: -220 TIME_OUT.
[Probes.com9] [ModemUARTDFU-com9] Error during image file upload. Upload returned an error.
        extra: [Probes.com9] [ModemUARTDFU-com9] Failed to program bootloader file
        extra: [Probes.com9] [ModemUARTDFU-com9]
        extra: [Probes.com9] [ModemUARTDFUProbe] Failed to program DFU package
        extra: [HighLevel] Failed programming the device.
PS C:\Users\Admin\new-tracker\nfed\samples\mfw_update>

Reading the memory requires an external programmer. You can upgrade the MFW with that as well if you have one.

External programmer:
https://docs.circuitdojo.com/nrf9160-programming-and-debugging.html#requirements-for-external-programming-and-debugging

Updating MFW with external programmer:
https://docs.circuitdojo.com/nrf9160-managing-mfw.html#modem-firmware-update-with-nrfjprog

Note: you don’t need the Tag Connect cable for the Thing Plus variant.

Thanks Jared,

i’ll start running through some troubleshooting on the external programing now.

going through those instructions you sent I run into some errors with jlink.

C:\Users\Admin>jlink
SEGGER J-Link Commander V7.92c (Compiled Aug 30 2023 15:00:03)
DLL version V7.92c, compiled Aug 30 2023 14:58:23

Connecting to J-Link via USB…FAILED: Cannot connect to J-Link.

2 months later
Terms and Conditions | Privacy Policy