Reading eeprom with CH341a / EZP2019+

[as4]

Hi there!

I just bricked my 5.0 2air when I tried to update it. I'm trying to read the eeprom, unpack it and save a signature file.

I have a modified CH341a to support 3.3v voltage, but I get different binaries every time I try to read it. I managed to unpack one of these binaries and even extracted a signature file, but it can be corrupted I guess.

Then I bought EZP2019, it reads about 3kb of data and then everything else are FFs. Also different every time, but the differences is only how much data it can read, but the data is stable itself.

I also tried to update using different flash drives with different images including the one Carlinkit sent to me, but no luck. It doesn't even try to update now - no more flashing red/green light - it just boots and then falls to green-yellow blinking mode.

Should I buy another CH341a? These are not the best choice I guess and it has to be modified for 3.3v.

I need to read the eeprom and save it before flashing anything.

[ninja-]

No I wouldn't put Ch341A anywhere close to C2A. I already burned 2 deviecs this way - for science purposes ;) even at 3.3v, it can easily fry C2A with reverse current once you disconnect it.

Unfortunately, a fried device is usually not distinguishable from a device with failed update due to all UART debugging being blocked.

Your best bet is POMONA SOIC clip + Raspberri PI 4B connected using scheme fotographed in this repo (sometimes the voltage is too unstable and ERASE command will get stuck, due to shitty voltage regulator of RPI, but for some reason it works if one of the pins is left floating, I don't remember which right now)

[as4]

So I guess I fried it? :(

[ninja-]

no if it's blinking it's alive. I don't remember the exact trigger for green-yellow blinking, it may be failure to start wifi/bt stack - or something else entirely