DM6446 NAND issue

satish kumar

Hi,

In our custom DM6446 processor board, when we try to load the Linux kernel with the following commands

U-Boot > tftp 0x80700000 uImage
U-Boot > nand erase 0x60000 0x200000
U-Boot > nand write 0x80700000 0x60000 0x200000

all are executed successfully. kernel also loaded successfully. But when we re-boot the board UBL massages are looping as given below

DM644x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000014.
   DONE
Jumping to entry point at 0x81080000.
   .
   .
   .

DM644x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000014.
   DONE
Jumping to entry point at 0x81080000.

if we don't load the kernel in NAND and run form DDR every-time, the device working perfectly.

please guide us in solving the issue.

Thanks,

Satish.

over 10 years ago

0 Prabhakar Lad over 10 years ago

Guru 11260 points

Hi,

Strange! can you try booting from NAND (UBL + UBOOT in nand) and uImage from tftp server/SD card, boot it and restart and see if you see the same issue ?

Cheers,
--Prabhakar Lad

0 Shankari G over 10 years ago

TI__Mastermind 43955 points

Hi Satish,

I believe your writing the uImage (kernel) in u-boot location (so that u-boot area got corrupted).
After re-flashing the u-boot and without writing kernel image (uImage), do a reboot, you wont see any issues there after.

If it behaves like that, then it is surely due to over writing the u-boot area with kernel.

Could you check the kernel location!.

Try to avoid the u-boot and kernel overlapping.

Try this.

U-Boot > tftp 0x80700000 uImage
U-Boot > nand erase 0x200000 0x400000
U-Boot > nand write 0x80700000 0x200000 0x400000

0 satish kumar over 10 years ago in reply to Shankari G

Intellectual 295 points

Hi Shankari,

Thank you. It worked. But what may be the issue? we used nand different from DM6446 EVM, but configured CONFIG_SYS_NAND_LARGEPAGE
for 128K sector size.

Thanks,
satish.

0 satish kumar over 10 years ago in reply to Prabhakar Lad

Intellectual 295 points

Hi Prabhakar,

the issue mentioned above is for NAND boot only and uImage is from tftp.

Thanks,
satish.

0 Shankari G over 10 years ago in reply to satish kumar

TI__Mastermind 43955 points

Hi Sathish,
I'm glad that you problem got solved.
Thanks for your update.
Always try to keep the kernel from u-boot location to avoid overlapping between them.

Processors

Processors forum

DM6446 NAND issue