Mobile device using secure spin torque transfer magnetic random access memory (STTMRAM)
US-8996888-B2 · Mar 31, 2015 · US
US11086797B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11086797-B2 |
| Application number | US-201415518218-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 31, 2014 |
| Priority date | Oct 31, 2014 |
| Publication date | Aug 10, 2021 |
| Grant date | Aug 10, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for restricting write access to a non-volatile memory. The method includes receiving a request to write to a protected location in the non-volatile memory and determining whether the protected location is in a write-protected state. If the protected location is not in a write-protected state, the method includes writing data indicated by the request to the protected location. If the protected location is in a write-protected state, the method includes rejecting the request. The protected location stores a validation key to validate the contents of another portion of the non-volatile memory.
Opening claim text (preview).
What is claimed is: 1. A method for restricting write access to a non-volatile memory, the method comprising: routing read and write requests for an address or address range corresponding to a protected location in the non-volatile memory of a memory module including a media controller and the non-volatile memory from a processing unit to the media controller; passing read and write requests for addresses other than the address or address range corresponding to the protected location from the processing unit directly to the non-volatile memory; receiving, by the media controller, a routed request to write to the protected location in the non-volatile memory; determining whether the protected location is in a write-protected state; if the protected location is not in a write-protected state, writing data indicated by the routed request to the protected location; and if the protected location is in a write-protected state, rejecting the routed request. 2. The method of claim 1 wherein the protected location stores a validation key to validate the contents of another portion of the non-volatile memory, and the validation key comprises a checksum to validate the contents of the other portion. 3. The method of claim 2 further comprising: computing a checksum for the other portion of the non-volatile memory; comparing the computed checksum to the validation key; and validating the portion of the non-volatile memory if the computed checksum matches the validation key. 4. The method of claim 1 wherein determining whether the protected location is in a write-protected state comprises analyzing, in a register of the media controller, whether a metadata field of the data stored at the protected location indicates that the protected location is in a write-protected state. 5. A method for restricting write access to a non-volatile memory and maintaining a log buffer, the method comprising: defining the log buffer by an address range within the non-volatile memory starting at a base address and ending at a last address; initializing the log buffer by resetting each location within the address range other than at the last address as not in a write-protected state, and resetting a location at the last address as in the write-protected state; receiving, by a media controller associated with the non-volatile memory, a request to write to a protected location in the non-volatile memory, the protected location comprising a base address and a next address; if the request is to write to the protected location and the protected location is in a write-protected state, rejecting the request; if the request is to write to the next address that is not in the write-protected state, writing data indicated by the request to an address indicated by a write next pointer, setting the location at the next address as in the write-protected state, and incrementing the write next pointer. 6. The method of claim 5 further comprising: receiving, by the media controller, a request to read from the protected location; if the request is to read from the base address and the base address is in the write-protected state, returning data from the base address and setting a read next pointer to a second address in the log buffer; if the request is to read from the next address and the address pointed to by the read next pointer is in a write-protected state, returning data from the address pointed to by the read next pointer and incrementing the read next pointer. 7. The method of claim 6 further comprising: in response to determining that the request is to read from the base address and the base address is not in the write-protected state, returning null data; in response to determining that the request is to read from the next address and the address pointed to by the read next pointer is not in the write-protected state, returning the null data. 8. The method of claim 6 further comprising: in response to determining that the request is to read from the next address and the read next pointer points to the same address as the write next pointer, returning the null data.
Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory · CPC title
for a module or a part of a module · CPC title
for peripheral access to main memory, e.g. direct memory access [DMA] · CPC title
for a range · CPC title
management of metadata or control data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.