Need help with dynamic programming basics ADAU1702

     Hello,

     As KKSL said, the process of integrating your DSP into a finished system does take some engineering.  Because of its difficulty relative to the ease of building a SigmaStudio project, it's by far the most asked-about topic in the SigmaDSP community.  This means there's plenty of advice available by searching the forum.  I'll try to guide you through some of these resources.

     After SigmaStudio compiles your project, the Export System Files command generates the files you'll need to have your microcontroller boot your -1702.  There's at least two ways to use these files:

1. ADI's standard method uses the generated C header files which can be referenced in your microcontroller's source code to put everything in the right place.  This method is described at: How do I create the microcontroller code to interface to my SigmaDSP?  This is by far the best method for most SigmaDSPs.
2. Unlike many newer / more powerful SigmaDSPs, the ADAU170x has a relatively simple boot sequence.   Thus you can simply cut and paste the hex codes that SigmaStudio provides in the TxBuffer export file directly into your microcontroller code.  This method is described at Updating SigmaDSP Parameter with a Microcontroller  -- which also describes how to have your uC change filter parameters and such.  Note that the parameter addresses move when you modify the project flow.  ADI's C header files automate such changes, otherwise you'll have to do it manually.
3. Generally, it's best to place your microcontroller in charge of as much of the system as possible.  It should boot the DSP, handle the user interface (LCD, encoders, buttons etc), while holding these settings in NV memory over power down if needed.  When the user adjusts EQ or other functions, the microcontroller by calculation and/or lookup tables comes up with the new parameters and safeloads them to the DSP.  For very simple applications one could self-boot the -170x and control everything through GPIOs and Aux ADCs, but this becomes impractical when many user controls are involved, such as with parametric EQs.
4. Parametric and Shelf filter coefficients can be obtained by adapting the calculations in the spreadsheet at https://ez.analog.com/message/159539#159539
5. Safeloading these coefficients is described at https://ez.analog.com/message/61175#61175

     Sorry, I wish it were easier.  Where I work our first product booted a -1701 from a PIC18 micro by the manual method.  This product needed only minimal interaction between the DSP and the micro, which we handled by GPIOs.  Our present prototype has a dsPIC updating filter parameters as described above.

     Best regards,

     Bob

     Hello,

     As KKSL said, the process of integrating your DSP into a finished system does take some engineering.  Because of its difficulty relative to the ease of building a SigmaStudio project, it's by far the most asked-about topic in the SigmaDSP community.  This means there's plenty of advice available by searching the forum.  I'll try to guide you through some of these resources.

     After SigmaStudio compiles your project, the Export System Files command generates the files you'll need to have your microcontroller boot your -1702.  There's at least two ways to use these files:

1. ADI's standard method uses the generated C header files which can be referenced in your microcontroller's source code to put everything in the right place.  This method is described at: How do I create the microcontroller code to interface to my SigmaDSP?  This is by far the best method for most SigmaDSPs.
2. Unlike many newer / more powerful SigmaDSPs, the ADAU170x has a relatively simple boot sequence.   Thus you can simply cut and paste the hex codes that SigmaStudio provides in the TxBuffer export file directly into your microcontroller code.  This method is described at Updating SigmaDSP Parameter with a Microcontroller  -- which also describes how to have your uC change filter parameters and such.  Note that the parameter addresses move when you modify the project flow.  ADI's C header files automate such changes, otherwise you'll have to do it manually.
3. Generally, it's best to place your microcontroller in charge of as much of the system as possible.  It should boot the DSP, handle the user interface (LCD, encoders, buttons etc), while holding these settings in NV memory over power down if needed.  When the user adjusts EQ or other functions, the microcontroller by calculation and/or lookup tables comes up with the new parameters and safeloads them to the DSP.  For very simple applications one could self-boot the -170x and control everything through GPIOs and Aux ADCs, but this becomes impractical when many user controls are involved, such as with parametric EQs.
4. Parametric and Shelf filter coefficients can be obtained by adapting the calculations in the spreadsheet at https://ez.analog.com/message/159539#159539
5. Safeloading these coefficients is described at https://ez.analog.com/message/61175#61175

     Sorry, I wish it were easier.  Where I work our first product booted a -1701 from a PIC18 micro by the manual method.  This product needed only minimal interaction between the DSP and the micro, which we handled by GPIOs.  Our present prototype has a dsPIC updating filter parameters as described above.

     Best regards,

     Bob