I was using nRF Connect (v3.6.1) to communicate to Segger J-link Base (version 11.0) but it failed. The error message was: ""Failed to setup device: No serial port available for device with serial number xxxxxxxx"". Anyone has an idea how to fix this issue? Thanks!
Hi
What nRFConnect app are you trying to connect the J-Link device to? The Bluetooth Low Energy app for instance, is only compatible with Nordic Semiconductor DKs for example. How is the nRF you're using connected to the J-Link Base?
Are you able to detect the SEGGER J-Link Base in your device manager at all?
Best regards,
Simon
Thanks for quick response! I was using Bluetooth Low Energy App and nRF52 chip was connected to J-Link. The app detected the J-Link Base but when I clicked it the error message showed up.
Hi
nRFConnect communicates with nRF devices over the Virtual COM port in J-Link. Does your J-Link devices support this functionality? If not, I'm afraid you won't be able to use it with nRFConnect for Desktop.
Additionally, the nRFConnect Bluetooth Low Energy app has stored a specific range of SEGGER IDs that are reserved for Nordics Development Kit debugger chips, so it will know if it is a supported device that is connected. Only our Development Kits and Dongles can be used with this particular app. If your J-Link device support acting as a Virtual COM link, you should be able to use nRFConnect apps like the Programmer though.
Best regards,
Simon
The SEGGER J-Link Base I used does have virtual COM, but it was disabled by default. Today I was able to enable it using J-Link Config tool. It still failed but had different error messages. Here is the log file for your reference:
23T01:16:14.690Z INFO Device setup completed
2021-03-23T01:16:14.691Z INFO The device is not in the list of supported devices. Attempting to open as a custom device.
2021-03-23T01:16:14.691Z INFO Opening custom device
2021-03-23T01:16:14.691Z INFO Note: firmware must be compatible with connectivity firmware version: 4.1.2, SoftDevice API version: 5 and baud rate: 1000000.
2021-03-23T01:16:14.697Z INFO Opening adapter connected to COM8
2021-03-23T01:16:15.668Z INFO Reset performed on adapter COM8
2021-03-23T01:16:15.677Z INFO Successfully opened COM8. Baud rate: 1000000. Flow control: none. Parity: none.
2021-03-23T01:16:15.677Z DEBUG State change: STATE_START -> STATE_RESET
2021-03-23T01:16:15.677Z DEBUG 1 -> [N/A] type: RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2021-03-23T01:16:15.982Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2021-03-23T01:16:15.983Z DEBUG 2 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:16.231Z DEBUG 3 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:16.490Z DEBUG 4 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:16.738Z DEBUG 5 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:16.989Z DEBUG 6 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:17.236Z DEBUG 7 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-03-23T01:16:17.486Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2021-03-23T01:16:17.486Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2021-03-23T01:16:18.382Z ERROR serial port write operation on port COM8 failed. Error: A device attached to the system is not functioning.[31]
2021-03-23T01:16:18.382Z DEBUG serial port read on port COM8 aborted.
2021-03-23T01:16:18.725Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)
Hi
As I mentioned in my last reply, the BLE app in nRFConnect for Desktop is restricted to use with Nordic DKs, so you won't be able to use it successfully with a J-Link Base (we can see this from the line "2021-03-23T01:16:14.691Z INFO The device is not in the list of supported devices. Attempting to open as a custom device.." in the log).
You should however be able to make use of I.E. the Programmer app in nRFConnect for Desktop, as this doesn't have that restriction.
Best regards,
Simon
