Jump to content
  • 0

Espressobin support development efforts


lanefu
 Share

Question

 

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

Spoiler

# Marvell Armada 37x 1xmPCIe 2xGBE

BOARD_NAME="espressobin"

LINUXFAMILY="mvebu64"

BOOTCONFIG="mvebu_espressobin-88f3720_defconfig"

#BOOTCONFIG="mvebu_armada-37xx"

MODULES="mv_cesa"

MODULES_NEXT="mv_cesa"

CLI_TARGET="jessie,xenial:default,next"

KERNEL_TARGET="default,next"

BUILD_DESKTOP="no"

#

BOARDRATING=""

CHIP="http://docs.armbian.com/Hardware_Other/#marvel-armada-espressobin"

REVIEW="http://forum.armbian.com/index.php/topic/TBD/"

HARDWARE="http://wiki.espressobin.net/tiki-index.php?page=About+ESPRESSObin"

FORUMS="http://forum.armbian.com/index.php/forum/11-other-boards/"

 

mvebu64.conf

Spoiler

ARCH=arm64

KERNEL_IMAGE_TYPE=Image

HAS_UUID_SUPPORT=yes

#OFFSET=2

 

BOOTSCRIPT="boot-marvell.cmd:boot.cmd"

 

BOOTSOURCE=$MAINLINE_UBOOT_SOURCE

BOOTDIR=$MAINLINE_UBOOT_DIR

BOOTBRANCH=tag:v2017.05-rc1

 

 

BOOTENV_FILE='clearfog-default.txt'

HAS_UUID_SUPPORT=yes

 

case $BRANCH in

        default)

        KERNELSOURCE='https://github.com/MarvellEmbeddedProcessors/linux-marvell.git'

        KERNELBRANCH='branch:linux-4.4.8-armada-17.02-espressobin'

        KERNELDIR='linux-marvell'

        DEB_BRANCH=4.4.8

#       CHOSEN_KERNEL=linux-image-linux-4.4.8-armada-17.02-${LINUXFAMILY}

        ;;

 

        next)

        KERNELSOURCE=$MAINLINE_KERNEL_SOURCE

        KERNELBRANCH=$MAINLINE_KERNEL_BRANCH

        KERNELDIR=$MAINLINE_KERNEL_DIR

 

        KERNEL_ALT_GCC='> 6.1'

        ;;

esac

 

## can probaly go slower

CPUMIN=800000

CPUMAX=1200000

GOVERNOR=ondemand

 

 

write_uboot_platform()

{

#       dd if=$1/u-boot.mmc of=$2 bs=512 seek=1 status=noxfer > /dev/null 2>&1

        echo "hey"

}

 

family_tweaks()

{

        chroot $CACHEDIR/$SDCARD /bin/bash -c "apt-get -y -qq remove --auto-remove lirc linux-sound-base alsa-base alsa-utils bluez>/dev/null 2>&1"

}

 
Edited by zador.blood.stained
Renamed to reflect the contents
Link to comment
Share on other sites

Recommended Posts

  • 0

Well I've fixed my instability issue. The root cause was the same as https://forum.netgate.com/topic/144636/sg-1100-intermittent-reboots, and it was power related. The fix was to replace the 470uf/16V capacitor (component EC1 on the schematic) sat immediately behind the 12V DC jack which under testing leaked under certain temperature conditions (variations). As such the board is now stable and has been running OpenWRT 18.06.2 for 24 hours with memtester and stress running continuous during that entire time.

 

I'll leave it a few more days, after that I'm going to assume that its fixed and that is what NetGate were referring too when they mention 'a power related component'.

 

And GlobalScape will not tell you, they know of the problem, in a reply from Kevin Liu he says 'Yes, I do have knowledge regards the power related component issue.' when I asked which component it was so i could attempt to replace myself.

Link to comment
Share on other sites

Search Before Posting!

  • 0

@FlashBurn I'm having the same problem - only getting 800MHz. It's frustrating, since I bought this board because it claimed to deliver 1.2GHz.

 

I think this is a problem in Linux, but I'm not sure where to report it, so I made a post in the espressobin.net forums.

Now I just discovered that they deleted my thread, but here's a repost:

 

Edited by Anders
Update link.
Link to comment
Share on other sites

  • 0
19 minutes ago, Smurfix said:

Yet another reason not to buy one of those things.


Yeah you guys are inspiring me to just throw my 2 boards in the trash.  I wanted to build an OMV box for my brother-in-law but I'm afraid to do so.

Link to comment
Share on other sites

  • 0

To be fair, I have three, from the first series. With identical settings, one is definitely unstable (dunno how they got it to pass what Globalscale considers testing, let alone what I would do), one is 100% stable and working as my main router, and one is in my "TODO try with current mainline" pile. We'll see whether I can get the thing to work without much hassle; if not, it'll be replaced with a Raspberry Pi 4 and two USB3 Ethernet dongles.

 

NB: Recycling, not trash, please. (Yes I know that electronics recycling is far from optimal.)

Link to comment
Share on other sites

  • 0

Despite of all the seemingly bad news, I boldly ordered a batch of 10 EspressoBin V7 recently. Globalscale promised to test them for me for stability (I am not interested in squeezing out the last bit of performance), and I tested them again after reception: They all seem to run stable with Ubuntu Xenial (the "newest" image provided by Globalscale) and with Armbian kernel 4.19.59-mvebu64.

Since there is still a few weeks till they go on duty, if anyone is interested in a particular test on them, I am willing to do so. I am not into kernel development, so I would need some instruction. ;-)

Link to comment
Share on other sites

  • 0
14 hours ago, barish said:

Despite of all the seemingly bad news, I boldly ordered a batch of 10 EspressoBin V7 recently. Globalscale promised to test them for me for stability (I am not interested in squeezing out the last bit of performance), and I tested them again after reception: They all seem to run stable with Ubuntu Xenial (the "newest" image provided by Globalscale) and with Armbian kernel 4.19.59-mvebu64.

Since there is still a few weeks till they go on duty, if anyone is interested in a particular test on them, I am willing to do so. I am not into kernel development, so I would need some instruction. ;-)

 

that is bold! I hope it goes smoothly..

You could try the Armbian testing tools.. its just a few config files to adjust for your use..

https://github.com/armbian/autotests

Link to comment
Share on other sites

  • 0

After a power outage my espressobin does not boot from SD card. In my kermit console I see:

## Executing script at 06d00000
Wrong image format for "source" command
/boot/
1119 bytes read in 16 ms (67.4 KiB/s)
## Executing script at 06d00000
221 bytes read in 5 ms (43 KiB/s)
16488960 bytes read in 708 ms (22.2 MiB/s)
8029703 bytes read in 353 ms (21.7 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:    8029639 Bytes = 7.7 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 3ee82000, end 3f62a5c7 ... 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.56-mvebu64 (root@armbian.com) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.89 SMP PREEMPT Tue Jun 25 22:27:47 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 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: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!


BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 

Indeed, there is no device /dev/mmcblk0p1. But I can see the bootable sd card at /dev/mmcblk1p1.

Any ideas what is wrong here?

Link to comment
Share on other sites

  • 0
36 minutes ago, Andrius said:

After a power outage my espressobin does not boot from SD card. In my kermit console I see:

Indeed, there is no device /dev/mmcblk0p1. But I can see the bootable sd card at /dev/mmcblk1p1.

Any ideas what is wrong here?

Maybe the filesystem got corrupted. Can you mount it the sd card on another computer?

Link to comment
Share on other sites

  • 0

As a workaround, try putting the following line into /boot/armbianEnv.txt:

rootdev="/dev/mmcblk1p1"

Or modify and compile boot.cmd accordingly. Why the SD card's device has changed though, I cannot tell. I know that Linux changes device names for HDDs, which might be called /dev/sda or /dev/sdb with no apparent hardware or software change.

Link to comment
Share on other sites

  • 0

Can anyone tell me what are the differences between the legacy U-Boot WTMI-armada-17.10.5-bb8f823 and the one used by Armbian ( WTMI-devel-18.12.1-e6bb176 )? The unmodified boards boot perfectly each time, but when I change to Armbian u-boot, no matter what frequency (I tried 800 and 1000 MHz), the boards need one to four power cycles till they boot even into u-boot. On serial console, I get:

TIM-1.0
WTMI-devel-18.12.1-e6bb176
WTMI: system early-init
SVC REV: 5, CPU VDD voltage: 1.108V

And that's it. I need to pull the power plug and put it back in for several times, then finally the board boots fine (and runs fine ever after). The voltage varies depending on the frequency set by loading different u-boot images.

 

Has anyone a clue?

Link to comment
Share on other sites

  • 0
1 hour ago, barish said:

As a workaround, try putting the following line into /boot/armbianEnv.txt:


rootdev="/dev/mmcblk1p1"

That is only for specifying U-Boot location and passing it to kernel ... But :

 

The "ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!" really means that /etc/fstab isn't trying to mount proper partition.

Link to comment
Share on other sites

  • 0
3 hours ago, martinayotte said:

That is only for specifying U-Boot location and passing it to kernel ... But :

 

The "ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell!" really means that /etc/fstab isn't trying to mount proper partition.

Then change fstab device to mmcblk1p1 or even better to the UUID of the SD card, no?

Link to comment
Share on other sites

  • 0
4 hours ago, barish said:

Can anyone tell me what are the differences between the legacy U-Boot WTMI-armada-17.10.5-bb8f823 and the one used by Armbian ( WTMI-devel-18.12.1-e6bb176 )? The unmodified boards boot perfectly each time, but when I change to Armbian u-boot, no matter what frequency (I tried 800 and 1000 MHz), the boards need one to four power cycles till they boot even into u-boot.

By now, I found some more information regarding TIM and WTMI. According to Marvell's A3700-utils documents, TIM is a first aproach to address DDR3/DD4 at fixed freq of 300/400MHz, while WTMI "performs dynamic DDR PHY training" to gain higher memory speed. Apparently, the Armbian U-Boot uses a later version of WTMI (and maybe uses different parameters?), does anyone know about this?

Link to comment
Share on other sites

  • 0

I changed now to the legacy U-Boot (17.10) because it boots very reliably (which is what I need). I am not sure of the negative effects (testing is ongoing) but there is no option for me at the moment. I hope that someone with U-Boot and/or Marvell skills can tell me what changes from 17.10 -> 18.12 led to the unreliable booting. Since it takes place at the start of the WTMI RAM tuning process, I can only assume that there is the rub.

Link to comment
Share on other sites

  • 0

Thanks for you advices.

First I checked /etc/fstab and found that it already contains the entry with the correct UUID:

UUID=a02e20f8-402e-4469-87e0-9d0c9507ea15 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1

Then, as suggested, I updated /boot/armbianEnv.txt with rootdev="/dev/mmcblk1p1". 

Strange thing was that this file contained some apparently zero chars at the end which did not make happy some text editors:

 

rootdev="/dev/mmcblk1p1"

/var/log.hdd/apt/term.log {
  rotate 12
  monthly
  compress
  missingok
  notifempty
}

/var/log.hdd/apt/history.log {
  rotate 12
  monthly
  compress
  missingok
  notifempty
}

^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

I let it boot and got somewhat different output, but still no go:

 

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 4.19.56-mvebu64 (root@armbian.com) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.89 SMP PREEMPT Tue Jun 25 22:27:47 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 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
Checking all file systems.
done.
mount: mounting "/dev/mmcblk1p1" on /root failed: No such file or directory
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
No init found. Try passing init= bootarg.


BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

Should I remove those pesky zeros? Are they a sign the file system has problems?

 

Link to comment
Share on other sites

  • 0
On 5/7/2020 at 11:01 PM, barish said:

Despite of all the seemingly bad news, I boldly ordered a batch of 10 EspressoBin V7 recently. Globalscale promised to test them for me for stability (I am not interested in squeezing out the last bit of performance), and I tested them again after reception: They all seem to run stable with Ubuntu Xenial (the "newest" image provided by Globalscale) and with Armbian kernel 4.19.59-mvebu64.

Since there is still a few weeks till they go on duty, if anyone is interested in a particular test on them, I am willing to do so. I am not into kernel development, so I would need some instruction. ;-)

Hey, I am considering getting this board as a openwrt router. How where you able to get them to commit to testing it before purchasing. Also have you had any issues since?

Link to comment
Share on other sites

  • 0
6 hours ago, bigbrovar said:

Hey, I am considering getting this board as a openwrt router. How where you able to get them to commit to testing it before purchasing. Also have you had any issues since?

I purchased 10 and will most probably buy more in future. :-P I had no issues with U-Boot 17.10 despite intensive testing. If you are in Germany, I can offer you a tested EspressoBin v7 1GB.

Link to comment
Share on other sites

  • 0
On 6/24/2020 at 1:33 PM, barish said:

I purchased 10 and will most probably buy more in future. :-P I had no issues with U-Boot 17.10 despite intensive testing. If you are in Germany, I can offer you a tested EspressoBin v7 1GB.

I think I might have to take you up on this offer. I don't stay in Germany but I am sure I can be shipped to.

Link to comment
Share on other sites

  • 0
On 6/24/2020 at 1:33 PM, barish said:

I purchased 10 and will most probably buy more in future. :-P I had no issues with U-Boot 17.10 despite intensive testing. If you are in Germany, I can offer you a tested EspressoBin v7 1GB.

Can you send me a message or how do we make this happen? :)

Link to comment
Share on other sites

  • 0

Is there a time frame when espressobin will also have a newer kernel version? I tried arch linux with kernel 5.8 and there the espressobin was working as intended, but on the armbian kernel 4.19.120 (or something like that) it is still not running with the right frequency :(

Link to comment
Share on other sites

  • 0
4 hours ago, lanefu said:

hey @FlashBurn

v20.08 armbian will have kernel 5.6. you can test it out on a nightly image now if you like

How? I wanted to change the kernel, but there are only old kernels on armbian-config. So how can I change to a nightly built? Or do you mean from the download site? This hasn´t worked for me yesterday, but I can try tomorrow again.

 

Edit::

Nope, still not working (nightly built download). Goes right to 404 :(

Edited by FlashBurn
Link to comment
Share on other sites

  • 0

I still don´t get it. I tried archlinux with a kernel 5.8 and it worked like it should. So I tried armbian and build my own kernel 5.7.16 (dev) and still the problem that I don´t get the right frequency.

 

Does anyone has an idea what I can check to find the differences between the archlinux kernel and the armbian kernel?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...