Hi Karsten, many thanks for the u-boot explanation. That helps me a lot.
On Saturday 15 November 2014 11:51:05 Karsten Merker wrote: [...] > > dd if=/usr/lib/u-boot/mx6_cubox-i/u-boot-spl.bin of=/dev/sdX bs=1K seek=1 > dd if=/usr/lib/u-boot/mx6_cubox-i/u-boot.img of=/dev/sdX bs=1K seek=42 What is the difference between u-boot-spl.bin and SPL in rd@home:~$ ls -l /usr/lib/u-boot/mx6_cubox-i/ insgesamt 588 -rw-r--r-- 1 root root 31744 Nov 2 01:32 SPL -rw-r--r-- 1 root root 302872 Nov 2 01:32 uboot.elf -rw-r--r-- 1 root root 236248 Nov 2 01:32 u-boot.img -rw-r--r-- 1 root root 25665 Nov 2 01:32 u-boot-spl.bin rd@home:~$ ? So far I always used SPL which worked for me: blackbox:~# dd if=/mnt/tmp/usr/lib/u-boot/mx6_cubox-i/SPL of=/dev/sdX bs=1K seek=1 blackbox:~# dd if=/mnt/tmp/usr/lib/u-boot/mx6_cubox-i/u-boot.img of=/dev/sdX bs=1K seek=42 blackbox:/mnt/tmp# > Once you have have booted from this SD card, you should get a > u-boot prompt, from which you can continue as described in the > installation guide. yes, that works. > > > Daily-built netboot images are available at > > > http://d-i.debian.org/daily-images/armhf/daily/netboot/ and > > > the device-tree files for the supported systems are at > > > http://d-i.debian.org/daily-images/armhf/daily/device-tree/. > > > > > > We have recently added support for hd-media images, i.e. booting > > > the installer from a USB stick, to d-i, but this works "out of > > > the box" only on systems that have a very recent u-boot version > > > (v2014.10) with support for the new common u-boot bootcmd > > > handling framework. > > > > Again, here we are talking about the SPL not the IPL, right? In this case > > you the u-boot version from sid would do for the Cubox-i you mention. > > I am not sure that we are using the same nomenclature regarding > IPL (Initial Program Loader) and SPL (Secondary Program Loader). > > On modern ARM-based SoCs, IPL usually means the hardcoded boot > ROM code that is a fixed part of the SoC; it performs the primary > startup of the SoC and loads the SPL boot code from a removable > medium into some SoC-internal SRAM. After the IPL is run, i.e. > at the point where control gets transferred to the SPL, the > system DRAM controller is usually not yet set up, so only this > small area of SRAM is accessible. This area is too small for a > full-featured firmware/bootloader, so the SPL sets up the DRAM > controller and loads the remaining firmware/bootloader code > (often called the TPL - Tertiary Program Loader) into DRAM and > starts it there. > > In our case we have: > - IPL: internal to the i.MX6 SoC > - SPL: /usr/lib/u-boot/mx6_cubox-i/u-boot-spl.bin > - TPL: /usr/lib/u-boot/mx6_cubox-i/u-boot.img Many thanks. Is the environment (setenv, saveenv,...) also part of the u- boot.img? > Regarding the hd-media support: as Vagrant wrote that he has > patched some support for the new common u-boot bootcmd handling > into the i.MX6 u-boot.img in sid, this should hopefully work, but > due to lack of i.MX6 hardware I have never tested that. > > Please note that as a new kernel version has migrated to testing > sometime this week, there might be a mismatch between the > daily-built hd-media tarball and the testing CD image which was > generated last monday. A new CD image will be built next monday, > which should solve this issue, but for the moment you should > probably first try installing by tftp. I will try that probably after Monday. Kind regards, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/2178420.0WkutniNIT@blackbox
