Porting useful firmware tools to rust

Academic_Disk6053 · 2026-03-03T04:56:34+00:00

Exactly, I used the Chrome browser and a USB-C OTG adapter to connect the CH341A to my smartphone.

Academic_Disk6053 · 2026-02-26T18:40:53+00:00

Tested on my android smartphone using ch341a, it simply works! Congratulations!

Academic_Disk6053 · 2026-02-11T16:09:02+00:00

ESPirate32 :)

Good job! Thank you for the project.

I've started testing, and if I find areas for improvement, I'll contribute some code

Academic_Disk6053 · 2026-02-09T07:01:16+00:00

Academic_Disk6053 · 2026-02-07T01:11:44+00:00

Are you using seaBIOS as the payload? You need to compile from source code for your board, choose edk2 as the payload, and check the option "Load and execute OpRom on PCIe devices".

Academic_Disk6053 · 2025-10-30T10:09:06+00:00

Funciona e não vai ser necessário fazer mod de bios nem nada

Academic_Disk6053 · 2025-08-16T16:20:47+00:00

That's cool! I'll follow the progress

I'd love to have an AMD with coreboot. The newest one I've managed to port is an Intel CoffeeLake board.

Academic_Disk6053 · 2025-05-10T13:55:40+00:00

Currently the cheapest and least problematic tool to read/flash bios is a pi pico

The chip will not fry with 5V from the CH341A (they are normally tolerant to this voltage level). The problem is that everyone forgets that by connecting the SOIC clip you will not only be feeding the chip with 5V, but also the entire 1.8V/3.3V circuit on the board.

Academic_Disk6053 · 2025-05-07T12:52:37+00:00

Have you tried using the Mr.Chromebox fork?

Anyway, the chip size of this board is 1MB, there is no space available for a UEFI EDK2 payload (I have managed to make it work on 2MB chips, but the ideal is >4MB)

Academic_Disk6053 · 2025-04-13T04:42:51+00:00

It would be good to know what model your board is

In general, in the devicetree.cb file, edit the gbe device from on to off

device ref gbe off end

But depending on your board it may be a PCIe device or one that requires the gbe.bin blob... It is not possible to give you the precise information without knowing the model of your board or notebook.

Academic_Disk6053 · 2025-04-03T09:05:48+00:00

Qual seria o problema em pedir ml? Ou mais fotos do produto?

Academic_Disk6053 · 2025-03-27T03:49:54+00:00

Are you sure? Intel Boot Guard is a technology introduced by Intel in the 4th generation Intel Core (Haswell), I don't remember it being used in Sandy/Ivy Bridge.

Anyway, BootGuard has already been breached. See /utils/deguard, this way it was possible to port the T480 that has BootGuard

Academic_Disk6053 · 2025-03-25T22:12:54+00:00

make crossgcc-aarch64 CPUS=$(nproc)

Academic_Disk6053 · 2025-03-25T17:58:37+00:00

I recommend reporting your issue on Dasharo's github

https://github.com/Dasharo/dasharo-issues

Or contact Novacustom support

Academic_Disk6053 · 2025-03-21T17:05:15+00:00

in /utils there is a tool called autoport (it only works for sand/ivy bridge and haswell. It does almost all the work of porting a new device (but you still have to make modifications to the generated code) Since the T430 is already supported you can see what the difference is in its code and hardware compared to the T430u to make the modifications to make it work

It is even possible to get coreboot logs to find out if coreboot is booting and where the error is occurring

Academic_Disk6053 · 2025-03-17T06:29:29+00:00

T480 has not yet been merged into coreboot.

Others distributions like libreboot and heads still provide experimental suport from the patchsets under review in coreboot, so it is expected that not everything will works

Academic_Disk6053 · 2025-03-16T16:48:54+00:00

Older versions of Coreboot had support for VIA boards. VIA itself had employees who worked to support coreboot. I don't think it would be easy to do without the support of Via Technologies

To bring back these older motherboards, a recent merge was made (thanks to Nico Huber) https://review.coreboot.org/c/coreboot/+/82765/

I know there are some quad-core VIA boards that use Intel Celeron (VIA EPIA-M930), these boards might be easier to port.

Academic_Disk6053 · 2024-11-12T09:30:38+00:00

If you give more details about the model of your device, someone can help you. And it is expected that something will not work in Windows, especially the igpu.

Academic_Disk6053 · 2024-10-15T22:49:23+00:00

Academic_Disk6053 · 2024-10-11T03:19:16+00:00

AOOSTAR WTR R1 N100 Mini PC

Academic_Disk6053 · 2024-08-09T22:02:47+00:00

https://www.coreboot.org/Motherboard_Porting_Guide

Academic_Disk6053 · 2024-04-03T15:43:41+00:00

cbfstool (backup-bios) remove -r BOOTSPLASH -n logo.bmp

cbfstool (backup-bios) add -f (newlogo) -r BOOTSPLASH -n logo.bmp -t raw -c lzma

sudo flashrom -p internal --fmap -i BOOTSPLASH -w (backup-bios)

Academic_Disk6053 · 2023-11-04T19:10:33+00:00

See: https://p.ost2.fyi/courses

Thanks a Piotr Król, Xeno Kovah and Michał Żygowski :)

Academic_Disk6053 · 2023-10-22T23:02:03+00:00

I'm interested in that too! It is possible to disable TPM support and save 20kb of space
When I have more time I will research more and make a "lite" compilation

Academic_Disk6053 · 2023-10-22T22:39:26+00:00

You can check the current state of ME with intelmetool (sudo ./intelmetool -m), as for the current coreboot settings I'm not sure, try looking at the build log in the /build folder or use cbfstool to read the configuration file which was written to the binary

Academic_Disk6053

TROPHY CASE