• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 1105 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.

Compiler/TMS320C6713B: Peripheral Interrupt connection to CPU interrupt lines.

kowalski
Expert 1285 points
Part Number: TMS320C6713B

Tool/software: TI C/C++ Compiler

Hi,

I am looking at c6000 (c6713 dsk) internal hardware and various peripheral. From c6713 workshop (Workshop), the 12 configurable interrupts are can be connected to various peripheral events by using MUXL and MUXH registers (spru190d, Figure 14-2). This is shown bellow:

The values of MUXL and MUXH are given bellow (spru190d, Table 14-6):

The figure above shows default events and their respective event Number. Suppose I want to connect I2C module (TX/RX event) to any of INT4-INT15 interrupt (SPRU175c). what value should i set to in MUX[X] registers?? I mean where are event Numbers for various peripherals are given? Where i can find other peripheral event numbers that can be mapped to CPU interrupts so that respective interrupt can reach CPU.

I don't want to use CSL Library. I know there are functions in CSL that can do that but I want to stick to baremetal programming.

Kind Regards,

Aimal.

  • 0
    TI__Guru**** 161600 points
    Hi Aimal,

    We're looking into this. Feedback will be posted directly here.

    Best Regards,
    Yordan
  • 0
    TI__Guru* 84110 points

    Aimal,

    You have multiple threads running discussing this topic from different points of view. Please see the answer I posted to Compiler/TMS320C6713B: I2C Interrupt and mark it if you understand the answer there, and now for here.

    We wrote the CSL to provide efficient support with descriptive terms. It is difficult to debug and support hundreds of engineers writing the same thing in baremetal, so we wrote it for you in CSL to get your job done quickly. If you prefer to understand all the details below it, please read the documentation like the datasheet and User Guides and the training materials. And write your project using CSL, get it working, then you will have something to test against as you write your own baremetal code. Even better, you will have the CSL source code to read through and understand how things work. Plus you will avoid many mistakes that we made along the way getting the CSL working well, for you.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Expert 1285 points
    Thanks RandyP, You really made my day...