PS3 CECHB01 Teensy troubles

[RCWD21]

Ok the people probably replying to this are already aware of the background of my particular console so to sum it up I have a teensy soldered to both nand chips on the motherboard with 3.3v being supplied to the teensy from a regulated ps3 power supply (5v down to 3.3v, regulator is rated up to 3amp and is about the size of a dime)

I have pyps3tools master zip, ps3 nand flasher 4.0, the NORway master zip, flow rebuilder 5.2, pyps3checker standalone, and a folder ready to receive any dumps I get from the motherboard.

I also have littlebalup's WAY-launchers v2.04 but I cant download v2.05 because windows flags it saying it has a virus even when downloaded from the main github file.

I can run WAY-launcher v2.04 perfectly fine but when I run the info command it gives me "Teensy not found. Command aborted"

The teensy itself can be programmed with the dual nand hey file a d responds to the reset button when using the teensy.exe program to load files to it.

As for the teensy, when I try to run the serial_install.exe file for the virtual com ports it either gives me a blank error or it says windows already has that driver installed. I have no idea if thats needed for windows or if thats strictly Linux but I figured I'd mention it anyways. Ive read that the teensy uses a different usb protocol or something so it won't show in the Ports sub directory in device manager.


I have python 3.9.5 installed on my laptop along with pyserial and pycryptodome if thats needed although I'm not very good at it.

TL;DR I have the teensy wired to the nand chips and powered. My pc allows me to communicate with the teensy and load the needed hex file. I can run the v2.04 way launcher for windows but I get the error Teensy not found"


I think that's everything [emoji848]

Sent from my SM-G965U using Tapatalk

 

[RCWD21]

Tiny little update. I followed the steps outlined on pjrc where I purchased my teensy from and still no luck.

The only change is I uninstalled the "unknown device" and reinstalled it. Now the serial_install.exe is giving me the message that "Windows 10 USB Serial Device driver is present. No installation is necessary."

Sent from my SM-G965U using Tapatalk

 

[vyktormvmpay25]

Ok what voltage do you see on vcc pin beside USB port (on teensy pcb) while you are connected on pc?
It may be Windows wrong version, but not sure, I never used to work with windows 10, try removing signature certificate for driver. Or go on any windows 7.It is an old driver for teensy probably that why not working.
Anyway python version 2.7 and pyserial 2.5 should be installed on your computer in order to see in way launch. Not really on those way lunch automatically run, run scrip.py in a dos window should work well if all drivers are correctly working.
Script.py is a reference on any python files that you find in your case should be nandway.py
On teensy pcb you should have 3v3 when power external power supply, or in your case with that vreg it should be 3v3 on that vcc point while only teensy on usb without any wires soldered on ps3 motherboard . I will suggest you remove wires from teensy to ps3 board and focus to get teensy recognised as virtual port com on device manager. Dual nand never worked for me, I suggest using only one nand with single files and set teensy later for single nand.

 

[sandungas]

As far i remember it needs to be python v2.7 (not newer), so i would start by uninstalling python v3.9.5 and installing v2.7

The teensy should be shown in the windows "device manager", if is not shown or is shown as unknown it means you dont have the correct drivers installed
Also, remember the teensy have 2 different "boot modes" (that depends of the "pressed state" of the teensy button), and as far i remember windows "device manager" should display them as 2 different devices. In one of the modes is where you should program the teensy with the bootloader... and the other mode is where you should program the teensy with the "nandway dual nand" version

Also, i suggest to dont use the way launchers by now, thats something handy after you have everything working... but by now for an initial setup and checks i think is better to stay with the basic python script

Btw... when you run the script for first time it should display a welcome text with something like "NANDway made by judges" or something like that, as far i remember this mesasge comes from the teensy, so is an indication that you have the software/s in the teensy installed correctly

 

[vyktormvmpay25]

If you push that tiny button on teensy it should let you write the hex, then disconnect/connect usb and see what driver you see on device manager.

 

[RCWD21]

Ok so what I've done is completely remove the teensy and re-bridge the 5v pad so it can be powered via the USB lead.

When you plug it into the computer you get the little sound windows gives you when a USB device gets plugged in.

Under device manager it now shows as USB Device Com 3. The little led is on though faint. I may have accidentally tagged it with the soldering iron earlier but it does still work.

It says it is driver version 10.0.19041.906, driver date 6/21/2006. Hitting update only gives me the message that the best driver is already installed.

I can open Teensy.exe and hit the reset button and the program recognizes that there's a teensy present and waiting to be programmed.

After hitting the reset button on the teensy, in device manager com port 3 is no longer showing up under ports. It doesn't show up at all actually.

If I go back into the NORway master zip and try to install the serial driver to be able to use the teensy I once again get the message "An error occurred while installing the INF file. Windows SetupCopyOEMInf error was ""

I'm running it as administrator so that shouldn't even be an issue.



Sent from my SM-G965U using Tapatalk

 

[vyktormvmpay25]

Yes I have that error in Windows 10. Did not work for me, most programs are complete compatible with Windows 7.
It's a patch /update on Windows 10 and didn't work as much as I've been trying.

 

[RIP-Felix]

Did you ever figure this out? I'm going back over the syscon thread recording results in a spreadsheet. I'm curious if you ever did confirm this was a botched FW update?