marvell development board (DB-MV784MP-GP) damaged uboot

I saw that this development board is supported on the main line of uboot, but I didn't find the relevant cross compilation tool chain. I wrote a damaged file on the original uboot and can't start it now

The development board supports the kwboot tool. The kwboot operation log is as follows, but NAND is not recognized after startup

luo@ubuntu:~/boot/1/usr/share/uboot/db-mv784mp-gp$ kwboot -t -d -b u-boot-spl.kwb -B 115200 /dev/ttyUSB0 -p
Sending debug message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
 10 % [......................................................................]
 12 % [......................................................................]
 13 % [...................................................................
U-Boot SPL 2021.10 (Oct 04 2021 - 00:00:00 +0000)
High speed PHY - Version: 2.1.5 (COM-PHY-V20)
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 5.7.4
DDR3 Training Sequence - Number of DIMMs detected: 1
DDR3 Training Sequence - Ended Successfully
Trying to boot from BOOTROM
Returning to BootROM (return address 0xffff0aa0)...
...]
 14 % [......................................................................]
 16 % [......................................................................]
 17 % [......................................................................]
 19 % [......................................................................]
 20 % [......................................................................]
 21 % [......................................................................]
 23 % [......................................................................]
 24 % [......................................................................]
 25 % [......................................................................]
 27 % [......................................................................]
 28 % [......................................................................]
 29 % [......................................................................]
 31 % [......................................................................]
 32 % [......................................................................]
 33 % [......................................................................]
 35 % [......................................................................]
 36 % [......................................................................]
 38 % [......................................................................]
 39 % [......................................................................]
 40 % [......................................................................]
 42 % [......................................................................]
 43 % [......................................................................]
 44 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 48 % [......................................................................]
 50 % [......................................................................]
 51 % [......................................................................]
 52 % [......................................................................]
 54 % [......................................................................]
 55 % [......................................................................]
 57 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 61 % [......................................................................]
 62 % [......................................................................]
 63 % [......................................................................]
 65 % [......................................................................]
 66 % [......................................................................]
 67 % [......................................................................]
 69 % [......................................................................]
 70 % [......................................................................]
 72 % [......................................................................]
 73 % [......................................................................]
 74 % [......................................................................]
 76 % [......................................................................]
 77 % [......................................................................]
 78 % [......................................................................]
 80 % [......................................................................]
 81 % [......................................................................]
 82 % [......................................................................]
 84 % [......................................................................]
 85 % [......................................................................]
 86 % [......................................................................]
 88 % [......................................................................]
 89 % [......................................................................]
 91 % [......................................................................]
 92 % [......................................................................]
 93 % [......................................................................]
 95 % [......................................................................]
 96 % [......................................................................]
 97 % [......................................................................]
 99 % [............................................]
[Type Ctrl-\ + c to quit]


U-Boot 2021.10 (Oct 04 2021 - 00:00:00 +0000)

SoC:   MV78460-B0 at 1600 MHz
I2C:   ready
DRAM:  4 GiB (800 MHz, 64-bit, ECC not enabled)
NAND:  0 MiB
Loading Environment from SPIFlash... SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

Model: Marvell Armada XP Development Board DB-MV784MP-GP
Board: Marvell DB-MV784MP-GP
Net:   
Error: ethernet@70000 address not set.

Error: ethernet@74000 address not set.

Error: ethernet@30000 address not set.

Error: ethernet@34000 address not set.
No ethernet found.

=>

The uboot file I used is the u-boot-spl.kwb extracted from the uboot-images-armv7-2021.10-1.fc36.noarch.rpm filehttp://rpmfind.net/linux/rpm2html/search.php?query=uboot-images-armv7

I want to recover the damaged uboot file on SPI flash. How should I make the uboot file

luo,

> I saw that this development board is supported on
> the main line of uboot, but I didn't find the
> relevant cross compilation tool chain. I wrote a
> damaged file on the original uboot and can't start
> it now

> I want to recover the damaged uboot file on SPI
> flash. How should I make the uboot file

I don't have this board so cannot help you with flashing (don't want to make it worse). But I can build the u-boot images for you if needed.

If you want to run stock FW only, then find the FW recovery procedure for your box (which box is this?). And then look at how the vendor flash u-boot images to SPI flash.

=====

However, since you have already found a working u-boot image. And can kwboot with it. You can get it booting before worrying about flashing.

- The 1st step is to find the correct envs for this box. Either you have saved the listing, or you can find a listing from a good box. This is most important.

- Enter the envs one-by-one in u-boot console, and try booting stock FW with it.

Once you can boot into stock FW, if your goal is to boot latest Debian, then you can consider booting to rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 with this DTB:

armada-xp-db.dtb

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank you

This is not a box, this is Marvell's development board, model db-mv784mp-gp

When I check the armada-xp-db.dts file, there is a comment at the beginning:

// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
 * Device Tree file for Marvell Armada XP development board
 * (DB-MV784MP-GP)
 *
 * Copyright (C) 2013-2014 Marvell
 *
 * Lior Amsalem <alior@marvell.com>
 * Gregory CLEMENT <gregory.clement@free-electrons.com>
 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 *
 * Note: this Device Tree assumes that the bootloader has remapped the
 * internal registers to 0xf1000000 (instead of the default
 * 0xd0000000). The 0xf1000000 is the default used by the recent,
 * DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
 * boards were delivered with an older version of the bootloader that
 * left internal registers mapped at 0xd0000000. If you are in this
 * situation, you should either update your bootloader (preferred
 * solution) or the below Device Tree should be adjusted.
 */

After I insert the DTB file into the kernel, I can't start, and ttys0 has no output, so I guess the original uboot doesn't support this DTB file,

Can you help me make uboot launched from SPI



Edited 1 time(s). Last edit at 10/08/2021 09:52PM by luo.

luo,

> After I insert the DTB file into the kernel, I
> can't start, and ttys0 has no output, so I guess
> the original uboot doesn't support this DTB file,

I need to see serial boot log, as always.

> Can you help me make uboot launched from SPI

Sorry, not possible for me to do that at this time (too time consuming do it remotely, not sitting in front of the board).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank you bodhi

The translation software misunderstood my meaning

I mean, you help me build a u-boot image (stored on SPI flash)

Or you taught me how to build a u-boot image,

Or modify it from the existing uboot-spl.kwb file launched from UART



Edited 1 time(s). Last edit at 10/08/2021 11:30PM by luo.

> Or modify it from the existing uboot-spl.kwb file
> launched from UART

You've already did kwboot with UART.

So my suggestion above:

https://forum.doozan.com/read.php?3,126044,126059#msg-126059

Quote

However, since you have already found a working u-boot image. And can kwboot with it. You can get it booting before worrying about flashing.

- The 1st step is to find the correct envs for this box. Either you have saved the listing, or you can find a listing from a good box. This is most important.

- Enter the envs one-by-one in u-boot console, and try booting stock FW with it.

Once you can boot into stock FW, if your goal is to boot latest Debian, then you can consider booting to rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 with this DTB:

armada-xp-db.dtb

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Uboot startup log：

U-Boot 2021.10 (Oct 08 2021 - 23:58:07 -0700)

SoC:   MV78460-B0 at 1600 MHz
I2C:   ready
DRAM:  4 GiB (800 MHz, 64-bit, ECC not enabled)
NAND:  0 MiB
Loading Environment from SPIFlash... SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

Model: Marvell Armada XP Development Board DB-MV784MP-GP
Board: Marvell DB-MV784MP-GP
Net:   
Error: ethernet@70000 address not set.

Error: ethernet@74000 address not set.

Error: ethernet@30000 address not set.

Error: ethernet@34000 address not set.
No ethernet found.

I used the bubt command to burn uboot-spl.kwb, and an error occurred：

maevell:>bubt
Burning U-Boot image "u-boot-spl.kwb" from "tftp" to "spi"
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@74000'
mdio_register: non unique device name 'ethernet@30000'
mdio_register: non unique device name 'ethernet@34000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
No ethernet found.
mdio_register: non unique device name 'ethernet@70000'
mdio_register: non unique device name 'ethernet@70000'
bubt cmd does not support this SoC device or family!
Error: Image header verification failed
maevell:>

This error is whether the uboot does not initialize the network port or the uboot environment variable is configured incorrectly?

If the uboot environment variable is incorrectly configured, which entries do I need to configure

I also reported an error when I read the uboot file from the USB disk

maevell:>usb reset
resetting USB...
Bus usb@50000: USB EHCI 1.00
Bus usb@51000: USB EHCI 1.00
scanning bus usb@50000 for devices... 1 USB Device(s) found
scanning bus usb@51000 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
maevell:>fatls usb 0:1
            boot/
            efi/
            sources/
            support/
      128   autorun.inf
   386976   bootmgr
  1168736   bootmgr.efi
    80576   setup.exe
            System Volume Information/
   659712   u-boot.kwb
   827856   uboot214.bin

6 file(s), 5 dir(s)

maevell:>fatload usb 0:1 0x1000000 u-boot.kwb
** Reading file would overwrite reserved memory **
Failed to load 'u-boot.kwb'
maevell:>

** Reading file would overwrite reserved memory **
Is it a memory initialization error



Edited 1 time(s). Last edit at 10/09/2021 05:03AM by luo.

luo,

Read again what I posted above:

https://forum.doozan.com/read.php?3,126044,126079#msg-126079

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)