rahmanih

Hi @SimonTechv, Could you try to customize the "lx_user.h" by enabling the 2 following flags: * https://github.com/eclipse-threadx/levelx/blob/ec683ddf1461a05e462d301bf8a15124136b2ca0/common/inc/lx_user_sample.h#L97 * https://github.com/eclipse-threadx/levelx/blob/ec683ddf1461a05e462d301bf8a15124136b2ca0/common/inc/lx_user_sample.h#L106 after enabling this flags you'll need to call in the API:...

> @rahmanih, I tried to enable all the options you described, but it did not affect the initialization speed. > > Sometimes an INVALID_BLOCK error occurs during operation, which never...

@SimonTechv > I changed the sector size to 64 KB. Initialization time has been reduced to 700 milliseconds. However, when I did fault tolerance testing, I found out that a...

>I found out that a sudden reset damages the internal data structure >For more information, I have uploaded the [project code](https://github.com/SimonTechv/azure_stm32_ftl) Sorry but there isn't any 'fault tolerance' code within...

> @rahmanih Protection against power failures is littered in the LevelX documentation. I'm using a random external reset generator for the microcontroller, so my code just uses sequential writing. unless...

> I noticed this line. There are many more 512 byte blocks in a 64 kilobyte block than described in the [comment](https://github.com/eclipse-threadx/levelx/blob/master/common%2Fsrc%2Flx_nor_flash_simulator.c#L33) I want know about limitations for main settings....

closing this issue as solution is provided.