I've have an ESPRESSObin Ultra which ships from Globalscale with old, buggy, and unmaintained firmware. I think the old firmware could explain a lot of the issues users have reported here with the V7. I forked the old factory firmware build script from Globalscale and moved it all to up-to-date, upstream projects: https://github.com/bschnei/ebu-bootloader

I believe with some small modifications, it is possible to also build an up-to-date bootloader for other Globalscale devices that also use the Armada 37XX SoC, for example the ESPRESSObin V7.

I currently use Arch Linux ARM on my device and have notified their community as well: https://archlinuxarm.org/forum/viewtopic.php?f=67&t=16746

One of the issues I can confirm has been fixed is EFI booting from U-Boot. Fixing this means we can use U-Boot Standard Boot (bootflow scan) to load user-friendly EFI apps like systemd-boot, GRUB, etc. This significantly streamlines the boot process eliminating the need for u-boot to load separate kernel, initramfs, and device tree files. This also makes packaging it a lot easier too.

It also means your bootloader becomes configurable from the OS which is really nice because it means your distro of choice can configure the bootloader instead of requiring users to configure U-Boot manually. I'm not familiar with Armbian, but I think it ships with systemd-boot (?) which has an EFI application that gives you a user friendly way to control device booting. GRUB has a similar capability.

Please send me a note if you are interested in testing firmware for the ESPRESSObin V7 or Ultra.

Without one attached as soon as power sis applied all the ethernet interface LEDs flash briefly. With the SSD card that doesn't happen. There is no activity at the console.

Do I need to change jumpers or do some other setting at the Marvell prompt before attaching it?

Help would be much appreciated.

Many thanks

LA.

I installed the latest stable (and updated) debian image on clearfogpro from SD card.

I then chose "boot from SD, install on SATA ..." as I have a M.2 SSD card which is viewed as /dev/sda device, with the "armbian-install"

utility.

However, this one does not offer to boot directly from M2. SSD, which should be possible as there is a DIP switch configuration for it.

I tried to burn the iso image on sata with "dd" and then, to "dd" the u-boot.sata on "/dev/sda" (bs=512 seek=1).

When switching to sata boot (dip switch), it begins well, the sata device is found, but nothing happens after, the iso image is not loaded.

How can I boot directly from M.2 SSD with system installed on it ?

Armbian-unofficial_25.05.0-trunk_Khadas-vim2_bookworm_edge_6.13.7.img Armbian-unofficial_25.05.0-trunk_Rockpro64_bookworm_edge_6.14.0-rc4.img

Why is this only with the EspressoBin can someone help me ?

Kind regards
StarSurfer

I would like to sell my helios4 and helios64.

They weren't in operation much and are like new. So they are perfect for spare parts or to use them as a complete replacement.

I really like the products but I don't want the hustle of fiddling around with every new armbian release.

So if anybody is interested you can contact me and/or write here a comment.

Thank you very much!

I would like to sell my Helios64.

The NAS is in excellent condition, and has been used with care. It is ready to be configured according to your needs.

I did not make the fix to take advantage of 2.5Gb/s connectivity (2.5G Ethernet Issue at 1Gbps Link Speed).

I bought it for $285.00 + $28.00 shipping + $45.00 customs clearance + $15.00 for a 2.5" adapter (KOB-H64-ADP-01) (SSD support for the system).

Total = $373.00 (~€340)

I can provide purchase invoices for these amounts.

You can make me your offer proposals.

Here are some photos :

Best regards,

Flolm

env default -a
## Resetting to default environment

I added the image and fdt address with:

setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb
setenv image_name boot/Image
setenv scriptaddr 0x6d00000

The last line is after seeing in the forum that this setting has been erased when resetting the default environment

my environment is now:

Quote

Marvell>> printenv
arch=arm
baudrate=115200
board=mvebu_armada-37xx
board_name=mvebu_armada-37xx
bootcmd=run get_images; run set_bootargs; run load_script;booti $kernel_addr $ramfs_addr $fdt_addr
bootdelay=4
console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000
cpu=armv8
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=00:51:82:11:22:00
ethprime=eth0
extra_params=pci=pcie_bus_safe
fdt_addr_r=0x6f00000
fdt_high=0xffffffffffffffff
fdt_name=boot/dtb/marvell/armada-3720-espressobin.dtb
fdtcontroladdr=7f62d490
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_ri
hostname=marvell
image_name=boot/Image
initrd_addr=0xa00000
initrd_size=0x2000000
ipaddr=0.0.0.0
kernel_addr_r=0x7000000
load_script=if test -e mmc 0:1 boot/boot.scr; then echo "... booting from SD";setenv boot_interface mmc;else echo "... booting from USB/SATA";usi
loadaddr=0x6000000
netdev=eth0
netmask=255.255.255.0
ramdisk_addr_r=0x8000000
ramfs_name=-
root=root=/dev/nfs rw
rootpath=/srv/nfs/
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 $e
soc=mvebu
stderr=serial@12000
stdin=serial@12000
stdout=serial@12000
vendor=Marvell

When I try to boot, it seems to load the initrd but never complete the boot I get:

Marvell>> boot
*** ERROR: `serverip' not set
*** ERROR: `serverip' not set
... booting from SD
1631 bytes read in 9 ms (176.8 KiB/s)
## Executing script at 00800000
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.
## Info: input data size = 2100 = 0x834
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.
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]
    - boot application image stored in memory
        passing arguments 'arg ...'; when booting a Linux kernel,
        'arg' can be the address of an initrd image
        When booting a Linux kernel which requires a flat device-tree
        a third argument is required which is the address of the
        device-tree blob. To boot that kernel without an initrd image,
        use a '-' for the second argument. If you do not pass a third
        a bd_info struct will be passed instead

Sub-commands to do part of the bootm sequence.  The sub-commands must be
issued in the order below (it's ok to not issue all sub-commands):
        start [addr [arg ...]]
        loados  - load OS image
        ramdisk - relocate initrd, set env initrd_start/initrd_end
        fdt     - relocate flat device tree
        cmdline - OS specific command line processing/setup
        bdt     - OS specific bd_t processing
        prep    - OS specific prep before relocation or go
        go      - start OS
21764608 bytes read in 2021 ms (10.3 MiB/s)
ext4load - load binary file from a Ext4 filesystem

Usage:
ext4load <interface> [<dev[:part]> [addr [filename [bytes [pos]]]]]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext4 filesystem
11618 bytes read in 12 ms (945.3 KiB/s)
## Flattened Device Tree blob at 06f00000
   Booting using the fdt blob at 0x6f00000
   Using Device Tree in place at 0000000006f00000, end 0000000006f05d61

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.15.48-mvebu64 (root@8b3d501f9218) (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) #22.05.3 SMP PREEMPT Wed Jun 22 07:22:16 UTC 2022
[    0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board
[    0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
  
..... Omitted a long boot log ....
  
  [    2.376178] Key type fscrypt-provisioning registered
[    2.383950] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
[    2.394740] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 0, base_baud = 1562500) is a mvebu-uart
[    2.404251] printk: console [ttyMV0] enabled
[    2.404251] printk: console [ttyMV0] enabled
[    2.412987] printk: bootconsole [ar3700_uart0] disabled
[    2.412987] printk: bootconsole [ar3700_uart0] disabled
[    2.425972] xenon-sdhci d00d0000.sdhci: Got CD GPIO
[    2.464648] mmc0: SDHCI controller on d00d0000.sdhci [d00d0000.sdhci] using ADMA
[    2.473851] Waiting for root device ...
[    2.512635] mmc0: new high speed SDHC card at address d6d7
[    2.520455] mmcblk0: mmc0:d6d7 SU08G 7.40 GiB
[    2.531514]  mmcblk0: p1

It seems that my boot env is incomplete.

I tried with the last bullseyes and bookworm image, with the same result.

I also tried the instructions in Armbian Documentation - Esspresso bin even if it seems obsolete by now, as it uses old uboot variable names, and contain a booiti command after sourcing the boot.scr script which itself contain the booti command; but I got the same result, even if the inird addr was distinct.

Please what is wrong, and what I'm missing in this uboot environment.

if anyone's interested.

Armbian_23.11.1_Espressobin_bookworm_current_5.15.139.img.xz

is not mounting.

Downloaded from

https://armbian.site-meganet.com/dl/espressobin/archive/Armbian_23.11.1_Espressobin_bookworm_current_5.15.139.img.xz

Mounting from loop or from USB gives the same error:

# mount /dev/loop0p1 /mnt/img/

mount: /mnt/img: wrong fs type, bad option, bad superblock on /dev/loop0p1, missing codepage or helper program, or other error

Is there other working image?

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).

root:# hwclock --systohc
root:# while true; do date; hwclock -r; sleep 60; done

observing drift of 1 sec.

even tried this https://github.com/armbian/build/pull/2352/commits/59cdf431ef691d67d649adbfaf973f9d451823bc#diff-dc13c5522aed383d1b20662d765c5be9f2635553256069dce64f29be94f89b69

specs:

Armada 38x RTC driver 

ARM_GLOBAL_TIMER

Board : Marvell Armada A385 DB AP  Kernel : 4.14 

community help will be grateful

Regards

Hardik

Download link from source page for EspressoBin doesn't work: https://www.armbian.com/espressobin/

gets you here:

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?

I'm trying to add some storage to espressobin board and idea to utilize existing mini pcie socket for that was very appealing. I have bought Mini PCI-E to NVME Adapter on aliexpress (PCI-E to NVME Adapter) and Samsung PM991a 256Gb drive. 

To my surprise it is almost worked immediately - drive is detected and appeared in system as nvme device. The next step would be to check if it works and I was hit by a failure immediately, 

Reading from drive using dd command seems to work for first 19 Mb's seems to work, but attempt to ready anything beyond 20 Mb mark produces drive freeze and then disconnect. Drive becomes unusable until power cycle.

Command I have used: 

dd if=/dev/nvme0n1 of=/dev/null bs=1M status=progress count=20

Dmesg shows following output:

[  134.109735] nvme nvme0: I/O 288 QID 2 timeout, aborting
[  134.109797] nvme nvme0: I/O 289 QID 2 timeout, aborting
[  164.828756] nvme nvme0: I/O 288 QID 2 timeout, reset controller
[  195.547760] nvme nvme0: I/O 16 QID 0 timeout, reset controller
[  256.769932] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[  256.786083] blk_update_request: I/O error, dev nvme0n1, sector 40704 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  256.786183] blk_update_request: I/O error, dev nvme0n1, sector 41472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  256.786367] nvme nvme0: Abort status: 0x371
[  256.786381] nvme nvme0: Abort status: 0x371
[  287.322517] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[  287.322547] nvme nvme0: Removing after probe failure status: -19
[  317.841253] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[  317.841505] Buffer I/O error on dev nvme0n1, logical block 5088, async page read
[  317.841524] nvme0n1: detected capacity change from 500118192 to 0

This output is quite similar to broken APST support  and workaround to add "nvme_core.default_ps_max_latency_us=0" to kernel parameters is usually advised. Unfortunately it didn't help in my situation.

Right now I'm actually out of ideas how to troubleshoot the problem further and seeking for advice from community...

System itself is up to date:

root@espressobin:~# uname -a
Linux espressobin 5.15.93-mvebu64 #23.02.2 SMP PREEMPT Fri Feb 17 23:51:39 UTC 2023 aarch64 GNU/Linux
root@espressobin:~# cat /etc/deb
debconf.conf    debian_version
root@espressobin:~# cat /etc/debian_version
11.6
root@espressobin:~# cat /etc/issue
Armbian 22.11.1 Bullseye \l

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

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.

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

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
..................
 ..............

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

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

I was using Arch Linux ARM on my Clearfog Pro for years. Then things got bad. I think it's a bad combination to have a distro with the most up-to-date software while developers are rapidly abandoning and not testing 32-bit Linux software. First wget became incompatible with gnutls and then programs in coreutils that use utmp started malfunctioning. The last straw was the system became unbootable, issuing a message about ext4 "ext4fs_devread read outside partition 18446744073709551440".

I switched to Armbian but now I'm at a loss as to how to configure DSA on the Clearfog Pro.

I installed the mv88e6xxx but the LAN ports on the DSA switch did not come to life.

sudo modprobe mv88e6xxx

 Module                  Size  Used by
+mv88e6xxx             139264  0
+dsa_core               61440  1 mv88e6xxx
+hsr                    28672  1 dsa_core
+bridge                163840  2 mv88e6xxx,dsa_core
+stp                    16384  1 bridge
+llc                    16384  2 bridge,stp
 rfkill                 20480  1
 lz4hc                  16384  0
 lz4                    16384  0
 
$ networkctl -a
WARNING: systemd-networkd is not running, output will be incomplete.

IDX LINK TYPE     OPERATIONAL SETUP
  1 lo   loopback n/a         unmanaged
  2 eth0 ether    n/a         unmanaged
  3 eth1 ether    n/a         unmanaged
  4 eth2 ether    n/a         unmanaged

4 links listed.

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024
    link/ether 02:b3:7f:ac:38:c4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
       valid_lft 39361sec preferred_lft 39361sec
    inet6 fdee:207b:f0ce::6ba/128 scope global dynamic noprefixroute 
       valid_lft 39363sec preferred_lft 39363sec
    inet6 fdee:207b:f0ce:0:7b29:63c:40fc:4405/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::e1d8:2674:2151:93fc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1024
    link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1024
    link/ether 00:50:43:0d:19:18 brd ff:ff:ff:ff:ff:ff

Back when it was working on Arch Linux ARM I would see this

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 4e:ea:ed:f3:18:fb brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.8/24 brd 192.168.0.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 2601:14a:600:6420:4cea:edff:fef3:18fb/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 3069586540sec preferred_lft 3069586540sec
    inet6 fe80::4cea:edff:fef3:18fb/64 scope link 
       valid_lft forever preferred_lft forever
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 532
    link/ether 00:50:43:00:05:01 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::250:43ff:fe00:1/64 scope link 
       valid_lft forever preferred_lft forever
5: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 532
    link/ether 00:50:43:05:00:00 brd ff:ff:ff:ff:ff:ff
6: lan5@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
7: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:c0:ca:95:8b:89 brd ff:ff:ff:ff:ff:ff
8: lan4@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
9: lan3@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
10: lan2@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
11: lan1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff
12: lan6@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff

Does anyone know what I should do to bring up the DSA?

Best Regards,

KES

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!

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

Quote

TIM-1.0

mv_ddr-devel-g251bc63 DDR4 16b 1GB 1CS

 

TIM-1.0

mv_ddr-devel-g251bc63 DDR4 16b 1GB 1CS

NOTICE: Booting Trusted Firmware

NOTICE: BL1: v1.3(release):armada-17.06.2:a37c108

NOTICE: BL1: Built : 14:30:53, Jul 5 2

NOTICE: BL2: v1.3(release):armada-17.06.2:a37c108

NOTICE: BL2: Built : 14:30:55, Jul 5 20

NOTICE: BL31: v1.3(release):armada-17.06.2:a37c108

NOTICE: BL31:

 

U-Boot 2017.03-armada-17.06.3-ga33ecb8 (Jul 05 2017 - 14:30:47 +0800)

 

Model: Marvell Armada 3720 Community Board ESPRESSOBin

             CPU @ 1000 [MHz]

             L2 @ 800 [MHz]

             TClock @ 200 [MHz]

             DDR @ 800 [MHz]

DRAM: 1 GiB

U-Boot DComphy-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

SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB

After the boot it tries to boot from a network source instead of sdcard.

printenv

Quote

baudrate=115200

boot_targets=usb sata mmc1 mmc0

bootargs=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/nfs rw ip=10.10.10.4:10.10.10.4:10.10.10.1:255.255.255.0:marvell:eth0:none nfsroot=10.10.10.4:/srv/nfs/

bootcmd=run get_images; run set_bootargs; booti ${kernel_addr} ${ramfs_addr} ${fdt_addr}

bootdelay=2

console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 ethact=neta@30000

ethprime=eth0

fdt_addr=0x1000000

fdt_high=0xffffffffffffffff

fdt_name=fdt.dtb fdtcontroladdr=3fb1a7c8

gatewayip=10.10.10.1

get_images=tftpboot ${kernel_addr} ${image_name}; tftpboot ${fdt_addr} ${fdt_name}; run get_ramfs

get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x3000000; tftpboot ${ramfs_addr} ${ramfs_name}; else setenv ramfs_addr -;fi

hostname=marvell

image_name=Image

initrd_addr=0xa00000

initrd_size=0x2000000

ipaddr=10.10.10.4

kernel_addr=0x2000000

loadaddr=0x2000000

netdev=eth0

netmask=255.255.255.0

ramfs_addr=-

ramfs_name=-

root=root=/dev/nfs rw rootpath=/srv/nfs/

serverip=10.10.10.4

set_bootargs=setenv bootargs ${console} ${root} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:none nfsroot=${serverip}:${rootpath} ${extra_params}

stderr=serial@12000

stdin=serial@12000

stdout=serial@12000

 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?

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.

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>>

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.

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

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

Hello all, 

it is this time of the year again. The pcie struggles with certain devices have returned with LK5.10 and are unfortunately not magically gone with LK5.13

As interest around clearfog is not that high, I am not expecting quick solutions here. But will post my findings and perhaps solution. If you have ideas welcome to chime in.

pcie especially with wifi cards has been troublesome on clearfog (maybe even linux on the whole) forever(?). In LK5.4 we had it at a point where multiple different ones ran fine. Even "higher performance" ones as QCA988X (WLE600). We also list them as "supported hardware" on the download page... Now starting from LK5.10 they are making problems again. QCA988X is not booting while older one Intel Centrino N2200 works fine. I will try to figure this out...

Below are relevant 'dmesg' extracts from the boot. All kernel versions have been booted from the same uboot2018 armbian is using for mvebu/clearfog.

Working good LK4.19

LK 4.19.167-mvebu
http://ix.io/3AlL


[    1.881163] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.881168] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.881172] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.881175] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.881178] pci_bus 0000:00: scanning bus
[    1.881302] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
[    1.881444] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
[    1.882442] pci_bus 0000:00: fixups for bus
[    1.882448] PCI: bus0: Fast back to back transfers disabled
[    1.882452] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    1.882456] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.882461] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 0
[    1.882464] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.882468] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    1.882504] pci_bus 0000:01: scanning bus
[    1.882522] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000
[    1.882548] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    1.882572] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    1.882634] pci 0000:01:00.0: supports D1 D2
[    1.883705] pci_bus 0000:01: fixups for bus
[    1.883710] PCI: bus1: Fast back to back transfers disabled
[    1.883713] pci_bus 0000:01: bus scan returning with max=01
[    1.883717] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.883723] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 1
[    1.883762] pci_bus 0000:02: scanning bus
[    1.884756] pci_bus 0000:02: fixups for bus
[    1.884758] PCI: bus2: Fast back to back transfers enabled
[    1.884761] pci_bus 0000:02: bus scan returning with max=02
[    1.884764] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    1.884768] pci_bus 0000:00: bus scan returning with max=02
[    1.884786] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    1.884792] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
[    1.884802] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
[    1.884806] pci 0000:00:02.0: PCI bridge to [bus 01]
[    1.884810] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    1.884815] pci 0000:00:03.0: PCI bridge to [bus 02]


[    6.693469] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.761303] systemd[1]: Finished Raise network interfaces.
[    6.774501] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.848202] PKCS#7 signature not signed with a trusted key
[    6.848213] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    6.862199] ath10k_pci 0000:01:00.0: assign IRQ: got 80
[    6.866856] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[    6.871638] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    6.871655] pci 0000:00:02.0: enabling bus mastering
[    6.871662] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[    6.871671] ath10k_pci 0000:01:00.0: enabling bus mastering
[    6.871920] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    7.068348] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[    7.068355] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[    7.068894] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[    7.106317] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08

Working good LK5.4

LK 5.4.149-mvebu
http://ix.io/3AlL

[    1.903720] mvebu-pcie soc:pcie: /soc/pcie/pcie@2,0: reset gpio is active low
[    1.903925] mvebu-pcie soc:pcie: /soc/pcie/pcie@3,0: reset gpio is active low
[    1.904430] mmc0: new high speed SDHC card at address aaaa
[    1.904726] mmcblk0: mmc0:aaaa ACLCD 29.7 GiB
[    1.906798]  mmcblk0: p1
[    2.083351] ata1: SATA link down (SStatus 0 SControl 300)
[    2.083371] ata2: SATA link down (SStatus 0 SControl 300)
[    2.091349] ata4: SATA link down (SStatus 0 SControl 300)
[    2.091363] ata3: SATA link down (SStatus 0 SControl 300)
[    2.117318] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    2.117324] pci_bus 0000:00: root bus resource [bus 00-ff]
[    2.117328] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    2.117332] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    2.117336] pci_bus 0000:00: scanning bus
[    2.117448] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
[    2.117462] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    2.117595] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
[    2.117605] pci 0000:00:03.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    2.118385] pci_bus 0000:00: fixups for bus
[    2.118391] PCI: bus0: Fast back to back transfers disabled
[    2.118395] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    2.118399] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    2.118404] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 0
[    2.118408] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    2.118413] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    2.118455] pci_bus 0000:01: scanning bus
[    2.118474] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000
[    2.118500] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    2.118524] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    2.118591] pci 0000:01:00.0: supports D1 D2
[    2.119429] pci_bus 0000:01: fixups for bus
[    2.119435] PCI: bus1: Fast back to back transfers disabled
[    2.119438] pci_bus 0000:01: bus scan returning with max=01
[    2.119443] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    2.119449] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 1
[    2.119490] pci_bus 0000:02: scanning bus
[    2.120260] pci_bus 0000:02: fixups for bus
[    2.120262] PCI: bus2: Fast back to back transfers enabled
[    2.120265] pci_bus 0000:02: bus scan returning with max=02
[    2.120269] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    2.120274] pci_bus 0000:00: bus scan returning with max=02
[    2.120293] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    2.120298] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    2.120302] pci 0000:00:03.0: BAR 6: assigned [mem 0xe0400000-0xe04007ff pref]
[    2.120308] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
[    2.120317] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
[    2.120321] pci 0000:00:02.0: PCI bridge to [bus 01]
[    2.120326] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    2.120331] pci 0000:00:03.0: PCI bridge to [bus 02]


[    6.675948] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.690769] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.708861] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    6.729342] systemd[1]: Finished Raise network interfaces.
[    6.836270] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[    6.841362] ath10k_pci 0000:01:00.0: assign IRQ: got 81
[    6.841721] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    6.841735] pci 0000:00:02.0: enabling bus mastering
[    6.841741] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[    6.841750] ath10k_pci 0000:01:00.0: enabling bus mastering
[    6.841920] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    7.050902] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[    7.050909] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
[    7.051434] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[    7.087755] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08

Breaking LK5.10

LK 5.10.60-mvebu
http://ix.io/3AlL

[    1.762421] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges:
[    1.762431] mvebu-pcie soc:pcie: Parsing ranges property...
[    1.762447] mvebu-pcie soc:pcie:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    1.762460] mvebu-pcie soc:pcie:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    1.762472] mvebu-pcie soc:pcie:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    1.762494] mvebu-pcie soc:pcie:      MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
[    1.762507] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.762518] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.762529] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.762540] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.762551] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.762562] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.762573] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.762580] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.762620] mvebu-pcie soc:pcie: /soc/pcie/pcie@2,0: reset gpio is active low
[    1.762824] mvebu-pcie soc:pcie: /soc/pcie/pcie@3,0: reset gpio is active low
[    1.788078] mmc0: new high speed SDHC card at address aaaa
[    1.788385] mmcblk0: mmc0:aaaa ACLCD 29.7 GiB 
[    1.790341]  mmcblk0: p1
[    1.977439] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.977446] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.977452] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    1.977457] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    1.977461] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    1.977466] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff])
[    1.977469] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.977473] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.977477] pci_bus 0000:00: scanning bus
[    1.977601] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
[    1.977611] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.977823] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
[    1.977834] pci 0000:00:03.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.978843] pci_bus 0000:00: fixups for bus
[    1.978851] PCI: bus0: Fast back to back transfers disabled
[    1.978857] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    1.978861] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.978867] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 0
[    1.978871] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.978876] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    1.978919] pci_bus 0000:01: scanning bus
[    1.978947] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000
[    1.978965] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    1.978989] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    1.979062] pci 0000:01:00.0: supports D1 D2
[    1.979149] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[    1.999532] ata4: SATA link down (SStatus 0 SControl 300)
[    1.999535] ata2: SATA link down (SStatus 0 SControl 300)
[    1.999568] ata1: SATA link down (SStatus 0 SControl 300)
[    1.999571] ata3: SATA link down (SStatus 0 SControl 300)
[    2.013354] pci 0000:00:02.0: up support 3 enabled 0
[    2.013358] pci 0000:00:02.0: dn support 0 enabled 0
[    2.014320] pci_bus 0000:01: fixups for bus
[    2.014324] PCI: bus1: Fast back to back transfers enabled
[    2.014328] pci_bus 0000:01: bus scan returning with max=01
[    2.014333] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    2.014340] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 1
[    2.014390] pci_bus 0000:02: scanning bus
[    2.015336] pci_bus 0000:02: fixups for bus
[    2.015339] PCI: bus2: Fast back to back transfers enabled
[    2.015342] pci_bus 0000:02: bus scan returning with max=02
[    2.015346] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    2.015351] pci_bus 0000:00: bus scan returning with max=02
[    2.015374] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    2.015380] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    2.015387] pci 0000:00:03.0: BAR 6: assigned [mem 0xe0400000-0xe04007ff pref]
[    2.015393] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
[    2.015399] pci 0000:01:00.0: BAR 0: error updating (0xe0000004 != 0xffffffff)
[    2.015403] pci 0000:01:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff)
[    2.015408] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
[    2.015412] pci 0000:00:02.0: PCI bridge to [bus 01]
[    2.015418] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    2.015423] pci 0000:00:03.0: PCI bridge to [bus 02]


[    6.137823] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.175339] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.235642] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    6.294554] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[    6.321527] ath10k_pci 0000:01:00.0: of_irq_parse_pci: failed with rc=134
[    6.321535] ath10k_pci 0000:01:00.0: assign IRQ: got 0
[    6.322234] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    6.322249] pci 0000:00:02.0: enabling bus mastering
[    6.322255] ath10k_pci 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible)
[    6.352438] ath10k_pci 0000:01:00.0: failed to wake up device : -110
[    6.356213] ath10k_pci 0000:01:00.0: disabling bus mastering
[    6.356343] ath10k_pci: probe of 0000:01:00.0 failed with error -110

Still broken LK5.13

LK 5.13.19-mvebu
http://ix.io/3AlL

[    1.524358] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges:
[    1.524378] mvebu-pcie soc:pcie: Parsing ranges property...
[    1.524394] mvebu-pcie soc:pcie:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    1.524410] mvebu-pcie soc:pcie:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    1.524425] mvebu-pcie soc:pcie:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    1.524439] mvebu-pcie soc:pcie:      MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
[    1.524453] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.524466] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.524480] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.524493] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.524506] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.524519] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.524533] mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.524542] mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.524580] mvebu-pcie soc:pcie: /soc/pcie/pcie@2,0: reset gpio is active low
[    1.524799] mvebu-pcie soc:pcie: /soc/pcie/pcie@3,0: reset gpio is active low
[    1.548105] mmc0: new high speed SDHC card at address aaaa
[    1.548421] mmcblk0: mmc0:aaaa ACLCD 29.7 GiB 
[    1.550417]  mmcblk0: p1
[    1.737513] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.737521] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.737529] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    1.737536] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    1.737542] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    1.737549] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff])
[    1.737554] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.737559] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.737565] pci_bus 0000:00: scanning bus
[    1.737692] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
[    1.737706] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.737898] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
[    1.737910] pci 0000:00:03.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    1.738874] pci_bus 0000:00: fixups for bus
[    1.738882] PCI: bus0: Fast back to back transfers disabled
[    1.738888] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    1.738894] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.738901] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 0
[    1.738907] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.738913] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    1.738962] pci_bus 0000:01: scanning bus
[    1.738990] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000
[    1.739010] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    1.739037] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    1.739111] pci 0000:01:00.0: supports D1 D2
[    1.739204] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[    1.755536] ata1: SATA link down (SStatus 0 SControl 300)
[    1.755561] ata2: SATA link down (SStatus 0 SControl 300)
[    1.763587] ata3: SATA link down (SStatus 0 SControl 300)
[    1.763608] ata4: SATA link down (SStatus 0 SControl 300)
[    1.773427] pci 0000:00:02.0: up support 3 enabled 0
[    1.773433] pci 0000:00:02.0: dn support 0 enabled 0
[    1.774362] pci_bus 0000:01: fixups for bus
[    1.774367] PCI: bus1: Fast back to back transfers enabled
[    1.774372] pci_bus 0000:01: bus scan returning with max=01
[    1.774377] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.774386] pci 0000:00:03.0: scanning [bus 00-00] behind bridge, pass 1
[    1.774436] pci_bus 0000:02: scanning bus
[    1.775348] pci_bus 0000:02: fixups for bus
[    1.775352] PCI: bus2: Fast back to back transfers enabled
[    1.775356] pci_bus 0000:02: bus scan returning with max=02
[    1.775361] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    1.775369] pci_bus 0000:00: bus scan returning with max=02
[    1.775392] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    1.775401] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    1.775410] pci 0000:00:03.0: BAR 6: assigned [mem 0xe0400000-0xe04007ff pref]
[    1.775418] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
[    1.775425] pci 0000:01:00.0: BAR 0: error updating (0xe0000004 != 0xffffffff)
[    1.775432] pci 0000:01:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff)
[    1.775439] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
[    1.775445] pci 0000:00:02.0: PCI bridge to [bus 01]
[    1.775451] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    1.775459] pci 0000:00:03.0: PCI bridge to [bus 02]

[    6.181887] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.198802] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.236001] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    6.265871] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[    6.400151] ath10k_pci 0000:01:00.0: of_irq_parse_pci: failed with rc=134
[    6.400164] ath10k_pci 0000:01:00.0: assign IRQ: got 0
[    6.401115] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    6.401135] pci 0000:00:02.0: enabling bus mastering
[    6.401141] ath10k_pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[    6.431325] ath10k_pci 0000:01:00.0: failed to wake up device : -110
[    6.435003] ath10k_pci 0000:01:00.0: disabling bus mastering
[    6.435134] ath10k_pci: probe of 0000:01:00.0 failed with error -110

All bootlogs etc. are also in the armbianmonitor link attached to this post.

From a first glance there are some errors assigning the pci memory regions, and the main problem seems to be the power state not changing.  I try to figure out breaking version.

Greetings,

Heisath

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.

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.

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

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?

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.

```

[  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 ]---

```

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...

Hi there,

The red LED on the EspressoBin v5 stopped working at Version 20.11.

I opgrade from Armbian_20.02.0-rc1_Espressobin_buster_current_4.19.98
to the laetest version Armbian_20.11_Espressobin_buster_current_5.8.18.
Also not working with Armbian_21.02.0-trunk.18_Espressobin_buster_current_5.8.18.

On Armbian_20.02.0-rc1 to Armbian_20.05.2:

root@espressobin:/sys/class/leds# ls -al
total 0
drwxr-xr-x  2 root root 0 Jan 25  2020 .
drwxr-xr-x 51 root root 0 Feb 14  2019 ..
lrwxrwxrwx  1 root root 0 Jan 25  2020 espressobin:red:usr -> ../../devices/platform/leds/leds/espressobin:red:usr
lrwxrwxrwx  1 root root 0 Jan 25  2020 mmc0:: -> ../../devices/platform/soc/soc:internal-regs@d0000000/d00d8000.sdhci/leds/mmc0::
lrwxrwxrwx  1 root root 0 Jan 25  2020 mmc1:: -> ../../devices/platform/soc/soc:internal-regs@d0000000/d00d0000.sdhci/leds/mmc1::
root@espressobin:/sys/class/leds#
root@espressobin:/sys/class/leds/espressobin:red:usr# ls -al
total 0
-rw-r--r-- 1 root root 4096 Nov 30 15:37 brightness
lrwxrwxrwx 1 root root    0 Nov 30 15:37 device -> ../../../leds
-r--r--r-- 1 root root 4096 Nov 30 15:37 max_brightness
drwxr-xr-x 2 root root    0 Jan 25  2020 power
lrwxrwxrwx 1 root root    0 Jan 25  2020 subsystem -> ../../../../../class/leds
-rw-r--r-- 1 root root 4096 Nov 30 15:37 trigger
-rw-r--r-- 1 root root 4096 Jan 25  2020 uevent
root@espressobin:/sys/class/leds/espressobin:red:usr#

user_led_on:
echo 255 > /sys/class/leds/espressobin:red:usr/brightness

user_led_off:
echo 0 > /sys/class/leds/espressobin:red:usr/brightness

user_led_trigger:
echo heartbeat > /sys/class/leds/espressobin:red:usr/trigger

Now on Armbian_20.11:

root@espressobin:/sys/class/leds# ls -al
total 0
drwxr-xr-x  2 root root 0 Nov 25 12:19 .
drwxr-xr-x 54 root root 0 Feb 14  2019 ..
lrwxrwxrwx  1 root root 0 Nov 25 12:19 mmc0:: -> ../../devices/platform/soc/soc:internal-regs@d0000000/d00d0000.sdhci/leds/mmc0::
root@espressobin:/sys/class/leds#

Its seems file armada-3720-espressobin.dtb this not supported more.
Is there also another way that it works again?

Any suggestion ? 

Kind regards,
Thanks

Hi I am trying to get my board restored.   Following a simple power on reset, which I have done many, many times in the past.   I have never worked with this or any other board at this low a level before (UART restore - whatever that is.) The entire memory of the bootloader has been wiped out for no apparent reason. I am wondering if this is a common problem after seeing 3 other people reporting it on the espressobin forum? 

All I have is the E and > appearing on the serial console.   I am following this page:

http://wiki.espressobin.net/tiki-index.php?page=Bootloader%2Brecovery%2Bvia%2BUART

In the image choices I can download, it offers a boot image of 1G DDR3 (my version is V5 and 1G sticker on the board) but I don't know how to tell if I need the 2CS or 1CS firmware because I don't know what chips to look for on the board to see if I have a 1 Gig chip or a 2 512M chip model which the only indication of my memory is via a round sticker stuck on the LAN connector labeled "1G".

I am looking for the best boot image to run with OpenWRT (no offense).   Thanks in advance!   (I am very low skilled in this area so please have mercy.   I also need a copy of the WTPTP executable for Windows 10 if anyone has it.   Espressobin now demands anyone who wants the Windows tools to register for their customer portal and this portal requires anyone who wants the tools to sign a non-disclosure agreement by contacting their sales team.   Plus, they don't answer online inquiries or their telephone.   Any help or guidance would be appreciated.

Hello,

I have discovered interesting behaviour of the clearfogpro switching between lk4.19 and 5.8 and would like to know if others are able to reproduce. And maybe have ideas on how to fix.

Steps to reproduce: 

- have a clearfogpro

- get the current armbian image https://archive.armbian.com/clearfogpro/archive/  20.08

- 'apt update && apt full-upgrade' 

- set the lan1-6 interfaces to bridging (example via following /etc/network/interfaces : https://pastebin.com/dpXEBe6g )

- reboot

- plug into your network should be GBit (on lan1-5). Verify you get ip, and can reach other devices.

- run iperf3 between clearfogpro and other gbit device in your network. Should yield about 900MBit/s

Now the interesting part:

- attach another device to the switch

- see how both status leds blink when transfering data via iperf3 ?     The bridge seems to run as a hub and not a switch.

- now plug a 100mbit/s device into the bridge.

- test speed to a gbit device with iperf (both directions): one direction will only yield about 100mbit/s. 

- while iperf3 is running to the gbit device, unplug and replug the 100mbit/s device on the switch, you should see the rate jump between 100 and 1000.....

NOTICE: This only happens in the direction where the clearfogpro is receiving data. Send speed is still at 1gbit/s.

Now use armbian-config and switch to LK4.19, reproduce steps from above. You should only see one activity led blinking and the switch functioning correctly at 1gbit/s even with a 100mbit/s device connected. 

So this leads me to think there's either some difference in the handling of the clearfogpro switch chip (between LK4 and 5) or some difference in bridge package. 

It would be great if someone could confirm so I am sure, it is not a problem with my setup.

root@clearfogpro:~# iperf3 -c 192.168.42.3 -t 100 -R
Connecting to host 192.168.42.3, port 5201
Reverse mode, remote host 192.168.42.3 is sending
[  5] local 192.168.42.106 port 33648 connected to 192.168.42.3 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  11.3 MBytes  94.3 Mbits/sec	# 100mbit/s device plugged into the switch 
[  5]   1.00-2.00   sec  11.2 MBytes  94.1 Mbits/sec
[  5]   2.00-3.00   sec  11.2 MBytes  94.1 Mbits/sec
[  5]   3.00-4.00   sec  11.2 MBytes  94.1 Mbits/sec
[  5]   4.00-5.00   sec  26.7 MBytes   224 Mbits/sec	# 100mbit/s device removed
[  5]   5.00-6.00   sec   107 MBytes   900 Mbits/sec
[  5]   6.00-7.00   sec   105 MBytes   878 Mbits/sec
[  5]   7.00-8.00   sec   107 MBytes   893 Mbits/sec
^C[  5]   8.00-8.61   sec  63.9 MBytes   885 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-8.61   sec  0.00 Bytes  0.00 bits/sec                  sender
[  5]   0.00-8.61   sec   454 MBytes   443 Mbits/sec                  receiver

Apologies, I couldn't move the code block once I'd put it in here.

I'm trying to boot Armbian_20.08.2_Espressobin_buster_current_5.8.6.img written onto a known-good SD card. I've tried both on an older bootloader and the 2018 one suggested by Armbian.

Just updated both my cubietruck and espressobin to 5.85, however the latter doesn't up come again after the update (from 5.83 IMO).

(Had to get it out of the basement and) the console gives me the following error msg, now:
 

Marvell>> boot
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
/
Card did not respond to voltage select!
** Bad device mmc 1 **
## Executing script at 06d00000
Wrong image format for "source" command
/boot/
Card did not respond to voltage select!
** 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/
1119 bytes read in 13 ms (84 KiB/s)
## Executing script at 06d00000
221 bytes read in 5 ms (43 KiB/s)
16488960 bytes read in 706 ms (22.3 MiB/s)
6196865 bytes read in 275 ms (21.5 MiB/s)
** File not found /boot/dtb/marvell/armada-3720-community.dtb **
8942 bytes read in 9 ms (969.7 KiB/s)
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    6196801 Bytes = 5.9 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 3f042000, end 3f62ae41 ... OK
   Using Device Tree in place at 0000000006000000, end 00000000060052ed

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 4.19.41-mvebu64 (root@armbian.com) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.85 SMP PREEMPT Wed May 8 16:07:35 CEST 2019
[    0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board
[    0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
[    0.000000] bootconsole [ar3700_uart0] enabled
Loading, please wait...
starting version 232
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.29.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1
/dev/mmcblk1p1: clean, 55272/444624 files, 453885/1900644 blocks
done.
done.
Begin: Running /scripts/local-bottom ... /scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdadm: rm: not found
done.
Begin: Running /scripts/init-bottom ... done.
[    6.537013] SError Interrupt on CPU1, code 0xbf000001 -- SError
[    6.537017] CPU: 1 PID: 1 Comm: init Not tainted 4.19.41-mvebu64 #5.85
[    6.537019] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[    6.537021] pstate: 20000005 (nzCv daif -PAN -UAO)
[    6.537023] pc : get_page_from_freelist+0x5c/0x10e8
[    6.537025] lr : __alloc_pages_nodemask+0xf4/0xb48
[    6.537026] sp : ffffff8008033970
[    6.537028] x29: ffffff8008033970 x28: 0000000000000002
[    6.537032] x27: 00000000006200ca x26: 0000000000000081
[    6.537035] x25: 0000000000000000 x24: 0000000000000000
[    6.537039] x23: 0000000000000000 x22: ffffff8008033b38
[    6.537042] x21: ffffffc03ffeb500 x20: 0000000000000081
[    6.537046] x19: ffffffc03ffea180 x18: 0000000000000000
[    6.537049] x17: 0000000000000000 x16: 0000000000000000
[    6.537053] x15: 0000000000000000 x14: 0000000000000000
[    6.537056] x13: 0000000000000000 x12: 0000000000000000
[    6.537060] x11: 0000000000000000 x10: 0000000000000000
[    6.537063] x9 : 0000000000000000 x8 : 0000000000000000
[    6.537066] x7 : 0000000000000000 x6 : 0000000000000000
[    6.537070] x5 : 0000000000000014 x4 : 0000000000000000
[    6.537073] x3 : 0000000000000000 x2 : 00000000000000c0
[    6.537077] x1 : 0000000000000001 x0 : 0000000000000068
[    6.537081] Kernel panic - not syncing: Asynchronous SError Interrupt
[    6.537083] CPU: 1 PID: 1 Comm: init Not tainted 4.19.41-mvebu64 #5.85
[    6.537085] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[    6.537087] Call trace:
[    6.537088]  dump_backtrace+0x0/0x1a0
[    6.537089]  show_stack+0x14/0x20
[    6.537091]  dump_stack+0x9c/0xbc
[    6.537092]  panic+0x130/0x2a4
[    6.537093]  nmi_panic+0x6c/0x70
[    6.537095]  arm64_serror_panic+0x74/0x88
[    6.537096]  do_serror+0x134/0x138
[    6.537098]  el1_error+0x7c/0xdc
[    6.537099]  get_page_from_freelist+0x5c/0x10e8
[    6.537101]  __alloc_pages_nodemask+0xf4/0xb48
[    6.537102]  alloc_pages_vma+0x88/0x210
[    6.537104]  __handle_mm_fault+0x3e8/0xdc8
[    6.537105]  handle_mm_fault+0x11c/0x1e0
[    6.537107]  do_page_fault+0x1c0/0x480
[    6.537108]  do_translation_fault+0x58/0x60
[    6.537110]  do_mem_abort+0x54/0x100
[    6.537111]  el0_da+0x20/0x24
[    6.537130] SMP: stopping secondary CPUs
[    6.537131] Kernel Offset: disabled
[    6.537133] CPU features: 0x0,2080200c
[    6.537134] Memory Limit: none
[    6.755334] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

as per title...

i have 2 boards running armbian (Debian version). Even if the mac addresses on  /boot/armbianEnv.txt are set differently,  all nic cards of both boards, have the same exact mac address, specifically f0:ad:4e:03:64:7f   this of course creates a lot of problems because i cannot connect my 2 boards in the same network

here is armbianmonitor from the 1st board - https://pastebin.com/N9AuwV2h

 here is the same for the 2nd board -  https://pastebin.com/QcTq3BaD

apparently i am not the only one http://espressobin.net/forums/topic/each-network-interface-has-the-same-mac-address/

I'm getting tired of Globalscale deleting my post from the Espressobin forums, instead of either fixing or acknowledging the problem.

So I'll repost this here for future reference. This is the URL to the original thread: http://espressobin.net/forums/topic/mainline-linux-not-running-at-1ghz/

Hi All

That the Espressobin aims to support mainline is awesome – a lot of the benefits are described here http://espressobin.net/mainline-linux/.

But I’m unable to get my v7 board running at more than 800MHz using the mainline kernel (for some reason cpufreq-info insists on reporting 1GHz with actual benchmarking only showing 800MHz).

For the sake of this post, I tried pulling the most recent linux-next kernel. I’m using the config file from armbian.

export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
git checkout next-20190614
curl https://raw.githubusercontent.com/armbian/build/master/config/kernel/linux-mvebu64-next.config > .config
make oldconfig # Just picked the defaults for new options
make -j7 Image dtbs modules

cp arch/arm64/boot/Image /mnt/sdcard/boot/
cp arch/arm64/boot/dts/marvell/armada-3720-espressobin.dtb /mnt/sdcard/boot/dtb/marvell/
make modules_install INSTALL_MOD_PATH=/mnt/sdcard/

Here are the results. Notice the performance numbers and CPU Freq reported by 7-Zip:

root@espressobin:~# uname -a
Linux espressobin 5.2.0-rc4-next-20190614 #7 SMP PREEMPT Sun Jun 16 10:27:52 CEST 2019 aarch64 GNU/Linux

root@espressobin:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 0.97 ms.
  hardware limits: 200 MHz - 1000 MHz
  available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 250 MHz and 1000 MHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 200 MHz:0.09%, 250 MHz:3.60%, 500 MHz:0.16%, 1000 MHz:96.15%  (152)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 0.97 ms.
  hardware limits: 200 MHz - 1000 MHz
  available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 250 MHz and 1000 MHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 200 MHz:0.09%, 250 MHz:3.60%, 500 MHz:0.16%, 1000 MHz:96.15%  (152)

root@espressobin:~# lscpu
Architecture:          aarch64
Byte Order:            Little Endian
CPU(s):                2
On-line CPU(s) list:   0,1
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Model:                 4
CPU max MHz:           1000.0000
CPU min MHz:           200.0000
BogoMIPS:              25.00
NUMA node0 CPU(s):     0,1
Flags:                 fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid

root@espressobin:~# 7za b

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,2 CPUs LE)

LE
CPU Freq:   794   794   794   794   794   794   794   794

RAM size:     986 MB,  # CPU hardware threads:   2
RAM usage:    441 MB,  # Benchmark threads:      2

                       Compressing  |                  Decompressing
Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
         KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS

22:        709   148    467    690  |      17938   199    771   1532
23:        701   149    480    715  |      17737   199    770   1535
24:        696   149    503    749  |      17395   199    768   1527
25:        688   149    528    786  |      17149   198    769   1526
----------------------------------  | ------------------------------
Avr:             149    494    735  |              199    770   1530
Tot:             174    632   1133

The following are the performance numbers I’m looking for, achieved using 4.4.8-armada-17.02-espressobin kernel downloaded from http://espressobin.net/tech-spec/. That one, and 4.4.52-armada-17.10.4-g719fc86-dirty are the only kernels I have been able to actually get 1GHz performance with:

root@espressobin:~# uname -a
Linux espressobin 4.4.52-armada-17.10.4-g719fc86-dirty #7 SMP PREEMPT Tue Jul 3 10:59:53 UTC 2018 aarch64 GNU/Linux

root@espressobin:~# 7za b

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,2 CPUs LE)

LE
CPU Freq:   734   997   998   998   998   992   996   996

RAM size:     927 MB,  # CPU hardware threads:   2
RAM usage:    441 MB,  # Benchmark threads:      2

                       Compressing  |                  Decompressing
Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
         KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS

22:        870   150    563    847  |      22431   198    969   1915
23:        860   151    582    876  |      22154   198    968   1918
24:        854   151    607    918  |      21735   198    963   1908
25:        848   152    639    969  |      21341   198    960   1900
----------------------------------  | ------------------------------
Avr:             151    598    903  |              198    965   1910
Tot:             174    781   1406

Following http://wiki.espressobin.net/tiki-index.php?page=Build+From+Source+-+Kernel to build 4.4.52-armada-17.10.4-g719fc86-dirty also works fine at 1GHz.

I’ve tried a bunch of different U-boots, all with the same result, so I really think the bug is in Linux.

(FYI this is not the only problem I have been having with the v7, but lets focus on one bug at a time. Not to mention that Globalscale claims 1.2 GHz for v7 which seems entirely out of reach as any 1200 u-boot bricks my board).

Hi Everyone,

I'm considering getting an Espressobin to use as a simple NAS. Is this a good idea?

My requirements are quite basic; a single SATA SSD and a single ethernet port, running NFS and Samba. I do need a newish version of Samba (required to support "Time Machine" backup from my Mac) which I believe is in Debian Buster but not in Stretch. I've been a Debian user for decades; I guess I might be happier if the hardware supplier provided a Debian image, but it's great that Armbian is available.

This board's hardware looks good; it has a SATA connector. But there are a few posts here mentioning stability issues, related to power supply hardware or possibly u-boot. And the board has recently had an update (v7) which may have made it better in some ways but less reliable???

Anyway, I'm posting this mainly to see if anyone shouts "No, Bad Idea!". What's the verdict? I'm looking for something that "just works"; I don't want to have to fiddle around with things for days! (I've done enough of that in the past.)

Also: can anyone recommend an enclosure that would take this board and an SSD?
Also2: is it correct that I don't need an SD card or eMMC if I have an external SATA disk for the root filesystem?

Thanks, Phil.

Hi everyone,

I updated the Linux kernel on my Espressobin to the latest version (5.6.2) and had some issues booting from SATA as my SSD was not detected properly after boot.
Using the device tree from an older kernel version did help, but I also read somewhere that updating to the latest Armbian U-Boot would solve the issue.

So I downloaded the version that matches my hardware (flash-image-ddr3-2g-2cs-1000_800.bin) and flashed it.

It indeed fixed the boot issues, but now only 1 GB of RAM is detected instead of 2 GB.

This happens as soon as the board is powered on, in U-Boot:

DRAM:  1 GiB

Before that, I was using the U-Boot version from espressobin.net, and the 2 GB were detected and usable.

I'm sure of it, because before downloading the Armbian U-Boot I checked the output to make sure that I indeed had the 2 GB version.

I cannot do a downgrade to verify this right now, because the espressobin.net website is broken; most pages report a 404 error, including the one where the U-Boot files were located.

I tried different versions, like the slower flash-image-ddr3-2g-2cs-800_800.bin or the version in the https://dl.armbian.com/espressobin/u-boot/archive/10/ folder, with similar results.

I also tried the 1200 MHz version out of curiosity, and had to recover the SPI flash using the SATA rescue image.

In any case, I would prefer to continue using the Armbian U-Boot version, since it is more up to date and works with the current mainline kernel and device tree.

I did not find any answer for this in the forums or using Google.

I actually find it very odd that it works at all.

What is then used? Only one RAM chip? Or 512 MB from each?

Did I install the wrong image, or did I miss a step when migrating U-Boot?

Hi All!

I am verifying the function about pcie  to net port on armada-3720 ESPRESSObin. I insert 3 PCIE network cards in 3720 with PCIE bridge, connect to PC by switch. PC ping 3 net port at the same time ,but only one net port could be pinged successfully.   

I use the same test environment to test on the cavium's development board ,and  PC can ping 3 network cards successfully at the same time.

Besides, I used 3 network cards connect to 3 PC directly not by switch on 3720, and 3 PC can also ping 3 network cards successfully at the same time.

Through the above cross-testing, it seems that this problem will occur as long as there is some communication connection between different network cards. I think it may be related to the 3720's pcie driver and compatibility.  Is it?    

linux-kernel 4.14    https://github.com/MarvellEmbeddedProcessors/linux-marvell/tree/linux-4.14.76-armada-18.12

can somebody confirm this problem?
 

in the year 2017 someone mentioned in http://espressobin.net/forums/topic/boot-behavior-of-the-switch-and-security/

some security concerns with older uboot bootloaders and port-mask setting in armada-3720-espressobin.dts(i)

this seems still to be the case in the current released armbian bootloaders  found in https://dl.armbian.com/espressobin/u-boot/

WTMI-devel-18.12.1-e6bb176
U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100)

since they also seem to use  port-mask = <0xf> instead of the suggested port-mask = <0x3> ?!

https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/blob/u-boot-2018.03-armada-18.12/arch/arm/dts/armada-3720-espressobin.dts#L55

this means...

as soon as ESPRESSOBin board (revision v5 and v7) gets powered up,  you will see that u-boot is still initialising the switch chipset to forward traffic.

u-boot sets the topaz switch chipsatz portmask in a way that the board is in "full switch mode" and  all ports are bridged.

security concers:

* at every "normal" reboot you have bridged the ports for some seconds, until armbian final loads the linux kernel, newer dtb and module mv88e6xxx.
* but furthermore... if you stop autoboot manually, or if your boot fails for any reason (boot-medium has a corrupt filesystem).. you will run into the serious problem,
that you're stuck in the Marvell Uboot Console, which is default forwarding all traffic... and so you LAN and WAN ports are bridged all the time. 

the switch chipset seems to have bootstrap pins which allows at least 3 different configurations:
1. start with forwarding enabled
2. start with forwarding disabled
3. fetch configuration from EEPROM

as mentioned in espressobin forum, the RGE_RXD3 has a pull down and tis should prevent traffic flow at reset/power up by default..
.... but u-boot is (re)enabling the forward again.

So it seems, that all uboot images for espressobin should have the setting with disabled lan ports and just use wan port per default.

how to fix?
 

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>>

Quote

load ${boot_interface} ${devnum}:1 ${scriptaddr} ${prefix}armbianEnv.txt
env import -t ${scriptaddr} ${filesize}

-Is this correct ?

scriptaddr is where the boot.scr is loaded, as far as I understand, it overwrites itself by loading armbianEnv.txt to the same address.

So wouldn't it be better to load armbianEnv.txt to kernel_addr, initrd_addr or fdt_addr, since armbianEnv.txt is only used for a short time ?

I have not tried making an armbianEnv.txt, which is larger than boot.scr, but it looks like it would stop the board from booting if it's just long enough to overwrite the 'env import' line.

My impression is that it's very much like setting up Xenial and the same issues seem to be present.

I mention them in the order of importance.

1: #reboot sometimes hang, so does #poweroff. It would be great to get this fixed, because it would be a disaster if a device hangs on rebooting from remote (eg. the device is 200km away).

2: sudo apt-get update && sudo apt-get upgrade destroys the network setup. No network access is possible after doing this. I think a fix is important, because people would likely issue those commands.

3: Network seem to be configured slightly different than on Xenial; it seems I cannot configure a static IP on the WAN port (see my other post specifically on static IP). For now, I'll be using a static IP address on the br0, this works, so it's not the highest priority.

I definitely also need to write some good stuff.

1: 3Gbit JMB321 Port Multipliers work well with Xenial (and likely also Bionic); just remember to connect the boot device to SATA0 and there should be no problems.

2: 6Gbit JMB575 (StarTech) works great with Bionic (and likely also Xenial); again connect the boot device to SATA0.

For those, who want to boot "directly" from SATA, this is what I do on both boards; it's fairly easy and there are plenty of ways you can do it.

The first time, I just made a 'dd' from my SD-card's partition to my harddisk's partition. This works fine and the partition will be expanded when Armbian boots.

My preferred way, though, is to make a tarball of the unmodified SD-image's partition, boot my EspressoBIN from the SD-card and extract the files onto my desired partition. This gives me a different UUID from the SD-card, thus inserting the Armbian SD card won't confuse my boot-up sequence.

To create a tarball, this can be used (mounted as /mnt/sd) ...

cd /mnt/sd && sudo tar -cpzf /data/armbian-bionic-rootfs.tar.gz .

To extract onto your partition (mounted as /mnt/rootfs), this can be used ...

cd /mnt/rootfs && sudo tar -xpzf /data/armbian-bionic-rootfs.tar.gz -C .

Those will preserve permissions, timestamps and other attributes as necessary, but this will only happen if you're root, otherwise permissions will be messed up and you'll get a half-working system (quite useless).

I use a custom UUID on my own setup, so that I only need to set it once in u-boot. I highly recommend using UUID for identifying the boot device, especially is you use a port multiplier, because you never know if a USB-drive suddenly get /dev/sda instead of the drive you expect.

In your startup boot sequence, I recommend a 3-stage check ...

1: Check for SD-card (SD/MMC slot)

2: Check for USB-boot

3: Use a 'scsi scan; scsi dev $bootdev:$bootpart;' then check for your SATA-device here.

Personally I only have step 1 and 3, since I often mount my SD-card as a USB-drive when I do not want to boot from it.

The Espresobin wiki says

2 x Gigabit Ethernet 1Gbps / 2.5Gbps
SGMII / HS-SGMII / RGMII

Does that mean we actually have 2.5Gbps Nic x2?

I also find this link

But it's saying 

Quote

..and I think i'm officially convinced that the max bandwidth between topaz switch and cpu is in fact 1gigabit... The connection is using a seperate RGMII lane. (eth0)

And there is even an official wiki talking about 2.5Gbps. Anyone has any luck on 2.5Gbps mode?

Hi all, I have an espressobin v5, running the newest Armbian 20.02.01 Buster that is available online (installed just recently). I am using this device as a home gateway/router so there is hostapd,  dnsmasq, iptables that kind which is all working perfectly.

But I cannot enable name resolution for the subnet!! Packet forwarding works fine, if I set the DNS manually on any of the devices connected to the subnet then the connection works perfectly but I would prefer to have it performed dynamically for any guest that connects.

I installed bind9, this is the named.conf.options file:

acl allowed_clients {
        localhost;
        172.24.0.0/16;
};

options {
        directory "/var/cache/bind";
        // managed-keys-directory "/etc/bind";

        // If there is a firewall between you and nameservers you want
        // to talk to, you may need to fix the firewall to allow multiple
        // ports to talk.  See http://www.kb.cert.org/vuls/id/800113

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

        recursion yes;
        allow-query { allowed_clients; };
        forward only;
        listen-on {
                //172.24.0.0/16;
                any;};

        forwarders {
                208.67.222.222;
                208.67.220.220;
        };

        //========================================================================
        // If BIND logs error messages about the root key being expired,
        // you will need to update your keys.  See https://www.isc.org/bind-keys
        //========================================================================
        dnssec-validation auto;

        listen-on-v6 { none; };
};

The status of the bind9 service shows the following:
 

Mar 18 15:35:25 espressobin named[671]: zone 255.in-addr.arpa/IN: loaded serial 1
Mar 18 15:35:25 espressobin named[671]: zone localhost/IN: loaded serial 2
Mar 18 15:35:25 espressobin named[671]: all zones loaded
Mar 18 15:35:25 espressobin named[671]: running
Mar 18 15:35:25 espressobin named[671]: network unreachable resolving './DNSKEY/IN': 208.67.222.222#53
Mar 18 15:35:25 espressobin named[671]: network unreachable resolving './DNSKEY/IN': 208.67.220.220#53
Mar 18 15:35:25 espressobin named[671]: managed-keys-zone: Unable to fetch DNSKEY set '.': SERVFAIL
Mar 18 15:35:26 espressobin systemd[1]: Started BIND Domain Name Server.
Mar 18 15:37:18 espressobin named[671]: listening on IPv4 interface br1, 172.24.1.1#53
Mar 18 15:37:21 espressobin named[671]: listening on IPv4 interface wan, 192.168.0.10#53

If anyone can point out what I am doing wrong I would be grateful. The bridge br1 bridges between lan0, lan1 and wlx24050fae5224 (wireless transceiver).

Hi there,

a erroneously powered the Espressobin (V7) with my laptop power-supply [ i.e. 19V 2.31A ( right polarity i.e. + inside) ] ...

The EspressoBin now does not boot.

A green led lights-up for a moment and then nothing else.

Any suggestion ?

Thanks

Hi, 

We made a custom board based on ClearfogBase. And we will change the size of DDR to 512MB.

But, I have no idea if it would work without any software changes.

Thanks in advance

JS

I just got a new espressobin v7 with 2gb of ram. Output from working u-boot:

U-Boot 2017.03-armada-17.10.2-g255b9cc (Nov 07 2018 - 09:48:30 +0800)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  2 GiB
U-Boot DT blob at : 000000007f7161b8
Comphy-0: USB3          5 Gbps
Comphy-1: PEX0          2.5 Gbps
Comphy-2: SATA0         6 Gbps

...

Marvell>> sspi
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB

Marvell>> version

U-Boot 2017.03-armada-17.10.2-g255b9cc (Nov 07 2018 - 09:48:30 +0800)
aarch64-linux-gnu-gcc (Linaro GCC 5.3-2016.05) 5.3.1 20160412
GNU ld (Linaro_Binutils-2016.05) 2.25.0 Linaro 2016_02

I'm trying to update to the latest u-boot version from here https://dl.armbian.com/espressobin/u-boot/  flash-image-ddr4-2g-2cs-1000_800.bin

Marvell>> bubt flash-image-ddr4-2g-2cs-1000_800.bin spi usb
Burning U-BOOT image "flash-image-ddr4-2g-2cs-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... ** First descriptor is NOT a primary desc on 0:1 **
2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
Image checksum...OK!
823492 bytes written, 65536 bytes skipped in 7.538s, speed 120754 B/s
Done!

So everything seems to go ok. From here, I reset the board and I get nothing at all. No serial console, nothing. I need to go into uart just to get any kind of a sign that the board is still alive. From uart I can recover using the following image from http://espressobin.net/tech-spec/ (U-Boot 2017.03-armada-17.10):

espressobin-bootloader-cpu-1000-ddr4-2cs-2g-atf-g39a62a1-uboot-g255b9cc-20181107-REL.bin

which brings me back to the initial state at the start of this post. Any ideas why flashing the latest u-boot image from armbian seems to completely bricks my board?

Thanks!

My Debian Buster with Armbian Linux 4.19.59-mvebu64 has no /dev/watchdog...

I am a little confused - is there a simple solution to e.g. add the kernel module for the watchdog? I am not into kernel compiling myself unfortunately, so I appreciate any help.

Hi

I want to boot from emmc(all bootloader ,rootfs and kernel are in emmc).

Now I can boot kernel from SD card and emmc (bootloader in spi nor flash.), and it works well.

At present ,I have got the flash-image.bin by  ATF using BOOTDEV=EMMCNORM  option and copy this one to emmc partition 1(mmcblk0p1  179:1    0  7.3G  0 part)

Then i changed the jumper to emmc boot mode and reboot the board ,but uboot can not up .The output just show ">"  "E"

Can anyone tell me how should I do.

Thanks 

Hi everyone,

My name is Gabriel and I am a new person in the community.

After installing ARMBIAN (Armbian_5.91_Clearfogbase_Debian_stretch_default_4.14.135) with the Mini PCI Express Marvel 88SE9215, I got a problem with my Clearfog Pro-A1 revision-2.1. It did not work properly like 88SE9215 did not show me my disks. My Idea is to deploy my NAS server with OMV.

I tried to compile the kernel so many times with different modules like SATA, PATA, and AHCI but it did not work also. I guess that my u-boot is not setup properly because I was reading a couple post about it and it’s working to everyone.

Someone can give me a favor pls and tell me your ideas to try to solve that problem

Thanks.

Logs:

Armbianmonitor:  http://ix.io/201C

root@clearfogbase:~# lspci

00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 0a)

00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 0a)

02:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

root@clearfogbase:~# lspci -nv

00:02.0 0604: 11ab:6828 (rev 0a) (prog-if 00 [Normal decode])

        Flags: fast devsel

        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

        Prefetchable memory behind bridge: 00000000-000fffff

        Capabilities: [40] Express Root Port (Slot+), MSI 00

        Capabilities: [100] Advanced Error Reporting

00:03.0 0604: 11ab:6828 (rev 0a) (prog-if 00 [Normal decode])

        Flags: bus master, fast devsel, latency 0

        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0

        I/O behind bridge: 00010000-00010fff

        Memory behind bridge: e0000000-e00fffff

        Prefetchable memory behind bridge: 00000000-000fffff

        Capabilities: [40] Express Root Port (Slot+), MSI 00

        Capabilities: [100] Advanced Error Reporting

02:00.0 0106: 1b4b:9215 (rev 11) (prog-if 01 [AHCI 1.0])

        Subsystem: 1b4b:9215

        Flags: bus master, fast devsel, latency 0, IRQ 53

        I/O ports at 10020

  I/O ports at 10030

        I/O ports at 10028

        I/O ports at 10034

        I/O ports at 10000

        Memory at e0040000 (32-bit, non-prefetchable)

        Expansion ROM at e0000000

        Capabilities: [40] Power Management version 3

        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-

        Capabilities: [70] Express Legacy Endpoint, MSI 00

        Capabilities: [e0] SATA HBA v0.0

        Capabilities: [100] Advanced Error Reporting

        Kernel driver in use: ahci

Booting from Clearfog 

U-Boot SPL 2018.01-02337-gdc4398fdb8 (May 14 2018 - 19:03:16)

High speed PHY - Version: 2.0

Detected Device ID 6828

board SerDes lanes topology details:

 | Lane #  | Speed |  Type       |

 --------------------------------

 |   0    |  3   |  SATA0       |

 |   1    |  0   |  SGMII1      |

 |   2    |  5   |  PCIe1       |

 |   3    |  5   |  USB3 HOST1  |

 |   4    |  5   |  PCIe2       |

 |   5    |  0   |  SGMII2      |

 --------------------------------

PCIe, Idx 1: detected no link

PCIe, Idx 2: detected no link

High speed PHY - Ended Successfully

DDR3 Training Sequence - Ver TIP-1.29.0

DDR3 Training Sequence - Switching XBAR Window to FastPath Window

DDR3 Training Sequence - Ended Successfully

Trying to boot from SPI

U-Boot 2018.01-02337-gdc4398fdb8 (May 14 2018 - 19:03:16 +0200), Build: jenkins-u-boot-clearfog-model=pro,variant=spi-10

SoC:   MV88F6828-?? (a) at 1600 MHz

DRAM:  1 GiB (800 MHz, 32-bit, ECC not enabled)

MMC:   mv_sdh: 0

SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB

Model: SolidRun Clearfog

Board: SolidRun ClearFog Pro

SCSI:  SATA link 0 timeout.

AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode

Net:   eth1: ethernet@70000, eth2: ethernet@30000, eth3: ethernet@34000

Hit any key to stop autoboot:  0

switch to partitions #0, OK

mmc0(part 0) is current device

** No partition table - mmc 0 **

starting USB...

USB0:   Register 2000120 NbrPorts 2

Starting the controller

USB XHCI 1.00

scanning bus 0 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: device type unknown

... is now current device

** Bad device usb 0 **

** Bad device usb 0 **

scanning bus for devices...

Found 0 device(s).

Hello,

There are many leds on the clearfogpro that I would like to switch off. But 

/sys/class/leds

only has "mmc0::".

Is there a way to access other leds ? namely those of the ethernet ports ?

Regards

deb2016

Hello everybody and a nice evening.

I have two EspressoBin 1GB at home and try desperately to change the static IP.
No matter if in the armbian-config or under /etc/systemd/network/10-br0.network I just can not get it.
Does anyone else have any advice?

I've already tried Google and the forum search but any attempt fails that the IP is constantly jumping or that I no longer get a gateway.

Armbian is a great distro and nobody has gotten the kernel to work so far.

I hope you can help me.

Alone a nice evening :-)

LG StarSurfer

Previously running a different Linux, I followed the instructions to update the boot loader so I could try Armbian on my Espressobin. The update completed ok, but could no longer read from the SD card. After several hours of frustration, I attempted to revert back to the original boot loader and found I could no longer tftp or update from USB.

After several days of frustration, I am near the point of giving up. Here's what happens when I attempt to use the UART rescue found at the Espressobin web site:

Marvell>> usb start
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
Marvell>> bubt bootloader.bin spi usb
Burning U-BOOT image "bootloader.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... 2 USB Device(s) found                             
scanning bus 1 for devices... 1 USB Device(s) found                             
Image checksum...OK!                                                            
SF: unrecognized JEDEC id bytes: c2, 25, 36                                     
Failed to probe SPI Flash                                                       
exit not allowed from main input shell.                                         
Marvell>>

I then tried various newer UART rescue images, which all seem to recognize the SPI flash chip but cannot update from USB (yes, I tried various working USB memory sticks...):

Marvell>> usb start
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
Marvell>> bubt bootloader.bin spi usb
Burning U-BOOT image "bootloader.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... 2 USB Device(s) found                             
scanning bus 1 for devices... 1 USB Device(s) found                             
BUG: failure at drivers/usb/host/xhci-ring.c:489/abort_td()!                    
BUG!                                                                            
resetting ...                                                                   
>

I also tried updating via TFTP. All the UART rescue images I tried give the same result: tftp hangs, like this:

Marvell>> setenv serverip 192.168.1.15
Marvell>> setenv ipaddr 192.168.1.12
Marvell>> ping $serverip
Using neta@30000 device
host 192.168.1.15 is alive
Marvell>> bubt bootloader.bin spi tftp
Burning U-BOOT image "bootloader.bin" from "tftp" to "spi"
Using neta@30000 device
TFTP from server 192.168.1.15; our IP address is 192.168.1.12
Filename 'bootloader.bin'.
Load address: 0x80000000
Loading: #

Has anyone else experienced this problem? I find it hard to believe the board is broken, since it was working fine prior to the first boot loader update.

Hi everybody,

I have an Espressobin v5 in front of me and by default it boots fine from SATA:

Quote

TIM-1.0                                                                                                                           
WTMI-armada-17.10.5-bb8f823                                                                                                       
WTMI: system early-init                                                                                                           
SVC REV: 3, CPU VDD voltage: 1.132V                                                                                               
                                                                                                                                  
Fill memory before self refresh...done                                                                                            
                                                                                                                                  
Now in Self-refresh Mode                                                                                                          
Restore termination values to original values                                                                                     
Exited self-refresh ...                                                                                                           
                                                                                                                                  
                                                                                                                                  
Self refresh Pass.                                                                                                                
DDR self test mode test done!!                                                                                                    
                                                                                                                                  
QS GATING                                                                                                                         
=============                                                                                                                     
Calibration done: cycle = 0x00 tap =0x5B                                                                                          
CH0_PHY_RL_Control_CS0_B0[0xC0001180]: 0x0000005B                                                                                 
CH0_PHY_RL_Control_CS0_B1[0xC0001184]: 0x0000005B                                                                                 
                                                                                                                                  
DLL TUNING                                                                                                                        
==============                                                                                                                    
   DLL 0xc0001050[21:16]: [0,2d,16]                                                                                               
   DLL 0xc0001050[29:24]: [0,2d,16]                                                                                               
   DLL 0xc0001054[21:16]: [0,26,13]                                                                                               
   DLL 0xc0001054[29:24]: [3,2e,18]                                                                                               
   DLL 0xc0001074[21:16]: [0,3f,1f]                                                                                               
   DLL 0xc0001074NOTICE:  Booting Trusted Firmware                                                                                
NOTICE:  BL1: v1.3(release):armada-17.10.3:39a62a1                                                                                
NOTICE:  BL1: Built : 11:19:53, Jun 19 2NOTICE:  BL2: v1.3(release):armada-17.10.3:39a62a1                                        
NOTICE:  BL2: Built : 11:19:54, Jun 19 2018NOTICE:  BL31: v1.3(release):armada-17.10.3:39a62a1                                    
NOTICE:  BL31:                                                                                                                    
                                                                                                                                  
U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 19 2018 - 11:18:51 +0800)                                                             
                                                                                                                                  
Model: Marvell Armada 3720 Community Board ESPRESSOBin                                                                            
       CPU    @ 1000 [MHz]                                                                                                        
       L2     @ 800 [MHz]                                                                                                         
       TClock @ 200 [MHz]                                                                                                         
       DDR    @ 800 [MHz]                                                                                                         
DRAM:  1 GiB                                                                                                                      
U-Boot DT blob at : 000000003f7161b8                                                                                              
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
SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
Net:   eth0: neta@30000 [PRIME]
Hit any key to stop autoboot:  0

Now I need it to load the bootloader (U-Boot) from SD card. However, I can't seem to get it working.

What I have tried so far:

1. Set the jumper on the board (J11,J3,J10) to "eMMC download mode" as well as "eMMC alternate download mode".

2. Get a SD card connected to my Linux host. Empty it with "dd if=/dev/zero of=/dev/sdg bs=1M count=100".

3. Then I tried to get the U-Boot on the SD card, but I am not exactly sure about the proper way. I tried two different things:

3.a. I just copied it raw onto the SD card with "dd if=/home/amue/Downloads/flash-image-ddr3-1g-2cs-1000_800.bin of=/dev/sdg".

3.b. I created an ext4 partition and then copied the U-Boot binary onto the partition.

I have no success with both of those tries. All I see when booting is a minimal console environment:

Quote

E
>?
h/? - print this help screen
r yyyyyyyy - read register/memory at address yyyyyyyy in hex
w yyyyyyyy zzzzzzzz - write zzzzzzzz to address yyyyyyyy in hex
j yyyyyyyy - jump to address yyyyyyyy in hex
x y - change the boot mode, where y is in hex
a - UART control passed to AP CPU ROM
c - UART control passed to CM3 CPU ROM
>
E
>

As I said, I am not sure about the proper way for loading U-Boot from the SD card, since I can't seem to find the correct documentation for it. I would appreciate any help with this, as I am sure that quite a few people have already done this.

Best regards,

Andre

I recently, yesterday, updated u-boot to 800-800.  I did a dist-upgrade to buster.  I've got kernel 4.19.56.  I'm using espressobin as a firewall for my home network, connected to comcast (where I used to have ipv6 addresses).  systemd reports version 241.  This is part status-report, documentation for others, and questions.

Used to have ipv6 addresses - So before the dist-upgrade and kernel upgrade, I was on .20 in Jessie.  And systemd-networkd was giving me prefix delegation such that my home net had public IPv6.  Now, systemd is unable to complete the transaction.  It just repeats this block:  [edit] I had it misconfigured.

Network startup - When the board boots, it seems the wan interface is slow.  The first time systemd-networkd tries to configure the wan interface, it gives an error, saying "Network is down".  This is easy enough to fix, I just log into the box after any boot and send a `ip link set wan up`, and it works from there. 

Again with networkd, the bridge interface seems to try to configure too early.  See below, "could not bring up interface: invalid argument".  This one, however, resolves itself when the lan interface gets set up, as it detects the carrier and goes back to set up the bridge again.  So this one's not so bad.

orkd[299]: No virtualization found in /proc/device-tree/*
orkd[299]: UML virtualization not found in /proc/cpuinfo.
orkd[299]: This platform does not support /proc/sysinfo
orkd[299]: Found VM virtualization none
orkd[299]: lo: Unmanaged
orkd[299]: wan: Could not bring up interface: Network is down
orkd[299]: lan0: Joined netdev
orkd[299]: lan0: Bringing link up
orkd[299]: lan1: Joined netdev
orkd[299]: lan1: Bringing link up
orkd[299]: eth0: Flags change: +UP +LOWER_UP +RUNNING
orkd[299]: LLDP: Started LLDP client
orkd[299]: eth0: Started LLDP.
orkd[299]: eth0: Gained carrier
orkd[299]: eth0: Configured
...
orkd[299]: br0: udev initialized link
orkd[299]: br0: Link state is up-to-date
orkd[299]: br0: found matching network '/etc/systemd/network/10-br0.network'
orkd[299]: br0: Setting address genmode for link
orkd[299]: br0: Bringing link up
orkd[299]: br0: Flags change: +UP
orkd[299]: br0: Could not bring up interface: Invalid argument
orkd[299]: Got inotify event on bus bus-api-network.
orkd[299]: Added inotify watch for /run on bus bus-api-network: 2
orkd[299]: Added inotify watch for /run/dbus on bus bus-api-network: -1
orkd[299]: lan0: Flags change: +LOWER_UP +RUNNING
orkd[299]: lan0: Gained carrier

I found a systemd bug report 12784 that describes similar behavior to what I'm seeing, with Debian sid, kernel 5.2, and systemd 241.  It's very recent, so maybe it's already fixed and just needs to propagate?  

NFTables and network devices - I have an nftable rule that makes use of "iif" (input interface), which supposedly uses the network interface index rather than its name.  Which means, if "wan" doesn't exist when nftables.service gets started, then the ruleset fails.  That's what I'm seeing.  I corrected to "iifname", which does a string compare per packet.  That seems wrong.  Does anyone have a suggestion for how to order nftables rules for after a given interface is created, but before it's brought up?  Maybe a oneshot service that's "after" udev but "before" systemd-networkd?

And while I'm on nftables, my ruleset has a "counter".  But "nft list counters" doesn't show it, nor getting more specific into "nft list counters table inet filter".  When I attempted to name the counter in the ruleset, nft complained about a missing file/directory.  I vaguely guess that there's a module missing, but I don't know how to debug that further, and it's not important enough that I'll spend the time, unless someone else would benefit too.

But my final state, after a manual process each post-reboot, is that I have a capable, functional linux box as my network firewall.  And that's pretty cool.

Hi,

I'm using an esprossobin with Debian Stretch with Armbian Linux 4.19.56-mvebu64.

However regardless inwhat USB-TTL / Serial adapter I connect to he espressobin's USB2.0 port I don't get a ttyUSB0 device

I tried to use a Prolific and a couple of others I got lend from a friend

The postfix V7 suggests that it will eventually succeed the EspressoBin V5 and in a long run, the V5 might disappear. Since I am about to start a business based on the EspressoBin, I would be really interested if there are good experiences regarding the V7 – as I had a very disappointing one, while the V5 seems to run very stable and reliably. By "reliable", I mean suitable for a home server running weeks and months without any bumps or hickups.

I'd also be interested whereelse I could find a community running the EspressoBin in reasonable numbers to investigate there as well.

Thanks in advance and sorry for the off-topic with respect to Armbian.

I am trying to resuscitate an EspressoBin that I purchased back in 2017.  I bought it to make a Linux firewall, but the Ubuntu image apparently wasn't up to networking, and I was too busy to deal with attempting to make a custom Linux build to ensure that networking was enabled.  I am specifically looking for help with the SATA Rescue procedure.

It seems that Armbian has created a Linux image with networking enabled, so I am trying to load the image.  The Armbian instructions said to update the bootloader before attempting to use the new image.  I (tried to) follow the instructions, but I had no success with the load.  Using Kermit on my Linux laptop to watch the board, I see the boot sequence start over and over again, interrupted, it seems, by strings starting with NOTICE:

It could be that my board is irretrievably broken, but I'm trying to use the SATA rescue routine.   I used dd to copy the flash-image-sata.bin file (and also, later, flash-image-sata-2cs-2g.bin from the Armbian site) to a new SATA SSD, according to the online instructions, but the board still shows an interrupted boot sequence.   When I use fdisk to look at the SATA drive, it still looks empty.  I don't know if my failure is due to a bad board or to an incompetent usage of dd.  I expected that copying the image to the SATA drive would create a partition in which the code would be found.  I tried copying the image to a flash drive to see if it made a partition there (in case the SATA drive is bad), but it has the same result there, that is, no partition.  That gives me some confidence in my process, at the expense of some suspicion of the image.

(I would try the UART rescue, but I can't find the WrtDownload_linux program mentioned in the UART rescue instructions.)

So...is there any way to confirm a successful SATA rescue image transfer to the SATA drive, short of a successful booting of the board?  Is there any further advice for rescuing a bricked EspressoBin? 

Thanks,

Chuck Jungmann

I have just updated armbian on my clearfogpro and after the hard drive plugged on the PCIe sata card (2 slots) is no more recognized, it does not appear at all in logs.

It was working like a charm before.  I wonder what happened ?

Here is the output of lspci

00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

I think the PCIe card is recognized (I have also a wifi card on the other PCI slot). I wonder why armbian does no more see the hard drive, this one is powered I can hear it.

It must be due to the u-boot version. Here is the listing of /boot directory : 

-rw-rw-r-- 1 root root     319 Jan 12 17:28 armbianEnv.txt
-rw-rw-r-- 1 root root     319 Jan 12 17:28 armbianEnv.txte
-rw-rw-r-- 1 root root    1624 Jan 27  2018 armbian_first_run.txt.template
-rw-rw-r-- 1 root root   38518 Jan 27  2018 boot.bmp
-rw-rw-r-- 1 root root    1532 Jan 27  2018 boot.cmd
-rw-rw-r-- 1 root root    4882 Jan 27  2018 boot-desktop.png
-rw-rw-r-- 1 root root    1604 Jan 27  2018 boot.scr
-rw-r--r-- 1 root root  123827 Nov 26 08:29 config-4.14.83-mvebu
lrwxrwxrwx 1 root root      17 Jan 12 17:21 dtb -> dtb-4.14.83-mvebu
drwxr-xr-x 2 root root    4096 Jan 12 17:20 dtb-4.14.83-mvebu
lrwxrwxrwx 1 root root      17 Mar 10  2018 dtb.old -> dtb-4.14.18-mvebu
-rw-r--r-- 1 root root 5073125 Jan 12 17:21 initrd.img-4.14.83-mvebu
-rw-r--r-- 1 root root 2179815 Nov 26 08:29 System.map-4.14.83-mvebu
lrwxrwxrwx 1 root root      21 Jan 12 17:21 uInitrd -> uInitrd-4.14.83-mvebu
-rw-r--r-- 1 root root 5073189 Jan 12 17:21 uInitrd-4.14.83-mvebu
-rwxr-xr-x 1 root root 5450232 Nov 26 08:29 vmlinuz-4.14.83-mvebu
lrwxrwxrwx 1 root root      21 Jan 12 17:21 zImage -> vmlinuz-4.14.83-mvebu

In the dtb directory, I see many *dtb files, one is for the clearfogpro, but in the logs I can see : 

[    0.000000] OF: fdt: Machine model: SolidRun Clearfog A1

Should not it say "Clearfogpro" ?

Hostapd config file:

ssid=ARMBIAN
interface=wlx24050fae5224
hw_mode=g
channel=5
bridge=br0
driver=nl80211

logger_syslog=0
logger_syslog_level=0
wmm_enabled=0
wpa=2
preamble=1

wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27
wpa_passphrase=********
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
auth_algs=1
macaddr_acl=0

noscan=1

ctrl_interface=/var/run/hostapd
ctrl_interface_group=0

dnsmasq config file:

interface=wlx24050fae5224
dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,24h

The ip address for my laptop on the network is 192.168.0.24 and for my phone is 192.168.0.11 further proving that dnsmasq is not controlling any ip addresses.

I took a look at the router I got from my internet provider (it has reallllly crappy wifi so that is one of the reasons I am undertaking this project) and my phone and laptop, connected to the espressobin wifi network are show on the network with ip addresses 192.168.0.11 and the phone has an ip address of 100.73.80.157 (???).

I have no idea what is going on; I have used linux desktop for about 5 years now but this is my first time dealing with networking. Any input would be valued.

I am trying to use each Espressobin network port as a independent network interface ( each connected to separate a network). Using systemd.networkd configuration. I have linux systems connected to each port and only one of the ports (lan0) receives anything but broadcast packets. All ports were monitored with tcpdump on both ends. Espressobin board (V5) sends ARP requests on all ports but only hears reply on lan0 . The MAC address for eth0 is different from each interface MAC address. Although replies to other ports are sent with the correct MAC address for that port, the reply seems to be filtered/dropped and not received, However the port does receive broadcast packets. This may be related/similar to:

Network config files:

/etc/systemd/network/10-eth0.network
[Match]
Name=eth0

[Network]
DHCP=no

/etc/systemd/network/20-wan.network
[Match]
Name=wan

[Link]
MACAddress=f0:ad:4e:03:64:82

[Network]
Address=192.168.1.131/24
Gateway=192.168.1.1

/etc/systemd/network/30-lan0.network
[Match]
Name=lan0

[Link]
MACAddress=f0:ad:4e:03:64:80

[Network]
DHCP=no
BindCarrier=eth0
Address=172.17.49.2/24

/etc/systemd/network/40-lan1.network
[Match]
Name=lan1

[Link]
MACAddress=f0:ad:4e:03:64:81

[Network]
DHCP=no
BindCarrier=eth0
Address=10.0.49.70/24
Gateway=10.0.49.1
DNS=10.0.49.1

I get kernel panic from TTL:

espressobin login: [26830.163585] Internal error: synchronous parity or ECC error: 86000018 [#1] PREEMPT SMP
[26830.168894] Modules linked in: zstd zram zsmalloc bridge stp llc sch_fq_codel ip_tables x_tables mv88e6xxx dsa_core
[26830.179650] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.20-mvebu64 #5.75
[26830.186812] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[26830.193445] pstate: 60000085 (nZCv daIf -PAN -UAO)
[26830.198382] pc : need_update+0x0/0xb0
[26830.202138] lr : quiet_vmstat+0x4c/0x60
[26830.206076] sp : ffffff8008f73e80
[26830.209480] x29: ffffff8008f73e80 x28: 0000000007ed0018
[26830.214946] x27: 0000000000000000 x26: ffffff8008f826c0
[26830.220411] x25: 0000000000000000 x24: 000018670e807e00
[26830.225877] x23: 0000000000000000 x22: 0000186738b3b700
[26830.231343] x21: 0000186738b3b700 x20: 0000000000000000
[26830.236809] x19: ffffffc03ffbed08 x18: 0000000000000000
[26830.242273] x17: 0000000000000000 x16: 0000000000000000
[26830.247740] x15: 0000000000000400 x14: 0000000000000400
[26830.253205] x13: 0000000000000000 x12: 0000000000000001
[26830.258671] x11: 0000000000037708 x10: 0000000000000910
[26830.264136] x9 : ffffff8008f73e40 x8 : ffffff8008f83030
[26830.269601] x7 : 0000000000000000 x6 : 0000000000000000
[26830.275067] x5 : 0000004037055000 x4 : ffffff80090336c8
[26830.280532] x3 : 0000000000000000 x2 : 0000000000000001
[26830.285999] x1 : 0000004037055000 x0 : 0000000000000000
[26830.291467] Process swapper/0 (pid: 0, stack limit = 0x000000006512fe99)
[26830.298363] Call trace:
[26830.300876]  need_update+0x0/0xb0
[26830.304283]  tick_nohz_idle_stop_tick+0xb8/0x240
[26830.309029]  do_idle+0x1c4/0x298
[26830.312343]  cpu_startup_entry+0x24/0x28
[26830.316379]  rest_init+0xd0/0xe0
[26830.319694]  start_kernel+0x3ec/0x418
[26830.323456] Code: 910003fd 97ffff11 a8c17bfd d65f03c0 (a9bd7bfd)
[26830.329733] ---[ end trace ea6ec43db8163ab5 ]---
[26830.334475] Kernel panic - not syncing: Attempted to kill the idle task!
[26830.341372] SMP: stopping secondary CPUs
[26830.345409] Kernel Offset: disabled
[26830.348990] CPU features: 0x0,2080200c
[26830.352840] Memory Limit: none
[26830.355981] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---

I used Ubuntu 18.04.1 LTS armbian with 4.19.20-mvebu64 kernel. U-Boot info:

U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Feb 18 2019 - 23:13:53 -0500)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU     1000 [MHz]
       L2      800 [MHz]
       TClock  200 [MHz]
       DDR     800 [MHz]
DRAM:  1 GiB
 

Hi!

I have a Espressobin V7 and would make a router with this tutorial

https://blog.tjll.net/building-my-perfect-router/

Dnsmasq is nativ with ArchLinux ARM

That is dnsmasq.conf of the floder /etc

# Listen for requests on this interface
interface=br0

# Address range to draw from
dhcp-range=192.168.1.5,192.168.1.250,255.255.255.0,24h

# Default route for clients (the address we used in /etc/systemd/network/br0.network)
dhcp-option=option:router,192.168.1.1

 cat /etc/systemd/network/

br0.netdev

[NetDev]
Name=br0
Kind=bridge

br0.network
 

[Match]
Name=br0

[Network]
Address=192.168.1.1/24
IPForward=ipv4
#IPMasquerade=yes not activ while I need 1 Gbit/s between wan and br0
ConfigureWithoutCarrier=yes

eth0.network

[Match]
Name=eth0

lan.network

[Match]
Name=lan*

[Network]
Bridge=br0
BindCarrier=eth0

wan.network

[Match]
Name=wan

[Network]
DHCP=yes
DNSSEC=no
BindCarrier=eth0
IPForward=ipv4

Error when i start dnsmasq with

systemctl start dnsmasq

May 13 00:49:46 alarm systemd-resolved[344]: Using degraded feature set (UDP) f>
May 13 00:49:50 alarm systemd-resolved[344]: Using degraded feature set (UDP) f>
lines 2046-2068/2068 (END)[ 1302.028960] audit: type=1130 audit(1557699855.230:359): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dnsmasq comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1302.048344] audit: type=1131 audit(1557699855.230:360): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dnsmasq comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1302.105771] audit: type=1130 audit(1557699855.310:361): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dnsmasq comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

ifconfig

[root@alarm ~]# ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2a02:120b:c3f6:f671:50ea:a8ff:fe06:b6a  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::50ea:a8ff:fe06:b6a  prefixlen 64  scopeid 0x20<link>
        ether 52:ea:a8:06:0b:6a  txqueuelen 1000  (Ethernet)
        RX packets 722  bytes 408503 (398.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 562  bytes 70734 (69.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1508
        inet6 fe80::f2ad:4eff:fe09:6a7f  prefixlen 64  scopeid 0x20<link>
        ether f0:ad:4e:09:6a:7f  txqueuelen 1024  (Ethernet)
        RX packets 722  bytes 424387 (414.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 582  bytes 76891 (75.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 11  

lan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f0:ad:4e:09:6a:7f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether f0:ad:4e:09:6a:7f  txqueuelen 1000  (Ethernet)
        RX packets 722  bytes 408503 (398.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 562  bytes 70734 (69.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 80  bytes 6320 (6.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 6320 (6.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wan: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f0:ad:4e:09:6a:7f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

What is wrong ?

And have also no Internet

I pluged a FritzBox 5490 with DHCP v6 and v4  to the Wan Port

Shorewall is not running

Trying to get the serial port working on pins 24 and 26 of the espressobin.

I've tried all of the armbian builds, plus building the kernel from the Marvell github repo - various branches.

On the 4.4.52 kernels, the serial port on the header pins shows up with port of 0000 and IRQ of 8, but will not work.

On the 4.14 kernels, I get port 0000 and IRQ 0, and also doesn't work

Has anyone managed to get the serial port working on the header pins 24,26 of the espressobin? I have posted more detail here on the github page but no progress so thought I'd ask here if anyone has had any success with this?

Thanks

https://github.com/MarvellEmbeddedProcessors/mainline-public/issues/81

Seems my espressoBin started randomly rebooting.

sometimes it does it while sitting in a u boot prompt

other times it will do it while bootting the os

Any suggestions? anyone seen this before?

Tried updateing uboot with no luck

Hello folks,

  I am building a small Kubernetes cluster and k8s absolutely *hates* swap, it wants it switched off. I have tried the customary purge of Adam Conrad's zram-config tool, but it looks like on Armbian the setup of zram is coming from deeper down in the system... any help?

  I would normally want zram on, but in this case, because of K8s's quirk, it is making nodes fail cluster init on reboot... it is not helping.

thanks -F

Good evening,

as uboot doesn't get updated automatically since a few versions back, I ran the uboot install script manually today - so far everything worked, uboot got copied to the boot sector.

After rebooting though it seems that uboot is not working / properly compiled. It runs normally until the point where it would boot linux, then stops saying it can't find the various commands (bootz, help, echo etc).

It dropped me to the uboot shell. I tried a few commands (help, reset etc) and all just gave a "command not found" failure.

After restoring the 5.75 uboot from some backup it works again.

Is there some known problem in the current uboot? Otherwise we should probably tell users not to upgrade atm.

I will provide uboot serial output tomorrow, no time today. 

Greetings,

count-doku

every second boot, there is a kernel crash:

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 4.19.20-mvebu64 (root@armbian.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.75 SMP PREEMPT Fri Feb 8 09:54:18 CET 2019
[    0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board
[    0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
[    0.000000] bootconsole [ar3700_uart0] enabled
Loading, please wait...
starting version 232
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.29.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1
/dev/mmcblk1p1: recovering journal
/dev/mmcblk1p1: clean, 37821/942080 files, 494863/3757996 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 9 (stretch)!

[    8.127417] Internal error: Oops: 96000021 [#1] PREEMPT SMP
[    8.130321] Modules linked in: ip_tables x_tables mv88e6xxx dsa_core
[    8.136863] CPU: 0 PID: 219 Comm: systemd Not tainted 4.19.20-mvebu64 #5.75
[    8.144022] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[    8.150655] pstate: a0000005 (NzCv daif -PAN -UAO)
[    8.155591] pc : fput+0x10/0xb8
[    8.158810] lr : vma_do_fput+0x2c/0x38
[    8.162658] sp : ffffff8009b5bac0
[    8.166063] x29: ffffff8009b5bac0 x28: ffffffc03baba580
[    8.171528] x27: ffffffc03bad5e00 x26: 0000000000000000
[    8.176993] x25: ffffffc03b530800 x24: ffffffc03bd686e8
[    8.182459] x23: ffffffc03b530800 x22: ffffffc03ba4ad80
[    8.187925] x21: ffffff8008f79000 x20: ffffffc03bac8539
[    8.193391] x19: ffffffc03bb5fb00 x18: 0000000000000000
[    8.198856] x17: 0000000000000000 x16: 0000000000000000
[    8.204322] x15: 0000000000000200 x14: 00000000000003f8
[    8.209786] x13: 00000000000003f8 x12: 0000000007ff2600
[    8.215253] x11: ffffffc03ffea180 x10: 0000004037055000
[    8.220718] x9 : ffffffc03ffea180 x8 : 0000000044040000
[    8.226184] x7 : 0000000000210d00 x6 : ffffff8008f796c8
[    8.231649] x5 : ffffff80080d50b0 x4 : ffffffc03bd68000
[    8.237116] x3 : ffffffc03bac8571 x2 : 0000000000000000
[    8.242580] x1 : 0000000000000014 x0 : ffffffc03bac8539
[    8.248049] Process systemd (pid: 219, stack limit = 0x(____ptrval____))
[    8.254946] Call trace:
[    8.257458]  fput+0x10/0xb8
[    8.260324]  vma_do_fput+0x2c/0x38
[    8.263821]  remove_vma+0x44/0x68
[    8.267224]  exit_mmap+0x114/0x180
[    8.270721]  mmput+0x5c/0x128
[    8.273767]  flush_old_exec+0x45c/0x6c0
[    8.277709]  load_elf_binary+0x240/0x1264
[    8.281830]  search_binary_handler+0x90/0x290
[    8.286310]  __do_execve_file.isra.14+0x5a0/0x6b0
[    8.291148]  do_execve+0x2c/0x38
[    8.294464]  __arm64_sys_execve+0x28/0x38
[    8.298587]  el0_svc_common+0x60/0x100
[    8.302436]  el0_svc_handler+0x24/0x80
[    8.306289]  el0_svc+0x8/0xc
[    8.309249] Code: a9be7bfd 9100e003 910003fd f9800071 (c85f7c61)
[    8.315519] ---[ end trace bbf74bb1f6385571 ]---
[    8.577617] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[    8.583936] Mem abort info:
[    8.586765]   ESR = 0x96000005
[    8.589911]   Exception class = DABT (current EL), IL = 32 bits
[    8.596016]   SET = 0, FnV = 0
[    8.599100]   EA = 0, S1PTW = 0
[    8.602316] Data abort info:
[    8.605277]   ISV = 0, ISS = 0x00000005
[    8.609216]   CM = 0, WnR = 0
[    8.612259] user pgtable: 4k pages, 39-bit VAs, pgdp = (____ptrval____)
[    8.619077] [0000000000000000] pgd=0000000000000000, pud=0000000000000000
[    8.626065] Internal error: Oops: 96000005 [#2] PREEMPT SMP
[    8.631787] Modules linked in: ip_tables x_tables mv88e6xxx dsa_core
[    8.638334] CPU: 1 PID: 218 Comm: systemd-gpt-aut Tainted: G      D           4.19.20-mvebu64 #5.75
[    8.647645] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[    8.654278] pstate: 60000005 (nZCv daif -PAN -UAO)
[    8.659216] pc : __rb_erase_color+0xd4/0x290
[    8.663600] lr : vma_interval_tree_remove+0x1bc/0x2e8
[    8.668790] sp : ffffff80099ebbe0
[    8.672196] x29: ffffff80099ebbe0 x28: ffffffc03bd6ce00
[    8.677660] x27: 0000000000000000 x26: 0000000000000000
[    8.683126] x25: ffffffc03ba4b160 x24: 0000000000000000
[    8.688591] x23: ffffff80081fb9b0 x22: ffffffc03cd7c278
[    8.694057] x21: ffffffc03bb6e538 x20: 0000000000000000
[    8.699523] x19: ffffffc03b461178 x18: 0000000000000000
[    8.704988] x17: 0000000000000000 x16: 0000000000000000
[    8.710454] x15: 0000000000000000 x14: 0000000000000000
[    8.715919] x13: 0000000000000000 x12: 00000000055a3200
[    8.721386] x11: 00000055a3201000 x10: 0000005592800000
[    8.726851] x9 : 00000000ffffffff x8 : 0000000000000000
[    8.732317] x7 : ffffffc03bb5aa18 x6 : 0000000000100073
[    8.737782] x5 : 0000007f90aa7000 x4 : ffffffc03baf2398
[    8.743248] x3 : 000fffc03749ca97 x2 : ffffff80081fb9b0
[    8.748714] x1 : 0000000000000000 x0 : ffffffc03b461178
[    8.754181] Process systemd-gpt-aut (pid: 218, stack limit = 0x(____ptrval____))
[    8.761795] Call trace:
[    8.764307]  __rb_erase_color+0xd4/0x290
[    8.768338]  vma_interval_tree_remove+0x1bc/0x2e8
[    8.773181]  __remove_shared_vm_struct.isra.1+0x54/0x60
[    8.778554]  unlink_file_vma+0x40/0x60
[    8.782405]  free_pgtables+0xc4/0x118
[    8.786169]  exit_mmap+0xe4/0x180
[    8.789577]  mmput+0x5c/0x128
[    8.792621]  do_exit+0x27c/0x9b8
[    8.795935]  do_group_exit+0x38/0xa0
[    8.799609]  __arm64_sys_exit_group+0x14/0x18
[    8.804092]  el0_svc_common+0x60/0x100
[    8.807942]  el0_svc_handler+0x24/0x80
[    8.811795]  el0_svc+0x8/0xc
[    8.814753] Code: f9400674 eb01029f 54fffb21 f9400a74 (a9405680)
[    8.821025] ---[ end trace bbf74bb1f6385572 ]---
[    8.825832] Fixing recursive fault but reboot is needed!

and console is costantly spammed with this:

Debian GNU/Linux 9 ESPRESSOBIN-SRV-02 ttyMV0

ESPRESSOBIN-SRV-02 login: [   45.636823] BUG: Bad page state in process dbus-daemon  pfn:3b61e
[   45.640320] page:ffffffbf00ed8780 count:4096 mapcount:0 mapping:0000000000000000 index:0x0
[   45.648961] flags: 0x0()
[   45.651432] raw: 0000000000000000 0000000000000000 ffffffbf00ed8788 0000000000000000
[   45.659538] raw: 0000000000000000 0000000000000000 00001000ffffffff 0000000000000000
[   45.667473] page dumped because: nonzero _refcount
[   81.632844] BUG: Bad page state in process khugepaged  pfn:337f0
[   81.636239] page:ffffffbf00cdfc00 count:0 mapcount:0 mapping:0000000000001000 index:0x0
[   81.644462] flags: 0x0()
[   81.647084] raw: 0000000000000000 0000000000000000 ffffffbf00cdfc08 0000000000001000
[   81.655050] raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
[   81.663009] page dumped because: non-NULL mapping
[  132.832811] BUG: Bad page state in process khugepaged  pfn:33a17
[  132.836205] page:ffffffbf00ce85c0 count:4096 mapcount:0 mapping:0000000000000000 index:0x0
[  132.844698] flags: 0x0()
[  132.847319] raw: 0000000000000000 0000000000000000 ffffffbf00ce85c8 0000000000000000
[  132.855284] raw: 0000000000000000 0000000000000000 00001000ffffffff 0000000000000000
[  132.863242] page dumped because: nonzero _count

Hello,

today I tried upgrading my ClearfogPro Kernel from 4.14.106 (next) to 4.19.20(dev). So far everything seems to be working (samba, dnsmasq, minidlna, network etc.), see also attached armbianmonitor link.  Great work @ armbian.

I also noticed that the reported temperature by "cat /sys/devices/virtual/thermal/thermal_zone0/temp" seems to be about 20°C lower than with the old kernel. I appreciate this, because it seems to be closer to the real value (measured with thermal probe at heatsink).  The old 4.14 kernel always reported some value around 65-70°C which seemed a bit high for idling (cpu running at 800Mhz like 80% of the time). The new value of 35°C is quite realistic I guess.

Does anyone know / have information about a change in temperature reading on the clearfog in the last kernel upgrades? 

EDIT:

Checked in the kernel diff between 4.14 and 4.19 and there are some changes to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/thermal/armada_thermal.c?h=linux-4.19.y

They definitely  changed something regarding some trim values - though I don't understand enough to really say if that changes the temperature reading.

But if it did it might also be interesting for the Helios4 guys, I remember seeing some questions about high temperatures in their thread. @gprovost could this be related?

Can I somehow help getting the 4.19 Kernel to be next? Like specific things to test?

Or is your plan to skip 4.19 completely and go directly to 5.x?

Greetings,

count-doku

Hi,

I have this latest ESPRESSObin v7 board. It doe's not boot official Armbian BIONIC. I have used Armbian before on other chips and I am pretty confident I am following the instructions correctly. Steps I did to get it going:

1. I followed official instructions to flash u-boot with bubt tool to it's latest version. My board is DDR4, 1GB,1 ram chip, 1000cpu,800ram. I got the right one - as all works just fine after a reset. Also applied relevant boot environment as instructed here https://www.armbian.com/espressobin/

2. I have then used etcher to burn SD card with bionic. Tried to boot - didn't work. Only getting call traces in kernel log.

3. I burned a flash stick and tried to boot from it over USB3 port - same result. kernel traces.

4. Just tried again with same USB - it all booted as i'm writing. I was greeted with linux login prompt. I thought all good. Then in 10 seconds after, without clicking anything - it failed with kernel error.

Full log attached below. Beginning of it you can see kernel log of a failed boot attempt. Then after I hit reset - you will see that it booted to login prompt as normal - and then shortly after it failed. 

[  971.024128]  kthread+0x128/0x130

[  971.027443]  ret_from_fork+0x10/0x1c

[  971.031115] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[  971.037212] rcu:     0-...!: (29 ticks this GP) idle=c42/1/0x4000000000000002 softirq=76/91 fqs=88 

[  971.046256] rcu:     (detected by 1, t=241577 jiffies, g=-1183, q=53)

[  971.052618] Task dump for CPU 0:

[  971.055933] rcu_preempt     R  running task        0    10      2 0x0000002a

[  971.063190] Call trace:

[  971.065703]  __switch_to+0x94/0xd8

[  971.069197]  schedule_timeout+0x1c4/0x368

[  971.073318]  rcu_gp_kthread+0x48c/0x840

[  971.077260]  kthread+0x128/0x130

[  971.080577]  ret_from_fork+0x10/0x1c

[  971.084252] rcu: rcu_sched kthread starved for 241397 jiffies! g-1183 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1

[  971.094819] rcu: RCU grace-period kthread stack dump:

[  971.100016] rcu_sched       R  running task        0    11      2 0x00000028

[  971.107274] Call trace:

[  971.109786]  __switch_to+0x94/0xd8

[  971.113281]  __schedule+0x1e4/0x618

[  971.116865]  schedule+0x38/0xa0

[  971.120089]  schedule_timeout+0x90/0x368

[  971.124121]  rcu_gp_kthread+0x48c/0x840

[  971.128064]  kthread+0x128/0x130

[  971.131378]  ret_from_fork+0x10/0x1c

[ 1033.956483] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:

[ 1033.959908] rcu:     0-...!: (1 ticks this GP) idle=c42/1/0x4000000000000002 softirq=91/91 fqs=0 

[ 1033.968771] rcu:     (detected by 1, t=257332 jiffies, g=-931, q=10717)

[ 1033.975312] Task dump for CPU 0:

[ 1033.978628] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1033.985884] Call trace:

[ 1033.988397]  __switch_to+0x94/0xd8

[ 1033.991891]  schedule_timeout+0x1c4/0x368

[ 1033.996012]  rcu_gp_kthread+0x48c/0x840

[ 1033.999955]  kthread+0x128/0x130

[ 1034.003270]  ret_from_fork+0x10/0x1c

[ 1034.006946] rcu: rcu_preempt kthread starved for 257332 jiffies! g-931 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0

[ 1034.017603] rcu: RCU grace-period kthread stack dump:

[ 1034.022801] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1034.030058] Call trace:

[ 1034.032569]  __switch_to+0x94/0xd8

[ 1034.036063]  schedule_timeout+0x1c4/0x368

[ 1034.040185]  rcu_gp_kthread+0x48c/0x840

[ 1034.044128]  kthread+0x128/0x130

[ 1034.047442]  ret_from_fork+0x10/0x1c

[ 1034.051114] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[ 1034.057212] rcu:     0-...!: (29 ticks this GP) idle=c42/1/0x4000000000000002 softirq=76/91 fqs=88 

[ 1034.066256] rcu:     (detected by 1, t=257332 jiffies, g=-1183, q=53)

[ 1034.072618] Task dump for CPU 0:

[ 1034.075934] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1034.083190] Call trace:

[ 1034.085703]  __switch_to+0x94/0xd8

[ 1034.089197]  schedule_timeout+0x1c4/0x368

[ 1034.093318]  rcu_gp_kthread+0x48c/0x840

[ 1034.097260]  kthread+0x128/0x130

[ 1034.100576]  ret_from_fork+0x10/0x1c

[ 1034.104252] rcu: rcu_sched kthread starved for 257152 jiffies! g-1183 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1

[ 1034.114819] rcu: RCU grace-period kthread stack dump:

[ 1034.120016] rcu_sched       R  running task        0    11      2 0x00000028

[ 1034.127274] Call trace:

[ 1034.129786]  __switch_to+0x94/0xd8

[ 1034.133280]  __schedule+0x1e4/0x618

[ 1034.136865]  schedule+0x38/0xa0

[ 1034.140089]  schedule_timeout+0x90/0x368

[ 1034.144121]  rcu_gp_kthread+0x48c/0x840

[ 1034.148064]  kthread+0x128/0x130

[ 1034.151379]  ret_from_fork+0x10/0x1c

[ 1096.976483] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:

[ 1096.979908] rcu:     0-...!: (1 ticks this GP) idle=c42/1/0x4000000000000002 softirq=91/91 fqs=0 

[ 1096.988772] rcu:     (detected by 1, t=273087 jiffies, g=-931, q=10717)

[ 1096.995313] Task dump for CPU 0:

[ 1096.998628] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1097.005884] Call trace:

[ 1097.008399]  __switch_to+0x94/0xd8

[ 1097.011892]  schedule_timeout+0x1c4/0x368

[ 1097.016012]  rcu_gp_kthread+0x48c/0x840

[ 1097.019956]  kthread+0x128/0x130

[ 1097.023271]  ret_from_fork+0x10/0x1c

[ 1097.026946] rcu: rcu_preempt kthread starved for 273087 jiffies! g-931 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0

[ 1097.037604] rcu: RCU grace-period kthread stack dump:

[ 1097.042801] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1097.050057] Call trace:

[ 1097.052570]  __switch_to+0x94/0xd8

[ 1097.056064]  schedule_timeout+0x1c4/0x368

[ 1097.060185]  rcu_gp_kthread+0x48c/0x840

[ 1097.064128]  kthread+0x128/0x130

[ 1097.067444]  ret_from_fork+0x10/0x1c

[ 1097.071115] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:

[ 1097.077212] rcu:     0-...!: (29 ticks this GP) idle=c42/1/0x4000000000000002 softirq=76/91 fqs=88 

[ 1097.086256] rcu:     (detected by 1, t=273087 jiffies, g=-1183, q=53)

[ 1097.092618] Task dump for CPU 0:

[ 1097.095934] rcu_preempt     R  running task        0    10      2 0x0000002a

[ 1097.103191] Call trace:

[ 1097.105703]  __switch_to+0x94/0xd8

[ 1097.109197]  schedule_timeout+0x1c4/0x368

[ 1097.113318]  rcu_gp_kthread+0x48c/0x840

[ 1097.117261]  kthread+0x128/0x130

[ 1097.120576]  ret_from_fork+0x10/0x1c

[ 1097.124252] rcu: rcu_sched kthread starved for 272907 jiffies! g-1183 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1

[ 1097.134819] rcu: RCU grace-period kthread stack dump:

[ 1097.140017] rcu_sched       R  running task        0    11      2 0x00000028

[ 1097.147275] Call trace:

[ 1097.149786]  __switch_to+0x94/0xd8

[ 1097.153281]  __schedule+0x1e4/0x618

[ 1097.156865]  schedule+0x38/0xa0

[ 1097.160090]  schedule_timeout+0x90/0x368

[ 1097.164121]  rcu_gp_kthread+0x48c/0x840

[ 1097.168064]  kthread+0x128/0x130

[ 1097.171379]  ret_from_fork+0x10/0x1c

TIM-1.0

WTMI-devel-18.12.0-a0a1cb8

WTMI: system early-init

SVC REV: 4, CPU VDD voltage: 1.120V

NOTICE:  Booting Trusted Firmware

NOTICE:  BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)

NOTICE:  BL1: Built : 13:50:08, Dec 26 2018

NOTICE:  BL1: Booting BL2

NOTICE:  BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)

NOTICE:  BL2: Built : 13:50:09, Dec 26 2018

NOTICE:  BL1: Booting BL31

NOTICE:  BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)

NOTICE:  BL31: Built : 13:5

U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Dec 26 2018 - 13:45:06 +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

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]

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/

1119 bytes read in 25 ms (43 KiB/s)

## Executing script at 06d00000

172 bytes read in 10 ms (16.6 KiB/s)

15897088 bytes read in 101 ms (150.1 MiB/s)

7879752 bytes read in 61 ms (123.2 MiB/s)

** File not found /boot/dtb/marvell/armada-3720-community.dtb **

8942 bytes read in 16 ms (544.9 KiB/s)

## Loading init Ramdisk from Legacy Image at 01100000 ...

   Image Name:   uInitrd

   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)

   Data Size:    7879688 Bytes = 7.5 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 3eea7000, end 3f62ac08 ... OK

   Using Device Tree in place at 0000000006000000, end 00000000060052ed

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

[    0.000000] Linux version 4.19.14-mvebu64 (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.69 SMP PREEMPT T9

[    0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board

[    0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')

[    0.000000] bootconsole [ar3700_uart0] enabled

Loading, please wait...

starting version 237

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.31.1

[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 

/dev/sda1: clean, 34664/67104 files, 229938/268288 blocks

done.

done.

Begin: Running /scripts/local-bottom ... done.

Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 18.04.1 LTS!

[  OK  ] Reached target Remote File Systems.

[  OK  ] Created slice User and Session Slice.

[  OK  ] Started Forward Password Requests to Wall Directory Watch.

[  OK  ] Created slice System Slice.

[  OK  ] Listening on Journal Socket (/dev/log).

[  OK  ] Reached target Slices.

[  OK  ] Created slice system-serial\x2dgetty.slice.

[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.

[  OK  ] Listening on fsck to fsckd communication Socket.

[  OK  ] Listening on Syslog Socket.

[  OK  ] Listening on udev Kernel Socket.

[  OK  ] Listening on udev Control Socket.

[  OK  ] Listening on Journal Audit Socket.

[  OK  ] Reached target Swap.

[  OK  ] Reached target System Time Synchronized.

[  OK  ] Started ntp-systemd-netif.path.

[  OK  ] Started Dispatch Password Requests to Console Directory Watch.

[  OK  ] Reached target Local Encrypted Volumes.

[  OK  ] Listening on Journal Socket.

         Starting Create list of required st?…ce nodes for the current kernel...

         Starting Nameserver information manager...

         Starting Journal Service...

         Starting Remount Root and Kernel File Systems...

         Mounting Huge Pages File System...

         Mounting POSIX Message Queue File System...

         Starting udev Coldplug all Devices...

         Mounting Kernel Debug File System...

         Starting Load Kernel Modules...

         Starting Restore / save the current clock...

         Starting Set the console keyboard layout...

[  OK  ] Started Create list of required sta?…vice nodes for the current kernel.

[  OK  ] Started Journal Service.

[  OK  ] Started Remount Root and Kernel File Systems.

[  OK  ] Mounted Huge Pages File System.

[  OK  ] Mounted POSIX Message Queue File System.

[  OK  ] Mounted Kernel Debug File System.

[  OK  ] Started Load Kernel Modules.

[  OK  ] Started Restore / save the current clock.

[  OK  ] Started Nameserver information manager.

[  OK  ] Reached target Network (Pre).

         Mounting Kernel Configuration File System...

         Starting Apply Kernel Variables...

         Starting Load/Save Random Seed...

         Starting Flush Journal to Persistent Storage...

         Starting Create Static Device Nodes in /dev...

[  OK  ] Mounted Kernel Configuration File System.

[  OK  ] Started Load/Save Random Seed.

[  OK  ] Started Apply Kernel Variables.

[  OK  ] Started Flush Journal to Persistent Storage.

[  OK  ] Started Create Static Device Nodes in /dev.

         Starting udev Kernel Device Manager...

[  OK  ] Started udev Coldplug all Devices.

[  OK  ] Started udev Kernel Device Manager.

[  OK  ] Started Set the console keyboard layout.

[  OK  ] Reached target Local File Systems (Pre).

         Mounting /tmp...

[  OK  ] Mounted /tmp.

[  OK  ] Reached target Local File Systems.

         Starting Create Volatile Files and Directories...

         Starting Raise network interfaces...

         Starting Armbian ZRAM config...

         Starting Set console font and keymap...

[  OK  ] Started Set console font and keymap.

[  OK  ] Started Create Volatile Files and Directories.

         Starting Network Name Resolution...

         Starting Network Time Synchronization...

         Starting Update UTMP about System Boot/Shutdown...

[  OK  ] Started Entropy daemon using the HAVEGE algorithm.

[  OK  ] Started Update UTMP about System Boot/Shutdown.

[  OK  ] Started Network Time Synchronization.

[  OK  ] Started Network Name Resolution.

[  OK  ] Reached target Host and Network Name Lookups.

[  OK  ] Found device /dev/ttyMV0.

[  OK  ] Started Raise network interfaces.

[  OK  ] Started Armbian ZRAM config.

         Starting Armbian memory supported logging...

[  OK  ] Started Armbian memory supported logging.

[  OK  ] Reached target System Initialization.

[  OK  ] Started Daily Cleanup of Temporary Directories.

         Starting Armbian hardware monitoring...

[  OK  ] Started Daily apt download activities.

[  OK  ] Started resolvconf-pull-resolved.path.

[  OK  ] Reached target Paths.

[  OK  ] Started Daily apt upgrade and clean activities.

[  OK  ] Started Discard unused blocks once a week.

[  OK  ] Started Message of the Day.

[  OK  ] Reached target Timers.

[  OK  ] Listening on D-Bus System Message Bus Socket.

[  OK  ] Reached target Sockets.

         Starting Armbian filesystem resize...

         Starting Armbian hardware optimization...

[  OK  ] Started Armbian hardware monitoring.

[  OK  ] Started Armbian hardware optimization.

[  OK  ] Started Armbian filesystem resize.

[  OK  ] Reached target Basic System.

         Starting Resets System Activity Data Collector...

         Starting resolvconf-pull-resolved.service...

         Starting Dispatcher daemon for systemd-networkd...

         Starting System Logging Service...

         Starting LSB: Load kernel modules needed to enable cpufreq scaling...

         Starting Login Service...

[  OK  ] Started ntp-systemd-netif.service.

[  OK  ] Started D-Bus System Message Bus.

[  OK  ] Started Login Service.

         Starting WPA supplicant...

         Starting Network Manager...

[  OK  ] Started Regular background program processing daemon.

[  OK  ] Started Armbian first run tasks.

[  OK  ] Started System Logging Service.

[  OK  ] Started Resets System Activity Data Collector.

[  OK  ] Started resolvconf-pull-resolved.service.

[  OK  ] Started WPA supplicant.

[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.

         Starting LSB: set CPUFreq kernel parameters...

         Starting Hostname Service...

[  OK  ] Started LSB: set CPUFreq kernel parameters.

         Starting LSB: Set sysfs variables from /etc/sysfs.conf...

[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.

[  OK  ] Started Hostname Service.

[  OK  ] Started Network Manager.

         Starting Network Manager Wait Online...

[  OK  ] Reached target Network.

         Starting OpenBSD Secure Shell server...

[  OK  ] Started Unattended Upgrades Shutdown.

         Starting Permit User Sessions...

[  OK  ] Started Permit User Sessions.

         Starting Network Manager Script Dispatcher Service...

         Starting Set console scheme...

[  OK  ] Started Set console scheme.

[  OK  ] Created slice system-getty.slice.

[  OK  ] Started Network Manager Script Dispatcher Service.

[  OK  ] Started OpenBSD Secure Shell server.

         Starting Authorization Manager...

[  OK  ] Started Network Manager Wait Online.

[  OK  ] Reached target Network is Online.

         Starting /etc/rc.local Compatibility...

         Starting LSB: Advanced IEEE 802.11 management daemon...

[  OK  ] Started Authorization Manager.

[  OK  ] Started /etc/rc.local Compatibility.

[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.

[  OK  ] Started Getty on tty1.

[  OK  ] Started Serial Getty on ttyMV0.

[  OK  ] Reached target Login Prompts.

[  OK  ] Started Dispatcher daemon for systemd-networkd.

[  OK  ] Reached target Multi-User System.

[  OK  ] Reached target Graphical Interface.

         Starting Update UTMP about System Runlevel Changes...

[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 18.04.1 LTS espressobin ttyMV0

espressobin login: [   47.082691] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000100

[   47.089045] Mem abort info:

[   47.091855]   ESR = 0x96000005

[   47.094981]   Exception class = DABT (current EL), IL = 32 bits

[   47.101079]   SET = 0, FnV = 0

[   47.104215]   EA = 0, S1PTW = 0

[   47.107435] Data abort info:

[   47.110394]   ISV = 0, ISS = 0x00000005

[   47.114364]   CM = 0, WnR = 0

[   47.117406] user pgtable: 4k pages, 39-bit VAs, pgdp = 00000000a7778165

[   47.124205] [0000000000000100] pgd=0000000000000000, pud=0000000000000000

[   47.131198] Internal error: Oops: 96000005 [#1] PREEMPT SMP

[   47.136875] Modules linked in: bridge stp llc zstd zram zsmalloc sch_fq_codel ip_tables x_tables mv88e6xxx uas dsa_core

[   47.148000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.14-mvebu64 #5.69

[   47.155148] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)

[   47.161786] pstate: 40000005 (nZcv daif -PAN -UAO)

[   47.166746] pc : ipv6_chk_mcast_addr+0x6c/0x140

[   47.171378] lr : ipv6_chk_mcast_addr+0x54/0x140

[   47.176021] sp : ffffff8008003740

[   47.179429] x29: ffffff8008003740 x28: ffffff8008003b48 

[   47.184893] x27: 0000000000000000 x26: ffffffc03b013828 

[   47.190358] x25: 0000000000000001 x24: ffffffc03228faca 

[   47.195825] x23: ffffffc03b89dcd0 x22: ffffffc03228faf0 

[   47.201288] x21: 0000000000000000 x20: 0000000000000000 

[   47.206756] x19: 0000000000000100 x18: 0000000000000000 

[   47.212220] x17: 0000000000000000 x16: 0000000000000000 

[   47.217687] x15: 0000000000000100 x14: 0000000000000400 

[   47.223153] x13: 000000000000000a x12: 0000000000000000 

[   47.228617] x11: 0000000000000000 x10: ffffff8008ef96c8 

[   47.234083] x9 : 0000000000000000 x8 : ffffffc03b108e40 

[   47.239548] x7 : 0000000000000001 x6 : 0000000000000001 

[   47.245014] x5 : 00000040370d6000 x4 : 0000000000000064 

[   47.250479] x3 : 00000000000002ff x2 : 0200010000000000 

[   47.255945] x1 : 0300010000000000 x0 : 0300010000000300 

[   47.261420] Process swapper/0 (pid: 0, stack limit = 0x000000002308e799)

[   47.268310] Call trace:

[   47.270839]  ipv6_chk_mcast_addr+0x6c/0x140

[   47.275138]  ip6_mc_input+0xd0/0x238

[   47.278808]  ip6_rcv_finish+0x4c/0x80

[   47.282571]  ipv6_rcv+0x64/0xf8

[   47.285800]  __netif_receive_skb_one_core+0x54/0x80

[   47.290810]  __netif_receive_skb+0x14/0x60

[   47.295022]  netif_receive_skb_internal+0x54/0x150

[   47.299950]  netif_receive_skb+0xc/0x18

[   47.304009]  br_netif_receive_skb+0x2c/0x48 [bridge]

[   47.309094]  br_pass_frame_up+0x9c/0x130 [bridge]

[   47.313930]  br_handle_frame_finish+0x2d8/0x400 [bridge]

[   47.319396]  br_handle_frame+0x158/0x328 [bridge]

[   47.324146]  __netif_receive_skb_core+0x218/0xac0

[   47.328981]  __netif_receive_skb_one_core+0x38/0x80

[   47.333998]  __netif_receive_skb+0x14/0x60

[   47.338210]  netif_receive_skb_internal+0x54/0x150

[   47.343137]  netif_receive_skb+0xc/0x18

[   47.347130]  dsa_switch_rcv+0xac/0x1e0 [dsa_core]

[   47.351918]  __netif_receive_skb_one_core+0x54/0x80

[   47.356935]  __netif_receive_skb+0x14/0x60

[   47.361148]  netif_receive_skb_internal+0x54/0x150

[   47.366074]  napi_gro_receive+0xa4/0xc8

[   47.370028]  mvneta_poll+0x758/0xc30

[   47.373690]  net_rx_action+0x10c/0x2d0

[   47.377547]  __do_softirq+0x10c/0x200

[   47.381310]  irq_exit+0xac/0xc0

[   47.384538]  __handle_domain_irq+0x60/0xb0

[   47.388741]  gic_handle_irq+0x7c/0x180

[   47.392593]  el1_irq+0xb0/0x128

[   47.395824]  arch_cpu_idle+0x10/0x18

[   47.399494]  do_idle+0x1d4/0x298

[   47.402810]  cpu_startup_entry+0x24/0x28

[   47.406851]  rest_init+0xd0/0xe0

[   47.410164]  start_kernel+0x3ec/0x418

[   47.413932] Code: a9400ac3 14000003 f9400e73 b4000593 (a9400660) 

[   47.420209] ---[ end trace e9c57f1bcaeb7111 ]---

[   47.424938] Kernel panic - not syncing: Fatal exception in interrupt

[   47.431475] SMP: stopping secondary CPUs

[   47.435511] Kernel Offset: disabled

[   47.439093] CPU features: 0x0,2080200c

[   47.442939] Memory Limit: none

[   47.446094] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---

Hi everyone, brace yourselves this a breakdown of the efforts I have made so far to turn the espressobin into a usb device.

The armada3720 soc on the espressobin contains a usb 3 and a usb 2 device controller. I have been trying to enable them in order to turn the espressobin into a usb network adapter of sorts or a usb mass storage device.

This may indeed be an impossibility, and I would love to hear any arguments as to why it is impossible.

Thus far here are the main issues as I understand them so far:

1. The espressobin does not have a usb type b port,  which is generally viewed as requirement for a usb device. However since there are other pieces of hardware that use the type A female interface in device mode maybe this is possible with the espressobin too.  The rockpi 4 has a Type A interface that can be put in device mode using a switch for example. Maybe the espressobin can turn put the port into device mode using software instead of a hardware switch.

2. Though the 4.4.x kernels have some sort of support for the usb3 device controller on the espressobin, neither mainline nor the marvell 4.14 kernel do. Which may indicate that the feature does not actually work or will not be supported longer term.

3. I can't get it work:

 Test methodology so far:

a) Compile u-boot version 2018.03-armada-18.12 to put comphy lane0 in to device mode in dts file - see patch 0001 below

b) Compile Marvell 4.4.52 kernel with host controller disabled and device controllers enabled, lane 0 comphy configured in various modes: COMPHY_USB3, and a few others, though I don't actually know what they are in any human decipherable form ... patch 0005)

                            - To be more specific according to include/dt-bindings/phy-comphy-mvebu.h a device mode is defined which one would think would work for the usb device controller: 

line 73

#define COMPHY_USB3D0           COMPHY_DEF(COMPHY_USB3D_MODE,  COMPHY_UNIT_ID0, \
                                        COMPHY_SPEED_DEFAULT, COMPHY_POLARITY_NO_INVERT)

                              - However if I set the mode of the comphy to COMPHY_USB3D0 in the armada-3720-community.dts file in the 4.4.52 kernel, the kernel boots and says that it is the "Wrong mode for the phy"

                            - Once this happened I was only able to determine the hex values for compatible modes by inserting some debug codes into the drivers/usb/gadget/udc/mvebu_u3d.c driver code and recompiling. 

                            - The hex values for the comphy modes I have been testing are summarised in patch 0002 below

                            - So here is where I am now, I am configuring the u3d device to use comphy mode that is in a valid mode, but may or may not be in a vdevice mode and attempting to test the kernel as a usb device. The good news is that the controllers are visible by the kernel. /sys/class/udc becomes populated with two device controllers one for the usb3 and one for usb2 d0050000.u3d and  d0054100.udc respectively.

                            - To configure them I use the ag (short for add gadget) script attached this script works fine on other machines.

                            - RESULT: 

                                               i) On linux machines as the host end absolutely no sign that there is a usb device connected when either using a usb-A male  to type-C cable or a USB-A male to USB-A male cable 

                                               ii) On windows machines as the host end I get "Usb device malfunctioned because it did not respond to a port reset" or something along those lines

                                               iii) On the espressobin as a device, I see "USB Device: disconnected" after the gadget seems to be initialized to some degree, but is saying it is disconnected because there is no signal on the vbus or something.

                                                      a) When I change the checkvbus function to fake the vbus being connected, I can see that the controller is trying to pullup some dp or dn lines on the usb controller and I am able to see a "USB Device: connected" line being printed but still there is absolutely no indication that there is a device connected on a linux machine as the usb host as in RESULT(i)

Summary:

The main suspects 

1) Neither udc or u3d are connected physically to the usb hosts ports at all, neither the usb2 or the usb3 type a female ports, thus no amount of reconfiguration will casue them to allow the espressobin to act as a device.

2) the lane 0 settings are not set correctly, I have not been assigning the COMPHY  the appropriate hex value as outlined in patch 0002, they may even need to be connected in host modes instead of device modes since the espressobin does not actually have a Type B port on the outside only two USB Type A and micro usb a/b.

3) I have somehow misconfigured the utmi (like the lane 0 comphy, utmi32 can be configured to used in a device mode see patch 0004 and then referenced by the usb2 device controller see patch 0005.

INCIDENTALLY:

The armada-3720 also supports a usb OTG mode whereby the usb3 xhci device, u3d and udc devices are enabled simultaneously in the armada-3720-community.dts file and a usb-phy is also created and enabled as described in the 4.4.52 documentation file: Documentation/devicetree/bindings/usb/armada3700-usb-phy.txt , I have tried this technique by enabling the OTG option in the kernel and then following the directions in a3700-usb-phy.txt, but did not really get anywhere, with similar results of nothing being detected by a linux usb host machine. 

Patch 0001

--- a/arch/arm/dts/armada-3720-espressobin.dts
+++ b/arch/arm/dts/armada-3720-espressobin.dts
@@ -60,7 +60,7 @@
 &comphy {
        max-lanes = <3>;
        phy0 {
-               phy-type = <COMPHY_TYPE_USB3>;
+               phy-type = <COMPHY_TYPE_USB3_DEVICE>;
                phy-speed = <COMPHY_SPEED_5G>;
        };
 

Patch 0002

diff --git a/arch/arm64/boot/dts/marvell/armada-3720-community.dts b/arch/arm64/boot/dts/marvell/armada-3720-community.dts
index 844e46bcfc95..82a241528a86 100644
--- a/arch/arm64/boot/dts/marvell/armada-3720-community.dts
+++ b/arch/arm64/boot/dts/marvell/armada-3720-community.dts
@@ -114,7 +114,13 @@
 
                        u3d@50000 {
                                status = "okay";
-                               phys =  <&a3700_comphy 0 COMPHY_USB3>; 
+                               /* NUM1 phys =  <&a3700_comphy 0 0x21fc>; */
+                               /* NUM2 phys =  <&a3700_comphy 0 0x31fc>; */
+                               phys = <&a3700_comphy 0 0xa0fc>; /* NUM3 */
+                               /* Either NUM1,NUM2,NUM3 corresponds to mode COMPHY_USB3 because
+                               these are the only three modes and I have tested, are available for the lane according to mvebu_u3d.c, and
+                               setting phys = <&a3700_comphy 0 COMPHY_USB3>  works without causing the kernel to complain.
+                               */
                                phy-names = "usb";
                        };

Patch 0003

diff --git a/arch/arm64/boot/dts/marvell/armada-37xx.dtsi b/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
index e6f170ae2b39..cb8784456978 100644
--- a/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
+++ b/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
@@ -375,7 +375,7 @@
                        utmi_usb32: utmi@5d000 {
                                compatible = "marvell,armada-3700-utmi-phy";
                                reg = <0x5d000 0x1000>;
-                               utmi-port = <UTMI_PHY_TO_USB3_HOST0>;
+                               utmi-port = <UTMI_PHY_TO_USB3_DEVICE0>;
                                #phy-cells = <0>;
                                status = "disabled";
                        };

Patch 0005

--- a/arch/arm64/boot/dts/marvell/armada-3720-community.dts
+++ b/arch/arm64/boot/dts/marvell/armada-3720-community.dts
@@ -113,20 +113,26 @@
                        };
 
                        u3d@50000 {
-                               status = "disabled";
-                               phys = <&a3700_comphy 0 COMPHY_USB3>;
+                               status = "okay";
+                               /* NUM1 phys =  <&a3700_comphy 0 0x21fc>; */
+                               /* NUM2 phys =  <&a3700_comphy 0 0x31fc>; */
+                               phys = <&a3700_comphy 0 0xa0fc>; /* NUM3 */
+                               /* Either NUM1,NUM2,NUM3 corresponds to mode COMPHY_USB3 because
+                               these are the only three modes and I have tested
+                               phys = <&a3700_comphy 0 COMPHY_USB3> and the kernel does not complain
+                               */
                                phy-names = "usb";
                        };
 
                        udc@54100 {
-                               status = "disabled";
+                               status = "okay";
                                phys = <&utmi_usb32>;
                                phy-names = "usb";
                        };
 
                        usb3@58000 {
                                compatible = "generic-xhci";
-                               status = "okay";
+                               status = "disabled";
                                phys = <&utmi_usb32>, /* utmi usb32 dedicated phy */
                                       <&a3700_comphy 0 COMPHY_USB3>; /* usb3 comphy */
                                phy-names = "usb2", "usb3";

ag

New revelation... the v7 of espressobin has flipped the ethernet port order.

On v5 they were (left to right) lan1 lan0 wan

On v7 they are (left to right) wan lan0 lan1

When I load armbian with latest u-boot (I believe v7 are the only boards with ddr4...) the ports are in v5 order.

The v7 ports have the intended wan port separated from lan0 lan1, so they really need to be re-assigned.

Is there a way to fix this without rebuilding u-boot?

I've installed the latest u-boot for the boards I'm working with (I have a v5 and a v7) and while I have been able to figure out how to set the MAC in linux, I would like to set the WAN MAC at the uboot level if possible.

The u-boot environment variables seem to have no affect. I've flashed two boards and they both come up with the same MAC in Armbian f0:ad:4e:03:64:7f

Can this somehow be altered before flashing the new u-boot?

The u-boot I used is flash-image-1g-2cs-800_800.bin. It can boot linux from usb and in linux, it can detect my emmc.

root@espressobin:~# dmesg|grep -i mmc
[    4.266090] mmc0: SDHCI controller on d00d8000.sdhci [d00d8000.sdhci] using ADMA
[    4.308521] mmc0: new DDR MMC card at address 0001
[    4.309517] mmcblk0: mmc0:0001 SEM04G 3.69 GiB
[    4.310228] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
[    4.310928] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
[    4.311176] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB, chardev (243:0)
[    4.311340] mmc1: SDHCI controller on d00d0000.sdhci [d00d0000.sdhci] using ADMA
[    4.316565]  mmcblk0: p1

But u-boot can't detect emmc and boot from it:

U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Dec 26 2018 - 13:45:06 +0100)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU     800 [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
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
Marvell>> mmc list
sdhci@d0000: 0
Marvell>> mmc dev 0
Card did not respond to voltage select!
Marvell>> mmc dev 1
MMC Device 1 not found
no mmc device at slot 1

Looks mmc dev0 is sd card and dev1 is emmc. This is different with boot script.

Hi everyone, 

especially armbian maintainers!

I'd like to make use of great performance of this board regarding SATA performance which is crippled by 1Gbps so my question is, would etherchannel work on this hardware? I understand that the board has only 1Gbps from the switch (dual LAN ports) so I guess the only possible way to exceed 1Gbps output would be to bundle WAN && [LAN01|LAN02]. Anyone tried this or believe it should work? I don't have the board to try.

Thanks.

Hello all. New ESPRESSObin owner here, so please forgive any obvious oversights I may have missed. I'm still getting familiar with it.

I'm following the instructions on the Download page. I have a new 32GB Samsung SD card with an Armbian (mainline kernel 4.19.y) flashed onto it using Etcher for Windows. I flashed a new version of u-boot, specifically "flash-image-ddr4-1g-1cs-1000_800.bin", and that seemed to work without a hitch. I defined the environment variables as directed. When booting, it seems to go through my devices and I would guess that it can't find the image based on the "bad device, wrong image format" messages but I'm not 100% sure.

I read that some folks suggest disconnecting your PC from power when using the console so I tried that. I tried reflashing the SD card and u-boot and those processes seem to be successful. I also tried using a 4GB USB flash drive with the same Armbian image flashed to it and the same message appears. I've been trying this for a few hours now- starting fresh, reflashing, rebooting, reading threads/guides, etc...

Can anyone point me in the right direction of how to overcome this? What am I doing wrong here? Any tips would be greatly appreciated.

Also, I see a reference to "REV 5" near the top of my log. Do I have a v5 board? I bought it from Amazon and it specifically said "v7" in the title and this board has the newer 15-pin SATA connector, and I believe that's an indicator of v7.

Full console log:

Marvell>> TIM-1.0
WTMI-devel-18.12.0-a0a1cb8
WTMI: system early-init
SVC REV: 5, CPU VDD voltage: 1.143V
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE:  BL1: Built : 09:50:21, Feb 20 2019
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE:  BL2: Built : 09:50:23, Feb 20 2019
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE:  BL31: Built : 09:5

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 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]
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 006d0000
Wrong image format for "source" command
/boot/
** Bad device usb 0 **
## Executing script at 006d0000
Wrong image format for "source" command
scanning bus for devices...

Device 0: unknown device
/
** Bad device scsi 0 **
## Executing script at 006d0000
Wrong image format for "source" command
/boot/
** Bad device scsi 0 **
## Executing script at 006d0000
Wrong image format for "source" command
/
Card did not respond to voltage select!
** Bad device mmc 1 **
## Executing script at 006d0000
Wrong image format for "source" command
/boot/
Card did not respond to voltage select!
** Bad device mmc 1 **
## Executing script at 006d0000
Wrong image format for "source" command
/
** File not found /boot.scr **
## Executing script at 006d0000
Wrong image format for "source" command
/boot/
1119 bytes read in 14 ms (77.1 KiB/s)
## Executing script at 006d0000
172 bytes read in 5 ms (33.2 KiB/s)
16421376 bytes read in 703 ms (22.3 MiB/s)
ext4load - load binary file from a Ext4 filesystem

Usage:
ext4load <interface> [<dev[:part]> [addr [filename [bytes [pos]]]]]
    - load binary file 'filename' from 'dev' on 'interface'
      to address 'addr' from ext4 filesystem
** File not found /boot/dtb/marvell/armada-3720-community.dtb **
8942 bytes read in 8 ms (1.1 MiB/s)
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
Marvell>>

I have worked through the installation of Armbian Ubuntu 18.04 to the embedded MMC in an ESPRESSObin v7.   It took a while and there were some quirks along the way, so here is a procedure with observations that may be useful to others.

1. The Armbian u-boot does not appear to recognise the eMMC.  I used Globalscale's u-boot espressobin-bootloader-cpu-1000-ddr4-1cs-1g
2. I created a USB stick using the standard procedure and booted the ESPRESSObin from this.
3. I copied the Armbian .img file to the ESPRESSObin USB system and used this to flash the eMMC

   sudo dd if= Armbian_5.69_Espressobin_Debian_stretch_next_4.19.14 of=/dev/mmcblk0 bs=128K status=progress

    

4. I could then mount the Linux partition on the eMMC.

   sudo mkdir /mnt/emmc
   sudo mount /dev/mmcblk0p1 /mnt/emmc

    

5. Note that the eMMC u-boot device number is "1"  (not the hard-coded 0 in the boot.scr) so I edited /mnt/emmc/boot/boot.cmd to use $devnum instead:

   ...
   # use $devnum in place of hard-coded 0
   
   ext4load $boot_interface $devnum:1  $kernel_addr ${prefix}$image_name      
   ext4load $boot_interface $devnum:1  $initrd_addr ${prefix}$initrd_image
   ext4load $boot_interface $devnum:1  $fdt_addr ${prefix}$fdt_name_a
   ext4load $boot_interface $devnum:1  $fdt_addr ${prefix}$fdt_name_b

    

6. I generated the boot.scr u-boot file:

   sudo mkimage -C none -A arm -T script -d /mnt/emmc/boot/boot.cmd /mnt/emmc/boot/boot.scr

7. I rebooted with the USB stick removed. The system booted from the eMMC, however there were some issues with the Ubuntu system...

8. The Linux startup waited for two minutes for systemd-networkd-wait-online.service. This appears to be a common issue with multiple Ethernet ports. I disabled the systemd-networkd-wait-online.service
    

   sudo systemctl disable systemd-networkd-wait-online.service

      

9. The Ubuntu system would not use the DHCP provided DNS server. I modifed /etc/systemd/resolved.conf to remove the default DNS server (1.0.0.1)

10. The naming of the Ethernet ports in Armbian is different to Globalscale's
     

    Front view

     

    USB2.0 lan1 lan0 wan USB3.0 (Armbian)

    USB2.0 wan lan0 lan1 USB3.0 (Globalscale)

11. I set my system with three nn-bridged Ethernet ports
     

    ls  /etc/systemd/network/
    10-br0.netdev.disbled  10-br0.network.disabled  10-eth0.network  10-lan0.network  10-lan1.network  10-wan.network
    
    cat /etc/systemd/network/*
    [NetDev]
    Name=br0
    Kind=bridge
    [Match]
    Name=br0
    [Network]
    #DHCP=ipv4
    #BindCarrier=eth0
    [Match]
    Name=eth0
    [Network]
    [Match]
    Name=lan0
    [Network]
    #Bridge=br0
    DHCP=ipv4
    BindCarrier=eth0
    [Match]
    Name=lan1
    [Network]
    #Bridge=br0
    DHCP=ipv4
    BindCarrier=eth0
    [Match]
    Name=wan 
    [Network]
    #Bridge=br0
    DHCP=ipv4
    BindCarrier=eth0

     

12. I could not find a way to specify the MAC addresses for the Ethernet ports so I installed macchanger and go it to assign random MACs at startup.  See https://wiki.archlinux.org/index.php/MAC_address_spoofing for setup.

I just got my EspressoBin V7 and installed the current armbian for it. I haven't tested much, but Globalscale has changed the numbering of the ethernet ports, as can been seen in the Wiki of the EspressoBin.

What do I have to do to rename the ports permanently, so that no update can change it back?

Or is this something that needs to be changed in armbian for the V7 boards?

Is the ESPRESSObin version 7 supported by Armbian?

Hi, I have not been able to find clear instructions explaning how to compile u-boot so it detects the installed msata disk.

What I think I have to do is rebuild u-boot using the armbian build tools and patch uboot by moving and renaming file below

~/armbian/patch/u-boot/u-boot-mvebu/slot0=sata_1=sata.patch.disabled

to the folder

~/armbian/userpatches/u-boot/u-boot-mvebu/board_clearfogpro/slot0=sata_1=sata.patch

After builds completes I get a linux-u-boot-clearfogpro_5.74_armhf.deb which I installed and nothing happened the msata disk still not detected.

Is that how am I supposted to go about to enable msata support?

ARMBIAN 5.60 stable Debian GNU/Linux 9 (stretch) 4.4.153-mvebu

root@armada:~# dpkg -L linux-u-boot-clearfogpro-default
/.
/usr
/usr/lib
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot-uart.flash
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot-uart.mmc
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot-uart.sata
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot.flash
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot.mmc
/usr/lib/linux-u-boot-clearfogpro_5.74_armhf/u-boot.sata
/usr/lib/u-boot
/usr/lib/u-boot/LICENSE
/usr/lib/u-boot/platform_install.sh

does anyone know if the provided UART interface on the mikrobus header on the clearfog is 5V tolerant?

Greetings,

count-doku

root@tottenham:~# cat /etc/nftables.conf 

flush ruleset

table inet filter {
	chain input { type filter hook input priority 0; policy accept;	}
	chain forward {
		type filter hook forward priority 0; policy accept;
	}
	chain output {
		type filter hook output priority 0; policy accept;
	}
}
root@tottenham:~# nft -f /etc/nftables.conf 
/etc/nftables.conf:5:15-19: Error: Could not process rule: No such file or directory
	chain input { type filter hook input priority 0; policy accept;	}
	             ^^^^^
/etc/nftables.conf:6:15-21: Error: Could not process rule: No such file or directory
	chain forward {
	             ^^^^^^^
/etc/nftables.conf:9:15-20: Error: Could not process rule: No such file or directory
	chain output {
	             ^^^^^^
root@tottenham:~# cat /proc/version
Linux version 4.19.12-mvebu64 (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.68 SMP PREEMPT Fri Dec 28 20:24:51 CET 2018

Does anyone have any idea why it seems to think "type filter hook input priority 0;" is not OK?

if I create just *empty* chains it does work:

root@tottenham:~# nft create table inet filter
root@tottenham:~# nft create chain inet filter input
root@tottenham:~# nft list ruleset
table inet filter {
	chain input {
	}
}

using: U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian (Sep 05 2018 - 21:49:34 +0200)

i get: SF: unrecognized JEDEC id bytes: 9d, 70, 16. from the chip lookup (U10):

IS25WP032 - UNSUPPORTED by armbian as of 2018-11-29

so i will try to gather already seen spi chips and their status with corresponding armbian uboots/kernels. since i'm new in the espressobin land, i ask other owners to post their chips and status.

The only problem I'm having is that the bcache tools doesn't seem to be providing a kernel module -- at least, none is present anywhere I can find, particularly in the initramfs. 

Any suggestions?

https://github.com/MarvellEmbeddedProcessors/A3700-utils-marvell/commits/A3700_utils-armada-18.12

https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell/commits/mv_ddr-armada-18.12

https://github.com/MarvellEmbeddedProcessors/atf-marvell/commits/atf-v1.5-armada-18.12

https://github.com/MarvellEmbeddedProcessors/uefi-marvell/commits/uefi-2.7-armada-18.12

https://github.com/MarvellEmbeddedProcessors/linux-marvell/commits/linux-4.14.76-armada-18.12

This release is based on ATF v1.5, but is also compatible with mainline ATF v2.0 sources. The the flash image could be build with both mainline and LSP ATF sources

Marvell>> bubt flash-image-1g-1cs-1000_800.bin spi usb
Burning U-BOOT image "flash-image-1g-1cs-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
reading flash-image-1g-1cs-1000_800.bin
Image checksum...OK!
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
262144 bytes written, 593344 bytes skipped in 2.65s, speed 424017 B/s
Done!
Marvell>> TIM-1.0
TIM-1.0
TIM-1.0
WTMI-armada-17.10.5-bb8f823
WTMI: system early-init
SVC REV: 4, CPU VDD voltage: 1.120V

Fill memory before self refresh...done

Now in Self-refresh Mode
Exited self-refresh ...


Self refresh Pass.
DDR self test mode test done!!
Vref read training
===================
Final vdac_value 0x00000020

Vref write training
===================
Final vref_value 0x0000001F

DLL TUNING
==============
   DLL 0xc0001050[21:16]: [8,35,1e]
   DLL 0xc0001050[29:24]: [8,2b,19]
   DLL 0xc0001054[21:16]: [b,31,1e]
   DLL 0xc0001054[29:24]: [e,30,1f]
   DLL 0xc0001074[21:16]: [0,3f,1f]
   DLL 0xc0001074NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL1: Built : 15:40:57, Jun  1 2NOTICE:  BL2: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL2: Built : 15:40:59, Jun  1 201NOTICE:  BL31: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL31:

U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  1 GiB
U-Boot DT blob at : 000000003f7161b8
Comphy-0: USB3          5 Gbps
Comphy-1: PEX0          2.5 Gbps

By selecting another channel tells me after trying that I can not start AP on 5Ghz and start at 2GHz   successfull.

Any idea how to deal with this?

recently purchased the 2g espressobin and am not understanding why I cannot obtain gigabit speeds from lan to wan. I am able to do so from the OS out/in, but from a client machine to a machine attached to the wan I am getting 1/3 the speed of gigabit. Below is the iperf results along with my systemd/network settings. Does anyone have an idea why this is occurring?

Client to machine in Ethernet attached to wan:

Connecting to host 192.168.2.1, port 5001
[  4] local 192.168.22.209 port 5859 connected to 192.168.2.1 port 5001
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  36.6 MBytes   307 Mbits/sec
[  4]   1.00-2.00   sec  42.4 MBytes   355 Mbits/sec
[  4]   2.00-3.00   sec  42.1 MBytes   354 Mbits/sec
[  4]   3.00-4.00   sec  42.0 MBytes   352 Mbits/sec
[  4]   4.00-5.00   sec  42.2 MBytes   355 Mbits/sec
[  4]   5.00-6.00   sec  42.4 MBytes   355 Mbits/sec
[  4]   6.00-7.00   sec  42.0 MBytes   353 Mbits/sec
[  4]   7.00-8.00   sec  42.5 MBytes   357 Mbits/sec
[  4]   8.00-9.00   sec  42.5 MBytes   356 Mbits/sec
[  4]   9.00-10.00  sec  42.0 MBytes   353 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec   417 MBytes   350 Mbits/sec                  sender
[  4]   0.00-10.00  sec   417 MBytes   349 Mbits/sec                  receiver

iperf Done.

From espressobin OS to wan connected machine:

root@espressobin:~# iperf3 -c 192.168.2.1 -p 5001
Connecting to host 192.168.2.1, port 5001
[  4] local 192.168.2.76 port 44154 connected to 192.168.2.1 port 5001
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   105 MBytes   879 Mbits/sec    0    708 KBytes
[  4]   1.00-2.00   sec   112 MBytes   938 Mbits/sec    0    708 KBytes
[  4]   2.00-3.00   sec   111 MBytes   934 Mbits/sec    0    708 KBytes
[  4]   3.00-4.00   sec   112 MBytes   939 Mbits/sec    0    708 KBytes
[  4]   4.00-5.00   sec   111 MBytes   933 Mbits/sec    0    708 KBytes
[  4]   5.00-6.00   sec   112 MBytes   939 Mbits/sec    0    708 KBytes
[  4]   6.00-7.00   sec   111 MBytes   934 Mbits/sec    0    708 KBytes
[  4]   7.00-8.00   sec   112 MBytes   939 Mbits/sec    0    708 KBytes
[  4]   8.00-9.00   sec   111 MBytes   933 Mbits/sec    0    708 KBytes
[  4]   9.00-10.00  sec   112 MBytes   939 Mbits/sec    0    708 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.08 GBytes   931 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  1.08 GBytes   931 Mbits/sec                  receiver

systemd/network config:

root@espressobin:~# cat /etc/systemd/network/*
/etc/systemd/network/10-br0.netdev:
[NetDev]
Name=br0
Kind=bridge

/etc/systemd/network/10-br0.network:
[Match]
Name=br0

[Network]
Address=192.168.22.1/24
IPForward=ipv4
IPMasquerade=yes
ConfigureWithoutCarrier=yes

/etc/systemd/network/10-eth0.network:
[Match]
Name=eth0

[Network]
DHCP=ipv4

/etc/systemd/network/10-lan0.network:
[Match]
Name=lan0

[Network]
Bridge=br0

/etc/systemd/network/10-lan1.network:
[Match]
Name=lan1

[Network]
Bridge=br0

/etc/systemd/network/10-wan.network:
[Match]
Name=wan

[Network]
DHCP=yes
BindCarrier=eth0
IPForward=ipv4
root@espressobin:~#

Linux espressobin 4.18.16-mvebu64 #402 SMP PREEMPT Fri Oct 26 17:23:18 CEST 2018 aarch64 GNU/Linux

I recently acquired an U-Blox MPCI-L201 4g LTE modem. This is my first time attempting this type of connection and things are not as intuitive as I would hope so I thought I would reach out.

I downloaded the most recent Armbian Stretch from the downloads page and re-flashed the emmc. 

lsusb clearly shows the device

root@clearfogpro:~# lsusb
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 1546:1146 U-Blox AG 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@clearfogpro:~# 

I'm using screen in a command box on an XU4 with Hardkernel's 18.04 as the host.

I've had good results with nmtui on a fresh Armbian install to set up the initial network connection, so I thought I would give that a try. It looks like the modem shows 4 additional wired connections that are not there if the card is removed. But I have to move the cursor to get something to display -

If I move the cursor up and down it exposes the entries -

Choosing Activate reveals the four wired connections -

so it appears the hardware is 'working.' These entries only show if the device is in either of the mpci slots. 

But it gets more difficult to decipher from there. Attempting to select one of the wired connections and then the Activate button makes it impossible to figure out what's happening on the screen -

Armbian-config displays similarly so I'm assuming this particular problem is graphic oriented.

I booted the XU4 into an Armbian build and had similar results. I found some really detailed information on the screen command that, while really interesting, was basically useless for this issue as far as I can tell as I couldn't find any formatting parameters with the exception of the "-a" switch which I think should automatically try to format pages but it didn't make a difference.

Through trial and success I connected to my Hotspot so I updated and upgraded, but that made no difference. But now I can find its ip and connect via ssh, and nmtui is nice via ssh!

But armbian-config, although it appears to run properly, complains that it does not have internet although clearly it does -

As I tried several times I noted the asterisks (*) move to different wired connections under USB Ethernet. After connecting via SSH I noted the <Activate> button becomes <Deactivate> when highlighting a starred entry, verified with my WiFi hotspot.  (BUT how is the Eth1 active with nothing connected?)

So this leads me to ask a couple questions ...

a) How to get past this 'screen' issue. In the past I've noticed these graphic issues don't happen on an SSH session.  I was lucky to guess and type the passphrase of my wifi and get this connected. I tried unsuccessfully several times to guess and enter the info for one of the ethernet ports. 

I tried several different terminal emulators, all had weird display results. I really need to be controlling the device through the USB serial rather than ssh through a hotspot on my phone. Again, it was a good guess getting this connected and I don't want to try again to get onto my local wifi.

b) once I was able to SSH to the clearfog, armbian-config shows me there is an ethernet connection over USB0 along side the terminal connection - how can I connect to this? I know there is a way to have multiple IPs on an adapter in linux but I haven't tried that; the instructions I found seemed more complex than I wanted to dive into, although I'd bet there's a simple proper way to do this.

c) What's the proper, or a better, way to enable a new 4G modem? I read some cryptic notes about wvdial on a TV box and followed some google links to various docs but I'm not quite putting it together. (separate post) Or is it even an issue as it looks like it and the sim work together to "just connect?"

d) If it is connected, or when I get it connected, how to I determine what the details are such as its IP, etc? It appears that it 'just works' but I need to be able to reference it for networking and, well, learn something.

Thanks in advance for any advice offered.