• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 681 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSv5 - Created clock in RTSC editor but does not run

JumpStart
Intellectual 605 points

Other Parts Discussed in Thread: SYSBIOS

Hello TI E2E Community,

I created a clock in my application using the RTSC editor within CCSv5.  When I go to debug the application, I find that the clock function never gets called.  I have also created a clock manually in my code and that does not run either.  What am I missing in sys/bios that is not setup correctly?

Thanks,
JumpStart

  • 0
    TI__Mastermind 21645 points

    Hi JumpStart,

    Can you post the version number of the tools you are using (i.e. Sys/Bios, XdcTools, ...) along with the name of the target you are building your application for ? Also, can you post the full version number of CCS ?

    Best,

    Ashish

  • 0 in reply to Ashish Kapania
    Intellectual 605 points

    Hello Ashish,

    I was trying to merge the facedetect demo from the C6SDK and the uart_dev_serial example that was provided in the StarterWare package and found that interrupts were not working correctly.  Individually the two examples works properly.  I just found out that the uart_dev_serial funtions SetupInt() and ConfigureIntUART() modifies/corrupts the interrupts and so my programs fail to run correctly.  I have commented out these functions and used the Hwi_xxxx() functions to setup and enable interrupts and now the merged program runs.

    I have a question how the Hwi_Params.eventId is used.  The facedetect demo sets the eventId for VPIF to 95 and LCD to 73.  Where did these numbers come from and what do they do?

    Thanks,
    JumpStart

  • 0 in reply to JumpStart
    TI__Mastermind 21645 points

    Hi JumpStart,

    Here's an excerpt from the C6670 datasheet explaining the difference between cpu interrupts and events. You can get the full document from TI website.


    On C6x devices, you can either map a single event to a single interrupt (using Hwi_eventMap API) or map multiple events to a single interrupt (using Event Combiner APIs). In case you are interested in mapping multiple events to a single interrupts you can have a look at the Sys/Bios API reference guide's ti.sysbios.family.c64p.EventCombiner page in CCS Help.

    Best,

    Ashish