KCC's Quizzes AQQ304 - A pure logic
1. Quote of the month: "I am not lazy, I'm just in energy-saving mode" - unknown
2. Quiz AQQ304 about finding a pure logic puzzle
Mike is looking at Anne, but Anne is looking at Paul.
Mike is married, but Paul is not.
Question:
Is a married
View All
September Monthly Blog Quiz! Read the blog, take the quiz, and you could win a gift card
Quiz: How Well Do You Know Adaptive Power Switching?
Is your I/O module overheating? The AD74416H's Adaptive Power Switching (APS) can cut heat dissipation by up to 40% — but how well do you really understand how it works?
Read the blog first: Cooling
View All
ADAU1467
Production
The ADAU1463/ADAU1467 are automotive qualified audio processors that far exceed the digital signal processing capabilities of earlier SigmaDSP® devices...
Datasheet
ADAU1467 on Analog.com
Hi
Having spent many hours trying to understand what was going wrong, I now have a minimum project to demonstrate this failure.
Simply put, the existence of an Interface Write block prevents Self Boot. Take the following trivial example, the oscillator is simply to produce an output that tells me all is well, and the DC block is a substitute for my volume control GPIO configuration : -

If the Interface Write block is removed then 'Write latest compilation through DSP' works perfectly, and a tone can be heard.
With the Interface Write block in place Link Compile Download works perfectly, however 'Write latest compilation through DSP' appears to work ok, but doesn't produce a tone.
From earlier tests using SPI Read I can see that the Interface Write does successfully write to the correct EEPROM address when using Link Compile Download (The WriteAddress defined in the parameters)
I'm using I2C to connect to the board, and SPI EEPROM, functionally equivalent to the EVAL board from this perspective.
So, it looks like a bug to me, does anyone have a workround?
Thanks in advance
Jonathan