NRF_ERROR_TIMEOUT when executing advertising example given in pc-ble-driver-py

[djedjiga salmi]

hello,

I'm working with nRF52840 dongle, i installed nRF Connect for desktop v3.6.1 on ubunto 18.4 and i am using python3. After programming  connectivity_4.1.4_usb_with_s132_5.1.0.hex and installling pc-ble-driver version 0.15.0, i tried to execute the example (Advertising)  given in pc-ble-driver i got this error when i type the comand

python3 ./advertising.py NRF52 /dev/ttyACM0

Serial port used: /dev/ttyACM0
Traceback (most recent call last):
  File "./advertising.py", line 107, in <module>
    main(sys.argv[2])
  File "./advertising.py", line 65, in main
    driver.open()
  File "/home/my_pc/.local/lib/python3.6/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 open. Error code: NRF_ERROR_TIMEOUT

i have obtained the same error with sudo python3 ./advertising.py NRF52 /dev/ttyACM0

Has anyone else had an issue like this ?

[Sigurd]

Hi,

Are you sure that ttyACM0 is correct ? Maybe it's ttyACM1,ttyACM2 or similar ?

Have you granted serial port access permissions to your user? To do this, run the following command:

sudo usermod -a -G dialout <username>

[djedjiga salmi]

Thank you, yes i'm sure it is ttyACM0, i have  also the serial port access permissions to my user ut i have always the same error. should i install the nRF connect SDK also?

[Sigurd]

I'm not able to reproduce this.

Did you install pc_ble_driver_py using pip? Can you double check the version that you are using?

pip show pc_ble_driver_py

[djedjiga salmi]

yes, it is 0.15.0 version

[Sigurd]

Check what this command returns:

ls -l /dev/serial/by-id

then use the com-port listed with this command, e.g. for ttyACM1:

sudo chmod a+rw /dev/ttyACM1

and then try again with the pc-ble-driver-py advertising.py script

[djedjiga salmi]

Thank you,

it return this :

total 0
lrwxrwxrwx 1 root root 13 mai    7 09:43 usb-Nordic_Semiconductor_Open_DFU_Bootloader_D6F9B927D70E-if00 -> ../../ttyACM0

i executed it by using this command : sudo python3 ./advertising.py NRF52 /dev/ttyACM0
but it is the same thing, i don't understand the reason.

Serial port used: /dev/ttyACM0
Traceback (most recent call last):
  File "./advertising.py", line 107, in <module>
    main(sys.argv[2])
  File "./advertising.py", line 65, in main
    driver.open()
  File "/home/My-pc/.local/lib/python3.6/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 open. Error code: NRF_ERROR_TIMEOUT

[Sigurd]

djedjiga salmi said:

Nordic_Semiconductor_Open_DFU_Bootloader_D6F9B927D70E

This means that you are in bootloader mode, and the connectivity firmware is not running.

Is the LED on the dongle blinking red ?

Could you try to program the connectivity_4.1.4_usb_with_s132_5.1.0.hex again, with nRF Connect programmer app?

[djedjiga salmi]

yes, the led is blinking red. when i programmed the  connectivity_4.1.4_usb_with_s132_5.1.0.hex i got this:

12:53:50.161

Application data folder: /home/My-pc/.config/nrfconnect/pc-nrfconnect-programmer

12:53:50.202

Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

12:53:52.408

Using USB SDFU protocol to communicate with target

12:53:52.415

Protocol Version: 1 found

12:53:52.416

Hardware: 52840 found

12:53:52.424

Firmware: Bootloader found

12:53:52.424

Firmware: SoftDevice found

12:53:52.424

Firmware: Application found

12:54:05.224

Parsing HEX file: /home/My-pc/Downloads/connectivity_1.0.0_usb_with_s132_5.1.0.hex

12:54:05.259

File was last modified at 1/18/2019, 10:39:36 AM

12:54:05.349

SoftDevice detected, id 0xA5 (S132 v5.1.0)

12:54:07.659

Does not need to be reloaded: /home/My-pc/Downloads/connectivity_1.0.0_usb_with_s132_5.1.0.hex

12:54:07.663

SdReq for SoftDevice is set as 0x00.

12:54:07.664

Hash is generated by SHA256

12:54:07.665

Hash is generated by SHA256

12:54:07.671

Performing DFU. This may take a few seconds

12:54:07.684

DFU procedure starts. This may take a few seconds.

12:54:14.951

DFU for SoftDevice completed successfully!

12:54:14.952

1 dfu package(s) left.

12:54:14.952

Waiting for device

12:54:15.069

DFU procedure starts. This may take a few seconds.

12:54:24.750

DFU for Application completed successfully!

12:54:24.750

0 dfu package(s) left.

12:54:24.750

Waiting for device

12:54:25.855

All dfu images have been written to the target device.

12:54:25.856

DFU trigger interface found, changing to bootloader...

12:54:26.801

Using USB SDFU protocol to communicate with target

12:54:26.804

Protocol Version: 1 found

12:54:26.804

Hardware: 52840 found

12:54:26.806

Firmware: Bootloader found

12:54:26.806

Firmware: SoftDevice found

12:54:26.807

Firmware: Application found

12:54:26.812

SoftDevice detected, id 0xA5 (S132 v5.1.0)

it was the same thing that i had before

[Sigurd]

1) Why does it say "connectivity_1.0.0_usb_with_s132_5.1.0" in your log? It should be "connectivity_4.1.4_usb_with_s132_5.1.0.hex" ?

2) After programming the dongle, if you plug it out from the computer, and then plug it back in, does the LED still blink red?

[djedjiga salmi]

1) i have tried different connectivity. Now i'm working with "connectivity_4.1.4_usb_with_s132_5.1.0.hex" and it works also

2) No, it is not blinking when i plug it out from the computer, and then plug it back in.