Spi flash programmer software

Production Mode. For operators in production to control multiple programmers and improve the throughput. Command Line. Customer software can control multiple SF programmers by command line interface.

Optimizing batch speed on production mode. Optimizing smart update speed. Fix smart update issue. Once reading is completed, save the output to a file by clicking on the save disk icon. After completing and saving the second dump of the BIOS, we can compare the two files to see if they are exactly the same. This is step 7. We can do that easily by calculating the MD5 checksum from them. In Windows this can be done using certutil with the following command:.

In the above output we can see that both files generated the same hash, so they are identical. This is a good indication that communication with the IC and programmer works as expected. Both files can now be saved as a backup in case things go wrong of in case you want to reflash the BIOS to an older version. Next, we can finally write the new or modified contents to the BIOS chip.

Once programming is done, optionally, you can read the BIOS chip again, as indicated above, and compare the hash of the written file with the actual contents after writing.

This is to make sure that there is no corruption and the contents of the chip matches exactly with the data you wanted to be there. The steps under Linux are the same as from Windows. Only here we will use the CLI tool flashrom.

The easiest is to launch the tool and let it try to detect the type of BIOS chip:. Same as with AsProgrammer, we can see that flashrom is able to come up with a selection but we still have to specify the exact type using the -c option. As our type is MX25LE, we can now read the contents of the chip and save it to file backup1.

Same here again is to read the contents twice and save it in two different files. Like on Windows, using this method we can be sure that the programmer can communicate properly with the chip and we reduce the chance for corruption. All seems to be good in the above output. If you see a different hash, you first need to fix this before proceeding. The next step is to write the backup, dump or modded file using flashrom. This time we use the -w option and specify the input file:.

Optionally here as well is to read the contents again and to compare the MD5 checksum with the file we used as input bios. In the example above, I wrote back the earlier backed up file, so flashrom was smart enough to detect this and give me a warning about it. Hopefully this article can help some people that, just like I was, feel bad because their expensive piece of hardware completely stopped working just because the contents of one tiny IC got corrupted.

Thank you for this excellent guide it has saved me an awful lot of time doing all the research myself. Particularly as the CHA programmer comes with no instructions whatsoever, having said that it is a very low cost item which would be very time consuming to make for yourself.

My current requirment is to reflash the BIOS on a secondhand laptop which has an unknown BIOS setup password and so far no software based tools have been of help. I wrote an article about a HP laptop, to remove the Bios setup password as well as update to a later Bios. As it was a HP laptop, I needed to use cpqtag. Depends completely what you want to do with it. Great, thank you. My CHA came faulty, was not recognizable by the system.

Upon closer inspection, there was a tiny solder bridge between the data lines at the contact points of the USB plug. After removal of the bridge, it works OK. Good to hear this helped. Also took me some time to figure this out, hence why I decided to specifically mention it. Did you remove connectors from de motherboard keyboard, screen, hdd, etc. Both modules can be installed with pip :. Connect the chip as follows, assuming you have an 3. You will need an Arduino running at 3. See 3. To the extent possible under law, the authors below have waived all copyright and related or neighboring rights to spi-flash-programmer.

Recent versions of OpenWRT detect the larger Flash and automatically use it, so you don't need to do any patching. U-Boot still thinks the chip is 4MB large, but Linux doesn't seem to care. So all you need to do is copy the image and write the ART wireless firmware partition to the right spot, which is right at the end of Flash.

I guess if you do a system upgrade which puts the kernel image somewhere after the first 4MB you might be in trouble, so upgrade u-boot before doing that.