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/PROCESSOR-SDK-AM65X: SD card create issue

Part Number: PROCESSOR-SDK-AM65X

Tool/software: Linux

Hi,

I was successful in building linux image for am65xx-evm. Used MACHINE=am65xx-evm bitbake arago-base-tisdk-image. And all executable was found in /deploy/image/am65xx-evm folder.

I used this link for copying images to sd card. So I executed create-sdcard.sh as root.

But If I select Install prebuilt images , boot partition will populate with u-boot  and other files.

But if I give custom path it is not taking. In that execution itself it will show to give either directory or tar file. I am giving directory which contains following files.

arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.cpio
arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.cpio.xz
arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.manifest
arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.tar.xz
arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.tar.xz.md5
arago-base-tisdk-image-am65xx-evm-20190627052256.rootfs.wic.xz
arago-base-tisdk-image-am65xx-evm-20190627052256.testdata.json
arago-base-tisdk-image-am65xx-evm.cpio
arago-base-tisdk-image-am65xx-evm.cpio.xz
arago-base-tisdk-image-am65xx-evm.manifest
arago-base-tisdk-image-am65xx-evm.tar.xz
arago-base-tisdk-image-am65xx-evm.tar.xz.md5
arago-base-tisdk-image-am65xx-evm.testdata.json
arago-base-tisdk-image-am65xx-evm.wic.xz
bl31.bin
bl31.elf
bl32.bin
bl32.elf
Image
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-am65xx-evm-20190626115958.bin
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190626115958.dtb
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-csi2-ov490-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-oldi-lcd1evm-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-tc358876-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-gp-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-idk-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-idk-interposer-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-pcie-usb2-20190626115958.dtbo
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-pcie-usb3-20190626115958.dtbo
Image-am65xx-evm.bin
Image-k3-am654-base-board.dtb
Image-k3-am654-evm-csi2-ov490.dtbo
Image-k3-am654-evm-oldi-lcd1evm.dtbo
Image-k3-am654-evm-tc358876.dtbo
Image-k3-am654-gp.dtbo
Image-k3-am654-idk.dtbo
Image-k3-am654-idk-interposer.dtbo
Image-k3-am654-pcie-usb2.dtbo
Image-k3-am654-pcie-usb3.dtbo
k3-am654-base-board.dtb
k3-am654-evm-csi2-ov490.dtbo
k3-am654-evm-oldi-lcd1evm.dtbo
k3-am654-evm-tc358876.dtbo
k3-am654-gp.dtbo
k3-am654-idk.dtbo
k3-am654-idk-interposer.dtbo
k3-am654-pcie-usb2.dtbo
k3-am654-pcie-usb3.dtbo
modules--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-am65xx-evm-20190626115958.tgz
modules-am65xx-evm.tgz
sysfw-2019.02.itb
sysfw.itb
tiboot3-am65xx-evm-2018.01+gitAUTOINC+313dcd69c2-r30.tisdk1.bin
tiboot3-am65xx-evm.bin
tiboot3.bin
ti-sci-firmware-am65x-gp.bin
tispl.bin
tispl.bin-am65xx-evm
tispl.bin-am65xx-evm-2018.01+gitAUTOINC+313dcd69c2-r30.tisdk1
u-boot-am65xx-evm-2018.01+gitAUTOINC+313dcd69c2-r30.tisdk1.img
u-boot-am65xx-evm.img
u-boot.img
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190626115958.dtb
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-csi2-ov490-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-oldi-lcd1evm-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-evm-tc358876-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-gp-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-idk-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-idk-interposer-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-pcie-usb2-20190626115958.dtbo
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-pcie-usb3-20190626115958.dtbo
vmlinux.gz
vmlinux.gz--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-am65xx-evm-20190626115958.bin
vmlinux.gz-am65xx-evm.bin
vmlinux-k3-am654-base-board.dtb
vmlinux-k3-am654-evm-csi2-ov490.dtbo
vmlinux-k3-am654-evm-oldi-lcd1evm.dtbo
vmlinux-k3-am654-evm-tc358876.dtbo
vmlinux-k3-am654-gp.dtbo
vmlinux-k3-am654-idk.dtbo
vmlinux-k3-am654-idk-interposer.dtbo
vmlinux-k3-am654-pcie-usb2.dtbo
vmlinux-k3-am654-pcie-usb3.dtbo

But after excution I will get error like this.

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

    Copying files now... will take minutes

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

Copying boot partition
xz: /u/yocto/tisdk/build/arago-tmp-external-linaro-toolchain/deploy/images/am65xx-evm/: Is a directory, skipping
tar (child): /u/yocto/tisdk/build/arago-tmp-external-linaro-toolchain/deploy/images/am65xx-evm/: Cannot read: Is a directory
tar (child): At beginning of tape, quitting now
tar (child): Error is not recoverable: exiting now
xz: (stdin): File format not recognized
tar: Child returned status 2                                                                                                                   
tar: Error is not recoverable: exiting now
cp: cannot stat '/u/ti-pdk/bin/tmp/*': No such file or directory


Copying rootfs System partition
                                                                                                                                               

Syncing...
 file not found
Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190626115958.dtb copied
Image-k3-am654-base-board.dtb copied
k3-am654-base-board.dtb copied
vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190626115958.dtb copied
vmlinux-k3-am654-base-board.dtb copied
 
Un-mount the partitions
 
Remove created temp directories
 
Operation Finished

For U-boot :

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

  For U-boot and MLO

  If files are located in Tarball write complete path including the file name.
      e.x. $:  /home/user/MyCustomTars/boot.tar.xz

  If files are located in a directory write the directory path
      e.x. $: /ti-sdk/board-support/prebuilt-images/

  NOTE: Not all platforms will have an MLO file and this file can
        be ignored for platforms that do not support an MLO.

  Update: The proper location for the kernel image and device tree
          files have moved from the boot partition to the root filesystem.

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

Enter path for Boot Partition : /u/yocto/tisdk/build/arago-tmp-external-linaro-toolchain/deploy/images/am65xx-evm/

I gave directory.

 

Can you help me on this.

Thanks and Regards,

Vishnu

  • Hi team,

    The files

    sysfw,itb

    tispl.bin

    tiboot3.bin

    u-boot.img

    These files are should present in boot partition of sd card. But after building the images these are soft link to another file. Since the script will search for these files, will it fail because it is not actual file?

    I tried by changing name of the linked file to this name, but got failed.

    How can I copy these files using create-sdcard.sh

    Do I need to copy without script and modify the name ?

    Thanks and Regards,

    Vishnu

  • Hello Vishnu,

    The link you provided above does not exist and I am wondering if could you please share which create-sdcard.sh you are using.

    Regards,
    Krunal

  • Hello Vishnu,

    Please do not use the Yocto image directory as your custom path for the following purpose:

    a. In the create-sdcard.sh, the following line of code "ISBOOTTAR=`ls $BOOTUSERFILEPATH | grep .tar.xz | awk {'print $1'}`" checks for any tar-ball in the custom directory. Since the Yocto folder contains a bunch of tar-ball, it will execute the tar command on a directory and give an error "xz: /u/yocto/tisdk/build/arago-tmp-external-linaro-toolchain/deploy/images/am65xx-evm/: Is a directory, skipping"

    Solution: Copy the relevant boot images from the Yocto directory to another user created directory. 

    b. The Yocto folder creates multiple variations of the same name, for example: "MLO", "MLO-am57xx-evm" and "MLO-am57xx-evm-2018.01+gitAUTOINC+313dcd69c2-r30.tisdk1". The script will try to copy all the files into one file called MLO and that does not make any sense. By default, the script expects to find only one file named MLO. 

    Solution: Copy the relevant boot/rootfs images from the Yocto directory to another user created directory.

    Regards,
    Krunal

  • Hi Krunal,

    i tried with another directory as you told. Still I am facing the same issue.

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

        Copying files now... will take minutes

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

    Copying boot partition
    xz: /u/CustomPath/: Is a directory, skipping
    tar (child): /u/CustomPath/: Cannot read: Is a directory
    tar (child): At beginning of tape, quitting now
    tar (child): Error is not recoverable: exiting now
    xz: (stdin): File format not recognized
    tar: Child returned status 2                                                                                                                   
    tar: Error is not recoverable: exiting now
    cp: cannot stat '/u/ti-pdk/bin/tmp/*': No such file or directory


    Copying rootfs System partition
                                                                                                                                                   

    Syncing...
     file not found
    Image--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190704062459.dtb copied
    Image-k3-am654-base-board.dtb copied
    k3-am654-base-board.dtb copied
    vmlinux--4.14.79+git0+e669d52447-r0c.arago5.tisdk4.9-k3-am654-base-board-20190704062459.dtb copied
    vmlinux-k3-am654-base-board.dtb copied
     
    Un-mount the partitions
     
    Remove created temp directories
     
    Operation Finished

    I copied every images in /deploy/images/am65xx-evm to /u/CustomPath.

    But the same condition I  am facing. Boot partion images are not copying. Because I am give tarball for rootfs it is copying.

    Please help me in this.

    Thanks and Regards,

    Vishnu

  • Hello Vishnu,

    I am wondering if you have any tar-balls in your "/u/CustomPath/" folder. Personally, I recommend having two folders for boot and rootfs. In the boot folder, please copy all the appropriate images excluding any tar-balls. In the rootfs folder, please copy all the kernel/dtb images.

    Regards,
    Krunal

  • Hi krunal,

    I have copied all files in "/deploy/images/"  in yocto build. But still it is not taking those things.

    But rootfs is taking correctly.

    The files should be copied into boot partition are soft llinks to another files. Is this the issue for the script that is not taking and copying it.

    In prebuilt images directory they are not soft link file.

    Do I need to change soft link?

    From this guide it is mentioning to select target boards ( only for AM65xx ) but while running the script I am not getting this prompt.

    How to select the board before its runs.

    Thanks and Regards,

    Vishnu

  • Hello Vishnu,

    Please do not copy any soft links to the boot partition and it should contain the raw images. I am wondering if you could please share a picture of your "/u/CustomPath/" folder. Also, please ignore the "Select the Target Board [AM65x/DRA80xM Only]" section because it was only applicable to PSDK5.1. I have filed an internal ticket to update the section.

    Regards,
    Krunal