Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A block (128K Byte) of 1.5M data written to the levelx of the main line and the nand partition of 4M will be erased. #42

Open
wono01 opened this issue Apr 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@wono01
Copy link

wono01 commented Apr 9, 2024

A block (128K Byte) of 1.5M data written to the levelx of the main line and the nand partition of 4M will be erased.
Trace the UINT _lx_nand_flash_metadata_allocate (LX_NAND_FLASH * nand_flash) call
_lx_nand_flash_driver_block_erase (nand_flash, block, nand_flash ->lx_nand_flash_base_erase_count+nand_flash ->lx_nand_flash_erase_count_table [block]) has been erased
, I locally implemented erase_count to erase multiple blocks, but the simulator only erased one block,
UINT _lx_nand_flash_simulator_block_erase (ULONG block, ULONG erase_count)
LX_PARAMETER_NOT_USED (erase_count);
According to the context, only one block is added to the list below, and it should be correct to erase only one block. I want to know the correct usage of erase_count.

@wono01 wono01 added the bug Something isn't working label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant