ADAU1761: code generation
Hallo,
using the code generation (SigmaStudio 3.5.1, same with 3.5.3) show the following:
in *IC_1_REG.h
/* Playback Line Out Right - Registers (IC 1) */
#define REG_PLAYBACK_LINE_OUT_RIGHT_ADDR 0x4026
#define REG_PLAYBACK_LINE_OUT_RIGHT_BYTE 1
#define REG_PLAYBACK_LINE_OUT_RIGHT_VALUE 0x0
in in *IC_1.h
/* Register Default - IC 1.Playback Output Signal Path Registers */
#define R10_PLAYBACK_OUTPUT_SIGNAL_PATH_REGISTERS_SIZE 14
ADI_REG_TYPE R10_PLAYBACK_OUTPUT_SIGNAL_PATH_REGISTERS_Default[R10_PLAYBACK_OUTPUT_SIGNAL_PATH_REGISTERS_SIZE] = {
0x21, 0x00, 0x41, 0x00, 0x03, 0x09, 0x01, 0x97, 0x97, 0xE6, 0xE2, 0x01, 0x00, 0x03
};
where 0xE2 is on the addr 0x4026.
Programming the DSP the value 0xE2 is used.
That means for me the output to *IC_1_REG.h is wrong on some places !
Best regards.
changed to correct addr
Audio Signal Processors
SigmaDSP Audio Processors
adau1761
Thanks very much for reporting this! I will forward this to the software team and enter it in the SigmaStudio bug-tracker.
Hi,
The software team gave this response:
The "IC_1_REG.h" has the "Default" values from the memory map specifications. The "IC_1_.h" file has the current values the DSP has when compiled and then exported.
So, the IC_1_REG.h reflects the default register values when you start a new project in SigmaStudio, and IC_1_.h reflects the actual register settings that were active when you compiled the project.
I will discuss this further with the software team... Perhaps it would make sense to change the way this works, but for now, that's how it is set up.
Hello BrettG,
thank for your investigation.
From my point of view for using the ADAU1761 together with a microcontroller
and having the possibility to parametering all the needed parts of dsp hardware
and software I need all the actual register settings as the default values for my
application.
My goal is to parse all the needed exported files from sigmastudio with an external
self written application and build automatic the needed tables for my microcontroller
application.
A solution could be to export another f.e. IC_1_REG_ACTUAL.h with the actual parameters.
So you can left the IC_1_REG.h for the default parameters.
Best Regards
I like that idea. Or maybe we could have the values appear in the same file, but with a different variable name. The default values could end in VALUE_DEFAULT whereas the actual settings in the project could be VALUE_SETTING or something like that. I will run that by the software team.
Please log in to reply.