Hello,
read kwboot to serial load the bootloader.
mvebu64boot for mocchabin.
The GlobalScaleTechnologies devices are really non-brickables (by
software and system sides) devices since the sheevaplugs...
Not quite affordable but really nice for development board.
High level deloppers skill may be needed because of long times bugs in
the developpment and upstreamed actions.
I am in work on a linux python swisstool for them and will share soon
some code and tips.
I also look on integration for a personal solution already POCed from
years but still in heavy development for end users...
I can shared some experiences of my tests, somes are on my blog
CyberMind.FR.
I already boot UEFI on EspressoBin and tried IPFire and also reborn the
EnigmaBox Suite (that I will also refresh and share on GitHub).
I get twoBoot UEFI tried recently and now think about multi boot and
auto recovery.
I work on this from years for a Home Security and IOT Gateway device.
Still in think to get another OS than OpenWrt, may be a Debian or
ARMBian refork, and also something more sexy for end users devices with
a prettier WebUI.
A lot of manufacturers works with these Marvell SoC, like RaidSonic,
NetGear, GLInet, Logitech SqueezeBox, French ISP Free.FR, ...
Stay tuned...
Cheers.
Have a nice day,
++Gk2
PS; I get a mass crash on all my IT, so my notes are somewhere, my codes
and POC also, if any question about GST devices are still pending, do
not hesitate to ask, I will help with pleasure...
PPS; I have no affiliation with GST, I just like these Marvell Based
devices, still too much innovative.
GuruPlugs get ZigBee in very first and now MocchaBin gets the MikroPik BUS !
SheevaPlugs still runs Debian in a 24/24, 7/7 without any issues...
PPPS; sorry for the little out of topic, but still mainly in the Subject
about EspressoBin.
Le 29/10/2025 à 13:42, Gandalf a écrit :
ARF, sorry for the :
You can also test the I pot without flashing and for recouvert with
lavoir toilette.
You may read, instead;
You can also test the UBOOT without flashing or for recovery with
kboot utils.
Sorry for noise...
++Gk2
Le 28/10/2025 à 17:56, Gérald KERMA a écrit :
Hello
You can also test the I pot without flashing and for recouvert with
lavoir toilette.
You may find some advices on the blog CyberMind.fR which will soon
been enhanced with édition and mocchabin.
Cheers
Le mar. 28 oct. 2025 à 03:01, Alan Corey <[email protected]> a écrit :
Learn to read error messages. The poor thing has no idea what
ext4ls is. It could be a missing header or library.
_________________________
Life will be better once the Republicans move to Mars.
_________________________
FIRE TRUMP!
On Mon, Oct 27, 2025, 6:49 PM Marcin Juszkiewicz
<[email protected]> wrote:
W dniu 27.10.2025 o 16:39, Rainer Dorsch pisze:
> Hello,
>
> has anybody by chance advise for running Debian 13 on the
espressobin v5?
I was running OpenWRT on mine a few years ago. Wrote a blog
post about
handling U-Boot build and update:
https://marcin.juszkiewicz.com.pl/2021/02/15/ebbr-on-espressobin/
<https://marcin.juszkiewicz.com.pl/2021/02/15/ebbr-on-espressobin/>
> Is u-boot potentially too old to work with a Debian 13
installer image?
This device is probably still supported in U-Boot so you
should be able
to build current one. But you have Armbian one so I would
expect it to
be able to boot Debian in some way.
> Marvell>> version
>
> U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian (Sep 05 2018
- 21:49:34 +0200)
> If yes, how would I update u-boot? The device supports a
bubt command:
>
> Marvell>> help bubt
> bubt - Burn a u-boot image to flash
From my post above:
Marvell>> bubt flash-image.bin spi usb
Burning U-Boot image "flash-image.bin" from "usb" to "spi"
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... 2 USB Device(s) found
Image checksum...OK!
SF: Detected is25wp032 with page size 256 Bytes, erase size 4
KiB, total
4 MiB
Erasing 991232 bytes (242 blocks) at offset 0 ...Done!
Writing 990944 bytes from 0x6000000 to offset 0 ...Done!
