Re: d-i on Firefly-rk3288

[Diego Roversi <diegor@tiscali.it>]

On Sun, 11 Dec 2016 08:21:12 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

>  make sure you wipe out at least 150mb (so as to trash *all* the
> partitions) - i had some segfaults occur with the default 3.10 kernels
> by not erasing enough data.  i only erased 10mb and it left
> half-set-up partitions on the drive.  wark-wark...

Ok, this part is done. Now the u-boot is loaded correctly from sd, but now I have this error:

U-Boot SPL 2016.09+dfsg1-2 (Oct 24 2016 - 02:36:36)
Trying to boot from MMC1


U-Boot 2016.09+dfsg1-2 (Oct 24 2016 - 02:36:36 +0000)

Model: Firefly-RK3288
DRAM:  2 GiB
MMC:   dwmmc@ff0c0000: 0, dwmmc@ff0f0000: 1
*** Warning - bad CRC, using default environment

stdio_add_devices: Video device failed (ret=-19)
In:    serial
Out:   serial
Err:   serial
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
1575 bytes read in 5 ms (307.6 KiB/s)
## Executing script at 00000000
Mainline u-boot / new-style environment detected.
fdtfile environment variable not set. Aborting boot process.
SCRIPT FAILED: continuing...
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
** No partition table - mmc 1 **

I have workaround to this error with the following commands:

=> setenv fdtfile rk3288-firefly.dtb
=> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
1575 bytes read in 5 ms (307.6 KiB/s)
## Executing script at 00000000
Mainline u-boot / new-style environment detected.
reading vmlinuz
3701000 bytes read in 282 ms (12.5 MiB/s)
reading dtbs/rk3288-firefly.dtb
36029 bytes read in 23 ms (1.5 MiB/s)
reading initrd.gz
19320863 bytes read in 1448 ms (12.7 MiB/s)
Booting the Debian installer... 

## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 1ed92000, end 1ffff01f ... OK
   Loading Device Tree to 1ed86000, end 1ed91cbc ... OK

Starting kernel ...

  and now it hangs here. I was expecting something on the serial, and I have no monitor attached to the board, so I don't understand if it is doing something or not... 

-- 
Diego Roversi <diegor@tiscali.it>