![]() ![]() If motivation is research, then go for it, but be prepared for some late nights. ![]() ![]() If the goal is to try and fix electrical issues to recover from the drive itself without de-soldering NAND, i believe much time would be used up compared to regular NAND off recovery. If that was the case, and the NAND chip is toast(Ive never seen any firmware upgrades available for NAND Chips) then continuing with recovery wouldnt be of any use. I wonder if it's even possible to read the NAND flash in "raw" mode in this state. If so, then placing the controller in BootROM mode by shorting a link or by invalidating the NAND during power-up should enable the controller to identify itself via USB, thus eliminating it and the USB interface as suspects. I'm wondering whether there are times when the NAND firmware becomes corrupt so that the controller remains busy. This can be achieved in several ways:ġ.Use host/go_isp.py script to reboot PS2303 from normal mode to BootROM (simplest, temporary)Ģ.Disrupt NAND probing at power up shorting some DATA lines with tweezers (temporary) fast USB 3.0 to FPGA bridge).Ī PS2303-based USB stick must be in BootROM mode to be able to load and run custom code. This project's goal is to turn PS2303-based USB flash drive into a cheap USB 3.0 development platform (i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |