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

TMS570LC4357: TMS570LC4357: Is it possible to Use either N2HET2 terminal as output

S. Grimm
Prodigy 40 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN

Dear Sir/Madam,

I am using the TMS570LC4357 Hercules safety MCU development kit. I am having trouble with using many of the N2HET2 bits as GIO outputs on their default terminals. An example here is N2HET2[09], the default ball is L16 and the alternate ball location is K17. When I mux N2HET2[09] to K17 I am able to drive it as an output without any issues, however when I try to use it unmuxed I am unable to drive output on default terminal L16 with otherwise the same settings.

The datasheet is a little confusing on whether it is even possible to use L16 as an output. Ball L16 is not in the output mux table (6-1 in the datasheet) but I had interpreted this to mean that while this was not a muxed ouput pin, it could still be used as an output. 

Could you confirm whether or not it is indeed possible to use L16 as an output? If it is possible what could I be missing in Halcogen? Or could this be related to the Hercules development kit? Is it the same for many of the other pins in N2HET2?

Kind regards,

S Grimm

  • 0
    TI__Guru**** 186226 points

    Hello,

    Both L16 and K17 can be used as N2HET[9] output. L16 will show the N2HET2[9] signal regardless of the pinmux configuration for K17.

    Please make sure the pin is configured as OUTPUT from HDTDIR register.

  • +1 in reply to QJ Wang
    Prodigy 40 points

    With some help from Ti support over the phone I was able to pinpoint the problem. It turns out that the pin labelled L16 on the Hercules HDK I/O header is not actually physically connected to L16 of the MCU. I tested my code on the launchpad development board which does have L16 connected and was able to drive the output correctly. 

    Perhaps it would be wise to remove labels for unconnected pins on the Hercules IO headers in the future to prevent headaches, In any case thanks for the quick support.