nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Unable to run heart_rate_collector.js example script on pc-ble-driver-js for armv7 architecture

Hello,

I am using armv7 architecture and trying to run the pc-ble-driver-js/examples/heart_rate_collector.js script using nrf52840 as central and another nRF52840 evaluation kit as peripheral with heart_rate_monitor.js example. We are facing an issue of the script getting stuck on the adapter open.

Cross-compiling pc-ble-driver-js v2.7.2 on raspberry pi 2 has the same architecture and setup works fine but doing so on a custom board, the script is stuck at:

bash-5.0# node heart_rate_collector.js /dev/ttyACM0 v5
Opening adapter with ID: and baud rate: 1000000...

There is no error message nor any more debugs printed.

I am trying to understand why my com port is not opening and scanning has not started.

Thank you

Sakib K

Parents

0 user14926 over 4 years ago

Hi,

Is the serial port path (/dev/ttyACM0) correct for the custom board?

Can you try to increase the logLevel to 'debug', to see if this provides more details about where the problem occurs?

Best regards,
Jørgen
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user14926 over 4 years ago in reply to user14926

Which OS are you running on? Maybe there is some syslogs that can explain what is happening?

Sounds like this could be a problem with the OS/system and not with the pc-ble-driver-js application.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user89683 over 4 years ago in reply to user14926

I am running this on docker node-red version 1.1.0. If this causes an issue what would be a possible solution to overcome this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user14926 over 4 years ago in reply to user14926

Hard to say anything about possible solutions, without knowing the root cause.

If you can check the system logs, to see if those gives any suggestions to what is happening, that would be useful.

Do you have access to the UART pins on the nRF52840 where you run the connectivity firmware? If you do, can you check the lines with a logic analyzer to see if any data is sent from the PC to the board?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 user14926 over 4 years ago in reply to user14926

Hard to say anything about possible solutions, without knowing the root cause.

If you can check the system logs, to see if those gives any suggestions to what is happening, that would be useful.

Do you have access to the UART pins on the nRF52840 where you run the connectivity firmware? If you do, can you check the lines with a logic analyzer to see if any data is sent from the PC to the board?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data