• State Not Answered
  • Replies 9 replies
  • Subscribers 74 subscribers
  • Views 2839 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 242084
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrfConnect 3.3.0 NRF_ERROR_TIMEOUT (0xd), Linux (Ubuntu 18.04)

OS Na

Hi,


I'm trying to get NRF Connect 3.3.0 connected to a nRF52 DK with a PCA10040 and get the following when I try to connect to the device:
Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
Error occurred when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

I'm using Ubuntu 18.04 with JLink Version 6.52c. Attached is the log file.

I already tried disabling the MSD as suggested here www.nordicsemi.com/nRFConnectOSXfix and erased the memory as mentioned in other forum entries concerning this error message.

Thanks for helping. If you need more information, let me know.

Fullscreen 2020-01-06T11_26_53.679Z-log.txt Download 
2020-01-06T11:26:53.965Z INFO Application data folder: /.../.config/nrfconnect/pc-nrfconnect-ble
2020-01-06T11:26:54.046Z DEBUG App pc-nrfconnect-ble v2.3.2 official
2020-01-06T11:26:54.047Z DEBUG App path: /home/.../.nrfconnect-apps/node_modules/pc-nrfconnect-ble
2020-01-06T11:26:54.047Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2020-01-06T11:26:54.047Z DEBUG nRFConnect path: /.../nrfconnect-3.3.0-x64/resources/app.asar
2020-01-06T11:26:54.047Z DEBUG HomeDir: /home/...
2020-01-06T11:26:54.047Z DEBUG TmpDir: /tmp
2020-01-06T11:26:54.120Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2020-01-06T11:26:54.120Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2020-01-06T11:26:54.120Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2020-01-06T11:26:54.120Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2020-01-06T11:26:54.120Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2020-01-06T11:26:54.121Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2020-01-06T11:26:54.122Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2020-01-06T11:26:56.044Z INFO Validating connectivity firmware for device with serial number xxx...
2020-01-06T11:26:57.079Z INFO Connectivity firmware is valid.
2020-01-06T11:26:57.080Z INFO Note: Adapters with Segger JLink debug probe requires MSD to be disabled to function properly on MacOS and Linux. Please visit www.nordicsemi.com/nRFConnectOSXfix for further instructions.
2020-01-06T11:26:57.080Z INFO Getting information from J-Link debugger...
2020-01-06T11:26:58.173Z INFO Found device type: nRF52832. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15.
2020-01-06T11:26:58.173Z INFO Connectivity firmware version: 4.1.1. SoftDevice API version: 3. Baud rate: 1000000.
2020-01-06T11:26:58.175Z INFO Opening adapter connected to /dev/ttyACM0
2020-01-06T11:26:59.103Z INFO Successfully opened /dev/ttyACM0. Baud rate: 1000000. Flow control: none. Parity: none.
2020-01-06T11:26:59.104Z DEBUG State change: STATE_START -> STATE_RESET
2020-01-06T11:26:59.104Z DEBUG        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2020-01-06T11:26:59.105Z INFO Reset performed on adapter /dev/ttyACM0
2020-01-06T11:26:59.403Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2020-01-06T11:26:59.404Z DEBUG        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:26:59.654Z DEBUG        3 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:26:59.904Z DEBUG        4 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:27:00.154Z DEBUG        5 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:27:00.404Z DEBUG        6 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:27:00.654Z DEBUG        7 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-01-06T11:27:00.905Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2020-01-06T11:27:00.905Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2020-01-06T11:27:02.103Z DEBUG serial port read on port /dev/ttyACM0 aborted.
2020-01-06T11:27:02.133Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

  • 0

    Everything looks good, just seems there is no answer from the connectivity firmware.

    Have you tried running 'nrfjprog -e' from command line, and let the app program the connectivity firmware over again?

    Kenneth

  • 0 in reply to Kenneth

    Yes I tried that (sorry for not stating it explicitly and no it did not help)

  • 0 in reply to OS Na

    Are you able to confirm that the DK with the connectivity firmware do work in Windows?

    Kenneth

  • 0 in reply to Kenneth

    I don't have a Windows machine available.

    I just did, however, try it on an old Archlinux with nrfConnect 2.6.0 if that helps. It produced a similar log (see attached file), though it did not produce an error but simply crashed instead.

    Are you suggesting the DK is broken?

    Fullscreen 2020-01-08T12_30_41.560Z-log.txt Download 
    2020-01-08T12:30:42.844Z INFO Application data folder: /home/.../.config/nrfconnect/pc-nrfconnect-ble
2020-01-08T12:30:43.001Z DEBUG App pc-nrfconnect-ble v2.2.0 official
2020-01-08T12:30:43.001Z DEBUG App path: /home/.../.nrfconnect-apps/node_modules/pc-nrfconnect-ble
2020-01-08T12:30:43.001Z DEBUG nRFConnect 2.6.0 is supported by the app (^2.4.0)
2020-01-08T12:30:43.001Z DEBUG nRFConnect path: /tmp/.mount_nrfcon2dOgTJ/app/resources/app.asar
2020-01-08T12:30:43.001Z DEBUG HomeDir: /home/...
2020-01-08T12:30:43.001Z DEBUG TmpDir: /tmp
2020-01-08T12:30:43.203Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2020-01-08T12:30:43.203Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2020-01-08T12:30:43.203Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2020-01-08T12:30:43.203Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2020-01-08T12:30:49.384Z INFO Validating connectivity firmware for device with serial number xxx...
2020-01-08T12:30:51.825Z INFO Connectivity firmware is valid.
2020-01-08T12:30:51.826Z INFO Note: Adapters with Segger JLink debug probe requires MSD to be disabled to function properly on MacOS and Linux. Please visit www.nordicsemi.com/nRFConnectOSXfix for further instructions.
2020-01-08T12:30:51.826Z INFO Getting information from J-Link debugger...
2020-01-08T12:30:54.306Z INFO Found device type: nRF52832. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15.
2020-01-08T12:30:54.307Z INFO Connectivity firmware version: 1.2.3. SoftDevice API version: 3. Baud rate: 1000000.
2020-01-08T12:30:54.309Z INFO Opening adapter connected to /dev/ttyACM0
2020-01-08T12:30:54.849Z INFO Successfully opened /dev/ttyACM0. Baud rate: 1000000. Flow control: none. Parity: none.

2020-01-08T12:30:54.849Z DEBUG State change: STATE_START -> STATE_RESET

2020-01-08T12:30:54.850Z DEBUG        1 ->  []
               type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0
2020-01-08T12:30:54.851Z INFO Reset performed on adapter /dev/ttyACM0
2020-01-08T12:30:55.150Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED

2020-01-08T12:30:55.150Z DEBUG        2 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:55.400Z DEBUG        3 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:55.650Z DEBUG        4 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:55.900Z DEBUG        5 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:56.151Z DEBUG        6 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:56.401Z DEBUG        7 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2020-01-08T12:30:56.651Z DEBUG State change: STATE_UNINITIALIZED -> STATE_FAILED

  • 0 in reply to OS Na

    Do you have similar problems if using RSSI Viewer nRF Connect?

    It would help to verify hardware if you had access to a Windows PC.

    Best regards,
    Kenneth

Related
Terms of service