On 05/13/13 18:21, Thomas Petazzoni wrote:
On Mon, 13 May 2013 18:12:00 +0200, Sebastian Hesselbarth wrote:
One solution for Barebox is to have a DATA line in our kwbimage.cfg
that does:
DATA 0xd0020080 0xf1000000
and so when Barebox boots, the remapping to 0xf1 is already done,
and we don't have to worry about it. This way, a Barebox can
chainload a second Barebox.
Thomas, have you tried the above? I did and Dove immediately stops
responding to Xmodem transfer. I have the strong feeling, that BootROM
relies on stuff located at 0xd0000000.
So remapping _that_ early will maybe not work either.
No, I did not test that, it was just a supposition from me that it
would work. I was under the impression that the SoC would load the
entire image in SRAM, and then go through the DATA commands and apply
them. But of course, if it does apply each and every DATA command as
soon as it receives them, then it cannot work, and Barebox will have to
do its remapping and give up the possibility of being booted by itself.
Hmm, Dove spec says about BootROM Address Decoding:
"BootROM firmware uses the default address map, and does not change it
throughout the entire boot process."
And of course, if you change the address map early, BootROM will fail
to access peripherals (SPI, I2C, NAND, ...).
Remap by kwbimage.cfg looks like a no-go.
Sebastian
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
