Reconnecting LTE after Disconnect

Built and installed the at_client, then opened up LTE Monitor, pressed RST button and the terminal showed this:

2022-03-03T02:48:48.515Z DEBUG modem << õýÕ÷¯ÿõ÷õÕUý÷·Uÿõ÷÷ýßõõõõõõ÷õõ÷ÿõ½×õõý÷µÿÿõ÷·ÿßÿõýwõ÷õÿuõõÿõUuW÷uõõUu_UuõõWu]UõýUuWUuõõUuýõÝõWw}õuýWuÿõýõUw]UõõUwÿõßõUõýUõýWw}õõõýõ÷õ]ÝõUõõUõýWuõUõýUwõUõýUuõUõýWuÿ]]ÕõW÷õõÝõWw_uõõõýuWuõõõUuWuõõõýõõõõÝõWõ÷õõýõWWÿÕwuõwß__õU»uuu}õU÷WýUõõU÷õõ_}Uý}ÝõýõõõõýõÿuõõU*** Booting Zephyr OS build v2.6.99-ncs1-1 ***
2022-03-03T02:48:48.520Z DEBUG modem << The AT host sample started

Kind of gives me mixed messages there – looks like the at_client is working, but what’s the garbage before that? Is it maybe some random data that’s been sent as a test?

It’s the SPM image running at 1M baud. Change your BAUD to 1M to see what it says.

If you hit AT and press enter, does it respond?

For monitoring its 115200

For transferring its 1000000

How do I change the baud rate to 1M, and is that a potential fix for the problem of updating the modem firmware?

If you wanted to view that gibberish you’d have to use a different program to view the output. If you’re using VSCode Zephyr Tools you can invoke zephyr-tools-monitor to monitor a different BAUD:

❯ zephyr-tools-monitor --port COM3 --baud 1000000

Nevertheless, the update_mfw sample runs by default at 1000000 BAUD. You don’t need to change anything.

How old is the board you’re working with?

jaredwolff How old is the board you’re working with?

Purchased within the last year.

jaredwolff If you’re using VSCode Zephyr Tools you can invoke zephyr-tools-monitor to monitor a different BAUD

Ah ha!

> zephyr-tools-monitor --port COM3 --baud 1000000
Connecting..
Connected to COM3!
*** Booting Zephyr OS build v2.6.99-ncs1-1  ***
Flash regions           Domain          Permissions
00 03 0x00000 0x20000   Secure          rwxl
04 31 0x20000 0x100000  Non-Secure      rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region             Domain          Permissions
00 07 0x00000 0x10000   Secure          rwxl
08 31 0x10000 0x40000   Non-Secure      rwxl

Peripheral              Domain          Status
00 NRF_P0               Non-Secure      OK
01 NRF_CLOCK            Non-Secure      OK
02 NRF_RTC0             Non-Secure      OK
03 NRF_RTC1             Non-Secure      OK
04 NRF_NVMC             Non-Secure      OK
05 NRF_UARTE1           Non-Secure      OK
06 NRF_UARTE2           Secure          SKIP
07 NRF_TWIM2            Non-Secure      OK
08 NRF_SPIM3            Non-Secure      OK
09 NRF_TIMER0           Non-Secure      OK
10 NRF_TIMER1           Non-Secure      OK
11 NRF_TIMER2           Non-Secure      OK
12 NRF_SAADC            Non-Secure      OK
13 NRF_PWM0             Non-Secure      OK
14 NRF_PWM1             Non-Secure      OK
15 NRF_PWM2             Non-Secure      OK
16 NRF_PWM3             Non-Secure      OK
17 NRF_WDT              Non-Secure      OK
18 NRF_IPC              Non-Secure      OK
19 NRF_VMC              Non-Secure      OK
20 NRF_FPU              Non-Secure      OK
21 NRF_EGU1             Non-Secure      OK
22 NRF_EGU2             Non-Secure      OK
23 NRF_DPPIC            Non-Secure      OK
24 NRF_REGULATORS       Non-Secure      OK
25 NRF_PDM              Non-Secure      OK
26 NRF_I2S              Non-Secure      OK
27 NRF_GPIOTE1          Non-Secure      OK

SPM: NS image at 0x20200
SPM: NS MSP at 0x20020760
SPM: NS reset vector at 0x225c9
SPM: prepare to jump to Non-Secure image.

Just restarted my system and tried again with the mfw_update. Still fails to program the device.

> python3 update_modem.py mfw_nrf9160_1.3.1.zip com3 1000000
# modem firmware upgrade over serial port example started.
[HighLevel] Creating new probe
[HighLevel] Initialize new probe.
[Probes.com3] [ModemUARTDFUProbe] Dll directory is C:\Users\barli\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pynrfjprog\lib_x64.
[Probes.com3] [ModemUARTDFUProbe] Find and connect to dfu dll
[Probes.com3] [ModemUARTDFUProbe] Using DFU dll at C:\Users\barli\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pynrfjprog\lib_x64\NRFDFU.dll.
[Probes.com3] [ModemUARTDFUProbe] Load library at C:\Users\barli\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pynrfjprog\lib_x64\NRFDFU.dll.
[Probes.com3] [ModemUARTDFUProbe] Library loaded, loading member functions.
[Probes.com3] [ModemUARTDFUProbe] Member functions succesfully loaded.
[Probes.com3] [ModemUARTDFU-com3] Initialize new probe.
[Probes.com3] [ModemUARTDFU-com3] Successfully opened port: com3@1000000,flow_control:none,parity:none.
[Probes.com3] [ModemUARTDFU-com3] {
    "duration": 891,
    "error_code": "Ok",
    "operation": "open_uart",
    "outcome": "success",
    "progress_percentage": 100
}
[HighLevel] Probe initialization complete!
[Probes.com3] [ModemUARTDFU-com3] Check if provided file exists
[Probes.com3] [ModemUARTDFU-com3] Check if provided file can be read
[Probes.com3] [ModemUARTDFU-com3] Programming bootloader
[Probes.com3] [ModemUARTDFU-com3] Programming modem bootloader 72B3D7C.ipc_dfu.signed_1.1.0.ihex.
[Probes.com3] [ModemUARTDFU-com3] Extracting 13416 bytes from 72B3D7C.ipc_dfu.signed_1.1.0.ihex.
[Probes.com3] [ModemUARTDFU-com3] {
    "duration": 0,
    "message": "Calculating image size",
    "operation": "upload_image",
    "progress_percentage": 5
}
[Probes.com3] [ModemUARTDFU-com3] {
    "duration": 1,
    "message": "Uploading image to device",
    "operation": "upload_image",
    "progress_percentage": 10
}
[Probes.com3] [ModemUARTDFU-com3] {
    "duration": 30004,
    "error_code": "Timeout",
    "message": "Image upload failed. Bad response from device",
    "operation": "upload_image",
    "outcome": "fail",
    "progress_percentage": 100
}
[Probes.com3] [ModemUARTDFU-com3] Error during image file upload. Upload returned an error.
[Probes.com3] [ModemUARTDFU-com3] Failed to program bootloader file
[Probes.com3] [ModemUARTDFUProbe] Failed to program DFU package
[HighLevel] Failed programming the device.
[Probes.com3] b'An error was reported by NRFJPROG DLL: -220 TIME_OUT. \n[Probes.com3] [ModemUARTDFU-com3] Error during image file upload. Upload returned an error.\n\textra: [Probes.com3] [ModemUARTDFU-com3] Failed to program bootloader file\n\textra: [Probes.com3] [ModemUARTDFUProbe] Failed to program DFU package\n\textra: [HighLevel] Failed programming the device.' 
[Probes.com3] [ModemUARTDFUProbe] Uninitializing ModemUARTDFU probe at serial port com3.
[Probes.com3] [ModemUARTDFU-com3] Sending device reset request
[Probes.com3] [ModemUARTDFU-com3] Sending reset request to device.
[Probes.com3] [ModemUARTDFU-com3] Closing connection to mcuboot device
[Probes.com3] [ModemUARTDFU-com3] serial port com3 closed.
[Probes.com3] [ModemUARTDFU-com3] {
    "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 "D:\David\Wildlife\DeterGents\ZephyrToolsRepo\nfed\samples\mfw_update\update_modem.py", line 43, in <module>
    run(args.uart, args.firmware, args.baudrate)
  File "D:\David\Wildlife\DeterGents\ZephyrToolsRepo\nfed\samples\mfw_update\update_modem.py", line 26, in run
    modem_dfu_probe.program(modem_firmware_zip)
  File "C:\Users\barli\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pynrfjprog\HighLevel.py", line 388, 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.com3] [ModemUARTDFU-com3] Error during image file upload. Upload returned an error.
        extra: [Probes.com3] [ModemUARTDFU-com3] Failed to program bootloader file
        extra: [Probes.com3] [ModemUARTDFUProbe] Failed to program DFU package
        extra: [HighLevel] Failed programming the device.

Help?

Since you’re able to communicate with the device it’s probably not a USB issue. Just to confirm, you can flip the orientation of your USB connector (turn it 180 degrees from the way you were using it) to see if that makes an improvement.

Do you only have one board to try this on Barliesque ?

Barliesque if you got another machine to work, I expect to think it’s some type of issue with the Python library. In the case of the above, it looks like maybe you didn’t install the library?

**Failed to load dll** at C:\Users\usaf\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pynrfjprog\lib_x64\NRFDFU.dll.

Do you have the command line tools installed?

https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download

Make sure you have the latest

I’ve tried downgrading both machines with: pip install "pynrfjprog<10.14"
Neither was able to complete the update.

An error was reported by NRFJPROG DLL: -220 TIME_OUT.

Barliesque I’m not sure how long you want to spend on this but my next step would be to reach out to Nordic since it’s their library.

Alternatively, you may want to get your hands on a nRF9160dk so you can update modem firmware that way. Or, another alternative, you can send it my way and I can update the modem firmware for you. Let me know.

jaredwolff Or, another alternative, you can send it my way and I can update the modem firmware for you.

That is kind. Unfortunately, we haven’t got the time available for turnaround. Would you be up for checking things out directly with TeamViewer?

Success at last. I don’t have a clear picture of what exactly had to be done, as Brian got on with TeamViewer to have a poke around. Anyway, it looks like things are working at long last. Thank you, Jared, for your help.

Barliesque oh awesome. If you have an idea of what Brian did that would be helpful for everyone to know. Overall I’m glad you’re unstuck!!