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.

using SYSCFG CHIPINT interrupts

Other Parts Discussed in Thread: OMAPL138

I am using the OMAPL138 soc and DSPLINK 1.65.0.2 and DSP/BIOS 5.41.2.14. I would like to use SYSCFG CHIPINT2 for my own interrupt purposes between the ARM and DSP. It appears that DSPLINK is configured to use CHIPINT2 by default.

How do I configure dsplink to not use CHIPINT2 as an interrupt so that I can configure it my self?

Thanks,

Greg.

  • Greg

    DSPLINK experts might be able to address this better, while they get to this, I am curious to understand what use-case is prompting you to do this. There are 2 ARM to DSP interrupts CHIPINT2 and CHIPINT3. Are you essentially trying to swap CHIPINT3 and CHIPINT2 functionality, or you want to use CHIPINT2 for your use-case as well as DSPLINK?

    Regards

    Mukul

  • I am interested in a minimal communication scheme between the ARM and the DSP. Using CHIPINT2 as a interrupt from the ARM to the DSP as a first step while preserving the dsplink to load and start execution of the DSP

     

    Regards,

    Greg.

  • Greg

    This is possible. You can configure DSPLink in Proc only configuration and use it for boot loading the DSP. The feature to boot load non DSPLink executables was added in 1.6x stream and should be available in the version that you have. See here for build details.

    Have you looked at Notify IPC for a simpler communication scheme between ARM and DSP? See here for details.

    The OMAPL138 configuration file is at $DSPLINK\config\all\CFG_OMAPL138GEM_SHMEM.c

    I have updated the configuration and attached it to this post. Please compare the file to understand the difference. Basically I am not configuring CHIPINT2 in DSPLink and free-ing it for your use.

    Deepali