adau1452 + cs42448 memory problem

Hello lajs,

Is the board set to selfboot?

Did you program the EEPROM?

I do not know this board you have in the picture. How is it wired? Do you have the pin drives and MP pins setup properly to use SPI on the master port? Also, do you have pull ups on the slave port to use I2C?

It is a little unusual to have one setup for I2C and the other for SPI but it has been done.

Also, This is described on the datasheet. I am not sure how you are using these pins?

This is from the datasheet:

"The slave communications port defaults to I2C mode; however, it can be put into SPI mode by toggling SS (SS/ADDR0), the slave select pin, low three times. Each toggle must last at least the duration of one clock period of the clock on MCLK (XTALIN/MCLK), the master clock input pin."

Thanks,

Dave T

Hello Dave, the board itself doesn't have control for selfboot. the project i am using is edited from a test file made for this exact board. i haven't changed the hardware configuration. after rebooting the board and performing "check latest compilation" it fails and every page seems to 0x00, yet they have 256 bytes.

thanks

CS42448_PCB.pdfCS42448原理图.pdf

Hello lajs,

Can you send over the schematic or this board?

The Selfboot EEPROM has to be on the secondary comms port. The USBi is connected to the primary comms port. So that is a complication.

I would like to see what they do with the Selfboot pin.

It would probably be good to send over your project as well.

It is interesting that you say you see levels on the meters. That would mean the program is running in the DSP and it is communicating with a converter or SPDIF or some other input.

I also suggest you go back to the unedited version of the test file for this board.

Also, check all the power rails for the board and for the DSP.

Dave T

hello Dave,

sorry, i couldn't find the schematic for the dsp board, only for the codec board. but i will send the original test file that has been translated to english.

i have tried the test file but it seems to do the same, so maybe the problem is just that my flash chip is damaged or corrupt. the flash is zd25q016m so it is indeed spi.

DaveThib said:
It is interesting that you say you see levels on the meters. That would mean the program is running in the DSP and it is communicating with a converter or SPDIF or some other input.

correcting myself, the level meters see the input signal of my optical input only when i've pressed "link compile download" and then "write latest compilation through dsp" so the board works when i've done those, until i turn it off and on again and it boots blank.

so the "link compile download" itself doesn't do anything by itself. only until i've written it through the dsp it works temporarily. i've tried to use a CYD esp32 to use as a i2c programmer mainto bypass the flash but it seems that because the selfboot is hardwired high, i can't write anything to the dsp via arduino ide.

with a magnifying glass i can't see visually anything wrong with the board, and the power rails have voltage, tested with a multimeter. and i've tried to press the memory chip down which doesn't seem to help. my file has the dsp connection as i2c because i'm programming via i2c using a fx2lp ez usb

dsp_saatoa.dspproj

1452_cs42448_192_relabelled (1).dspproj

Hello lajs,

This is a bit is a headscratcher...

I just used your file, the "relabeled" one, Here is what I have done:

Set the board for Selfboot

link compile download it works fine.

Then I power down and when it powers up a different program is there, something I wrote at some point. I link/compile/connect and verify it is not your program.

Then without powering down I link/compile/download and it works fine.

Then I write the program through the DSP.

Then of course it works.

I again link/compile/download and it works.

Then I power down and power it back up. Then I link/compile/connect and it works.

So I am not seeing any issues here.

se a scope to see if the SPI comms going to the EEPROM look good?

Since you are able to directly write the program then the slave SPI is probably good.

I noticed you have setup an LED that blinks. That is great to see it working on the eval board. MP11 is an LED on the board I am using.

Dave T