• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 382 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.

HET1 not selected in PINMUX but IO working great

Frank Freihube
Intellectual 350 points
Other Parts Discussed in Thread: RM48L952, HALCOGEN

Hi,

I'm working with a RM48L952 using the development board TMDXRM48HDK.

I've used the HET1 module to switch the LEDs on/off wich works pretty fine. Today I've seen that the HET1 module is not selected in the PINMUX-Section in HALCoGen(nothing is selected in PINMUX at all) they are only set as output pin in HALCoGen in HET1->Pin x-y.

5 of the 8 LEDs are using the HET-Pins 17, 25, 27, 29 and 31 who are not muxed to the chips outputs by default.

My question is why those LEDs are working when they are not selected to get muxed?

  • 0
    TI__Guru 59540 points

    Hello Frank,

    Can you upload your Halcogen project for me to have a look at? Also, please let me know which version of Halcogen you are using. Thanks.

  • 0 in reply to Chuck Davenport
    TI__Guru 68920 points

    Frank

    Please do send your config to Chuck.


    However - if the HET pin that is working great is the "Default" function for the pin, then if one of the valid one-hot selections is not programmed into the pinmux field - the hardware is designed to pick the "Default" function.
    This is a robustness feature.

     

  • 0 in reply to Anthony F. Seely
    TI__Guru 59540 points

    Hello Frank,

    I cross checked the IOMUX table in spnu503B and all of the N2HET1 channels you mentioned are brought out to pins by default in the BGA device that is included in the kits.

    N2HET1[17]  --> terminal A13

    N2HET1[25]  --> terminal M3

    N2HET1[27]  --> terminal A9

    N2HET1[29]  --> terminal A3

    N2HET1[31]  --> terminal J17

    However, I see where the confusion comes in since these functions are also muxed behind other functions on some pins. This is due to multiple package availability where these functions are not brought directly to pin by default such as in the 144 pin TQFP PGE package. As Anthony stated, since these are brought directly to pins in the BGA package there is no need to touch the IOMM module for them to work.

     

  • 0 in reply to Chuck Davenport
    Intellectual 350 points

    Thank you for the fast response.

    It was an error on my side, i didn't expect that a pin which is not selected in PINMUX-Section is connected to any ball, but most of the NHET-Pins are connected to a special ball if they are no't muxed to another one.