[U-Boot] NAND DMA timed out with i.mx boot source code.
Hi: I have one board which hardware copied from mx28evk board, and compiled the source code cloned from u-boot mainline git. The rom in mx28 print 0x80508008, that is "NAND DMA timed out". I compile the source from u-boot-testing, and it's no any wrong print, and the start is OK. I don't know why result in this issue.
Best Regards, Alex
Dear alex,
Hi: I have one board which hardware copied from mx28evk board, and compiled the source code cloned from u-boot mainline git. The rom in mx28 print 0x80508008, that is "NAND DMA timed out". I compile the source from u-boot-testing, and it's no any wrong print, and the start is OK. I don't know why result in this issue.
u-boot-testing is quite ancient. But the code you're getting is during bootrom booting from NAND, not in uboot, correct? Does your nand chip have 2048b pages with 64b OOB? Did you use nand_update_full() to reload the NAND?
Best Regards, Alex
Best regards, Marek Vasut
No network on my board, so nand_update_full can't be run. I use command "kobs-ng init u-boot.sb" to update(default: /dev/mtd0) or mfgtools from freescale. I just add support NAND to mx28evk configs file copied from m28evk configs. Sub-page size of nand flash is 2048bytes with oob size is 64byte, and size is 128M.
At 2012-06-28 18:49:39,"Marek Vasut" marex@denx.de wrote:
Dear alex,
Hi: I have one board which hardware copied from mx28evk board, and compiled the source code cloned from u-boot mainline git. The rom in mx28 print 0x80508008, that is "NAND DMA timed out". I compile the source from u-boot-testing, and it's no any wrong print, and the start is OK. I don't know why result in this issue.
u-boot-testing is quite ancient. But the code you're getting is during bootrom booting from NAND, not in uboot, correct? Does your nand chip have 2048b pages with 64b OOB? Did you use nand_update_full() to reload the NAND?
Best Regards, Alex
Best regards, Marek Vasut
On Thu, Jun 28, 2012 at 11:24 PM, alex laub923@163.com wrote:
No network on my board, so nand_update_full can't be run. I use command "kobs-ng init u-boot.sb" to update(default: > /dev/mtd0) or mfgtools from freescale. I just add support NAND to mx28evk configs file copied from m28evk configs.
There is NAND support on mx28evk.h in mainline. Looks like you are using old code.
Please use the latest mainline code and try again.
Are you able to boot from SD card on your board?
No sd support on my board. I use the the latest code. update by command "kobs-ng init u-boot.sb", and give error as below: mtd: erase stepping bounds mtd: Failed to erase block @0x1e0000 mtd: Failed to write BS#1 FAILED to commit structures
At 2012-06-29 10:51:58,"Fabio Estevam" festevam@gmail.com wrote:
On Thu, Jun 28, 2012 at 11:24 PM, alex laub923@163.com wrote:
No network on my board, so nand_update_full can't be run. I use command "kobs-ng init u-boot.sb" to update(default: > /dev/mtd0) or mfgtools from freescale. I just add support NAND to mx28evk configs file copied from m28evk configs.
There is NAND support on mx28evk.h in mainline. Looks like you are using old code.
Please use the latest mainline code and try again.
Are you able to boot from SD card on your board?
Dear alex,
No network on my board, so nand_update_full can't be run.
I'm sure you can figure out how to transfer the update file, the rest is the same.
I use command "kobs-ng init u-boot.sb" to update(default: /dev/mtd0) or mfgtools from freescale.
That won't work, see vim doc/README.mx28_common (section 4) about NAND, around line 150)
I just add support NAND to mx28evk configs file copied from m28evk configs. Sub-page size of nand flash is 2048bytes with oob size is 64byte, and size is 128M.
At 2012-06-28 18:49:39,"Marek Vasut" marex@denx.de wrote:
Dear alex,
Hi: I have one board which hardware copied from mx28evk board, and compiled
the source code cloned from u-boot mainline git. The rom in mx28 print 0x80508008, that is "NAND DMA timed out". I compile the source from u-boot-testing, and it's no any wrong print, and the start is OK. I don't know why result in this issue.
u-boot-testing is quite ancient. But the code you're getting is during bootrom booting from NAND, not in uboot, correct? Does your nand chip have 2048b pages with 64b OOB? Did you use nand_update_full() to reload the NAND?
Best Regards, Alex
Best regards, Marek Vasut
Best regards, Marek Vasut
participants (3)
-
alex -
Fabio Estevam -
Marek Vasut