• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 1269 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/AM5728: Which Yocto output files get programmed into SD card

Doug Abramson
Prodigy 20 points

Part Number: AM5728

Tool/software: Linux

This is for the AM57xx-evm.  I'm kind of new at this whole embedded Linux thing so bear with me.  I've built a Linux Kernel/RootFS via Yocto/Arago.  In the output directory (/tisdk/build/arago-tmp-external-linaro-toolchain/deploy/images/am57xx-evm) there's a ton of files.  This is my first crack at doing this for the EVM, so I just want enough stuff to show the Linux prompt.  I've also loaded and ran the create-sd card utility from the SDK, but it doesn't really walk you though the process.  

It's not clear which files I need to load to get to that point.  I know I need a preloader (spl?  mlo?) then U-boot, then the kernel, then rootfs.  Is there a little table that shows what files go to what partition and how it's formated (ext3, fat, etc).  I feel like I don't really even need a utility to do this as long as I know what files go into what partition.  

I'm perfectly happy with a pointer to the right piece of documentation also. 

Anyway, here's what came out of yocto.

tisdk-rootfs-image-am57xx-evm-20170825124133.rootfs.tar.xz
modules--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-20170823182502.tgz
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-20170823182502.bin
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-20170823182502.bin
u-boot-am57xx-evm-2017.01+gitAUTOINC+590c7d7fe1-r12.img
MLO-am57xx-evm-2017.01+gitAUTOINC+590c7d7fe1-r12
u-boot-spl.bin-am57xx-evm-2017.01+gitAUTOINC+590c7d7fe1-r12
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-lcd-osd101t2045-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-lcd-osd101t2587-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-lcd-osd101t2045-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-lcd-osd101t2587-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-cam-ov10635-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-cam-ov10635-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-cam-mt9t111-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-cam-mt9t111-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-cam-ov10635-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-cam-ov10635-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-cam-mt9t111-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-cam-mt9t111-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-reva3-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am572x-idk-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-evm-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-beagle-x15-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-beagle-x15-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-beagle-x15-revb1-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am57xx-beagle-x15-revb1-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-lcd-osd101t2045-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-lcd-osd101t2587-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-lcd-osd101t2045-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-lcd-osd101t2587-20170823182502.dtb
uImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-20170823182502.dtb
zImage--4.9.41+git0+7448cce4e5-r7c.arago5.2-am571x-idk-20170823182502.dtb
tisdk-rootfs-image-am57xx-evm-20170825124133.rootfs.manifest
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt

Thanks!

Doug

  • 0
    TI__Guru**** 161600 points
    Hi Doug,

    MLO & u-boot.img go into the boot partition of the sd card.
    If you check tisdk-rootfs-image-am57xx-evm-20170825124133.rootfs.tar.xz, you should see that the dtb files & the zImage are located in the /boot folder, so you just need to extract this file to the rootfs partition of the sd card.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Prodigy 20 points

    Thanks Yordan.  

    I think I'm feeling kind of stupid here.  In my admittedly limited experience with this stuff, the SD card usually has a few different partitions.  There's the boot partition, which has in our case MLO and UBOOT.  This is a FAT32 partition.  Then there's a partition that contains the kernel and the ROOTFS.  Which files correspond to that and what's the format of the partition they go in.  Isn't it something like EXT3, or something to that effect?  Is there some table that just shows this?  Thanks for any clarification.  I'll keep fighting with this.

    D. 

  • 0 in reply to Doug Abramson
    Expert 2020 points
    Hi Doug,

    You are on the right track of understanding. Just to clarify, as Yordan mentioned, the rootfs.tar will have the boot images along with rootfs.
    The general design of sdcard/Nand partition is as follows :
    1) Boot partition - Contains MLO, uboot and Kernel images along with dtb's. Its generally a FAT partition along with boot flag enabled.
    2) Rootfs partition - This contains the standard filesystem created along the lines of File System Hierarchy(FSH), which includes system binaries, services, scripts, device files and end user application. The type of file system here can be really varied. For example sdcard can have ext3 and NAND can have UBIFS, JFFS, JFFS2, XFS and many more.

    I hope I could clear your doubts.

    Thanks,
    Prabhuraj
    BlackPepper Technologies