Checksum error using interface write
Hi everyone,
2 years ago I started a thread with the same problem. Due to my routine, the project became a dust collector haha.... So, now I'm back and spend more 30h trying make this work, without sucess.
I thought was a clock error, or communication error, or a EMC/EMI problem, but now I have a complete bench to test... I didn't find anything.
With more search, I realized that all Writes through DSP was sucessful, but back again, I need the data from rotary encoder saving after reboot, what with the normal program is not possible.
Following the thread RE: [Bug Report] ADAU1467 Interface Write creates Self Boot failure , I changed all last 8 bytes to zero's, and was unsucessful again.
Clearly is a checksum error... Why I know?
if I dont change rotary encoder position, it reboots normally. When I change the Interface Write value, the problem becomes to haunt me.
Anyone please tell me that have another solution after this 2 years and I can close this project.
ps.: My last thread: Interface write block causing boot failure
Audio Signal Processors
adau1452
boot
Audio Products
checksum
software
4.7
i2c
problem
adau1467
sigmastudio
SigmaDSP Audio Processors
error
SigmaDSP
adau1466
Show More
Hello IcaroViana2,
Looking at the older posts It looks like we did come up with a work-around which was to zero out the checksum so the program would selfboot the next time after the Writeback made changes.
This is still going to be an issue. We have not made any significant changes to Rev 4.7 of SigmaStudio. All of our development has been in SigmaStudio+ recently. That said, I am guessing this is a bug in that version too.
So thanks for bringing this up to my attention again. I am going to report this to the programmers to see if it has been fixed or to alert them to the problem. It is actually a tough issue. If you place the address above the location of the checksum (which is at the end of the hex file) then yes, if you write a different value it will not be included in the checksum so it will not fail but it also means it will not be read in! So the saved value will not be loaded when the program starts to run. There might be a fix for that in the "Beginning Code" but I will leave this to the programmers to see if they can come up with a solution.
When they do then you will have to move over to the new SigmaStudio+ program. By the way, the programming team has been working hard on it and made some great improvements I have recently seen. It is not out yet but will be soon.
Dave T
Please log in to reply.