Delay in startup after rebooting the data saved to the ADAU1701

Processors & DSP Audioecia Jul 19, 2026 00:00 1 replies Original on forum ↗

Audioecia Question

Jul 19, 2026 00:00

Hi, my name is Andre; I'm from Brazil and I'm really enjoying the ADAU1701 DSP. I'm working on an interesting 4-channel amplifier project; I've set everything up in SigmaStudio, and it's running perfectly. The problem is that after turning the DSP off and restarting it, it takes a long time to power up, load, or initialize the saved configuration... I'd like to know if there's an error in my project or if there's room for improvement! Thanks!

dspamp_v1.dspproj

Edit Notes
Realocate sigma code

[edited by: Audioecia at 12:25 AM (GMT -4) on 20 Jul 2026]

hardware

processors and dsp

sigmastudio

SigmaDSP Audio Processors

Processors and Microcontrollers

adau1701

dspamp_v1.dspproj180.7 KB

Report

DaveThib Reply

Jul 20, 2026 00:00

Hello Andre!!!
I hope all is well in Brazil!

It does not seem like there is an error in your project. I am not able to lest it on the bench right now due to other work I am involved in.

There are some power input reasons that might be a factor. The Reset pin needs to go high of course before anything starts up. Then the Selfboot pin also needs to go high to initiate the selfboot.

There is a chance you have some higher value pull-up resistors and a large filter cap that is slowing this process down?

So have a look at that on a scope.

Also look at the PVDD pin and the PVDD_LF pin to see if those are coming up slowly?

Also, see if the voltage regulator it coming up quick enough. There is a filter pin for it, FILTD, pin 41.

I do not expect an issue with the VDRIVE pin which drives the 1.8V internal regulator.

I did notice that your program is 1,000 instructions which is close to the max of 1,024. So it will take a bit longer to load up.

Then I looked for things in your program that could be slowing things down.

I did not see any delay lines so that is not a problem.

I do see you are using a rotary encoder. Try bypassing that to see if that is slowing things down? There is a ramp up with that block.

Another thing you can try is loading up a super simple program that just takes the input and send it to the output! This might help to rule out a hardware issues verses a software issue.

Well, this is a bunch of ideas to try.
This week will be busy for me so ping me with a message if I do not see your responses quickly.

Dave T

Report