Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 377

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=377 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 158

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 228
Dave's PCF WIP: Paragraphs

6400

Application Calibrating non-volatile memory read thresholds
Matter Number US10998041B1 Reference Case 1 US10998041B1
Created 12/22/21, 12:00 AM Modified 12/22/21, 12:00 AM
Application Number

16869424

Paragraph Number

160

Content

With each iterative check, the valley search operation compares a result (e.g., number of activated memory cells or bit error rate) with a prior result for a previous check. If the candidate read level being checked/tested results in higher bit errors or more activated memory cells, the valley search operation may check a threshold voltage in an opposite direction than the direction that lead to the higher bit errors (activated memory cells). So, if the candidate read level #5 results in fewer activated memory cells than candidate read level #6, then the valley search operation may next test candidate read level #4. If the candidate read level #4 results in fewer activated memory cells than candidate read level #5, then the valley search operation may next test candidate read level #3. If the candidate read level #3 results in more activated memory cells than candidate read level #4, then the valley search operation may stop iterating and determine that candidate read level #4 is the "valley" between the Er memory state and A memory state. Consequently, the valley search operation may change a default read level from candidate read level #5 to candidate read level #4. Next, the valley search operation may follow this similar process for read level D 412, read level F 416, and read level K 426. For example, candidate read levels from read level window 604, read level window 606, and read level window 608 may be iteratively tested. Furthermore, of a valley search operation is done for all logical pages, eventually, all the read levels of the Vt window will be tested and potentially changed to obtain optimal read operation results. A valley search operation is an iterative trial and error method for determining how to adjust read levels.

Notes

Added by DJM 12 2021