• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 574 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.

HET25 is not able to function as general purpose input

Markus Uhle
Prodigy 190 points
Other Parts Discussed in Thread: HALCOGEN

Hi,

on our RM46L852ZWT (BGA-package), we connected HET1-25 (Ball M3) to a 3,3V input signal. The input pin always provides a "0" and seems not to work as expected.

When we debug the program and configure this port to output (only change the bit 25 in the direction register), then we can measure High and Low signals corresponding to the DOUT register.

We even see the corresponding signal on the DIN register.

When we switch back to "input" than we just can see only a "0".

This behaviour seems to be on 5 different boards.

Need help. Maybe some special  undocumented "please set bit 33 in the xyz register".

By the way:

The documentation of the N2HET registers in the Technical reference manual" is completely blank !!!!!!!!!!

Regards,

Markus

  • 0
    TI__Genius 11645 points

    Markus,

    By default the input to any module is from the dedicated input pin, unless you modify the pinmux registers to select the multiplexed pin.

    Can you please check on the input multiplexing registers to make you have not modified anything unintentionally, (PINMMR25[16]).

    Best Regards,

    Karthik.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Prodigy 190 points

    Hi Karthik,

    I checked the PINMMR25[16]. It is '0'.

    I read the technical ref manual again. Only the output-functions of a pin are multiplexed. The input is broadcasted to all connected modules. Maybe I am doing wrong something else.

  • 0 in reply to Markus Uhle
    TI__Genius 11645 points

    Hi Markus,

    Can you pls get me the contents of both these registers,

    1) PINMMR7

    2) PINMMR25 

    Also pls help me with the exact document number/version you are referring to as well. Thanks.

    Best Regards,

    Karthik.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Prodigy 190 points

    Hi Karthik,

    all Nhet1 registers are '0' except:

    GlbCtrl 0x003001

    Pfr 0x0000503

    IntFlg 0x0001fffe

    Dir 0xd1085500

    Din != 0

    DOut 0x80080000

    DSet 0x80080000

    DClr 0x80080000

    PDis 0x0f020000

    PSel 0x87021000

    ParCtrl 0x0000000a

    Are there known issues in the silicon? We are using xRM46L852ZWTT YFA-26ATT4W GI.

    We are using the Technical Reference Manual "SPNU514" from September 2012. Starting at page 991

    to page 1023 there are 33 undocumented HET registers.

    Regards,

    Markus

  • 0 in reply to Markus Uhle
    TI__Genius 11645 points

    Hello Markus,

    There is no known issue, but I just wanted to make sure about the documentation you are referring to so that I'm in synch.

    In the meanwhile I suspect this to be an input pinmux problem and since your O/P functionality is working and just changing this to I/P on the dir pin should be good as far as HET is concerned.

    So pls let me know the contents of the following pinmux registers when you are doing this test,

    PINMMR07 = ??

    PINMMR25 = ??

    Best Regards,

    Karthik. 

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Prodigy 190 points

    Hi Karthik,

    sorry... I forgot the Pinmux registers... here they are:

    Pinmmr07 = 0x00020200

    Pinmmr25 = 0x01000100

  • 0 in reply to Markus Uhle
    TI__Genius 11645 points

    Hi Markus,

    Can you pls try the following settings before you try to use that pin as input,

    Pinmmr07 = 0x00020200

    Pinmmr25 = 0x01010100

    Let me know if that work's. I will try to dig a little more in to documentation if this works for you.

    Best Regards,

    Karthik.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Prodigy 190 points

    Hi Karthik,

    this works !!!

    We checked, why this bit is not set by HalCoGen and it seems that there are some bugs in the generated C-code and/or in the conflict-checking mechanism of the HalCoGen user interface.

    I am wondering, because in the datasheet you can read, that all inputs are broadcasted and need no multiplexing on the BGA package. This seems not to be the case.

    Many thanks for your help.

  • 0 in reply to Markus Uhle
    TI__Genius 11645 points

    Hello Markus,

    I still believe the documentation assumes you leave the default pinmux configuration as such to route the inputs from dedicated pin's to reach the module's in 337 BGA configuration. May be you are modifying the pinmux registers by overwriting this bit which I suggested in the end and that's why you are seeing this issue.

    If this answers your question, then please click verify answer below to close this thread. Thanks.