• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 426 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.

RTOS/PROCESSOR-SDK-DRA7X: xdctool binaries version different than file versions

John H. Gardner
Guru 52601 points
Part Number: PROCESSOR-SDK-DRA7X
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

I have a customer who is using: bios version 6.46.05.55 and xdctools version 3_32_01_22_core.

During program creation, the customer had binary output that have a different version of xdctools.

It contains verion xdctools_3_30_06_67_core.

Earlier today, the customer downloaded and installed BIOS from link http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sysbios/6_46_05_55/index_FDS.html

I believe they used the following command:

$ cd /bios_6_46_05_55

$ grep xdctools_3_30_06_67_core -rn | wc -l 1738

$ grep xdctools_3_32_01_22_core -nr | wc -l 0

They could not find any information about xdctools_3_32_01_22_core.

Ultimately, the question is they are trying to find out why they have different verson of xdctools_3_30_06_67_core in the built program.

The FAE noted that in all version of the XDC tool, he was seeing the Core-mem file.  So, he thinks this is possibly a build issue with *.cfg, but we decided to float to the e2e community.  

 

  • 0
    TI__Guru*** 125430 points
    Here's the explanation of this behavior from Karl Wechsler of our sysbios kernel team (Thanks, Karl!):

    This is expected. SYS/BIOS is made up of a number of components that we manage locally. Some are built and left on the shelf untouched (except for including them in a new SYS/BIOS release).

    Some of those components are built with older XDC tools. We archive the versions in some metadata files within these components.

    In many cases, new versions of XDC tools can consume components built with old versions of XDC tools. We try to be backwards compatible, so that existing/stable components can be used with newer version of XDC tools w/o having to be rebuilt and retested. In this case, XDC 3.32 can be used with components that were built with 3.31 and 3.30.

    The converse is not true. We do not support components that are built with 3.32 to be consumed with an older 3.31 or 3.30.

    The rule of thumb is that customers must use a version of XDC tools that is >= the version from all components.

    Sometimes we break compatibility completely. In this case, all components would have to be rebuilt with a new common baseline and the game would begin again.
  • 0 in reply to Brad Griffis
    TI__Guru 52601 points
    Brad (and Karl) - thanks for the quick responses!
  • 0 in reply to John H. Gardner
    TI__Mastermind 42515 points
    Hi John,

    I will close the thread, if you have further questions on this topic, you can write a post here to reopen it.

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    TI__Guru 52601 points

    Yordan - thanks. Go ahead and close for now.