I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Fri, 12 May 2023 08:12:49 GMT

Hello,

So what am I looking at here? Where is that log coming from? Is this the log from the nRF52? And the "garbled characters", are they from the UART on the nRF52840DK?

If not, please enlighten me 🙂

Best regards,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Wed, 10 May 2023 08:05:49 GMT

Attached is my block diagram:

I hope to use DK to receive nrf 52832 data and draw the received data into a real-time curve.
At present, when I use realterm to view, it will be garbled characters. I hope it can be the same as the LOG file seen in nrf connect BLE.

The attached picture is the data in the log file.

Many thanks for your kind help.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Tue, 09 May 2023 19:20:30 GMT

Did you connect the I2C pins from the sensor directly to the uart pins on the on the DK? I didn't see any references to I2C in your application.

Please note that UART and I2C are two completely different serial protocols. If your sensor is using I2C, you need to use I2C in your application as well to get the sensordata.

Hint: In the nRF5 SDK, "TWI" is the name for I2C. Look under the SDK\examples\peripheral folder and try out the different I2C/TWI examples. Note that you probably need to find a driver for your sensor (online). It will not spew out data. The sensor is a slave, so it needs to wait for commands from the master (the nRF) in order to reply with data.

Best regards,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Tue, 09 May 2023 16:19:25 GMT

My sensor is connected to nrf52832 through I2C, and then dump data on UART.
Later I found out that there was a problem with the program used to test it. After I tested it with realterm, I received the data, but the data is garbled.
Is the reason for the garbled characters that the size of each piece of data is 2 bytes? If so, which part should I modify?

Thanks again for your time and help.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Tue, 09 May 2023 11:56:35 GMT

Hello,

have you ever used the sensor that you want to interface? What kind of sensor is it? Does it use UART at all?

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Tue, 09 May 2023 07:11:16 GMT

I'm not really sure, but it should dump data on UART.
The attached picture is the connection using BLE in nRF connect.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Tue, 09 May 2023 06:14:21 GMT

Remember that I do not know anything about your sensor. Will it just dump data on UART, or do you need to do something for it to report back?

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Mon, 08 May 2023 14:54:17 GMT

Just read a previous reply and I realized I had something in sdk_config.h that I didn't adjust.
I adjusted these two things in sdk_config.h and it worked without error.
#define NRF_BLE_SCAN_NAME_CNT 1
#define NRF_BLE_SCAN_SHORT_NAME_CNT 1

After this adjust, the device can connect successfully.
If I want it to receive data from the sensor (I'm not sure if it does now), where should I start to modify it?

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Mon, 08 May 2023 14:06:08 GMT

My main.c line 203 is APP_ERROR_CHECK(err_code)， and the value passed into the line 203 is “err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_SHORT_NAME_FILTER, &short_name);”（the code I previose give.）
I only know that NRF_ERROR_INVALID_PARAMS is a case in nrf_ble_scan_filter_set (in nrf_ble_scan.c), but I don’t know what causes it.

I have attached this file below.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_c_5F00_1717.zip

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Mon, 08 May 2023 13:27:10 GMT

Ok. What is in your main.c line 203? Or to be precise, what function returned the value passed into the APP_ERROR_CHECK(err_code) on line 203?

And can you see (by looking into that function), why it returned 7, NRF_ERROR_INVALID_PARAMS?

Best regards,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Mon, 08 May 2023 13:24:26 GMT

The error message that was cut off in the photo is:<error> app: ERROR 7 [NRF_ERROR_INVALID_PARAM] at C:\Users\Justin_Kuo\AppData\nRF5SDK\nRF5_SDK_17.1.0_ddde560\examples\ble_central\ble_app_uart_c_1717\main.c:203
PC at: 0x0002B5FB

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Mon, 08 May 2023 13:15:35 GMT

Ok, add "DEBUG" to your preprocessor definitions, like I showed you how to do in one of my replies containing this line:

[quote user="Edvin Holmseth"] So I added the preprocessor definition "DEBUG", in order to get some more debug information in the log:[/quote]

There you will see a screenshot on how to do that.

Try to add that, and let me know what you see.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Mon, 08 May 2023 09:58:03 GMT

ok i got it
I'm now copying out a new ble_app_uart_c file and trying to use the internal app_uart to do what I want.
I first added the following program inside scan_init():

    //scan device name "the champ"
    char s_name[] = "the champ" ;
    nrf_ble_scan_short_name_t short_name ;
    short_name.p_short_name = ( const char* )&s_name ;
    short_name.short_name_min_len = 9 ;
    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_SHORT_NAME_FILTER, &short_name);
    APP_ERROR_CHECK(err_code);

    char name[] = "the champ 10007" ;
    err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_NAME_FILTER, name);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_ble_scan_filters_enable(&m_scan, NRF_BLE_SCAN_ALL_FILTER, false);
    APP_ERROR_CHECK(err_code);

But on the DEBUG page, it tells me that there is a fatal error in "err_code = nrf_ble_scan_filter_set(&m_scan, SCAN_SHORT_NAME_FILTER, &short_name);
APP_ERROR_CHECK(err_code);", if I want it to connect to the device I specified, how should I modify it?

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Mon, 08 May 2023 08:46:43 GMT

Ok, I see. Well, another option is to use the app_uart module that is already being used in the ble_app_uart_c example.

Either way, as your application is now, you have two modules trying to use the same UART. So you either need to comment out uart_init() in your main() function, or you need to comment out the libuarte stuff that you added. You can't have both using UART0 at the same time.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Fri, 05 May 2023 14:01:43 GMT

The function I want to achieve is to connect an external 6-axis sensor via Bluetooth and receive data from the sensor.
As for the reason why I will use libuarte in another Ticket, my reference program is to use nrf_serial to realize this function (older version)
At the beginning, there was an error when compiling with nrf_serial.h. When asking for a solution, I was recommended to use libuarte (because nrf_serial has been deprecated), so I changed my SDK version and tried to implement this function.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Fri, 05 May 2023 13:11:02 GMT

[quote user="Edvin Holmseth"]in main(), then it no longer returns NRF_ERROR_INVALID_PARAM, but rather NRF_ERROR_BUSY (17). Thsi is because you are already using your uart instance in uart_init() in main.c, so there you need to decide what you want to do.[/quote]

Yes. That is because you already initialized and set up that UART in uart_init() in main.

Are you really sure that you want to use libuarte? The example that you are using (ble_app_uart_c) already uses the UART in it's application.

Perhaps you can explain to me what you actually want to acheive. Is there a particular reason why you need to use libuarte instead of the normal uart driver that is already being used.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Fri, 05 May 2023 11:22:12 GMT

Ok, I see, and this is my log message:

Respectfully.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Fri, 05 May 2023 10:42:22 GMT

the ble_app_uart_c example doesn't use UART for logging, so you will not be able to see it in Realterm. It is using RTT logging, so you can either use JLink RTT Viewer (part of JLink bundle, so chances are that it is already installed on your computer).

Alternatively, I see from your screenshot that you are using Segger Embedded Studio. If you start a debug session, it will automatically open the RTT log:

BR,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Thu, 04 May 2023 14:12:49 GMT

Sorry, I didn't express it clearly, when I use Realterm to test it, it doesn't connect successfully.
I'm not quite sure if it's executing in the main() loop, in fact, I don't know how to check it.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Thu, 04 May 2023 12:16:36 GMT

[quote user="MuMu"]After these changes, my compile is successed, but it doesn't work as I expected: scans to the external sensor and connects it, is there something I might not have noticed?
[/quote]

What do you mean? Does it not connect to the device?

Is the main() loop reached? What does the log say?

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Thu, 04 May 2023 03:41:14 GMT

I followed your instructions:
I removed the files nrf_nvic.c and nrf_soc.c.
and I changed #define PPI_ENABLED 1, #define NRFX_PPI_ENABLED 1, #define NRF_BLE_SCAN_NAME_CNT 1 and #define NRF_BLE_SCAN_SHORT_NAME_CNT 1 in sdk_config.h.

Finally, I modified .int_prio = APP_IRQ_PRIORITY_LOW_MID in nrf_libuarte_async_config_t.

After these changes, my compile is successed, but it doesn't work as I expected: scans to the external sensor and connects it, is there something I might not have noticed?
The device name is "The champ 10006" .

Thanks a ton.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Wed, 03 May 2023 13:22:52 GMT

Ok, I took the time to adjust the scan filter settings in sdk_config.h:

#define NRF_BLE_SCAN_NAME_CNT 1
#define NRF_BLE_SCAN_SHORT_NAME_CNT 1

Then the next error points to 767 in main.c, the APP_ERROR_CHECK() after nrf_libuarte_async_init(), which returned 7 (NRF_ERROR_INVALID_PARAM).

So it doesn't like your configuration for your libuarte.

I don't know if it is intentional, but you are using the app_timer instance for libuarte (the libuarte is a large complex, resource heavy beast, so you should only use it if this is what you want to do. After changing:

.int_prio = APP_IRQ_PRIORITY_LOW_MID

in main(), then it no longer returns NRF_ERROR_INVALID_PARAM, but rather NRF_ERROR_BUSY (17). Thsi is because you are already using your uart instance in uart_init() in main.c, so there you need to decide what you want to do.

Best regards,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Wed, 03 May 2023 12:57:52 GMT

Ok, so I tried to compile, and it complained about not finding NRF_SUCCESS. The reason is that you included the files nrf_nvic.c and nrf_soc.c. These are intended for applications that doesn't have the SoftDevice. Since the application that you were using as a starting point, the ble_app_uart_c example, uses the SoftDevice, you don't need these two files.

Try to remove these two files, (right click and either remove or check the "exclude from build" option), and see if it builds.

In my case, I needed to do two more changes. in sdk_config.h:

#define PPI_ENABLED 1

and

#define NRFX_PPI_ENABLED 1

After that it built, and I tried running it. However, it failed, and the log said "Fatal error.". So I added the preprocessor definition "DEBUG", in order to get some more debug information in the log:

After that, the log pointed to line 220 in main.c, so this is not really related to the libuarte. Since this something completely different, perhaps you have already solved this at an earlier point. Let me know if you are struggling with this.

Best regards,

Edvin

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

MuMu — Wed, 03 May 2023 01:33:50 GMT

Hello Edvin, I have solved these two problems, they are all caused by the internal content of sdk_config.h not being added or enabled.
After solving these problems, when I use nrf_libuarte_async_init, an error as the picture shows:

Then I found an error message in nrf_libuarte_async.h, I tried to solve the problem by adding the C file used by libuarte to the nRF_Drivers folder, but I don’t know why nrf_error.h can’t be used.

This is my application and I use "Segger Embedded Studio"
devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_c_5F00_V17.1.zip

Thanks a ton.

RE: I have some problem about merge "ble_app_uart_c" with "libuarte", SDK17.1.0

Edvin — Tue, 02 May 2023 21:53:27 GMT

Hello,

It looks like you solved the first issue, but in case you have not, you probably just need to add the definition of NRF_LIBUARTE_DRV_UARTE0 to your sdk_config.h file, and set it to one. You can copy it from the libuarte example (sdk\examples\peripheral\libuarte).

The last issue is a bit more cryptic. Can you please let me know what it says when you are trying to compile your application? Copy the entire build log.

If possible, you can upload your application here (zip the application folder and upload), and I can have a look. Please let me know what IDE you are using if you do so.

Best regards,

Edvin