Method and device for a accessing non-volatile memory by PC and X-BOX

• US 20040221130A1
• Filed: 04/30/2004
• Published: 11/04/2004
• Est. Priority Date: 05/02/2003
• Status: Abandoned Application

• Current Assignee: Genesys Logic Incorporated
• Original Assignee: Genesys Logic Incorporated
• Inventors: Lai, Jui Yang, Yin, Hsin Ching
• Application Number:
  US10/834,994
• Publication Number:
  US 20040221130A1
• Time in Patent Office: Days
• US Class Current: 711/203
• CPC Class Codes: G06F 12/0292 using tables or multilevel address translation means G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10
• CPC Class Codes: G06F 2212/2022 Flash memory

Abstract

A method for accessing a non-volatile memory by both PC and X-BOX is disclosed. The method includes the following steps: initializing a memory controller, preferably with a USB interface, for accessing the non-volatile memory; generating the first logical-to-physical address mapping table for mapping the first portion of the non-volatile memory; configuring the controller; monitoring the occurrence of an event; analyzing the starting logic address specified in a token packet sent from the host to the controller in response to the event; and generating the second logical-to-physical address mapping table for mapping the second portion of the non-volatile memory when its starting logic address is absent in the first logical-to-physical address mapping table.

Claims

1. A method for accessing a non-volatile memory, comprising the steps of:

initializing a controller for accessing said non-volatile memory, the controller having a USB interface;

generating a first logical-to-physical address mapping table, for mapping a first portion of said non-volatile memory;

configuring said controller;

monitoring an event;

analyzing a token packet sent from the host to said controller to obtain a starting logical address being in response to said event; and

generating a second logical-to-physical address mapping table, for mapping a second portion of said non-volatile memory when said starting logical address is absent in said first logical-to-physical address mapping table.

2. The method as claimed in claim 1 further comprising a step of mapping said starting logical address onto a corresponding physical address in said first mapping table when said starting logical address exists in said first mapping table, so as to allow said controller to access said physical address in said non-volatile memory in response to said token packet.

3. The method as claimed in claim 1 further comprising steps of mapping said starting logical address onto a corresponding physical address in said second mapping table when said starting logical address is absent in said first mapping table;

and said controller to access said physical address in said non-volatile memory in response to said token packet.

4. The method as claimed in claim 1, wherein the size of said first logical-to-physical address mapping table is substantially larger than the size of said second logical-to-physical address mapping table.

5. The method as claimed in claim 1 further comprising a step of:

updating said second logical-to-physical mapping table to map a third portion of said non-volatile memory when said starting logical address is absent in said first mapping table and said second mapping table.

6. The method as claimed in claim 5 further comprising a step of mapping said starting logical address onto a corresponding physical address in said updated second mapping table, so as to allow said controller accessing said physical address in said non-volatile memory in response to said token packet.

7. The method as claimed in claim 1, wherein said configuring step comprises steps of:

acquiring a device descriptor;

setting an address for said controller; and

acquiring a configuration information.

8. The method as claimed in claim 7, wherein said configuration information comprises a configuration descriptor, an interface descriptor, and an endpoint descriptor.

9. The method as claimed in claim 7, wherein said interface descriptor comprises a bInterfaceSubClass field;

wherein when said bInterfaceSubClass field equals to 06, said controller determines the platform is a PC, and when said bInterfaceSubClass field equals to 42, said controller determines the platform is an X-BOX.

10. A method for accessing a non-volatile memory, comprising the steps of:

initializing a controller for accessing said non-volatile memory;

generating in said controller a first logical-to-physical address mapping table for mapping a first portion of said non-volatile memory;

receiving a token packet containing a starting logical address;

generating in said controller a second logical-to-physical address mapping table for mapping a second portion of said non-volatile memory;

generating in said controller a third logical-to-physical address mapping table for mapping a third portion of said non-volatile memory;

mapping said starting logical address to a physical address utilizing said first mapping table, said second mapping table, and said third mapping table; and

accessing said corresponding physical address of said non-volatile memory in response to said token packet.

11. The method as claimed in claim 10, wherein in said generating the third mapping table step, said third mapping table is generated while said starting logical address is present in said second mapping table and said controller is accessing said physical address of said non-volatile memory in response to said token packet.

12. The method as claimed in claim 10 further comprising a step of:

updating said second mapping table while said starting logical address is present in said third mapping table and said controller is accessing said physical address of said non-volatile memory in response to said token packet.

13. The method as claimed in claim 10 further comprising a step of:

updating said third mapping table while said starting logical address is present in said second mapping table and said controller is accessing said physical address of said non-volatile memory in response to said token packet.

14. A controller for accessing a non-volatile memory, comprising:

a read-only memory (ROM), pre-programmed with a firmware;

a random access memory (RAM); and

a microprocessor, coupled to said ROM and said RAM,

wherein said microprocessor operates with said firmware to generate in said RAM a first logical-to-physical address mapping table and a second logical-to-physical address mapping table, in order to map a first portion and a second portion of said non-volatile memory, respectively.

15. The controller as claimed in claim 14, wherein said microprocessor uses said firmware to generate in said RAM a third logical-to-physical address mapping table for mapping a third portion of said non-volatile memory.

16. The controller as claimed in claim 15, wherein said microprocessor generates a third logical-to-physical address mapping table while a starting logical address is present in said second mapping table and said controller is accessing said non-volatile memory in response to said starting logical address.

17. The controller as claimed in claim 15, wherein said microprocessor updates said second logical-to-physical address mapping table while a starting logical address is present in said third mapping table, and said controller is accessing said non-volatile memory in response to said starting logical address.