• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 734 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Including manual code into generated script file / PurePath Studio

jaiv
Prodigy 90 points

Other Parts Discussed in Thread: PUREPATHSTUDIO

Hi there,

I am wondering what the normal process is to include manual register settings into a script generated with PurePathStudio.

With manual register settings I mean all the analog routing setup and clock configuration etc as they are apparently not included in the generated file. If I add these settings just after the reset in the script they might be overwritten by the automatic script. Very similar if I add the code at the end of the script I might overwrite settings from the generated script.

I am not using the EVM anymore so I have to take full control of the CODEC. (AIC3254)

 

Do I realy have to analyse the whole script and find out if there could be any overwriting and then decide case by case where to put the values?

 

I am using PPS Version: 2.1 build 2

 

Thanks

  • 0
    TI__Mastermind 46195 points

    Hi Ivo,

    See http://e2e.ti.com/support/data_converters/audio_converters/f/64/p/2479/8520.aspx#8520.

    Instead of using the .cfg file, the generated .h file is better suited for the end implementation. The structures are organized in a register settings (pages 0 and 1) portion and miniDSP_A / miniDSP_D portions.

    Regards,

    J-

  • 0 in reply to J-
    Prodigy 90 points

    Hi J,

    Thanks for this link, the h-file is much better. But now i am still a bit confused why some registers are not at the reset value. For example Page0, register 4,5,6 : The CODEC is set up for using the internal PLL as clock source. Why is this?

    The point is that I want to set up a toolchain for adding manual code into the generated script (or generate a supplementary one). I am not using the EVM board anymore, therefore I have to take full control of the CODEC. Clock settings, Powersupply settings, Interface settings etc. That's why I am wondering if there is a way to include manual code into the PurePath project similar to the clock settings which I mentioned in the first paragraph. This would simplify the development process as I only need to recompile the project and the manual settings are already included.

    Thanks,Ivo

  • 0 in reply to jaiv
    TI__Mastermind 46195 points

    Hi Ivo,

    The PLL is used to obtain the appropriate clocks to satisfy the number of instructions (IDAC/IADC) of the miniDSPs. MDAC*DOSR and MADC*AOSR must be equal than or higher than  IDAC and IADC, respectively. See the Design and Configuration Guide and datasheet in the AIC3254 product folder for more information.

    The framework generates register configuration for use with the EVM. One way to use custom register settings without modyfing the original .h file is to create another .h file with the register settings for your system.

    The structures must be executed in the following order:

    1) miniDSP_A and miniDSP_D

    2) Custom register configuration (e.g. PLL settings, analog routing, power options, etc). Note that the IADC, IDAC, interpolation factor, decimation factor, etc must be set properly. Also, miniDSP must be selected for ADC and DAC processing instead of the processing blocks (PRBs). If you are using adaptive filtering, it should also be configured. Refer to the REG section in the .h file for more details.

    Regards,

    J-