Creator CI20: Formato de imagem incorreto para o comando bootm

0

Estou tentando fazer com que meu Criador CI20 seja inicialize a partir do sdcard diretamente.

Eu compilei um kernel Linux vanilla 4.9.20 usando (estou executando o debian stretch no meu laptop):

$ make ARCH=mips ci20_defconfig
$ make ARCH=mips CROSS_COMPILE=mipsel-linux-gnu- uImage
Image Name:   Linux-4.9.20
Created:      Sat Jul  1 21:04:19 2017
Image Type:   MIPS Linux Kernel Image (uncompressed)
Data Size:    5225712 Bytes = 5103.23 kB = 4.98 MB
Load Address: 80010000
Entry Point:  8034d0a0
  Image arch/mips/boot/uImage is ready

Se eu copiar o arquivo arch/mips/boot/uImage para o meu local do tftp , posso gerenciar o kernel para inicializar corretamente:

Hit any key to stop autoboot:  0
ci20# dhcp 0x88000000 192.168.0.14:uImage
ERROR: resetting DM9000 -> not responding
dm9000 i/o: 0xb6000000, id: 0x90000a46 
DM9000: running in 8 bit mode
MAC: d0:31:10:ff:7d:02
operating at 100M full duplex mode
BOOTP broadcast 1
DHCP client bound to address 192.168.0.15
Using dm9000 device
TFTP from server 192.168.0.14; our IP address is 192.168.0.15
Filename 'uImage'.
Load address: 0x88000000
Loading: #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     #################################################################
     ################################
     264.6 KiB/s
done
Bytes transferred = 4924012 (4b226c hex)

## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-4.9.20
   Image Type:   MIPS Linux Kernel Image (uncompressed)
   Data Size:    4923948 Bytes = 4.7 MiB
   Load Address: 80010000
   Entry Point:  803465e0
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting k[    0.111767] jz4780-nemc 13410000.nemc: failed to calculate clock period
[    0.148419] UBI error: cannot open mtd 3, error -19[    0.153621] UBI error: cannot open mtd 4, error -19
[    0.158775] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.167039] Rebooting in 10 seconds..bootm 0x88000000NAND:  8192 MiB

Mas se eu copiá-lo para o meu cartão SD, eu recebo esta mensagem estranha de u-boot:

U-Boot 2013.10-rc3-g25f5638f9 (Jul 01 2017 - 16:30:50)

Board: ci20 (r1) (Ingenic XBurst JZ4780 SoC)
DRAM:  1 GiB
NAND:  8192 MiB
MMC:   jz_mmc msc1: 0
In:    eserial4
Out:   eserial4
Err:   eserial4
Net:   dm9000
Hit any key to stop autoboot:  0 
** File not found /boot/uImage **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Aqui está o conteúdo do sdcard:

% tree /media/mathieu/466bcc7d-37c4-41f3-b83f-8ac6628eb2bb/boot 
/media/mathieu/466bcc7d-37c4-41f3-b83f-8ac6628eb2bb/boot
├── uImage
└── vmlinux.img

0 directories, 2 files

E o sistema de arquivos é:

% mount
/dev/mmcblk0p1 on /media/mathieu/466bcc7d-37c4-41f3-b83f-8ac6628eb2bb type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)

Existe uma maneira de obter um pouco mais de informações sobre o que o erro poderia ser?

    
por malat 01.07.2017 / 21:11

1 resposta

0

Como explicado por @ tom-rini, o problema era simplesmente o 64bits no ext4 adicionado automaticamente.

A documentação de:

Descreve:

$ sudo mkfs.ext4 /dev/sdx1

em vez disso, deveria ter dito (para o mais novo comando mkfs.ext4):

$ sudo mkfs.ext4 -O^64bit,^metadata_csum /dev/sdx1

Apenas para a posteridade, esta é a segunda vez que sou mordido por isso:

Espero que o último.

    
por 05.07.2017 / 22:28