Hi,
I am using a DM8168EVM and I am not able to access the targetfs [ Location: /home/user/targetfs] from the target [ DM8168-evm].
I have gone through the forum queries and nothing has helped me resolve this.
Could anybody suggest a workaround?
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.
Hi,
I am using a DM8168EVM and I am not able to access the targetfs [ Location: /home/user/targetfs] from the target [ DM8168-evm].
I have gone through the forum queries and nothing has helped me resolve this.
Could anybody suggest a workaround?
Hi Sanjay Sanju,
Could you provide a little more of background on your issue? I think I didn't get your question. Have you tried with the Ridgerun EVAL SDK?
https://developer.ridgerun.com/wiki/index.php/Getting_Started_Guide_for_DM8168_EVM
http://ridgerun.com/www/index.php/download-center.html
-David
Hello David,
I am not using the ridgerun EVAL SDK, instead I am using the EZSDK provided by TI. I have tried using the version ti-dm816x_evm-5_05_01_04 and ti-dm816x_evm-5_05_02_00.
I am following the procedure step by step while trying to see the targetfs from the target [ DM8168 ], however I am not successful.
Kindly advice.
Hi Sanjay,
I would recommend you to try to configure the EZSDK to boot from an SD card, you can find instructions about how to do it here:
http://processors.wiki.ti.com/index.php/EZSDK_Using_data_on_SD_and_filesystem_on_NAND
Also there are some tutorials on line about using the EZSDK: http://www.fedevel.com/welldoneblog/2011/10/starting-with-ti-exsdk-c6a816x-video-tutorial/
In general, you can find the filesystem of the EZSDK on /home/$USER/ti-ezsdk_dm816x-evm_5_05_02_00/filesystem/ezsdk-dm816x-evm-rootfs.tar.gz
Also, the Ridgerun SDK is already integrated with the EZSDK, the eval should work if you following step by step this guide: https://developer.ridgerun.com/wiki/index.php/Getting_Started_Guide_for_DM8168_EVM
-David
Also, I don't know why your EZSDK is not creating your filesystem directory, but you can check in your uboot environment where is the board looking for the filesystem, from uboot, stop the countdown and type printenv, it should show you bootargs, something like:
bootargs=console=ttyO2,115200n8 notifyk.vpssm3_sva=0xBF900000 root=/dev/mmcblk0p2 rootdelay=2 rootfstype=ext4 mem=364M@0x80000000 mem=320M@0x9FC00000 vmalloc=512M vram=81M
Hello David,
When I stop the countdown from u-boot and type printenv, The following output is seen.
bootcmd=if mmc rescan 0; then if run loadbootscript; then run bootscript; else echo In case ENV on MMC/SD is required; echo P lease put a valid script named boot.scr on the card; echo Refer to the User Guide on how to generate the image; fi; else echo
Please set bootargs and bootcmd before booting the kernel; echo If that has already been done please ignore this message; fi
bootdelay=3
baudrate=115200
autoload=no
verify=yes
bootfile=uImage
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 0 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}
ethaddr=00:18:31:e6:e0:dc
ethact=DaVinci EMAC
ver=U-Boot 2010.06 (Oct 10 2012 - 02:01:22)
Environment size: 742/8188 bytes
These lines were missing on the previous post!
I do not see anything similar to what you mentioned in your post in the response what I get on the console. What should be inferred from this? Kindly advice.
Hi Sanjay,
You don't see those lines because in your case, uboot will run the instructions present in the bootcmd variable which at some point runs
fatload mmc 0 ${script_addr} boot.scr
this part will load the definitions from the boot.scr file present in your SD card (http://processors.wiki.ti.com/index.php/DM816x_AM389x_PSP_U-Boot#ENV_on_SD_card_using_a_script) which should contain something like:
bootargs=console=ttyO2,115200n8 notifyk.vpssm3_sva=0xBF900000 root=/dev/mmcblk0p2 rootdelay=2 rootfstype=ext4 mem=364M@0x80000000 mem=320M@0x9FC00000 vmalloc=512M vram=81M
I just found this video that might help you too https://www.youtube.com/watch?v=FahIFEpvtPw