• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 104 subscribers
  • Views 1005 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

sysbios_ind_sdk_2.1.1.2\sdk\examples\profibus_slave does not build

Ted Heying
Intellectual 470 points
Other Parts Discussed in Thread: PROFIBUS, AM3356, AM3359, SYSBIOS

Get the following error:

CDT Build Console [profibus_slave]

**** Build Finished ****
Buildfile generation error occurred..
Product 'SYS/BIOS' v6.41.4.54 is not currently installed and no compatible version is available. Please install this product or a compatible version.
Build stopped..

Problems

Errors (1 item)

Description Resource Path Location Type
Product 'SYS/BIOS' v6.41.4.54 is not currently installed and no compatible version is available. Please install this product or a compatible version. profibus_slave profibus_slave Problems

Warnings (2 items)

Description Resource Path Location Type
Build variable 'BIOS_CG_ROOT' cannot be resolved. profibus_slave properties Problems

Description Resource Path Location Type
XDCpath repository '/packages' cannot be found! Visit project's 'Properties > General > RTSC' tab to adjust the XDCpath. profibus_slave profibus_slave Problems

I had built and run this example with an older version of the SDK 01 01 00 10 without problem. I was directed to install SDK 2.1.1.2 because I need to also run the starterware mcspi flash example which i did w/no problem. Now I tried to run the profibus slave example with the newer SDK and got the errors above.

Our application needs to leverage both of these examples so it behooves me to evaluate them on our AM3359 ICE board before we design our AM3356 based board.

Actually I would like to port and integrate the profibus slave example into the mcspi flash starterware example as I wish to run the profibus stack w/out an RTOS. I'm not sure if this is possible. 

Does the profibus stack require use of the RTOS (SYSBIOS) as it is referred to? 

If so does it require the 2.1.1.2 SDK?

Need to use both SPI0 (connected to a flash device similar to the eval board) and SPI1 (connected to an energy mesaurement device) as well as the profibus stack preferably w/out an OS. But in the event I the profibus stack requires me to use the OS I need to know what version (hopefully the latest) as well as the version of the SDK itself (hopefully the latest).

If I can not get answers to these questions I will have to recommend that we choose another (non-TI) solution.

As you can imagine I am getting frustrated when out-of-the box examples DO NOT WORK!!!

  • 0
    TI__Guru**** 393215 points
    I will ask the ISDK team to look at this.
  • 0
    TI__Mastermind 32505 points
    Hi Ted
    I was able to build profibus_slave, without any issues, using sysbios_ind_sdk_2.1.1.1 (I will try later sysbios_ind_sdk_2.1.1.2) and CCS 6.1.2
    I think you just need to install sysbios 6.41.4.54 or check CCS can find this package. Please check you are installing SDK in a location where CCS can locate it (tipically C:/TI/ folder).

    About profibus_slave OS-less, It will require a good amount of effort converting it from sysbios stack to starterware..

    thank you,
    Paula
  • 0 in reply to Paula Carrillo
    Intellectual 470 points
    Was able to get the profibus_slave example using sysbios_ind_sdk_2.1.1.2 and CCS 6.1.2 after installing processor_sdk_rtos_am335x_2_00_01_07.

    What do you mean by "a good amount of work" converting profibus_slave to starterware? Is it just the example app that needs to be changed or does the stack itself reference the OS? So far it is the only component we need that requires the OS.

    Thanks,
    Ted
  • 0 in reply to Ted Heying
    TI__Mastermind 32505 points
    Hi Ted, libprofibus_stack is created using the same tools as profibus_slave application (including BIOS). Converting to a baremetal app and stack would require to change the application to a non-bios (task, timers, soc platform, among others, relies on bios). Also you will need to rebuild the stack lib. I am not sure about the changes inside the stack lib files, but the CCS stack lib project uses XDC platform definition from Sysbios (memory map, linked command, etc).

    Thank you,
    Paula
  • 0 in reply to Ted Heying
    TI__Mastermind 43121 points

    Hi Ted,

    Ted Heying said:
    What do you mean by "a good amount of work" converting profibus_slave to starterware? Is it just the example app that needs to be changed or does the stack itself reference the OS?


    Indeed the question here is how much use of our Bios modules does the stack make? I assume the best would be to ask TMG, the stack vendor. Assuming that many of the industrial stacks originate from MCU world, they are usually not relying on a lot of RTOS features. You need to get the stack sources from them anyway.

    The example code in the IA-SDK also points in that direction. There are only a few tasks that I could identify here (I am not a Profibus expert...). Two of them are for UART and Timer! Of course interrupt API would change slightly. I could not find Semaphores, Queues, Gates or other advanced stuff.

    If you are rewriting the application anyway I assume it could be converted to bare metal. It is more a matter of testing. Compiling stack and driver layers with different compile/linker options should be no issue I assume.

    But on the other side you may just keep Sys/Bios to benefit from the features. E.g. ROV and UIA are great tools for debugging. And Bios does not cause a huge overhead too. You may later extend your app easily by adding more tasks.

    Just my 2 cents...

    regards,