You can always use the $1 SD shield which automatically converts the 5V to 3.3V....
Arduino has 5V gpio voltage levels which is 2 high for interfacing an eMMC.
...
You can always use the $1 SD shield which automatically converts the 5V to 3.3V....
Arduino has 5V gpio voltage levels which is 2 high for interfacing an eMMC.
...
We already know how to restore the NAND (with sd card reader), so I think that it would be posible to tell the controller to erase the NAND, unlock it and then flash the nand back with a sd card reader.If they really locked the eMMC you will need the passkey to unlock it without erasure of it's contents
or you will need a working nand backup and a method to restore it.
An arduino can talk to the eMMC in both modes as basically every gpio pin of it can be set as input or output and can be set high or low.
The arduino microcontroller only has hardware support for the SPI protocol.
This means that all other communication has to be emulated in software which is usually much slower than a dedicated hardware interface for the same purpose.
Arduino has 5V gpio voltage levels which is 2 high for interfacing an eMMC.
The raspberry uses 3V3 gpio voltage levels which might be what is needed?
The problem is finding (writing) the needed software to communicate with the eMMC at a level that shows us what is going on. Being able to read it's registers would already help a lot as some status bits might indicate the condition of the eMMC chip.
We already know how to restore the NAND (with sd card reader), so I think that it would be posible to tell the controller to erase the NAND, unlock it and then flash the nand back with a sd card reader.
I don't assume you have a link to those datasheets?
All I could find until now were more commercial leaflets.
Please don't tell me google is my friend. He let me down when I searched for the eMMC chip datasheets.
Instead of donating it, you could try getting a cheap mmc card and communicate with it using SPI, and if that works then it should be easy to send any commands to the controller directly.
That datasheet is about the Trace 32 JTAG debugger. It just describes how the device can be used to interface an eMMC.
It probably won't tell the voltage levels used in the 3ds for eMMC interfacing either?
The best way to figure out will likely be measuring the voltage on the eMMC interface lines, as the eMMC can be interfaced with 2 different voltages.
Its posible to use 2.7v-3.6v without problems, from what I remember first the CMD0 (reset) is send using 3.6v then after the card answers with IDLE the host can switch the data lines to 1.70v-1.95v while keeping the power lines on 3.6vPower : Interface power → VDD (1.70V ~ 1.95V or 2.7V ~ 3.6V) , Memory power → VDDF(2.7V ~ 3.6V)
I have arduino uno,AT Mega and raspberry model B.Just don't have a bricked 3ds.Anyone willing to donate a bricked 3ds?
Do you know how to connect an SD card to it ? Because first we should test it with a card, write a program which can erase it and then try it on a bricked 3DS. Then if it works, unbricking consoles will be super easy, it would be posible to even make a small unbricker device what can be used by those who have no programming knowledge (and it would be super cheap)
Haven't done that but I can try.If a shell is needed then I need to order online.Any recomended library to use?