• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 458 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM2634: AM263x SysCfg Tool CCS 11.1 HowTo assign interrupts

ngrkus
Expert 1020 points
Part Number: AM2634
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I am trying to modify program "fsi_loopback_interrupt_am263x-cc_r5fss0-0_nortos_ti-arm-clang" in the example section of the SDK 8.2.0.28 using the syscfg configuration tool. I try to map the FSI channel 0 to FSI channel 2 and connect the Tx/Rx channel 2 to the connector J6 of the 'AM263x Control Card Hardware User's Guide'. This works without problem. I can 'scope' the flush pattern for the FSI channel on the transmitter at the beginning. However I don't get any interrupts anymore ...

Using the program without any modification from the example folder works out of the box. I try to configure the interrupts for the FSI channel 2, however it is unclear to me what needs to be known. I do not understand the dependencies with respect to the interrupt crossbars and the FSI channel number...

Q: What do I need to configure on the INT XBAR TI driver section within the syscfg tool to make this work?

I did modify the function "fsi_loopback_main(NULL)" called by main to accomodate for channel 2 instead of 0 with respect to FSI. However the needed interrupt configuration for this modified example remains a mystery to me.

Markus

  • +1
    TI__Mastermind 29198 points

    Hi Markus,

    ngrkus said:
    What do I need to configure on the INT XBAR TI driver section within the syscfg tool to make this work?

    I was able to modify fsi_loopback_interrupt_am263x-cc_r5fss0-0_nortos_ti-arm-clang to use FSI2 Tx & Rx.

    I understand you're already able to change the FSI instance from 0 to 2, so I won't discuss that.

    To get the interrupts to work, I set the INT XBAR settings in Sysconfig as follows:

    • CONFIG_INT_XBAR0:
      • XBAR Output: FSIRX2_INT1N
      • Instance: INT_XBAR_20
    • CONFIG_INT_XBAR1:
      • XBAR Output: FSITX2_INT1N
      • Instance: INT_XBAR_28

    It appears the SDK associates each FSI instance with particular VIM interrupt inputs. Please see these files:

    • mcu_plus_sdk_am263x_08_02_00_28\source\drivers\.meta\fsi_rx\soc\fsi_rx_am263x.syscfg.js
    • mcu_plus_sdk_am263x_08_02_00_28\source\drivers\.meta\fsi_tx\soc\fsi_tx_am263x.syscfg.js

    These VIM interrupts are connected to particular CONTROLSS INTXBAR0 outputs, please see the TRM (spruj17.pdf), Table 10-8.

    The generated code in ti_drivers_config.h contains the macros defining the VIM interrupts used for the FSI interrupts, e.g. this is what I see when I've selected in Syscfg:

    Fullscreen
    1
    2
    3
    4
    #define CONFIG_FSI_RX0_INTR1 (CSLR_R5FSS0_CORE0_CONTROLSS_INTRXBAR0_OUT_20)
    #define CONFIG_FSI_RX0_INTR2 (CSLR_R5FSS0_CORE0_CONTROLSS_INTRXBAR0_OUT_21)
    #define CONFIG_FSI_TX0_INTR1 (CSLR_R5FSS0_CORE0_CONTROLSS_INTRXBAR0_OUT_28)
    #define CONFIG_FSI_TX0_INTR2 (CSLR_R5FSS0_CORE0_CONTROLSS_INTRXBAR0_OUT_29)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Once this association is known, the INT XBAR output can be configured in Syscfg.

    I don't see a way in Syscfg of knowing the association, or changing the association, between the FSI instances and VIM interrupt numbers. I'll ask the SW Development team about this.

    Regards,
    Frank

  • +1 in reply to Frank Livingston
    TI__Mastermind 29198 points

    Hi Markus,

    I confirmed the FSI to VIM assignment is currently static. A future SDK release will allow dynamic assignment from Syscfg. The current plan shows this will be included in the 08.03.00 release, which is scheduled for the end of May.

    Regards,
    Frank

  • 0 in reply to Frank Livingston
    Expert 1020 points

    Hi Frank,

    thank you for the update.

    br

    Markus