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.

TDA4VM: Clarification on "static" status of VIM INTR_EN_SET/INTR_EN_CLR registers in SDL_VIM_getStaticRegs

Part Number: TDA4VM

Tool/software:

Hello,

I am integrating the SDL library and observing behavior related to the SDL_VIM_getStaticRegs API. This function returns a SDL_vimStaticRegs structure, which contains SDL_vimStaticRegs_GRP elements. Within these GRP elements, I see INTR_EN_SET and INTR_EN_CLR registers.

According to the device's Technical Reference Manual (TRM), these INTR_EN_SET and INTR_EN_CLR registers are used for enabling and disabling interrupt masks for event groups, and they are typically modified at runtime based on application needs.

Could you please clarify why these registers, which appear to be dynamic and runtime-alterable per the TRM, are included in a structure (and accessed via an API) explicitly named SDL_VIM_getStaticRegs? This naming suggests they hold static, unchanging values.

Thank you for your insights.

  • Hi, 

    The idea behind having these registers in the SDL API is that the value of these registers once configured, do not change dynamically.

    Regards,

    Josiitaa

  • Hello Josiita,
    Okay but I don't think this can be applied to many register in the configuration structure as their values are expected to be changed dynamically for example the "SDL_vimRegs_PRI" register containing the "/* Interrupt Priority Register */", this value can be changed during run time according to the "the highest priority pending IRQwhich makes this register can't be treated as static as per the previously mentioned definition.

  • Hi,

    The interrupt Q priority register is also a static register. It is not expected to change after interrupt configuration. It does not change dynamically without reconfiguration.

    Regards,

    Josiitaa