ABF023
-
Posts
20 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by ABF023
-
-
hi ManoftheSea~🥺
-
Maybe it can help you
-
Probably understood~ Thank you for all your help and replies, look forward to the new version to solve these problems, thank you again ~~
-
hi~ManoftheSea：
here's another problem.When I full-upgrade, the network does not start automatically, I need to execute:
root@espressobin:~# ifconfig eth0 up
root@espressobin:~# dhclient wan
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
root@espressobin:~#After execution, I can get the LAN IP, but I can't resolve the domain name, and then I add dns to /etc/resolv.conf to resolve the domain name normally
When I restart, I need to repeat the operation again, how can I get it up and running automatically?
-
This can be executed, but there is no information output..Only one ‘disabled’ output
root@espressobin:~# cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000/status
disabledroot@espressobin:~#
-
39 minutes ago, ManoftheSea said:
Sorry, I provided the directory, yes. Cat the "status" file within it - that should not say "disabled". If it is, your FDT is wrong. If it's enabled... hmm, I'll have to think more about that one.
Do you have the dtb file available to u-boot? In /dtb/ or /boot/dtb?
Yes, it's in there，thanks
root@espressobin:/boot/dtb/marvell# ls armada-3720-db.dtb armada-8040-mcbin-singleshot.dtb armada-3720-espressobin.dtb armada-8040-puzzle-m801.dtb armada-3720-espressobin-emmc.dtb armada-8080-db.dtb armada-3720-espressobin-ultra.dtb cn9130-crb-A.dtb armada-3720-espressobin-v7.dtb cn9130-crb-B.dtb armada-3720-espressobin-v7-emmc.dtb cn9130-db-B.dtb armada-3720-turris-mox.dtb cn9130-db.dtb armada-3720-uDPU.dtb cn9131-db-B.dtb armada-7040-db.dtb cn9131-db.dtb armada-8040-clearfog-gt-8k.dtb cn9132-db-B.dtb armada-8040-db.dtb cn9132-db.dtb armada-8040-mcbin.dtb -
OK, yes. After adding scriptaddr, it starts normally
-
root@espressobin:~# cat /boot/armbianEnv.txt board_version=v7 verbosity=1 rootdev=UUID=ea6c33de-9fb0-4d48-afc8-639a9682ec9a rootfstype=ext4 fdtfile=marvell/armada-3720-espressobin-v7-emmc.dtb -
On 12/1/2022 at 2:40 AM, ManoftheSea said:
Can you tell me what FDT you're using? If you aren't passing the right tree, it may be disabling the emmc.
Check by:
"cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000"
root@espressobin:~# cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000 cat: /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000: Is a directory root@espressobin:~# cd /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000 root@espressobin:/proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000# ls '#address-cells' interrupts mmc-ddr-1_8v pinctrl-names bus-width marvell,pad-type mmc-hs400-1_8v reg clock-names marvell,xenon-emmc name '#size-cells' clocks marvell,xenon-tun-count non-removable status compatible mmccard@0 pinctrl-0
-
TIM-1.0 mv_ddr-devel-g251bc63 DDR4 16b 2GB 2CS WTMI-devel-18.12.1-1d97715 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.213V Setting clocks: CPU 1200 MHz, DDR 750 MHz CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06) Running on ESPRESSObin NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.6(release):a921da5e NOTICE: BL1: Built : 17:55:48, May 16 2022 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.6(release):a921da5e NOTICE: BL2: Built : 17:55:48, May 16 2022 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.6(release):a921da5e NOTICE: BL31: Built : 17:55:48, May 16 2022 U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000) DRAM: 2 GiB Core: 38 devices, 20 uclasses, devicetree: fit WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 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: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: ethernet@30000 Hit any key to stop autoboot: 0 => mmc list sdhci@d0000: 0 sdhci@d8000: 1 => mmc dev 0 MMC: no card present => mmc dev 1 switch to partitions #0, OK mmc1(part 0) is current device => mmcinfo Device: sdhci@d8000 Manufacturer ID: 15 OEM: 0 Name: 4FTE4R Bus Speed: 52000000 Mode: MMC High Speed (52MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 3.6 GiB Bus Width: 8-bit Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 3.6 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 512 KiB ENH Boot area 0 is not write protected Boot area 1 is not write protectedWhen I enter armbian, mmc cannot be detected........Several versions have the same problem, 22.11, 22.08, 22.05
root@espressobin:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 28.7G 0 disk └─sda1 8:1 1 28.4G 0 part / mtdblock0 31:0 0 3.9M 0 disk mtdblock1 31:1 0 64K 0 disk zram0 254:0 0 993.7M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 993.7M 0 disk /tmp root@espressobin:~# dmesg|grep -i mmc [ 1.393013] mmc0: SDHCI controller on d00d0000.sdhci [d00d0000.sdhci] using ADMA -
Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. [ ***] A start job is running for Wait for… to be Configured (57s / no limit)I stay here for a long time every time I start... Does anyone know why?
Then an error message appears:
[ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. [FAILED] Failed to start Wait for Network to be Configured. See 'systemctl status systemd-networkd-wait-online.service' for details. [ OK ] Reached target Network is Online. Starting LSB: Advanced IEEE 802.11 management daemon... Starting /etc/rc.local Compatibility... [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started /etc/rc.local Compatibility.Then when I follow the error prompt, the following message appears:
root@espressobin:~# systemctl status systemd-networkd-wait-online.service ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; > Active: failed (Result: exit-code) since Thu 2022-11-10 12:34:58 UTC; 5min> Docs: man:systemd-networkd-wait-online.service(8) Process: 667 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exit> Main PID: 667 (code=exited, status=1/FAILURE) CPU: 153ms Nov 10 12:34:58 espressobin systemd-networkd-wait-online[667]: Event loop faile> Nov 10 12:34:58 espressobin systemd[1]: systemd-networkd-wait-online.service: M> Nov 10 12:34:58 espressobin systemd[1]: systemd-networkd-wait-online.service: F> Nov 10 12:34:58 espressobin systemd[1]: Failed to start Wait for Network to be > Warning: journal has been rotated since unit was started, output may be incompl -
Thank you very much. The printenv information is as follows:
-
Is this problem the cause of u-boot or Armbian 22.08 Bullseye?
Thank you~ -
Thanks for replying, how do I enter debug mode?
23 minutes ago, Pali said:You need to debug it why it cannot load required file. Probably file does not exist or there is an error on that load line in that script.
-
Seems that you have broken /boot/boot.scr script on mmc 0:1 device (SD card?).On the SDcard is the latest Armbian 22.08 Bullseye ，
How do I fix this error? Please give me a hint...
-
I flashed my espressobin v7 with
bubt flash-image-DDR4-1g_1cs_5-1000_800.bin spi usb
and set u-boot prompt:
printenv ethaddr
env default -a
saveenv
After the boot
printenv：TIM-1.0 mv_ddr-devel-g251bc63 DDR4 16b 1GB 1CS WTMI-devel-18.12.1-1d97715 WTMI: system early-init CPU VDD voltage default value: 1.155V Setting clocks: CPU 1000 MHz, DDR 800 MHz CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06) Running on ESPRESSObin NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.6(release):a921da5e NOTICE: BL1: Built : 17:54:27, May 16 2022 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.6(release):a921da5e NOTICE: BL2: Built : 17:54:27, May 16 2022 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.6(release):a921da5e NOTICE: BL31: Built : 17:54:27, May 16 2022 U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000) DRAM: 1 GiB Core: 38 devices, 20 uclasses, devicetree: fit WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 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: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPIFlash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: ethernet@30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk sdhci@d0000.blk... Scanning disk sdhci@d8000.blk... Found 4 disks No EFI system partition ERROR: invalid device tree switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr load - load binary file from a filesystem Usage: load <interface> [<dev[:part]> [<addr> [<filename> [bytes [pos]]]]] - Load binary file 'filename' from partition 'part' on device type 'interface' instance 'dev' to address 'addr' in memory. 'bytes' gives the size to load in bytes. If 'bytes' is 0 or omitted, the file is read until the end. 'pos' gives the file byte position to start reading from. If 'pos' is 0 or omitted, the file is read from the start. ## Executing script at 06000000 Wrong image format for "source" command SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC ERROR: invalid device tree starting USB... Bus usb@58000: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 Bus usb@5e000: USB EHCI 1.00 scanning bus usb@58000 for devices... 1 USB Device(s) found scanning bus usb@5e000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device scanning bus for devices... Device 0: unknown device (NULL udevice *): mvneta_setup_txqs: can't create txq=0 BOOTP broadcast 1 timeout: packet not sent BOOTP broadcast 2 timeout: packet not sent BOOTP broadcast 3 timeout: packet not sent BOOTP broadcast 4 timeout: packet not sent .................. ..............
any help? thanks more~
-
I flashed my espressobin v7 with
bubt flash-image-DDR4-1g_1cs_5-1000_800.bin spi usb
and set u-boot prompt:
printenv ethaddr env default -a saveenvAfter the boot
printenv：TIM-1.0 mv_ddr-devel-g251bc63 DDR4 16b 1GB 1CS WTMI-devel-18.12.1-1d97715 WTMI: system early-init CPU VDD voltage default value: 1.155V Setting clocks: CPU 1000 MHz, DDR 800 MHz CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06) Running on ESPRESSObin NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.6(release):a921da5e NOTICE: BL1: Built : 17:54:27, May 16 2022 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.6(release):a921da5e NOTICE: BL2: Built : 17:54:27, May 16 2022 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.6(release):a921da5e NOTICE: BL31: Built : 17:54:27, May 16 2022 U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000) DRAM: 1 GiB Core: 38 devices, 20 uclasses, devicetree: fit WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 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: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPIFlash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: ethernet@30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk sdhci@d0000.blk... Scanning disk sdhci@d8000.blk... Found 4 disks No EFI system partition ERROR: invalid device tree switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr load - load binary file from a filesystem Usage: load <interface> [<dev[:part]> [<addr> [<filename> [bytes [pos]]]]] - Load binary file 'filename' from partition 'part' on device type 'interface' instance 'dev' to address 'addr' in memory. 'bytes' gives the size to load in bytes. If 'bytes' is 0 or omitted, the file is read until the end. 'pos' gives the file byte position to start reading from. If 'pos' is 0 or omitted, the file is read from the start. ## Executing script at 06000000 Wrong image format for "source" command SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC ERROR: invalid device tree starting USB... Bus usb@58000: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 Bus usb@5e000: USB EHCI 1.00 scanning bus usb@58000 for devices... 1 USB Device(s) found scanning bus usb@5e000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device scanning bus for devices... Device 0: unknown device (NULL udevice *): mvneta_setup_txqs: can't create txq=0 BOOTP broadcast 1 timeout: packet not sent BOOTP broadcast 2 timeout: packet not sent BOOTP broadcast 3 timeout: packet not sent BOOTP broadcast 4 timeout: packet not sent .................. ..............
-
Thank‘s for your reply. My version is V5, which confirms that EMMC has been installed on the backplane.
-
when I used the command "nand-sata-install" ,then i select The first one, install Armbian from the SD card to the Built in emmc, After step-by-step execution, I will prompt poweroff. Then I remove the SD card and prepare to start from EMMC. However, the following error prompt appears. I cannot enter the system from EMMC normally，Please help me, thank you
TIM-1.0 WTMI-devel-18.12.1-e6bb176 WTMI: system early-init CPU VDD voltage default value: 1.155V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 16:23:10, May 21 2019 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 16:23:11, May 21 2019 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 16:2 U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [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 w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found / ** Bad device usb 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device usb 0 ** ## Executing script at 06d00000 Wrong image format for "source" command scanning bus for devices... Device 0: unknown device / ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command / ** File not found /boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ 1119 bytes read in 15 ms (72.3 KiB/s) ## Executing script at 06d00000 240 bytes read in 4 ms (58.6 KiB/s) Card did not respond to voltage select! ** Bad device mmc 0 ** Card did not respond to voltage select! ** Bad device mmc 0 ** Card did not respond to voltage select! ** Bad device mmc 0 ** Card did not respond to voltage select! ** Bad device mmc 0 ** Bad Linux ARM64 Image magic! / Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 06d00000 Wrong image format for "source" command Marvell>>
espressobin can't detect emmc
in Marvell mvebu
Posted · Edited by ABF023
hi ManoftheSea~
Except add the "v5 emmc" and "v7 emmc" configurations to it， How to use UEFI booting?
I would like to refer to your usage
Thank you.