Setting up a system for first time

[rgrs]

Hi,

I'm trying to setup a new system for the very first time.
The board has two SPI NOR for BMC flash.

If I flash same image on both SPI, WebUI displays only one entry since versioning is same.
When I flash two different images in each SPI, activation of second image is not working.
U-boot goes into a loop and is not able boot.

Do we have any sequence to be followed when flashing the images?

UBInfo:
-------
root at srv1:~# ubinfo -d 0 -n 0
Volume ID:   0 (on ubi0)
Type:        static
Alignment:   1
Size:        43 LEBs (2812544 bytes, 2.6 MiB)
Data bytes:  2771656 bytes (2.6 MiB)
State:       OK
Name:        kernel-e2be67bb
Character device major/minor: 246:1
root at srv1:~# ubinfo -d 0 -n 1
Volume ID:   1 (on ubi0)
Type:        static
Alignment:   1
Size:        318 LEBs (20799744 bytes, 19.8 MiB)
Data bytes:  20754432 bytes (19.7 MiB)
State:       OK
Name:        rofs-e2be67bb
Character device major/minor: 246:2
root at srv1:~# ubinfo -d 0 -n 2
Volume ID:   2 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        97 LEBs (6344576 bytes, 6.0 MiB)
State:       OK
Name:        rwfs
Character device major/minor: 246:3
root at srv1:~# ubinfo -d 4 -n 0
Volume ID:   0 (on ubi4)
Type:        static
Alignment:   1
Size:        43 LEBs (2812544 bytes, 2.6 MiB)
Data bytes:  2771320 bytes (2.6 MiB)
State:       OK
Name:        kernel-63eb9784
Character device major/minor: 245:1
root at srv1:~# ubinfo -d 4 -n 1
Volume ID:   1 (on ubi4)
Type:        static
Alignment:   1
Size:        318 LEBs (20799744 bytes, 19.8 MiB)
Data bytes:  20750336 bytes (19.7 MiB)
State:       OK
Name:        rofs-63eb9784
Character device major/minor: 245:2
root at srv1:~# ubinfo -d 4 -n 2
Volume ID:   2 (on ubi4)
Type:        dynamic
Alignment:   1
Size:        97 LEBs (6344576 bytes, 6.0 MiB)
State:       OK
Name:        rwfs
Character device major/minor: 245:3
root at srv1:~#

Logs:
-------
U-Boot 2016.07 (Apr 21 2020 - 06:22:46 +0000)

 Watchdog enabled
DRAM:  496 MiB
Flash: 64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   eth0, eth1
Hit any key to stop autoboot:  0
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "mtd=2", size 31 MiB)
ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes
ubi0: min./max. I/O unit sizes: 1/1, sub-page size 1
ubi0: VID header offset: 64 (aligned 64), data offset: 128
ubi0: good PEBs: 504, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1180811006
ubi0: available PEBs: 42, total reserved PEBs: 462, PEBs reserved for bad PEB handling: 0
Read 0 bytes from volume kernel-63eb9784 to 80800000
Volume kernel-63eb9784 not found!
Wrong Image Format for bootm command
ERROR: can't get kernel image!

DRAM Init-V12-DDR4
0abc1-4Gb-Done
Read margin-DL:0.3823/DH:0.3921 CK (min:0.30)

U-Boot 2016.07 (Apr 21 2020 - 06:22:46 +0000)

Watchdog enabled
DRAM:  496 MiB
Flash: 64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   eth0, eth1
Hit any key to stop autoboot:  0
ast# printenv
63eb9784=1
baudrate=115200
bootalt=run wdt2bite
bootargs=console=ttyS4,115200n8 ubi.mtd=obmc-ubi,0,0,0 ubi.mtd=alt-obmc-ubi,0,0,4 ro rootfstype=squashfs
bootcmd=run set_bootargs; run obmc_bootcmd
bootdelay=2
do_rwreset=if test "${rwreset}" = "true"; then ubi remove rwfs; ubi create rwfs ${rwfs_size}; fi
e2be67bb=0
eth1addr=00:00:00:01:02:04
ethact=eth0
ethaddr=00:00:00:01:02:03
kernelname=kernel-e2be67bb
loadaddr=80800000
mtdids=nor0=bmc
mtdparts=mtdparts=bmc:384k(u-boot),128k(u-boot-env),-(obmc-ubi)
obmc_bootcmd=ubi part obmc-ubi; run do_rwreset; ubi read ${loadaddr} ${kernelname}; bootm ${loadaddr} || run bootalt
root=/dev/ubiblock4_1
rwfs_size=0x600000
set_bootargs=setenv bootargs console=ttyS4,115200n8 ubi.mtd=obmc-ubi,0,0,0 ubi.mtd=alt-obmc-ubi,0,0,4 ro rootfstype=squashfs ubi.block=${ubiblock} root=${root}
spi_dma=yes
stderr=serial
stdin=serial
stdout=serial
ubiblock=4,1
verify=yes
wdt2bite=mw.l 0x1e785024 0xa 1; mw.b 0x1e78502c 0xb3 1

Environment size: 1014/65531 bytes
ast#
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200423/b2311fa7/attachment-0001.htm>