MCU-PLUS-SDK-AM243X: AM64x boot RTOS application from eMMC

Hi Michael,

Just wanted to confirm that you have installed the additional python packages as specified in python setup page 

Regards

Anshu

Hi Anshu,

I verified that, and yes, I cam confirm you that I have pyserial and xmodem in my python library. 

Regads,

Michael

Michael,

we had similar issue pointed by another user, can you look at this thread while we try to recreate your issue. which EVM are you using GP or SK

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1122789/sk-am64-downloading-sbl_null-to-sk-am64-does-not-work-with-8-03-or-8-02-it-works-with-7-03

Regards

Anshu

Hi Anshu,

e are using a custom board with SDK version 08.02. In the forum it says that the SK variant is not yet included in this version and is only available in version 8.02. I will try to use the SK version on Monday and will give you feedback.

Regards

Michael

Hi Anshu,

I tested the solution from the forum. But it doesn't work. It is the same behavior.

Regards

Michael

Micheal,

I will need to check with the SW team about your issue, please allow me few days, next week is a long holiday in India and hence expect some delays.

Regards

Anshu

Micheal,

We get the same issue when we follow the below steps on AM64x with 08.03 SDK and OSPI flash:

- Power cycle the board.

- First Execution: Execute the python script uart_uniflash.py with a configuration file containing commands to send sbl_uart_uniflash image & flash an application image. The execution is performed successfully.

- Second Execution: Again execute the python script with the same configuration file or a different one containing at least the command to send sbl_uart_uniflash image. This time, however, we get the error same as yours.

Solution: This error happens because we try to send flash writer image again in second execution when we have already sent it in first execution. The error can be removed if we do not send the flash writer image again and only send the application images as flash writer image acts a server on the board waiting in loop for only application images to be sent. The error can also be resolved if we power cycle the board between different executions.

More on what happens when we flash files can be found at: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/08_03_00_18/exports/docs/api_guide_am64x/TOOLS_FLASH.html#autotoc_md971

If you followed the same steps, please try Solution and then let us know if the issue still persists. If you got the error following something else, can you please confirm if you have already tried power cycling the board as the error suggests and then only flash the files.

Regards,

Prashant

Hello Prashant,

Yes, I did a power cycle and the problem persists.
The bootloader does not write anything into the eMMC and does not return an error.

Regards

Michael

Dear Michael,

Please give us an update on the issue so that we can take action. Are you still facing it or got resolved?

Thanks,

Prashant

Hi Prashant,

sorry for replying so late. I was in vacation and when I came back, the forum was down.

I didn't solve the issue and I hope you can help me to fix it. 

Regards

Michael

Dear Michael,

Flasing should work as I could flash successfully an application image on eMMC. I suspect your issue could be a hardware issue. Can you try flashing the application image to OSPI instead of eMMC. That way, I can narrow down the cause of issue. You can use the default_sbl_ospi.cfg configuration file in path <MCU+ SDK Install Dir>/tools/boot/sbl_prebuilt/am64x-evm to flash to OSPI.

Also, can you please answer the following questions just to make sure I have the right information to work with.

• Is it right that you are using GPEVM board not the SKEVM one?
• Did you change the SBL UART Uniflash code in example, build it, copied it in prebuilt folder and using it in configuration file to flash application image?

Regards,

Prashant