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.

AM3874 root filesystem

Other Parts Discussed in Thread: AM3874, LINUXEZSDK-DAVINCI, TMS320DM8148, LINUXEZSDK-SITARA

Hi,

We're using the root filesystem from the ti-ezsdk_dm814x-evm_5_04_00_11 for our custom am3874 board.The exact file is 'ezsdk-dm814x-evm-rootfs.tar.gz' from 'filesystem' directory. I would like to be able to generate this set of files from sources. For that I'm following the steps from the link:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/131398.aspx

I'm using

$ MACHINE=dm814x-evm bitbake arago-console-image

but I think there is something wrong with these recipes because they are using linux-2.6.31 for instance. How do you generate this rootfilesystem in order to get the OpenGL ES packages, video firmwares and controllers and so on...

Regards,

Jorge

  • Jorge,

    First of all there are two filesystems available in the EZSDK:

    1. EZSDK filesystem - {EZSDK}/filesystem/ezsdk-dm814x-evm-rootfs.tar.gz

    2. ARAGO base filesystem - {EZSDK}/filesystem/arago-base-tisdk-image-dm814x-evm

    Please refer to the below links for more details:

    http://processors.wiki.ti.com/index.php/EZSDK_Filesystems

    http://processors.wiki.ti.com/index.php/EZ_SDK_FAQ

    http://processors.wiki.ti.com/index.php/Installing_gstreamer_on_Root_File_System_built_using_Arago

    http://e2e.ti.com/support/embedded/linux/f/354/t/7660.aspx

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/t/127951.aspx

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/200046.aspx

    http://e2e.ti.com/support/embedded/linux/f/354/t/180096.aspx

    Regards,
    Pavel

  • Hi Pavel,

    I'm back to AM3874. I've found that on OMAP5 that I can generate a complete rootfs with:

    $ MACHINE=omap5-evm bitbake arago-glsdk-multimedia-image

    and the SDK with:

    $ MACHINE=omap5-evm bitbake arago-core-tisdk-image

    With the last one, I get the script 'arago-2013.10-cortexa15-linux-gnueabi-tisdk.sh' which deploy the linux-devkit
    directory for OMAP5 used to compile our own projects against the headers of the project installed in the rootfs.

    On AM3874 the best approach I've found is

    MACHINE=dm814x-evm bitbake arago-tisdk-image

    which builds a more complete image with gstreamer but nothing related to TI, like the OpenGL ES components. The links speaking about EZSDK are interesting but nothing about how to generate it. I'm very interested to know how you built the ezsdk-dm814x-evm-rootfs.tar.gz with all the components AND, the more important thing, the linux-devkit directory in the ti-ezsdk_dm814x-evm_5_05_02_00 because is the base directory to use to compile our own projects.

    Are there more info how to generate the 'ezsdk-dm814x-evm-rootfs.tar.gz' image and the SDK (the 'linux-devkit' directory) like in the OMAP5??

    Regards,

    Jorge

  • Jorge,

    Jorge Fernandez said:
    The links speaking about EZSDK are interesting but nothing about how to generate it. I'm very interested to know how you built the ezsdk-dm814x-evm-rootfs.tar.gz with all the components

    You can not build full EZSDK (ezsdk-dm814x-evm-rootfs.tar.gz) from scratch. I do not build EZSDK filesystem, I am using the EZSDK installer (ezsdk_dm814x-evm_5_04_00_11_setuplinux) than the mksdboot.sh script to install the EZSDK filesystem on the /media/ROOTFS partition of the SD card or setup-targetfs-nfs.sh script to install the EZSDK filesystem in my home directory.

    http://processors.wiki.ti.com/index.php/EZSDK_Filesystems#Building_your_own_filesystem

    The EZSDK does not ship with a System Builder that allows you to build/customize a filesystem from scratch.

    You could use the following options to build/customize by hand.

    1. Start with the Arago Base Filesystem and add TI software and your application software. The EZSDK's toplevel Makefile supports make install of TI libraries and programs.
    2. Start with the EZSDK Filesystem, remove software that you will not use and add your application software. This is more challenging that the previous option as you would need to be careful about not breaking dependencies.
    3. Create a filesystem from scratch. The EZSDK filesystem is built from the Arago Project and therefore, this is a good starting point. Note that this is more challenging that the first option as well and requires good understanding of Linux and OpenEmbedded.

    http://processors.wiki.ti.com/index.php/Category:EZSDK_Software_BOM

    http://processors.wiki.ti.com/index.php/EZSDK_5.04.00_DM814x_Software_BOM

    http://processors.wiki.ti.com/index.php/Upgrading_Graphics_SDK_in_EZSDK

    Regards,
    Pavel

     

  • Hi,

    Pavel Botev said:

    You can not build full EZSDK (ezsdk-dm814x-evm-rootfs.tar.gz) from scratch. I do not build EZSDK filesystem, I am using the EZSDK installer (ezsdk_dm814x-evm_5_04_00_11_setuplinux) than the mksdboot.sh script to install the EZSDK filesystem on the /media/ROOTFS partition of the SD card or setup-targetfs-nfs.sh script to install the EZSDK filesystem in my home directory.

    Really?? How do you release a new version? How do you maintain on sync the linux-devkit with the binaries from the release? How the linux.devkit directory is generated?

    I've found a post in this link http://e2e.ti.com/support/embedded/linux/f/354/t/159086.aspx from Siddharth Heroor who tells about a git repository to generate the EZSDK.

    Sorry for insisting in this topic but I thought it was unified the building process for the amsdk, glsdk, and the other filesystems. The automatic generation is an important feature to easy the deploy of neww release to avoid breaking the building process of our custom projects.

    Thanks,

    Jorge

  • Jorge,

    There will be no new version for AM387x EZSDK. The last one is 5.04.00.11.

    Regards,
    Pavel

  • I think that's not correct... I'm using the ti-ezsdk_dm814x-evm_5_05_02_00 !

    What it means your sentence?? The AM387x is deprecated? No more bug or features will be added??

    Regards,

    Jorge

  • Jorge,

    Jorge Fernandez said:
    I think that's not correct... I'm using the ti-ezsdk_dm814x-evm_5_05_02_00 !

    EZSDK 5.05.02.00 is only for DM814x/DM816x devices:

     http://www.ti.com/product/tms320dm8148 -> http://www.ti.com/tool/linuxezsdk-davinci -> http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

    While for AM387x/AM389x devices:

    http://www.ti.com/product/am3874 -> http://www.ti.com/tool/linuxezsdk-sitara -> http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/5_04_00_11/index_FDS.html

    Regards,
    Pavel

  • For AM38xx (both AM389x and AM387x) devices, we are no longer validating our AM devices on new EZSDKs...the last one was 5.04. So you need to use the EZSDK 5.04

    Regards,
    Pavel

  • It's a little messy all about... In the http://downloads.ti.com/dsps/dsps_public_sw/ezsdk/latest/exports/ezsdk_5_05_02_00_dm814x_Release_Notes.pdf you can read sentences about DM814x/AM387x EVM...

    Well, then no more software updates are expected for the AM3874, isn't it? Is it the software end of life of the AM3874

    Regards,

    Jorge

  • Jorge,

    Jorge Fernandez said:
    It's a little messy all about... In the http://downloads.ti.com/dsps/dsps_public_sw/ezsdk/latest/exports/ezsdk_5_05_02_00_dm814x_Release_Notes.pdf you can read sentences about DM814x/AM387x EVM...

    The DM814x/AM387x EVM has DM8148 processor:

    http://www.ti.com/tool/tmdxevm8148

    DM8148 Processor (emulates AM3874)

    Jorge Fernandez said:
    Well, then no more software updates are expected for the AM3874, isn't it? Is it the software end of life of the AM3874

    The EZSDK will be no more validated with AM387x device. The last validated version of the EZSDK is 5.04. But I think this does not prevent you to check the new features and bugs fixed in the next versions of the EZSDK (5.05) and apply these to the AM387x EZSDK 5.04 (if applicable of course).

    I mean you can not use the newest EZSDK (5.05)  for AM387x device, but use 5.04 and apply on top of it all you find useful for AM387x device from the next EZSDK versions (5.05).

    Regards,
    Pavel

  • Pavel Botev said:

    The EZSDK will be no more validated with AM387x device. The last validated version of the EZSDK is 5.04. But I think this does not prevent you to check the new features and bugs fixed in the next versions of the EZSDK (5.05) and apply these to the AM387x EZSDK 5.04 (if applicable of course).

    I mean you can not use the newest EZSDK (5.05)  for AM387x device, but use 5.04 and apply on top of it all you find useful for AM387x device from the next EZSDK versions (5.05).

    Ok, I get it... If I want the bugs solved or the new features added I'll have to do the TI work... I suppose that's what's happens when you have a big portfolio of cpus and only the best sellers are supported (nothing to regret!) Thanks we have the source code for some components, but firmwares and graphics libraries are a handicap...


    Well, thanks for your answers!

    Jorge

  • Jorge,

    just a little note, we also have our 3rd party partners that could help you in case you need extra help.