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

include files generations bug?

SigmaDSP & SigmaStudio inventis Feb 3, 2010 00:00 3 replies Original on forum ↗
Subscribe
inventis Question
Feb 3, 2010 00:00

Hello,

I'm developing an application with ADAU1761

When I export a project the include file xxx_CODEC.H has some

variable with a incorrect name, for istance:

ADI_REG_TYPE R29_DSP_RUN_REGISTER_Default[REG_DSP_RUN_REGISTER_BYTE] = {
0X01
};

the DSPRUN register in the ADAU1761 is R62.

I'm also confused because in the datasheet the registry size is always 1byte but I found some initialization with multibyte

like this

/* Register Default - CODEC.Watchdog Registers */
#define R19_WATCHDOG_REGISTERS_SIZE 5
ADI_REG_TYPE R19_WATCHDOG_REGISTERS_Default[R19_WATCHDOG_REGISTERS_SIZE] = {
0X01, 0X00, 0X00, 0X00, 0X00
};

in the datasheet page 50 the watchdog register R56 has a size of 1byte

Audio Signal Processors

SigmaDSP Audio Processors

adau1761

ADIApproved Reply
Dec 13, 2011 00:00

Hi Stephano

Correct, I have seen this problem, I believe is related to the export file generation fixes we recently introduced. I'll make sure our software team is aware of his concern and fixes it in the next SigmaStudio release.

Best regards

Miguel

ADIApproved Reply
Dec 15, 2011 00:00

Hi Stefano,

The “R29” in the export file just means it’s the 29th default register value, it is unrelated to the actual register in the datasheet. Sorry for the confusion. The internal numbers in the export files code are simply unrelated to the datasheet numbers. However, the really important portion is just the address and data, so that should all be correct.

What's happening here with the register lengths is that there are multiple, sequential registers that are written in one burst write. There are actually 5 watchdog registers, as you can see here:

Basically, SigmaStudio is just writing all five of those in one burst, instead of 5 individual writes. You are free to do whichever you choose.

552b1e2f276813886eba6311fe9179da.jpg
552b1e2f276813886eba6311fe9179da.jpg
552b1e2f276813886eba6311fe9179da.jpg-450x49.jpg
552b1e2f276813886eba6311fe9179da.jpg-450x49.jpg
EZAdministrator Reply
Aug 2, 2018 00:00

This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.

Thank you,
EZ Admin