• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 1004 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.

CCS/TMS320F28035: ADCINT1 and ADCINT2 running wild

Arief Noor Rahman
Intellectual 395 points
Part Number: TMS320F28035


Tool/software: Code Composer Studio

Dear Friends,

I am currently working with F28035, I needs to utilize two ADCINT, since I have two different ADC sampling sequence and following each sampling sequence I need to execute a program.

My question is, my program timing working perfectly when I deactivate one of the ADCINT, however, when both ADCINT1 and ADCINT2 are active, the ADCINT1 and ADCINT2 are running wildly, the interrupt are executed multiple times between sampling time. Can anybody help me to rectify this issue?

Thanks

  • 0
    TI__Guru 62975 points
    Arief,

    Which PIE interrupts are you using for the ADCINTs?

    Are the ADC SOCs triggered by another module/event or are they running in continuous mode?

    -Tommy
  • 0 in reply to tlee
    Intellectual 395 points

    Hi Tommy,

    Thanks for your reply,

    I use EPWM4SOCA and EPWM5SOCA to trigger the adc soc channel, which then trigger ADCINT1 and ADCINT2 upon completion

    I use PIE 1 for both ADCINT1 and ADCINT2, in addition I also have CPU Interrupt on PIE 1 too.  I notice two cases, sometimes the program running wild, or sometimes it just throw the cpu to rsvd_ISR

    However, I've tried to use ADCINT3 and ADCINT4 instead of 1 and 2, and use PIE10...

    and somehow magically my program work. 

    could you please provide me with possible explanation for this issue?

    and also, what is rsvd_ISR actually?

    Thanks,

    Arief

  • 0 in reply to Arief Noor Rahman
    TI__Guru 62975 points

    Arief,

    rsvd_ISR() is the default trap routine in case an uninitialized interrupt is triggered.  You can see the mapping in PieVect.c.

    It sounds like you might have an interrupt triggering (possibly on PIE1) that is not being serviced.

    -Tommy