Hello,
Thanks for your reply.
In QCVS I imported LS1043A-QDS RCW file generated in Linux SDK 2.0 and tried to adapt it to our board but the board still does not boot.
Now I downloaded the last version of QCVS (2018-01) which seems to have default RCW to start from. Maybe I should start from this default RCW instead of QDS RCW since our board is different.
SERDES protocol = 3558
SDRAM = MT40A512M16JY-083E IT:B (We have to DDR4 SDRAM chip for total 1GB memory size )
I'started from u-boot for LS1043ARDB (as QDS is not for sell) and adapt it with QSPI device definition in device tree and ls1043ardb.h.
As complexity is increasing, I'am trying to validate the RCW and the boot with minimal code. So I used u-boot-spl.bin (SD boot SPL) for which I chaged the link address CONFIG_SPL_TEXT_BASE=0x40010000.I did the same on RDB board with link addresse 0x60100000 and it worked fine in parallel NOR flash. I'm using u-boot from DENX u-boot-qoriq GIT tree.
1) Is CodeWarior TAP abble to debug code in QSPI NOR flash ? (s25fs128s)
3) Is CodeWarior TAP abble to initialize DDR controller with our SDRAM
2) Do you have minimal software like uart example I may flash to validate the boot process instead of whole u-boot?
Currently I have Lauterbach Trace32 but it cannot initialize DDR by itsel but it use u-boot-spl then load code to SDRAM...(!!!)
Best regard.