Tool/software:
Hello TI Team,
I’m working with the T3 Gemstone O1 (AM67A-based) board and trying to perform DFU (Device Firmware Upgrade) boot.
When I use the tiboot3.bin and tispl.bin from the official TI Processor SDK (09_02_00_05) along with my custom-built u-boot.img (from my own Yocto-based SDK), the DFU process works perfectly:
* DFU communication is established
* Files are transferred successfully
* Boot sequence proceeds normally
However, when I rebuild tiboot3.bin using my own SDK (based on meta-ti and meta-gemstone (our custom product) layers), DFU does not start — the device doesn’t enumerate properly or show up in dfu-util -l.
Here’s what I verified:
-
The
u-boot.imgbuilt from my SDK works fine with TI’s tiboot3.bin and tispl.bin.
I followed this: e2e.ti.com/.../processor-sdk-j722s-j722s-evm-name-unknown-in-dfu-util--l-when-dfu-mode
Here's what I used for tiboot3.bin and tispl.bin directory:
So it seems the problem is specific to my custom tiboot3.bin build.
There is a problem with my Yocto configuration when I look at the UART on Picocom.
When I send "tiboot3.bin" via dfu I got this message when control this with "sudo dfu-util -l"
dynamic-layers/meta-ti/recipes-bsp directory.”
Question:
What specific configuration or build flag in TI SDK’s tiboot3 build might be required to enable DFU functionality that could be missing in my custom build?
Thanks in advance!
— Akif Erdem