wrong Image Format for bootm command ERROR: can't get kernel image!

[mahendra-space]

Hi,
I have installed QEMU on my Linux PC and try to start QEMU session with romulus image "obmc-phosphor-image-romulus.static.mtd" by using command-
]./qemu-system-arm -m 256 -M romulus-bmc -nographic
-drive file=./obmc-phosphor-image-romulus.static.mtd,format=raw,if=mtd
-net nic
-net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:2443-:443,hostfwd=udp:127.0.0.1:2623-:623,hostname=qemu"

But it is not started-
Issue- wrong Image Format for bootm command
ERROR: can't get kernel image!

any solution please ??
I am following this web link "https://github.com/openbmc/docs/blob/master/development/dev-environment.md"

[williamspatrick]

Where did your obmc-phosphor-image-romulus.static.mtd come from? Did you build it or download it?

https://github.com/openbmc/docs/blob/master/development/dev-environment.md#download-and-start-qemu-session

The instructions here give a wget call that downloads an image from Jenkins. Can you confirm this works? If it does, and you're attempting to run an image you built yourself, can you give more details on how you built it and what your tmp/deploy/images tree looks like after you built.

[mahendra-space]

Where did your obmc-phosphor-image-romulus.static.mtd come from? Did you build it or download it?

https://github.com/openbmc/docs/blob/master/development/dev-environment.md#download-and-start-qemu-session

The instructions here give a wget call that downloads an image from Jenkins. Can you confirm this works? If it does, and you're attempting to run an image you built yourself, can you give more details on how you built it and what your tmp/deploy/images tree looks like after you built.

Thanks for prompt reply Williamspatrick.

Actually I downloaded from "wget https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=romulus/lastSuccessfulBuild/artifact/openbmc/build/tmp/deploy/images/romulus/obmc-phosphor-image-romulus.static.mtd".

I followed instruction as given into this link "https://github.com/openbmc/docs/blob/master/development/dev-environment.md"
for downloading and installing and start QEMU session.

Where did your obmc-phosphor-image-romulus.static.mtd come from? Did you build it or download it?

https://github.com/openbmc/docs/blob/master/development/dev-environment.md#download-and-start-qemu-session

The instructions here give a wget call that downloads an image from Jenkins. Can you confirm this works? If it does, and you're attempting to run an image you built yourself, can you give more details on how you built it and what your tmp/deploy/images tree looks like after you built.

[mahendra-space]

Hi Williamspatrick,

I have also build openBMC source code by using bitbake.
QEMU session start and only once. But when I reboot my Linux pc and try to start QEMU, It got error-

:~/sdk$ ./qemu-system-arm -m 256 -M romulus-bmc -nographic -drive file=./obmc-phosphor-image-romulus.static.mtd,format=raw,if=mtd -net nic -net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:2443-:443,hostfwd=udp:127.0.0.1:2623-:623,hostname=qemu
qemu-system-arm: warning: Aspeed iBT has no chardev backend
qemu-system-arm: warning: nic ftgmac100.1 has no peer

U-Boot 2019.04 (Aug 09 2022 - 05:12:55 +0000)

SOC : AST2500-A1
RST : Power On
2nd Boot : Enable
LPC Mode : SIO:Enable : SuperIO-2e
Eth : MAC0: RMII/NCSI, , MAC1: RMII/NCSI,
Model: Romulus BMC
DRAM: 192 MiB (capacity:256 MiB, VGA:64 MiB, ECC:off)
MMC:
Loading Environment from SPI Flash... SF: Detected n25q256a with page size 256 Bytes, erase size 4 KiB, total 32 MiB
OK
In: serial@1e784000
Out: serial@1e784000
Err: serial@1e784000
Net: ftgmac100_probe - NCSI detected

Warning: ethernet@1e660000 (eth0) using random MAC address - 36:62:a6:cb:88:a4
eth0: ethernet@1e660000
Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
ast#

[williamspatrick]

Please confirm the wget is working and you are ending up with a 32 MB file. I ran this myself and it seems to work fine. I suspect your download is unsuccessful.

[williamspatrick]

~/sdk$ ./qemu-system-arm -m 256 -M romulus-bmc -nographic -drive file=./obmc-phosphor-image-romulus.static.mtd,format=raw,if=mtd

You mentioned that you once built with bitbake and it once worked, but then you gave an invocation as example like above. This is using “./“ for the image path, which is your current directory. Since the current directory is “SDK”, this is not the location of the bitbake image. I suggest changing the file parameter to point at your bitbake build tree. It is going to have something like “tmp/deploy/images” in the full path to the image.

Going back and forth further on GitHub is not likely to be productive. You would probably have more success asking in our Discord server for assistance so we can do more real-time investigation.

[mahendra-space]

Thanks Patrick Williams,

Actually, I am using only download image from "wget https://jenkins.openbmc.org/job/latest-master/label=docker-builder,target=romulus/lastSuccessfulBuild/artifact/openbmc/build/tmp/deploy/images/romulus/obmc-phosphor-image-romulus.static.mtd" which is in my "sdk" path only . I mean current directory.

Thanks,

[cometzero]

Hi, @mahendra-space and @williamspatrick,

Did you resolve this issue? Actually, I'm facing same issue on my envionment.
I followed the guide1. First booting was successful but second boot was same with @mahendra-space 's case.
I feel like some services or programs on the first booting will overwrite the kernel region.

qemu-system-arm: warning: Aspeed iBT has no chardev backend
qemu-system-arm: warning: nic ftgmac100.1 has no peer


U-Boot 2019.04 (May 30 2023 - 06:05:47 +0000)

SOC : AST2500-A1 
RST : Power On 
2nd Boot : Enable
LPC Mode : SIO:Enable : SuperIO-2e
Eth : MAC0: RMII/NCSI, , MAC1: RMII/NCSI, 
Model: Romulus BMC
DRAM:  192 MiB (capacity:256 MiB, VGA:64 MiB, ECC:off)
MMC:   
Loading Environment from SPI Flash... SF: Detected n25q256a with page size 256 Bytes, erase size 4 KiB, total 32 MiB
OK
In:    serial@1e784000
Out:   serial@1e784000
Err:   serial@1e784000
Net:   ftgmac100_probe - NCSI detected

Warning: ethernet@1e660000 (eth0) using random MAC address - de:16:60:26:de:1c
eth0: ethernet@1e660000
Hit any key to stop autoboot:  0 
Wrong Image Format for bootm command
ERROR: can't get kernel image!

[amboar]

Can you please paste the output of printenv at the u-boot prompt (stop the autoboot process by hitting a key)?

[cometzero]

hi @amboar , here is my result.

U-Boot 2019.04 (May 30 2023 - 06:05:47 +0000)

SOC : AST2500-A1 
RST : Power On 
2nd Boot : Enable
LPC Mode : SIO:Enable : SuperIO-2e
Eth : MAC0: RMII/NCSI, , MAC1: RMII/NCSI, 
Model: Romulus BMC
DRAM:  192 MiB (capacity:256 MiB, VGA:64 MiB, ECC:off)
MMC:   
Loading Environment from SPI Flash... SF: Detected n25q256a with page size 256 Bytes, erase size 4 KiB, total 32 MiB
OK
In:    serial@1e784000
Out:   serial@1e784000
Err:   serial@1e784000
Net:   ftgmac100_probe - NCSI detected

Warning: ethernet@1e660000 (eth0) using random MAC address - 02:ef:31:36:51:ea
eth0: ethernet@1e660000
Hit any key to stop autoboot:  0 
ast# printenv
baudrate=115200
bootargs=console=ttyS4,115200n8 root=/dev/ram rw
bootcmd=bootm 20100000
bootdelay=2
bootfile=all.bin
fdtcontroladdr=89f941d8
gatewayip=192.168.0.1
ipaddr=192.168.0.45
netmask=255.255.255.0
serverip=192.168.0.81
stderr=serial@1e784000
stdin=serial@1e784000
stdout=serial@1e784000
trace_args=trace_events=fsi_slave_init,fsi_slave_invalid_cfam,fsi_dev_init,
verify=yes

Environment size: 383/131068 bytes
ast# boot
Wrong Image Format for bootm command
ERROR: can't get kernel image!
ast#

[cometzero]

Once I revert the environment variables using below command, I was able to boot well.

env default -f -a
saveenv

[amboar]

What does printenv bootcmd say after you run env default -f -a ; saveenv ?

In the past I've seen this:

ast# printenv bootcmd
bootcmd=bootm 20100000
ast# setenv bootcmd bootm 20080000
ast# boot
## Loading kernel from FIT Image at 20080000 ...
...

[cometzero]

What does printenv bootcmd say after you run env default -f -a ; saveenv ?

Same as before. All other variables are same as well.

ast# printenv bootcmd
bootcmd=bootm 20080000

[amboar]

It's not the same as before. In your printenv output above where the boot failed, you have:

bootcmd=bootm 20100000

[cometzero]

Oh. The address has been changed from 20080000 to 20100000 from the second boot :(