Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Failure to upgrade to 24.04 client's SG-1100 via USB now stuck in Marvell.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 5 Posters 1.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      flatsphere
      last edited by

      Hi team,

      After several failed attempts to upgrade via upgrade feature in pfSense, I tried upgrading via USB. I received an image file from Netgate (pfSense-plus-installer-24.02-BETA2-aarch64-20240312-0600.img) earlier today. Followed instructions using Balena Etcher.
      Restarted, typed USB RESET when ready and RUN USBRECOVERY... process failed multiple times. Tried different sticks and both ports.
      Still stuck in Marvell.
      Here's some of the message:

      Retry count exceeded; starting again.dtb
      *** ERROR: serverip' not set0.dtb *** ERROR: serverip' not setormation/

      Starting EFI application at 07000000 ...

      Card did not respond to voltage select!
      Scanning disk sdhci@d0000.blk...
      Disk sdhci@d0000.blk not ready1.7 MiB/s)
      Scanning disk sdhci@d8000.blk...iB/s)
      Found 1 disksFI application at 07000000 ...
      fdt_find_or_add_subnode: chosen: FDT_ERR_BADSTRUCTURE
      ERROR: /chosen node create failed

      • must RESET the board to recover.

      ERROR: Failed to process device tree

      Application terminated, r = 9223372036854775786

      Help! :)
      Rafael

      F 1 Reply Last reply Reply Quote 0
      • F
        flatsphere @flatsphere
        last edited by

        @flatsphere Latest message:

        TIM-1.0
        WTMI-devel-18.12.1-1a13f2f
        WTMI: system early-init
        SVC REV: 5, CPU VDD voltage: 1.237V
        NOTICE: Booting Trusted Firmware
        NOTICE: BL1: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
        NOTICE: BL1: Built : 10:16:46, Oct 13 2021
        NOTICE: BL1: Booting BL2
        NOTICE: BL2: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
        NOTICE: BL2: Built : 10:16:50, Oct 13 2021
        NOTICE: BL1: Booting BL31
        NOTICE: BL31: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
        NOTICE: BL31: Built : 10

        U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Oct 13 2021 - 10:14:54 -0300)

        Model: Netgate 1100
        CPU 1200 [MHz]
        L2 800 [MHz]
        TClock 200 [MHz]
        DDR 750 [MHz]
        DRAM: 1 GiB
        Comphy chip #0:
        Comphy-0: USB3 5 Gbps
        Comphy-1: PEX0 2.5 Gbps
        Comphy-2: SATA0 6 Gbps
        SATA link 0 timeout.
        AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
        flags: ncq led only pmp fbss pio slum part sxs
        PCIE-0: Link down
        MMC: sdhci@d0000: 0, sdhci@d8000: 1
        Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
        OK
        Model: Netgate 1100
        Net: eth0: neta@30000 [PRIME]
        Hit any key to stop autoboot: 0

        Error: "setLED" not defined

        Error: "m2boot" not defined

        Marvell>>

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Do you have the full output after running usbrecovery?

          @flatsphere said in Failure to upgrade to 24.04 client's SG-1100 via USB now stuck in Marvell.:

          Error: "setLED" not defined
          Error: "m2boot" not defined

          Those are commands from the 2100. If it's also trying to the use the 2100 FDT file that would cause it to fail.

          Check the output of printenv.

          F 1 Reply Last reply Reply Quote 0
          • F
            flatsphere @stephenw10
            last edited by

            @stephenw10 Interesting. The file I received said it was for both the 2100 and 1100.
            Here is what I captured:

            Marvell>> printenv
            arch=arm
            baudrate=115200
            board=mvebu_armada-37xx
            board_name=mvebu_armada-37xx
            boot_file=efi/boot/bootaa64.efi
            bootcmd=run setLED; run m2boot;
            bootdelay=2
            console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000
            cpu=armv8
            dtb_name=armada-3720-netgate-1100.dtb
            dtb_name_old=armada-3720-sg1100.dtb
            emmcboot=mmc rescan; setenv loaddev mmc; setenv loadunit 1; if fatls $loaddev $loadunit:2 /; then run pfsenseboot; fi;
            eth1addr=00:51:82:11:22:01
            eth2addr=00:51:82:11:22:02
            eth3addr=00:51:82:11:22:03
            ethact=neta@30000
            ethaddr=f0:ad:4e:23:36:5f
            ethprime=eth0
            extra_params=pci=pcie_bus_safe
            fdt_addr_r=0x6f00000
            fdt_high=0xffffffffffffffff
            fdt_name=fdt.dtb
            fdtcontroladdr=3f62d490
            gatewayip=10.4.50.254
            get_images=tftpboot $kernel_addr_r $image_name; tftpboot $fdt_addr_r $fdt_name; run get_ramfs
            get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramdisk_addr_r 0x8000000; tftpboot $ramdisk_addr_r $ramfs_name; else setenv ramdisk_addr_r -;fi
            hostname=marvell
            image_name=Image
            initrd_addr=0xa00000
            initrd_size=0x2000000
            ipaddr=0.0.0.0
            kernel_addr_r=0x7000000
            loadaddr=0x7000000
            loaddev=scsi
            loadunit=0
            net=dhcp; tftp $fdt_addr_r $dtb_name; tftp $kernel_addr_r loader.efi; fdt addr $fdt_addr_r; fdt addr $fdt_addr_r; fdt set / sn $serial; fdt set /soc/internal-regs/ethernet local-mac-address $ethaddr; bootefi $kernel_addr_r $fdt_addr_r;
            netdev=eth0
            netmask=255.255.255.0
            pfsenseboot=if fatls $loaddev $loadunit:2 /armada-3720-netgate-1100.dtb ; then setenv dtb $dtb_name; else setenv dtb $dtb_name_old; fi; load $loaddev $loadunit:1 $kernel_addr_r $boot_file; load $loaddev $loadunit:2 $fdt_addr_r $dtb; fdt addr $fdt_addr_r; fdt set / sn $serial; fdt set /soc/internal-regs/ethernet local-mac-address $ethaddr; bootefi $kernel_addr_r $fdt_addr_r;
            ramdisk_addr_r=0x8000000
            ramfs_name=-
            recovery=run usbboot;
            root=root=/dev/nfs rw
            rootpath=/srv/nfs/
            scsiboot=scsi reset; setenv loaddev scsi; setenv loadunit 0; if fatls $loaddev $loadunit:2 /; then run pfsenseboot; fi;
            serial=NTG2210001956
            serverip=0.0.0.0
            set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath,tcp,v3 $extra_params $cpuidle
            soc=mvebu
            stderr=serial@12000
            stdin=serial@12000
            stdout=serial@12000
            usbboot=usb reset; setenv loaddev usb; setenv loadunit 0; if fatls $loaddev $loadunit:2 /; then run pfsenseboot; fi;
            usbrecovery=mmc dev 1; mmc erase 0 400000; run usbboot;
            vendor=Marvell

            Environment size: 2544/65532 bytes

            Rafael

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Hmm, OK well the bootcmd is wrong but the dtb files are correct. That command would only ever get set normally on a 3100 after adding an m.2 drive. That's obviously not possible on the 1100 so I have no explanation as to how it was set here. It pretty much must have been set manually at some point.

              Anyway it;s easily fixed. At the Marvel >> prompt run:
              setenv bootcmd 'run emmcboot;'
              saveenv
              reset

              See if that then boots as expected.

              F D 2 Replies Last reply Reply Quote 0
              • F
                flatsphere @stephenw10
                last edited by

                @stephenw10 Perfect!
                After the message below and system stopping, I was able restart and use the USB to update to ver 24.x and a fresh install.
                Thanks!
                Rafael

                Marvell>> setenv bootcmd 'run emmcboot;'
                Marvell>> saveenv
                Saving Environment to SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
                Erasing SPI flash...Writing to SPI flash...done
                OK
                Marvell>> reset
                resetting ...
                TIM-1.0
                WTMI-devel-18.12.1-1a13f2f
                WTMI: system early-init
                SVC REV: 5, CPU VDD voltage: 1.237V
                NOTICE: Booting Trusted Firmware
                NOTICE: BL1: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
                NOTICE: BL1: Built : 10:16:46, Oct 13 2021
                NOTICE: BL1: Booting BL2
                NOTICE: BL2: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
                NOTICE: BL2: Built : 10:16:50, Oct 13 2021
                NOTICE: BL1: Booting BL31
                NOTICE: BL31: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
                NOTICE: BL31: Built : 10

                U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Oct 13 2021 - 10:14:54 -0300)

                Model: Netgate 1100
                CPU 1200 [MHz]
                L2 800 [MHz]
                TClock 200 [MHz]
                DDR 750 [MHz]
                DRAM: 1 GiB
                Comphy chip #0:
                Comphy-0: USB3 5 Gbps
                Comphy-1: PEX0 2.5 Gbps
                Comphy-2: SATA0 6 Gbps
                SATA link 0 timeout.
                AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
                flags: ncq led only pmp fbss pio slum part sxs
                PCIE-0: Link down
                MMC: sdhci@d0000: 0, sdhci@d8000: 1
                Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
                OK
                Model: Netgate 1100
                Net: eth0: neta@30000 [PRIME]
                Hit any key to stop autoboot: 0
                Card did not respond to voltage select!
                ** No partition table - mmc 1 **

                1 Reply Last reply Reply Quote 1
                • D
                  dscheive @stephenw10
                  last edited by

                  @stephenw10 I'm having the same issue but even after running the commands it won't boot. What else can I do?

                  patient0P D 2 Replies Last reply Reply Quote 0
                  • patient0P
                    patient0 @dscheive
                    last edited by

                    @dscheive post the complete output you get when starting your SG-1100. For that you have to connect to the serial console.

                    https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.html

                    1 Reply Last reply Reply Quote 0
                    • D
                      dscheive @dscheive
                      last edited by

                      @dscheive I got it working now after issuing
                      Marvell>> run usbrecovery

                      patient0P 1 Reply Last reply Reply Quote 1
                      • patient0P
                        patient0 @dscheive
                        last edited by

                        @dscheive Mmmh, ok. usbrecovery does boot of an USB stick for intallation.

                        https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html#boot-the-installation-media

                        That is for the normal boot up.

                        1 Reply Last reply Reply Quote 0
                        • B
                          benslzr
                          last edited by

                          Default bootcmd for 2100, incase it helps anyone. This is for using default memory not usb or m2.

                          bootcmd=run setLED; run mmcboot; run scsiboot; run usbboot; run net;

                          So instead of...
                          Marvell>> setenv bootcmd 'run emmcboot;'
                          Marvell>> saveenv
                          Marvell>> reset

                          It would be...
                          Marvell>> setenv bootcmd 'run mmcboot;'
                          Marvell>> saveenv
                          Marvell>> reset

                          I had issue where I tried to get out of Marvell and really just messed up my bootcmd. I learned some more and found solution.

                          1 Reply Last reply Reply Quote 1
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            You should really use: `setenv bootcmd 'setLED; run mmcboot;'

                            Otherwise you won't see the expected LED sequence at boot.Though it would still boot fine.

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.