VF61 bad block memory

after rebooting. VF61 256 signal a memory failure in image memory.
I tried to flash again the image, but there were a lot of messages like:
“block xxx is marked as bad inside the spare area.”

There is a way to receover it ?

Hi,

Bad block on NAND flash are something normal.

You can read about that here - What you should know about Flash storage

Can you paste full output log you get?

flashimage nk20.bin
1 partitions on SD card.
File is an uncompressed bin file.
Image base address 80004000 - size: 39092988 bytes.
… … … … …
Loading done.

Warning: no splash screen found.
Writing image to FLASH: ImageLen: 39092992
block 400 is marked as bad inside the spare area.
block 399 is marked as bad inside the spare area.
block 398 is marked as bad inside the spare area.
block 397 is marked as bad inside the spare area.
block 396 is marked as bad inside the spare area.
block 395 is marked as bad inside the spare area.
block 394 is marked as bad inside the spare area.
block 393 is marked as bad inside the spare area.
block 392 is marked as bad inside the spare area.
block 391 is marked as bad inside the spare area.
block 390 is marked as bad inside the spare area.
block 389 is marked as bad inside the spare area.
block 388 is marked as bad inside the spare area.

I read the article about memory.
It talk about how preserve memory, but this is a brand new object.
I buy it last June, but i start with develop the last month.
I make my own image ( your standard + browser component + cf20),
and develop application using ram and sd card to preserve the flash memory.
One morning when i came in office, vybrid signal an error in the OS image and
when i tried to reflash the image i obtained the messages above.
I have another VF61 card that work properly again

Can you please give me serial number of the module?

col VF61 256MB IT V 1.2A
02815537

I checked this module and in production, it did not have bad blocks. Do you maybe remember what happened to this module before it started having so many bad blocks? You could also try erasing everything and recreate bad block table. you can type “eraseflash 0 256MB nocheck” but you will have to use recovery mode after that. Are you using the same version of bootloader and image?

I maked all you suggested. It works fine for now.
I used bootloader 1.3 and a my own image, starting from your 1.3 with browser and .net 2.0 components added.
i was testing my application and after a cold reset with your update tools, VF61 was unable to load the image for memory error. I tried to flash again, and i obtained bad block informations.
In apparence nothing strange happened.