UART in nrf52832

RE: UART in nrf52832

Karl Ylvisaker — Thu, 04 Jun 2020 11:10:06 GMT

Hello Gecko,

[quote user="Kalpeshh42"] I am using nRF_Connect now to send the commands instead of nRF Toolbox and commands are getting sent in HEX correctly[/quote]

I am happy that the issue was resolved!

[quote user="Kalpeshh42"]I receive ack of 1 byte ,sometimes 4 bytes or 6 bytes from sensor.[/quote]

Is there no way for you to anticipate either the length or the contents of your sensors ACK?
If so, I would suggest that you add an end-of-message character at the end of each ACK, and then look for that.
Alternatively, you could start every transmission by having the first byte be the length of the incoming transmission, or something similar.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Thu, 04 Jun 2020 06:52:14 GMT

Hi will you please reply I am still waiting

RE: UART in nrf52832

Gecko — Wed, 03 Jun 2020 16:46:52 GMT

Karl I am using nRF_Connect now to send the commands instead of nRF Toolbox and commands are getting sent in HEX correctly

below is my another doubt.

Now,when I am sending different commands from mobile(mobile->command->ble->pca10040->uart) I expect ack for that command from from my sensor (sensor->ack->uart->pca10040->ble->mobile).

I receive ack of 1 byte ,sometimes 4 bytes or 6 bytes from sensor.

Hence if I set (index >= 1)) I only receive 1st byte of 4 bytes ack. or when I set (index >= 6) I don't receive any bytes of 4 bytes ack because I have set limit of 6.

How can I generalize this condition so that even I get ack of 1 byte or 6 bytes or whatever size I should able to read it over mobile./ or print it on terminal

void uart_event_handle(app_uart_evt_t * p_event)
{
    static uint8_t data_array[BLE_NUS_MAX_DATA_LEN];
    static uint8_t index = 0;
    uint32_t       err_code;
    char temp_str[40];
  
    switch (p_event->evt_type)
    {
        case APP_UART_DATA_READY:
            UNUSED_VARIABLE(app_uart_get(&data_array[index]));
            index++;

            if ((data_array[index - 1] == '\n') ||
                (data_array[index - 1] == '\r') ||
                (index >= 6))
            {
                if (index > 0)       
                {

                    NRF_LOG_INFO("Ready to send data over BLE NUS");
//                  NRF_LOG_DEBUG("Ready to send data over BLE NUS");
                    NRF_LOG_HEXDUMP_DEBUG(data_array, index);

                    do
                    {
                        uint16_t length = (uint16_t)index;
                        err_code = ble_nus_data_send(&m_nus, data_array, &length, m_conn_handle);
                        if ((err_code != NRF_ERROR_INVALID_STATE) &&
                            (err_code != NRF_ERROR_RESOURCES) &&
                            (err_code != NRF_ERROR_NOT_FOUND))
                        {
                            APP_ERROR_CHECK(err_code);
                        }
                    } while (err_code == NRF_ERROR_RESOURCES);
                }

                index = 0;
            }
            break;

RE: UART in nrf52832

Karl Ylvisaker — Wed, 03 Jun 2020 16:22:19 GMT

Hello,

[quote user="Kalpeshh42"][/quote]

thanks for your reply I found the error in hardware config params in which I had to set

.use_parity = true, in the code.now I am receiving data on nrf_toolbox UART mobile app.

No problem at all. I am happy to hear that you were able to resolve the issue!

[quote user="Kalpeshh42"][/quote]

So I hard coded that value in the code as shown in my below attached code and it worked.

But I can not hard code single hex value in my code,because I need to send different(0x02,0x01,0x0405) commands.

How should I modify the code to send hex command correctly from mobile ?

From your description I suspect that your conversion between different types is what is causing the issue. Especially since it works as intended when hardcoded into the app.
If I recall correctly the NUS service sends the data as ASCII uint8_t chars. Could you ensure that what you are attempting to send to your sensor has the correct value? You could print the raw value of the data before sending it to your sensor, to verify that it is in fact 0x02.

If this turns out to be the case, then you would either have to modify the commands you send from your phone accordingly, or you may define an intermediate "translation" macro for each command.

Looking forward to resolving this issue together,

Best regards,
Karl

RE: UART in nrf52832

Gecko — Wed, 03 Jun 2020 06:45:49 GMT

Hi Karl, thanks for your reply I found the error in hardware config params in which I had to set

.use_parity = true, in the code.now I am receiving data on nrf_toolbox UART mobile app.

Now my UART sensor is sending data continuously which I can read on mobile.If I want to stop data I should send '0x02'(HEX) from the mobile.But when I am doing this it is not getting stopped.Upon further investigation I understood my sensor is not receiving '0x02'.

So I hard coded that value in the code as shown in my below attached code and it worked.

But I can not hard code single hex value in my code,because I need to send different(0x02,0x01,0x0405) commands.

How should I modify the code to send hex command correctly from mobile ?

static void nus_data_handler(ble_nus_evt_t * p_evt)
{

    if (p_evt->type == BLE_NUS_EVT_RX_DATA)
    {
        uint32_t err_code;

        NRF_LOG_INFO("Received data from BLE NUS. Writing data on UART.");
        NRF_LOG_HEXDUMP_DEBUG(p_evt->params.rx_data.p_data, p_evt->params.rx_data.length);
        for (uint32_t i = 0; i <p_evt->params.rx_data.length; i++)
        {
            do
            {
                
                //err_code = app_uart_put(p_evt->params.rx_data.p_data[i]);
                err_code = app_uart_put(0x02); //HARDCODED VALUE
                if ((err_code != NRF_SUCCESS) && (err_code != NRF_ERROR_BUSY))
                {
                    NRF_LOG_ERROR("Failed receiving NUS message. Error 0x%x. ", err_code);
                    APP_ERROR_CHECK(err_code);
                }
            } while (err_code == NRF_ERROR_BUSY);
        }
        if (p_evt->params.rx_data.p_data[p_evt->params.rx_data.length - 1] == '\r')
        {
            while (app_uart_put('\n') == NRF_ERROR_BUSY);
        }
    }

}

RE: UART in nrf52832

Karl Ylvisaker — Fri, 29 May 2020 14:06:49 GMT

Hello,

[quote user="Kalpeshh42"]ERROR 4 [NRF_ERROR_NO_MEM] at :0 [/quote]

Great, that is much better.
Which function is raising the error?
Please see this ticket.

[quote user="Kalpeshh42"]is it related to UART pins configuration for pull up ? But I’m doing that also.[/quote]

NO_MEM is not related to UART pin configuration, at least not directly.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 29 May 2020 12:37:45 GMT

1. Yes I am using Nordic UART BLE

2. After defining #DEBUG in app_error_weak.c it shows below error.

ERROR 4 [NRF_ERROR_NO_MEM] at :0

PC at: 0x00000000

is it related to UART pins configuration for pull up ? But I’m doing that also.

RE: UART in nrf52832

Karl Ylvisaker — Fri, 29 May 2020 12:22:30 GMT

Hello,

[quote user="Kalpeshh42"]I think the solution given by your colleague is for using breakpoints.[/quote]

The particular issue in the case was the use of breakpoints, but the issue with halting the CPU while debugging is what I wanted to highlight.
Are you still working with the UART peripheral example, or have you now moved on to working with the Nordic UART BLE example? I assumed the latter, since you mention the transmission to/from mobile, but in your initial ticket you only mention the UART peripheral example.

Have you defined DEBUG? It would be greatly beneficial to know the exact file name, line and error code.
There are multiple tickets on Devzone discussing the possible causes for the NRF_BREAKPOINT_COND when using UART. Could you attempt to solutions from this, and this ticket, and see if they resolve your problem, or at least identify the root issue?

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 29 May 2020 11:49:36 GMT

Hi Karl but I’m not using any breakpoints in my code.I think the solution given by your colleague is for using breakpoints.

all I’m doing is sending data from UART and I’m getting NRF_BREAKPOINT_COND

RE: UART in nrf52832

Karl Ylvisaker — Fri, 29 May 2020 10:45:05 GMT

Hello,

[quote user="Kalpeshh42"]Now I start debug button in SES. After that I am sending one byte of command from the sensor but I immediately receive NRF_BREAKPOINT_COND in app_error_weak.c file.[/quote]

Have you seen this answer by my colleague? Debugging will cause errors when using the SoftDevice, if you have not already followed the instructions my colleague details.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 29 May 2020 10:39:00 GMT

Hi I am waiting for your response.Thanks in advance.

RE: UART in nrf52832

Gecko — Fri, 29 May 2020 09:18:58 GMT

Hi Karl,

Now I have connected P0.8 (RX) to TX and P0.6 (TX) to RX of of my hardwired sensor.

Now I start debug button in SES. After that I am sending one byte of command from the sensor but I immediately receive NRF_BREAKPOINT_COND in app_error_weak.c file.

How to solve this ? Also I am not opening COM port at the same time as suggested by you.

RE: UART in nrf52832

Karl Ylvisaker — Mon, 25 May 2020 06:28:16 GMT

Hello,

I understand that you are trying to do a loopback test of the two connected devices.
Could you tell me what connections(with pin numbers) you have made to perform the loopback example?

[quote user="Kalpeshh42"]Now when I send "0x01\n" from mobile I am not receiving anything on the mobile.[/quote]

Could you elaborate on what happens when you do this? What are you observing?
Be advised that if you have the virtual com port open on the peripheral device, then it will send the data there instead of looping it around using the pins.
Could you confirm that you do not have the virtual com port open when performing your test?

Best regards,
Karl

RE: UART in nrf52832

Gecko — Sat, 23 May 2020 13:08:34 GMT

Hi Karl I'm waiting for your reply.Thanks in advance

RE: UART in nrf52832

Gecko — Sat, 23 May 2020 11:37:31 GMT

Hi Karl,

In the ble_app_uart code I dont want to use any serial terminal to send the data to nrf_uart app.
For this I did short rx to tx and rts to cts.Now when I send "0x01\n" from mobile I am not receiving anything on the mobile.
What could be wrong ?

RE: UART in nrf52832

Karl Ylvisaker — Fri, 22 May 2020 10:44:40 GMT

Hello again,

[quote user="Kalpeshh42"]Do you have any example code with data reception from uart interfaced device.[/quote]

Both the UART example and the Nordic UART example demonstrates this.

Have you seen the UART example? It implements UART communication with the possibility to perform a loopback test. To have the output show in your RTT terminal you would have to add a log call that logs the received/sent data.

[quote user="Kalpeshh42"]Because I understand app_uart_get function is used to receive the data from BLE where as in my case I will be receiving data from hardwired UART connections.[/quote]

This is incorrect. The app_uart_get has nothing to do with BLE, it retrieves data from the UART RX buffer, which is what you are attempting to do.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 22 May 2020 10:24:39 GMT

Hi Karl,I am waiting.please respond

RE: UART in nrf52832

Gecko — Fri, 22 May 2020 09:41:13 GMT

Okay thanks.

Do you have any example code with data reception from uart interfaced device.

Because I understand app_uart_get function is used to receive the data from BLE where as in my case I will be receiving data from hardwired UART connections.

OR maybe some example where I can do loopback and print data on debug terminal (not USB PORT)

RE: UART in nrf52832

Karl Ylvisaker — Fri, 22 May 2020 09:21:11 GMT

Hello,

[quote user="Kalpeshh42"]I have enabled RTT backend for logger module.And I could print logs on SES Debug Terminal using "NRF_LOG_INFO".[/quote]

Great, I am happy to hear that you got it working with RTT!

[quote user="Kalpeshh42"]So do you mean I can interface my external sensor with UART pins 5,6,7,8 without breaking those bridges and print the logs (Received UART data) on Debug Terminal ? [/quote]

Yes, as long as you do not open the virtual COM port, then you may use those same pins to connect to interface with another device. You may then use the logger module to see the received UART communication on your RTT viewer.
You do not have to break any solderbridges for this to work.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 22 May 2020 09:11:29 GMT

Hi Karl,

I have enabled RTT backend for logger module.And I could print logs on SES Debug Terminal using "NRF_LOG_INFO".

So do you mean I can interface my external sensor with UART pins 5,6,7,8 without breaking those bridges and print the logs (Received UART data) on Debug Terminal ?

thanks in advance.

RE: UART in nrf52832

Karl Ylvisaker — Fri, 22 May 2020 09:04:54 GMT

Hello again,

Sorry for my late reply - there was a national holiday in Norway yesterday.

[quote user="Kalpeshh42"]2.I have read in multiple nordic posts that 5,6,7,8 are connected to Interface MCU (PCA10040) hence these pins can not be used if I want to interface (Vibration sensor in my case) external hardware on UART.[/quote]

Well, yes and no. The pins are connected to the virtual COM port, but you do not have to break the solderbridges to use them as interface to another device. If you are going to use the UART as an interface to another device, then you may not use UART as the logging backend at the same time. I would therefor suggest using the RTT backend for logging.
As @Awneil also emphasized, you do not have to break the solderbridges to use the UART to interface another device - the GPIOs are tri-stated when nothing is connected to the virtual COM port.
To emphasize this, if you are running your application and communicating with your other device and then decide to open Putty to have a look at what is going on, it will not work.

[quote user="Kalpeshh42"]3. There is no NRF_LOG_BACKEND_RTT_ENABLED in sdk_config.h. For your information I am using uart example from nRF5_SDK_16.0.0_98a08e2 and installed mesh sdk is v4.0. [/quote]

You would have to add this to your SDK config yourself.
For an example on how to configure this, please see the ble peripheral Nordic UART example sdk_config.
Once you have RTT backend enabled(and UART backend disabled), you may use the Segger debug terminal, or the J-Link RTT Viewer application to see the logs.

[quote user="Kalpeshh42"][/quote]

if I break those bridges, I understand I will not get any logs on COM PORT (putty) then in that case how should I debug my loopback test ?

Which logs I can use to print my data on debug terminal

This is correct, but you do not have to break those bridges to use the UART to interface another device.
You may not have any logs on your COM port either way if you intend to use the UART to interface with another device, since there is only 1 UART instance on the nRF52832 DK.
Changing pins of the UART will not enable you to have both UART logs and UART device interface at the same time. You may however enable RTT backend for the logger module, instead of UART, which should solve your issue.

Best regards,
Karl

RE: UART in nrf52832

Gecko — Fri, 22 May 2020 04:53:42 GMT

Hi,I am waiting for your reply.thanks in advance

RE: UART in nrf52832

Gecko — Thu, 21 May 2020 11:02:31 GMT

Hi Karl,

if I break those bridges, I understand I will not get any logs on COM PORT (putty) then in that case how should I debug my loopback test ?

Which logs I can use to print my data on debug terminal

RE: UART in nrf52832

awneil — Thu, 21 May 2020 08:01:48 GMT

[quote userid="88876" url="~/f/nordic-q-a/61618/uart-in-nrf52832/251041"]I have read in multiple nordic posts that 5,6,7,8 are connected to Interface MCU (PCA10040) hence these pins can not be used [/quote]

Of course they can be used - but you have to bear in mind those other connections.

The User Guide tells you how to break those connections:

https://infocenter.nordicsemi.com/topic/ug_nrf52832_dk/UG/nrf52_DK/solderbridge.html

The User Guide also says:

"The UART signals are routed directly to the interface MCU. The UART pins connected to the interface MCU are tri-stated when no terminal is connected to the virtual COM port on the computer."

(my emphasis)

https://infocenter.nordicsemi.com/topic/ug_nrf52832_dk/UG/nrf52_DK/vir_com_port.html

RE: UART in nrf52832

Gecko — Thu, 21 May 2020 07:30:55 GMT

Hi Karl,

I am waiting for your reply.