I am able to open up the Cellular Monitor and successrully select the device an get a connection. However the option to ' Open a Serial Terminal' is greyed out, and so not available.
I am able to open up the Cellular Monitor and successrully select the device an get a connection. However the option to ' Open a Serial Terminal' is greyed out, and so not available.
Hello Jack,
What device are you using? Is it a DK?
If you hover over the grayed out option, does it say anything about the reason why?
Regards,
Elfving
Hi Elfving,
Hovering the mouse over the two greyed out buttons doesn't show anything.
We're connecting to our own nRF 9160 based hardware with our own custom firmware. The FW includes Asset Tracker II FW. We've also included the necessary AT Host FW. We're currenlty running modem FW 1.3.3 on the device. Also we're using an nRF 52840 and a connectivity bridge to make the USB connection.
I can provide more details on request, but we appear to be making a successful connection from our desktop machine to the device. Here's the log file from the Cellular Monitor:
2024-05-28T15:40:51.137Z INFO Initialising nrfutil module: device
2024-05-28T15:40:51.168Z DEBUG Application data folder: C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-cellularmonitor
2024-05-28T15:40:51.191Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-05-28T15:40:51.193Z DEBUG App pc-nrfconnect-cellularmonitor v2.4.0 (official)
2024-05-28T15:40:51.193Z DEBUG App path: C:\Users\jackw\.nrfconnect-apps\node_modules\pc-nrfconnect-cellularmonitor
2024-05-28T15:40:51.193Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-05-28T15:40:51.193Z DEBUG nRFConnect path: C:\Users\jackw\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-05-28T15:40:51.193Z DEBUG HomeDir: C:\Users\jackw
2024-05-28T15:40:51.193Z DEBUG TmpDir: C:\Users\jackw\AppData\Local\Temp
2024-05-28T15:40:51.876Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-05-28T15:40:52.392Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-05-28T15:40:52.392Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-05-28T15:40:52.401Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-05-28T15:40:52.561Z INFO Using nrfutil-device core version: 7.7.1
2024-05-28T15:40:53.149Z INFO Using nrfutil-device version: 2.1.1
2024-05-28T15:40:53.149Z INFO Using nrf-device-lib version: 0.17.5
2024-05-28T15:40:53.149Z INFO Using nrfjprog DLL version: 10.24.0
2024-05-28T15:40:53.149Z INFO Using JLink version: JLink_V7.96i
2024-05-28T15:40:53.149Z WARN Installed JLink version does not match the expected version (JLink_V7.94e)
2024-05-28T15:40:53.494Z INFO Getting serialport options from persistent store THINGY91 12PLACEHLDRS.pc-nrfconnect-cellularmonitor
2024-05-28T15:40:53.496Z DEBUG Sending event "cellularmonitor: device connected"
BTW, we have JLink_V796i installed.
Hope that helps.
Regards,
Jack
OK, here's the command and response:
PS C:\Users\jackw> nrfjprog -v
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.96i
Regards,
Jack
Elfving, I need help here please. I'm stuck. I need to make the Cellular Monitor work. Can you help me out please.
Thanks,
Jack
Sorry about the wait,
JackW said:JLinkARM.dll version: 7.96i
That could be the issue. Though before we uninstall anything let's see if its anything else. Version 7.94e is what seems to come with the newest nRF Command line tools.
Are you following the requirements mentioned here, I think the same thing is mentioned in the pop-up when opening the Cellular monitor app?
Could you go to the "About" tab on the right, check "verbose logging", and give me the log?
Regards,
Elfving
Hi Elfving,
Yes, we did include the code snippet in our application FW.
Here is the verbose log file:
2024-06-07T16:33:23.022Z INFO Initialising nrfutil module: device
2024-06-07T16:33:23.053Z DEBUG Application data folder: C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-cellularmonitor
2024-06-07T16:33:23.073Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-07T16:33:23.076Z DEBUG App pc-nrfconnect-cellularmonitor v2.4.0 (official)
2024-06-07T16:33:23.076Z DEBUG App path: C:\Users\jackw\.nrfconnect-apps\node_modules\pc-nrfconnect-cellularmonitor
2024-06-07T16:33:23.076Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-07T16:33:23.076Z DEBUG nRFConnect path: C:\Users\jackw\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-07T16:33:23.076Z DEBUG HomeDir: C:\Users\jackw
2024-06-07T16:33:23.076Z DEBUG TmpDir: C:\Users\jackw\AppData\Local\Temp
2024-06-07T16:33:23.789Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-07T16:33:28.466Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-07T16:33:28.466Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-07T16:33:28.475Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-07T16:33:28.638Z INFO Using nrfutil-device core version: 7.11.1
2024-06-07T16:33:28.752Z INFO [PID:31936] nrfutil-device (version = 2.1.1, platform = x86_64-pc-windows-msvc) invoked with list --traits nordicUsb,serialPorts,jlink,mcuBoot --hotplug --json --log-output=stdout --log-level trace
2024-06-07T16:33:28.753Z DEBUG [PID:31936] cargo = false, force_libnrfdl_lookup = false, force_nrfutil_libdir = false
2024-06-07T16:33:28.753Z DEBUG [PID:31936] Creating the nrfdl context via nrfdl_create_context_with_config: Plugin location is assumed to be C:\Users\jackw\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.1.1\lib\nrfutil-device
2024-06-07T16:33:28.764Z VERBOSE [PID:31936] [devkit] C API function: get_version_list
2024-06-07T16:33:28.764Z DEBUG [PID:31936] [devkit] Operation get_version_list failed with error code NRFDL_ERR_NOT_SUPPORTED
2024-06-07T16:33:28.888Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] open
2024-06-07T16:33:28.888Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] start
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] open
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] just_check_family
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] open_dll
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
2024-06-07T16:33:28.974Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-07T16:33:28.974Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command open executed for 3 milliseconds with result 0
2024-06-07T16:33:28.980Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command open executed for 83 milliseconds with result 0
2024-06-07T16:33:28.980Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] jlink_dll_version
2024-06-07T16:33:28.980Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command jlink_dll_version executed for 0 milliseconds with result 0
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] dll_version
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:28.997Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command jlink_dll_version executed for 0 milliseconds with result 0
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] close
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] close
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
2024-06-07T16:33:28.997Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
2024-06-07T16:33:29.012Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command close executed for 31 milliseconds with result 0
2024-06-07T16:33:29.012Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] terminate
2024-06-07T16:33:29.012Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command terminate executed for 0 milliseconds with result 0
2024-06-07T16:33:29.028Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command close executed for 31 milliseconds with result 0
2024-06-07T16:33:29.028Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
2024-06-07T16:33:29.028Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 34 milliseconds
2024-06-07T16:33:29.061Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-07T16:33:29.061Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-07T16:33:29.061Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
2024-06-07T16:33:29.062Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Executed 4 commands for 114 milliseconds
2024-06-07T16:33:29.062Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] terminate
2024-06-07T16:33:29.080Z WARN [PID:31936] [JlinkARM] JlinkARM version non expected one found: JLink_V7.96i, expected: JLink_V7.94e
2024-06-07T16:33:29.080Z VERBOSE [PID:31936] [boardController] C API function: get_version_list
2024-06-07T16:33:29.080Z DEBUG [PID:31936] [boardController] Operation get_version_list failed with error code NRFDL_ERR_NOT_SUPPORTED
2024-06-07T16:33:29.080Z VERBOSE [PID:31936] DeviceLister::enumerate: Checking future_status of enumerate_task_status
2024-06-07T16:33:29.080Z VERBOSE [PID:31936] DeviceLister::enumerate: Waiting for enumerate task to complete
2024-06-07T16:33:29.080Z VERBOSE [PID:31936] DeviceLister::enumerate::enumerate_task: Start
2024-06-07T16:33:29.080Z VERBOSE [PID:31936] DeviceLister::enumerate::enumerate_task: Before async_lister->enumerate
2024-06-07T16:33:29.080Z DEBUG [PID:31936] USBLister: enumerate
2024-06-07T16:33:29.080Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_10C4&PID_8170#5&3484486e&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.080Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=1
2024-06-07T16:33:29.080Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&1E61E7A&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {1CC6B0CE-1BBC-11EF-B87B-44E517FD729D}
2024-06-07T16:33:29.080Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: serial number: 41Y6KRN17K5M - v2.1b0.0r
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_10C4&PID_8170#5&3484486e&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {1CC6B0CE-1BBC-11EF-B87B-44E517FD729D}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_046D&PID_C537#5&3484486e&0&8#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=8
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&1E61E7A&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 8, origin: {03E2C909-1F82-11EE-B836-806E6F6E6963}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_046D&PID_C537#5&3484486e&0&8#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {03E2C909-1F82-11EE-B836-806E6F6E6963}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_090C&PID_1000#0376520070007864#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=24
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&1E61E7A&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 24, origin: {BF81377D-D724-5C1D-A9E4-1E9D85ECBD40}
2024-06-07T16:33:29.082Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: serial number: 0376520070007864
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_090C&PID_1000#0376520070007864#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {BF81377D-D724-5C1D-A9E4-1E9D85ECBD40}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_046D&PID_085B#2DDB45AF#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=0424, pid=2134, port=2
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0424&PID_2134#6&16F8BFEB&1&4#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 2, origin: {3F4BDB11-F218-5A46-B696-8E61F7F27F7D}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: serial number: 2DDB45AF
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_046D&PID_085B#2DDB45AF#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {3F4BDB11-F218-5A46-B696-8E61F7F27F7D}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_04D8&PID_0B27#7&2c644521&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=0424, pid=2134, port=1
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0424&PID_2134#6&16F8BFEB&1&4#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {63736D73-7835-7878-0000-0073113D0BF4}
2024-06-07T16:33:29.083Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_04D8&PID_0B27#7&2c644521&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {63736D73-7835-7878-0000-0073113D0BF4}
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_0764&PID_0501#5&3484486e&0&9#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=9
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&1E61E7A&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 9, origin: {D7E7CAD9-0614-11EE-B827-806E6F6E6963}
2024-06-07T16:33:29.087Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.090Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_0764&PID_0501#5&3484486e&0&9#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.090Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {D7E7CAD9-0614-11EE-B827-806E6F6E6963}
2024-06-07T16:33:29.090Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.090Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=0424, pid=2134, port=3
2024-06-07T16:33:29.091Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0424&PID_2134#5&3484486E&0&7#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 3, origin: {0EFAE234-B39E-574A-B6BC-DA9882F84662}
2024-06-07T16:33:29.091Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: serial number: THINGY91 12PLACEHLDRS
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {0EFAE234-B39E-574A-B6BC-DA9882F84662}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_046D&PID_C52B#6&16f8bfeb&1&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=0424, pid=2134, port=1
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#VID_0424&PID_2134#5&3484486E&0&7#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 1, origin: {6B0A4C69-16D4-11EF-B87B-44E517FD729D}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_046D&PID_C52B#6&16f8bfeb&1&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {6B0A4C69-16D4-11EF-B87B-44E517FD729D}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Enumerating device \\?\USB#VID_8087&PID_0032#5&3484486e&0&14#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.092Z DEBUG [PID:31936] USBPlatformAPI::Win32: Device connected to hub: vid=, pid=, port=14
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBPlatformAPI::Win32: Hub device path: \\?\USB#ROOT_HUB30#4&1E61E7A&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}, port number: 14, origin: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBPlatformAPI::Win32: Starting DeviceIoControl
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBPlatformAPI::Win32: USB identifier: \\?\USB#VID_8087&PID_0032#5&3484486e&0&14#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBPlatformAPI::Win32: containerID: {00000000-0000-0000-FFFF-FFFFFFFFFFFF}
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 1 and serial number: '41Y6KRN17K5M - v2.1b0.0r '
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 2 and serial number: '{6B0A4C69-16D4-11EF-B87B-44E517FD729D}'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 3 and serial number: '{03E2C909-1F82-11EE-B836-806E6F6E6963}'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 4 and serial number: '{D7E7CAD9-0614-11EE-B827-806E6F6E6963}'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 5 and serial number: '0376520070007864'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 6 and serial number: '2DDB45AF'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 7 and serial number: '{63736D73-7835-7878-0000-0073113D0BF4}'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 8 and serial number: 'THINGY91 12PLACEHLDRS'
2024-06-07T16:33:29.093Z DEBUG [PID:31936] USBLister: Adding new device with id 9 and serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-07T16:33:29.093Z VERBOSE [PID:31936] DeviceLister::enumerate::enumerate_task: After async_lister->enumerate
2024-06-07T16:33:29.093Z VERBOSE [PID:31936] [devkit] C API function: enumerate
2024-06-07T16:33:29.093Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 1
2024-06-07T16:33:29.094Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 2
2024-06-07T16:33:29.094Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 3
2024-06-07T16:33:29.095Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 4
2024-06-07T16:33:29.095Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 5
2024-06-07T16:33:29.096Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 6
2024-06-07T16:33:29.097Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 7
2024-06-07T16:33:29.097Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 8
2024-06-07T16:33:29.098Z VERBOSE [PID:31936] [devkit] enumerate: Inspecting device with ID 9
2024-06-07T16:33:29.098Z DEBUG [PID:31936] Enumeration for plugin 'devkit' took 5 ms
2024-06-07T16:33:29.098Z VERBOSE [PID:31936] [jlink] JLinkPlugin::enumerate
2024-06-07T16:33:29.206Z INFO Using nrfutil-device version: 2.1.1
2024-06-07T16:33:29.206Z INFO Using nrf-device-lib version: 0.17.5
2024-06-07T16:33:29.206Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-07T16:33:29.206Z INFO Using JLink version: JLink_V7.96i
2024-06-07T16:33:29.206Z WARN Installed JLink version does not match the expected version (JLink_V7.94e)
2024-06-07T16:33:29.213Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] open
2024-06-07T16:33:29.213Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] start
2024-06-07T16:33:29.321Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command open executed for 96 milliseconds with result 0
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] enum_emu_snr
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Logger sink registered in Segger backend logger
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][JLink][-] Logger sink registered in JLink logger
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] open
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] just_check_family
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] open_dll
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] No J-Link DLL path was provided. Attempting to auto detect.
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Set batch mode
2024-06-07T16:33:29.321Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] dll_version
2024-06-07T16:33:29.321Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command open executed for 3 milliseconds with result 0
2024-06-07T16:33:29.337Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command enum_emu_snr executed for 15 milliseconds with result 0
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] Found 0 JLink devices connected
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] enum_emu_snr
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] enum_emu_snr
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] ---just_enum_emu_snr
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] ---just_get_num_emus
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:29.337Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command enum_emu_snr executed for 1 milliseconds with result 0
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] close
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] close
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] disconnect_from_emu
2024-06-07T16:33:29.337Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] is_connected_to_emu
2024-06-07T16:33:29.353Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command close executed for 15 milliseconds with result 0
2024-06-07T16:33:29.353Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] terminate
2024-06-07T16:33:29.353Z DEBUG [PID:31936] [jlink] [NRFJPROG][SeggerBackend][-] Segger Backend closed.
2024-06-07T16:33:29.353Z DEBUG [PID:31936] [jlink] [NRFJPROG][nRFXX][-] nRF family DLL closed
2024-06-07T16:33:29.353Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command close executed for 15 milliseconds with result 0
2024-06-07T16:33:29.353Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Command terminate executed for 0 milliseconds with result 0
2024-06-07T16:33:29.368Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Command terminate executed for 0 milliseconds with result 0
2024-06-07T16:33:29.368Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Worker][-] Executed 4 commands for 19 milliseconds
2024-06-07T16:33:29.387Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-07T16:33:29.387Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Worker process exited with code: 0
2024-06-07T16:33:29.387Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] Child process terminated with result 0
2024-06-07T16:33:29.387Z VERBOSE [PID:31936] [jlink] [NRFJPROG][Client][-] Executed 4 commands for 126 milliseconds
2024-06-07T16:33:29.387Z DEBUG [PID:31936] [jlink] [NRFJPROG][Client][-] terminate
2024-06-07T16:33:29.419Z DEBUG [PID:31936] Enumeration for plugin 'jlink' took 320 ms
2024-06-07T16:33:29.419Z VERBOSE [PID:31936] [boardController] C API function: enumerate
2024-06-07T16:33:29.446Z DEBUG [PID:31936] [boardController] Found 18 HID devices.
2024-06-07T16:33:29.446Z DEBUG [PID:31936] Enumeration for plugin 'BOARDCONTROLLER' took 26 ms
2024-06-07T16:33:29.448Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1915&PID_9100&MI_00#7&104720B7&1&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-07T16:33:29.448Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Parent device: USB\VID_1915&PID_9100\THINGY91_12PLACEHLDRS
2024-06-07T16:33:29.449Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-07T16:33:29.449Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] - \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.449Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1915&PID_9100&MI_00#7&104720B7&1&0000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Searching parent device for: \\?\USB#VID_1915&PID_9100&MI_03#7&104720B7&1&0003#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Parent device: USB\VID_1915&PID_9100\THINGY91_12PLACEHLDRS
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] Parent device has 1 interfaces:
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] - \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] serial port \\?\USB#VID_1915&PID_9100&MI_03#7&104720B7&1&0003#{86e0d1e0-8089-11d0-9ce4-08003e301f73} has USB identifier \\?\USB#VID_1915&PID_9100#THINGY91_12PLACEHLDRS#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [SerialPortListerHW::WIN32] try to map FTDI to segger device
2024-06-07T16:33:29.450Z DEBUG [PID:31936] [serialport] serialport enumerate update device: 'THINGY91_12PLACEHLDRS'
2024-06-07T16:33:29.450Z DEBUG [PID:31936] Enumeration for plugin 'serialport' took 3 ms
2024-06-07T16:33:29.451Z DEBUG [PID:31936] Enumeration for plugin 'sdfu' took 0 ms
2024-06-07T16:33:29.451Z DEBUG [PID:31936] Enumeration for plugin 'mcuBoot' took 0 ms
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] [broken] BrokenPlugin::enumerate
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] [broken] The firmware on this Thingy:91 has no known USB CDC bugs.
2024-06-07T16:33:29.451Z DEBUG [PID:31936] Enumeration for plugin 'broken' took 0 ms
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '41Y6KRN17K5M - v2.1b0.0r '
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '{6B0A4C69-16D4-11EF-B87B-44E517FD729D}'
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '{03E2C909-1F82-11EE-B836-806E6F6E6963}'
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '{D7E7CAD9-0614-11EE-B827-806E6F6E6963}'
2024-06-07T16:33:29.451Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '0376520070007864'
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '2DDB45AF'
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '{63736D73-7835-7878-0000-0073113D0BF4}'
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: 'THINGY91 12PLACEHLDRS'
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: device registered to device list
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Found device with serial number: '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Finished in 371 ms
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: Completed waiting for enumerate task
2024-06-07T16:33:29.452Z VERBOSE [PID:31936] DeviceLister::enumerate: done
2024-06-07T16:33:29.453Z INFO Getting serialport options from persistent store THINGY91 12PLACEHLDRS.pc-nrfconnect-cellularmonitor
2024-06-07T16:33:29.454Z DEBUG Sending event "cellularmonitor: device connected"
Yeah then I think the JLink version is the issue.
JackW said:2024-05-28T15:40:53.149Z WARN Installed JLink version does not match the expected version (JLink_V7.94e)
Could you uninstall the version you have, install the expected one, restarting your system, and try again?
Regards,
Elfving
Yeah then I think the JLink version is the issue.
JackW said:2024-05-28T15:40:53.149Z WARN Installed JLink version does not match the expected version (JLink_V7.94e)
Could you uninstall the version you have, install the expected one, restarting your system, and try again?
Regards,
Elfving
Hi Elfving,
OK, I have installed JLink_V7.94e, and now the 'Open Serial Terminal' widget works (it didn't before), but I'm stll not able to populate the dashboard. Also, when I open the terminal and try to send AT commands to the device, nothing works.
Here's log file:
2024-06-11T16:04:43.474Z INFO Initialising nrfutil module: device
2024-06-11T16:04:43.510Z DEBUG Application data folder: C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-cellularmonitor
2024-06-11T16:04:43.529Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-11T16:04:43.532Z DEBUG App pc-nrfconnect-cellularmonitor v2.4.0 (official)
2024-06-11T16:04:43.532Z DEBUG App path: C:\Users\jackw\.nrfconnect-apps\node_modules\pc-nrfconnect-cellularmonitor
2024-06-11T16:04:43.532Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-11T16:04:43.532Z DEBUG nRFConnect path: C:\Users\jackw\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-11T16:04:43.532Z DEBUG HomeDir: C:\Users\jackw
2024-06-11T16:04:43.532Z DEBUG TmpDir: C:\Users\jackw\AppData\Local\Temp
2024-06-11T16:04:44.657Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-11T16:04:49.748Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-11T16:04:49.748Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-11T16:04:49.754Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-11T16:04:49.894Z INFO Using nrfutil-device core version: 7.11.1
2024-06-11T16:04:50.596Z INFO Using nrfutil-device version: 2.1.1
2024-06-11T16:04:50.596Z INFO Using nrf-device-lib version: 0.17.5
2024-06-11T16:04:50.596Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-11T16:04:50.596Z INFO Using JLink version: JLink_V7.94e
2024-06-11T16:04:50.876Z INFO Getting serialport options from persistent store THINGY91 12PLACEHLDRS.pc-nrfconnect-cellularmonitor
2024-06-11T16:04:50.876Z DEBUG Sending event "cellularmonitor: device connected"
2024-06-11T16:04:52.347Z INFO Selected device with s/n THINGY91 12PLACEHLDRS
2024-06-11T16:04:52.349Z DEBUG Terminal Serial Port: Will attempt to auto-connect to serial port COM6
2024-06-11T16:04:52.352Z DEBUG Sending event "cellularmonitor: device selected"
2024-06-11T16:04:52.357Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-11T16:04:53.193Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4_trace-db.json
2024-06-11T16:04:53.193Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.193Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5_trace-db.json
2024-06-11T16:04:53.193Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.194Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3_trace-db.json
2024-06-11T16:04:53.195Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.6_trace-db.json
2024-06-11T16:04:53.196Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.6-FOTA-TEST_trace-db.json
2024-06-11T16:04:53.369Z DEBUG Terminal Serial Port: Could not detect AT Host library
2024-06-11T16:05:22.657Z INFO Started tracefile
2024-06-11T16:05:22.658Z INFO Refreshing dashboard in 5 seconds
2024-06-11T16:05:22.673Z DEBUG Sending event "cellularmonitor: Starting Raw trace"
2024-06-11T16:06:35.370Z DEBUG Sending event "cellularmonitor: Stopping trace"
2024-06-11T16:06:35.372Z INFO Finished tracefile
Here's a link to a screen shot: Cellular Monitor Screen Image.jpg
Here's the log file from the terminal after I attempted to send an AT command to the device:
2024-06-11T16:07:57.035Z INFO Initialising nrfutil module: device
2024-06-11T16:07:57.058Z DEBUG Application data folder: C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-serial-terminal
2024-06-11T16:07:57.084Z DEBUG Sending event "serial-terminal: running nrfutil device"
2024-06-11T16:07:57.084Z DEBUG App pc-nrfconnect-serial-terminal v1.4.0 (official)
2024-06-11T16:07:57.084Z DEBUG App path: C:\Users\jackw\.nrfconnect-apps\node_modules\pc-nrfconnect-serial-terminal
2024-06-11T16:07:57.084Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-11T16:07:57.084Z DEBUG nRFConnect path: C:\Users\jackw\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-11T16:07:57.084Z DEBUG HomeDir: C:\Users\jackw
2024-06-11T16:07:57.084Z DEBUG TmpDir: C:\Users\jackw\AppData\Local\Temp
2024-06-11T16:07:57.782Z DEBUG Sending event "serial-terminal: running nrfutil device"
2024-06-11T16:08:02.566Z DEBUG Sending event "serial-terminal: running nrfutil device"
2024-06-11T16:08:02.566Z DEBUG Sending event "serial-terminal: running nrfutil device"
2024-06-11T16:08:02.575Z DEBUG Sending event "serial-terminal: running nrfutil device"
2024-06-11T16:08:02.706Z INFO Using nrfutil-device core version: 7.11.1
2024-06-11T16:08:03.412Z INFO Using nrfutil-device version: 2.1.1
2024-06-11T16:08:03.412Z INFO Using nrf-device-lib version: 0.17.5
2024-06-11T16:08:03.412Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-11T16:08:03.412Z INFO Using JLink version: JLink_V7.94e
2024-06-11T16:08:03.742Z INFO Device Connected SN:THINGY91 12PLACEHLDRS
2024-06-11T16:08:03.743Z INFO Getting serialport options from persistent store THINGY91 12PLACEHLDRS.pc-nrfconnect-serial-terminal
2024-06-11T16:08:03.746Z DEBUG Sending event "serial-terminal: device connected"
2024-06-11T16:08:03.746Z INFO Selected device with s/n THINGY91 12PLACEHLDRS
2024-06-11T16:08:03.748Z DEBUG Sending event "serial-terminal: device selected"
2024-06-11T16:08:03.758Z INFO Opened port with options: {"path":"COM6","baudRate":115200}
2024-06-11T16:08:03.763Z INFO Get terminal settings from persistent store THINGY91 12PLACEHLDRS.vCom-0.TerminalSettings
2024-06-11T16:11:12.303Z DEBUG The app will need to read the content of C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-serial-terminal\.history, becuase it may not be in-sync with the (in-memory) history buffer.
2024-06-11T16:13:45.962Z DEBUG The app will need to read the content of C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-serial-terminal\.history, becuase it may not be in-sync with the (in-memory) history buffer.
2024-06-11T18:06:33.433Z DEBUG The app will need to read the content of C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-serial-terminal\.history, becuase it may not be in-sync with the (in-memory) history buffer.
Here's a link to a screen shot showing the terminal: Terminal screen shot.jpg
Note that when attempting to send the AT command, nothing happens.
Hi Elfving,
I disconnected the Cellular Monitor from our prototype device and hooked it up to my nRF9160 Dev Kit instead to see if the problem was with our prototype.
I discovered that the Cellular Monitor isn't working with the Dev Kit either.
So something is defiinitely wrong with the nRF Connect for Desktop Cellular Monitor app.
This is a huge problem for me and I really need to get this fixed. I need to be able to use the terminal to send AT Commands to our device for testing purposes. I was able to do that in the old nRF Connect for Desktop app, but I can't make it work in the new Cellular Monitor app.
Please help me fix this.
Elfving,
Please, I need answers. This is taking way too long. It's been 2 1/2 weeks since I opened this ticket and we still haven't solved the problem. Please reply.
Hi Jack,
I am here to help since my college has other tasks to handle. Let's verify if your Cellular Monitor 2.4.0 has issue or not first.
Open Cellular Monitor->ADVANCED OPTIONS->Program device to program your nRF9160 Dev Kit(Is it nRF9160DK or Thingy91?) with Serial LTE Modem firmware.
Now you can test with Cellular Monitor, make sure "Refresh Dashboard on start" is enabled and "Modem Trace database" is set to the MFW version you are using, when "Open Serial Terminal" and wait for device connected, you would be able to see AT commands log in Serial Terminal and Dashboard updated.
Just let me know if you still have problems with Cellular Monitor 2.4.0.
Best regards,
Charlie
Hi Charlie,
Thank you very much for taking over this case.
OK, to start with I opened up the Program Device option and selected the Serial LTE Modem. I then programmed my nRF9160 Dev Kit with the mFW_nrf9160_1.3.5 and with the slm-with-trace.hex application.
2024-06-14T15:41:09.343Z INFO Initialising nrfutil module: device
2024-06-14T15:41:09.396Z DEBUG Application data folder: C:\Users\jackw\AppData\Roaming\nrfconnect\pc-nrfconnect-cellularmonitor
2024-06-14T15:41:09.430Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:09.437Z DEBUG App pc-nrfconnect-cellularmonitor v2.4.0 (official)
2024-06-14T15:41:09.437Z DEBUG App path: C:\Users\jackw\.nrfconnect-apps\node_modules\pc-nrfconnect-cellularmonitor
2024-06-14T15:41:09.437Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-06-14T15:41:09.437Z DEBUG nRFConnect path: C:\Users\jackw\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-06-14T15:41:09.437Z DEBUG HomeDir: C:\Users\jackw
2024-06-14T15:41:09.437Z DEBUG TmpDir: C:\Users\jackw\AppData\Local\Temp
2024-06-14T15:41:10.704Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:17.606Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:17.607Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:17.615Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:17.754Z INFO Using nrfutil-device core version: 7.12.0
2024-06-14T15:41:18.415Z INFO Using nrfutil-device version: 2.1.1
2024-06-14T15:41:18.415Z INFO Using nrf-device-lib version: 0.17.5
2024-06-14T15:41:18.415Z INFO Using nrfjprog DLL version: 10.24.0
2024-06-14T15:41:18.415Z INFO Using JLink version: JLink_V7.94e
2024-06-14T15:41:18.671Z INFO Getting serialport options from persistent store 000960000943.pc-nrfconnect-cellularmonitor
2024-06-14T15:41:18.672Z DEBUG Sending event "cellularmonitor: device connected"
2024-06-14T15:41:46.919Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:41:47.788Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4_trace-db.json
2024-06-14T15:41:47.789Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.789Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5_trace-db.json
2024-06-14T15:41:47.789Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.789Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.790Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4_trace-db.json
2024-06-14T15:41:47.791Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.792Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5_trace-db.json
2024-06-14T15:41:47.792Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5-FOTA-TEST_trace-db.json
2024-06-14T15:41:47.792Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.6_trace-db.json
2024-06-14T15:41:47.792Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.6-FOTA-TEST_trace-db.json
2024-06-14T15:41:48.711Z INFO Selected device with s/n 000960000943
2024-06-14T15:41:48.717Z DEBUG Terminal Serial Port: Will attempt to auto-connect to serial port COM3
2024-06-14T15:41:48.717Z DEBUG Sending event "cellularmonitor: device selected"
2024-06-14T15:41:48.722Z INFO Opened port with options: {"path":"COM3","baudRate":115200}
2024-06-14T15:41:49.726Z DEBUG Terminal Serial Port: Could not detect AT Host library
2024-06-14T15:42:50.653Z INFO Sample not found locally, downloading https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/samples/mfw_nrf9160_1.3.5.zip
2024-06-14T15:42:50.653Z INFO Sample not found locally, downloading https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/samples/slm-with-trace.hex
2024-06-14T15:42:50.654Z INFO Sample is bundled with app, copying.
2024-06-14T15:42:50.655Z DEBUG Sending event "cellularmonitor: Program sample application"
2024-06-14T15:42:50.663Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:42:50.668Z INFO Closed port: COM3
2024-06-14T15:42:52.166Z ERROR Error: Failed with exit code 1.
One or more program tasks failed.
Message: Failed, [jlink] INVALID_PARAMETER.
2024-06-14T15:42:52.166Z ERROR Failed with exit code 1.
One or more program tasks failed.
Message: Failed, [jlink] INVALID_PARAMETER.
2024-06-14T15:42:52.166Z ERROR Failed to program a sample
2024-06-14T15:42:52.166Z ERROR Failed with exit code 1.
One or more program tasks failed.
Message: Failed, [jlink] INVALID_PARAMETER.
2024-06-14T15:58:11.070Z DEBUG Sending event "cellularmonitor: Program sample application"
2024-06-14T15:58:11.077Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:58:12.279Z INFO 1/3: 100% - {"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"}
2024-06-14T15:58:12.279Z INFO 2/3: 0% - Uploading image through JLink.
2024-06-14T15:58:57.415Z INFO 3/3: 100% - Uploading image through JLink.
2024-06-14T15:58:58.012Z DEBUG Sending event "cellularmonitor: Program sample application"
2024-06-14T15:58:58.026Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:58:59.493Z INFO 1/3: 100% - {"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"}
2024-06-14T15:58:59.493Z INFO 2/3: 0% - Uploading image through JLink.
2024-06-14T15:59:01.844Z INFO 3/3: 100% - Uploading image through JLink.
2024-06-14T15:59:02.125Z INFO Programming complete, reseting device.
2024-06-14T15:59:02.144Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:59:05.144Z DEBUG Terminal Serial Port: Will attempt to auto-connect to serial port COM3
2024-06-14T15:59:05.150Z INFO Opened port with options: {"path":"COM3","baudRate":115200}
2024-06-14T15:59:05.156Z INFO Device is in line mode.
2024-06-14T15:59:05.156Z INFO Device is in line mode.
2024-06-14T15:59:05.156Z DEBUG Terminal Serial Port: Detected AT Host Library: Device is in Line mode
2024-06-14T15:59:31.558Z INFO Started tracefile
2024-06-14T15:59:31.558Z INFO Reseting device
2024-06-14T15:59:31.575Z DEBUG Sending event "cellularmonitor: Starting Raw trace"
2024-06-14T15:59:31.582Z DEBUG Sending event "cellularmonitor: running nrfutil device"
2024-06-14T15:59:33.260Z INFO Refreshing dashboard in 5 seconds
2024-06-14T15:59:38.456Z ERROR AT command AT+CPIN? failed:
+CME ERROR:
2024-06-14T15:59:38.462Z ERROR AT command AT+CIMI failed: 13
+CME ERROR
2024-06-14T15:59:38.873Z ERROR AT command AT%XICCID failed:
+CME ERROR: 0
2024-06-14T15:59:38.924Z ERROR AT command AT+CPINR="SIM PIN" failed:
+CME ERROR
2024-06-14T15:59:38.936Z ERROR AT command AT+CPINR="SIM PIN2" failed: : 0
+CME ERROR: 0
2024-06-14T15:59:38.945Z ERROR AT command AT+CPINR="SIM PUK" failed:
+CME ERROR: 0
2024-06-14T15:59:38.955Z ERROR AT command AT+CPINR="SIM PUK2" failed:
+CME ERROR:
2024-06-14T16:00:01.564Z DEBUG Sending event "cellularmonitor: Stopping trace"
2024-06-14T16:00:01.566Z INFO Finished tracefile
2024-06-14T16:10:55.868Z DEBUG Sending event "cellularmonitor: Open file directory"
I get a series of AT command failed messages. See the attached log file.