Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

bootm error - Wrong Image format, Can't get kernel image - Custom Board

$
0
0

Hello All

I am working on bringing up linux on a custom OMAP - L138 board and have come across certain obstacles.

BACKGROUND:

Network is not available on the custom board. Hence we have copied a single file to the flash by changing the code for flash utility (sft). This seems to be the best option as of now.

This file contains the following at the given addresses in flash

1) U-Boot -> Universal Boot Loader

2) U-Image -> Kernel Image

3) Filesystem

The kernel image and the filesytem are at an offset of 0x10000.

So kernel base address -> 0x90000 

Filesystem base address -> 0x310000

ENVIRONMENTAL VARIABLES:

Kernel                                                                   File System

K: 0xc90000 (Kernelbase)                             B: 0x310000 (File system base)

ks: 0x210000 (Kernel Size)                            S: 0x500000 (File system size)

L: 0xc0000000 (Load Address)                     A: 0x1180000 (Load address)

I have verified that files have been copied to these addresses by reading them in RAM and comparing the files.

sf read 0xc2000000 $B $S

cmp.b 0xc2000000 $A

 

sf read 0xc2000000 $K $ks

cmp.b 0xc2000000 $L

CURRENT:

I am trying to run the flashboot command do boot the images but not able to do so.

setenv flashboot ‘setenv bootargs console=ttyS2,115200n8 root =/dev/ram0 rw initrd $A; sf probe 0;; sf read $A $B $S; sf read $L $K $ks; bootm $L’

which is just

Sf probe 0;

Sf read $A $B $S   -> Read filesytem at $A

Sf read $L $K $ks   -> Read kernel image at $L

bootm $L -> Boot from $L

U-BOOT ERROR:

I get a bad CRC warning and Ethernet init failure as network is not up.

I read somewhere that it is because of unsaved environment variables.

ARM clock: 300000000 Hz

DDR clock: 132000000 Hz

FLASHBOOT ERROR

U-Boot: run F

SF: Detected M25P128 with page size 256, total 16MiB

16384 KiB M25P128 at 0:0 is now current device

Wrong Image Format for bootm command

ERROR: can't get kernel image!

I would be really grateful if anyone could come with some suggestions/procedures or request for additional info. 


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>