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

ADAU1461 INPUT 9 bug in SS 3.8

SigmaDSP & SigmaStudio Brettcoupe Sep 16, 2013 00:00 7 replies Original on forum ↗
Subscribe
Brettcoupe Question
Sep 16, 2013 00:00

Hi.

When trying to use input 9 (TDM ch 8 on the ADAU1461) in sigma studio3.8 i get an error on compile download.

"Error in Input1

Line Numer 30

"digin_9" variable used is not defined in RAM or not a RAM directive."

If i go back to Sigma Studio 3.2 it is OK.

Is there a Fix for this?

Thanks

Brett

ADAU1461

Audio Signal Processors

SigmaDSP Audio Processors

KJBob Reply
Sep 16, 2013 00:00

Hi Brett,

The same error occurs in SigmaStudio 3.9, so upgrading won't help:

Best regards,

Bob

6f508000541acb410c67363bcadb5b38.jpg
6f508000541acb410c67363bcadb5b38.jpg
6f508000541acb410c67363bcadb5b38.jpg-450x228.jpg
6f508000541acb410c67363bcadb5b38.jpg-450x228.jpg
Brettcoupe Reply
Sep 17, 2013 00:00

Hi Bob

Thats unfortunate.

Is there a plan to fix this soon, As I would like to use some of the new algs that 3.8 has

Thanks.

ADIApproved Reply
Sep 17, 2013 00:00

I'll forward this to the software team and see if they have a comment.

Thanks,

Brett

Brettcoupe Reply
Oct 21, 2013 00:00

Hi Brett.

Any News on this?

Thanks

ADIApproved Reply
Oct 21, 2013 00:00

I just checked this on the latest 3.10.1 beta, which is now available to download on the website.

http://www.analog.com/en/dsp-software/ss_sigst_02/sw.html

I reported it to the team.

Luckily, there's a very simple workaround. Just use the ADAU1761 instead of the ADAU1461.

Technically, there are no differences between the ADAU1461 and the ADAU1761 other than the temperature range and automotive qualification. In SigmaStudio, the code and register settings generated by an ADAU1761 project should be the exact same as an ADAU1461 project. They are, in fact, interchangeable (at least as far as the software is concerned).

I tested inputs 8 and 9 with an ADAU1761 in the latest beta and I didn't see the compiler error this time.

Thanks,
Brett

Wilfrido Reply
Oct 22, 2013 00:00

I fixed this bug. It will be available on our next release 3.10.2 Beta.

Thanks for your feedback.

Wilfrido.

Brettcoupe Reply
Oct 25, 2013 00:00

Thanks guys

Aprreaciate it