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.

AM335x SDK installation problem

Hello Everyone,

Yes, I realize this is for an older product. However, I am using the exact build specs on a native machine and this is broken.

Does any one know of a simple fix for this?

We built a dedicated Ubuntu 18 native machine just for this since it would not work well on our Ubuntu 22 stuff.

  • I understand you are trying to get AM335x SDK v6.3 setup. The documentation for that release at https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/AM335X/linux/Overview_Building_the_SDK.html says it should support Ubuntu 18.04, so it's a great start that this is what you setup. I suspect perhaps some newer packages got integrated over the Ubuntu 18.04 lifecycle with your 18.04.06 release, breaking the installation process.

    Can you try running the installer from the command line to see if this gives you additional context/logs for the error message?

    Similarly, it seems like the installer tries to invoke an executable called cg_xml_installer. Can you also start this manually (after the failed installation) with the parameters it shows in the error message, and see what it does? From the name it sounds like a sub-installer that provides meta-files for the TI toolchain ("cg" comes from "code gen" tools usually) is what's failing.

    Also just to check the obvious, you have sufficient RAM and disk space, right?

    Regards, Andreas

  • Hi Andreas,

    Here is another issue, this time with the yocto, my apologies for adding this, since we are already on Ubuntu 18 it seems some what relevant.

    fred@eng6:~/tisdk/build$ MACHINE=am335x-evm bitbake tisdk-base-image
    NOTE: Your conf/bblayers.conf has been automatically updated.
    NOTE: Your conf/bblayers.conf has been automatically updated.
    NOTE: Started PRServer with DBfile: /home/fred/tisdk/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 41699, PID: 28232
    WARNING: /home/fred/tisdk/sources/meta-arago/meta-arago-distro/recipes-core/meta/external-arm-secondary-sdk-toolchain.bb: Variable key PREFERRED_PROVIDER_binutils-cross-canadian-${TRANSLATED_TARGET_ARCH} (external-arm-sdk-toolchain-${TRANSLATED_TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_binutils-cross-canadian-invalid (external-arm-secondary-sdk-toolchain-${SECONDARY_TARGET_ARCH}).
    WARNING: /home/fred/tisdk/sources/meta-arago/meta-arago-distro/recipes-core/meta/external-arm-secondary-sdk-toolchain.bb: Variable key PREFERRED_PROVIDER_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} (external-arm-sdk-toolchain-${TRANSLATED_TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_gcc-cross-canadian-invalid (external-arm-secondary-sdk-toolchain-${SECONDARY_TARGET_ARCH}).
    Parsing recipes: 100% |##########################################| Time: 0:01:39
    Parsing of 2922 .bb files complete (0 cached, 2922 parsed). 4118 targets, 602 skipped, 0 masked, 0 errors.
    NOTE: Resolving any missing task queue dependencies
    
    Build Configuration:
    BB_VERSION           = "1.46.0"
    BUILD_SYS            = "x86_64-linux"
    NATIVELSBSTRING      = "ubuntu-18.04"
    TARGET_SYS           = "arm-linux-gnueabi"
    MACHINE              = "am335x-evm"
    DISTRO               = "arago"
    DISTRO_VERSION       = "2021.09"
    TUNE_FEATURES        = "arm armv7a vfp thumb neon callconvention-hard"
    TARGET_FPU           = "hard"
    meta-processor-sdk   = "HEAD:716008bc1003478d2e6c3e0c741f0fd80dcee5fb"
    meta-arago-distro    
    meta-arago-extras    = "HEAD:382ca36beb21a524de726bfd1c57e3d26f10cf82"
    meta-qt5             = "HEAD:6bfe29d9e8fdd5c2fd17c736814b6df859b3af50"
    meta-virtualization  = "HEAD:c5f61e547b90aa8058cf816f00902afed9c96f72"
    meta-networking      
    meta-python          
    meta-oe              
    meta-gnome           
    meta-filesystems     = "HEAD:0722ff6f021df91542b5efa1ff5b5f6269f66add"
    meta-ti              = "HEAD:facd5397cdc5c35c69e7a8e8f908a98a5c23d270"
    meta-arm             
    meta-arm-toolchain   = "HEAD:c4f04f3fb66f8f4365b08b553af8206372e90a63"
    meta                 = "HEAD:51844f2d60d77fb8cb46ffe460402f76ae216ca5"
    
    Initialising tasks: 100% |#######################################| Time: 0:00:02
    Sstate summary: Wanted 1302 Found 0 Missed 1302 Current 0 (0% match, 0% complete)
    NOTE: Executing Tasks
    WARNING: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Failed to fetch URL git://gitlab.gnome.org/GNOME/mobile-broadband-provider-info.git;protocol=https;branch=master, attempting MIRRORS if available
    ERROR: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Fetcher failure: Unable to find revision 90f3fe28aa25135b7e4a54a7816388913bfd4a2a in branch master even from upstream
    ERROR: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://gitlab.gnome.org/GNOME/mobile-broadband-provider-info.git;protocol=https;branch=master')
    ERROR: Logfile of failure stored in: /home/fred/tisdk/build/arago-tmp-external-arm-glibc/work/armv7at2hf-neon-linux-gnueabi/mobile-broadband-provider-info/1_20201225-r0/temp/log.do_fetch.7741
    ERROR: Task (/home/fred/tisdk/sources/oe-core/meta/recipes-connectivity/mobile-broadband-provider-info/mobile-broadband-provider-info_git.bb:do_fetch) failed with exit code '1'
    NOTE: Tasks Summary: Attempted 926 tasks of which 0 didn't need to be rerun and 1 failed.
    NOTE: Writing buildhistory
    NOTE: Writing buildhistory took: 4 seconds
    
    Summary: 1 task failed:
      /home/fred/tisdk/sources/oe-core/meta/recipes-connectivity/mobile-broadband-provider-info/mobile-broadband-provider-info_git.bb:do_fetch
    Summary: There were 3 WARNING messages shown.
    Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
    

    This is another one of the U 18 machines we set up for this, it only has 8G ram the other machine in the first post is 16G, both are 50G swap. Both machines are on empty 1TB drives since they were set up just for this application. Both are our retired servers that were retired and working, one is a Dell T20 and the other is Dell T110 II.

    When I get back to our other location I will try the CLI as you suggest.

    I will see if I can find the lower version of 18 and install that.

  • This is another one of the U 18 machines we set up for this, it only has 8G ram the other machine in the first post is 16G, both are 50G swap

    That should do the trick as long as you limit the number of threads. One typically budgets about 4GB of RAM for each Yocto build thread (BB_NUMBER_THREADS). 

    Also the issue with the mobile-broadband-provider package you ran into is well known, this E2E post here should help you get going: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1127637/processor-sdk-am437x-mobile-broadband-provider-fetcher-failure-in-clean-08-build/4185326#4185326

    On a related note you'll likely discover other issues similar like that. Usually (and unfortunately) those recipes "rot" in some way over time due to constant upstream changes such as branches getting renamed to use "inclusive language" (master -> main), or servers moving. Unfortunately the error messages Yocto emits in such cases can be misleading at times. So best is it to look at the failing recipe and see if you can manually clone the URL given there, check out the given branch (Yocto insists checking out the branch even if all it really needs is the commit ID which it could just check out). And double check Git commit ID is still there. But usually all those are easy to fix, see above link as an example.

    Regards, Andreas

  • Can you try running the installer from the command line to see if this gives you additional context/logs for the error message?

    Hello Andreas,

    Tried to run it and it does not launch.

  • Tried to run it and it does not launch.

    You need to be applying the command line parameters as well that were shown your previous error message.