On 8 November 2016 at 17:46, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx> wrote: > On Tue, Nov 08, 2016 at 05:37:25PM +0000, Sudeep Holla wrote: >> >> >> On 08/11/16 16:06, Russell King - ARM Linux wrote: >> >On Tue, Nov 08, 2016 at 03:40:38PM +0000, Russell King - ARM Linux wrote: >> >>As it contains a zero sized Image and .dtb files, I tried copying my >> >>Image and .dtb over, and also copied my original config.txt (only >> >>change is AUTORUN: FALSE). It still doesn't appear to boot beyond >> >>this point. >> > >> >Well, it seems that I can't even go back to my original set of firmware >> >as UEFI has stopped working: >> > >> >NOTICE: Booting Trusted Firmware >> >NOTICE: BL1: v1.0(release):14b6608 >> >NOTICE: BL1: Built : 14:15:51, Sep 1 2014 >> >NOTICE: BL1: Booting BL2 >> >NOTICE: BL2: v1.0(release):14b6608 >> >NOTICE: BL2: Built : 14:15:51, Sep 1 2014 >> >NOTICE: BL1: Booting BL3-1 >> >NOTICE: BL3-1: v1.0(release):14b6608 >> >NOTICE: BL3-1: Built : 14:15:53, Sep 1 2014 >> >UEFI firmware (version v2.1 built at 14:41:56 on Oct 23 2014) >> >Warning: Fail to load FDT file 'juno.dtb'. >> > >> >> This again because of incompatibility of the configuration data saved in >> NOR flash. The erase command I gave early is to erase that when you >> switched between the UEFI binaries. It's really horrible mess UEFI >> created in the initial days of Juno, and hopefully they have moved to >> some standard format these days. > > Yea, what it means is I've no possibility to go back to what was > originally working now, since I don't understand how to get UEFI to > behave (Will set the machine up for me, I don't have any information > on how it was originally configured other than what was on the uSD > card, which appears incomplete.) > >> >and UEFI is the most unfriendly thing going - the "boot manager" thing >> >doesn't let you view the configuration: >> > >> >> I completely agree. I had real bad times in past dealing with such >> things in UEFI. >> >> >[1] Linux from NOR Flash >> >[2] Shell >> >[3] Boot Manager >> >Start: 3 >> >[1] Add Boot Device Entry >> >[2] Update Boot Device Entry >> >[3] Remove Boot Device Entry >> >[4] Reorder Boot Device Entries >> >[5] Update FDT path >> >[6] Set Boot Timeout >> >[7] Return to main menu >> >Choice: >> > >> >and dropping into the shell... well, I've no idea how to get a listing >> >of what it thinks is in the NOR device (or even how to refer to the >> >NOR device.) "devices" shows nothing that's even remotely English. >> > Using UEFI is painful enough on Juno. Using a 2 year old version with "that" menu system is even worse. So I'll just pitch in here and recommend you switch to using u-boot. Then you can see your config with "printenv" and you'll probably understand it too. The board will boot my prebuilt kernel/DTB using u-boot if you erase the uSD card and unzip this firmware image to it: http://releases.linaro.org/members/arm/platforms/16.10/juno-latest-oe-uboot.zip Then you can copy over your own kernel & DTB for your own testing, configure u-boot for TFTP, or whatever you like. Switching to u-boot won't solve any thermal sensor calibration problems. >> >> I think startup.nsh needs some edits. Just replace it with something like: >> >> "norkern dtb=board.dtb console=ttyAMA0,115200n8 root=/dev/nfs rw >> rootwait ip=dhcp systemd.log_target=null nfsroot=..." or something >> alike. Currently it just echos and stops. >> >> Regarding the new firmware stopping abruptly, I have no clue, except >> asking you to erase the flash completely when switching between the >> firmware versions. That has worked for me for all UEFI related issues in >> the past. It's really annoying I understand. >> >> flash> eraseall > > I've tried that, it still stops at the same point, after: > > FV2 Hob 0xFE07B000 - 0xFE8253BF > > and remains unresponsive. > > I do notice that the uSD card becomes visible through USB at this point > though. > > Okay, well, I'm going to have to disable Juno from the nightly boots > until we get some kind of resolution on this, as my Juno is now > incapable of booting anything. > > -- > RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ > FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up > according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
