Hello,
I have a IMX53 board, based on loco with a NAND.
I need to boot from NAND, but have some problem, and it don't work.
I would try to debug IMX ROM Bootloader with lauterbah due to verify if the NAND work good or there are some compatibility issue, (I know that it work good on linux, because starting from SD, I can use NAND as rootfs, etc).
There is something that help to do this operation? (like some source to load, the starting address, .. anything that help, I'm really frustrated about that).
My issue is explained here:
IMX53 Loco based board with MT29F8G08ABABA as NFC 8bit
and this is a really similar issue:
Regards
Hi Cristian
MT29F8G08ABABA has 224 byte spare size and formally
is not supported by ROM for boot (max. supported 4KB + 218 Bytes).
Still one can try with setting BOOT_CFG2[7:6]="4KB + 218 Bytes" .
NAND FCB can be written only with kobs-ng tool and
easy way to make bootable NAND image is to use MFG Tool IMX_MFG_TOOL ,
refer to attached ucl.xml file with profile: LIST name="MX53ARD-NAND(JFFS2) .
README_MX53_NAND_BOOT.pdf describes changes
needed for support NAND uboot, these patches are already included
in FSL ltib i.MX53 releases L2.6.35_11_09_ER_SOURCE, for correct
bulding one needs to select "mx53_ard" for uboot building. In general one
can also try kobs-ng from i.MX6 BSP releases, it supports more NAND configurations.
One can try to debug checking NAND signals by oscilloscope,
image header should appear in NFC RAM buffer (then ROM reads it
to iRAM 0xf8006400) - this can be checked with jtag. Note i.MX53
NFC controller supports max.16 bit ECC, NANDs required more ECC
bits are not supported.
Best regards
igor
Hello *,
I'm trying to debug imx53 in early stage, but seems that the ROM loader get some issue, the code run in loop in memory at 40xxxxh and in Bxxh, so as in the IMX53RM.pdf page 483, at c0h-3fffh and 400000h-40bffh there is the ROM Bootstrap.
With the scope I see some data on NAND bus.
I tried also to follow this guide, with this u-boot (2014-10) code:
http://www.denx-cs.de/doku/?q=m53evkcompileinstalluboot
after this I use this command (whit my kernel that work good with nand):
umount /dev/mtdblock*
umount /rwfs/
ubidetach -d 5 /dev/ubi_ctrl
mount
mount /dev/mmcblk0p3 /mnt/cdrom/
sleep 3
echo 1 > /sys/devices/platform/mxc_nandv2_flash.0/ignorebad
kobs-ng init -v /mnt/cdrom/u-boot-with-nand-spl.imx
echo 1 > /sys/devices/platform/mxc_nandv2_flash.0/ignorebad
In the first part I umount all nand partition, mount external sdcard, where is located nand-spl.
My nand is also on PATA pins, the only change is that my UART is on UART1, so I changed the iomux.
Hello Cristian,
At least you should try to sue this sequence to connect to the baord:
SYStem.RESet
SYStem.CPU IMX535
SYStem.Option ResBreak OFF
SYStem.Option WaitReset 100ms
SYStem.Up
The chip does not allow to connect to the board in an early boot stage, because the debugger has to wait, till the debug clocks internaly are enabled. Important at this stage is, that they later will nto be disabled again by the bootloader (there were some versions, were debug debug port was disablked completely).
If this is not working, then it would be good to know, what error messages you get. You can try to connect in a later boot stage using Attach instead of Up, just to see, if debugging is possible at all. If you were not able to connect in any case, then you could try to select a different boot mode, just for testing.
Best Regards,
Steffen.