Issues with CLI over BLE Example

RE: Issues with CLI over BLE Example

Jared — Tue, 24 Nov 2020 12:56:30 GMT

Sorry for the confusion, but to be clear:

The python scrip should be run on the computer. But the python scrip itself will flash the second board with the fw by using pc-ble-driver.

RE: Issues with CLI over BLE Example

kmassa5 — Tue, 24 Nov 2020 12:44:30 GMT

Ok, thanks Jared! I've actually been running the Python script on my laptop via the terminal, so maybe that's been the source of my problems. I did some quick searching and found Zerynth and MicroPython as options for programming the additional board with ble_serial.py. Do you happen to have any recommendations between the two of them (or others)? I couldn't find anything super recent on Zerynth on DevZone.

Thanks!

RE: Issues with CLI over BLE Example

Jared — Tue, 24 Nov 2020 07:49:26 GMT

Hi,

Is the other board still advertising when you try to connect via PuTTY? Note that it will go to sleep after about 3 minutes of advertising. The flow of execution should be as follows:

Program board 1 with ble_app_cli application and the softdevice. Make sure that the led is blinking indicating that it's advertising.
Program board 2 with the python script.
Use PuTTY to instruct board 2 to connect with board 1 by connecting to 127.0.0.1 with port 8889
The led on Board 1 should then indicate that they are connected and a terminal should be created in the PuTTY.

regards

Jared

RE: Issues with CLI over BLE Example

kmassa5 — Sat, 21 Nov 2020 00:17:29 GMT

Ok, I tried it in PuTTY too. When I click open, it causes ble_serial.py to crash with the error:

Connected with 127.0.0.1:64025

Traceback (most recent call last):

File "ble_serial.py", line 242, in <module>

b = BLE_Serial(comport, args.name, conn)

File "ble_serial.py", line 96, in __init__

self.adapter.driver.open()

File "/Users/kylemassa/Library/Python/2.7/lib/python/site-packages/pc_ble_driver_py/ble_driver.py", line 127, in wrapper

raise NordicSemiException('Failed to {}. Error code: {}'.format(wrapped.__name__, err_code))

pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 3

RE: Issues with CLI over BLE Example

kmassa5 — Wed, 18 Nov 2020 22:54:17 GMT

Thanks Jared! So to be clear, I am still trying to get past step 4 of the example instructions.

In one terminal window, I ran ble_serial.py and got the following output (command included):

python ble_serial.py --snr 682672012 --name Nordic_CLI --com COM0006826720121 --family NRF52

Board already flashed with connectivity firmware.

Socket created

Socket bind complete

Socket now listening

Connected with 127.0.0.1:57604

Traceback (most recent call last):

File "ble_serial.py", line 242, in <module>

b = BLE_Serial(comport, args.name, conn)

File "ble_serial.py", line 96, in __init__

self.adapter.driver.open()

File "/Users/kylemassa/Library/Python/2.7/lib/python/site-packages/pc_ble_driver_py/ble_driver.py", line 127, in wrapper

raise NordicSemiException('Failed to {}. Error code: {}'.format(wrapped.__name__, err_code))

pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 3

In another terminal window, I ran telnet as you suggested. Here is the output from that window (command included):

telnet 127.0.0.1 8889

Trying 127.0.0.1...

Connected to localhost.

Escape character is '^]'.

Connection closed by foreign host.

It looks like the connection is being dropped immediately after it's established. What could be causing this behavior?

RE: Issues with CLI over BLE Example

Jared — Wed, 18 Nov 2020 13:48:52 GMT

Hi,

I still don't think that SSH would be the correct protocol. I'm not sure as we haven't tested the application on Mac OS AFAIK. Doing a quick google search revealed that the telnet protocol would be the appropriate one to get a raw TCP/IP connection. Could you try this one instead?

Also, if you do have a windows computer with PuTTY available, then I strongly suggest that you use that one for testing the example.

regards

Jared

RE: Issues with CLI over BLE Example

kmassa5 — Wed, 18 Nov 2020 12:40:33 GMT

Hi,

I'm running

python ble_serial.py --snr 682672012 --name Nordic_CLI --com COM0006826720121 --family NRF52

which produces the output

"Board already flashed with connectivity firmware.

Socket created

Socket bind complete

Socket now listening"

So I've completed step 3 and am working on step 4. When I type

127.0.0.1:8889

in a different terminal window without any command, it returns "Command not found". The output produced in my above reply is triggered when I've completed step 3 and I use ssh for step 4.

Thanks!

RE: Issues with CLI over BLE Example

Jared — Wed, 18 Nov 2020 07:44:16 GMT

Hi,

What are you passing as parameters to the script now? Could you describe in more detail exactly what step you're at and what you're doing?

And why are you using ssh? I think it should be enough to just type in the destination address

[quote user="kmassa5"]

which is just its serial number with three 0's appended to the front. Is this the COM port I should be using in the ble_serial.py inputs?

[/quote]

Yes.

RE: Issues with CLI over BLE Example

kmassa5 — Mon, 16 Nov 2020 12:37:40 GMT

Hey Jared!

I tried using the Mac terminal, running a command like,

ssh user@localhost -p8889

This causes the example to crash with an error message like,

Connected with 127.0.0.1:56148

Traceback (most recent call last):

File "ble_serial.py", line 242, in <module>

b = BLE_Serial(comport, args.name, conn)

File "ble_serial.py", line 96, in __init__

self.adapter.driver.open()

File "/Users/kylemassa/Library/Python/2.7/lib/python/site-packages/pc_ble_driver_py/ble_driver.py", line 127, in wrapper

raise NordicSemiException('Failed to {}. Error code: {}'.format(wrapped.__name__, err_code))

pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: 3

And the terminal exits with,

kex_exchange_identification: read: Connection reset by peer

EDIT: While connected to my laptop via a usb connection, the board just appears as

/dev/tty.usbmodem0006826720121

which is just its serial number with three 0's appended to the front. Is this the COM port I should be using in the ble_serial.py inputs?

Thanks!

RE: Issues with CLI over BLE Example

Jared — Mon, 16 Nov 2020 09:16:01 GMT

Hi,

[quote user="kmassa5"]Sorry how do I determine the correct COM port? Thank you for the advice![/quote]

The serial port will appear as /dev/tty.usbmodemXXXX.

[quote user="kmassa5"]How do I do this on a mac without using PuTTY? Is there a PuTTY equivalent that will do this for me? In the meantime, I will look for a mac solution and get back to you if I discover anything on my own. [/quote]

Try using the default terminal in Mac OS.

Note that there is some limitations of using Mac OS X with J-link

regards

Jared

RE: Issues with CLI over BLE Example

kmassa5 — Fri, 13 Nov 2020 22:23:24 GMT

Hi,

Sorry how do I determine the correct COM port? Thank you for the advice!

Ok, so then what do you recommend I do with regards to pc-ble-driver-py? If I run it with just the "python" command (2.7), it still fails and can't find the module.

Thanks!

UPDATE: I got ble_serial.py working, I had to uninstall nrfutil and reinstall using pip instead of pip3. The problem was, on my mac, pip was never installed along with Python 2.7.x, so I had to do that first. Once I reinstalled nrfutil, I had to change the line importing dfu_transport_ble.py (it was located inside nordicsemi/dfu/ , so I had to add those directories to the import path).

So now I still need help with step 4:

"Open a terminal, for example PuTTY. Set the Connection Type to Raw and the Destination Address to 127.0.0.1:8889."

How do I do this on a mac without using PuTTY? Is there a PuTTY equivalent that will do this for me? In the meantime, I will look for a mac solution and get back to you if I discover anything on my own.

Thanks!

RE: Issues with CLI over BLE Example

Jared — Fri, 13 Nov 2020 10:56:12 GMT

Hi,

Is the correct COM port really 115? Have you typed in the correct serial number of the board that you're using? It seems that you're using the example values from the doc.

I just tested the example and noted that the script included in the SDK works with python2.7 but did not with python3. So the script is most likely written with python 2.7. Sorry for the contraction in my previous reply. That is the latest version of pc-ble-driver-py requires python 3.6 but the python script is written for python2.7

regards

Jared

RE: Issues with CLI over BLE Example

kmassa5 — Thu, 12 Nov 2020 16:51:29 GMT

Hi Jared,

I'm running Python 3.9.0. When I run the command using python3, I get a new error:

python3 ble_serial.py --snr 680834186 --name Nordic_CLI --com COM115 --family NRF52

Traceback (most recent call last):

File "/Users/kylemassa/Downloads/nRF5_SDK_16/examples/ble_peripheral/experimental/ble_app_cli/ble_serial.py", line 38, in <module>

import Queue

RE: Issues with CLI over BLE Example

Jared — Thu, 12 Nov 2020 12:35:02 GMT

Hi,

What version of python are you using? The latest version of pc-ble-driver-py requires minimum python 3.6

regards

Jared