Amiga.org

Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: x56h34 on May 11, 2004, 06:05:23 PM

Title: BlizzardPPC flash update problem.
Post by: x56h34 on May 11, 2004, 06:05:23 PM
I've decided to upgrade my BPPC 040/200Mhz no SCSI with the latest flash update and I seem to have corrupted the flashrom somehow. I've used the BlizzPPC040Update file and I've booted without startup-sequence, disabled every HD volume, etc., etc.

When I ran the update file, it started to detect my hardware and it correctly reported Blizzard 603e 200Mhz CPU, but then the unthinkable happened. I got this message:

MFB error: sector 0 protected
Oops! You're in deep trouble now !
Close all doors and wait for the end of the world or rerun the program.

Hmmm...immediately I suspected that the board is DOA from this point, and I am probably right, as now when I try to execute the flash update again and again (even used older flash updates of BlizzPPC040Update), I get a message that says something like:

Blizzard 603e unknown Mhz Speed?
Error detecting clock.

Is there any hope for this card yet or is it done for?
Title: Re: BlizzardPPC flash update problem.
Post by: Brian on May 11, 2004, 07:20:22 PM
Don't fix what isn't broken, especialy when it involves flashing of hardware which can end in dissaster.

Sadly I can't help you with your problem but the flash readme clearly say if the update isn't allowed to run it's course it can end up rendering the BPPC useless... hope for the best but prepare for the worst. :-(
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 11, 2004, 07:33:19 PM
But I had to run it. It's a revision 2 BPPC that I was going to use with Grex 1200, and in order to do that I needed the Grex compatible flashrom which carries the PCI boot menu option.

I wouldn't touch it otherwise, if things are working fine. I know about the sensitive nature of these cards, especially when it comes to 040 BPPC models.
Title: Re: BlizzardPPC flash update problem.
Post by: Ryu on May 11, 2004, 07:39:59 PM
this ones easy peasy, if you use the "?" qualifier youll see the flash tool has a mhz option, so you just need to enter the clockspeed manually, BlizzPPCupdate 200mhz, simple :-)
Title: Re: BlizzardPPC flash update problem.
Post by: Dragster on May 11, 2004, 07:45:57 PM
I think there's a "force" option which could help too. Try the MHZ argument first.

Cheers :)
Title: Re: BlizzardPPC flash update problem.
Post by: hnl_dk on May 11, 2004, 07:50:12 PM
Just searched a bit ... if you have updated to v2.2 (http://www.dcecom.de/pub/grex/flash/flash_20011012.lha), and use BlizKick ... then you need to use the newest BlizKick (http://vgr.tc3net.com/g-rex/BlizKick1_24beta8.lha)
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 11, 2004, 07:50:45 PM
Ryu,

if this works I will send you a nice little postcard. Thanks for the tip, I will try it out tonight.
Title: Re: BlizzardPPC flash update problem.
Post by: Karlos on May 11, 2004, 09:47:46 PM
Ive seen this error a few times on my machine, usually when it decides to "forget itself" and I have to reflash it to get it going. This happens occasionally for no apparent reason.

The problem seems to be with the v1.4 flashtool. Earlier flash updates using the v1.3 flashtool will happily install regardless of the "sector 0" thing.

The pre-grexx flash and the one before it work well. You can flash with either one and it ignores the write protection gubbins and will happily install. Then you can flash it with a more recent version.

Be careful flashing your system if it doesn't need it. I have to reflash my system once in a while as I said, simply because it suddenly decides to fail (almost like I disabled it using the "2" key). Unfortunately the 10 second reset key combination trick doens't work here because I'm using a PC keyboard that won't hold the reset line that long.

Anyway, generally I seriously don't reccomend any of the later flash updates such as those that support grexx etc., unless you need to use it. I found it stopped warp3d etc. running on my bvision.
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 12, 2004, 03:50:54 AM
The card lives! :-)

I've used the 200MHZ comment and it worked. The flashing process lasted longer than usual (5 minutes or so), but I suppose this was due to the previously corrupted flashrom. I can now access the bootmenu again. Thanks Ryu! Also thanks to others who chiped in with tips. ;-)

As soon as I get a tower case, I am ready to unleash the awesome power of Grex 1200 PCI. :-P

The case will most likely be Infinitiv Tower. :lol:
Title: Re: BlizzardPPC flash update problem.
Post by: Brian on May 12, 2004, 08:53:51 AM
Infinitiv tower... eeew... it should be criminal to create such a lousy product!
Title: Re: BlizzardPPC flash update problem.
Post by: Peter_s on May 12, 2004, 11:15:19 AM
Quote
Infinitiv tower... eeew... it should be criminal to create such a lousy product!


Yea tell me about it, I have two of them and everytime I look at them they fall apart.
Title: Re: BlizzardPPC flash update problem.
Post by: AmiGR on May 12, 2004, 12:56:21 PM
BlizzPPC040Update -force
Title: Re: BlizzardPPC flash update problem.
Post by: Karlos on May 12, 2004, 01:28:27 PM
Quote

x56h34 wrote:
The card lives! :-)

I've used the 200MHZ comment and it worked. The flashing process lasted longer than usual (5 minutes or so), but I suppose this was due to the previously corrupted flashrom. I can now access the bootmenu again. Thanks Ryu! Also thanks to others who chiped in with tips. ;-)


Actually, it sounds *just* like the problem I have with mine when it decided to "go funny."

It takes ages because your fast mem is not available and the whole flash program runs from grindingly slow, uncached chipram.

You might find this happens again in the future. I know I'm not the only one who has a weird flashrom in a BPPC, so don't worry - you'll know what to do if it does happen again.

Quote

As soon as I get a tower case, I am ready to unleash the awesome power of Grex 1200 PCI. :-P

The case will most likely be Infinitiv Tower. :lol:


Oh, I didn't read the bit about th GRrex when I told you not to touch that version of the flash update. Of course if you are intending to use one, of course you need it :-)

You might want to keep any eye on heat etc. with that GRex - IIRC Lempkee said his overheated and died. I dunno if he was just unlucky or what.
Title: Re: BlizzardPPC flash update problem.
Post by: Ryu on May 12, 2004, 02:19:32 PM
I know at least 5 others who have had there Grex's die within a day or 2 with heat damage. I know one guy who lost his BPPC  and motherboard to it, needless to say he no longer uses an amiga. But still some people have been lucky with a Grex so...
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 12, 2004, 03:22:07 PM
I've had a Grex 1200 before, when it was still neck to neck with Mediator (my old Power Tower 1200 BPPC 060 setup), and it ran perfectly well.

I would assume that those dead Grex boards and PPC cards were most likely killed due to usage with BPPC 040 cards. Now, before I actually got one, I assumed that Lempkee was exaggeratting about their heat problems, but boy was I wrong. A BPPC 040 has got to be the hottest Amiga product of all, and I mean this heat wise, not hot as in good or cool! ;-)

I will need to implement some major cooling for this. The 040 will get a 486 heatsink and fan, and I may as well put some sort of an extra fan over the PPC heatsink. I just need to find one that can easily be attached and is the right size.
Title: Re: BlizzardPPC flash update problem.
Post by: Karlos on May 12, 2004, 03:57:44 PM
You could do a lot worse than getting a VGA cooler to bold onto the heatsink.

GadgetMaster got hold of one for me, a VanTec IceBerq 4. It has a low profile, is wide enoough to cover the ppc heatsink and has a solid copper construction.

It also comes with a few small copper passive heatsinks for chipsets and thermal pads to stick them on with. I used 2 cut in halld to secure the main fan (it weighs 77 grams) and some thermal paste between the base of it and the surface of the PPC cooler.

It runs at 6000 RPM and keeps the thing nicely cooled. The original fan is totally redundant now and I'm thinking to detach it as it is a chronic source of dust building up inside the ppc cooler. You really need to keep an eye on that side at least, the dust can kill your ppc.

As for the 040, I have a passive (but hefty) heatsink bonded to it. I have shoved a temperature probe into it and have yet to see it go over 32 deg C.
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 12, 2004, 06:34:24 PM
@Karlos:

Sounds good. Do you have any pictures of all that, by any chance? :-)
Title: Re: BlizzardPPC flash update problem.
Post by: AmiGR on May 12, 2004, 07:54:44 PM
I had no problems with the G-Rex so far but my machine is
well cooled.
The only problem I ever had (and still have ) is that the
BPPC was damaged when a PSU died, so PPC OSes do not work
with the G-Rex anymore. The BVPPC (which uses a static
PCI addr) works fine.
Title: Re: BlizzardPPC flash update problem.
Post by: Karlos on May 12, 2004, 08:09:18 PM
Quote

x56h34 wrote:
@Karlos:

Sounds good. Do you have any pictures of all that, by any chance? :-)


Not of the thing installed (don't have a camera handy), but the fan itself is here (http://www.vantecusa.com/product-cooling.html#) (site requires flash).

Look at the system cooling section down the page and select VGA card/CCB-A4C.

The temperature probe isn't a permanent thing, I was just monitoring it to get an idea. Currently it's 29.2 deg C on the 040 heatsink, but if I measure the PPC heatsink (a bit fiddly) it's actually about 20 deg C with the fan going.
Title: Re: BlizzardPPC flash update problem.
Post by: SWAUG on May 12, 2004, 08:31:28 PM
Goto the SWAUG.org.uk website to see the ICEBERQ attached to the BlizzardPPC

Link: http://www.swaug.org.uk/overclock.html (5th Picture)
Title: Re: BlizzardPPC flash update problem.
Post by: x56h34 on May 12, 2004, 08:41:37 PM
Thanks! :-)
Title: Re: BlizzardPPC flash update problem.
Post by: Karlos on May 12, 2004, 09:52:09 PM
@SWAUG

That's not exactly the same model but very close. As far as I can see, the only differences are that this one seems a bit larger diameter and has "go faster" blue LEDs :lol: