Big disappointment with this box Ethernet.

Since the chip is USB 2.0 Ethernet, it drops data like crazy in my flow-control-off Gbit network. Not usable for anything serious.

Now that I looked closer, it's the same chip in the previous rPi boards. That was a big flaw in those boards design.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Yep, perfomance of those boxes sucks. I'm using one as a wireguard gateway for admin access to my remote cabin which has only a low speed gsm connection so it is enough, but its performance limits other uses.

Tried running the script. It stops with “Line 4: Unsupported command” regardless of the USB device

Giunto Wrote:
-------------------------------------------------------
> Tried running the script. It stops with “Line 4:
> Unsupported command” regardless of the USB
> device


Solved it by flashing from bare metal instead of a virtual machine. Now, I need to access it via SSH. Does this Debian support SSH via OpenSSH by default, or do I need to crack the hardware open?

I have successfully gotten one of my 3020 boxes to boot from USB with the updated 6.14.6 kernel and the 6.6.2 rootfs, but am experiencing the same problems as mmm, where wloader jams the eMMC if USB boot is not selected before eMMC is read by wloader. My wloader firmware seems to be the same major version (7.1_212) as mmm's (7.1_216), so I imagine the cause is the same or similar. Has any progress been made on flashing the SPI from within Linux? I would like to attempt flashing one of Ksuszka's firmware dumps to see if this solves the issue.

Phaze Henot,

> Has any
> progress been made on flashing the SPI from within
> Linux? I would like to attempt flashing one of
> Ksuszka's firmware dumps to see if this solves the
> issue.

I have not looked into how to flash this boot loader in Linux. I need a recovery mechanism before I'd try flashing Ksuszka's firmware dumps. Not sure if we've figured that out how in this thread. If there is a way, e.g. firmware on USB recovery, then I will try.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Understandable, in that case, I have ordered a CH341A programmer so that I may attempt to flash the chip directly, as well as recover from any unsuccessful testing. With this, I should be able to verify if it is solely the wloader version causing the eMMC issues. If this is the case, I should be able to experiment with different methods of flashing the firmware from within Linux. Are there any approaches or tests you would like me to try?

mmm has tried here:

https://forum.doozan.com/read.php?2,134563,136711#msg-136711

Gravelrash has tried here:

https://forum.doozan.com/read.php?2,134563,135491#msg-135491

That is how you flash boot loader to SPI (with flashcp). But unfortunately it did not work.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

ksuszka has info about recovery here:

https://forum.doozan.com/read.php?2,134563,137486#msg-137486

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)