• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 321 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DRA80M: Booting from eMMC questions/clarifications

Barend Ungrodt
Intellectual 1420 points

Part Number: DRA80M

Hi Processors Team,

My customer has followed the below links in order to flash the u-boot to eMMC.

Booting from eMMC to u-boot is working fine, but my customer has some questions/needs some clarification.

  1. To copy the filesystem they will be using the RootFS available in the SDK, i.e tisdk-docker-rootfs-image-am65xx-evm.tar.xz. When they scan the drive, they can only see only one partition that has been created. Is this the partition where they need to copy the RootFS?

   If the answer is yes, then they are unable to mount the drive to check the contents due to the following errors.


 

They thought is that they are getting this error since the drive is a GPT type partition.

To fix this, and continue with the configuration, will either below command work?

 root@am65xx-evm:~# dd if=/home/root/tisdk-docker-rootfs-image-am65xx-evm.tar.xz of=/dev/mmcblk0p1 bs=1M && sync

or

root@am65xx-evm:~# dd if=/home/root/tisdk-docker-rootfs-image-am65xx-evm.ext4 of=/dev/mmcblk0p1 bs=1M && sync

 

2. How can they modify/change the bootloader images that they have flashed through u-boot from the kernel space?

The device they are using is the DRA804M(AM6548x) and are on version 06_00_00_07 of the SDK.

Let me know if you need any more details!

Thanks,
Barend

  • 0
    TI__Guru** 113800 points

    Hi Barend,

    1) Has the customer attempted to use the tisdk-rootfs-image-am65xx-evm.tar.xz and do they see the same results?

    2) You can access the bootloader images from user space via /run/media/<device>.

    Let me know if that helped.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Intellectual 1420 points

    Hi Karthik,

    Here are the answers/clarifications from the customers. Let me know what the next steps are.

    1)      Have you tried using tisdk-rootfs-image-am65xx-evm.tar.xz, and if so, do you see the same results?

    A : To boot the kernel, u-boot needs to find the corresponding files/images from the /boot/ folder of the rootFS partition. In order that to happen, I need to extract the files from the tidsk-rootfs and store the file contents to the rootFS partition. Currently I am not able to load any type of tisdk-rootfs files to the rootFS partition as its not visible from user space.

    2)      You can access the bootloader images from user space via /run/media/<device>, let me know if this works

    A : I can only see the bootloader partition created in SD card not in but not in eMMC as eMMC partition is not getting mounted. PFA.

     You can see this is the eMMC partition that I am getting which i created while following the SDK commands. PFA.

    Thanks,
    Barend

  • 0 in reply to Barend Ungrodt
    TI__Guru** 113800 points

    Hi All,

    Posting an update here that there are some discussions happening in parallel over emails and I will summarize the thread at an appropriate time.

    The thread remains open until we close the discussions.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Guru** 113800 points

    Offline discussions are still happening. This thread will get an update after the discussions are completed.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Guru** 113800 points

    Barend,

    I will keep this thread open for one more week before closing it out. Lets try to summarize before that.

    Regards

    Karthik