ADAU1452 & MCU connection using Evaluation Board EVAL-ADAU1452

Hello!

We are following the steps outlined in the Wilfrido´s Sierra 2010 document :Basic Microcontroller Integration Using Sigma Studio along with the ADAU 1452 datasheet. I believe that waiting for the PLL lock is implicit in the implementation of the default_download function (page 14 of the document). This part of the code writes the code exported by SigmaStudio to the MCU - it even has a delay after the PLL write (highlighted in yellow in the image below). As I understand it, that part is absent in this procedure:

Here we have a print configuration of the Slave Port, the three dummy writes. You need 4 blocks of 8 pulses in the SCLK: the first for the chip address, the second for the high byte of the sub address, the third for the low byte of the sub address, and the fourth (and subsequent, when necessary) for the data.

This is the print is the writes of the SigmaStudio exported code:

We can not access the registers in this procedure because they export the contents of the binary in vector form so that through the MCU its possible to write via SPI the binary in DSP memory.

We are connecting the two evalboards, ST and AD, through SPI Port Control (attached one photo).
We only used the pins that, at first, seem to be necessary (pin 5 to 10). The first 4 pins, including the 4 (USB 5 Volts), were not connected.

Could you please advice if connections are made correctly, as well if the tutorial is still valid for the recent version of SigmaStudio and ADAU1452? Is there any procedure we have to make sure in the connections to make this SigmaDSP + MCU integration?

Thank you very much!!

Att

Juliano

Parents
  •    Hello,
    •    Looking into digital signals generated by the uC output I could realize that the codes did not respect DS spec for the family at all, so I asked customer to manually adapt those. 
    •    Customer had to review the process of "System Initialization". By doing that it was noticed that the code generated by Sigma Studio when clicking on the "Export System Files" - in particular the function "default_download_IC_1" generate some writes in the registers that do not correspond to the one described in the datasheet. So there was the need to re-implement this part  by following the "Example System Initialization Register Write Sequence" of the data sheet and it worked perfectly. 
    •    In addition to some seemingly unnecessary writings (it has been reduced from 60 writes to 19 writes to the registers) some values that needed to be set were different from those described in the example.
    •    Additionally we had to add some extra time that is performed by the ADM811. Between reset and comms start we are delaying 600ms.
    I hope this helps ADI to fix this issue on a new release of our SigmaStudio. We have other customer under development in Brazil and it would be nice to give them a typical good solution from the factory.
    Everything worked perfectly but we bumped into this only step. 
    • There it says new releases of the SigmaStudio could solve this issue, regardless the Silicon Version. Was that fixed? as TomC asked, how do we check that?

    Thanks a lot

    Best Regards

    Juliano

Reply
  •    Hello,
    •    Looking into digital signals generated by the uC output I could realize that the codes did not respect DS spec for the family at all, so I asked customer to manually adapt those. 
    •    Customer had to review the process of "System Initialization". By doing that it was noticed that the code generated by Sigma Studio when clicking on the "Export System Files" - in particular the function "default_download_IC_1" generate some writes in the registers that do not correspond to the one described in the datasheet. So there was the need to re-implement this part  by following the "Example System Initialization Register Write Sequence" of the data sheet and it worked perfectly. 
    •    In addition to some seemingly unnecessary writings (it has been reduced from 60 writes to 19 writes to the registers) some values that needed to be set were different from those described in the example.
    •    Additionally we had to add some extra time that is performed by the ADM811. Between reset and comms start we are delaying 600ms.
    I hope this helps ADI to fix this issue on a new release of our SigmaStudio. We have other customer under development in Brazil and it would be nice to give them a typical good solution from the factory.
    Everything worked perfectly but we bumped into this only step. 
    • There it says new releases of the SigmaStudio could solve this issue, regardless the Silicon Version. Was that fixed? as TomC asked, how do we check that?

    Thanks a lot

    Best Regards

    Juliano

Children
No Data