Dataman 48pro2 29f64g08cbaba verift error.
-
- Posts: 2
- Joined: 01 Aug 2022 01:41
Dataman 48pro2 29f64g08cbaba verift error.
hello, I am a new dataman user, I am trying to copy and write mt 29f64g08cbaba 48pin wp nand flash with my newly purchased dataman -48pro2 device, but I am constantly getting this error, please can you help me.
- Attachments
-
- PG4UW_LOG_windows_content_1176-03278.zip
- (161.82 KiB) Downloaded 4 times
-
- Posts: 883
- Joined: 10 Nov 2011 09:51
Re: Dataman 48pro2 29f64g08cbaba verift error.
Hello Dataadam1984,
Welcome to the Dataman users forum. Looking at the problem report I can see invalid block errors and a verify error. invalid blocks are a normal occurrence in NAND FLASH which is why you need an invalid block management system which maps the invalid blocks and builds a table to keep track of them.
The verify error is most likely due to the fact that you cancelled the READ operation before it completed so the verify procedure when comparing the data in the buffer (incomplete) with the data in the device, it will find differences and show an error.
Working with NAND FLASH memories is non-trivial. Have you seen the application note we provided on this topic?
https://www.dataman.com/mwdownloads/dow ... nk/id/264/
If you have any questions after reading the application note then please contact me.
Best regards.
Neil Parker
Dataman Programmers
Welcome to the Dataman users forum. Looking at the problem report I can see invalid block errors and a verify error. invalid blocks are a normal occurrence in NAND FLASH which is why you need an invalid block management system which maps the invalid blocks and builds a table to keep track of them.
The verify error is most likely due to the fact that you cancelled the READ operation before it completed so the verify procedure when comparing the data in the buffer (incomplete) with the data in the device, it will find differences and show an error.
Working with NAND FLASH memories is non-trivial. Have you seen the application note we provided on this topic?
https://www.dataman.com/mwdownloads/dow ... nk/id/264/
If you have any questions after reading the application note then please contact me.
Best regards.
Neil Parker
Dataman Programmers
-
- Posts: 2
- Joined: 01 Aug 2022 01:41
Re: Dataman 48pro2 29f64g08cbaba verift error.
hello, thank you for your answer, but the reading process is finished and the verification is automatically passed, so the reading is not interrupted (the flash I am trying to read is just written and I got an error of a working radio, maybe it was locked by the installer)?
-
- Posts: 883
- Joined: 10 Nov 2011 09:51
Re: Dataman 48pro2 29f64g08cbaba verift error.
Hello,
If you are trying to copy a NAND FLASH device there is a specific set of options that need to be used:
In general, copying NAND FLASH is not the best way.
Our recommended procedure (without any guarantee of success):
1. Reading master device:
Select the device and then open Access Method <Alt+S> menu and change the following settings:
Invalid blocks management = Treat All Blocks
Spare Area Usage = User Data
User Area - Number of Blocks = number of blocks in device (e.g. 4096 for MT29F4G08ABADAWP)
Run Read operation. After Read is done, save the buffer content to disk.
Now you have a Master device byte-by-byte image stored on your disk. Remember, please, that this image includes all bad blocks existing in the master device, as well as all read flip-flops that have occurred during Read. Both, bad blocks as well as read flip-flops, will propagate into the target device, thus reducing its capacity (bad block propagation) and data reliability (read flip-flops propagation).
I hope this helps.
Best regards,
Neil Parker
Dataman Programmers
If you are trying to copy a NAND FLASH device there is a specific set of options that need to be used:
In general, copying NAND FLASH is not the best way.
Our recommended procedure (without any guarantee of success):
1. Reading master device:
Select the device and then open Access Method <Alt+S> menu and change the following settings:
Invalid blocks management = Treat All Blocks
Spare Area Usage = User Data
User Area - Number of Blocks = number of blocks in device (e.g. 4096 for MT29F4G08ABADAWP)
Run Read operation. After Read is done, save the buffer content to disk.
Now you have a Master device byte-by-byte image stored on your disk. Remember, please, that this image includes all bad blocks existing in the master device, as well as all read flip-flops that have occurred during Read. Both, bad blocks as well as read flip-flops, will propagate into the target device, thus reducing its capacity (bad block propagation) and data reliability (read flip-flops propagation).
I hope this helps.
Best regards,
Neil Parker
Dataman Programmers
Who is online
Users browsing this forum: No registered users and 0 guests