Hi,
I am trying to read the device descriptor table on a MSP430F5638 Rev D (1AAFSFTG4). I am using a CCS Version: 5.1.1.00031.
The only data i can read is 3FFF. Can anybody help me? Why i can not find the expected data?
Thank you
Alessandro Fulignani
I do not have a F5638. But I think:
(a) The MSP430 Tool Chains are flaky. Which Tool Chain did you use? Did you use one of the Tools to show the Device Descriptor? If so, what the tool tells you may not be real. You may need to write code to read it and show it.
(b) The User's Guide and Data Sheet may have mistakes and misled you to look at the wrong place. What did you try?
(c) You may have misunderstood something or made mistakes somewhere when you tried to read the Device Descriptor.
The Data Sheet SLAS650B.pdf (page 97, Table 68) says the Device Descriptor is at address 0x1A00 to 0x1A24. But page 17 Table 7 of the same document shows nothing in that address range.
The User's Guide SLAU208J.pdf (page 43, Section 1.11) says the Device Descriptor Type, Address of start of the structure, and Table are at 0x0FF0-0x0FF3, 0x0FF4-0x0FF7, and 0x1A00 to 0x1A7F respectively.
What did you do exactly?
Thank you for your answer.Sorry for my late, i was trying some experiment. Well i put all the available memory vectors, from 0x0000 to 0xFFFFF on the usart and then compared with some data that should be available on the DDT. I surrender on my devices, DDT does not exist.
Alessandro Fulignanicompared with some data that should be available on the DDT
The table 68 in the 563x datasheet shows position and content of the DDT. Most entries there are 'per unit'. As you can see, there is only a calibration tag, no tags for the other hardware components. Well, the table might be incomplete. It not even shows the end tag. And no calibration values for the references.
However, if you have XMS silicon (pre-release samples), they might indeed not contain a TLV.
_____________________________________Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.