* Stephen Warren wrote: > Thierry Reding wrote at Thursday, October 20, 2011 2:08 AM: > ... > > I've been working some on getting our boards to boot from a device tree. > > Unfortunately, the U-Boot issue seems to be more of a problem than I > > anticipated. Since the mainline U-Boot doesn't run properly, > > ----------==========----------==========----------==========----------========== > What issues are you having? I assume you're referring to something more > than just getting stuff flashed with nvflash. Flashing U-Boot is not the problem, but when booting the device, there's no output whatsoever on the debug port. That's what I meant in one of the previous mails. nvflash says it's loading fastboot.bin at address 0x00108000, and quickboot seems to use the same load address. However, U-Boot is built with CONFIG_SYS_TEXT_BASE set to 0x00E08000. If it is loaded to the same address as fastboot/quickboot it obviously cannot run. So I went ahead and built U-Boot (both mainline and the one from the Chromium repo) with a load address of 0x00108000 - to no avail. I'm starting to think that perhaps I'm completely overlooking something obvious. When I use the Vibrante U-Boot, I get normal U-Boot output on the debug port when I flash it as stage 2 for quickboot. The other versions of U-Boot don't work in that setup. None of the three versions boot when flashed standalone (substituting u-boot.bin for fastboot.bin in the nvflash configuration file). I would guess that at least with quickboot as stage 1 I should be able to get serial output from the mainline U-Boot. Would it be helpful to move the discussion to the U-Boot mailing list instead? It's sort of off-topic here. Thierry
Attachment:
pgphumJKFAogT.pgp
Description: PGP signature
