SPL boot with NAND on i.MX6 data abort
Hi all,
I'm currently working on the port of u-boot for our custom boards. Previously we were using u-boot based on v2013.04 without SPL for our boards (we have boards with SD also) and this worked for all of our devices.
As we now have new boards with different (bigger) RAM, I decided to use the newest bootloader (v2015.10) and enable SPL support. This is already working on a board with SD-Card but I'm not getting it to work on the boards with NAND.
When I try to boot, SPL is detecting and loading u-boot but u-boot throws a "data abort" during "ubifs mount".
The strange thing for me is that when I disable SPL, the board will boot properly.
Could anyone give me a hint how I could trace this error? I can also provide logs or code snippets if needed!
Best Regards
Markus
Hi Markus,
Quoted 8 lines · Markus Stelzhammer
Hi all,
I'm currently working on the port of u-boot for our custom boards. Previously we were using u-boot based on v2013.04 without SPL for our boards (we have boards with SD also) and this worked for all of our devices.
Quoted 7 lines
As we now have new boards with different (bigger) RAM, I decided to use the newest bootloader (v2015.10) and enable SPL support. This is already working on a board with SD-Card but I'm not getting it to work on the boards with NAND.
When I try to boot, SPL is detecting and loading u-boot but u-boot throws a "data abort" during "ubifs mount".
u-boot ist also in NAND ? Then SPL has configured correctly the device else u-boot was not loaded.
Quoted 2 lines
The strange thing for me is that when I disable SPL, the board will boot properly.
You can try to follow the data abort and check which addresses are involved. We cannot underestimate that the bug is still present in u-boot, but it appears only together with SPL.
Quoted 3 lines
Could anyone give me a hint how I could trace this error? I can also provide logs or code snippets if needed!
Some initialization done previously in u-boot, is done now by SPL - check your code if there is something missing.
As your board is not mainlined, we cannot help a much with code.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
Hi Stefano,
Today I grabbed a different Hardware with a bigger NAND chip (512 instead of 256MB).
At this hardware, SPL is not able to jump to U-Boot. So currently I assume that I might have some problems when flashing.
Would you be so kind to review my header file if I miss something or if there is something completely wrong?! (I attached it)
The commands I use to flash are the following:
Quoted 2 lines
./kobs-ng init -v -x SPL
nandwrite --start=0x11000 --pad/dev/mtd0u-boot.uim (I also
tried to flash u-boot.bin and u-boot.imx)
The output I get at boot are the following, but then it stucks.
.......
Quoted 1 line
Quoted 1 line
spl:board_init_r()
using memory 0x18300000-0x1b500000 for malloc() spl_init()
boot device - 4
spl: nand - using hw ecc
NAND : 0x01:0xdc erasesize=1 (>>0)
writesize=-1 (>>0)
oobsize=65535
chipsize=1095216660225
Not support the NAND chips whose oob size is larger then 1024 bytes! 1044479 MiBnand_spl_load_image offset:0x00011000 len:64 page:69632 mkimage signature not found - ih_magic = 0 nand_spl_load_image offset:0x00011000 len:409600 page:69632 Jumping to U-Boot
loaded - jumping to U-Boot...image entry point: 0x17800000
Quoted 29 lines · Stefano Babic
Hi Markus,
Quoted 8 lines · Markus Stelzhammer
Hi all,
I'm currently working on the port of u-boot for our custom boards. Previously we were using u-boot based on v2013.04 without SPL for our boards (we have boards with SD also) and this worked for all of our devices.
Quoted 7 lines
As we now have new boards with different (bigger) RAM, I decided to use the newest bootloader (v2015.10) and enable SPL support. This is already working on a board with SD-Card but I'm not getting it to work on the boards with NAND.
When I try to boot, SPL is detecting and loading u-boot but u-boot throws a "data abort" during "ubifs mount".
u-boot ist also in NAND ? Then SPL has configured correctly the device else u-boot was not loaded.
Quoted 2 lines
The strange thing for me is that when I disable SPL, the board will boot properly.
You can try to follow the data abort and check which addresses are involved. We cannot underestimate that the bug is still present in u-boot, but it appears only together with SPL.
Quoted 2 lines
Could anyone give me a hint how I could trace this error? I can also provide logs or code snippets if needed!
Quoted 8 lines
Some initialization done previously in u-boot, is done now by SPL - check your code if there is something missing.
As your board is not mainlined, we cannot help a much with code.
Best regards,
Stefano Babic
Best regards,
Markus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sigmatek-mx6.h
Type: text/x-chdr
Size: 7606 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150924/9597ebe1/attachment.h>
Hello Markus,
Am 24.09.2015 um 17:03 schrieb Markus Stelzhammer:
Quoted 15 lines
Hi Stefano,
Today I grabbed a different Hardware with a bigger NAND chip (512 instead of 256MB). At this hardware, SPL is not able to jump to U-Boot. So currently I assume that I might have some problems when flashing.
Would you be so kind to review my header file if I miss something or if there is something completely wrong?! (I attached it)
The commands I use to flash are the following:Quoted 2 lines
./kobs-ng init -v -x SPL
nandwrite --start=0x11000 --pad/dev/mtd0u-boot.uim (I also tried to flash u-boot.binand u-boot.imx)
Quoted 8 lines
The output I get at boot are the following, but then it stucks.
.......Quoted 1 line
Quoted 1 line
spl:board_init_r()
using memory 0x18300000-0x1b500000 for
malloc()spl_init()
boot device - 4
spl: nand - using hw ecc
NAND : 0x01:0xdc erasesize=1 (>>0)
From here the values seems bogus to me ... erasesize 1 ?
Quoted 1 line
writesize=-1 (>>0)
negative writesize?
Quoted 2 lines
oobsize=65535
chipsize=1095216660225
Such a big chip?
Quoted 2 lines
Not support the NAND chips whose oob size is larger then 1024 bytes! 1044479 MiB
Wow ...
I think you have problems with detecting the NAND, maybe wrong bus timings?
bye,
Heiko
Quoted 55 lines
nand_spl_load_imageoffset:0x00011000 len:64 page:69632 mkimage signature not found -ih_magic= 0nand_spl_load_imageoffset:0x00011000 len:409600 page:69632 Jumping to U-Boot
loaded - jumping to U-Boot...image entry point:0x17800000Quoted 29 lines · Stefano Babic
Hi Markus,
Quoted 8 lines · Markus Stelzhammer
Hi all,
I'm currently working on the port of u-boot for our custom boards. Previously we were using u-boot based on v2013.04 without SPL for our boards (we have boards with SD also) and this worked for all of our devices.
Quoted 7 lines
As we now have new boards with different (bigger) RAM, I decided to use the newest bootloader (v2015.10) and enable SPL support. This is already working on a board with SD-Card but I'm not getting it to work on the boards with NAND.
When I try to boot, SPL is detecting and loading u-boot but u-boot throws a "data abort" during "ubifs mount".
u-boot ist also in NAND ? Then SPL has configured correctly the device else u-boot was not loaded.
Quoted 2 lines
The strange thing for me is that when I disable SPL, the board will boot properly.
You can try to follow the data abort and check which addresses are involved. We cannot underestimate that the bug is still present in u-boot, but it appears only together with SPL.
Quoted 2 lines
Could anyone give me a hint how I could trace this error? I can also provide logs or code snippets if needed!
Quoted 8 lines
Some initialization done previously in u-boot, is done now by SPL - check your code if there is something missing.
As your board is not mainlined, we cannot help a much with code.
Best regards,
Stefano BabicBest regards,
Markus_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Hi Markus,
Quoted 8 lines · Markus Stelzhammer
Hi Stefano,
Today I grabbed a different Hardware with a bigger NAND chip (512 instead of 256MB).
At this hardware, SPL is not able to jump to U-Boot. So currently I assume that I might have some problems when flashing.
If you are not flashing correctly, SPL does not run. It looks like that your board boots (SPL runs).
Quoted 8 lines
Would you be so kind to review my header file if I miss something or if there is something completely wrong?! (I attached it)
The commands I use to flash are the following:Quoted 2 lines
./kobs-ng init -v -x SPL
nandwrite --start=0x11000 --pad/dev/mtd0u-boot.uim(I also tried to flash u-boot.bin and u-boot.imx)
Quoted 8 lines
The output I get at boot are the following, but then it stucks.
.......Quoted 1 line
Quoted 1 line
spl:board_init_r()
using memory 0x18300000-0x1b500000 for
malloc()spl_init()
boot device - 4
spl: nand - using hw ecc
NAND : 0x01:0xdc erasesize=1 (>>0)
erasesize = 1 ??
Quoted 5 lines
writesize=-1 (>>0)
oobsize=65535
chipsize=1095216660225
Not support the NAND chips whose oob size is larger then 1024 bytes! 1044479 MiB
This larger NAND cannot be recognized correctly - it is not a problem by flashing.
You have to investigate why this NAND (even if ONFI) is not recognized, but it is a different problem as the one you reported previously.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================