How to print Unicode character

[Nabeel Ar]

Board: nRF52833

SoftDevice: s122

SDK version: 17.0.2

I'm trying to connect my device to the Edge Impulse through the edge impulse data forwarder. I have a peripheral that sends the sensor data to the central device through ble. The central device has the usbd_ble_uart example in it and it sends the data to the serial monitor through USB. While connecting to the data forwarder I'm getting the following error.

The error seems to be that it's printing a non-Unicode character. But the data looks fine on my serial monitor.

How can I change the data that has been printed to the Unicode character to solve this issue? Thanks in advance.

[Kenneth]

Hi,

I am not familiar with how the edge impulse data forwarded is working, but looking at the implementation of nus_data_handler() in usbd_ble_uart() I can find that is is strictly forwarding anything it does receive on BLE to USB without any modification, possible with the exception that is does add a ENDLINGE_STRING (\n\r). I think you will need to look at the peripheral side, though it's always possible to add mofications to your nus_data_handler() on the central if you know what to look for and for instance change it before fowarding it to USB. This is something you can do if you like.

It may seem you need to contact edge impulse in this case, alternatively I would recommend to check out nRF Connect SDK, since we are not really doing any new features with the nRF5 SDK: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/samples_edge.html

Kenneth

[Nabeel Ar]

Hi,

Kenneth said:

I think you will need to look at the peripheral side

I'm just receiving the data from the sensor and sending it through the ble_nus_data_send() function.

I found the #define APP_USBD_CONFIG_DESC_STRING_UTF_ENABLED 0 define in sdk_config.h file. Does it do anything with the issue? Though I tried enabling it, nothing has changed. Does UTF have to do anything with it? Is there any other way to solve it?

Thanks!

[Kenneth]

Please consider the usbd_ble_uart as fully transparent, so if you have any problems with data not in the correct format etc then the problem is not related to the usbd_ble_uart example, since the example just pass through any data as it's received.

Kenneth