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.

F2812 Boot Code

Other Parts Discussed in Thread: TMS320F2812

1.    What is the version of Boot code present in TMS320F2812 DSP?

2.    How can you identify the version of boot code software present in DSP?

3.    How does TI manage the changes in Boot code if any?

4.    Incase of any error found in boot code, how will TI handle the changes and maintain the version numbering?

regards

 

  • Himansu Shah said:
    1.    What is the version of Boot code present in TMS320F2812 DSP?

    For F281x we have never updated the ROM.  Version 1.

    Himansu Shah said:
    2.    How can you identify the version of boot code software present in DSP?

    The version and release date (month/year) are both embedded in the ROM itself.  The locations are documented in the boot ROM reference guide.  For the F281x, the document is www.ti.com/lit/spru095 section 2, page 11.

    Himansu Shah said:
    3.    How does TI manage the changes in Boot code if any?

    We realize any change will cause many of our customers to update their code and/or retest/requalify.  For this reason, changes after TMS or Rev A are not an option for us.

    Up until now, no changes have been made after silicon goes to TMS.  For Piccolo, Rev A will have an update, and this has been documented in the errata.

    Changes are documented in the errata and the boot ROM guide.

    Himansu Shah said:
    4.    Incase of any error found in boot code, how will TI handle the changes and maintain the version numbering?

    In the case of 281x the bug would be documented in the errata.  As I mentioned before changes after TMS or Rev A are not encouraged.

    In cases were the device is being sampled, the version in the ROM will be increased by 1 (0x001, 0x0002 etc) or a letter added and the date in the ROM will be changed appropriately.    In one case we had a minor change that was identified before the code went to silicon so the ROM version number has a letter (ie 0x0B01).  These are documented in the reference guide.