• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 83 subscribers
  • Views 1086 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.

RTC code for CCS

Terry16065
Expert 1185 points
Other Parts Discussed in Thread: MSP430F5418

Some time ago, we got a code snippet (RTCASM.s43) to fix the RTC problems with the MSP430F5418 we have been using.

Now the 5418A version is available, and IAR wants $$$ to upgrade to support it, so we've decided to give Code Composer a try, and see if our source will move without too many problems. 

We've downloaded the Code Composer Kickstart edition, and we're having problems with the RTC include file....which internally states that it is specific for the IAR system.....

Where can we get the equivalent of this file for Code Composer?
Or is there some other trick we need to know about?

  • 0
    Expert 2840 points
    Can you post the RTC file that you want to move to CCS and the error? I think that you will need to translate your RTCASM.s43 into syntax of the CCS asembler, it is different than IAR. Some language costructions must be changed when you move.
    Regards,
    Piotr Romaniuk, Ph.D.
    ELESOFTROM
  • 0
    Guru 12160 points
    The 'A' revisions fixed the RTC bugs. So you don't need the special asm code anymore. -- Jeff
  • 0 in reply to Jeff Tenney
    TI__Guru* 79801 points

    Hi Terry,

    To clarify: Are you using the 5418 still, or have you moved to the 5418A? If you have moved to 5418A, then Jeff is correct, you will not need the workaround anymore. If you are still trying to use the 5418, then try the RTC_Workaround.zip package attached. This includes versions for both IAR and CCS.

    UPDATE: Later testing has confirmed that the 54xxA devices are indeed affected by RTC3 and will still require the workaround. Please see the latest versions of the errata documents.

    Regards,

    Katie

    RTC_Workaround.zip
  • 0 in reply to Katie Pier
    Expert 1185 points

    Katie,

    Yes, it is the A version so we should be good.

    Terry

  • 0 in reply to Katie Pier
    Prodigy 215 points

    Hi Katie...

     

    Our problem is that we are using both the A and NON-A versions (until we use up inventory, anyway), and have many hundreds non-A units in the field with a RS-232 bootloader installed for upgrades...so at a minimum we need to be able to compile our code for both versions, generate the .TXT file, and disseminate it to clients to upgrade their firmware as needed....Ideally we'd like one file that detects the "A"-ness of the CPU and execute the RTC Fix snippet or not....

    Darn legacy issues!

     

    I'll pass your fix package to our firmware guy, and we'll see how it goes....Stay tuned

    Regards,

    Kelly

     

  • 0 in reply to William Borsum
    Guru 227245 points

    William Borsum said:
    Ideally we'd like one file that detects the "A"-ness of the CPU and execute the RTC Fix snippet or not....

    It's not only the RTC. The 'A' devices have a REF module which the non-A don't.
    So you need to disable the REF module to have non-A ADC code running properly.

    What you can try to detect the A devices is to check the existence of the reverse CRC registers, which the As have and the non-As don't. Feed two bytes into the CRC module and check the reverse result. If it is corrent, it's an A, if it is nonsense, it is a non-A.

    However, you can also check the TLV structure.

    at 0x01a04, you'll find the device ID. It is 0x54 0x38 for the 5438 (big endian and hex/BCD!) and 0x54 0x37 for the 5437 etc.

    On the A devices, the datasheets list 0x05 0x80 for the 5438A, 0x04 0x80 for the 5437A etc. (little endian and enumerated). Strange numbering..

**Attention** This is a public forum