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

Does the TMS320f280x have serial number?

haiming pan
Prodigy 75 points
Other Parts Discussed in Thread: TMS320F28020, TMS320F280200

Does the TMS320f280x have serial number or  unique ID? and how to read it?

and how the parallel debug manager (PDM)  know the current MCU which is connected?

in the DSP280x_DevEmu.h, there is a stuction

struct DEV_EMU_REGS {
             union DEVICECNF_REG DEVICECNF; // device configuration
             union PARTID_REG PARTID; // Part ID
             Uint16 REVID; // Device ID
             Uint16 PROTSTART; // Write-Read protection start
             Uint16 PROTRANGE; // Write-Read protection range
             Uint16 rsvd2[202];
};

but there is no serial number.

thank

  • 0
    Prodigy 75 points

    Is there any one who can tell me about this question?

  • 0
    Intellectual 465 points

    The datasheet says the PARTID is located at 0x3D7FFF in the memory map.  Just read that area.

    Also in the datasheet under "3.5 Device Emulation Registers" you can see what device the PARTID translates to, and some other ID types.

  • 0 in reply to Daniel Bland
    Prodigy 75 points

    thank you!

    but there is no unique id.

    struct DEV_EMU_REGS {
    union DEVICECNF_REG DEVICECNF; // device configuration
    union PARTID_REG PARTID; // Part ID
    Uint16 REVID; // Device ID
    Uint16 PROTSTART; // Write-Read protection start
    Uint16 PROTRANGE; // Write-Read protection range
    Uint16 rsvd2[202];
    };

    this struct  include all the registers for Emulation, but the PARTID is not the serial number and it is the type of the MCU,such as: the value is 0x00c1 if the MCU is tms320f280200pt; and there is the other registers,such as CLASSID(the class of the MCU,such as:the value is 0x00c7 if the mcu is tms320f280200 or tms320f28020/22/26  ),REVID( the revion ID), those are not unique ids.

  • 0 in reply to haiming pan
    Prodigy 75 points

    I hope to find the identification number in the MCU, which is different between any two MCU. And  that can not be modified while programing.

  • 0 in reply to haiming pan
    Intellectual 465 points

    I am almost certain there is no unique ID between any two MCU's (of the same type).  You'd have to program one into the flash.

  • 0 in reply to Daniel Bland
    Prodigy 75 points

    Thank you very much!

    I think so that there is no unique ID.

    But I am  wondering, how the Parallel Debug Manager (PDM) to select the suitable MCU from those,  which connected to the same JTAG.

  • 0 in reply to haiming pan
    Intellectual 465 points

    The PARTID should be enough for the PDM, as all it needs to know is what MCU type it is.


    So like you said, the value of 0x00C1 is the MCU TMS320F280200pt.  Knowing that is enough for the PDM to configure itself.

  • 0 in reply to Daniel Bland
    Prodigy 75 points

    Just like this circuit, the JTAG is connected to two MCU. If the type of two MCU is TMS320F280200pt,How the PDM to configure itself.

    the figure is from "Hardware Design Guidelines for TMS320F28xx and TMS320F28xxx DSCs, spraas1b.pdf, page 10".

  • 0 in reply to haiming pan
    Intellectual 465 points

    I'm not entirely sure, but it would have to do with the EMU pins.  PDM does the synchronous debugging for you, but I don't know exactly HOW it does it. Like it says in the datasheet:

    When debugging systems that have more than one TI device defined, you are required to use the parallel
    debug manager (PDM), which provides a method of synchronous debugging of your multiprocessor
    application. If you have configured a multiprocessor system within CC_Setup, the PDM is automatically
    invoked when you start CC_App.
    For additional information on the emulation features see Emulation Fundamentals for TI's DSP Solutions
    (SPRA439), the Emulation Features section in TMS320C28x DSP CPU and Instruction Set Reference
    Guide (SPRU430), and the Designer Considerations for Using the XDS510 Emulator section in the
    TMS320F/C24x DSP Controllers CPU and Instruction Set Reference Guide (SPRU160).

    Maybe try those additional datasheets?