It seems I’ve introduced an annoying bug into some Phoebes that shipped recently (some group 1 orders). The symptoms are:
- status LED on Phoebe is lit for 3 seconds, then blinks once, then the cycle repeats
- games don’t work, console behaves oddly
This is triggered randomly, typically when the supply voltage is unstable (so during power-up or power-down) and will not go away on it’s own. Can’t be fixed by reflashing 3.6 FW.
Here’s the procedure you need to follow:
Do you already have the issue? If not, start RMENU and press C button to see what FW version your ODE has. If it’s less than 4.0 then it won’t happen to you.
If it is 4.0.0 there is a good chance you will eventually ecounter this problem – you don’t need to do anything right now but I’d recommend fixing it anyway, sooner rather than later.
If you already have it or want to fix it before it happens:
Download the FIX FW file and the 4.0.1 FW. Prepare a card for FW upgrade, read about the process on my Updating Phoebe page and be sure you understand the instructions. If not, ask first.
1) Flash the _fix FW, turn your console off after flashing. Remove the SD card and any Saturn slot carts you might have installed.
2) Turn the console on, without any card/cart inserted. It might not show the opening animation but it will go into the Saturn BIOS menu eventually. Turn console off once it does.
DO NOT turn it off until you get into the menu, doing so might brick your ODE.
3) Put the 4.0.1 FW on the card and flash that. Once it is done you can use the console again and the problem should not return.
Few things to note:
– The 4.0 series can’t be downgraded to anything lower than 4.0.0
– To prevent people from flashing just the 4.0.1, without the fix, it will not work unless it detects the fix being applied previously.
– You don’t need to upgrade from 3.6 to 4.0 – but if you want to, you have to apply the fix first.
The only difference between 3.6 and 4.0 is I’ve updated the bootloader so it’s much faster now. This is a backport of DocBrown code and allows flashing much bigger FW files in reasonable time.
Sorry for all that but my consoles didn’t trigger the bug (yet) so I never caught it in testing. And again, if anything is not clear ask first.