PSGroove USB Boards and DIY Teensy Schematics Detailed

[ramx2]

You will probably have to use the Amtel FLIP programming application if you build a Teensy clone, not the usual Teensy-specific flashing application, since the bootloader on shipping Teensy boards is HalfChip, which I believe is different than the one shipping on Amtel chips by default. Could be wrong. Shouldn't be that big an issue either way. Once someone builds one of these things, please let us know.

You are right it's already documented here in pjrc datasheet page:

Atmel's Official Page
The Official Atmel Page provides this datasheet and other information. However, most of their code is NOT compatible with GCC (it only works with expensive commercial compilers).

Atmel uses a different bootloader called "DFU", which is different from HalfKay on the Teensy. DFU takes 4K of the 16K flash memory, whereas HalfKay uses only 0.5K! Atmel's FLIP tool only works with DFU. You need to use the Teensy Loader with Teensy boards that have HalfKay

What can we do about that?

[imtoodvs]

lol, this is getting out of hand. right now i'm looking into the blackcatusb move. if the psp port works, then sony's gonna have a great 4th quarter.

[drhuman]

Can someone help me find the right kind of crystal for this? I've sourced everything else, just not sure about the oscillator.

The crystal your after is a 16mhz

http://www.maplin.co.uk/Module.aspx?ModuleNo=31822&OrderCode=RR89W

[jimmyo88]

Heya guys, it seems like theres going to be a massive shortage for the teensy boards or anything similar. I was just wondering, as we know how the boards are made, and the components required, is there anyone here willing to create them or a similar for the masses??

Obviously, there would have to be some profit involved for the people who work on this and they would also be helping a lot off people get on the road of ps3 Hacking.

Maybe some trusted people could work together on developing these boards and make a nice profit for themselves. I would definetly be one of your first customers.

[simonb0987]

Does anyone know where to get one of these boards in the uk?

[jd200]

Does anyone know where to get one of these boards in the uk?

everything seems to be out of stock in uk so just have to wait see what else comes out thats usefull was hoping for psp way

i have a Willem EPROM/EEPROM Programmer but dont know if this will be handy for anything

[joysei]

Finally receive the order of the Teensy++ 2.0

Test result:
1. Install manager.pkg under "*Install Package Files" ------ work
2. Backup PS3 games to both internal/external hardisk ------ work
3. Cannot play the games ------ not working
- the games icon doesnt appear
- "*/app_home/PS3_GAME*" appear, and giving an error message if try to
execute it.
"An error occurred during the start operation (80028F14)"

note: a. Using the "motor storm" for testing which is proven to be work at
normal PS JailBreak.
b. using the HEX file "TEENSY++2.0-psgroovecjpc.hex" with crc32=3250287A

seems there are some problem with the HEX code. Anyone has proven Teensy++2.0 was working b4?

[ramx2]

We need to know which pcbs are working now we know the USBCAT works and teensy++2 needs some work out on the hex, anyone else guys?? Come on we need to know the working hardware!!!

Regards

[Alibaba123]

Finally receive the order of the Teensy++ 2.0

Test result:
1. Install manager.pkg under "*Install Package Files" ------ work
2. Backup PS3 games to both internal/external hardisk ------ work
3. Cannot play the games ------ not working
- the games icon doesnt appear
- "*/app_home/PS3_GAME*" appear, and giving an error message if try to
execute it.
"An error occurred during the start operation (80028F14)"

note: a. Using the "motor storm" for testing which is proven to be work at
normal PS JailBreak.
b. using the HEX file "TEENSY++2.0-psgroovecjpc.hex" with crc32=3250287A

seems there are some problem with the HEX code. Anyone has proven Teensy++2.0 was working b4?

Did you used the patched PSGroove?

[twiggs462]

Searching around online I found this:

The backup manager code is still there, but disabled in the code.

Changing 0×78, 0×78, 0×78, 0×78 for 0×62, 0×64, 0×76, 0×64 in descriptor.h will reactivate it.