Build 330 isn't able to program SST (or PCT rebranded) 25VF064C. I also program 25VF016B frequently, and build 330 is working correctly with those.
1) The definition in SPI.VB is incorrect. It uses AAI mode that doesn't exist in the SST device. A second (correct) definition with PCT branding is included in SPI.VB, but the program stops searching when it finds the first (incorrect) definition. I can override this in three ways (patch source and rebuild in VS2010, patch binary EXE to change ID# of first definition, use manual SPI setting). But...
2) Writing to the device from firmware versions 3.04 and 3.05 will fail. Only every third page is written. I can use versions 1.09 or 2.02 of firmware with builds 282-312 with 100% stability.
I'm programming soldered devices on PC motherboards via a DediProg connector. The cable is 2" long and the longest traces on the motherboards is about 1".
PS: Any hope of releasing the Atmel source someday?
1) The definition in SPI.VB is incorrect. It uses AAI mode that doesn't exist in the SST device. A second (correct) definition with PCT branding is included in SPI.VB, but the program stops searching when it finds the first (incorrect) definition. I can override this in three ways (patch source and rebuild in VS2010, patch binary EXE to change ID# of first definition, use manual SPI setting). But...
2) Writing to the device from firmware versions 3.04 and 3.05 will fail. Only every third page is written. I can use versions 1.09 or 2.02 of firmware with builds 282-312 with 100% stability.
I'm programming soldered devices on PC motherboards via a DediProg connector. The cable is 2" long and the longest traces on the motherboards is about 1".
PS: Any hope of releasing the Atmel source someday?