My question is why we are using the byte swap rcw to boot the ls1021a iot (rev 1, rev b) using QSPI, is there any way we can use the normally generated RCW.bin?
And if it is necessary to boot using swapped rcw then there must be some changes required for CST tool in yocto to generate hash code for u-boot image and u-boot header image also?
When we tried normal boot (i.e byte swapped rcw and u-boot), board is getting boot up but when we set SB_EN=1 bit in RCW and tried to boot the board with (rcw_swap.bin, header-u-boot.out and u-boot.bin) DUT console gets hanged up and no logs are shown then...
Please help us to debug this issue,
Thanks in advance..
Regarding your question : "why we are using the
byte swap rcw to boot the ls1021a iot (rev 1, rev b) using QSPI",
please take a look at the Application Note : AN4893.
It gives a good overview of endian differences on this
SoC. QSPI endianness requires the swap. As for not
able to boot, there was an erratum on booting from QSPI
on rev 1. You might want to review the errata list for rev 1
and see if it applies to your board.
Thanks Sinan Akman,
Further I have some Queries, that when we are changing UART=1 from UART=4 in RCW and then compiling the RCW we are getting byte_swapped rcw (we are using byte_swap.tcl file for generating the byte swap rcw) by using the swapped RCW we are able to boot LS1021a iot Rev 1 Rev b board.
But when we are tying to boot LS1021aiot rev 1 b board with secure boot enabled in u-boot
RCW SB_EN=1 is made enabled at 202th location,
used hdr_u-boot.out (byte swap) file generated by using CST tool in yocto,
then also we are not able to boot LS1021aiot ...
Please help ...