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

TMS570LS2124 MibSPI5 Trigger Event

Jose Cuervo
Prodigy 80 points
Other Parts Discussed in Thread: HALCOGEN

I am seeing a potential issue with the TMS570LS2124PGE revision C processor where a MibSPI5 transfer is not triggered when the trigger event and trigger source are set to falling edge and N2HET1[10], respectively.  The same event and pin can, however, be used to trigger and ADC event group conversion.

In an attempt to get this to work, I jumped N2HET1[10] to GIOA[2].  Using HALCoGen 04.04.00, I left the ADC event group trigger set to N2HET1[10] falling edge, but I changed the MibSPI5 transfer group trigger source to GIOA[2].  The transfer group triggers as expected, as does the ADC event group.  This leads me to believe there may be an issue with the MibSPI/N2HET triggering mechanism.

One other data point...

We use IAR Embedded Workbench as our IDE.  Given my original setup (MibSPI5 transfer triggered from N2HET[10]), I noticed that if I halt at a breakpoint after all HALCoGen init() functions have been called and toggle the 8th bit in the HETDOUT register from 1 to 0, a MibSPI5 transfer is triggered.

I did not see anything in the errata document.  Is there something I may be overlooking in my HALCoGen configuration?  What additional information is needed for TI to investigate this potential issue?

Using HALCoGen 04.04.00, I have

  • 0
    TI__Mastermind 22715 points
    Jose,

    You can find the following description below the trigger table in the datasheet. What you observed is normal.

    For N2HET1 trigger sources, the connection to the MibSPI5 module trigger input is made from the input side of the output buffer (at the N2HET1 module boundary). This way, a trigger condition can be generated even if the N2HET1 signal is not selected to be output on the pad. You can not trigger Mibspi by connecting the NHET pin to an external source.

    For ADEVT, N2HET1 and GIOB trigger sources, the connection to the MibADC1 module trigger input is made from the output side of the input buffer.

    Thanks and regards,

    Zhaohong
  • 0 in reply to Zhaohong Zhang
    Prodigy 80 points
    Thank you for the clarification. Those descriptions in the datasheet were unclear to me because they are worded in a way that leads me to believe they refer to an illustration of the pin I/O logic. No figure exists in the datasheet. Adding the following sentence to the datasheet would make the triggering event behavior crystal clear...

    "You can not trigger Mibspi by connecting the NHET pin to an external source. "