• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 422 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.

Can BIOS6 be abstracted from RTSC architecture?

Chen Neville54361
Intellectual 315 points
Other Parts Discussed in Thread: SYSBIOS

Hi all,

as you know, BIOS6 is designed on RTSC architecture. If we use BIOS6, we should use xdc tools to compile BIOS6 RTSC packages in our CCS4 project. I think it's the same in CCS5. Does anyone tell me whether BIOS6 can be abstracted from RTSC architecture? Then we don't use xdc tools to compile BIOS6 in the project which is like in CCS3.3? Thanks a lot.

Best regards,

Neville Chen

  • 0
    TI__Mastermind 37985 points

    Neville,
    SYSBIOS 6 has to be configured in order to be used in an app, and for that you have to use XDCtools. There could be a scenario where you would build a SYSBIOS 6 configuration, and then someone else would use that configuration in their app without XDCtools. There is a some experimental support for that, but you would have to tell me what is your use case, so I can tell you if that applies to you.

  • 0 in reply to Sasha Slijepcevic
    Intellectual 315 points

    Sasha,

    In CCS4, we configure SYSBIOS6 and XDC components in .cfg file (which is corresponding to tcf file in CCS3.3) in our project, and CCS4 IDE will invoke XDCTools to build this configuration and generate a package for our app, and then CGT will build our app with this generated pacakge and create a final output file(.out file). Since SYSBIOS6 is designed on RTSC architecture and it's XDCTools to build RTSC component. Here I wonder whether SYSBIOS6 can be abstracted from RTSC architecture and then we don't need use XDCTools to build SYSBIOS6 component? Cause RTSC component's build with XDCTools is a little bit complicate and lasts long time and this makes efficiency a little bit low.

    For "There could be a scenario where you would build a SYSBIOS 6 configuration, and then someone else would use that configuration in their app without XDCtools.", my understanding is that I can crreate a seperate SYSBIOS6 configuration project w/o app code and build it with XDCTools, someone else would  depend on this SYSBIOS6 project to use SYSBIOS6 configuration. Then he doesn't need to build SYSBIOS6 configuration with XDCTools. Is my understanding correct? Thanks.

    Best regards,

    Neville Chen

  • 0 in reply to Chen Neville54361
    TI__Mastermind 20805 points

    Which version of SYS/BIOS are you using?  The whole_program link step we used in SYS/BIOS 6.31 and earlier is very slow and we're moving to a more traditional build model.

    You might want to try SYS/BIOS 6.32.04 which improves the build time.   You also need corresponding XDCtools and IPC which are referenced on the left side of the link.  Install all 3 in default directory and CCS should discover them the next time you start CCS.  Change your project to use the new version of these components and your build should improve.   You should use 'release' profile instead of 'whole_program' profile when you move to 6.32.  More info in the release notes and User's Guide.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/index.html

    -Karl-

  • 0 in reply to Karl Wechsler
    Intellectual 315 points

    The SYSBIOS version I used is 6.31.04.27.  It's shipped with CCS4.2.2 release version. Here I have several questions. Thanks.

    1. What do you mean "a more traditioal build model"? Is it referred to "release" profile?

    2. Can SYSBIOS6.32.04 be used in CCS4.2.2?

    3. Regarding the question in the topic, is the answer "No"? Can I make this conclusion?

    Best regards,

    Neville Chen

  • 0 in reply to Chen Neville54361
    TI__Mastermind 37985 points

    Chen Neville54361 said:

    Sasha,

    In CCS4, we configure SYSBIOS6 and XDC components in .cfg file (which is corresponding to tcf file in CCS3.3) in our project, and CCS4 IDE will invoke XDCTools to build this configuration and generate a package for our app, and then CGT will build our app with this generated pacakge and create a final output file(.out file). Since SYSBIOS6 is designed on RTSC architecture and it's XDCTools to build RTSC component. Here I wonder whether SYSBIOS6 can be abstracted from RTSC architecture and then we don't need use XDCTools to build SYSBIOS6 component? Cause RTSC component's build with XDCTools is a little bit complicate and lasts long time and this makes efficiency a little bit low.

    For this scenario, the answer is no. There is no tool other than XDCtools that can configure SYSBIOS 6.

    Chen Neville54361 said:

    For "There could be a scenario where you would build a SYSBIOS 6 configuration, and then someone else would use that configuration in their app without XDCtools.", my understanding is that I can crreate a seperate SYSBIOS6 configuration project w/o app code and build it with XDCTools, someone else would  depend on this SYSBIOS6 project to use SYSBIOS6 configuration. Then he doesn't need to build SYSBIOS6 configuration with XDCTools. Is my understanding correct? Thanks.

    When you configure SYSBIOS 6, you use XDCtools to create a configuration, and then a compiler and a linker consume the files from the created configuration. So, you need XDCtools only in the first step. Normally, both steps are executed in CCS 4, on the same host and immediately one after another. But, if you wanted to run these steps on different hosts you would have to use an experimental XDCtools package xdc.tools.closure. To get that working, you would have to create a gmake project in CCS 4, or to build outside of CCS 4. This flow is not tested much, so you may hit some bumps, but if that workflow is exactly what you need, you may want to try it.