On 22.02.2012 11:46, Stefano Babic wrote:
On 22/02/2012 11:30, Dirk Behme wrote:
On 22.02.2012 11:24, Stefano Babic wrote: ...
+BOOT_FROM nor
I assume that you have tested this and it works with the imximage?
I have not any problem with the current imximage, so I am quite confused.
Hmm, yes, this is quite confusing :(
Agree that you are fixing a bug, but I have not understood why I have not seen any issue on my board, a MX53 using V2 image header.
My board boots flawlessly from the NOR interface. I will try to investigate why and, of course, I will be able to test your patch on my board.
Can you confirm that your board does not boot ?
Yes, removing the imximage fix stops the board from booting. Unfortunately it's hard to debug how the boot ROM deals with the header information. So either it works, or not, but there is little chance to debug :(
For testing, taking the SabreLite (mx6qsabrelite), switching it to NOR [1] and then compiling it without and with my imximage fix, results in the following difference in the header (disassembly of u-boot.imx):
- 20: 177ff800 + 20: 177fec00
At offset 0x20 in the header, this is the target address in the destination memory. Having a header with the size of 0x400 (like here) the destination address should be TEXT_BASE - 0x400 (header size) - 0x1000 (NOR offset), i.e. 0x17800000 - 0x1400. So my understanding is that 0x177fec00 is correct for NOR, while 0x177ff800 is valid for all FLASH_OFFSET_STANDARD devices.
Best regards
Dirk
[1]
board/freescale/mx6qsabrelite/imximage.cfg BOOT_FROM nor