When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Thu, 04 Jul 2024 01:51:06 GMT

Remove the serial port sending operation from `nus_data_handler` and use timer to trigger serial port sending to solve the problem.

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Mon, 01 Jul 2024 06:00:04 GMT

During stress testing, it was found that when the Bluetooth signal was poor, the data transmission rate decreased and app_uart_put was more likely to return NRF_ERROR_NO_MEM

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Mon, 24 Jun 2024 04:41:03 GMT

Hi Kenneth

There is one thing I didn't make clear. I used app_uart_fifo.c.
First, if I change it as you said above, the uart will lose data. So I used fifo. The code is in nRF5_SDK_17.1.0_ddde560\components\libraries\uart\app_uart_fifo.c +221 in the sdk, and it does return that the fifo is full.

uint32_t app_uart_put(uint8_t byte)
{
    uint32_t err_code;
    err_code = app_fifo_put(&m_tx_fifo, byte);
    if (err_code == NRF_SUCCESS)
    {
        // The new byte has been added to FIFO. It will be picked up from there
        // (in 'uart_event_handler') when all preceding bytes are transmitted.
        // But if UART is not transmitting anything at the moment, we must start
        // a new transmission here.
        if (!nrf_drv_uart_tx_in_progress(&app_uart_inst))
        {
            // This operation should be almost always successful, since we've
            // just added a byte to FIFO, but if some bigger delay occurred
            // (some heavy interrupt handler routine has been executed) since
            // that time, FIFO might be empty already.
            if (app_fifo_get(&m_tx_fifo, tx_buffer) == NRF_SUCCESS)
            {
                err_code = nrf_drv_uart_tx(&app_uart_inst, tx_buffer, 1);
            }
        }
    }
    return err_code;
}

Regards

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Kenneth — Sun, 23 Jun 2024 18:36:09 GMT

Looking at the implementation of app_uart_put() it looks like app_uart_put() changes NRF_ERROR_BUSY to NRF_ERROR_NO_MEM, see here:

uint32_t app_uart_put(uint8_t byte)
{
    tx_buffer[0] = byte;
    ret_code_t ret =  nrf_drv_uart_tx(&app_uart_inst, tx_buffer, 1);
    if (NRF_ERROR_BUSY == ret)
    {
        return NRF_ERROR_NO_MEM;
    }
    ...
    ...

So that means in main() you also need to replace NRF_ERROR_BUSY to NRF_ERROR_NO_MEM also. Looks like line 238 and 243 must do this change.

Kenneth

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Sun, 23 Jun 2024 15:19:01 GMT

Hi Kenneth:

This example is to test the Bluetooth transmission rate. The problem I am facing now is that the data received by BLE is sent through UART, and the FIFO is full, as mentioned in the title.

I have tested it without changing any code, and the problem still occurs. I changed the code just to print the BLE receiving rate.

This zip does have a problem, and I also tried it. You can directly use the code sent by Sigurd Hellesvik for testing.

Regards

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Kenneth — Sat, 22 Jun 2024 10:04:05 GMT

The zip seems to be corrupt/invalid, I am not able to open. I suggest to first verify that the example works as-is before you do any modification. I highly recommend to order yourself a DK for comparison.

Kenneth

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Wed, 19 Jun 2024 03:26:52 GMT

This is the code I modified and used on my board. I don't have a development board here. If possible, can you help me verify it? My verification logic is as follows

devzone.nordicsemi.com/.../usr_5F00_ble_5F00_app_5F00_uart_5F00_throughput.zip

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 17:03:05 GMT

I tried this example and still the same problem occurs, I added the data rate print received by bluetooth

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Sigurd Hellesvik — Tue, 18 Jun 2024 14:28:46 GMT

[quote user="Sigurd Hellesvik"]Aha, so it does not appear always, just when you send a lot of data at once, right?[/quote]

Here is an example for sending a lot of data via the NUS sample:

devzone.nordicsemi.com/.../8865.nrf5_5F00_sdk_5F00_17.0.2-_2D00_-ble_5F00_app_5F00_uart_5F00_throughput.zip

See that to learn how to increase performance.

[quote user="guojf"]By the way, what could be the reason why ncs cannot be downloaded?[/quote]

This can happen in China due to firewall issues i think
Try to Contact your local sales people. They may have some tips to how to fix this, as they are in the same country.

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 09:58:32 GMT

By the way, what could be the reason why ncs cannot be downloaded?

recover and readregs is ok

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 09:37:08 GMT

Yes

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Sigurd Hellesvik — Tue, 18 Jun 2024 09:27:14 GMT

Aha, so it does not appear always, just when you send a lot of data at once, right?

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 07:50:21 GMT

By the way, I also changed the connection interval

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(30, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(30, UNIT_1_25_MS)

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 07:49:04 GMT

Sometimes it even appears at around 8KB/s

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 07:44:41 GMT

To verify this problem, I used the example, changed the pin of UART, enabled UARTE, and realized the transparent transmission between BLE<->UART<->CP2102<->PC.

Deleted the code related to button and LED, and checked that there was no conflict between pin and UART pin.

It is easy to appear when approaching 115200bps, and it will appear during the sending and receiving process. It has never appeared when only sending or only receiving.

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Sigurd Hellesvik — Tue, 18 Jun 2024 07:35:38 GMT

Alright, lets do nRF5 then.

You say your ble_app_uart example fails.
What do you use on the other side to communicate with it?
Did you change anything in the sample?
Does it fail no matter how little text you send?

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Tue, 18 Jun 2024 07:27:34 GMT

Since yesterday, I have been trying ncs, and now I have been unable to download the code. I think it will take some time to implement the original project on ncs. If possible, I would like to solve this problem on nrf5 now.

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Sigurd Hellesvik — Tue, 18 Jun 2024 06:45:21 GMT

If you want to continue using the nRF5 SDK instead, I can help you. Just wanted to let you know that the new one is new.
Which SDK do you choose?

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

guojf — Mon, 17 Jun 2024 14:19:58 GMT

Hi Sigurd Hellesvik:

Thanks for your reply. The reason why I chose nrf5sdk is that keil development is easy to use and debugging is also convenient. I have already developed a product. I will try to verify this issue using nRF Connect SDK.

Regards

RE: When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Sigurd Hellesvik — Mon, 17 Jun 2024 11:13:54 GMT

Hi,

I see that this is your first ticket, and that you are using the nRF5 SDK.

If you do not have a reason to use this, I recommend that you use our new SDK instead, the nRF Connect SDK.

See the nRF Connect SDK and nRF5 SDK statement.

I recommend the Nordic Developer Academy as an excellent place to start learning the nRF Connect SDK.

Regards,
Sigurd Hellesvik