Data storage devices and methods for firmware failure prevention
A data storage device including a non-volatile memory and a micro-controller is provided. The non-volatile memory includes a first block and a second block, wherein the first block stores firmware code. The micro-controller writes one predetermined string into the second block before an execution of the firmware code, and determines whether there is more than one predetermined string in the second block. In response to there being no more than one predetermined string in the second block, the micro-controller allows the execution of the firmware code and erases the predetermined string in the second block upon successful completion of a prerequisite procedure during the execution of the firmware code. In response to there being more than one predetermined string in the second block, the micro-controller does not allow the execution of the firmware code.
1. A data storage device, comprising:
a non-volatile memory, comprising a first block and a second block, wherein the first block stores firmware code; and
a micro-controller, configured to:
write one predetermined string into the second block before an execution of the firmware code;
determine whether there is more than one predetermined string in the second block;
in response to there being no more than one predetermined string in the second block, allow the execution of the firmware code and erase the predetermined string in the second block upon successful completion of a prerequisite procedure during the execution of the firmware code; and
in response to there being more than one predetermined string in the second block, not allow the execution of the firmware code.
2. The data storage device as claimed in claim 1 , wherein the prerequisite procedure comprises a link building procedure of the firmware code.
3. The data storage device as claimed in claim 1 , wherein the non-volatile memory is configured to store a boot code, and the micro-controller is further configured to load and execute the boot code from the non-volatile memory, and the writing of the predetermined string into the second block is performed in response to obtaining an address of where the firmware code is stored in the non-volatile memory during the execution of the boot code.
4. The data storage device as claimed in claim 1 , wherein the micro-controller is further configured to enter a ROM-code mode in response to there being more than one predetermined string in the second block.
5. The data storage device as claimed in claim 1 , wherein the micro-controller is further configured to determine whether to perform a debug procedure or not in response to there being more than one predetermined string in the second block, allow the execution of the firmware code in response to determining to perform the debug procedure, and not allow the execution of the firmware code in response to determining not to perform the debug procedure.
6. The data storage device as claimed in claim 1 , wherein the second block is an idle block.
7. The data storage device as claimed in claim 1 , wherein the writing of the predetermined string into the second block comprises:
selecting one of a plurality of empty pages from the second block; and
writing the predetermined string into the selected empty page.
8. A method for firmware failure prevention, executed by a micro-controller of a data storage device comprising a non-volatile memory, the method comprising:
before loading and executing firmware code from a first block of the non-volatile memory, writing one predetermined string into a second block of the non-volatile memory;
determining whether there is more than one predetermined string in the second block;
in response to there being no more than one predetermined string in the second block, allowing the execution of the firmware code and erasing the predetermined string in the second block upon successful completion of a prerequisite procedure during the execution of the firmware code; and
in response to there being more than one predetermined string in the second block, not allowing the execution of the firmware code.
9. The method as claimed in claim 8 , wherein the prerequisite procedure comprises a link building procedure of the firmware code.
10. The method as claimed in claim 8 , further comprising:
loading and executing boot code from the non-volatile memory;
wherein the writing of the predetermined string into the second block is performed in response to obtaining an address of where the firmware code is stored in the non-volatile memory during the execution of the boot code.
11. The method as claimed in claim 8 , further comprising:
entering a ROM-code mode, in response to there being more than one predetermined string in the second block.
12. The method as claimed in claim 8 , further comprising:
determining whether to perform a debug procedure or not in response to there being more than one predetermined string in the second block;
allowing the execution of the firmware code in response to determining to perform the debug procedure; and
not allowing the execution of the firmware code in response to determining not to perform the debug procedure.
13. The method as claimed in claim 8 , wherein the second block is an idle block.
14. The method as claimed in claim 8 , wherein the writing of the predetermined string into the second block comprises:
selecting one of a plurality of empty pages from the second block; and
writing the predetermined string into the selected empty page.