• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 229 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.

LAUNCHXL-F280049C: revision identification, XDS110 MCU

Wolfgang R.
Intellectual 366 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: TM4C1290NCPDT

Tool/software:

Hi all,

I have 2 new LAUNCHXL-F280049C boards we want to use for a proof-of-concept.

According to https://www.ti.com/lit/ug/spruii7b/spruii7b.pdf?ts=1732015845334&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FLAUNCHXL-F280049C there are revisions A and B of this board:
"Revision A ... can be identified by the "MCU025A" silkscreen labeling on the back side of the EVM between the BoosterPack Connector site 1 towards the top of the board."
"Revision B ... can be identified by the "MCU025B" silkscreen labeling on the back side of the EVM."

My silkscreen says "MCU025B" - Revision B.

The abovementioned doc also states "Revision B ... Enhancements: ... XDS110 MCU (U2) TM4C129x device replaced with MSP432E401 device"

But my supposedly Revision B board is populated with a TM4C1294 for U2, pointing to revision A.

I'm asking because I'd like to know whether I have a revision B (or later) board that has all the issues of Revision A fixed, or maybe an intermediate revision A/B with issues.
Also, we need the exact schematics to match our boards.

Thanks,
Wolfgang

  • +1
    TI__Mastermind 19531 points

    Hi Wolfgang,

    Thanks for reaching out on E2E. There is no intermediary version between Revision A and B, you can refer to the Revision lettering on the board to safety know the revision.

    I'm not sure why the TM4C -> MSP432 change is listed on the revision, actually both part numbers refer to the same device (i.e. they are pin-to-pin swappable) and it's just a matter of inventory/stock supply at the time of the EVM board manufacturing that determines what device gets populated on the board as the debugger. My guess is that this was documented to add clarity to the other parts of the user guide where TM4C may be mentioned. In any case, the debugger functions the same either way. It does look like you have a Revision B board

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    Intellectual 366 points

    Thanks for the clarification, this helps.

    Side note: I wasn't aware that TM4C and MSP432 are the same.
    So it went Stellaris -> Tiva -> MSP432. As we still have a TM4C1290NCPDT design in production, this information might become useful if we ever run into supply problems.