eep24c(1) [debian man page]
EEP24C(1) General Commands Manual EEP24C(1) NAME
eep24c - read and write 24Cxxx eeprom devices SYNOPSIS
eep24c -d device [ -r[n] filename | -w[n] filename | -k[n] filename | -f[n] xx ] DESCRIPTION
The command eep24c can be used to read and write 24Cxxx eeprom devices. OPTIONS
The following options are available: -d device Specify the device type. To see a list of the supported devices, try -d help -r filename Read from eeprom and save to a file. -w filename Read from a file and write to eeprom. The addresses not specified in the input file will be filled with 00. -k filename Read from a file and write to eeprom. The addresses not specified in the input file will be kept with its previous values. (this mode is twice slower. It reads whole memory to know previous values, then write whole memory) -f XX Fills the whole eeprom with XX (XX is an hexadecimal value) n Can be used to multiply clock time. If you have a long cable, you may use this option. Example: -r5 will read eeprom 5 times slower (pulse width will be standard value multiplied by 5). Valid range for n is from 1 to 50. Default value is 1. USAGE EXAMPLES
eep24c -d 24c04 -r file.hex read eeprom, write to file.hex eep24c -d 24c04 -r3 file.hex read eeprom, write to file.hex, 3 times slower. eep24c -d 24c04 -w file.hex read file.hex and write to eeprom. All the bytes not found in file.hex will be written as 00. eep24c -d 24c04 -k file.hex read file.hex and write to eeprom. All the bytes not found in file.hex will remain unchanged. eep24c -d 24c04 -f 7A fill eeprom with 7A (hexadecimal). INPUT AND OUTPUT FORMAT
Input and output file format is Intel Hexadecimal Object File Format You can find this specification at ftp://download.intel.com/support/processors/ i960/devtools/INTELHEX.PDF Record types 00 and 01 are implemented in this version. In input lines, LF and CR+LF are accepted as newline markers. Output files are generated with LF as a newline marker. DEVICE SPECIFIC
If you are using Microchip 24*515, you must tie its pin A2 to VCC (needs a hardware modification, see device datasheet). SEE ALSO
ihex2txt(1), txt2ihex(1). AUTHOR
This manual page was written by Pedro Zorzenon Neto <pzn@vztech.com.br>. 2002-11-14 EEP24C(1)
Check Out this Related Man Page
I2C(8) BSD System Manager's Manual I2C(8) NAME
i2c -- test I2C bus and slave devices SYNOPSIS
i2c -a address [-f device] [-d r|w] [-w 0|8|16] [-o offset] [-c count] [-m ss|rs|no] [-b] [-v] i2c -s [-f device] [-n skip_addr] [-v] i2c -r [-f device] [-v] DESCRIPTION
The i2c utility can be used to perform raw data transfers (read or write) with devices on the I2C bus. It can also scan the bus for available devices and reset the I2C controller. The options are as follows: -a address 7-bit address on the I2C device to operate on (hex). -b binary mode - when performing a read operation, the data read from the device is output in binary format on stdout; when doing a write, the binary data to be written to the device is read from stdin. -c count number of bytes to transfer (dec). -d r|w transfer direction: r - read, w - write. -f device I2C bus to use (default is /dev/iic0). -m ss|rs|no addressing mode, i.e., I2C bus operations performed after the offset for the transfer has been written to the device and before the actual read/write operation. rs - repeated start; ss - stop start; no - none. -n skip_addr skip address - address(es) to be skipped during bus scan. There are two ways to specify addresses to ignore: by range 'a..b' or using selected addresses 'a:b:c'. This option is available only when "-s" is used. -o offset offset within the device for data transfer (hex). -r reset the controller. -s scan the bus for devices. -v be verbose. -w 0|8|16 device addressing width (in bits). WARNINGS
Great care must be taken when manipulating slave I2C devices with the i2c utility. Often times important configuration data for the system is kept in non-volatile but write enabled memories located on the I2C bus, for example Ethernet hardware addresses, RAM module parameters (SPD), processor reset configuration word etc. It is very easy to render the whole system unusable when such configuration data is deleted or altered, so use the ``-d w'' (write) command only if you know exactly what you are doing. Also avoid ungraceful interrupting of an ongoing transaction on the I2C bus, as it can lead to potentially dangerous effects. Consider the following scenario: when the host CPU is reset (for whatever reason) in the middle of a started I2C transaction, the I2C slave device could be left in write mode waiting for data or offset to arrive. When the CPU reinitializes itself and talks to this I2C slave device again, the commands and other control info it sends are treated by the slave device as data or offset it was waiting for, and there's great potential for corruption if such a write is performed. EXAMPLES
o Scan the default bus (/dev/iic0) for devices: i2c -s o Scan the default bus (/dev/iic0) for devices and skip addresses 0x56 and 0x45. i2c -s -n 0x56:0x45 o Scan the default bus (/dev/iic0) for devices and skip address range 0x34 to 0x56. i2c -s -n 0x34..0x56 o Read 8 bytes of data from device at address 0x56 (e.g., an EEPROM): i2c -a 0x56 -d r -c 8 o Write 16 bytes of data from file data.bin to device 0x56 at offset 0x10: i2c -a 0x56 -d w -c 16 -o 0x10 -b < data.bin o Copy 4 bytes between two EEPROMs (0x56 on /dev/iic1 to 0x57 on /dev/iic0): i2c -a 0x56 -f /dev/iic1 -d r -c 0x4 -b | i2c -a 0x57 -f /dev/iic0 -d w -c 4 -b o Reset the controller: i2c -f /dev/iic1 -r SEE ALSO
iic(4), iicbus(4) HISTORY
The i2c utility appeared in FreeBSD 8.0. AUTHORS
The i2c utility and this manual page were written by Bartlomiej Sieka <tur@semihalf.com> and Michal Hajduk <mih@semihalf.com>. BSD
January 23, 2009 BSD