The Depot in Brno is asking about Nand Flash DCN00188 on the VC5090 that was written in 2008. I am not sure if Richard Yost was the PM at that time or not ..

But I am asking if anyone knows if there is a tool that was created for this Nand Flash change to assist with wearing?

 

As per  (Kubicek Jan-CQH374),

“It was not implemented as this cab file was finally not for VC5090. That was all so far regarding lock up on splash support on VC5090 but issue remains. We can still see some units coming to repair with this problem.

 

Is there any tool existing like for e.g. MC70? NAND wear estimator and new controller?”

 

I don’t recall this DCN being released.

 

There was an SPR13531 where Suvarcha reports

“Comments: Reviewed the flash contents extracted from the unit in question. All data (monitor, OS etc) was valid except the Application partition. We reflashed only the Application partition and were able to recover the unit completely. We tried to duplicate the field issue by repeatedly cold booting this unit, but did not see a failure. In the meantime, software team has the following suggestions, 'Make sure whether the customer application will run automatically after every cold boot or warm boot. Because during boot time, GWES won’t be ready and if the application calls any Window related API calls, the terminal will hang. This might be the cause.' Provided this update to SAe.”  

 

I know there was a P1 SPR 17144 that dealt with corruption of the flash when customers removed power from the device without suspending. Official result of that SPR was that due to the design of the device, it is a requirement to suspend the device prior to removing from power prevent corruption (as stated in manual) .

 

Can anyone offer additional information or does this require to be a new SPR?