Jump to content

Search the Community

Showing results for tags 'espressobin'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. I was running espressobin v7 with Welcome to Armbian 21.08.1 Bullseye with Linux 5.10.60-mvebu64 and made an upgrade in a regular way : # apt upgrade The following packages will be upgraded: apache2 apache2-bin apache2-data apache2-dev apache2-utils armbian-bsp-cli-espressobin armbian-config armbian-firmware armbian-zsh asterisk asterisk-config asterisk-modules asterisk-voicemail avahi-autoipd base-files bash curl deb.torproject.org-keyring dirmngr distro-info-data dpkg dpkg-dev ffmpeg gnupg gnupg-l10n gnupg-utils gnupg2 gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv gzip hostapd ifenslave inetutils-inetd inetutils-telnet libapache2-mod-php7.4 libavahi-client3 libavahi-common-data libavahi-common3 libavcodec58 libavdevice58 libavfilter7 libavformat58 libavresample4 libavutil56 libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libcups2 libcurl3-gnutls libcurl4 libdpkg-perl libfreetype6 libfribidi0 libgnutls30 libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 libldap-2.4-2 libldap2-dev libldb2 liblzma5 libnm0 libnss-myhostname libntfs-3g883 libpam-systemd libpcre2-16-0 libpcre2-32-0 libpcre2-8-0 libpcre2-dev libpcre2-posix2 libpostproc55 libpq5 libsdl2-2.0-0 libsmbclient libsnmp-base libsnmp40 libssl-dev libssl1.1 libswresample3 libswscale5 libsystemd0 libtiff5 libtirpc-common libtirpc-dev libtirpc3 libudev1 libwbclient0 libxml2 libxslt1.1 linux-dtb-current-mvebu64 linux-image-current-mvebu64 linux-libc-dev linux-u-boot-espressobin-current locales logrotate nano network-manager ntfs-3g openssh-client openssh-server openssh-sftp-server openssl php7.4 php7.4-cli php7.4-common php7.4-curl php7.4-json php7.4-opcache php7.4-readline python3-ldb python3-samba rsyslog samba samba-common samba-common-bin samba-libs smbclient systemd systemd-sysv tcpdump tor tor-geoipdb tzdata udev unzip wireless-regdb xz-utils zlib1g ... update-initramfs: Converting to u-boot format update-initramfs: Converting to u-boot FIT image FIT description: EspressoBIN 3720 FIT Image Created: Sun Oct 23 13:08:21 2022 Image 0 (kernel) Description: Vanilla Linux kernel Created: Sun Oct 23 13:08:21 2022 Type: Kernel Image Compression: lzma compressed Data Size: 6882687 Bytes = 6721.37 KiB = 6.56 MiB Architecture: AArch64 OS: Linux Load Address: 0x07000000 Entry Point: 0x07000000 Hash algo: sha1 Hash value: c8d92b9c244fdcc9fb56f640d05e6fc4d3f7ffb6 Image 1 (ramdisk) Description: Boot ramdisk Created: Sun Oct 23 13:08:21 2022 Type: RAMDisk Image Compression: Unknown Compression Data Size: 8909801 Bytes = 8700.98 KiB = 8.50 MiB Architecture: AArch64 OS: Linux Load Address: unavailable Entry Point: unavailable Hash algo: sha1 Hash value: 3be954cf886386101311f7673115fa0be0c95366 Image 2 (fdtv5) Description: Flattened Device Tree ebinv5 Created: Sun Oct 23 13:08:21 2022 Type: Flat Device Tree Compression: uncompressed Data Size: 11618 Bytes = 11.35 KiB = 0.01 MiB Architecture: AArch64 Load Address: 0x06f00000 Hash algo: sha1 Hash value: dcfa1e753a26493b713b8d6eee19e0895db09cc3 Image 3 (fdtv7) Description: Flattened Device Tree ebinv7 Created: Sun Oct 23 13:08:21 2022 Type: Flat Device Tree Compression: uncompressed Data Size: 11646 Bytes = 11.37 KiB = 0.01 MiB Architecture: AArch64 Load Address: 0x06f00000 Hash algo: sha1 Hash value: 0230f9e11a6f364dc66c0aca9a72620b19a0f1e0 Default Configuration: 'v5' Configuration 0 (v5) Description: Standard Boot ebinv5 Kernel: kernel Init Ramdisk: ramdisk FDT: fdtv5 Hash algo: sha1 Hash value: unavailable Configuration 1 (v7) Description: Standard Boot ebinv7 Kernel: kernel Init Ramdisk: ramdisk FDT: fdtv7 Hash algo: sha1 Hash value: unavailable After upgrade and reboot the kernel was upgraded to : Welcome to Armbian 22.08.6 Bullseye with Linux 5.15.74-mvebu64 The side effect is that cpu-freq regulation seems to be broken: root@tiger:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. The # htop is unable to determine it either : Cpu Freq: 0 MHz The previous setup before upgrade "Armbian 21.08.1 Bullseye with Linux 5.10.60-mvebu64" ran frequency switch flawlessly: # cpufreq-info current CPU frequency is 200 MHz (asserted by call to hardware). cpufreq stats: 200 MHz:93.04%, 300 MHz:0.48%, 600 MHz:0.18%, 1.20 GHz:6.30% (215) Due to inability of CPU frequency regulation, I found that the board temperature has been increased by about 5 deg. C. What could be done to fix this issue?
  2. 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 protected When 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
  3. Folks, it has been a long time since I messed around with my ebin v5, but just wanted give it a second chance as I need to do something about my EOL Cubietruck (and my "broken" NT4 domain). So I started a second attempt with "Armbian_22.08.1_Espressobin_bullseye_current_5.15.63" just a few days ago, but didn't got much further than updating uboot and to apt update / upgrade the system, before I got distracted again. In the meantime I noticed the new "Armbian_22.11.1_Espressobin_bullseye_current_5.15.80" and I thought it would be a better idea starting from scratch with that version. However, when I boot this up from SD the only interface shown ("ifconfig") is lo. (I 'see' the other port with "ifconfig -a", but I don't get an IP set (via DHCP) whatever physical port I use on the topaz switch, though the leds are happily blinking indicating a proper link.
  4. Hi eveyone, I am coming from a a hint off Github here: https://github.com/armbian/documentation/issues/165. Igor was so kind and redirected me to this community. I am struggling since beginning christmas to get my EspressoBin to latest versions out of dusty 2018 images. Device EspressoBin v7 DDR4 1G 1000_800Mhz Baseline - What did I do? - Update U-Boot according https://www.armbian.com/espressobin to devel-18.12.3 - Flashed SD-Card with armbian Focal via Balena according https://docs.armbian.com/User-Guide_Getting-Started/ - Updated Boot Environment according https://www.armbian.com/espressobin/#kernels-archive-all Problem Description - U-Boot Loads and starts over to boot from SD-Card - Booting from SD fails with Marvell>> boot *** ERROR: serverip' not set *** ERROR: serverip' not set Bad Linux ARM64 Image magic! I would be very grateful for any hints how to get armbian booted on the EspressoBin in 2022! Happy Holidays to all. cheers Full Logs U-Boot 2018.03-devel-18.12.3-gc9aa92ce70-armbian (Sep 18 2020 - 10:07:21 +0200) 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 up MMC: sdhci@d0000: 0 Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 [PRIME] https://github.com/armbian/documentation/issues/165
  5. 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 .................. ..............
  6. 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
  7. Hello Everyone! In the company where I am, we are migrating the current Zynq architecture with DDR3 to Armada 3700 family with DDR4. Before deciding to migrate, we bought some espressobin and were delighted with this product. We have therefore attempted to develop two cards that use the armada A3700 processor without success. We concluded that the problem is HW but we don't know exactly where. I have done numerous tests. I try to summarize the key points as briefly as possible. Our board uses DDR4 MT40A512M16LY-062E IT:E with Armada 88F3720-A0-BVB2I080-P123. We have created a TIM, WTMI, Uboot package using A3700-utils-marvell, mv-ddr-marvell and atf-marvell from github as indicated in http://espressobin.net/espressobin-ultra-build-instruction/. The package works correctly on espressobin V7. To test it we set the serial boot with the jumpers on the board then we used the tool A3700-utils-marvell/wtptp/linux/WtpDownload_linux . We tried to throw the same thing on our board but uboot didn't start. We then investigated further: to eliminate all the SW section above WTMI we modified the source code at A3700-utils-marvell/wtmi/sys_init/main.c by inserting a return 0 immediately inside the main (therefore after “u32 status”). On espressobin we see that the DDR switches correctly at 800MHz and the console goes back to the bootROM ones (therefore with the ">" symbol). On our board, however, the symbol is always that of the bootROM (we have never seen anything different) but the DDR does not switch at 800MHz: it remains at 400MHz instead. Deepening the topic, several registers have been read from the bootROM console. In particular: the section starting from address 1FFF_0000 onwards (at least 100 registers), the section starting from 2000_6000 (at least 100 registers) and the section starting at 6410_0000 have been read. Sections 1FFF_0000 and 2000_6000 have consistent content between our board and espressobin (this is also consistent with TIM and WTMI file). The section 6410_0000 instead is consistent on espressobin with the uboot binary but it is not so on our board. Random and non-repeatable data are read following a power down of our board. We have therefore concluded (I kindly ask for your confirmation) that the problem is the DDR. To rule out any possibility, our DDR was mounted on a V7 espressobin. The system starts correctly and has therefore validated the HW component. In order to generate the package that contains the TIM (which from what we understand describes among other things some registers to allow switching to 800MHz) we use the following command: export CROSS_COMPILE = / opt / toolchains / gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu / bin / aarch64-linux-gnu- export BL33 = $ BINARIES_DIR / u-boot.bin make DEBUG = $ MY_DBG USE_COHERENT_MEM = 0 LOG_LEVEL = 60 SECURE = 0 CLOCKSPRESET = CPU_600_DDR_600 DDR_TOPOLOGY = 5 BOOTDEV = SPINOR PARTNUM = 0 PLAT = a3700 all fip CLOCKSPRESET = CPU_800_DDR_800 was also tried. The variations of this parameter are seen on espressobin (with oscilloscope on DDR clock) but not on our board (which remains at 400MHz). Further analyzing the A3700-utils-marvell/tim/ddr/DDR_TOPOLOGY_5.txt file and the "ddr_tool" sources present in mv-ddr-marvell/. The ddr_tool are compiled by us with the following: export PLATFORM = a3700 export DDR_TYPE = DDR4 make clean make We tried to change the value of CL and CWL. Putting wrong values also the espressobin stops (like our board) but we were not able to start our board instead. From what we understand (I kindly ask for your confirmation), the problem is that the TIM structure does not correctly describe our DDR4 (or our PCB with the correct timings on the tracks) this causes the check on the checksum of the uboot section made by bootROM to fail. Then reset the chip. We therefore ask for confirmation on our deduction and if there is any tool capable of giving us the correct values to be entered in ddr_tool to correctly set the communication with DDR4 on our board. At the HW level we checked the DDR4 signals (with eye diagrams too). We do not see important reflections on signals that could compromise correct communication. However, the DDR4 clock always remains stationary at 400MHz and the data contained in it always seems to be random (read with command r 6410_0000 and following from the bootROM console). Hope it can help you with problem analysis, Best regards
  8. Hi, Trying to get the latest U-Boot working on my ESPRESSObin board - a v5, DDR3, 1 GB, 1cs version. I have no issues flashing it, and tftpbooting ... with the "old" supplied U-Boot. But wanting to run a recent version of OpenWrt on the board, so trying to update U-Boot. I flashed the latest version of U-Boot for it ... U-Boot comes up fine (I have serial access), but - ethernet seems to have an issue (for tftpboot, or even ping), I get, => ping 192.168.2.1 (NULL udevice *): mvneta_setup_txqs: can't create txq=0 Using ethernet@30000 device timeout: packet not sent timeout: packet not sent timeout: packet not sent timeout: packet not sent I can go back to the old U-Boot (circa 2017), and it works again (flashing from USB). But ... has anyone seen the issue above? And of course, any fixes? Thanks!
  9. not an expert in device-tree, anybody knows how enable uart2/uart4? dts is attached. expressobin v7 mainline many thanks. armada-3720-espressobin-v7.dts
  10. I flashed my espressobin v5 with flash-image-DDR4-1g_1cs_5-1000_800.bin After the boot it tries to boot from a network source instead of sdcard. printenv I dont know how it got to this point all I want now is to be able to boot from sdcard. Any thoughts or ideas?
  11. I've been having a recent issue over the last couple months where my ArmbianEvn.txt file is being overwritten thus causing Helios to hang in the boot process. Using some samples i've found on these forums, I was able to re-create my file and get the Helios back up and running and have since stored a copy so that when it happens, I can just copy and paste and back up running in no time. To date, i've had this happen to me 4 times. I'm not worried about having go through this at this point in time, but I was curious if anyone else has seen this issue or not? I've saved a couple samples of what was written into the ArmbianEnv.txt file: /var/log/armbian-hardware-monitor.log { rotate 12 weekly compress missi /var/log/alternatives.log { monthly rotate 12 compress delaycompress missingok notifempty create 644 root root } I'm running Buster 5.10.21. I have 5-14TB EXOS drives in Raid 6 and have OMV as the only thing installed.
  12. I am not shure if this is board specific so I post it here and hope that you might be willing to try this on your board: - I installed audit: apt install auditd - I set up a rule for a file audit should watch: auditctl -w /boot/armbianEnv.txt -p wa - I change or touch the file being watched: touch /boot/armbianEnv.txt - I have a look at the log of audit: cat /var/log/audit/audit.log And then ––– I see nothing... Any hints what's going wrong? My guess is that the kernel might be lacking the audit module?!
  13. I was able to boot from a SATA disk that was manually setup with a GPT-formatted table and a debootstrap'ed debian arm64 kernel. The GPT partitions included: 1. BIOS from sector 34-2047, no filesystem 2. ESP from 2048-409599 (which u-boot calls bootable even if the flag isn't set), vfat filesystem 3. XBOOTLDR from 409600-819199 with bootable flag set (0x4), ext4 FS without journal 4. linux swap 5. ARM64 root (gdisk type 8305) with bit 60 set (read-only), ext4 without journal 6. linux /var (gdisk type 8310), ext4, with /srv/ and /home/ bind-mounted from /var/local/ The bootscripts/extlinux configuration live in /boot, onto which is mounted partition 3 (XBOOTLDR) next to the actual kernel/initramdisk. It is necessary to mark this partition bootable in gdisk to have the u-boot distro-boot search it for extlinux/boot.scr. While the espressobin doesn't require u-boot flashed on the boot media, this disk partition scheme would allow rockchip64 systems to boot if the BIOS partition is extended to somewhere around sector 32767 (as rockchip needs code at sector 64 and maybe 16384 and 24576).
  14. Getting stuck out of the gate (of course never goes as documented🤣) https://puhoy.github.io/posts/armbian_on_espressobin/ While attempting to flash the required uboot update I keep getting a "permission" type error I've tried with usb stick and sd card, formated ext4, formatted fat and various permutations including simple filename....all give the same error even though usb and mmc commands say the media is there This is a v5. I have an identical one I set up a few years ago with ubuntu 18 but I did not have to flash this new uboot. Any thoughts? Do one of the jumpers have to be set in order to flash? Marvell>> usb info 1: Hub, USB Revision 3.0 - U-Boot XHCI Host Controller - Class: Hub - PacketSize: 9 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 1: Hub, USB Revision 2.0 - u-boot EHCI Host Controller - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Mass Storage, USB Revision 2.0 - SanDisk Corporation Staples Relay SNDK7E38850327C07602 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x0781 Product 0x5202 Version 0.32 Configuration: 1 - Interfaces: 1 Bus Powered 200mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 In Bulk MaxPacket 512 - Endpoint 1 Out Bulk MaxPacket 512 Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi usb Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "usb" to "spi" 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... 2 USB Device(s) found ** File not found flash-image-DDR3-2g_2cs_7-1000_800.bin ** Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from usb exit not allowed from main input shell. Marvell>> mmc info Device: sdhci@d0000 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi mmc Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "mmc" to "spi" Card did not respond to voltage select! mmc_init: -95, time 42 MMC Device 1 not found No SD/MMC/eMMC card found Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from mmc exit not allowed from main input shell.
  15. Hello everyone, i build a own Image for the EspressoBin and it wont boot. In the u-boot log shows boot.scr but on the Image himself is just a boot.scr.uimg. What is the problem ? Greetings StarSurfer Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 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... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found / ** File not found /boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** File not found /boot/boot.scr ** ## 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 / ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command / 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>>
  16. Hello, [short version] My expresso bin V5 only boots from the micro sd card and I would like it to boot from the EMMC module. [long version] My old old expresso bin V5 did not came with a pre installed EMMC module, I had a 16gb kingston EMMC module from aliexpress soldered onto it, the EMMC module is correctly detected by armbian bionic as seen from the output of blkid as /dev/mmcblk0p1: /dev/mmcblk0p1: UUID="dc265376-877d-40a1-9417-7379fb332efe" TYPE="ext4" PARTUUID="36c210f9-01" /dev/mmcblk1p1: LABEL="root" UUID="621decff-6765-4dbd-ae8c-c7e2d5c0193d" TYPE="ext4" PARTUUID="04b226a1-01" /dev/mmcblk1p3: LABEL="home" UUID="df5bfbe2-de80-49b4-ac8f-2378fd736e4f" TYPE="ext4" PARTUUID="04b226a1-03" /dev/zram0: LABEL="log2ram" UUID="1d15f838-3c4d-4acf-a58c-fde890ecdea9" TYPE="ext4" /dev/mmcblk0: PTUUID="36c210f9" PTTYPE="dos" /dev/mmcblk1: PTUUID="04b226a1" PTTYPE="dos" /dev/zram1: UUID="c759b67d-75a8-4452-95a8-fe45f11d1e4c" TYPE="swap" I can mount, read and write on /dev/mmcblk0p1, initially I ran armbian-config to install armbian on the EMMC module and it worked with a weird shortcoming, it would only boot from the EMMC module if a micro SD card was inserted on the board, I could tell right away from the "Usage of /:" field on the amrbian prompt from which storage device I had booted but I also checked the UUID on fstab and boot.cmd to make sure. uboot threw an error message saying Card did respond to voltage select! whenever I tried to boot without a micro SD card on the expresso bin From here on out what I did made matters much worse, I figured uboot was the problem and decided to update it to a newer version without backing up the on I had on the board from February 2019(stupid of me), so I downloaded and installed the lastest version I could find on https://xogium.performanceservers.nl/archive/espressobin/u-boot/ Ever since I cannot boot from the EMMC module with or without a micro SD card on the expressobin and uboot does not detect it at all, since the following command only prints one device when it used to print 2: Marvell>> mmc list sdhci@d0000: 0 I'm still able to mount and write stuff to the EMMC storage while on bionic as before, but on uboot it's like it doesen't exist. The uboot environment is like this: Marvell>> env print arch=arm baudrate=115200 board=mvebu_armada-37xx board_name=mvebu_armada-37xx boot_a_script=ext4load ${boot_interface} ${devnum}:1 ${scriptaddr} ${prefix}boot.scr;source ${scriptaddr}; boot_interface=mmc boot_prefixes=/ /boot/ boot_targets=usb sata mmc1 mmc0 bootargs=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=UUID=dc265376-877d-40a1-9417-7379fb332efe rootfstype=ext4 rootwait loglevel=1 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u mtdparts=spi0.0:1536k(uboot),64k(uboot-environment),-(reserved) bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done bootcmd_mmc0=setenv devnum 0; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_mmc1=setenv devnum 1; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_sata=setenv devnum 0; scsi scan; scsi dev 0; setenv boot_interface scsi; run scan_dev_for_boot; bootcmd_usb=setenv devnum 0; usb start;setenv boot_interface usb; run scan_dev_for_boot; bootdelay=2 console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 cpu=armv8 devnum=0 emmc_fix=on eth1addr=06:8E:A0:24:0F:88 eth2addr=00:50:43:84:25:2f eth3addr=00:50:43:0d:19:18 ethact=neta@30000 ethaddr=F0:AD:4E:03:64:7F ethprime=eth0 extra_params=pci=pcie_bus_safe fdt_addr=0x6000000 fdt_addr_r=0x6f00000 fdt_high=0xffffffffffffffff fdt_name=fdt.dtb fdt_name_a=dtb/marvell/armada-3720-community.dtb fdt_name_b=dtb/marvell/armada-3720-espressobin.dtb fdtcontroladdr=3f62d490 fileaddr=6d00000 filesize=ea 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=0x1100000 initrd_image=uInitrd initrd_size=0x2000000 ipaddr=0.0.0.0 kernel_addr=0x7000000 kernel_addr_r=0x7000000 loadaddr=0x8000000 netdev=eth0 netmask=255.255.255.0 ramdisk_addr_r=0x8000000 ramfs_name=- root=root=/dev/nfs rw rootdev=UUID=dc265376-877d-40a1-9417-7379fb332efe rootfstype=ext4 rootpath=/srv/nfs/ scan_dev_for_boot=for prefix in ${boot_prefixes}; do echo ${prefix};run boot_a_script; done scriptaddr=0x6d00000 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 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u vendor=Marvell verbosity=1 Environment size: 2655/65532 bytes While booting, uboot throws these errors: / ** 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 / ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device mmc 1 ** ## 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/ Any help in getting amrbian booting from the recently soldered EMMC module would be greatly appreciated.
  17. I'm sooooo close to sharing a WIP for building armbiain for espressobin , but I'm having trouble getting armbian builder to use the file name for the kernel package deb. │ dpkg-deb: building package 'linux-headers-4.4.8-mvebu64' in '../linux-headers-4.4.8-mvebu64_5.27_arm64.deb'. │ │ dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_5.27_arm64.deb'. │ │ dpkg-deb: building package 'linux-image-4.4.8-mvebu64' in '../linux-image-4.4.8-mvebu64_5.27_arm64.deb'. │ │ dpkg-deb: building package 'linux-image-4.4.8-mvebu64-dbg' in '../linux-image-4.4.8-mvebu64-dbg_5.27_arm64.deb'. │ │ dpkg-genchanges: binary-only upload (no source code included) │ └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ dpkg-deb: error: failed to read archive '/root/output/debs/linux-image-mvebu64_5.27_arm64.deb': No such file or directory What's the cleanest way to have the resulting deb and armbianbuilder line up? Stuff I've done: made esspressobin.wip board config Made mvebu64 sources config Made mvebu64 Kernel config Made kernel patch to elminate the localversion file assured VERSION_AUTO is disabled in kernel config Files n stuff esspressobin.wip mvebu64.conf
  18. So, I thought this was worth a try: diff --git a/config/sources/families/mvebu64.conf b/config/sources/families/mvebu64.conf index 091b7633..79e85954 100644 --- a/config/sources/families/mvebu64.conf +++ b/config/sources/families/mvebu64.conf @@ -1,6 +1,6 @@ ARCH=arm64 -BOOTSOURCE='https://github.com/MarvellEmbeddedProcessors/u-boot-marvell.git' -BOOTBRANCH='branch:u-boot-2018.03-armada-18.12' +BOOTSOURCE='https://github.com/u-boot/u-boot' +BOOTBRANCH='branch:master' BOOTENV_FILE='mvebu64.txt' ATFSOURCE='https://github.com/MarvellEmbeddedProcessors/atf-marvell' ATFDIR='arm-trusted-firmware-espressobin' TIM-1.0 WTMI-devel-18.12.1-e6bb176 WTMI: system early-init DDR topology parameters: ======================== ddr type DDR3 ddr speedbin 12 bus width 16-bits cs num 2 cs[0] - group num 0 cs[0] - bank num 8 cs[0] - capacity 1024MiB cs[1] - group num 0 cs[1] - bank num 8 cs[1] - capacity 1024MiB CPU VDD voltage default value: 1.108V DRAM windows: ============= WIN[0] - base addr 0x60000000 WIN[0] - size 0x40000000 WIN[1] - base addr 0xa0000000 WIN[1] - size 0x20000000 memory test region: =================== CS[0] 0x60000000 - 0x9fffffff CS[1] 0xa0000000 - 0xbfffffff SELF-REFRESH TEST PASS SELF-REFRESH TEST PASS CS0: QS GATE TRAINING PASSED CS1: QS GATE TRAINING PASSED DLL TUNING PASSED NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 14:05:30, Oct 20 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 14:05:30, Oct 20 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 14:05:30 U-Boot 2020.10-armbian (Oct 20 2020 - 14:05:01 +0000) DRAM: 2 GiB Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 5 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 up MMC: sdhci@d0000: 0 Loading Environment from SPIFlash... SF: Detected w25q32dw with page size 256 By tes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: neta@30000 [PRIME] My own kernels boot but I'm still having issues with the latest armbian SD card images (same issue with 2017 and 2018 u-boots). I'm not game to touch atf - someone with Marvell's wtp tools set up can do that
  19. Morning All, Around a year and a half ago I found the USB port from my Espressobin V5 had broken off. This has not greatly affected me because the board itself continued to operate perfectly up to the point of merging with the mainline kernel 5.x which it simply will not boot, I am assuming because a new boot script needs to be set for the device as described on the download page ( https://www.armbian.com/espressobin/ ) but of course I am unable to access the U-Boot command without serial communication. I have set the kernel update on hold thus far, but this of course cannot hold forever. Is there anyway to update the boot script without access to serial communication on the device? I still have SSH control and it is booting a 4.19 kernel without a hitch. My Espressobin is currently being used as a subnet: LAN support where required, vpn server, NFS server, 2.4 and 5GHz wifi networks that actually outperform the piece of garbage router that my ISP sent to me. I love it. I would eventually replace it with whichever is newest from Globalscale but for now it is doing what I need, just have to figure out how to update it.
  20. Hi All! I am having a lot of trouble making my ESPRESSObin v7 1GB DDR4 run without crashes. I have tried both Bionic (5.75 4.19.20) and Stretch (5.75 4.19.20) images, and neither are stable. I have tried with a lot of different PSUs (all switch-mode though) and booting from both microSD and USB sticks. My U-Boot is "flash-image-ddr4-1g-1cs-1000_800.bin". It seems like there is about 50% chance that it will boot without a crash. The type of crashes I get seems random. Ex http://ix.io/1JGY And then it just freezes. Or this one which includes a proper kernel Oops: http://ix.io/1JGZ While running, I get errors like this one: [ 71.136812] BUG: Bad page state in process khugepaged pfn:31d99 [ 71.140206] page:ffffffbf00c76640 count:0 mapcount:0 mapping:0000000000002000 index:0x0 [ 71.148428] flags: 0x0() [ 71.151049] raw: 0000000000000000 0000000000000000 ffffffbf00c76648 0000000000002000 [ 71.159015] raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 [ 71.166975] page dumped because: non-NULL mapping [ 71.172329] BUG: Bad page state in process khugepaged pfn:3261c [ 71.178001] page:ffffffbf00c98700 count:0 mapcount:0 mapping:0000000000002000 index:0x0 [ 71.186236] flags: 0x0() [ 71.188853] raw: 0000000000000000 0000000000000000 ffffffbf00c98708 0000000000002000 [ 71.196825] raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 [ 71.204782] page dumped because: non-NULL mapping Once successfully booted, setting the CPUfreq governor to "performance" seems to make it more stable. Am I the only one having problems getting a stable boot on V7? Has anyone of you any tips on how to make it stable? I am willing to try compiling a new kernel if some experimental patches exists.
  21. Hello every one, I own two ESPRESSOBin boards V5. And to both I attached an XCSOURCE® MiniPCIe Sata3.0 AC696 extension card via MiniPCIe. This is the link to amazon: https://www.amazon.de/dp/B06XRG2TGV I tested several images from https://www.armbian.com/espressobin/#kernels-archive-all Unfortunatelly all the old images have been deleted last week, so I could not continue testing. Tested Kernels 8 weeks ago + the latest two this week: - 5.10.09-mvebu64 #21.02.0-hirsute (trunk) <-- works not - 5.08.18-mvebu64 #20.11.6-bionic <-- works not - 5.08.18-mvebu64 #20.11.3-focal <-- works not - 5.08.18-mvebu64 #20.11.3-bionic <-- works not - 5.08.06-mvebu64 #20.08.2-focal <-- works not - 4.14.135-mvebu64 #19.11.3-bionic <-- works Here is the whole UART-dump: TIM-1.0 WTMI-devel-18.12.0-a0a1cb8 WTMI: system early-init SVC REV: 3, CPU VDD voltage: 1.155V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 09:48:09, Feb 20 2019 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 09:48:10, Feb 20 2019 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 09:4 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: 2 GiB Comphy chip #0: Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps Target spinup took 0 ms. 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 up 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 ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 10750023 Bytes = 10.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06000000 Booting using the fdt blob at 0x6000000 Loading Ramdisk to 7ebea000, end 7f62a847 ... OK Using Device Tree in place at 0000000006000000, end 00000000060059cd Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.8.18-mvebu64 (root@beast) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #20.11.3 SMP PREEMPT Fri Dec 11 21:10:52 CET 2020 [ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board [ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '') [ 0.000000] printk: bootconsole [ar3700_uart0] enabled Loading, please wait... Starting version 245.4-4ubuntu3.3 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.34 [/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 41739/1828336 files, 439779/7502824 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. [ 3.694604] Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP [ 3.699465] Modules linked in: tag_edsa mv88e6xxx dsa_core bridge stp llc phy_mvebu_a3700_comphy [ 3.708518] CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.8.18-mvebu64 #20.11.3 [ 3.716037] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [ 3.722685] Workqueue: events free_work [ 3.726614] pstate: 00000085 (nzcv daIf -PAN -UAO BTYPE=--) [ 3.732352] pc : ahci_single_level_irq_intr+0x1c/0x90 [ 3.737549] lr : __handle_irq_event_percpu+0x5c/0x168 [ 3.742737] sp : ffffffc0113bbd10 [ 3.746142] x29: ffffffc0113bbd10 x28: ffffff807d48b700 [ 3.751608] x27: 0000000000000060 x26: ffffffc010f085e8 [ 3.757073] x25: ffffffc0113075a5 x24: ffffff8079101800 [ 3.762539] x23: 000000000000002d x22: ffffffc0113bbdd4 [ 3.768004] x21: 0000000000000000 x20: ffffffc011465008 [ 3.773470] x19: ffffff8079381600 x18: 0000000000000000 [ 3.778936] x17: 0000000000000000 x16: 0000000000000000 [ 3.784401] x15: 000000d2c010fc50 x14: 0000000000000323 [ 3.789867] x13: 00000000000002d4 x12: 0000000000000000 [ 3.795332] x11: 0000000000000040 x10: ffffffc011282dd8 [ 3.800798] x9 : ffffffc011282dd0 x8 : ffffff807d000270 [ 3.806263] x7 : 0000000000000000 x6 : 0000000000000000 [ 3.811729] x5 : ffffffc06ea93000 x4 : ffffffc0113bbe10 [ 3.817196] x3 : ffffffc06ea93000 x2 : ffffff8079101a80 [ 3.822661] x1 : ffffff8078803e00 x0 : 000000000000002d [ 3.828126] Call trace: [ 3.830642] ahci_single_level_irq_intr+0x1c/0x90 [ 3.835478] __handle_irq_event_percpu+0x5c/0x168 [ 3.840315] handle_irq_event_percpu+0x38/0x90 [ 3.844885] handle_irq_event+0x48/0xe0 [ 3.848828] handle_simple_irq+0x94/0xd0 [ 3.852860] generic_handle_irq+0x30/0x48 [ 3.856985] advk_pcie_irq_handler+0x214/0x240 [ 3.861552] __handle_irq_event_percpu+0x5c/0x168 [ 3.866389] handle_irq_event_percpu+0x38/0x90 [ 3.870959] handle_irq_event+0x48/0xe0 [ 3.874900] handle_fasteoi_irq+0xb8/0x170 [ 3.879112] generic_handle_irq+0x30/0x48 [ 3.883234] __handle_domain_irq+0x64/0xc0 [ 3.887447] gic_handle_irq+0xc8/0x168 [ 3.891298] el1_irq+0xb8/0x180 [ 3.894524] unmap_kernel_range_noflush+0x128/0x188 [ 3.899540] remove_vm_area+0xac/0xd0 [ 3.903303] __vunmap+0x48/0x298 [ 3.906618] free_work+0x44/0x60 [ 3.909937] process_one_work+0x1e8/0x360 [ 3.914057] worker_thread+0x44/0x480 [ 3.917820] kthread+0x154/0x158 [ 3.921135] ret_from_fork+0x10/0x34 [ 3.924812] Code: a90153f3 f9401022 f9400854 91002294 (b9400293) [ 3.931087] ---[ end trace 98b323414bb99c99 ]--- [ 3.935829] Kernel panic - not syncing: Fatal exception in interrupt [ 3.942368] SMP: stopping secondary CPUs [ 3.946403] Kernel Offset: disabled [ 3.949985] CPU features: 0x240002,2000200c [ 3.954283] Memory Limit: none [ 3.957424] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- The boards boots up if I don't plug in any SATA HDDs into the extension card. I hope this helps. If you need any other information just let me know, I'm absolutely willing to help. But please be aware that I'm a software developer coming from windows trying to get into linux. But I have no clue of kernel patching/compiling etc. Sorry! Thank you very, very much in advance! You're doing an awesome job. Sincerely Rötti
  22. My Espressobin v5 with 4.14 reports 800Mhz and I am wondering if is there any progress on making it work at 1G or 1.2Ghz?
  23. sorry for asking about espressobin... I had this board working with armbian, but it was sitting in a box for a while. I remade the sd card with the new current 5.10 buster and it won't boot. I tried different sd cards and power supplies. It hangs at "Loading, please wait" Maybe I need new u-boot, but that https://minio.k-space.ee/ site isn't working or is gone. Not armbian's fault obviously. Anyone know another way to get a current u-boot image? I don't really want to build one. I don't have a toolchain set up and I'll probably buy a different board anyways. (Anyone know a well supported 2 port box that's easy to get in the USA?) These things are a pain.
  24. ``` [ 160.434443] ------------[ cut here ]------------ [ 160.434470] WARNING: CPU: 0 PID: 0 at net/bridge/br_switchdev.c:46 nbp_switchdev_frame_mark+0x20/0x30 [bridge] [ 160.434571] Modules linked in: xfrm_user xfrm_algo ip6t_REJECT nf_reject_ipv6 ip6_tables nf_log_ipv6 xt_recent xt_comment xt_multiport ipt_REJECT nf_reject_ipv4 xt_conntrack xt_hashlimit xt_mark xt_MASQUERADE nft_counter xt_CT xt_tcpudp xt_addrtype nft_compat nft_chain_nat br_netfilter nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink 8021q garp mrp bonding overlay zram zsmalloc 88x2bu cfg80211 rfkill armada_37xx_wdt watchdog fuse tag_dsa ip_tables x_tables mv88e6xxx dsa_core hsr bridge stp llc phy_mvebu_a3700_comphy [ 160.434892] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.12.18-mvebu64 #trunk.94 [ 160.434903] Hardware name: Globalscale Marvell ESPRESSOBin Board V7 (DT) [ 160.434910] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--) [ 160.434919] pc : nbp_switchdev_frame_mark+0x20/0x30 [bridge] [ 160.434983] lr : br_handle_frame_finish+0xb4/0x460 [bridge] [ 160.435046] sp : ffffffc010003ba0 [ 160.435051] x29: ffffffc010003ba0 x28: ffffff800898fe00 [ 160.435065] x27: ffffffc010003d30 x26: ffffff8012cd4c00 [ 160.435078] x25: ffffffc010003d30 x24: 0000000000000001 [ 160.435091] x23: ffffff801ff80818 x22: 0000000000000000 [ 160.435103] x21: ffffff800898fe00 x20: ffffff8012cd4c00 [ 160.435116] x19: ffffffc0112e9948 x18: 0000000000000000 [ 160.435129] x17: 0000000000000000 x16: 0000000000000000 [ 160.435141] x15: 0000000000000001 x14: 0000000000000002 [ 160.435154] x13: 0000000000011511 x12: 00003d0900000000 [ 160.435167] x11: 0000000000000000 x10: ffffff80002256f0 [ 160.435179] x9 : 0000000000000020 x8 : 0000000000000002 [ 160.435192] x7 : 000000000000eb52 x6 : ffffff800bce210e [ 160.435205] x5 : 0000000000000001 x4 : ffffffc010003bfd [ 160.435218] x3 : ffffffc010003bfe x2 : 0000000000000008 [ 160.435230] x1 : ffffff800898fe00 x0 : 0000000000000000 [ 160.435244] Call trace: [ 160.435250] nbp_switchdev_frame_mark+0x20/0x30 [bridge] [ 160.435313] br_handle_frame+0x28c/0x3a0 [bridge] [ 160.435376] __netif_receive_skb_core+0x278/0x9d8 [ 160.435392] __netif_receive_skb_one_core+0x38/0x80 [ 160.435402] __netif_receive_skb+0x18/0x70 [ 160.435410] process_backlog+0xb4/0x178 [ 160.435419] __napi_poll+0x38/0x1b0 [ 160.435429] net_rx_action+0xe4/0x220 [ 160.435438] _stext+0x11c/0x274 [ 160.435448] irq_exit+0xbc/0xd8 [ 160.435459] __handle_domain_irq+0x68/0xc0 [ 160.435470] gic_handle_irq+0xc0/0x138 [ 160.435482] el1_irq+0xb8/0x180 [ 160.435490] arch_cpu_idle+0x18/0x28 [ 160.435500] default_idle_call+0x24/0x5c [ 160.435512] do_idle+0x204/0x278 [ 160.435522] cpu_startup_entry+0x24/0x68 [ 160.435531] rest_init+0xd8/0xe8 [ 160.435539] arch_call_rest_init+0x10/0x1c [ 160.435551] start_kernel+0x4f4/0x528 [ 160.435562] ---[ end trace a0efa004c37badcf ]--- ```
  25. Does anyone managed to use vlan tagging on ports Lan0 and Lan1 on openwrt ? I neet to setup 6 differents VLANs with this 2 ports ;-) If someone succeeded, I'm interrested on the way to proceed...
×
×
  • Create New...