RESET command value via bluetooth

RE: RESET command value via bluetooth

Hieu — Mon, 02 Oct 2023 07:42:05 GMT

It's great to know that you got it. Please feel free to close this ticket at your convenience then 🙂

Regards,

Hieu

RE: RESET command value via bluetooth

fran_ce — Sat, 30 Sep 2023 15:39:31 GMT

Thank you very much!
After some tries I finally managed it!
I was encoding the payload in the wrong way, but your guide has been very helpful with this, very appreciate.

Best,

Francesco

RE: RESET command value via bluetooth

Hieu — Wed, 13 Sep 2023 15:41:37 GMT

Hi Francesco,

The specification for the SMP commands can be found here: SMP Protocol Specification — Zephyr Project documentation (nRF Connect SDK) (nordicsemi.com).

As far as I can see, the value from the nRF Connect App for Android that you noted down looks correct.

A thing to note is that, as noted in the protocol specification, the Sequence Number is supposed to increment with each subsequent command.
In my tests, I see that it doesn't seem to matter, so it might not explain your setup not working. Nonetheless, please try to increment the Sequence Number appropriately in your future attempts.

Finally, the Data is a CBOR encoded, and is just empty. The encoding library used in the app simply encodes empty data, {} as a BF FF, with a Data Length of 2. You can keep it as is.

So, the command you will want is:

02-00-00-02-00-00-<Sequence Number>-05-BF-FF

I am not familiar with the react-native-ble-plx library. If you really want someone to join you looking into it, I can. As of right now, I can only make these suggestions:

Please see if it is possible to enable logging to see what the library tries to send to the device.
Please check if the byte order is handled differently in that library.
- For a quick test, you can try to get it to talk with the Nordic UART Service instead. This service handles notifications as ASCII strings.

For the device end, you can configure the following Kconfig to get logging from the BLE Transport of the SMP module:

CONFIG_MCUMGR_TRANSPORT_LOG_LEVEL_DBG=y
CONFIG_LOG_MAX_LEVEL=4

# Need immediate logging or the device will reset 
# before the hex dump of the command is printed
# For debugging purpose only
CONFIG_LOG_MODE_IMMEDIATE=y

# Set SMP Transport work queue stack size unreasonably large 
# to prevent stack overflow due to immediate logging
# For debugging purpose only
CONFIG_MCUMGR_TRANSPORT_WORKQUEUE_STACK_SIZE=8192

# Optionally switching logging backend to UART
CONFIG_LOG_BACKEND_RTT=n 
CONFIG_LOG_BACKEND_UART=y

With that, I was able to log that the device reset at the same command you found:

RE: RESET command value via bluetooth

fran_ce — Tue, 12 Sep 2023 16:39:47 GMT

Hi Hieu,

thank you for your fast reply.

You're correct, the GATT Service I'm using is the SMP Server you linked.

I'm trying to figure out the format of the string to encode in Base64 to pass as value of the write function

RE: RESET command value via bluetooth

Hieu — Tue, 12 Sep 2023 08:54:25 GMT

Hi Francesco,

Welcome to DevZone!

In the nRF Connect SDK, our default BLE GATT Service for device management is the SMP Server. However, it seems like you have a certain communication protocol going on.

The details don't appear familiar to me. Could you please tell me what GATT Service you are using?

Regards,

Hieu