Forum RSS Feed Follow @ Twitter Follow @ Twitter

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Striker extrem corrupted BIOS + chip erased
how do you delete messages?
Not a good sign with no beeps for no memory, that should also give sign too like no GFX does.

BIOS contains bootblock within the BIOS, if you write the whole file to chip then bootblock is written as well, same for erase, if you erase whole chip then BIOS and boot block is gone. This is why EZ Flash gives you that option, to skip or write/update with the one in the file, AWDFlash have that option too for these older BIOS via /SB (Skip boot block) or /WB (Write/Update Boot Block) - some boards also have a boot block jumper which protects the BIOS region that contains the boot block from being overwritten. Since you think you overwrote it via EZFlash, once you have working programmer compatible with your chip you can put it back to via programming the entire BIOS to chip (ie telling EZFlash /WB)

EZFlash may or may not always write entire BIOS, but nothing to see here since you are not using EZ Flash, you have a flash programmer. Boot block is contained in all BIOS, unless someone removes in a mod and forgets to put back in. If you open BIOS in hex, Bootblock for 2002 BIOS starts at 0xFE000, there you can see it's part of the BIOS you are trying to program into the BIOS chip right now. This is last block of the BIOS, from 0xFE000 to 0xFFFFFh is the Bootblock (Actually it starts at 0xFE005h - after entry header)
[Image: wZL7ptq.png]

Now, some boards have boot block that is not part of the BIOS, but I'm not sure if your board does or not. But if it did, you wouldn't have erased it with programmer, since it's not part of the BIOS in those cases, and the wimbios link below would then apply to you

Every BIOS Chip has an ID, that tells the programmer what chip ID is along with it's details such as Brand, size, page size etc
Probably some issue with your programmer, software version and this BIOS ID etc. This is common with programmers, sometimes they do not always work for all chip ID's. That's why I mentioned you may need to try a different programmer (Nano USB one), especially since you are seeing some red pin error.

Did you try recovery via floppy with BIOS named AMIBOOT.ROM?
I'd also put a copy of the normal named BIOS, and put on CD and USB too (FAT32) - per the manual's recovery method

See here also, they discuss shorting pins to invoke bootblock recovery * This will only work if you programmed BIOS again, and dumped that and compared in hex and see same contents as you wrote, so you know chip has complete BIOS data on it
Similar info here -
Thumbs Up 
Yesterday, I have the brain worse than my mobo (bug), excuse me.
What's this GFX ?
the boot block is embedded in the downloadable BIOS of the manufacturer ?
Part of your text that I knew, but the other not at all from the hexadecimal edition.
I found (logiciel tl866ii) the address 0xFE000 and 0XFE000 = 000FE000? But not the 0XF05h, I typed it in address search, but nothing ?

And with Hex Workshop Hex Editor, I start and I'm looking for ...

I am slow at the beginning, and at the end ... too.

Attached Files Thumbnail(s)
chip ID, can you be precise? EEPROM PLCC32 Winbond W .......? The original does not pose a problem with the one I bought on, the person with whom I contacted a confirmed that I was compatible and then, I apparently have the technical documentation of the manufacturer . I also compared the 32 pins (vpp, vdd, ic, vss, nc ....) everything was good.
Excuse me was in French.

Attached Files
.pdf   W39V080APZ.pdf (Size: 265.45 KB / Downloads: 0)
I don't understand why you have three quotes from yourself, empty posts? Just because you flashed the boot block vs not, with stock BIOS and EZ Flash means nothing anyway, anytime you flash the BIOS it can brick - whether you flash the boot block or not, BIOS flashing is always a risk.
Ne faites pas attention aux messages d'hier soir, j'ai plusieurs PC avec un système d'exploitation différent et l'un des PC est presque mort, et hier j'étais épuisé. Pouvez-vous tous lire à nouveau? Je les ai écrites.
Pour ma carte mère, je vérifie les instructions, mais je connais parfaitement et le bloc d'amorçage se trouve dans le BIOS.
Pour les pins marqués en rouge, je suis mal énoncé, quand je programme mes 2 EEPROM SST et que Winbond, les pins rouges ne sont jamais apparus. Les broches en rouge sont indiquées par un diagramme: exemple 1
- c'est si nous allons dans select IC une puce qui n'est pas identique à celle de l'adolescent et que, dans l'adaptateur, nous plaçons une puce, ils seront alors rouges.
- Nous sommes la puce à l'envers (exemple 1)
- is a puce is a mort of the broches is a mort of the broches on a blash endommagé.
Je vous envoie toujours en anglais.

Attached Files
.pdf   TL866II_Instructions.pdf (Size: 3.44 MB / Downloads: 0)
GFX, sorry it's short term used for "graphics card"

Yes, I was talking hex addresses there, and yes boot block is in downloadable BIOS, I showed image of it's location in the BIOS in hex
Boot block start FE000 >> Boot block end FFFFF (Boot block actual start, after header >> FE005) You have to know hex to realize FE005 is 6th byte in FE000 row (= 41)

I don't know about hex search and your hex app etc, all hex applications are different. In the one I use I just put in address I want to go to in top left address location box and hit enter and it takes me there. If you have to use search to move to a certain location then yes you can use those addresses mentioned above. Look at my image, you will see, it's shown in hex so you should recognize (Top left corner shows current location)

I see your hex app (Flash program I guess) shows things very differently, looks like a terrible one to use due to that hyphen being placed in address locations. Use an actual hex program to inspect the BIOS, it will be easier to find things, then you can just scroll to where you want to go. But yes, you are in the correct place in your image.

I cannot read your #15 post.
The table is in hex: I can not find an address (000FE000), or convert the table into an address.
I think I need to study the editing software
I'll be back in a few days ...
I showed you image of it's location, and you showed me image you were there in programmer too (Just address looks different in your programmer because of how it puts "-' in the address locations. You are there in your image above at post #14, that is the boot block, you can read it in the text in your image. Here, I show you it all with your own image

[Image: 4OaxUMw.png]

Anyway, looking at that helps nothing, so waste of time really. I only wanted to show you it's there, and where it was etc.

Forum Jump:

Users browsing this thread: 3 Guest(s)