From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sjoerd Simons Date: Mon, 30 Mar 2015 10:14:22 +0200 Subject: [U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support In-Reply-To: References: <1424212195-7501-1-git-send-email-sjg@chromium.org> <1424909540.14929.65.camel@collabora.co.uk> Message-ID: <1427703262.24522.59.camel@collabora.co.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, 2015-02-27 at 22:11 -0700, Simon Glass wrote: > Hi Sjoerd, > > On 25 February 2015 at 17:12, Sjoerd Simons > wrote: > > Hey Simon, > > > > Incidentally i got acces to a Nyan big and wanted to start testing > > u-boot on it. Unfortunately putting a uImage in a vboot signed blob to > > chainload it from the primary bootloader like on the exynos based > > chromebooks seemed not to work. > > > > Do you have any good pointers how to use u-boot on nyan? (Ideally > > without having to re-flash coreboot, as i would like to create images > > people can easily test on a vanilla chromebook) > > No I don't sorry. I suppose in dev mode it should boot a signed image > so if you put U-Boot in a FIT as with snow/pit it should work. But I > don't have instructions...if you figure it out it would be good to put > this info somewhere. Finally got time to play a bit with this. On the snow/peach boards the approach is to put u-boot in a legacy u-boot image (not a FIT image), which has the nice side-effect of re-locating u-boot before jumping to it. Unfortunately the depthcharge on the nyan boards appears not to support legacy images, only FIT images, which don't get relocated before jumping into the kernel blob. Long story short, on the nyan boards the FIT image gets loaded at 0x81000000 and the FIT images i created put the u-boot blob at an offset of 0xCC. After re-configuring CONFIG_SYS_TEXT_BASE to match i got u-boot starting \o/ ;) Unfortunately the board seems to hard hang when it tries to enable/use the data cache. Enabling CONFIG_SYS_DCACHE_OFF makes it get to the u-boot prompt. Unfortunately neither MMC (didn't detect card) nor USB (failed to get descriptor from my usb network dongle) worked so i couldn't try booting a kernel just, but it's start. Simon, does data cache/MMC/USB work properly when booting u-boot "natively" rather then chainloading from coreboot or does it have similar issues? Fwiw, I've attached the output of u-boot running onthe board (with CONFIG_SYS_DCACHE_OFF enabled). -- Sjoerd Simons Collabora Ltd. -------------- next part -------------- U-Boot 2015.04-rc4-00125-g662e2ac-dirty (Mar 30 2015 - 00:17:30) TEGRA124 Model: Acer Chromebook 13 CB5-311 DRAM: 2 GiB MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2 Card did not respond to voltage select! MMC init failed Using default environment In: serial Out: serial Err: serial Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 2  1  0 MMC: no card present Card did not respond to voltage select! starting USB... USB0: USB EHCI 1.10 scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80 EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008c80 EHCI timed out on TD - token=0x80008c80 usb_get_configuration_no: failed to get descriptor - too long: 65460 usb_new_device: Cannot read configuration, skipping device 58f4:fffa 1 USB Device(s) found USB1: USB EHCI 1.10 scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found USB device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-tegra124 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. Tegra124 (Nyan-big) #