Other Parts Discussed in Thread: TMDSEVM572X
Tool/software: Linux
Dear team,
There is difference in the images flashed into uSD card shipped along with EVM TMDSEVM572X), when compared with the filesystem tar ball (arago*.tar.xz and tisdk*.tar.xz from the installation of PROCESSOR-SDK-LINUX-AM57X) differences I figured out is
1) Boot animation appears booting through the images pre-built/flashed on uSD card, this will not happen in case of using filesystem tar files provided along with the SDK installation
2) dd command is more stripped down
3) copying a file to /dev/null works fine on the images pre-built/flashed on uSD card, the same will case error "No space left on the device" when its done using the filesystem tar files provided along with the SDK installation
I do not understand why all these complexities created by TI (working with OMAP2/3/5 was very smooth), please help answering for my queries above.
=> I would like to replicate the same functionality as that of images pre-built/flashed on uSD card, by building all the images (bootloaders, kernel and filesystem) building from the source provided through SDK.
Instead of using the pre-built filesystem tar files, I wish to build the customized filesystem, please give your inputs to start with.
