• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 744 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.

difference between DM365 and DM368 register values

aky wong
Prodigy 20 points
Other Parts Discussed in Thread: TMS320DM365

I use the same ubl for both dm368 and dm365 ,and i want to config different arm clock automatically.

if there any difference between the DM365 register values and DM368's ,

or can i distinguish DM365 from DM368 through register values? 

  • 0
    Guru 25210 points

    You can use the DEVICE_ID register for this purpose.

  • 0 in reply to Brian Boorman
    Prodigy 20 points

    I can't find this register,could you tell me the register address?

  • 0 in reply to aky wong
    Guru 25210 points

    aky wong said:
    I can't find this register,could you tell me the register address?

    I wonder if you read and/or searched the datasheet and user's manuals....

    For the DM365, the datasheet is here: http://www.ti.com/lit/ds/symlink/tms320dm365.pdf

    On Page 50 is a listing in Table 3-1 of the System Module Registers (DEVICE_ID is one of them). The PDF text also includes the link to the User's Guide (also here: http://www.ti.com/litv/pdf/sprufg5a)

    In that document, Page 138 (Table 89) describes the register contents of the DEVICE_ID register.

    The same information is available in the DM368 datasheet, but I'll leave it up to you to find it.

  • 0 in reply to Brian Boorman
    Prodigy 10 points

    Dear Sir,

    We meet the same scenario.

    The DEVICE_ID looks the same either from ARM Subsystem user's guide or direct print of such register from DM365/DM368 device.

    I use regrw in linux to read register 0x01c40028 (DEVICE_ID), both DM365/DM368 got 0x8b83e02f.

    Does there any solution to automatically identify DM365/DM368 from chip registers?