TMDSEVM572X: Please tell me the detailed usage of the boot sample of AM5728.

Hi,

Which version of SDK are you using?
Also, are you not getting any logs at all, not even from the SBL? If you are using pre-built SBL, you should be able to see some logs on UART. If that is not the case, there might be something wrong with the setup, please double check the following:

1) The UART cable is proper and it is attached properly.
2) The boot mode is set to UART mode. Please refer to the user guide https://www.tij.co.jp/jp/lit/ug/spruig1/spruig1.pdf?ts=1658128371501&ref_url=https%253A%252F%252Fwww.google.com%252F  for boot mode options.
You can also try booting Linux to confirm the setup.

Regards,
Parth

Hello Parth Nagpal,

Which version of SDK are you using?
->The SDK version is "08.01.00.09".

1) The UART cable is proper and it is attached properly.
->I tried the sample "UART_BasicExample_evmAM572x_armExampleProject", so the UART cable is fine.

2) The boot mode is set to UART mode.
->I put it in UART mode, but nothing worked.


When J3, J4, J6 were all set on the Pin1-2 side, something was output from the UART.
However, the output data does not seem to change regardless of whether the SD card is inserted or not.
What should I look for next?

By the way, should I save the data (app, MLO) in the root folder of the SD card?

Regards,
MTS OS

Hi,

Parth Nagpal said:

The boot mode is set to UART mode.

Sorry that's a typo. Please make sure boot mode is set to SD boot. You can refer to the user guide for details.

MTS OS said:

By the way, should I save the data (app, MLO) in the root folder of the SD card?

No, that should be in boot partition. You can see the how SD card creation guide https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_00_00_07/linux/Overview_Getting_Started_Guide.html#linux-sd-card-creation-guide 

Also, are you using pre-built MLO image or have you changed anything?

Regards,
Parth 

Hello Parth Nagpal,

Also, are you using pre-built MLO image or have you changed anything?
-> Not changed. Keeping the SDK defaults, I created the MLO file by running the make command. ("7.make all_sbl_images SBL_PLATFORM = am57xx" in the first post)


You're talking about Linux-SDK, can I do the same with RTOS-SDK?

I use a Windows PC. So I looked at the Windows guide.
software-dl.ti.com/.../index_overview.html

I wrote sd_image.img to the SD card with Win32 Disk Imager.(Fully formatted with SD card formatter in advance)

But how do I write the MLO and app files after writing sd_image.img?
Windows PC is told to "format" the SD card and can't write MLO and app files.

Regards,
MTS OS

Hi MTS,

Can you please try with the pre-built MLO that comes with the SDK?

MTS OS said:

You're talking about Linux-SDK, can I do the same with RTOS-SDK?

You can create the SD card using the scripts in linux SDK and then copy MLO and app in boot partition.

I have not tried it on windows PC, but you should have an option to skip the "format" in windows.

Have you verified the boot config settings?

Regards,
Parth

Hello Parth Nagpal,

sorry.
I took a lot of time to prepare my Linux PC (Ubuntu 18.04).

Have you verified the boot config settings?
->I used to say that when I turned on the power, something was output to UART, but it seems that I was in UART mode by mistake. I reconfirmed it again and put it in SD boot mode.
The result is not booting. Probably because the SD card is not ready.

I have installed RTOS-SDK for Linux on my Linux PC.
Then I ran the following command from my home directory:
software-dl.ti.com/.../index_overview.html
　>1.1.12.3. Creating an SD card

sudo ./processor_sdk_rtos_am57xx_08_01_00_09/processor_sdk_rtos_am57xx_08_01_00_09/bin/create-sdcard.sh ./processor_sdk_rtos_am57xx_08_01_00_09/processor_sdk_rtos_am57xx_08_01_00_09/prebuilt-sdcards/evmAM572x/sd_card_files/

MLO and app files were written to the SD card(8GB).

However, it seems that the partition of the SD card has not been set.
The capacity of the SD card remained at 8GB.
I used this SD card for the EVM board, but after all I couldn't boot SD.

Do you know why partitioning failed?

Regards,
MTS OS

Hi MTS,

MTS OS said:

MLO and app files were written to the SD card(8GB).

Did you replace the pre-written binaries in SD card with the binaries from PDK?

Regards,
Parth

Hello Parth Nagpal,

I'm sorry I didn't tell you this either.
I want to boot using another SD card instead of the one that came with the EVM board(TMDSEVM572X).

The SD card is fully formatted.
When I prepared the RTOS-SDK for Linux and executed the following command, the MLO and app files were written to the formatted and empty SD card.

sudo ./processor_sdk_rtos_am57xx_08_01_00_09/processor_sdk_rtos_am57xx_08_01_00_09/bin/create-sdcard.sh ./processor_sdk_rtos_am57xx_08_01_00_09/processor_sdk_rtos_am57xx_08_01_00_09/prebuilt-sdcards/evmAM572x/sd_card_files/

Do I need to use the Linux-SDK method because the RTOS-SDK method is incorrect?

Regards,
MTS OS

Hi MTS,

Parth Nagpal said:

Did you replace the pre-written binaries in SD card with the binaries from PDK?

I am referring to the step 2 of section 4.6.3.2.5.1.1. Preparing the SD card in the document https://software-dl.ti.com/processor-sdk-rtos/esd/AM57X/08_01_00_09/exports/docs/rtos/index_Foundational_Components.html?highlight=sbl#preparing-the-sd-card 

Did you do this step?

Regards,
Parth

Hello Parth Nagpal,

Did you do this step?
->No. I seem to be stumbling in step1.

For Windows
I unzipped "[SDK INSTALL DIR]\ prebuilt-sdcards \ evmAM572x \ sd_card_img \ sd_card.img.gz" to get sd_card.img.
I wrote sd_card.img to the SD card with Win32 Disk Imager.
However, using this SD card to a PC does not read it in FAT32 format.
WindowsPC says "formatting is required" and the file system does not work.
And, I used this SD card for a Linux PC and the file system didn't boot.

For Linux
I'm sorry to repeat.
I saw "1.1.12.3. Creating an SD card" and ran the following command:
"sudo [SDK INSTALL DIR] /bin/create-sdcard.sh [SDK INSTALL DIR] /prebuilt-sdcards/ [EVM DIR] / sd_card_files /"
And MLO and app file are copied to the SD card. However, the SD card does not have a volume of 1GB. Probably the partitioning has failed.
Just in case, paste the log of create-sdcard.sh.

################################################################################

This script will create a bootable SD card from custom or pre-built binaries.

The script must be run with root permissions and from the bin directory of
the SDK

Example:
 $ sudo ./create-sdcard.sh path/to/sdcard/files

Formatting can be skipped if the SD card is already formatted and
partitioned properly.

################################################################################


Available Drives to write images to: 

#  major   minor    size   name 
1:   8       16    7761920 sdb
 
Enter Device Number or n to exit: 1
 
sdb was selected

/dev/sdb is an sdx device
Unmounting the sdb drives
 unmounted /dev/sdb1
 unmounted /dev/sdb
umount: /dev/sdb: not mounted.
Current size of sdb1 7757824 bytes

################################################################################

		Now erasing partition table

################################################################################

1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 5.30174 s, 198 kB/s

################################################################################

		Partitioning Boot

################################################################################
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
attribute "partition" not found
 
Mount the partitions 
 
Emptying partitions 
 

Syncing....

################################################################################

	Copying files now... will take minutes

################################################################################

Copying boot partition



Syncing...
 
Un-mount the partitions 
 
Remove created temp directories 
 
Operation Finished

Regards,
MTS OS

Hi MTS,

MTS OS said:

Do I need to use the Linux-SDK method because the RTOS-SDK method is incorrect?

For now you can try using Linux-SDK method. Meanwhile, I'll verify the RTOS-SDK method and see if it is working fine on my end.

Regards,
Parth

Hi MTS,

I tried RTOS-SDK create SD Card script on my end and it is working fine.

I have a few queries here:
1) Are you trying this on TI-EVM or is it a custom board?
2) Did you check that the UART cable is connected correctly? Are you able to see any logs on serial console at all with any other method? May be try booting linux and see.

MTS OS said:

However, the SD card does not have a volume of 1GB.

3) Your logs seems to be fine. Why there should be a volume of 1GB? This script will take up the entire SD-Card and create a single boot volume with FAT partition.

Regards,
Parth

Hello Parth Nagpal,

Thank you for your confirmation.

Are you trying this on TI-EVM or is it a custom board?
-> I'm trying with TI-EVM.

Did you check that the UART cable is connected correctly?
->Yes. I have confirmed that Linux boots with the SD card that came with the board.

Why there should be a volume of 1GB?
->I think that the SD card will automatically become 1GB volume when preparing for SD boot.
The guide says that you have to use an SD card of 1GB or more, and that when I prepare for SD boot, the SD card will have a capacity of 1GB.

1.1.11.3.2.1. Limitations to the WinDisk32 SD card utility and alternate options
While, this utility formats the SD card in FAT format recognized by all the ROM bootloader supported on Sitara and K2G devices, it limits the storage capacity of larger volume SD cards to 1 GB volume.

I tried different SD cards and they all gave the same results. If the logs are okay, I'm sure the procedure is wrong, but what am I doing wrong?

Regards,
MTS OS

Hi MTS,

MTS OS said:

1.1.11.3.2.1. Limitations to the WinDisk32 SD card utility and alternate options
While, this utility formats the SD card in FAT format recognized by all the ROM bootloader supported on Sitara and K2G devices, it limits the storage capacity of larger volume SD cards to 1 GB volume.

Yes, but this is the case when you are using WinDisk32 on windows. But now you are trying on a Linux machine right?

Can you try the following MLO on your end and see if it works. MLO

Regards,
Parth