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.

PurePath studio generates erroneous code for aic3254 CODEC



5633.attachments.zip

 

Hi all,

As it seems, the code generated by PPS includes some writing to register #254

in page 0, however, there is only up to 128 registers per page in the aic3254 CODEC,

as it can be seen in the attached pictures (unzip the attached archive).

Am I missing something here?

Please let me know if more information needed.

 

Thanks in advance,

Igor

 

  • Hi Igor,

    We were planning on using the '254' magic number to add delay functionality (PurePath would parse this and convert that into a "d" command in the cfg file). It has not been implemented yet. You can remove this register from the SystemSettingsCode.

    Regards,

    J-

  • Hi J,

     

    Thank you for your answer.

     

    Actually I'm trying to parse the generated output file into another ascii file suited

    for SPI interface. I've written a little parsing program on C that basically detects

    the "r", "w" and ">" commands, drops the device's I2C address "0x30" and copying

    register addresses and the values for these registers as is.

     

    So, is there any other magic generated by the PPS that I should be

    aware of?

     

    Thank you in advance for your replies.

     

    Br,

    Igor

     

  • Hi Igor,

    Yes, there is a magic number "255". This is not shown in the SystemSettingCode or .cfg file. It is only shown in the .h file. This instructs the apps processor when to start loading the miniDSP code. See section 4.2.7 of the PurePath Studio Driver Support document located in the PurePath extranet.

    Regards,

    J-

  • Hi J,

     

    Thank you for your quick reply.

     

    Regards,

    Igor