These Python scripts are intended to make reading/writing large amounts of data to I2C EEPROM chips with a BusPirate much easier. I have found that tools like flashrom work really well for SPI EEPROM chips, but there don't really seem to be any programs that allow the same functionality for I2C EEPROM chips.
This list will be expanded as I get my hands on more EEPROM chips, but these scripts will be initially developed for the ATMEL 24C256 as it's what I have on hand. Datasheets for the chips I have tested will be in the Datasheets directory.
- ATMEL 24C256
- Python3.6+, since I rely (maybe too much) on f-strings, as do some libraries.
- pyBusPirateLite
- Just clone this repo somewhere and run
python ./setup.py installfrom in the repo to install the library and its dependencies.
- Just clone this repo somewhere and run
- tqdm
- termtables
- A BusPirate
| BusPirate | EEPROM Chip |
|---|---|
| +5V or 3V3 (Depending on your EEPROM) | VCC |
| CLK | SCL |
| MOSI | SDA |
| GND | GND |
The scripts can be run with python ./script-name.py. All scripts now use argparse to take command line arguments, and you can see the help for each individual script with python ./script-name.py --help
- Blank_Dump_Creator.py is used to create a .hex file filled with a byte of your choosing. This can be used to help verify the flasher, dumper and wiper script.
- BusPirate_I2C_EEPROM_Dump.py is used to dump everything from the EEPROM chip into a single binary file (.hex by default).
- BusPirate_I2C_EEPROM_Flash.py is used to upload a binary dump file (.hex by default) to the EEPROM chip.
- BusPirate_I2C_EEPROM_Wipe.py completely fills the EEPROM chip with a chosen array of bytes to remove other data.
- Currently I only plan to support EEPROM chips with up to 16-bit memory addresses. This is because the operation of chips with more memory addresses changes how the I2C addressing works; some of the bits of the I2C address are used to select different memory blocks in addition to the LSB being used to select read or write mode.
- I am aware that there is a lot of repeated code between the different scripts, but I elected to do it this way to allow users to download a single file as they need it, rather than having to download an entire codebase. It also means that the different scripts can be more easily understood, as the actual functional code is relatively small.