This is the new error " ==* CPU always reach BCT check (no glitch reaction, check mosfet) "
Check the sp1 and sp2 also the mosfet if you are not using flex pcbThis is the new error " ==* CPU always reach BCT check (no glitch reaction, check mosfet) "
Good to hear its working back.I change the flex and it working.... i think a bad mofset on the flex
Did you find them?? I'm also looking for sda/scl on v1
Post automatically merged:
Were you able to find them??
Last edited by Myst0gan,
Ok @QuiTim i see why you might be laughing after doing some research
I wasn’t able to find the gerber files though. I did find the GitHub page.
Post automatically merged:
It’s been a long long time since I’ve had to do those. You shouldn’t need them if everything is done properly honestly. What method are you using?
Yep, you got meOk @QuiTim i see why you might be laughing after doing some research
Post automatically merged:
It’s been a long long time since I’ve had to do those. You shouldn’t need them if everything is done properly honestly. What method are you using?
, but I figured it out. Here you go:Attachments
It's the only thing left to try, since I keep getting the same error, **/== either rst missing or clk not connected, I have checked the joints, wire, changed the wire from rst to a thinner one, cleaned up the flux, removed capton tape, tried with another rp2040... Nothing changed.Ok @QuiTim i see why you might be laughing after doing some research
Post automatically merged:
It’s been a long long time since I’ve had to do those. You shouldn’t need them if everything is done properly honestly. What method are you using?
Sda/scl is the only option left
Impossible you got the == CLK is not connected
There is none in the source code throws that error.
I think the note is not update. CMIIW.
The detection of voltage only happened on RST, CMD and Dat0, hence the errors.
https://github.com/rehius/usk/blob/6530fd9fe58980ea03d47905bad5e871b9439b7a/main.c#L54
It might be, if you use the very old firmware.
Because there is some commentary on the source code about that.
I guess it did check in the previous firmware, but in current source code, theres none.
And about the ** RST not connected. It might be false positive scenario.
RST is the first detection on voltage.
So theres possibility that your power inject to the 3.3V line of picofly are not 3.3V,
such that the value calculated on RST line got wrong.
Or the 3.3V voltage correct, but the picofly buggy / broken.
Such that its read the RST line wrongly.
Or the RST line voltage from the mainboard, give a wrong voltage.
In this scenario, the mainboard (emmc / cpu) is problematic.
The firmware detect if the RST should be around 1.8V +-0.2V.
Outside this range, it will throws **
V1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.Impossible you got the == CLK is not connected
There is none in the source code throws that error.
I think the note is not update. CMIIW.
The detection of voltage only happened on RST, CMD and Dat0, hence the errors.
https://github.com/rehius/usk/blob/6530fd9fe58980ea03d47905bad5e871b9439b7a/main.c#L54
It might be, if you use the very old firmware.
Because there is some commentary on the source code about that.
I guess it did check in the previous firmware, but in current source code, theres none.
And about the ** RST not connected. It might be false positive scenario.
RST is the first detection on voltage.
So theres possibility that your power inject to the 3.3V line of picofly are not 3.3V,
such that the value calculated on RST line got wrong.
Or the 3.3V voltage correct, but the picofly buggy / broken.
Such that its read the RST line wrongly.
Or the RST line voltage from the mainboard, give a wrong voltage.
In this scenario, the mainboard (emmc / cpu) is problematic.
The firmware detect if the RST should be around 1.8V +-0.2V.
Outside this range, it will throws **
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch function, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
Last edited by Myst0gan,
No it's a oledV1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch funktion, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
I don't know about the other stuff but the 3v3 from emmc board is safe to use, I have used it multiple times and other people here did the same. It might be some freak coincidence but rest assured that whatever the problem is it did not start from thereV1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch funktion, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
Im using the 3.3v from the nand. Never had issue with it, already modded 8nos of v1/v2 with that setup.V1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch funktion, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
The only thing I take from the board was ground and the cpu, the rest on nand. Your case is different for sure. Maybe you bridge something else.
If i remember, we could simply just check the voltage on rst using multimeter.V1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch funktion, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
If its around 1.8V +- 0.2V then the problem lay on broken picoboard or wrong voltage in 3.3V line.
3.3V from nand is okay.
you can do it on nand or onboard for your liking. for me all my points are on board because i'm too lazy to lift up the nand. less work more efficiency.V1?? If yes, look at the resistor near the rst pads
Post automatically merged:
I can't code, so just looked up the error codes on the guide, since I can't figure out if the blinking is short or long, I got only those two error options. I'm using the 2.75.
If I knew that not 3.3V can cause all that problems, then I wouldn't have all these stress. I fucked up both of the rst pads including the resistor for the Touch funktion, now I need to find a way to keep the console alive
I took 3.3V from nand, I guess it's not optimal point.
Post your work. I have a v1 here I need to do and I’ll post my work as well. Are you using a flex cable or mosfets?
Post automatically merged:
I saw this one as well but there are no gerber files
Last edited by BlueBeans,
Hi, what do you mean by THIS firmware?
I went to the first post of this thread but couldn't find any attachments?
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
@
BigOnYa:
@SylverReZ I've never used a disposable, seems like a waste. kinda cool idea tho. It would be nice to have vape built in to a cell phone even. "The iVape"+1 -
-
-
-
-
-
@
K3Nv2:
I was hoping I could add a custom ROM to this fire HD 10 tablet but guess no one's made twrp available -
-
-
-
-
-
-
-
-
-
-
-
-
