• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 81 subscribers
  • Views 600 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Location of EMACID of F28M36x in OTP

Markus Tamas
Intellectual 620 points
Other Parts Discussed in Thread: CONTROLSUITE, F28M36P63C2

Hi All,

I bumped into a problem while I was porting my F28M35x firmware code to the newer F28M36x. The problem is that I can't get the device MAC address on the new microcontroller. On F28M35 the MAC address of the device was programmed in the OTP at the following locations:

  • EMACID0 = 0x680810
  • EMACID1 =  0x680814

And it worked well. However in the F28M36 TRM (SPRUHE8) I found some (perhaps) controversial facts. The device MAC address also should be stored in the same location (page 1546), but in this new device a new MAC address field has been also appeared (page 540).:

  • EMACID[31:0] = 0x681010
  • EMACID[63:32] = 0x681014

The CCSv6 supports the OTP programming for the latest addresses, but in the latest controlSuite in the F28M36x_M3 CMD files there are the previous addresses yet.

So I'm a bit confused regarding the MAC address of the newer microcontroller. Do I have to handle two types of MAC address now? If so, how can I program the earlier addresses? Or it is just a typo in the device TRM and in case of F28M36x the new address is 0x681010 and 0x681014?

Thank you very much in advance!

Best Regards,
Tamas

  • 0
    TI__Guru** 109165 points

    Hi Tamas,

    On F28M36x device,  address of OTP locations have changed. It starts from 0x681000 instead of 0x680800 (like in F28M35x).  That's the reason address for EMACID in OTP are changed to "0x681010 & 0x681014" for F28M36x.

    Thanks for your feedback on TRM document and controlSUITE. We'll make appropriate changes in next release.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru** 109165 points

    Hi Tamas,

    The page number you mention are from old TRM. I was able to find the issue on different page number in latest TRM .

    I would suggest to use the latest TRM from WEB because there will be many updates/correction in new TRM which will be missing in old TRM. 

    Also which linker cmd file you are referring here. Could you send me the path of the file in controlSUITE.

    Regards,

    Vivek Singh

     

  • 0 in reply to Vivek Singh
    Intellectual 620 points

    Hi Vivek Singh,

    Actually, I checked SPRUHE8B also, but I sent you accidently the old TRM page numbers. Is the SPRUHE8B TMR the latest one?

    I am referring to the \controlSUITE\device_support\f28m36x\v203\MWare\cmd\F28M36P63C2_m3.cmd file. But I think that all CMD files in this folder contain the old OTP address (0x00680800).

    Best Regards,

    Tamas

  • 0 in reply to Markus Tamas
    TI__Guru** 109165 points

    Hi Tamas,

    Yes, SPRUHE8B is latest TRM.

    Thanks for providing the required info.

    Regards,

    Vivek Singh