ADAU1452 Self-Boot EEPROM Write Procedure link broken

Hello,

Thanks for pointing out the broken link. I have not idea why that is that way.

Here is a post that goes over the basics. Let me know if you run into problems.

https://ez.analog.com/thread/41119

Dave T

And... this link is still broken as are many on the site.

Is there a way to get this resolved?

I've sent private email to processor/tools group and no reply. In the past I have had a very hard time getting support here and have had to call corporate to escalate. It's a shame key links like this remain broken...

Thanks in advance for any help anyone can provide with this!

FYI - info below is helpful but I am finding that I am running into similar broken links all over site so thought I'd post here and see if any life even if it's old thread....

I put in a request to the software team to see if they can look into it.

Are there other specific questions you need answered?

Dave T

Hi Dave - thanks so much for reply and forwarding that on to team.

I seem to be having issues getting any documentation - is it me or is there some site-wide issue?

As far as specifics I just brought up a new '1452 design - all is working great so far.

I'e had two questions this afternoon - the push-hold block does not seem to work - I have the input connected to a GPIO input and that is driving other logic which works. Was wondering what the expected input range is? I get a 404 error on wiki link to that block...

Also looking to write code to boot device from a micro - have doc for that - the .dat file does not exactly match the capture window at the start. I can sort that out I think using logic analyzer and looking at files.

In general I reference site a lot and have hit a lot of links that just don't work anymore - thanks again for your help with this!

Regards,

Darius

Hello Darius,

I just tested the Push Hold cell and it seems to be working fine. I think what you may be experiencing is that the pulse it produces is one sample period long so you cannot see it using Readbacks. Well, at least not for long and you have to be lucky to read it exactly during that one sample.

What I did to test this was to use a pulse counter and I watched that output.

Most of the GPIO cells will take a zero input as a zero, then any non-zero input as a "1". So this will make it immune to number formats.

Here is what I did:

Regarding the Wiki help files. I know they need a lot of work. There has been some effort in updating but most of us Apps engineers just don't have the time to work on it. We will probably make a push on this in the near future. What I often do if the "F1" key press does not work is to go to the root of the SigmaDSP page and navigate through the site there. Sometimes you can find what you need in that way. But then sometimes you will end up with a 404 error. Using the forum is a great resource as well.

With the capture window, Keep in mind that SigmaStudio has to inject extra commands because it does not know the state of the DSP. Your controller will know if this is a cold boot or a hot reset/boot. It is really good that you are using the Capture window and the Params window, it will help you understand how SigmaStudio controls the object inside the DSP so you can replicate it with your micro.

Dave T

Thanks Dave! I think that was issue - I was trying to catch state using a read-back...

Thanks for schematic/suggestions and comments on support and links - I appreciate your quick reply!!!

Darius