[jwhat]

Well to keep this topic going, maybe another valid question is, does anyone know what IC the PROM’s flashed image is stored in? 

I assume it’s on an IO9?  Could one desoldered the working IC, place in a socket on the IO9, dump contents of desoldered IC using some kind of programmer, then if anything goes wrong- restore IC contents from previous backup and keep trying?

I know the older stations had a single chip for the PROM.  While I’d imagine the IO9 to be more integrated, if you backup your own IC and restore it, I’d imagine everything else on the board would be in  sync?

Any thoughts?

Hi Weblacky and others,

I am providing some feedback on "how to get Fuel CPU clock setting" fixed here, as the threads appears to track off onto something completely unrelated.

First some comments:

1. The Fuel does not have an IO9 board so any suggestions relating to IO9 board will not work
2. The Fuel does have L1 so you can use this to get into POD/DEX/CAC mode by setting the debug flags just like you do with O350

So you could possibly reset the CPU speed by first setting debug flag and then booting into POD/DEX/CAC mode.
This avoids the PROM boot sequence, so might provide a way to fix the problem with CPU speed setting.

Here are the basic steps:

1. Connect Fuel to L2 via L1 USB Port
2. Connect to Fuel console port via serial cable (null modem etc, on my Fuel I had to connect at 9600, others have reported connecting at 38400)
3. Set the L1 debug flag via L2: "debug 0x10d"
4. Power up the Fuel via L2: "power up"
5. Put L2 into console mode (Ctl-d)
6. Via the Fuel Serial Port (#1) and terminal emulator you should now get the CAC console prompt: "POD SysCt Cac> "
7. Enter your POD magic command (as mentioned by INDY99 at the start of this thread) ... I do not know what this is for the CPU speed reset, but typing "?" gives a list of valid commands
8. Return back to the L2 and get prompt back (Ctl-t)
9. On the L2 set the L1 debug flag back to 0: "debug 0"
10. Now back to the serial console and do reboot via POD command: "reset"

Your Fuel should now reboot and go into standard boot sequence. If the "magic" speed changing command worked then all is ok.

If not then you will have to do what Hamei says and do some physical CPU swapping to return the Fuel to a useable state.

Please note: I have not tested any "magic" POD speed change command, but I have verified that you can put the Fuel into POD debug mode just like an O350/Tezro.

More happy hacking and testing should anyone end up with bricked Fuel as a result of misconfiguring the CPU speed.

It would be great is someone could help with the "Magic" POD command, at that could prove to be very helpful in future,

Cheers from Oz,


John.