Can we get the sizes for these so when using PCBWAY we can input correct size, re: xmm - xmm
Can we get the sizes for these so when using PCBWAY we can input correct size, re: xmm - xmm
The flex-pcb was meaning.
I put 4 flex cables in the same fileThe flex-pcb was meaning.
When you look for jlcpcb to make, you can put it together like a puzzleThe flex-pcb was meaning.
"simpler" seems relative. People already struggle with just getting the three pads on the single mosfet correct, now you want them to get two separate PAIRS of three pads right and not mixed up?Is there any reason people aren't using dual MOSFETs like DMT3009UDT-7 or QH8KA4TCR ?
Seems like a simpler option.
Post automatically merged:
Is there any reason people aren't using dual MOSFETs like DMT3009UDT-7 or QH8KA4TCR ?
Seems like a simpler option.
I get what you're saying. Electronics experience aside, it just seems like a whole lot less fiddling around."simpler" seems relative. People already struggle with just getting the three pads on the single mosfet correct, now you want them to get two separate PAIRS of three pads right and not mixed up?
I do agree though, it could make for a much cleaner install as opposed to double mosfet installs.
Where can I find the file for the flex cables?I put 4 flex cables in the same file
Post automatically merged:
When you look for jlcpcb to make, you can put it together like a puzzle
View attachment 369058
like this
https://github.com/SQc04/PICOFLY-XWhere can I find the file for the flex cables?
No no, just greenCan i fit v2 Flex Cable on v1 nintendo switch?????
The yelow line is wier also???
Raspberry pi pico not supported?Latest firmware here
ChangeLog:
v2.0 + Active MMC communication
v2.1 + Toshiba support
v2.2 + Fix Toshiba boot fail
v2.3 + SanDisk support
v2.4 + Faster Toshiba boot
v2.5 + fix OFW boot
v2.6 + software update, xiao & itsy support
v2.61 + Instinct-NX sdloader, bug fixes
v2.62 + Make 16.0.1 happy (fix OFW boot)
v2.63 + roll back some 2.62 boot speed tricks
v2.64 + enable back the board detection
v2.65 + RP Pico support, double reset removed
v2.66 + Bypass to OFW after update for proper fuse burning
v2.67 + Don't bypass to OFW on first install
must be RED after USB write. if you see green, set "RGB mode" jumper
WHITE = eMMC write
BLUE = glitch
PURPLE = eMMC boot failure, check CMD / CLK
PINK = NS eMMC init fails, inoperative eMMC ?
YELLOW = eMMC write failure, check D0 / unsupported eMMC
CYAN = no reaction to glitch, check mosfet wire
GREEN = success
Q: What is supported?
A: Erista (v1), Mariko (v2, Lite, OLED)
Q: eMMC types support?
A: Tested on Hynix, Samsung, Toshiba, SanDisk
Q: rp2040 boards support
A: WaveShare 2040-zero/one, xiao-rp2040, adafruit itsybitsy (Pi Pico is not supported for now)
Q: GREEN, but instant reset
A: Clean flux near the RST point
Q: Do I really need 47 Ohm resistors?
A: You can skip them, however in this case you will have to use emuMMC due to the line interference, sysNAND would not boot (sysNAND data can be damaged).
Q: Does the firmware has learning? How to reset statistics
A: Short pin 0 to either 1 or GND during start for chip reset. The statistics is collected each boot. The more you start it - the better it boots.
Q: open source?
A: no
Q: why you made it?
A: to prove it possible!
Q: run Atmosphere?
A: no piracy
v2.5 firmware had a bug with BOOT0 corruption. To recover it:
- boot "Full Stock" using hekate
- update to the latest official firmware over Wi-Fi
- boot "Full Stock" using hekate
- perform a full system reset
- show firmware information
- update firmware from SD card (place update.bin into the root folder)
- rollback to the backup firmware slot
- reset learning statistics
- dump / write sdloader
if you have an rp2040-zero from waveshare/ali then it has a neopixel. It is used for diagnosing proper firmware flashes as well as console glitching. If you plug it in, and flash the uf2 firmware to it and immediately see a red light after flashing (this is not the same as flashing, then unplugging and replugging), then no rgb jumper needs to be made. If on the other hand, you get one quick green flashing light, then you need to bridge the jumper pads indicated to swap the LED colors for proper diagnoses capability.
Had the same idea. I ordered some 150n03ld (sop8, easier to test) a couple of weeks ago, still waiting on them.Is there any reason people aren't using dual MOSFETs like DMT3009UDT-7 or QH8KA4TCR ?
Seems like a simpler option.
Post automatically merged:
Is there any reason people aren't using dual MOSFETs like DMT3009UDT-7 or QH8KA4TCR ?
Seems like a simpler option.
In pico fly chip if you add firmware to it and want update it to 2.67 is that well damge it brick from pc????Had the same idea. I ordered some 150n03ld (sop8, easier to test) a couple of weeks ago, still waiting on them.
I think the firmware writes the same sectors so it should not be a problem. Just press and hold Boot, connect to PC and drop the firmware file again.In pico fly chip if you add firmware to it and want update it to 2.67 is that well damge it brick from pc????
How can know if there firmware pico fly inside it????
The LED after add 2.67 firmware it show blue to white blue blinking.I think the firmware writes the same sectors so it should not be a problem. Just press and hold Boot, connect to PC and drop the firmware file again.
Or you can clean the flash memory by flashing the attached file (remove .pdf extension) and start from scratch.
Thats how it supposed to be, Blue-glitching, White-writing.The LED after add 2.67 firmware it show blue to white blue blinking.
When i conect to PC it do same led...Thats how it supposed to be, Blue-glitching, White-writing.
what happes afterward? Does it boot? Any other color?
Blue lite white blue blinkingWhen i conect to PC it do same led...
Hold the Boot button and connect the Pico to PC then drop the flash_nuke.uf2 file.When i conect to PC it do same led...
Im ready add firmware to the chip... But still not soldring to v1 nintendo switch.. It well blinking blue lite to white blue then green.Hold the Boot button and connect the Pico to PC then drop the flash_nuke.uf2 file.
Disconnect the Pico then connect it again then flash the 2.67.
If this does not work you may have a bad rp2040 unit.