[nortnil]

Originally Posted by judges I had the same issue that console didn't power off after update. Never cared about it since it was working just fine. But actually this usually indicates that there was an update error (check the end of the log file created by lv2diag.self). If the log ends with "manufacturing updating FAILURE (0x8002f057)" right after updating BD firmware, you have 2 options to fix it: use a PS3UPDAT.PUP with noBD patch (e.g. Rogero 3.1), this will get rid of the update error. Or disconnect teensy's (or any other flasher's) control lines (or teensy/other flasher entirely) from console. This is also supposed to fix the update problem, since in rare cases on some consoles a connected flasher causes this. Although I've never tried that latter option myself.

Thank you, I didn't know that. I bet my error was caused by my blue-ray drive cable not being properly seated. I didn't notice the problem until i had fully flashed to a CFW. I will have to track down that log file and see.

[DiabolicGod]

So, it turns out that the issue was the PSP. I followed nortnil advice, and used judges psgrade code for teensy and once I finished flashing the PS3 with the downgrade.bin, and did the "power+eject" trick, it did everything it should...turned off after a few seconds, and bam, it was in service factory mode.

So basically yeh, everything was fine the first attempt I had at it, the only real issue was really the PSP not being able to put the PS3 into service factory mode...but teensy solved it!

And after that was all straightforward..

One quick question..anyone knows if there is a work in progress for the KTE-001 motherboard?

Thanks for the help guys, couldn't have done it with out ya!

Ho and by the way nortnil, they worked just fine...thank you once again!
And judges, latest beta works lovely! No issues what so ever...

Dia

[nortnil]

Originally Posted by DiabolicGod Ho and by the way nortnil, they worked just fine...thank you once again! Dia

Glad you got everything up and running. Happy to help.

[desperado]

Check my dump, please. http://dump.ru/file/5722585. I think that something wrong with him.

[Bohemio]

Originally Posted by desperado Check my dump, please. http://dump.ru/file/5722585. I think that something wrong with him.

Check your lines again ....... what fw version is your ps3 ???

[desperado]

Originally Posted by Bohemio Check your lines again ....... what fw version is your ps3 ???

3.70 was a fw version

[judges]

Originally Posted by desperado Check my dump, please. http://dump.ru/file/5722585. I think that something wrong with him.

Data lines seem to be fine. Two or more address lines are connected wrong.

[desperado]

Originally Posted by judges Data lines seem to be fine. Two or more address lines are connected wrong.

Can you fix my dump? I am sorry, but that dump was flashed into console and now it has a green light with freeze.

Sorry for my bad english.

[sguerrini97]

Hi, can someone give me a 3.55 patched core_os.bin or a tutorial on how to obtain a cos.bin from the CORE_OS_PACKAGE.PKG? Thanks.

Edit: is THIS (Ps3DevWiki)a valid patched coreos? It has the size required by norpatch, but the page says that I can install only firmwares with patched LV1, instead when I downgrade my PS3 for the first time I was able to install any 3.55 FW.. Thanks and sorry for my english.
Edit2: Yes, that coreos works with any 3.55 firmware (tested with OFW, 3.55.2 REBUG and 3.55-OTHEROS++ via FSM):.

[cory1492]

judges: first off, great work and thanks This ps3 slim with JPT-001 and spansion 'p' NOR now has a whole new level of functionality.

I did the install based on this design (note I was not installing for downgrading, I was already running hermes-3.41), as I could not order from PJRC
http://code.google.com/p/micropendou.../MicropendousA
It has a 1287 chip on it, and I removed SRAM and the buffer chip and relocated the USB plug to something more manageable for a permanent install.

I built firmware from the current source in you're repo with 1287 as the target. Unlike the progskeet I installed before this, it worked nearly perfectly from the get-go. The only problem I had, is the PS3 would not boot to gameos unless I connected usb to the PC and used python to de-assert tristate before hitting the power button.

I wound up removing the 3.3V VREG I added and sourced an alternate 3.3V that is active even when the machine is off and thought I'd share, considering the mention of a regulator getting hot when used to power the samsung NOR and in the hopes it'd help someone else along the way; simply put it's a good 3.3V source and seems to have no issues handling the 15mA that this AVR needed so long as you keep VUSB separate so the current firmware doesn't force you into tristate held low. The single wire in the pic is connected to the micropendous' VCC header hole.

When I get some time I'll dig around in the source a little and see if I can make it sleep until usb is connected, uses a fraction of the power that way. My only question is, do you think there could be some speed gains to be had by moving to a bulk protocol instead of CDC? I've written firmwares for the ARM arch before that can transfer a 16M NAND's contents to a PC in 22s, though NAND does have far less pins and states to deal with - if USB CDC is a possible bottleneck in this, I'd be glad to work on it a bit and see if I can do anything to help out.