Thierry Reding wrote at Thursday, October 20, 2011 1:08 PM: > * 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. OK, I built U-Boot with load address 0x00108000 and also see nothing at boot. So, I've reproduced at least one of your problems. (This is with an Android-style nvflash that configures the BCT to tell the CPU to load/boot the bootloader at address 0x00108000, so this should work.) So, I've added this observation into the bug I filed. I'll let you know once we've had a chance to investigate and/or solve this. Sorry this isn't working yet; it's pretty early days for U-Boot on Tegra outside of ChromeOS, which uses the modified nvflash and hence doesn't hit these issues. -- nvpublic -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
