• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 101 subscribers
  • Views 324 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

SK-AM69: Building the SDK with Yocto

SK-AM68: Cannot build tiboot3.bin or tiboot3_j721s2-hs-fs-evm.bin properly using yocto

Evan Williams
Intellectual 360 points
Part Number: SK-AM68

I have built and flashed an SD card with the yocto image, tisdk-default-image-j721s2-evm.rootfs.wic.

I can boot with the image if I use the tiboot3.bin or tiboot3_j721s2-hs-fs-evm.bin from the SD card that came with the devkit.

How can I build the tiboot3.bin correctly with yocto and make sure that it is properly populated in the wic image?

From the wic image I built, I renamed the tiboot3_j721s2-hs-fs-evm.bin to tiboot3.bin, but I get an error:

U-Boot SPL 2021.01-g62a9e51344 (Mar 01 2023 - 17:58:08 +0000)
ti_sci system-controller@44083000: Message not acknowledgedSYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.3-v08.06.03 (Chill Capybara')
EEPROM not available at 0x50, trying to read at 0x51

Thanks

  • 0
    TI__Expert 6025 points

    Doesn't look like the latest or correct version , based on u-boot log mentioned above. Try on 

    www.ti.com/.../PROCESSOR-SDK-AM68 9.1 release

  • 0 in reply to Praneeth Bajjuri
    Intellectual 360 points

    Hi Praneeth,

    Yes, using tiboot3-j721s2-hs-fs-evm.bin from the prebuilt directory of the SDK works.

    I'd prefer to automatically generate a wic image that has the correct tiboot3.bin using yocto. Is there any documentation or readme file surrounding that idea?

    I can see in the build directory ./u-boot-ti-staging/1_2023.04+gitAUTOINC+bd74e615a6-r0_psdkla_0_edgeai_2, (notice it's 2023.04, so should be new?), the symlink to tiboot3.bin is incorrect: tiboot3.bin -> ./tiboot3-j721s2-gp-evm.bin

    For sk-am68 it should be tiboot3-j721s2-hs-fs-evm.bin

  • +1 in reply to Evan Williams
    TI__Genius 9775 points

    Hi Evan,

    Evan Williams said:
    EEPROM not available at 0x50, trying to read at 0x51

    I've seen this issue in SDK 9.0. If you reset the board by pressing the blue button, after a few tries, it will boot. I haven't seen this issue in SDK 9.1.

    Evan Williams said:
    I'd prefer to automatically generate a wic image that has the correct tiboot3.bin using yocto. Is there any documentation or readme file surrounding that idea?

    You can do something similar to what is done within the tisdk-edgeai-image recipe. The first section would be what you'd put in the default recipe, but remove the :edgeai from the lines.

    # For AM68-SK, default tiboot3.bin should be HSFS
IMAGE_BOOT_FILES:remove:j721s2-evm:edgeai = "tiboot3.bin"
IMAGE_BOOT_FILES:append:j721s2-evm:edgeai = " tiboot3-j721s2-hs-fs-evm.bin;tiboot3.bin"

# For AM69-SK, default tiboot3.bin should be HSFS
IMAGE_BOOT_FILES:remove:j784s4-evm:edgeai = "tiboot3.bin"
IMAGE_BOOT_FILES:append:j784s4-evm:edgeai = " tiboot3-j784s4-hs-fs-evm.bin;tiboot3.bin"

# Package both HS-FS and gp binaries for Adas images
IMAGE_BOOT_FILES:append:j784s4-evm:adas = " tiboot3-j784s4-gp-evm.bin tiboot3-j784s4-hs-fs-evm.bin"
IMAGE_BOOT_FILES:append:j721s2-evm:adas = " tiboot3-j721s2-gp-evm.bin tiboot3-j721s2-hs-fs-evm.bin"

  • 0 in reply to Jared McArthur
    Intellectual 360 points

    Thanks Jared it's working!

    And thanks for pointing out the version difference! I was building the 9.0 SDK.

    I'm building with MACHINE=j721s2-evm and the tisdk-default-image, no branding.


    I found the root cause is these two lines in k3r5.inc
    SPL_BINARY = "tiboot3-${SYSFW_SOC}-${SYSFW_SUFFIX}-${SYSFW_CONFIG}.${SPL_SUFFIX}"
    SPL_SYMLINK = "tiboot3.${SPL_SUFFIX}"

    It overrides the k3r5 tiboot3.bin symlink to be the specific built version.

    For whatever reason, removing the image boot files didn't seem to make a difference.

    To fix it, seems like the u-boot.inc needs to use the correct symlink.
    File is included via u-boot-ti.inc into u-boot-ti-staging.

    I added a bbappend to u-boot-ti-staging:
    do_deploy:append:k3r5 () {
    ln -sf tiboot3-j721s2-hs-fs-evm.bin ${DEPLOYDIR}/${SPL_SYMLINK}
    }

  • 0 in reply to Evan Williams
    TI__Genius 9775 points

    Hi Evan,

    Ah, so did linking the tiboot3-j721s2-hs-fs-evm.bin to the tiboot3.bin result in an image with the hs-fs bin?

    If so, I will close the thread.

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Intellectual 360 points

    Yes, it has the correct bin now. Please feel free to close. Thanks!