IP Library Granted Patent US 7,032,039
Granted Patent B2
US 7,032,039 · App. 10/284,597 · Granted Apr 18, 2006

Method for identification of SPI compatible serial memory devices

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,032,039
App. No.
10/284,597
Granted
Apr 18, 2006
Kind
B2
Abstract

A method for identifying Serial Peripheral Interface (SPI) compatible serial interface memory devices. A microprocessor sends a single command requesting identification information to an SPI device installed on the SPI bus. A byte string, including the JEDEC manufacturer ID, device ID, and any extended device information, is sent back to the microprocessor. The byte string may include one or more continuation codes when the manufacturer ID exceeds 1 byte. The byte string also includes one byte indicating how many bytes of extended device information should be read by the microprocessor. The identification process, issuing the command and receiving the reply, is completed in one operation.

Claims (23)

1. A method for identifying a serial peripheral interface compatible serial interface memory device comprising:

a) sending a clocked command to the device, the command requesting manufacturer and device information; and

b) receiving a clocked reply from the device, the reply identifying:

i) the manufacturer of the device;

ii) device data;

iii) a length of an extended information string, wherein the string contains vendor specific information about the device, the length indicating a number of bytes to be read to obtain information in the extended information string; and

iv) extended vendor specific information about the device, if any, wherein identifying the device is completed in one operation.

2. The method of claim 1 wherein the reply identifies the device using a vendor specific format.

3. The method of claim 1 wherein the reply identifies a JEDEC manufacturer identification.

4. The method of claim 3 further comprising the reply providing at least one continuation code for identifying a JEDEC manufacturer identification.

5. The method of claim 1 wherein the reply identifies the manufacturer of the device in “n” bytes.

6. The method of claim 1 wherein the reply identifies the device data in two bytes.

7. A method for identifying a serial peripheral interface compatible serial interface memory device comprising:

a) requesting manufacturer and device information from the device using a single clocked command; and

b) receiving a clocked byte string of variable length including the requested information and any extended vendor specific information from the device, wherein the clocked byte string identifies a length of an extended information string identifying vendor specific information about the device, the length indicating a number of bytes to be read to obtain information in the extended information string, wherein requesting and receiving the information is completed in one operation.

8. The method of claim 7 wherein receiving the requested information further comprises reading the requested information.

9. The method of claim 7 wherein the byte string identifies the manufacturer of the device.

10. The method of claim 7 wherein the byte string identifies device data.

11. The method of claim 10 further comprising identifying device data with a vendor specific format.

12. The method of claim 9 further comprising identifying the manufacturer of the device with a JEDEC manufacturer identification.

13. The method of claim 12 further comprising using at least one continuation code for providing a JEDEC manufacturer identification.

14. The method of claim 7 wherein the byte string identifies the manufacturer of the device in “n” bytes.

15. The method of claim 7 wherein the byte string identifies the device data in two bytes.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Sep 24, 2019
From: OBSIDIAN AGENCY SERVICES, INC., AS COLLATERAL AGENT
To: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
Reel/Frame 050480/0836 →
RELEASE OF SECURITY INTEREST Recorded May 9, 2019
From: OPUS BANK
To: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
Reel/Frame 049125/0970 →
SECURITY INTEREST Recorded May 8, 2018
From: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
To: OBSIDIAN AGENCY SERVICES, INC., AS COLLATERAL AGENT
Reel/Frame 046105/0731 →
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2017
From: WESTERN ALLIANCE BANK
To: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
Reel/Frame 044219/0610 →
SECURITY INTEREST Recorded May 22, 2015
From: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
To: OPUS BANK
Reel/Frame 035754/0580 →
RELEASE OF SECURITY INTEREST Recorded Oct 15, 2013
From: OPUS BANK
To: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
Reel/Frame 031414/0232 →
SECURITY AGREEMENT Recorded Oct 7, 2013
From: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
To: BRIDGE BANK, NATIONAL ASSOCIATION
Reel/Frame 031371/0581 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2013
From: ATMEL CORPORATION
To: ARTEMIS ACQUISITION LLC
Reel/Frame 029605/0665 →
SECURITY AGREEMENT Recorded Oct 8, 2012
From: ADESTO TECHNOLOGIES CORPORATION; ARTEMIS ACQUISITION LLC
To: OPUS BANK
Reel/Frame 029090/0922 →