Bluetooth Mesh example: Interactive PyACI timeout

RE: Bluetooth Mesh example: Interactive PyACI timeout

pwgh — Fri, 08 Jun 2018 00:01:14 GMT

I've also been running into this issue since version 1.0 of the mesh SDK. I'm pretty sure this isn't a problem with my computer, the OS or any software on it. My setup is pretty similar to TYRI's except for Arch Linux.

The serial example seems to work once out of every ten tries. When it works, it continues to work until the board is turned off.

I've tried the following and nothing seems to have an effect:

Resetting with nrfjprog -r or -p
Using the switch to turn the board off and on
Unplugging the board from the USB port
Reflashing the serial example
Doing --eraseall then reflashing
Rebooting my computer
Switching between my desktop to my laptop
Running in debugging mode in Embedded studio
Leaving the board unplugged without a battery for several minutes
Switching between different devkit boards

Despite any of this, sending even a trivial Echo command to the board fails most of the time.

Sometimes when the example works I see the following error when starting interactive_pyaci.py:

2018-06-07 16:15:48,254 - ERROR - ttyACM0: Exception in pkt handler <bound method Interactive.__event_handler of <__main__.Interactive object at 0x7f4d97d5eef0>>
2018-06-07 16:15:48,261 - ERROR - ttyACM0: traceback: Traceback (most recent call last):
  File "/home/patonw/code/nordic/nrf5_sdk_for_mesh/scripts/interactive_pyaci/aci/aci_uart.py", line 88, in process_packet
    fun(packet)
  File "interactive_pyaci.py", line 164, in __event_handler
    if self._event_filter_enabled and event._opcode in self._event_filter:
AttributeError: 'Interactive' object has no attribute '_event_filter_enabled'

I need to spend more time with the debugger but my hunch is that something is not getting initialized in the mesh SDK. When the serial example behaves normally, it will trigger a breakpoint in serial_bearer_rx_get with the following call stack (doing this from memory since I can't get the example to work again):

bearer_event.c: EVENT_IRQHandler
bearer_event.c: bearer_event_handler
bearer_event.c: call_callback
serial.c: serial_process
serial.c: serial_process_cmd
serial_bearer.c: serial_bearer_rx_get

However, when the example fails to run none of these functions are invoked, aside from EVENT_IRQHandler which is getting called constantly, regardless.

RE: Bluetooth Mesh example: Interactive PyACI timeout

Mttrinh — Tue, 29 May 2018 14:06:22 GMT

See if this post could be of any help.

RE: Bluetooth Mesh example: Interactive PyACI timeout

TYRI — Fri, 25 May 2018 14:09:26 GMT

Thank you for the information. I've tried what you mentioned except for using the earlier SEGGER version. One thing to note is that ninja is calling /usr/bin/python which makes it harder to use a virtual python environment. i.e. it doesn't just call 'python' and hence bypasses the python selected by virtualenv (prepended to PATH).
I don't know if this is per default by ninja or due to your configuration of the build.

Please let me know if the situation improves.

RE: Bluetooth Mesh example: Interactive PyACI timeout

Mttrinh — Thu, 24 May 2018 15:17:12 GMT

This is a virtual com port issue. We don't have a specific fix for this unfortunately. You can try installing a different SEGGER J-LINK version, Jlink v6.16c, and give access to the COM port by adding the user to the dialout group: sudo adduser $USER dialout.

Also try plugging your board in and out or reflashing, see if that helps.

Another tip is to use a virtual environment when working with Python. It allows you to use multiple Python installations on one machine quite effortlessly. A guide for it is found here.

RE: Bluetooth Mesh example: Interactive PyACI timeout

TYRI — Fri, 18 May 2018 12:14:30 GMT

Unfortunately I still receive the timeout.

RE: Bluetooth Mesh example: Interactive PyACI timeout

Mttrinh — Wed, 16 May 2018 14:20:28 GMT

Hi,

Are you using 32-bit python? If not, I would suggest you to do so and see if that help fix the issue.