• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 811 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.

RM57 interrupt becomes pending after call to vimChannelMap

Rik Anderson
Prodigy 110 points
Other Parts Discussed in Thread: HALCOGEN

I am using IAR with the RM57 and startup code generated by HALCoGen. Everything generally seems to work, except when I call vimChannelMap the interrupt for the handler installed seems to become immediately pending. Before installing the interrupt I disable interrupts, I then install the interrupt and then enable the interrupts. As the interrupt has become pending it is immediately executed, which should not happen.

I do not get the same problem on an RM48 or a TMS570. Running similar code everything seems fine. I need to be able to install handlers on the fly so I cannot really work around this.

Thanks,

Rik 

  • 0
    TI__Guru 72500 points

    You did not specify which interrupt became pending. Could this be from erratum device#55? I have captured an image from SPNZ214. This erratum applies to revision A silicon, symbolized as RM57L843ZWTT or xRM57L843ZWTT. It is fixed in revision B silicon symbolized as PRM57L843ZWTT or RM57L843BZWTT.

  • 0 in reply to Bob Crosby
    Prodigy 110 points
    The problem occurred due the the cache being enabled but not the MPU. Our code controls the MPU so it is not switched on by the HalCoGen code. However the HalCoGen code did enable the cache. By not enabling the cache in HalCoGen the problem has gone away. I do however now have a further cache related problem which I put in a new question.