Memory device including one-time programmable block and operation method thereof
AssigneeSamsung Electronics Co., Ltd.
InventorsJae-Hoon Choi, Sang-Wan Nam, Sangyong Yoon, Kookhyun Cho
Life of this patent
Estimating the term…
Abstract
A memory package includes a printed circuit board, a first memory device that is stacked on the printed circuit board, and a second memory device stacked on the first memory device. The first memory device includes a first one-time programmable (OTP) block, the second memory device includes a second OTP block different from the first OTP block, and a horizontal distance from one side of the first memory device to the first OTP block is different from a horizontal distance from one side of the second memory device to the second OTP block.
Claims20
An operation method of a memory device, the method comprising:
- storing data, unassociated with a value indicating a defective block, in a non-defective block, wherein the non-defective block is registered in a bad block table and managed as a bad block despite being defect-free;
- receiving, from a host, a normal read command for the non-defective block;
- and
- replying to the host with a fail signal in response to the normal read command.
An operation method of a data storage device, the method comprising:
- storing data, unassociated with a value indicating a defective block, in a non-defective block among a plurality of non-defective blocks;
- and
- marking a location corresponding to the non-defective block in a bad block table so that the non-defective block is managed as a bad block despite being defect-free.
A memory device comprising:
- a memory cell array comprising a plurality of non-defective blocks;
- and
- an address register configured to store a location corresponding to a selected non-defective block among the plurality of non-defective blocks,
- wherein data stored in the selected non-defective block is unassociated with a value indicating a defective block, and
- wherein the location corresponding to the selected non-defective block is recorded in a bad block table and managed as a bad block despite the block being defect-free.
Dependencies are inferred from the claim text.