No HEX file generated with ADAU1466

jpwatts Question

Apr 30, 2020 00:00

Hello Dave,

I am working on a crossover with the evaluation card for the ADAU1466. That works well. Except that after the download in the eeprom, if I decide to click on "Export Sytem files", I have all the files, except that the HEX file is always at 0 bytes!
Why, and how should it be done, to have the HEX file created correctly and not empty?

Best regards,
Jean-pierre

PS: All my files created, below attached in ZIP.
Design 7_IC 1.zip

Audio Signal Processors

SigmaDSP Audio Processors

adau1466

Design-7_IC-1.zip45.6 KB

Report

DaveThib Reply

May 4, 2020 00:00

Hello jpwatts,

I have no idea why that file is included in the System Files. That is not the location of where the hex file is stored.

There is also a few steps that need to be done to create the hex file. you have most likely already done them.

First, you must have an EEPROM in your project. I will assume it will be assigned the name IC2. It can be different and you can actually change it if you like. This is what it will most likely look like:

Once that is done you need to compile the program. In the older versions of SigmaStudio this action would create the hex file but that was changed in recent revisions.

For the ADAU1452/1467 family of parts, The Sigma300/350, you need to right click on the part GUI, The ADAU1466 GUI, and select "Selfboot Memory", then Write Latest Compilation through DSP".

This action will create the hex file. You do not actually have to complete the process. When it asks you if it is OK to overwrite you can cancel at that point and the hex file will be there.

SigmaStudio will create a new folder in the project named with your project name and IC2 at the end of the name.

In that folder you will find the hex file.

Sorry for the confusion.

Dave T

Report

jpwatts Reply

May 6, 2020 00:00

OK Dave, it's good now.

however, in HEX we can see the variables (frequency for example) when we change them and recompile them.
On the other hand at the end of the HEX appears 4 bytes which change for each program.

What is the role of these 4 bytes? how are they calculated?

Report

DaveThib Reply

May 12, 2020 00:00

Hello jpwatts,

There are 8 bytes of checksum at the end. I think it is simply the sum that is allowed to overflow of the words and not the bytes but I could be wrong and it could be the bytes. This is not something I look into often. If you set the checksum to be zero then the DSP will ignore the checksum and assume the data was transferred properly.

By the way, this info is in figure 42 of the ADAU1452 Rev D datasheet.

So if you go in and change the parameter in the EEPROM you will have to change the checksum to either a number you calculate or change it to zero so it will be disabled.