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.
Hi expert,
Customer reported issue on SBL code in mmwave SDK 5.3.0.2. Because the debug configuration for SBL is not work, it is suggested to use release configuration.
Default SBL works well on EVM but we found if add McSPI into syscfg SBL failed to boot the application. If we change the optimization option from -Os to -O0 then SBL works again.
Please help to check below information and let us know your suggestion. Thank you.
The test bench is
EVM: 6432 ES1.0
SDK: 5.3.0.2
SBL project: C:\ti\MMWAVE_L_SDK_05_03_00_02\examples\drivers\boot\sbl\xwrL64xx-evm
Uniflash
Meta Image 1: sbl.Release.appimage
Meta Image 4: C:\ti\MMWAVE_L_SDK_05_03_00_02\examples\mmw_demo\mmwave_demo\prebuilt_binaries\xwrL64xx\mmwave_demo.release.appimage
With -Os and McSPI added, SBL failed to boot image
**********************************************
Secondary Bootloader Application Start
**********************************************
Press CR key or Space key to stop auto boot and Update Meta Image...
Loading existing Meta Image from Flash in 10 9 8 7 6 5 4 3 2 1
Booting the Application.
No Valid application found. Booting backup factory default image...
No Valid Image found in flash. Try loading Valid Application...
Change to -O0, SBL works.
**********************************************
Secondary Bootloader Application Start
**********************************************
Press CR key or Space key to stop auto boot and Update Meta Image...
Loading existing Meta Image from Flash in 10 9 8 7 6 5 4 3 2 1
Booting the Application.
No Valid application found. Booting backup factory default image...
******************************************
xWRL6432 MMW Demo 05.03.00.02
******************************************
mmwDemo:/>
syscfg is
Hey Allen,
Thanks for reaching out regarding this issue. One of our experts on the SBL will reach out to you within the next day or two. For now, are you trying to determine what code is being optimized out or potentially changed between each optimization level?
Regards,
Kristien
Hi Kristien,
Because the difference is add McSPI in the syscfg but not customer code, we can only change the whole project optimization level. Customer is trying to use -o0 for now but hope TI could fix this bug.
Regards,
Allen
Hi Allen,
Did you ensure these steps were followed when rebuilding the SBL example with the modifications?
Thanks,
Clinton
I also wanted to mention we plan to try to replicate this on our end and follow up in the next day or so with some additional feedback.
Thanks,
Clinton
Hi Clinton,
This is used to debug SBL using CCS. Customer did not need to debug SBL so I used uniflash to load appimage of sbl and mmw demo as below.
Hi Clinton,
You can reproduce issue as following steps.
1. In CCS 12.04, Import SBL project from SDK 5.3.0.2.
2. Add McSPI in sysconfig as below
3. Change build option to 'Release' active. Make sure the optimization level to 's'.
4. Build and run.
Regards,
Allen
Hi Allen,
I confirmed the behavior you're reporting. I will check on ES2.0 and the accompanying newer versions of the SDK and follow up in the next day or so.
Thanks,
Clinton