[jwhat]

Hi Weblacky,

I think you are onto something there, as each flash is recorded, and the only place to persist this is back in the PROM, smart thinking 99.

Here is the order of flashes and their count:

[800: 14 -> 15] 0000220 0000 0002 0000 00f0 0000 000e 0000 0010
[600: 15 -> 16] 0000220 0000 0002 0000 00ad 0000 000f 0000 0010
[800: 16 -> 17] 0000220 0000 0002 0000 00ee 0000 0010 0000 0010

So you are right, but it is incrementing, rather than decrementing! (6th column of dump values): 000e -> 000f -> 0010

The pattern on the other (forth column of dump values) is not quite right: [800 - FO (240)] -> [600 - AD (173)] -> [800 - EE (238)] , so if it was decrementing then the middle 600 flash would be Decimal 239 as you say, but it is decimal 173 ...

So this likely represents something else... I could do another cycle of down to 600 then back up to 800 and see if pattern is more apparent.

Care to take a guess on? :

[800: 14 -> 15] 0000160 0000 2faf 0800 0000 0000 0beb c200
[600: 15 -> 16] 0000160 0000 23c3 4600 0000 0000 0beb c200
[800: 16 -> 17] 0000160 0000 2faf 0800 0000 0000 0beb c200

If the last 3 hex in column three are: 800 -> 600 -> 800 then it is binary coded decimal...

The flash has 4 variables: CPU Speed, Hub Speed, Cache Size & Machine Type (SN11 / 2), noting that:
800 -> 320 (Hex)
200 -> C8 (Hex)
4 -> 4 (Hex) ;-)
"SN11" => 53 4E 31 31

Maybe someone could do dump on other speeds (500/700/900) so we can see these and help to find pattern...

To dump PROM: "flash -D" will dump to /usr/cpu/firmware directory with .dump suffix
To get hex: "od -xv <BIN-DUMP> > <HEX-FILE>"

Cheers from Oz,

jwhat/John