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.

Pin assignment problems in pinmux

Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN

Tool/software:

Hello,

We are developing our project with TMS570lc4357. We are using TMS570LC4357 Hercules Development Kit (HDK) to develop this project. We had some problems while working on the project. We share these problems with you. We would be very happy if you can help us.

To access the N2het2[02] signal from the D7 pin, N2het2[02] was selected in the pin muxing section of Halcogen as in PICTURE 01. Then the D7 pin was assigned to the n2het[02] signal in the Input Pin Muxing section. As a result, we can see the correct signal on N2het2[03] activated with the same configuration, but we cannot see any signal on N2het[02]. When we look at the TMS570LC43x Hercules Development Kit (HDK) User's Guide (Rev. A) page 17, it is seen that the D7 pin is the pin of the EMIF_ADDR[03] signal as shown in PICTURE 00. Could there be a problem here?

According to Pinmux, it can select N2het2[27] signal for P5 pin. Besides, the signals that can be selected are EMIF_DATA[11] and ETMDATA[27]. The P5 pin is assigned the N2het2[27] signal as in PICTURE 03. Under normal conditions, it is a signal that cannot be observed because there is no P5 pin on the connectors, but as we see in PICTURE 00, it seems that the EMIF_DATA[11] signal can be read on the P4 pin. From here, under normal conditions, the N2het2[19] signal should be read on the P4 pin, while the N2het2[27] signal is seen. Could there be a problem here?

Again, looking at pinmux, N2het2[27], EMIF_DATA[11] and ETMDATA[27] can be selected for pin N5. From here, the N2het2[27] signal is assigned with the correct configuration as in PICTURE 04. . Under normal conditions, it is a signal that cannot be observed because there is no N5 pin on the connectors, but as we see in PICTURE 00, it seems that the EMIF_DATA[11] signal can be read on the N4 pin. According to PICTURE 05, only the N2het2[18] signal should be output from the N4 pin, while in fact the signals of the N5 pin, N2het2[27], EMIF_DATA[11] and ETMDATA[27] are received. When this is tested, when the N2het2[27] signal is activated for the N5 pin, this signal can be read from the N4 pin. On the contrary, when the N2het2[18] signal is activated from the N4 pin, this signal cannot be received. Could there be a mistake here?

The pictures mentioned above are shown below.    

 

PICTURE 00

TMS570LC43x Hercules Development Kit (HDK) User’s Guide (Rev. A) page 17

 

PICTURE 01

 

PICTURE 02

 

PICTURE 03

 

PICTURE 04

Halcogen’s pinmux

 

PICTURE 05

TMS570LC4357 HerculesTm Microcontroller Based on the ARM® Cortex®-R Core datasheet (Rev. C) page 17

  • Hi Ataberk,

    Actually, i observed some typos in the HDK user guide and schematic:

    Here i highlighted the mistakes and i commented the right names:

    spnu597a.pdf

    3288.TMS570LC43_SCHEMATICS_REVE.pdf

    Example:

    If you verify the user guide J10 connector, here i highlighted the wrong pin names and in the comments i mentioned the right pin name.

    Similarly in schematic also i highlighted the wrong pin names for some pins and I commented the right pin names.

    We are sorry about these typo issues, i am raising a ticket to correct these issues.

    Actually, above schematic and user guide issues are interlinked, may be the user guide mistakes are due to the naming typos in the schematic only.

    Please verify these modifications, and hopefully this will solve your problems.

    For example:

    Regarding your first issue 

    You are correct D7 has the N2HET2[2] functionality but as you can see the corresponding D7 pin not terminated to anywhere in the board, so you cannot use this pin in this board directly.

    And also remember the 25th pin the J10 is not D7, and it is actually E7.

    --
    Thanks & regards,
    Jagadish.