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

adau1466Z self-boot faillure

SigmaDSP & SigmaStudio Chri Jul 18, 2018 00:00 3 replies Original on forum ↗
Subscribe
Chri Question
Jul 18, 2018 00:00

Hi all,

I'm using two ADAU1466Z eval board at the same time.

For one, I'm using self boot feature with no problem.

For the second one, with exactly the same sketch, same wiring, I'm unable to use self boot. After a reset or power off then on, no sound, nothing happens.

Do you have any idea of I could test or do to find the mistake?

Many thanks.

Best regards.

Chri Reply
Aug 17, 2018 00:00

Hi all,
After several tests, it appears that the problem is caused by a too high eeprom write speed.
The datasheet show 10000 kHz. If I use 1000 kHz it works fine.
Best regards.

DaveThib Reply
Aug 20, 2018 00:00

Hello Chri,

Since you said EEPROM Write Speed, I am assuming that you were having difficulty writing to the EEPROM. Usually the issue can be that the eval board is set to self-boot. What happens is that when the DSP is loaded with the program to pass data through the DSP it performs a reset. Then it is programmed from the USBi. Well, the soft reset also triggers the selfboot from the EEPROM. so there can be a clash and errors happen. Sometimes it can depend on timing so one may work where another does not. So check that the selfboot switch is off when trying to program the EEPROM.

Dave T

Chri Reply
Aug 21, 2018 00:00

Hi Dave,

Thanks for your kind reply!

Indeed, when I'm writing EEPROM, I move the self boot switch to OFF but I

don't push reset before writing. I wil try next time.

Thanks !

Best regards.

Chris

Le lun. 20 août 2018 à 19:20, DaveThib <

analog@analog-vm.hosted.jivesoftware.com> a écrit :

EngineerZone <https://ez.analog.com/?et=watches.email.thread>;

Re: adau1466Z self-boot faillure

reply from DaveThib

<DaveThib> in *SigmaDSP

Processors and SigmaStudio Development Tool* - View the full discussion

<https://ez.analog.com/message/363081-re-adau1466z-self-boot-faillure?commentID=363081&et=watches.email.thread#comment-363081>;