EVAL-ADAU1442EBZ SPI Communications mode configuration help reqd.

Hi,

I have moved this discussion from the Processors and DSP community to the SigmaDSP Processors and SigmaStudio Development Tool community. Please continue the discussion here.

Regards,

Craig.

Thanks Craig,

Hopefully will get a solution for this soon.

Rgds, David

Hi David,

Just wanted to let you know I am looking into this issue. I am having HW issues as well getting the EVAL-ADAU144x-EB board working with a simple talkthru even in I2C (thought the USBi says I am connected and downloaded). I need to review the jumper settings and try some other boards. Hopefully I will have an answer by tomorrow.

-JT

Hi David,

I got your messages. Glad to see you are making progress. I was experiencing the same thing trying to download via SPI. I think originally my board jumper configuration was slightly off from the default settings described in the evaluation manual.

However, it seems I can get it to work with your jumper configuration (ADDR1/CDATA high), SPI boot mode on S4 only after I download the program twice. This appears to be related to the I2C to SPI mode change described in a previous post: "I2C to SPI mode change"

Many of the newer SigmaDSPs with both I2C and SPI slave ports require 3 dummy SPI latch toggles to enable the SPI slave interface from default I2C out of reset. It looks to me the first 3 SPI writes are ignored by the ADAU144x during the initial download, i.e the core start pulse and run bits are not disabled during download, and perhaps the initial entire block write address to parameter memory gets corrupted during the 3rd SPI long CLATCH toggle. This would explain why the program somewhat ran but the audio was severely distored, probably because the parameter data was either not copied or incorrectly placed to other addresses in memory.

First SPI Write to address 0xE220

Second SPI Write to address to address 0xE228

Block Write to parameter memory 2000

Downloading the program twice in SigmaStudio will fix the problem.

Note that on the ADAU1452, SigmaStudio automatically will insert the 3 dummy SPI writes prior to download.

-JT

Hello David, (DR), (as opposed to DT which are my initials )

First I am wondering if you have stuffed the resistors going to the control port on the two CODECs? R14-R17 and R24 - R27. I would say do not stuff these right now until you get the comms with the DSP worked out. I like your approach if taking it one step at a time.

I am looking at the schematics of the control port headers. S4 switches the CCLK and the COUT between pins 5 & 7 and 1 & 3. It seems to me that you will want to be using J18 for the USBi and have the switch in the position to connect these signals to it. The schematic does not show which position is which but I think this is the SPI position and you are correctly configured.

When you say you see the signals are you looking at the actual pins of the 1442? Or the links close to it?

In looking around for possible causes of this problem:

1) You will want to remove LK15 and LK16 to isolate the E2PROM from the SPI lines.

2) make sure you are doing three dummy writes to the 1442 to place it into SPI mode.

3) The 1442 cannot use SPI with SELFBOOT mode. So make sure the selfboot pin is low. There seems to be no jumpers for this and it goes directly to the PIC comms processor. So you may have to cut the trace and set it low. Perhaps it is programmed to pull that pin low in SPI mode but since this has to be done right at powerup I am not sure if this happens fast enough. So look at this with a scope and make sure it is sitting low right from power up. I have a feeling it is not.

4) There are rather stiff pull-ups on the SCL and SDA lines. 2k. R164 and R165. This may cause issues later but I do not think this is the problem now.

After you get the 1442 up and running you will need to make some changes to the board to make the CODECs work properly.

1) Yes, you have to populate the open resistors with either small value resistors, 10-33 ohm, or just use 0-ohm jumpers.

2) Resistors R18 - R21 and R28 - R31 will need to be removed. Then you will need to install a pull-up on each CLATCH line of the two CODECs. That is pin 27. This can be a weak 10K pullup. It's purpose is to prevent this line from floating down to ground when power is applied. This will prevent the part from accidentally going into Standalone mode.

This should get you moving forward. Let me know how it is going.

Thanks,

Dave T, aka, DT

This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.

Thank you,
EZ Admin