MCU-PLUS-SDK-AM243X: How do we recognize the potential failure described in Eratta i2310

Hi Mark,

The assigned is expert is out of office today. Responses to this thread will be delayed. Thanks for your cooperation.

Regards,

Tushar

Hi Tushar,

Any update?

Thanks, Merril

Hi,

Thanks for your patience.

I have tracked the owner for the commit for i2310 which can be seen now in the MCU PLUS SDK under drivers/uart.

I will discuss and let you know once I have updates.

Regards,

Vaibhav

Hi,

I would need more time to comment my thoughts on this.

Regards,

Vaibhav

Hi Vaibhav,

Any update?

Thanks, Merril

Hi Newman,

I am trying to reproduce this issue on the AM243-LP TI EVM.

The goal here is as follows.

Please check my test application. Note, I have put a breakpoint at the API UART_i2310WA to see if it hits that and hence I can draw some conclusion from it.

/*
 *  Copyright (C) 2021 Texas Instruments Incorporated
 *
 *  Redistribution and use in source and binary forms, with or without
 *  modification, are permitted provided that the following conditions
 *  are met:
 *
 *    Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 *    Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the
 *    distribution.
 *
 *    Neither the name of Texas Instruments Incorporated nor the names of
 *    its contributors may be used to endorse or promote products derived
 *    from this software without specific prior written permission.
 *
 *  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
 *  "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
 *  LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
 *  A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
 *  OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 *  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 *  LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
 *  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
 *  THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 *  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 *  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

/* This example demonstrates the UART RX and TX operation by echoing char
 * that it recieves in blocking, interrupt mode of operation.
 * When user types 'quit', the application ends.
 */

#include <string.h>
#include <kernel/dpl/DebugP.h>
#include "ti_drivers_config.h"
#include "ti_drivers_open_close.h"
#include "ti_board_open_close.h"

#define APP_UART_BUFSIZE              (200U)
#define APP_UART_RECEIVE_BUFSIZE      (8U)

uint8_t gUartBuffer[APP_UART_BUFSIZE];
uint8_t gUartReceiveBuffer[APP_UART_RECEIVE_BUFSIZE];
volatile uint32_t gNumBytesRead = 0U, gNumBytesWritten = 0U;

#define APP_UART_ASSERT_ON_FAILURE(transferOK, transaction) \
    do { \
        if((SystemP_SUCCESS != (transferOK)) || (UART_TRANSFER_STATUS_SUCCESS != transaction.status)) \
        { \
            DebugP_assert(FALSE); /* UART TX/RX failed!! */ \
        } \
    } while(0) \

void uart_echo(void *args)
{
    int32_t          transferOK;
    UART_Transaction trans;

    Drivers_open();
    Board_driversOpen();

    DebugP_log("[UART] Echo example started ...\r\n");

    uint32_t tries = 1000;
    while(tries > 0)
    {
        tries--;
        UART_Transaction_init(&trans);

        /* Send entry string */
        gNumBytesWritten = 0U;
        trans.buf   = &gUartBuffer[0U];
        strncpy(trans.buf,"This is uart echo test blocking mode\r\nReceives 8 characters then echo's back. Please input..\r\n", APP_UART_BUFSIZE);
        trans.count = strlen(trans.buf);
        transferOK = UART_write(gUartHandle[CONFIG_UART_CONSOLE], &trans);
        APP_UART_ASSERT_ON_FAILURE(transferOK, trans);

        /* Read 8 chars */
        gNumBytesRead = 0U;
        trans.buf   = &gUartReceiveBuffer[0U];
        trans.count = APP_UART_RECEIVE_BUFSIZE;

        for(int i = 0; i < 8; i++) gUartReceiveBuffer[i] = 97 + i;

//        transferOK = UART_read(gUartHandle[CONFIG_UART_CONSOLE], &trans);
//        APP_UART_ASSERT_ON_FAILURE(transferOK, trans);

        /* Echo chars entered */
        gNumBytesWritten = 0U;
        trans.buf   = &gUartReceiveBuffer[0U];
        trans.count = APP_UART_RECEIVE_BUFSIZE;
        transferOK = UART_write(gUartHandle[CONFIG_UART_CONSOLE], &trans);
        APP_UART_ASSERT_ON_FAILURE(transferOK, trans);

        /* Send exit string */
        gNumBytesWritten = 0U;
        trans.buf   = &gUartBuffer[0U];
        strncpy(trans.buf, "\r\nAll tests have passed!!\r\n", APP_UART_BUFSIZE);
        trans.count = strlen(trans.buf);
        transferOK = UART_write(gUartHandle[CONFIG_UART_CONSOLE], &trans);
        APP_UART_ASSERT_ON_FAILURE(transferOK, trans);

        DebugP_log("All tests have passed!!\r\n");
    }

    Board_driversClose();
    Drivers_close();

    return;
}

Regards,

Vaibhav

I have looked through the code and putting out few things that I have narrowed down.

There is a register named UART_IIR_UART

This will tell us about the Interrupt type or more formally the type of interrupt which is currently generated.

Just focus on the yellow highlighted section. 

If the value read from the UART_IIR register is 1100b, then this means, the Interrupt is RX Timeout READ 6h.

If this occurs, then we check if there is minimum 1 byte to be read:

1. If NO bytes to be read, we are good to go ahead.
2. If YES, then we come across the errata i2310
   

Hello Vaibhav, 

We don't have an easy way to read the UART_EFR2 register, given that our production FW doesn't have a direct print for this register. 

Given this is a known errata on TI side, based on the script log above, can you help to confirm whether they are all due to this UART boot Errata?   


Thanks, 
Hong 

Hi Hong,

Hong Zhang said:

Given this is a known errata on TI side, based on the script log above, can you help to confirm whether they are all due to this UART boot Errata? 

I understand that this is a known errata, but currently it is hard to say when this is reproduced based off the logs.

Earlier, our test team has tested this by booting via Primary UART Bootmode over several cycles. They had a faulty sample, and hence they were able to reproduce this via ROM booting over primary uart bootmode.

But it was just that when it failed to boot, they concluded that as a failure due to the errata i2310 and proposed a fix for it.

I am not sure how this can translate to logs given you are doing UART Uniflash.

Please let me know if this helps you upto some extent: https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/10_01_00_32/exports/docs/api_guide_am243x/TOOLS_FLASH.html#TOOLS_FLASH_ERROR_MESSAGES

Regards,

Vaibhav