• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 589 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.

TMS320F28027F: FAST ROM configuration identification / version information

Jack Cochran
Prodigy 40 points

Part Number: TMS320F28027F
Other Parts Discussed in Thread: MOTORWARE

Greetings,

We have a pre-existing InstaSPIN-FOC motor controller application for the 28027F, and we now find ourselves needing to qualify it under DO-178C standards, at software level D.  At level D, we plan to verify that our application, together with the InstaSPIN library code and the FAST ROM, satisfy our motor control needs through integrated functional verification tests.  At level D, we can do this without access to the underlying source code--the verification tests will show that a particular instance of the binary software controls the motors in a satisfactory manner.

My question is:  Is there some way to know when the contents of the FAST ROM have changed?  Does the ROM get periodic software updates that ship on newer chips, or is it static for a given silicon revision?

The reason we are interested is that if the ROM software were to get an update after our product is qualified and in the field, then we would need to recheck our verification tests to show that there is no adverse effect on the motor control performance in our application.

  • 0
    TI__Guru* 93800 points

    Hello Jack,

    Jack Cochran said:
    Does the ROM get periodic software updates that ship on newer chips

    No, the ROM has not been updated on this device since it went into production (~2013).  It is disruptive to customers to modify the ROM so it is typically not done after a device goes into production unless there is a very dire need to do so.  (It is also expensive to do!).  

    Jack Cochran said:
    Is there some way to know when the contents of the FAST ROM have changed?

    There is a function in the FOC API that retrieves the version:  CTRL_getVersion ()  This could be used by SW to check for a revision. 

    There is also an overall ROM version which has not changed since first silicon (Ref Bootloader information in the TRM - Version and checksum information).

    Let me know if there is any additional information that will help. 

    Regards

    Lori

  • 0 in reply to Lori Heustess
    Prodigy 40 points

    Hello Lori,

    Are you saying that the boot ROM checksum, from 0x3FFFBC-0x3FFFBF (TRM section 2.4.1) also covers the FAST ROM area (0x3FC000-0x3FE000 [spruhp4, figure 7])?  That would be quite excellent. 

    I was previously thinking that CTRL_getVersion() maybe reported on version information for the non-ROM parts of the library.  But looking at the libraries in the Motorware SDK, it appears that on 2802x, CTRL_getVersion() may rely on information that comes from the FAST ROM area after all.  If so, that would make it useful for this purpose as well.

    I certainly understand the time and expense that goes into patching software on a production part that is already widely deployed.  I believe this is really more of a paperwork and compliance issue for us, rather than a practical concern.

    Thank you,

    Jack Cochran

  • 0 in reply to Jack Cochran
    TI__Guru* 93800 points

    Jack Cochran said:
    Are you saying that the boot ROM checksum, from 0x3FFFBC-0x3FFFBF (TRM section 2.4.1) also covers the FAST ROM area (0x3FC000-0x3FE000 [spruhp4, figure 7])?  That would be quite excellent. 

    Unfortunately it is just the general ROM and doesn't includes the fast ROM area. 

    Jack Cochran said:
    I was previously thinking that CTRL_getVersion() maybe reported on version information for the non-ROM parts of the library.  But looking at the libraries in the Motorware SDK, it appears that on 2802x, CTRL_getVersion() may rely on information that comes from the FAST ROM area after all.  If so, that would make it useful for this purpose as well.

    I will double check this with a colleague who is more familiar with the FOC software and get back to you early next week.

    Jack Cochran said:
    I certainly understand the time and expense that goes into patching software on a production part that is already widely deployed.  I believe this is really more of a paperwork and compliance issue for us, rather than a practical concern.

    Understand.  

    Best Regards

    Lori

  • 0 in reply to Lori Heustess
    TI__Guru* 93800 points

    Jack,

    My colleague confirmed that the information comes out of the ROM itself for CTRL_getVersion().

    Regards

    Lori

  • 0 in reply to Lori Heustess
    Prodigy 40 points

    Lori,

    Excellent. I believe we can proceed on this basis.  Thank you so much for your support.


    Jack