Doesn't load program from EEPROM

[DrJedikiah]

Hello, I have a generic ADAU1401 board from china. I2C addresses and parameters are correct, loadProgram works fine and my blocks actually work but since I don't want to control it realtime all the time I want to make it persistent on EEPROM.

The issue is when I connect WP to ground to write firmware to EEPROM, it succeeds, then I remove WP from ground, DSP starts working as if I loaded with loadProgram, but after I cut power to DSP and power it again it doesn't load any program on its own. Is there anything I need to do to make it load from EEPROM without I2C connected? Sorry if this is out of scope for this project, I hope you can help.

[MCUdude]

Hi! Why would you use the SigmaDSP library when if you don't want to control the DSP in real-time? Then you can just flash the EEPROM using the microcontroller and the DSP would self boot.

I've used the self-boot functionality with real-time control, and I've always connected the WP pin on the EEPROM to ground at all times. Also, you need to make sure the selfboot pin on the DSP is pulled high. Here is a snippet from a project where I've used the ADAU1701 in self-boot mode:

[DrJedikiah]

Thanks for the quick response! I know it's a bit odd but those USBi emulators are ridiculously expensive due to tariff here so I don't have one. It's my first time tinkering with a DSP so found this project as an alternative. I plan to use it for real-time stuff later but I just wanted to make it work as standalone for the time being. So am I wrong for using this project for just writing a program to the EEPROM? If WP is connected to ground then DSP (0x34) ping responds with "2"

[MCUdude]

Yes, the USBi programmers are very expensive. However, there are cheaper clones available on Aliexpress, but I've never tried them.

Try loading the i2c_scanner sketch and post the output here. The EEPROM address should be 0x50, and the DSP address 0x34. When pinging the DSP or the EEPROM, it should respond with 0.

[DrJedikiah]

It shows correct addresses but when WP connected to ground pinging DSP address results in 2

[MCUdude]

Weird. Pulling WP to ground shouldn't affect the DSP at all. I don't have that particular board so I can't troubleshoot it for you. Are you sure the WP pin isn't connected to anything else? and what is the output of the i2c_scanner sketch when you pull WP to ground? Is it connected to the DSP reset pin or something?

[DrJedikiah]

I don't have the schematics for this board, visually inspecting it doesn't look like it's connected to anything other than EEPROM. That's okay though, I thought maybe I was missing something crucial to do after writing or something. That's an issue on my board side probably. Thank you for your time, I'll just be using it connected to the arduino and maybe I add some other blocks too.

[Jay-esp]

i have that same board, when WP is connected to ground on boot there is a problem, when powered up and then connected to ground, no problem, i used both methods, using a cheap programmer based on a fx2 processor board works fine and programmed / controlled by esp32 work fine too, i control the wp pin too by the esp, but sometimes i need to power down the setup to get it working after download, otherwise both methods work when proper sequence is observed