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.

CCS/TMDXEVM3358: SD card boot fails

Part Number: TMDXEVM3358

Tool/software: Code Composer Studio

Hello,

I am unable to boot AM335x EVM board with SD card.

I have used starterware library as base and modified it as per my requirement.

I am renaming 'boot_ti.bin' of MMCSD release to 'MLO' and 'buzzerBeep_ti.bin' to 'app'.

I have formated SD card with FAT file system and copied both the files MLO and app in root.

After safely ejecting SD card from PC i have plugged it in EVM board and turned it on.

There is not any messages appearing on UART on power up and even after some time.

Also there is no sign of execution of my program.

Below is the SYSBOOTSW status :

SYSBOOT[7:0] = 0001 0111

SYSBOOT[15:8] = 0100 0000

EVM board is in profile 2.

With same settings if I copy default files which were present in SD card when I purchased EVM board, I can see booting U-boot on UART and LCD is also displaying some icons.

As per my observation there is an issue with .bin files but I can not figure out what exactly is the issue.

Please help.

Thank you in advance.

  • The RTOS team have been notified. They will respond here.
  • Yash,

    I am assuming that you are using Processor SDK RTOS for your testing. Can you use the MLO prebuilt binary folder processor_sdk_rtos_am335x_4_0x_00_xx\prebuilt-sdcards\evmAM335x\sd_card_files and confirm they are booting on your board instead of using the Uboot binary files. UBoot and Linux kernel boot uses the boot mechanism from Processor SDK Linux.

    When you use the MLO from the Processor SDK RTOS, please check to confirm that you can see the UART logs on the EVM. Now, replace the app from the SDK with your app and see if still boots. This will confirm that your app is created correctly. Next, if the MLO from SDK and your app boots, then try your MLO with your app.

    The bootloader in PDK/starterware is similar to any userlevel code, it can be debugged by loading the .out over emulator to root cause the issues. Some common steps to debug boot issues are discussed in the debug section of the following wiki:
    processors.wiki.ti.com/.../AM437x

    Common mistakes that we have observed during booting are: COnfiguration of entry points in bootloader and application, memory overlap between app and bootloader, etc.

    Let us know the results from your debug and we will provide further guidance.

    Regards,
    Rahul
  • Hi Rahul,

    Thank you for your reply.
    But we are not using RTOS. We have changed starterware example C files.
    Solution provided is clearly for RTOS only. I can not even find folders you have mentioned in my Starterware setup.

    --
    Yash
  • Yash,

    We are no longer supporting the standalone starterware offering. We have incorporate the starterware bootloader in Processor SDK RTOS such that it can be used with bare-metal and RTOS applications. This is the same code base as starterware so you should pretty much be able to map this back to what we have in the Processor SDK RTOS.

    In starterware, the binaries at the location starterware\binary\bootloader\bin. My comments regarding the debug still stand, you need to help us understand if the secondary bootloader is causing this issue or the app boot.

    Regards,
    Rahul
  • Hi Rahul,

    My while program is developed on Starterware only.
    I need some time to migrate it to RTOS bare-metal as I don't have much idea about RTOS.

    I am studying RTOS on my own.
    But it will be helpful if you can provide some documents or links which can help me to understand RTOS better.

    Thank you for your support.

    --
    Yash