ADBMS2950BCCSZ datasheet(65/97 Pages) AD

65 / 97 page

Data Sheet

ADBMS2950B

Rev. 0 | Page 65 of 97

1. Ensure that the GPIOs used for I2C transactions are

not actively forced low through CFGB register setting,

meaning GPIO3C and GPIO4C must be at their

default value (1) to release the pins.

2. Write data and control action through WRCOMM.

3. Perform transmission through STCOMM: 4 bytes for

CMD+PEC and 3 bytes per byte to be transmitted,

maximum 9 bytes, independent of the length of the

daisy-chain as all ICs of the daisy-chain perform the

transmission simultaneously (no daisy-chain shift

not care, for example, it can be set to all 0x00.

4. Get data received during transmission via RDCOMM

if required.

5. Continue with step 2 for any additional bytes.

The following example assumes an I2C EEPROM as

24LC02BHT-E/OT from Microchip connected to the I2C

controller interface of the ADBMS2950B. It shows writing one

byte to an address and reading it back.

First, write a byte (0x8E) to address 0xA0, and do the following

steps:

1. Write data and control action through WRCOMM.

ICOM0 = 0x6 (I2C START), FCOM0 = 0x8 (I2C:

Controller NACK on 9th clock)

ICOM1 = 0x0 (I2C BLANK), FCOM1 = 0x0 (I2C:

Controller ACK on 9th clock)

ICOM2 = 0x0 (I2C BLANK), FCOM2 = 0x9

(Controller NACK followed by STOP)

DATA0 = 0xA0, DATA1 = 0x00, DATA2 = 0x8E

2. Perform transmission through STCOMM.

STCOMM (4 bytes for CMD+PEC) followed by 9

bytes.

Next, perform a Read operation by first writing the memory

read address to I2C peripheral write address:

1. Write data and control action through WRCOMM.

ICOM0 = 0x6 (I2C START), FCOM0 = 0x8 (I2C:

Controller NACK on 9th clock)

ICOM1 = 0x0 (I2C BLANK), FCOM1 = 0x0 (I2C:

Controller ACK on 9th clock)

ICOM2 = 0x6 (I2C START), FCOM0 = 0x8 (I2C:

Controller NACK on 9th clock)

DATA0 = 0xA0, DATA1 = 0x00, DATA2 = 0xA1

2. Perform transmission through STCOMM.

STCOMM (4 bytes for CMD+PEC) followed by 9

bytes.

And finally, read back the byte:

1. Write data and control action through WRCOMM for

the last two remaining bytes.

2. ICOM0 = 0x0 (I2C BLANK), FCOM0 = 0x9

(Controller NACK followed by STOP)

ICOM1 = 0x7 (I2C No transmit), FCOM1 = 0x9

(Controller NACK followed by STOP)

ICOM2 = 0x7 (I2C No transmit), FCOM2 = 0x9

(Controller NACK followed by STOP)

DATA0 = 0xFF, DATA1 = 0x00, DATA2 = 0x00 (2nd

and 3rd byte are do not care)

3. Perform transmission through STCOMM.

STCOMM (4 bytes for CMD+PEC) followed by 9

bytes.

4. Get received data during transmission through

RDCOMM.

DATA0 (Contains 0x8E)

The specifics of the write and read address depends on the

peripheral that is connected. The I2C clock rate depends on the

frequency of the (iso)SPI clock. It might be necessary to slow

down the (iso)SPI clock to not exceed the maximum supported

frequency of the I2C peripheral.

ADBMS6830B COMPATIBLE COMMANDS

The ADBMS2950B supports all read and write commands of

the cell monitors ADBMS6830B to allow operation of daisy-

chains consisting of both device types as shown in SPI and

isoSPI Interface Topologies section.

The Command Code tables show in brackets the Command

Code name of the identical ADBMS6830B code. For example,

the RDI command is identical to the RDCVA command and

has an alternative ADBMS6830B compatible code RDFCA to

which the ADBMS2950B responds as it is an RDI command.

Also, certain poll or 4-byte-only commands are shared between

the ADBMS2950B and ADBMS6830B. For example, the ADI1

command is identical to the ADCV command and ADI2 is

identical to ADCV.

Certain exceptions apply in the case of ADI1 and ADI2 as listed

in the Table 41. Commands without the noted ADBMS6830B

code are ignored by the cell monitors and the ADBMS6830B

codes that are not listed here, for example, ADAX and ADAX2,

are ignored by the ADBMS2950B. This allows certain actions to

be triggered in one device type only.

Table 87 shows the additional compatible read and write

ADBMS6830B command codes. These codes do not have an

internal effect on the ADBMS2950B other than behaving as a

read command returning do not care data with a valid DPEC or

behaving as a write command with the data written being do

not care and incrementing the command counter if the DPEC is

valid for the do not care data.

ADBMS2950BCCSZ датащи(PDF) 65 Page - Analog Devices

ADBMS2950BCCSZ датащи(HTML) 65 Page - Analog Devices

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97

датащи скачать

ссылки URL