This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2434: have send errors when doing UART boot on custom board

Part Number: AM2434
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

Hi BU experts,

My customer is doing UART boot on their custom board. What they do is basically following the EVM setup guide, except that using their own board.

They are using the default_sbl_null.cfg for the python script and are able to execute the first command successfully. However, they have send errors when executing the second command, shown in below picture:

We've look at similar issues on E2E, and have run the follow tests:

1. Using serial terminal to confirm AM243x is sending 'C' after power-on

2. Make sure no other program is occupying the serial port. (Since the first command is successful, this is unlikely)

3. Make sure using python3

4. Make sure it's hs_fs device and uses the hs_fs images.

5. Connect to am243x and load the sbl symbol to see the status. As the python script is terminated due to send error, am243x is still waiting for uart data in the uart driver.

Meanwhile, we've removed mmcsd in the sbl syscfg since customer board has no mmcsd. The sbl would stuck at mmcsd initialization if mmcsd is not removed. I am not sure if this is relevant.

Any idea what might be the cause of this?

Thanks,

Hang.

  • Hi Bu experts,

    Customer has solved this problem by adding UDMA in the sbl_uart_uniflash. They added it because they saw uart is using fifo, and simply assume fifo requires udma. However, UDMA is not included in the original sbl_uart_uniflash.

    Could you please help explaining this?

    Thanks,

    Hang.

  • Hello Hang,

    I am assuming the customer is going ahead with the UDMA addition in SysConfig, as they are not facing errors.

    But this is interesting.

    I am going to check this internally to see if this is a known issue.

    Regards,

    Vaibhav

  • Hello Hang,

    Just a quick update here, I have got my hands on the AM243-lp board.

    I am starting to recreate this issue. 

    Please allow me sometime to get back to you with additional updates.

    Regards,

    Vaibhav

  • Greetings Hang,

    Thanks for your patience.

    I have got my hands on AM243-LP HSFS and I did the procedure as mentioned by you.

    I have not seen any failures as of now.

    I am assuming the customer is having the latest SDK or is using the latest SDK. 

    Regards,

    Vaibhav

  • Hi Vaibhav,

    Thank you for reproducing the problem. Since this cannot be reproduced on LP, there might be some problem on their custom board. Nevertheless, could you provide some possible reasons why this is related to UDMA? So that the customer can look into it.

    Thanks,

    Hang,

  • Hello Hang,

    Thanks for your response.

    I will check internally with experts on this issue, where UDMA addition led to no failures in flashing sbl null on AM243-LP.

    Please allow me sometime to get back on this.

    Thanks for your patience.

    Regards,

    Vaibhav

  • Hello Hang,

    As you have mentioned that the customer was facing errors when they were trying to send the sbl_null.release.hs_fs.tiimage

    Can you let me know if there are any changes which the customer has made in this respective file ?

    Looking forward to your response.

    Regards,

    Vaibhav

  • Hi Vaibhzv,

    Following are the changes:

    1. Removed emmc in syscfg. They don't have emmc on their board and stuck at emmc initialization in sbl previously.

    2. Add UMDA, as I mentioned before.

    Regards,

    Hang

  • Hello Hang,

    Thanks for your response.

    Please expect responses in sometime.

    Regards,

    Vaibhav

  • Hello Hang,

    Thanks for your patience.

    I am actively looking at this, and I want the customer to try the following:

    In file C:\ti\mcu_plus_sdk_am243x_09_01_00_41\source\drivers\bootloader\bootloader_uniflash.c

    At the top of the file please write: #undef DRV_VERSION_MMCSD_V0

    Please let me know if after adding this and rebuilding the needed libraries is it working for the customer?

    Looking forward to your response.

    Regards,

    Vaibhav