ΣSigmaStudio Ask AI Русский Log in

Check last compilation vs E2PROM fails

SigmaDSP & SigmaStudio BRO Dec 17, 2015 00:00 5 replies Original on forum ↗
Subscribe
BRO Question
Dec 17, 2015 00:00

My older dspproj checks OK, but my newer one, larger and with hierarchy blocks, reports a communication failure. It does not seems to be hardware related since it does it both on my production pcb and the development system: USBi and 1701 mini. The EEPROM is a 64K and the program is much smaller than that. Changing the EEPROM size specified in the dialog boxes does not seem to matter anyway; I can use 256K and it still works when it works.Any ideas anyone? Thanks in advance.

BRO Reply
Dec 17, 2015 00:00

some more poking around reveals the LEVEL DRIVEN HPF block is causing the problem. Delete it and the check is successful. But I still don't know why that circuit is a problem. It gacks whether it is in a hierarchy block or not.

BRO Reply
Dec 18, 2015 00:00

Some MORE poking reveals that the LEVEL DRIVEN HPF is not the fault because if other things are deleted and it left in, we get READ/WRITE SUCCESSFUL . So it is something about the size of the file that is the problem? The program_data.dat file is the largest at 42K. Well under 64K EEPROM size. Or is there a secret extra bloat?

BRO Reply
Dec 18, 2015 00:00

And of course the 1701 mini dev board has a 256K EEPROM. So while the error is associated with file size, it does not seem to be associated with EEPROM size. Some sort of time out? I tried with both SS 3.11 and 3.12 beta.

KJBob Reply
Dec 19, 2015 00:00

Hello,

I verified your results, suggesting that neither eval hardware nor a particular PC is the issue. The E2PROM Check also failed with one of my large projects -- again, verifying that this problem is related to program size. I tried a few workarounds involving the WinE2PROM Loader, but nothing helped.

Best regards,

Bob

DaveThib Reply
Mar 2, 2020 00:00

Hello BRO and all others on this post.

We finally have been able to track down this issue. The problem was in the ADAU1701 DLL. I will attach an updated version of the DLL. You will need to place this into the program folder with all the other DLLs and restart the program. It is always a good idea to save the old DLL in a safe place in another folder in case there is some unforeseen issue.

This fix will be in future revisions of SigmaStudio. The current revision as of this post is Rev 4.5

Sorry for all the trouble and thanks for the reports that helped us find this.

Dave T

Sigma100Protected.zip