ADAU1467 Initialization data different from the data sheet description

Hello takumi3952,

SigmaStudio sends a lot of extra data because it does not know the state of the part. Since with an evaluation board the part could have been powered down and turned back on or the other way, the part can have an older version of the program with old settings and parameters so SigmaStudio has to clear out everything to make no assumptions. Then there are also some things that the programmers did not write efficient code and much more data is sent that is not required. I would use the datasheets and the system files to develop the application.

Dave T

Hi Dave,

Thanks a lot.

I understood the situation.

Currently, the initialization code generated by SigmaStudio is complex.

It is difficult to determine which code is required for our project.

I'd like to reduce code that is as unnecessary as possible.

Is there any way to sort out the code it isn't needed?

Thanks and Regards,

Takumi3952,

As David says above, please refer to the data sheet and to the files generated by SigmaStudio. In those generated files, please look at the file <project-name>_IC_1.h. It defines a set of macros, one for each register that needs to be written, and then uses them to initialize the part in the function default_download_IC_1() at the bottom of the file. This is an appropriate boot sequence.

Ken