• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 365 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.

MUX and expansion connectors

matteo lucarelli
Genius 3265 points
Other Parts Discussed in Thread: HALCOGEN

Hi,

I'm planning the connections required for a multi device application on a RM48HDK and have some questions:

  1. the SCI port are not reported on the expansion connector scheme. Do I have to use the PINMUX table to connect SCI_TX to HET1_13 and SCI_RX to HET1_6? In this case the connection ports 113 and 106 will change their function from HET to SCI?
  2. the MibSPI1 and MibSPI3 connection are reported in the HalCoGen PINMUX table as muxed with HET1 ports but in the expansion connector scheme they are labeled in different places. Following the previous point question what does this mean?
  3. the SPI4 port is not reported in the expansion connector scheme. Where can I access them?
  4. I'm currently using the HET1 port directy writing on DOUT register. To make this work I don't need to enable HET1 on the PINMUX table. Why?

Thank you.

  • 0
    TI__Mastermind 30845 points

    Matteo,

    The Terminal Functions section of the datasheet lists the various modules and which pins/balls those signals are available on.

    It also describes that the name of the pin comes from the primary/default function of that pin. These pin names are carried over to the connectors on the HDK.

    Here's an example:

    N2HET1[1]/SPI4NENA/USB2.TXEN/USB_FUNC.PUENO/N2HET2[8]                       23

    The above tells us that pin 23 can be used for any one of the above options. As the name is too long, in the HDK schematics, only the first name N2HET1[1] is listed. But the fact is that pin 39 of J11 is connected to Pin 23 of the device. Thus, if you need to use SPI4NENA instead, you will need to change the pin mux and you will still use pin 39 of J11.

    As N2HET1[1] is the default function of that pin, no pin mux configuration was necessary, thus it works.

    Hope this answers all your 4 questions.

  • 0 in reply to A Arora
    Genius 3265 points

    Thank you,

    Your answer clarifies almost everything except:

    1. I cannot found a list of the default functions. Can I simply assume the default function as the first listed? So when a pin/ball is described as "N2HET1[0]/SPI4CLK" its default function is "N2HET1[0]". Right?
    2. In the tables of the datasheet (par 2) the pins are identified using the label of the 144PGE/337ZWT while on the expansion connectors of the HDK the label are different. Where can I found the correspondence? Should I trust on the default function?

    Thank you



  • 0 in reply to matteo lucarelli
    TI__Mastermind 30845 points

    Matteo,

    You are correct in your assumption - The first listed name (N2HET1[0]) is the default function.

    Also, for the 2nd point, I'd stick to the default name of the pin.

    Regards,

    Abhishek