• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 101 subscribers
  • Views 957 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.

TMS320C6748 SYS/BIOS Software Development Kit (SDK)

Pinakin Potdar
Expert 1050 points
Other Parts Discussed in Thread: TMS320C6748, OMAPL138, SYSBIOS

Hi, 

 

I downloaded the software for TMS320C6748 SYS/BIOS Software Development Kit (SDK). I then created a new project in CCS for IO_Stream example for OMAPL137 (not for DSP core but just for ARM 9 - single core). At the moment I just want to test the UART functionality of OMAPL137. I then selected all the RTSC options available. When I build this project it fails with the following 2 errors:

1.  fatal error #1965: cannot open source file "C:/...../Debug/configPkg/package/cfg/stream_pe9.h" 

2.  can't find the library 'lib/ti.targets.arm.rtsarm.ae9' specified by pakage ti.targets.arm.rtsarm. It was'nt found along the path '.....'.  

Is there something that I am missing here. I just want to build a UART example. 

 

  • 0
    TI__Mastermind 45025 points

    Hi Pinakin,

    Which hardware platform are you using?  Are you using the 6678/OMAPL138? (note this is a different h/w platform than the OMAPL137).

    Steve

  • 0 in reply to Steven Connell
    Expert 1050 points
    Hi Steve,

    Currently I am just trying to build the project. I do not have the hardware with me right now but I just wanted to get it built and set up.

    Pinakin
  • 0 in reply to Pinakin Potdar
    TI__Mastermind 45025 points

    Hi Pinakin,

    I see that Ashish was already helping you in this other thread and had recommended that you download the 6748 SDK and to port those drivers to work with the OMAPL137.  I agree that this is the best course of action for you, as there was never any SDK for the OMAPL137 with drivers for SYS/BIOS.

    I also saw that you found the drivers you want for the OMAPL137 but for DSP/BIOS.  You should be able to leverage the code of those drivers to port the 6748 SDK's drivers.

    Regarding the build errors you are seeing, do you see any errors related to the project's configuration file (*.cfg file)?  The error for the missing file "stream_pe9.h" is typically due to an error in the *.cfg file, since that header file is generated from the configuration settings made in that file.  It also seems like you may be missing some compiler tools.

    Is there a getting started guide of sorts that came with the SDK?  If so, I'm hoping that there is a section that details the software you need to set up prior to building any examples.  Can you please look for such a section and verify that you have done all the necessary set up required for using the SDK?

    Also, please make sure that you first build one of the SDK's standard examples, which should be for the OMAPL138 or 6678.  After you have that building, then you could try to move on to porting it to the OMAPL137.

    Steve

  • 0 in reply to Steven Connell
    Expert 1050 points
    Steve,

    I downloaded and tried the newer version of SysBios and selected the new version in my project. This seems to build fine with the code.

    I have not finalized to go with OMAPL137. I will probably use OMAPL138 instead as it seems similar to 137 and also has better power consumption. My concern is about developing new drivers. I still could not find any documentation for implementing a new driver in SYSBIOS. There seems to be a template for these drivers. There are package files, xdc files and cfg files. Do these files need to change. If there are any steps to implement drivers then that will be of help.

    Pinakin
  • 0 in reply to Pinakin Potdar
    TI__Mastermind 45025 points

    Pinakin,

    I'm not sure if there's a good doc on implementing a new driver.

    Pinakin Potdar said:
    There seems to be a template for these drivers. There are package files, xdc files and cfg files. Do these files need to change.

    Can you provide a little more information?  Which xdc and cfg files are you referring to?  I.e. please tell me the location of the files you are asking about in the product, so I can better answer your question.

    Steve

  • 0 in reply to Steven Connell
    Expert 1050 points

    I noticed that there are cfg and xdc files in the project. My question is that I developed a driver. Let's say I take the UART driver that I developed for OMAPL138 then how do I port it to SYS/BIOS. Where do I place them (assuming there is a preferred directory structure)? Also most of the drivers are as library files. How do I add my driver to be a part of the driver library? 

    Pinakin 

     

  • 0 in reply to Pinakin Potdar
    TI__Mastermind 45025 points

    I noticed that there are cfg and xdc files in the project.

    I still am not sure which project you're talking about.  I am looking at both the examples and the drivers in the TMS320C6748 SYS/BIOS SDK.  Both the examples and drivers have makefiles; there are not *.xdc or *.bld files that I can see.

    I think you are talking about an example from somewhere else.  A screen shot of where it exists in Windows explorer and/or where you found it in the product would provide some insight.

    Let's say I take the UART driver that I developed for OMAPL138 then how do I port it to SYS/BIOS.

    The 6748 SDK ships with both a UART driver and example for the 6748.  Have you seen those?

    Where do I place them (assuming there is a preferred directory structure)?

    If I were to add a new driver, I would copy one of the existing ones and put it right in the biospsp_03_00_01_00\drivers directory (shown in above screen shot), so that it sits next to other existing ones, e.g. uart, psc ...

    Also most of the drivers are as library files. How do I add my driver to be a part of the driver library? 

    You should build your driver to be its own individual library.  For example, the UART driver directory will build a library that is just for the functionality of the UART driver.  Similar for the others.  Each builds the library for the driver the folder is named after.

    If you follow these existing drivers as an example, then your new driver, let's call it "myDriver", should live in a directory "myDriver" and build a library called "bios_psp_myDriver.ae674"

    Steve

  • 0 in reply to Steven Connell
    TI__Mastermind 45025 points
    One more thing, I noticed that each driver has a "hidden" doc folder in its directory (as opposed the obvious top level docs folder). The document in there has details about the driver design and will be helpful in your understanding, if you haven't found it already. For example:

    biospsp_03_00_01_00\drivers\uart\docs\BIOSPSP_UART_Driver_Design.pdf

    Steve