# US 2008/0307154 A1 · System and Method for Dual-Ported I2C Flash Memory

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0307154 A1
- Document ID: US20080307154A1
- Status: Published application
- Kind: A1
- Application number: 11/759,348
- Filed: 2007-06-07
- Published: 2008-12-11
- Earliest claimed: 2007-06-07
- Assignees: International Business Machines Corporation
- Inventors: Kaveh Naderi; Patrick Allen Buckland; Jason Eric Moore; Abel Enrique Zuzuarregui
- Web page: https://patentgrep.com/patent/US20080307154A1

## CPC

- G06F 12/0292: {using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10)}
- G06F 13/24: using interrupt (G06F13/32 takes precedence)
- G11C 5/066: {Means for reducing external access-lines for a semiconductor memory clip, e.g. by multiplexing at least address and data signals}
- G11C 7/1075: {for multiport memories each having random access ports and serial ports, e.g. video RAM}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

A method for emulating a dual-port I2C device includes monitoring a bus for I2C traffic. A system receives an I2C interrupt on the bus. The system determines whether the received I2C interrupt is one of either a hardware interrupt or a software interrupt. In the event the received I2C interrupt is a hardware interrupt, the system responds to the hardware interrupt, and accesses a flash memory for read/write operation based on the hardware interrupt. In the event the received I2C interrupt is a software interrupt, the system responds to the software interrupt, and accesses a flash memory for read/write operation based on the software interrupt.

## Claims

### Claim 1

A method for emulating a dual-port I2C device, comprising:
monitoring a bus for I2C traffic;
receiving an I2C interrupt on the bus;
determining whether the received I2C interrupt is one of either a hardware interrupt or a software interrupt;
in the event the received I2C interrupt is a hardware interrupt, responding to the hardware interrupt, and accessing a flash memory for read/write operation based on the hardware interrupt; and
in the event the received I2C interrupt is a software interrupt, responding to the software interrupt, and accessing a flash memory for read/write operation based on the software interrupt.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining whether the received I2C interrupt references a supported I2C address; and
responding to the received I2C interrupt only in the event that the received I2C interrupt references a supported I2C address.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining whether the I2C interrupt is one of either a hardware interrupt or a software interrupt comprises identifying an active signal set between a first pair of wires and a second pair of wires.

### Claim 4 (depends on 1)

The method of claim 1, wherein responding to the hardware interrupt comprises responding in a first addressing mode and wherein responding to the software interrupt comprises responding in a second addressing mode, wherein the second addressing mode is different from the first addressing mode.

### Claim 5 (depends on 4)

The method of claim 4, wherein the first addressing mode is a 16-bit addressing mode and the second addressing mode is an 8-bit addressing mode.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
emulating a first I2C engine; and
emulating a second I2C engine.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
emulating a single 512-byte flash memory array accessible by the hardware interrupt; and
emulating two 256-byte flash memory arrays accessible by the software interrupt.

### Claim 8 (depends on 1)

The method of claim 1, wherein the bus comprises multiple masters.

### Claim 9 (depends on 1)

The method of claim 1, wherein the bus comprises multiple chips.

### Claim 10 (depends on 1)

The method of claim 1, wherein the dual-port device comprises a flash memory.

### Claim 11

A system, comprising:
a flash memory array configured to couple to an I2C bus;
a first I2C port coupled to the flash memory array, comprising a first pair of I2C wires and a hardware I2C engine coupled to the first pair of I2C wires and configured in a first addressing protocol;
a second I2C port coupled to the flash memory array, comprising a second pair of I2C wires and a software I2C engine coupled to the second pair of wires and configured in a second addressing protocol, differing from the first addressing protocol; and
wherein the first I2C port interfaces with the flash memory array as a single array;
wherein the second I2C port interfaces with the flash memory array as two independent arrays; and
wherein the first I2C port and the second I2C port are accessible to the I2C bus.

### Claim 12 (depends on 11)

The system of claim 11, wherein the system comprises a PSoC.

### Claim 13 (depends on 11)

The system of claim 11, wherein the first I2C port interfaces with the flash memory array as a single array comprising 512 bytes; and wherein the second I2C port interfaces with the flash memory array as two independent arrays, each comprising 256 bytes.

### Claim 14 (depends on 11)

The system of claim 11, wherein:
the first I2C port further comprises a main power interface; and
the second I2C port further comprises a standby power interface.

### Claim 15 (depends on 11)

The system of claim 11, further comprising an address translation table coupled to the first I2C port and the second I2C port.

### Claim 16 (depends on 11)

The system of claim 11, further comprising a memory buffer coupled to the flash memory array, the first I2C port, and the second I2C port.

### Claim 17

An apparatus comprising a computer program product for emulating a dual-port I2C device, the computer program product having a tangible computer-readable medium with a computer program embodied thereon, the computer program comprising:
computer code for receiving a transmit package for transmission on an Ethernet network;
computer code for monitoring a bus for I2C traffic;
computer code for receiving an I2C interrupt on the bus;
computer code for determining whether the received I2C interrupt is one of either a hardware interrupt or a software interrupt;
computer code for, in the event the received I2C interrupt is a hardware interrupt, responding to the hardware interrupt, and accessing a flash memory for read/write operation based on the hardware interrupt; and
computer code for, in the event the received I2C interrupt is a software interrupt responding to the software interrupt, and accessing a flash memory for read/write operation based on the software interrupt.

### Claim 18 (depends on 17)

The apparatus of claim 17, further comprising:
computer code for determining whether the received I2C interrupt references a supported I2C address; and
computer code for responding to the received I2C interrupt only in the event that the received I2C interrupt references a supported I2C address.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein responding to the hardware interrupt comprises responding in a first addressing mode and wherein responding to the software interrupt comprises responding in a second addressing mode, wherein the second addressing mode is different from the first addressing mode.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the first addressing mode is a 16-bit addressing mode and the second addressing mode is an 8-bit addressing mode.
