and without the doubles do you have the same problems?yes, i also have 2x resistors on dat0 and cmd
and without the doubles do you have the same problems?yes, i also have 2x resistors on dat0 and cmd
i dont knowand without the doubles do you have the same problems?
as a rule, even on the basic v1s there is always only 47 between cmd data and CLK and only in case of problems it doubles on cmd and data... try without doublesi dont know
with rp2040-zero usually with v1 I use
dat0 47+47
Cmd 47+47
CLK 47
as a rule, even on the basic v1s there is always only 47 between cmd data and CLK and only in case of problems it doubles on cmd and data... try without doubles
Very insightfull explanation.One thing worth mentioning is that this V1 has very slow boot times. Some things i would like to mention are that i do not have flux on the boards. Everything has been cleaned properly and put into solder mask(i tend to put a big amout of mask and then let it cure.From experience taking solder mask off, sometimes it does not cure all the way through since i put a lot in order to cover the joint properly,but i dont know if this could be the reason).The reason for these errors is usually some kind of signal interference on the dat0/cmd lines. The reason for using stronger resistance (100 ohm) is to reduce electrical noise from the rp2040, which sometimes solves these problems. Lowering the resistance will only increase the noise. Remember, the only task the rp2040 is supposed to perform happens before the switch boots. After that it should stay as silent as possible. As long as it is able to glitch, more resistance is better. I think the more likely culprit here is bad solder joints or too much flux residue still on the board. Time to clean things up with some isopropyl alcohol and a toothbrush.
What is it gonna help if u change the board if u have a MOSFET(or wire) issue?It would seem my RP2040-Zero has stopped working, the Switch (lite) keeps booting into OFW. Apparently that's a thing know. I'm getting the dreaded ==* error, but the MOSFET's are such a pain to get to that I'd rather try a different board first. I don't have a RP2040-Zero, but I have XIAO-RP2040 lying around. However, I think there might b an error in the guide. The board solder points for SDA and SCL are listed as 4 and 4, which are already occupied by D0 and CPU. Am I missing something? Also, is 2.75 proven or should I stick to 2.73 (I might have 2.74 on the Zero).
View attachment 398056
View attachment 398057
BTW, the SDA and SCL connected on the Zero; it doesn't seem to be helping (if ever) anymore.
Indeed, MOSFET issues is more likely, but replacing the board is much faster and easy. When researching the error I found few reports where replacing the board fixed it. I just wanted to point the error in the guide in case someone knows the correct solder points (if supported on the XIAO at all).What is it gonna help if u change the board if u have a MOSFET(or wire) issue?
The seed dia was made before the sda scl was ever a thing , maybe the pins have been changed after the sda scl update.
Yes 2.75 is stable otherwise it would've been taken down like 2.74.
I would say that the zero suddenly stopped working is not a thing now cause I installed way over a 100 and have not gotten any claims about a not working board. Eather u used a clone and thats where the issue is or your wire/mosefets have a issue.
So far no luck with the XIAO either, still getting ==*. The SDA and SCL wires are not connected though as I don't know the corresponding pins on the XIAO. Does anyone?Indeed, MOSFET issues is more likely, but replacing the board is much faster and easy. When researching the error I found few reports where replacing the board fixed it. I just wanted to point the error in the guide in case someone knows the correct solder points (if supported on the XIAO at all).
U have a issue with ur MOSFET.Indeed, MOSFET issues is more likely, but replacing the board is much faster and easy. When researching the error I found few reports where replacing the board fixed it. I just wanted to point the error in the guide in case someone knows the correct solder points (if supported on the XIAO at all).
Post automatically merged:
So far no luck with the XIAO either, still getting ==*. The SDA and SCL wires are not connected though as I don't know the corresponding pins on the XIAO. Does anyone?
Originally, when I installed the Waveshare board I was getting ==* until the SDA and SCL were connected. Would be nice to rule out the board completely before moving to the MOSFET's.
its hard to check for issues when you dont know what to look for. It s way easyer to narrow it down by changing component and ruling them out 1 by one. Its a bad process but its the best as a newbie. That is what i feel like.U have a issue with ur MOSFET.
How many MOSFETs do u have installed and what wire have u used?
According to the i2c post its pin 3 and 4.
I have never ran in to a case where sda scl was needed I guess u have bad soldering on ur MOSFETs that's why u need it.
Like I said check for the issue and don't just switch boards that's not how troubleshooting works
No u know where the issue lies most likely its the mosfets.its hard to check for issues when you dont know what to look for. It s way easyer to narrow it down by changing component and ruling them out 1 by one. Its a bad process but its the best as a newbie. That is what i feel like.
I've read the guide, it cant be pins 3 and 4; those are already used by CPU and D0 on XIAO.U have a issue with ur MOSFET.
How many MOSFETs do u have installed and what wire have u used?
According to the i2c post its pin 3 and 4.
I have never ran in to a case where sda scl was needed I guess u have bad soldering on ur MOSFETs that's why u need it.
Like I said check for the issue and don't just switch boards that's not how troubleshooting works
I've read the guide, it cant be pins 3 and 4; those are already used by CPU and D0 on XIAO.
I have one MOSFET, installed in this fashion:
View attachment 398205
I see the guide now also provides soldering points for the MOSFET on the back. What's the current preferred method?
Still 2 in front, or perhaps 1 front 1 back or 2 on back. Has anyone done 2 on back? Any caveats?
ive done 8 front mosfet installs. V1/V2/lite. I was using only 1 mosfet.
However now i have new batch of mosfets and these ones dont seem to work (i tryed 1x mosfet install on one console, it did not work, and i just abandoned this method. I did not try 2x mosfets).
give it a try.
i also agree that your problem is with mosfet.
What switch do u have?I've read the guide, it cant be pins 3 and 4; those are already used by CPU and D0 on XIAO.
I have one MOSFET, installed in this fashion:
View attachment 398205
I see the guide now also provides soldering points for the MOSFET on the back. What's the current preferred method?
Still 2 in front, or perhaps 1 front 1 back or 2 on back. Has anyone done 2 on back? Any caveats?
I have Switch Lite. Can the MOSFET be measured through the CPU wire? If I end up replacing it and it turns out it's the cause it could be useful information for future troubleshooting.What switch do u have?
Then its no wonder ur having issues.
Use 2 MOSFETs in the front and be done with it that's why ur probably having issues.
Or try if the one MOSFET in the back works for u without Sda/Scl
Broo... you NEED 2 MOSFETS on apu on lite and V2. This information is in the guide. That is why you re having problems.I have Switch Lite. Can the MOSFET be measured through the CPU wire? If I end up replacing it and it turns out it's the cause it could be useful information for future troubleshooting.
Thanks, I don't see where it says that. I'll try adding one more transistor on the back and go from there.Broo... you NEED 2 MOSFETS on apu on lite and V2. This information is in the guide. That is why you re having problems.
I had about thirty original sx-core Flex v1s aside. I've used them all on OLED, lite, mariko without any problems.Broo... you NEED 2 MOSFETS on apu on lite and V2. This information is in the guide. That is why you re having problems.