- unlock ccd
ccd reset factory
- flash latest 2405.1 UEFI image
that’s all you’ll need to do
ccd reset factory
that’s all you’ll need to do
Hello again,
I have the SuzyQ now and have been trying to follow this link
I can successfully perform the command:
ls /dev/ttyUSB*
Which returns:
dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3
I can also perform the command:
echo “ccd open” | sudo tee -a /dev/ttyUSB0 > /dev/null
without any errors or results.
When attempting to flash the bricked device from the other linux device, I use this command:
sudo flashrom -p raiden_debug_spi:target=AP -i SI_BIOS -w stock-firmware-FROSTFLOW-20240703.rom
and what returns is:
Region requested (with -i “SI_BIOS”), but no layout data is available.
If I try only:
sudo flashrom -p raiden_debug_spi:target=AP -w stock-firmware-FROSTFLOW-20240703.rom
I get:
Raiden target: 2
libusb error: …/raiden_debug_spi.c:1588 LIBUSB_ERROR_PIPE
Raiden: Failed to enable SPI bridge
Error: Programmer initialization failed.
I must be missing something obvious, I’m just not sure what. My goal here is just to get it back to factory. Any help is appreciated, and thank you.
from the flashing device, open a terminal to /dev/ttyUSB1 and run the ccd open
command there, and verify it’s open. then run ccd reset factory
as needed on a Ti50 device.
Then flash the latest UEFI firmware, not the stock firmware, unless you’re wanting to go back to stock for some reason.
I think I’m having trouble navigating there. Would that be as simple as running:
cd /dev/ttyUSB1
Or something else? Running cd /dev/ttyUSB1 from a terminal is returning no such file or directory.
Figured out I should be using something like “screen” to check the USBs.
I did:
sudo apt install screen
and then ran:
screen /dev/ttyUSB0
and quickly did:
ccd open
which returned:
ccd opened
then tried:
ccd reset factory
and it returned:
Access Denied
This is all while it continuously cycles through statements like “Idle Erase”, “EC-COMM: disabled”, “EC-COMM: enabled”, “PinWeaver Init”, etc.
as for USB1, I entered it via:
screen /dev/ttyUSB1
USB1 terminal returned:
TI50 RESET
???
A question mark would be added every few seconds. I cannot enter commands under this USB.
After a few minutes, all USBs (0-3) will “terminate” and nothing new is written in the terminal.
Unplugging and replugging the USB cable will seemingly restart the process of cycling through statements for each USB*.
All this is foreign to me, so I’m pretty lost on what to try next. I’ve been reading through bits of this, but it’s a boat load of information and will need to spend more time digesting.
the internal battery should be disconnected here when running the CCD commands
Yes, unfortunately this was all while the battery was disconnected
Your message had me thinking…and I’m very silly. I was thinking I for sure needed power plugged into the Chromebook while the battery was disconnected.
I disconnected the charger and…flashing the firmware has started after opening the ccd and then factory resetting the ccd.
Can’t believe I was shooting myself in the foot like that, but thank you. Hopefully I’m towards the end of this journey.
I don’t get it. Are you saying GSC doesn’t require power, you can use CCD with no battery and AC power?
Yes, I guess so. I could not flash the chip with the SuzyQ cable until the battery was disconnected and the Chromebook was disconnected from the charger.
I’m no electrical engineer, but I’m guessing the flash chip is so low power that the SuzyQ cable + other Linux device provides the current. I’m sure that’s obvious for the vets here, but noobs like me aren’t flashing chips too often.
when using the CCD functionality, power to the GSC is provided via the USB cable.