• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 181 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.

AM625: EVM SK-AM62x has pin TEMP_DIODE_P pin while same is not available into datasheet

Aditya Singh
Intellectual 280 points
Part Number: AM625

Hi E2E Team,

EVM SK-AM62x has pin E7 as "TEMP_DIODE_P" and NC into design while into AM62x processor datasheet has pin E7 as "MCU_RESETz" for ALW package. Please let us know your thoughts on the same.

Regards,

Aditya

  • 0
    TI__Guru**** 189879 points

    Hello Aditya

    Thak you for the quey.

    The EVM uses 13 mm x 13 mm, 0.5-mm pitch, 425-pin FCCSP BGA (ALW)

    Please check for this package in the daasheet.

    Please take the pin naming in the datasheet as the pin name and function.

    Regads,

    Seenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    Intellectual 280 points

    Hi Kallikuppa,

    Thanks for your response.

    I didn't found "TEMP_DIODE_P" signal into AM625 Datasheet. Pin diagram for ALW package ( 425 pin FCCSP BGA) on page no. 9.

    As per datasheet E7 pin is reserved and must be left unconnected. Same has been done into EVM SK-AM62x.

    Is there any particular reason to provide the name of the signal at pin E7 as "TEMP_DIODE_P" into the schematic of EVM SK-AM62x.

    Regards,

    Aditya

  • 0 in reply to Aditya Singh
    TI__Guru**** 189879 points

    Hello Aditya

    Thank you for the note.

    Any time there is differences in collaterals, it is always recommended to follow the datasheet for pin naming and usage recommendations.

    EVMs are evaluation platforms and may not represent a proper system implementation.  In many cases, the EVMs are partially or completely designed before we release the processor for fabrication.  This is done so the hardware platform is available when first silicon arrives.  We may learn new device requirements during processor bring-up and bench validation.  If so, these new requirements may not be accounted for in our hardware development platform.

    Regards,

    Sreenivasa