Hacking 3DS unbricking progress
- Thread starter krisztian1997
- Start date
- Views 349,406
- Replies 1,233
- Likes 32
Be careful with that. ( Besides that you have to lower the pull up )
What you do in this case is very dangerous when you are using a resistordevider
Without load The Voltage will be to high. ( Your emmc may be fried).
So that's why a levelshifter / buffer is still preferred.
If my uno arrives today i will in the evening report voltages and everything from using sn74lvc245
Has someone considered the fact that the CLK signal is an output from the 3DS to the eMMC?
Bidirectional lines like the DAT0 are normally driven by open collector or open drain signals.
This means that the line has a pullup resistor to 3V3 and is pulled to GND by the device that wants that line to become low.
While the eMMC standard accepts multiple eMMC devices on the same bus, the 3ds likely isn't expecting something else taking over control of the eMMC interface.
So, basically, in normal operating conditions, the 3ds is controlling the lines. What happens if the 3ds can't access the eMMC? Will it turn of it's clock signal?
If you measure 2.xV on the clk signal, it's probably an average of the signal being switched between high and low. And as you aren't switching it, it's likely the 3ds doing it.
Most digital circuits that are not open collector or open drain survive when their outputs is pulled to gnd. They don't survive when there output is pulled or forced to 3V3.
So basically, we need to find out how we can stop the 3ds from generating the eMMC clk signals. When this condition is met, we should measure 3V3 on the clk signal (If our arduino interface drives it high as well) It wouldn't suprise me that forcing one of the other CMD or DAT0 lines low will disable the 3ds to eMMC communication (blue screen with error code) No idea if that turns off the 3ds clk generation. To proper see the condition of the clk signal, you will need an oscilloscope or a logic probe. You can even use the arduino bord to probe that signal. If you sample it several lines, and you measure high as well as low, it's likely constantly changing between high and low.
Also note that it could make a difference if you allow the 3ds to initialise the eMMC (only connect your interface after the 3ds was turned on) or if you don't allow it (connect your interface and turn it on before the 3ds)
Even if your interface is connected before the 3ds is turned on, it shouldn't influence the 3ds operation if all your interface lines are in the high state.
If you don't understand what I am writing here, you are experimenting on a dangerous level.
In that case I would suggest you use the raspberry pi as it has proven to work.
If you are trying to learn something and don't mind frying your 3ds, ignore previous sentence.
Bidirectional lines like the DAT0 are normally driven by open collector or open drain signals.
This means that the line has a pullup resistor to 3V3 and is pulled to GND by the device that wants that line to become low.
While the eMMC standard accepts multiple eMMC devices on the same bus, the 3ds likely isn't expecting something else taking over control of the eMMC interface.
So, basically, in normal operating conditions, the 3ds is controlling the lines. What happens if the 3ds can't access the eMMC? Will it turn of it's clock signal?
If you measure 2.xV on the clk signal, it's probably an average of the signal being switched between high and low. And as you aren't switching it, it's likely the 3ds doing it.
Most digital circuits that are not open collector or open drain survive when their outputs is pulled to gnd. They don't survive when there output is pulled or forced to 3V3.
So basically, we need to find out how we can stop the 3ds from generating the eMMC clk signals. When this condition is met, we should measure 3V3 on the clk signal (If our arduino interface drives it high as well) It wouldn't suprise me that forcing one of the other CMD or DAT0 lines low will disable the 3ds to eMMC communication (blue screen with error code) No idea if that turns off the 3ds clk generation. To proper see the condition of the clk signal, you will need an oscilloscope or a logic probe. You can even use the arduino bord to probe that signal. If you sample it several lines, and you measure high as well as low, it's likely constantly changing between high and low.
Also note that it could make a difference if you allow the 3ds to initialise the eMMC (only connect your interface after the 3ds was turned on) or if you don't allow it (connect your interface and turn it on before the 3ds)
Even if your interface is connected before the 3ds is turned on, it shouldn't influence the 3ds operation if all your interface lines are in the high state.
If you don't understand what I am writing here, you are experimenting on a dangerous level.
In that case I would suggest you use the raspberry pi as it has proven to work.
If you are trying to learn something and don't mind frying your 3ds, ignore previous sentence.
Hmmm... Got some thing i have try now... Think my 10Mhz oscilloscope is enough? I disslike it xD want a better one lol.
But i have onebidea that acctually may work. Gonna test before i say more IF its a bad idea
Also i got it to work with the duemillanove before i fried it from a stupid misstake from a project... But never got so far to hook it to the 3ds
But i have onebidea that acctually may work. Gonna test before i say more IF its a bad idea
Also i got it to work with the duemillanove before i fried it from a stupid misstake from a project... But never got so far to hook it to the 3ds
ok I understand, So to prefend the 3ds for the risk of frieing up we have to isolate the clk-signal from the 3ds.
Thanks for stating out this important point! I too was suspecting something that the console is creating the problem, but was not sure what is causing it,since the 3ds must be powered on to supply voltage to the emmc unlike the sd cards which obtain voltage from arduino.I was thinking of the possibility of providing external source to the emmc without the 3ds...
You can hook the clock to the analog pin of your arduino too,just declare the pin as input,do an analog read,divide the value with 1023 and times with 5v,then print it on serial monitor
Ohh, its perfect that you got an oscilloscope, can you test the clock line while the 3ds is on and not connected to arduino, measure the arduino clock without the 3DS connected to it and then measure the 3ds clock when its connected to arduino and both of them are on.
isolating it might be difficult as for that you might need to cut a trace.
I assume there are methods to stop the 3ds clock signal in a high state somehow, as people can backup and restore their 3ds eMMC with an sd card reader.
They also can unlock and force erase it with a raspberry pi. I haven't heared of anyone frying his 3ds, but lowering the pullup resistors is a very bad idea as it increases the current needed to pull the line low.
Basically, 2 things need to be tested.
1. Finding a method to stop the 3ds clk signal and having that line in a high state. This can be checked by measuring it's voltage. It should be above 3.1V
2. Pulling such a frozen clock signal to gnd and measuring the current that is needed to do this.
If it's only a few hunderd microamps or even less, it's driven by an open drain on the 3ds as well and there is no danger in driving it with an additional open drain as well.
If it's several milliamps, it's driven with a logic gate. In such case it's hard to tell if it's 100% safe to drive the signal with external hardware without first isolating it.
The 3ds will probably be case 1. Even than, you should only pull the signals to gnd.
The resistor voltage divider gives a protection, as the maximum possible currents are limited by the resistors.
A (non open drain or open collector) buffer chip can easily drive several milli amps. This currents could be dangerous for the 3ds chip that controls the eMMC.
I can understand that most of you can deal with the software site of things, but have problems with the hardware.
It doesn't mean that correct interfacing the hardware is unimportant for a proper result (every time and reliable)
While experimenting with software usually isn't harmfull, the same can not be said about the hardware way of doing things.
Will do.
Number one is one if the ideas i got. Resolder a cut trace is no problem. I am Used to solder smds under a microscope :-P
wouldn't it work if the arduino was powering the nand instead of the 3ds battery? shouldn't be too hard to find a power pin for the nand no? There would be no need to turn on the 3ds, or for that we need more wires or something (besides the power wire ofc)?
The points i marked in red is the power for the nand right?
The points i marked in red is the power for the nand right?
I think that the problem is that the two devices are not synced while turning on... the arduino takes some time to boot up and untill it gets ready, the 3ds is already initialized with a different clock, and if the 3ds is plugged in after the arduino is initialized, its too late because the arduino thinks that its imposible to initialize the card and stops the execution of the code.
Edit: anyone willing to test my code now ? I added a super basic and ugly hot plug support, plug in a normal SD card first to initialize the arduino so there is a clock on CLK line, unplug the sd card, plug in the 3ds, wait around 5-6 seconds, then press i to reinitialize. If it doesnt works on first try, retry it 1-2 more times... I had succes with some card, but some failed to initialize when hot plugging.
Great! I finally got my Uno today ^^
first thing first just hook a SD card to test. Will shout in a little while when i've tested on the 3DS
first thing first just hook a SD card to test. Will shout in a little while when i've tested on the 3DS
don't want to rain on your parade, but
doesn't look all that good to me.
Code:
Reset command sent on MOSI, but no answer from the slave. Please check your card connection/soldering
ReadCardStatus = 11111111,11111111Looks like it failed to initialize the 3ds for some reasons (you hotswapped like how I said, right ?). Try it again 2-3 more times and maybe its gonna work...
Awesome, please test it on an oscilloscope if it fails to work, to see if the clock line is fine
- No one is chatting at the moment.
-
-
-
@
Xdqwerty:
Is it safe to update a modded ps3?
Can I play online in pirated games? (with ps3hen either enabled or not) -
-
-
-
-
-
@
Xdqwerty:
@salazarcosplay, I used apollo save tool to activate my ps3 offline so i could play a game that wasnt working
-
S @ salazarcosplay:from what I understood. you load up the piratged game. you the clear the syscalls, then you play
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
