AnsweredAssumed Answered

NAND boot imx6

Question asked by adnan ali on Dec 28, 2015
Latest reply on Dec 31, 2015 by adnan ali

I am trying to nand boot my mx6 based custom board. I have written the FCB manually. I can see the IVT header being placed at 0x907400

S:0x00907400: 0x0D100000  0x00040200  0x00000908  : ............

S:0x0090740C: 0x91800000  0x90C00907  0x8EC00907  : ............

S:0x00907418: 0x00000907  0x00000000  0x8EC00000  : ............

S:0x00907424: 0x00000903  0x0000000B  0x0D200000  : .......... .

S:0x00907430: 0x0CC40080  0x00004040  0x00000000  : ....@@......

S:0x0090743C: 0x00000000  0x00000000  0x00000000  : ............

S:0x00907448: 0x00000000  0x80000000  0x00000000  : ............

S:0x00907454: 0x00000000  0x00000000  0x00000000  : ............

S:0x00907460: 0x00000000  0x00000000  0x00000000  : ............

S:0x0090746C: 0x00000000  0x00000000  0x00000000  : ............

 

But I could not get my SPL loaded and executed. I have Nullified the DBBT so that ROM code does not search for the BAD blocks in the NAND. I have also tested kobs-ng tool here are the steps

dd if=SPL of=SPL-nand bs=512 seek=2
kobs-ng init -v SPL-nand

 

After it when I reboot the board it does not boot SPL neither fall back to USB boot which means that FCB is good to go. I cannot see the IVT header at 0x907400 in this case when I connect through JTAG

 

where as when I use my FCB command it fall backs to usb boot .

Moreover you can see that at address 907400 it is not the exact IVT header.The first four bytes are 402000D1 in the hexdump of the SPL

 

I have loaded the same SPL from usb tool and it works. I am using dstream and ds5 for JTAG debugging.

 

Am i missing something here ?

Outcomes