Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG
Tool/software:
Hello,
We are currently testing a CAN-based SBL bootloader on the AWRL6432 ES1.0 board.
Progress
-
Using CAN communication, the SBL successfully receives the application image, writes it to QSPI Flash, and completes CRC verification.
-
In the CCS Load/Run environment, the SBL operates correctly and is able to execute the application image stored in QSPI Flash.
-
However, after flashing the SBL to partition 1 (0x0) and the application image to partition 4 (0x0010_0000) using UniFlash, upon power reset there is no UART log output and no CAN response. The device fails to boot.
Observations
-
CAN-based image reception, Flash programming, and CRC/header verification are all successful.
-
The image size is ≥ 8KB and not a multiple of 2KB (Errata condition avoided).
-
Linker and SysConfig settings are consistent with TI examples.
-
CCS environment works correctly → The issue seems to occur specifically in the “ROM → QSPI → SBL” cold boot path.
Suspected Cause
-
According to the TI Errata, AWRL6432 ES1.0 has unstable or unsupported QSPI boot.
-
As a result, the ROM is unable to reliably load the SBL from QSPI during the boot process.
-
Therefore, while CAN-based image download and Flash programming work fine, after power reset the cold boot via QSPI does not function.
Questions
-
On the ES1.0 board, is it correct that SBL can only be executed via CCS Load/Run or UART boot, rather than QSPI cold boot?
-
Has there been any internal case or example where QSPI boot on ES1.0 functioned correctly?
