LAUNCHXL-CC1352P: Uart2_callback read error

Hi Ryan

     I changed my code as follow, It is strange.

   1、  I change readReturnMode to UART2_ReadReturnMode_PARTIAL, and I onle set my event in the read_calback function,

   2、  In my event,I write the received byte,then read one byte. 

   3、  The length of our uart cmd is not  fixed,so I can't read a fixed number of bytes

    Now,It's normal when I send one byte.But it only write the first byte once ,when I sent 2 bytes..

void hl_uart_write(uint8_t *inBuf,uint8_t inLen)
{
    UART2_write(UartHandle,inBuf,inLen,NULL);
}
void hl_uart_read(void *buffer, size_t size)
{
    UART2_read(UartHandle, buffer, size,NULL);
}
// uart init
void hl_uart_open(void)
{
    UART2_Params_init(&UartParams);
    UartParams.baudRate = 115200;
    UartParams.readReturnMode = UART2_ReadReturnMode_PARTIAL;
    UartParams.readMode = UART2_Mode_CALLBACK;
    UartParams.readCallback = AtProcess_processingLoop;

    UartHandle = UART2_open(CONFIG_UART2_0, &UartParams);
    if(UartHandle == NULL)
    {
        hl_print_string("Error opening the UART");
    }
    else
    {
        hl_print_string("UART open success");
        status = UART2_read(UartHandle, &ch_uart, 1,NULL);
    }
}
void AtProcess_processingLoop(UART2_Handle _handle, void *_buf, size_t _size, void *userArg, int_fast16_t status)
{
    hlAppLoopEvents |= HL_ZED_UART_EVT;
    Semaphore_post(appSemHandle);
}
//my loop
void hlApp_event_loop(void)
{
    if(hlAppLoopEvents & HL_ZED_1_EVT)
    {
//        hl_print_string("test");
        hlAppLoopEvents &= (~HL_ZED_1_EVT);
    }
    if(hlAppLoopEvents & HL_ZED_UART_EVT)
    {
        hl_uart_write(&ch_uart,1);
        hl_uart_read(&ch_uart,1);
        hlAppLoopEvents &= (~HL_ZED_UART_EVT);
    }
}

Hi Ryan

   4、I review the uart2callback example,it call uart2read() in "while (1)", I call it at the beging of the forever loop "zclSampleSw_process_loop()",   It does work, But I don't think it's reasonable for zed.

   5、I can't add pictures by "Insert—>Image/Video/file"，No URL button is selected

4. Do you wake up CC1252P before you start receiving UART message?

5. You can drag and drop image to reply box area to attach image.

4. Set an event inside the UART callback to be serviced by the main process loop after the semaphore has been posted.  Or handle the UART command directly inside the callback (if the instruction is brief enough).  Refer to the TI-RTOS section of the Z-Stack User's Guide, or the ZED switch UI which already incorporates UART for a sleepy node.

5. YK has the right idea, content insertion has changed since the E2E interface update and is still being improved upon.

Regards,
Ryan

The customer tried your suggestion, but it did not succeed.

The length of uart commands varies, some are more than ten bytes, and some are more than thirty bytes.

The reception is very unstable, when receiving long data in callback mode ,like:

Shaolin Zhang said:

But  when I send long buffer(31 bytes),my loop will run twice occasionally 

Make sure that the RX/TX ring buffer sizes have been increased in SysConfig -> UART2, also refer to this other E2E thread: https://e2e.ti.com/f/1/t/994971 

Regards,
Ryan