Device: robo360
I tried running this command from MrChromebox’s docs:
sudo flashrom -p raiden_debug_spi:target=AP -w <filename> --ifd -i bios
And it fails with this error:
❯ sudo flashrom -p raiden_debug_spi:target=ap -w coreboot_edk2-robo360-mrchromebox_20240914.rom --ifd -i bios
flashrom v1.3.0 on Linux 6.6.71 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Raiden target: 2
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
I tried with NixOS and Debian, both had the same result. CCD is opened (I did ccd reset factory before, and even running the ccd open results in the same error).
Every time I run the flashrom command, the Chromebook reboots.
The Chromebook does turn on, but besides pressing escape or arrow down the enter the boot menu at the beginning, it doesn’t let me press any keys. It used to default boot into Ventoy, which let me use the keys and boot into an OS, but now it just goes into the UEFI shell. In the UEFI shell it constantly spams a strange looking character continuously even though no keys are pressed, and doesn’t let me type anything.
The firmware that I last flashed on it is a custom built firmware based on GitHub - MrChromebox/coreboot at 6ca7ebe1192fe58e0630792c735d627335cf6b04 with make options
CONFIG_CONSOLE_SERIAL=y
CONFIG_EDK2_SERIAL_SUPPORT=y
I want to enable serial output through CCD so that I can debug a custom OS that I’m making. Idk why this firmware is messed up, I don’t think it would be because of the option I changed, maybe the latest commits are causing this. I could test it out without any changes to options, if I got the flash to work.