• State Not Answered
  • Replies 6 replies
  • Subscribers 73 subscribers
  • Views 1169 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249165
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

The NRF 52840 dongle rate in the center of the running exmaple example will be the 2020-05-07 16:40:31, 995/123145341956096 / StatusThread RpcAppStatus ioResourcesUnavailable: serial port read failed on port/dev/tty. UsbmodemC8A5C57A42372. Error: Device no

SYJ

When I was running the heart rate example, I would report this error below, someone tell me what caused this error, which causes the driver to fail to recognize now. But I found the device on the NRF connect desktop and on the command line.

python3 heart_rate_collector.py NRF52 /dev/tty.usbmodemC8A5C57A42372 ['heart_rate_collector.py', 'NRF52', '/dev/tty.usbmodemC8A5C57A42372'] Serial port used: /dev/tty.usbmodemC8A5C57A42372 2020-05-07 16:40:30,680 [123145336700928/LogThread] Successfully opened /dev/tty.usbmodemC8A5C57A42372. Baud rate: 1000000. Flow control: none. Parity: none. 2020-05-07 16:40:30,680 [123145336700928/LogThread] evt> severity(20) message(Successfully opened /dev/tty.usbmodemC8A5C57A42372. Baud rate: 1000000. Flow control: none. Parity: none.) 2020-05-07 16:40:30,681 [123145341956096/StatusThread] RpcAppStatus.resetPerformed: Target Reset performed 2020-05-07 16:40:30,681 [123145341956096/StatusThread] evt> status code(RpcAppStatus.resetPerformed) message(Target Reset performed) 2020-05-07 16:40:31,889 [123145341956096/StatusThread] RpcAppStatus.connectionActive: Connection active 2020-05-07 16:40:31,890 [123145341956096/StatusThread] evt> status code(RpcAppStatus.connectionActive) message(Connection active) 2020-05-07 16:40:31,995 [123145341956096/StatusThread] RpcAppStatus.ioResourcesUnavailable: serial port read failed on port /dev/tty.usbmodemC8A5C57A42372. Error: Device not configured [6] 2020-05-07 16:40:31,995 [123145341956096/StatusThread] evt> status code(RpcAppStatus.ioResourcesUnavailable) message(serial port read failed on port /dev/tty.usbmodemC8A5C57A42372. Error: Device not configured [6]) 2020-05-07 16:40:33,391 [123145336700928/LogThread] Failed to receive response for command Traceback (most recent call last): File "heart_rate_collector.py", line 222, in 2020-05-07 16:40:33,392 [123145336700928/LogThread] evt> severity(30) message(Failed to receive response for command) 2020-05-07 16:40:33,393 [123145341956096/StatusThread] RpcAppStatus.pktSendError: Error sending packet to target. Code: 0x8016 2020-05-07 16:40:33,393 [123145341956096/StatusThread] evt> status code(RpcAppStatus.pktSendError) message(Error sending packet to target. Code: 0x8016) main(serial_port) File "heart_rate_collector.py", line 178, in main collector.open() File "heart_rate_collector.py", line 103, in open self.adapter.driver.ble_cfg_set(BLEConfig.conn_gatt, gatt_cfg) File "/usr/local/lib/python3.7/site-packages/pc_ble_driver_py/ble_driver.py", line 107, in wrapper error_code=err_code, pc_ble_driver_py.exceptions.NordicSemiException: Failed to ble_cfg_set. Error code: NRF_ERROR_SD_RPC_SEND

  • 0 in reply to SYJ

    Hello,

    I am terribly sorry for my late reply. 
    I have checked, and the pc-ble-driver-py does support the nRF52840 dongle - but the programming of the dongle is a little different since the dongle does not have an onboard debugger.
    Have you see the "Installing drivers and tools" section of the pc-ble-driver-py? You must use serial DFU to program the dongle, since it has no debugger.
    - Is the dongle programmed according to this documentation? If so, did you experience any issues while programming it? It sounds like something might have gone wrong here.

    You might also be interested in seeing the Data corruption or drops section of the known issued.md.

    My sincerest apology for my late reply.
    Looking forward to resolving this issue together!

    Best regards,
    Karl

Related
Terms of service