Search the Community

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:

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. The Armbian u-boot does not appear to recognise the eMMC. I used Globalscale's u-boot espressobin-bootloader-cpu-1000-ddr4-1cs-1g I created a USB stick using the standard procedure and booted the ESPRESSObin from this. 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 I could then mount the Linux partition on the eMMC. sudo mkdir /mnt/emmc sudo mount /dev/mmcblk0p1 /mnt/emmc 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 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 I rebooted with the USB stick removed. The system booted from the eMMC, however there were some issues with the Ubuntu system... 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 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) 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) 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 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?

I don't know if this is some strange thing about the kernel supplied for the Espressobin or what, but I am unable to load even the most basic rule set in nftables, the empty one that comes with the nftables package: 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 { } }

so on 2018-11-20 i've ordered an espressobin and tried armbian. and i probably got bitten by "yet another spi chip". 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.

I just pulled my espressobin back out of the box, re-imaged with 4.18.6-nvebu64, and sparked it up. Nearly everything just works, I'm so impressed! 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/u-boot-marvell/commits/u-boot-2018.03-armada-18.12 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

I purchased a V7 version of ebin But after updating uboot, the reboot is still in stock uboot. 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

I have Espressobin v7 1G and PCIe card WLE900VX. With armbian-config create AP. Starts successfully on 36 channels. I tried all the channels in 5Ghz, but works only successfully at 36 and 44. 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?

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

Hi - I ordered a 2gb Espressobin from Globalscale and later flashed flash-image-2g-2cs-1200_750.bin, which caused my Espressobin to hang at: TIM-1.0 WTMI-devel-18.07.0-6050fd5 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 0.898V I am able to boot to SATA using the sata recovery image, but cannot flash back to the working flash-image-2g-2cs-1000_800.bin. Here is what happens when I boot to SATA and attempt to flash the old bin: Booting Trusted Firmware BL1: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c BL1: Built : 16:29:17, Apr 20 2NOTICE: BL2: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c NOTICE: BL2: Built : 16:29:17, Apr 20 20NOTICE: BL31: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c NOTICE: BL31: U-Boot 2015.01-armada-17.02.0-01546-g184fa4e (Apr 20 2017 - 16:21:34) I2C: ready DRAM: 512 MiB Board: DB-88F3720-ESPRESSOBin CPU @ 1000 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] Comphy-0: PEX0 2.5 Gbps Comphy-1: USB3 5 Gbps Comphy-2: SATA0 5 Gbps Now running in RAM - U-Boot at: 1ff2b000 U-Boot DT blob at : 000000001fa18168 MMC: XENON-SDHCI: 0 SF: Unsupported flash IDs: manuf c2, jedec 2536, ext_jedec c225 *** Warning - spi_flash_probe() failed, using default environment PCIE-0: Link down SCSI: 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 Net: neta0 Hit any key to stop autoboot: 0 Marvell>> bubt flash-image-2g-1000_800_boot_sd_and_usb.bin spi usb Burning U-BOOT image "flash-image-2g-1000_800_boot_sd_and_usb.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found reading flash-image-2g-1000_800_boot_sd_and_usb.bin Image checksum...OK! SF: Unsupported flash IDs: manuf c2, jedec 2536, ext_jedec c225 Failed to probe SPI Flash I initially attempted a UART flash, but I get a similar error, but with a different SF message: SF: unrecognized jedec id bytes: c2, 25, 36 I read through a few posts, tried things like flashing via tftp instead of USB, but to no avail. Can anyone help?

Greetings! Just flashed my 1000-800, 2 ram chips (for what I reckon, I could provide a picture) 1gb espressobin with the latest image : However, I've no rtc, it seems: I've seen some of these errors being present in the developement efforts thread, however, I don't see any solutions other than using the latest firmware, that as per my knowledge, I do... Thanks a lot in advance!

Maybe a long shot: rather than setting up armbian on my new ESPRESSObin (epb), installing needed SW and tools, porting configs off my Cubietruck (cbt), would it be possible to tweak the cbt's SDcard / FS to boot on the ESPRESSObin? If I'm not mistaken the cbtis armhf based and all those binaries should also run on the epb!? Would it be "good enough" to add the arm64 architecture to the CBT with "dpkg --add-architecture arm64" and then to install linux-u-boot-espressobin-next linux-image-next-mvebu64 linux-headers-next-mvebu64 linux-firmware-image-next-mvebu64 linux-dtb-next-mvebu64 linux-$(lsb_release -cs)-root-next-espressobin shut down the cbt and put the card into the epb, booting it in the epb?

Hi, With a downloaded and installed Armbian Ubuntu 16.04.5 LTS image things seem to work as expected: lan0 and lan1 act like they are ports on an ordinary ethernet switch. My LAN is connected to lan0 and a device (HDHomeRun) is connected to lan1. The device and the Espressobin are accessible from other computers on the LAN and the Espressobin can access everything on my LAN (and beyond). But, digging deeper, something isn't quite right. The DHCP server on my LAN has been configured to assign a fixed IP address to br0 and the DHCP client for br0 on the Espressobin should be activated by /etc/systemd/network/10-br0.network: ebin@espressobin:~$ cat /etc/systemd/network/10-br0.network [Match] Name=br0 [Network] DHCP=ipv4 That seems to work as expected. lan0 and lan1 are a different matter. Just as for an ethernet switch, I would expect (as members of a bridge) neither to be assigned an IP address. ebin@espressobin:~$ cat /etc/systemd/network/10-lan.network [Match] Name=lan* [Network] Bridge=br0 ebin@espressobin:~$ ip addr 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: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether b6:0e:66:f8:d3:a8 brd ff:ff:ff:ff:ff:ff 3: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 4a:ab:78:59:41:5f brd ff:ff:ff:ff:ff:ff inet6 fe80::48ab:78ff:fe59:415f/64 scope link valid_lft forever preferred_lft forever 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:50:43:84:fb:2f brd ff:ff:ff:ff:ff:ff inet6 fe80::250:43ff:fe84:fb2f/64 scope link valid_lft forever preferred_lft forever 5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9a:b7:48:8e:77:24 brd ff:ff:ff:ff:ff:ff inet 10.137.113.131/24 brd 10.137.113.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::98b7:48ff:fe8e:7724/64 scope link valid_lft forever preferred_lft forever 6: wan@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:fb:2f brd ff:ff:ff:ff:ff:ff 7: lan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state UP group default qlen 1000 link/ether 00:50:43:84:fb:2f brd ff:ff:ff:ff:ff:ff inet 10.137.113.11/24 brd 10.137.113.255 scope global lan0 valid_lft forever preferred_lft forever 8: lan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state UP group default qlen 1000 link/ether 00:50:43:84:fb:2f brd ff:ff:ff:ff:ff:ff For some reason lan0 gets an IP address, but lan1 doesn't. What's more, a DHCPDISCOVER is being sent out by the Espressobin every 10-15 seconds. What's going on here? pygr

Howdy, Trying to disable NCQ via kernel option, i have set the following extraarg=libata.force=5:noncq and extraarg=pcie_aspm=off in /boot/armbianEnv.txt. Rebooted and I do not see the change applied via: root@espressobin:~# cat /proc/cmdline console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=UUID=e5344a53-4325-4b08-b6f3-1bfe432789d1 rw rootwait Thanks, Tim

Hi, I am currently trying to install a secure /trusted U-Boot into the EspressoBin and got several questions for this issue. I followed this manual: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/blob/u-boot-2017.03-armada-17.10/doc/mvebu/trusted_boot.txt Regarding this manual the Flag for "efuse write BOOT_DEVICE SPINOR "has to be setup into NOR-Flash, so that the device will only boot from NOR anymore (which is a reason for security, I know). Can I skip this step, so that I do not damage the complete board? I would choose UART for testing my encrypted bootloader. I skipped the step "efuse write DEV_DEPLOY 1" and my board doesn't boot anymore. Could this be the reason? Initially, I installed my own keys for aes-256.txt and iv.txt and also generated CSK[0..F].txt,KAK.txt files (and csk[1..16].txt, kak.txt) each with different seeds. I couldn't find any manual for this setup. Does anyone have experience with the encryption-setup of U-Boot with ATF? Thanks for your help!

I have a few 2G boards bought from Globalscale over the last few months. They've been working fine without any issues. So far I've been using the firmware that came with the boards. One has: TIM-1.0 WTMI-armada-17.10.1-b90dbf0 ENTER init_ddrgen DDR_TOPOLOGY is 7 : DDR3, 2CS 1G + 1G WTMI_CLOCK=2 ... U-Boot 2017.03-armada-17.10.1-gaee49fc (Jan 29 2018 - 18:21:49 +0800) (and has the w25q32dw SPI) The other two have: TIM-1.0 WTMI-armada-17.10.5-bb8f823 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.143V ... U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800) (and have the newer Macronix mx25u3235f SPI) I wanted to try the Armbian boot images, first via SATA to see how they go on these boards rather than overwriting the images (which I haven't been able to find copies of). In all cases, I get "TIM-1.0" then eventually the ">" prompt, but nothing else. I copied the images with 'dd if=sata-image-2g-2cs-1000_800.bin of=/dev/sdd conv=fdatasync'. I saw a post suggesting that they should be copied starting at LBA 1 or 34, so I tried that too. In those cases I didn't even get the "TIM-1.0", but only the ">" prompt. I'm not sure what I'm missing here. Perhaps the images are not compatible with these boards? I guess my next step is to try loading the UART image via the serial port.

I goofed-up my espressobin install and need to recover and start over. Here is what happened (to my embarrassment): I recently obtained a 1GB espressobin from Amazon.com. I flashed the Armbian_5.59_Espressobin_Debian_stretch_next_4.18.6.img to a Sandisk Ultra and booted the board. The marvell>> prompt came up just fine, and I used the command bubt .flash-image-1g-1cs-800_800.bin spi usb to load the flash binary from my usb drive. But I did not know at the time that the correct flash to use was actually flash-image-1g-1cs-1000_800.bin. But my worse mistake was applying the script given on the instruction page, where it says: "Updated u-boot needs new default boot environment and new boot script (overwrite the one on your /boot media – needed only if you upgrade from < v5.59). This is what you need to copy/paste into u-boot prompt:". I guess I was supposed to use the script at https://dl.armbian.com/espressobin/u-boot/bootscript/ ? I tried to apply that script after the mistake, but it generated errors. So now when I try to boot the board, this is the kind output I get on my minicom: ## Error: "bootcmd_" not defined ** Bad device : 0x6d00000 ** ## Executing script at 06d00000 Wrong image format for "source" command So this is a mess. How do I go about recovering and getting back on track? Thanks, Tom

Since I don't have one unit yet and the information related to this board is scarce, I'd like to ask if someone who owns one could test what the power budget for the board is. In Marvell's github wiki there is the following mention: It would be really great if under load and with all the network ports connected to gigabit the board only took 1W@12V. I found a script in github that would help to reduce power usage: https://github.com/MarvellEmbeddedProcessors/main/wiki/Power-Saving-Script Thanks for you help. Depending on the results I may have a solution for one project where I need to use a dual-lan board with low power consumption.

Hi. I've ordererd a new bunch of espresso bins from globalscale. they have the same board revision as my old ones (V5_0_1 and 1G 2CS) - but now I get an error while trying to flash armbian uboot (mentioned in https://www.armbian.com/espressobin/) Marvell>> bubt espresso/flash-image-1g-2cs-800_800_boot_sd_and_usb.bin spi tftp Burning U-BOOT image "espresso/flash-image-1g-2cs-800_800_boot_sd_and_usb.bin" from "tftp" to "spi" Using neta@30000 device TFTP from server 192.168.5.5; our IP address is 192.168.5.10 Filename 'espresso/flash-image-1g-2cs-800_800_boot_sd_and_usb.bin'. Load address: 0x5000000 Loading: ######################################################## 2.1 MiB/s done Bytes transferred = 819136 (c7fc0 hex) Image checksum...OK! SF: unrecognized JEDEC id bytes: c2, 25, 36 Failed to probe SPI Flash some months ago I've ordered a bunch of espresso bins and I could flash uboot without any problems. I tried to flash two different boards out of the new order... both failed with this message. same thing, if I try to flash from usb stick instead of tftp. Has anyone else encountered this issue? Any idea how to fix it? Thanks in advance. +++ bootup of the currently shipped espresso bins after trying to flash the armbian uboot +++ TIM-1.0 WTMI-armada-17.10.5-34ce216 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.038V Fill memory before self refresh...done 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!! 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 QS GATING ============= Calibration done: cycle = 0x00 tap =0x5C CH0_PHY_RL_Control_CS1_B0[0xC00011A4]: 0x0000005C CH0_PHY_RL_Control_CS1_B1[0xC00011A8]: 0x0000005C DLL TUNING ============== DLL 0xc0001050[21:16]: [0,2b,15] DLL 0xc0001050[29:24]: [8,33,1d] DLL 0xc0001054[21:16]: [0,23,11] DLL 0xc0001054[29:24]: [8,2d,1a] DLL 0xc0001074[21:16]: [0,3f,1f] DLL 0xc0001074NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.3(release):armada-17.10.8:34247e0 NOTICE: BL1: Built : 16:46:13, May 10 2NOTICE: BL2: v1.3(release):armada-17.10.8:34247e0 NOTICE: BL2: Built : 16:46:13, May 10 2018 NNOTICE: BL31: v1.3(release):armada-17.10.8:34247e0 NOTICE: BL31: U-Boot 2017.03-armada-17.10.3-g06ad760-armbian (May 10 2018 - 16:45:48 +0200) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 800 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] DRAM: 1 GiB U-Boot DT blob at : 000000003f7182d8 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 SF: unrecognized JEDEC id bytes: c2, 25, 36 *** Warning - spi_flash_probe() failed, using default environment Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 Marvell>> bdinfo arch_number = 0x00000000 boot_params = 0x00000100 DRAM bank = 0x00000000 -> start = 0x00000000 -> size = 0x40000000 baudrate = 115200 bps TLB addr = 0x3FFF0000 relocaddr = 0x3FF2B000 reloc off = 0x3FF2B000 irq_sp = 0x3F7182C0 sp start = 0x3F7182C0 Early malloc usage: 220 / 2000 Marvell>> sspi SF: unrecognized JEDEC id bytes: c2, 25, 36 Marvell>> version U-Boot 2017.03-armada-17.10.3-g06ad760-armbian (May 10 2018 - 16:45:48 +0200) aarch64-linux-gnu-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 GNU ld (Linaro_Binutils-2017.11) 2.28.2.20170706 +++ Furthermore... +++ According to JEP106AW Jul 2018 (https://www.jedec.org/standards-documents/docs/jep-106ab#) the JEDEC id byte c2... means Macronix An indeed... The old boards use a Winbond 25Q32 FWS10 152 -> SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB The new ones use a Macronix MXIC MX 25V3 2311 -> SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB (images attached)

Using the WiFi card: Compex WLE900VX Configured: /etc/network/interfaces: allow-hotplug wlp0s0 iface wlp0s0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf and wpa_supplicant.conf ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US network={ ssid="****" scan_ssid=1 psk=''*****' } The networking.service tries to come up during boot before the WiFi and this causes problems so: $ systemctl disable networking the network comes up great on boot. I'm using a stretch 4.18.7 kernel compiled with realtime patches and compile to enable ALSA -- using this as a wifi streamer Need to add the firmware-atheros package!

i have a problem to get the Interfaces of the Board up at boot without the Bridge. What i found out is that the eth0 comes up to late so it could not find the other Interfaces. So how could i do something like eth0 post-up ifconfig wan up with systemd-networkd? Or could i change the order how the Interfaces will be initialize at boot? could somebody Help me with this Topic? System Info ARMBIAN 5.59 stable Debian networkctl status -a (snippet) 4: eth0 Link File: /lib/systemd/network/99-default.link Network File: /etc/systemd/network/10-eth0.network Type: ether State: degraded (configuring) Path: platform-d0030000.ethernet Driver: mvneta 5: wan Link File: /lib/systemd/network/99-default.link Network File: /etc/systemd/network/10-wan.network Type: ether State: off (configuring) Path: platform-d0032004.mdio Driver: dsa

So I have a new board that I am working with. I cannot get armbian-config to display anything. I have tried both the Ubuntu and Debian images. I also tried the default and next images with not luck. The default image has the drivers that I need for a mpcie network card. The final goal is to install the kernel source so I can update drivers. [ 2.037420] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 2.048872] r8169 0000:00:00.0 eth1: RTL8168evl/8111evl at 0xffffff8000376000, 00:13:3b:21:4b:62, XID 0c900800 IRQ 108 [ 2.048931] r8169 0000:00:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 2.653362] r8169 0000:00:00.0 enp0s0: renamed from eth1 [ 20.069026] r8169 0000:00:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2 [ 20.069052] r8169 0000:00:00.0 enp0s0: unable to load firmware patch rtl_nic/rtl8168e-3.fw (-2)