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.

Issues with using macros.ini

Other Parts Discussed in Thread: CCSTUDIO, OMAP-L138

Hi again!

I 'm following WORKSHOP C6000 Embedded Design Workshop Using BIOS v5.46 and I notice I need macros.ini to set environment paths for files to compile/link, but I notice that the file downloaded has only some paths. I know how to do this file, but I don't know what is the path of the MACROs espeficied in lab6, anyone does it know?

I need this:

-i"$(EDMA)\inc" -i"$(PSP)\inc" -i"$(PSP_6437)"
4. To locate all the builder paths used, replace the DspBiosBuilder section with:
["DspBiosBuilder" Settings: "Debug"]
Options=-Dconfig.importPath="$(BIOS_Common);$(PSP_I2C);$(Echo_Code)"
["DspBiosBuilder" Settings: "Release"]
Options=-Dconfig.importPath="$(BIOS_Common);$(PSP_I2C);$(Echo_Code)"
5. To locate driver libraries for debug builds, add to ["Linker" Settings: "Debug"]:
-i"$(BIOS_Common)" -i"$(PSP_Dbg)" -i"$(EDMA_Dbg)" -l"palos_bios.lib" -
l"i2c_bios_drv.lib" -l"mcasp_bios_drv.lib" -l"mcbsp_bios_drv.lib" -
l"audio_bios_drv.lib" -l"edma3_drv_bios.lib" -l"edma3_rm_bios.lib" -
l"edma3_drv_sample.lib" -l"log8.a64P"
6. To locate driver libraries for release builds, add to ["Linker" Settings: "Release"] :
-i"$(BIOS_c6000)" -i"$(PSP_Rel)" -i"$(EDMA_Rel)" -l"palos_bios.lib" -
l"i2c_bios_drv.lib" -l"mcasp_bios_drv.lib" -l"mcbsp_bios_drv.lib" -
l"audio_bios_drv.lib" -l"edma3_drv_bios.lib"


and in MACRO.ini there are these macros:

BSL=C:\CCStudio_v3.3\boards\evmdm6437_v2\include
PSP=C:\dvsdk_1_10_00_27\pspdrivers_1_10_00_09\packages
BIOS_Common=%BIOS_INSTALL_DIR%\packages\ti\bios\examples\common
BIOS_c6000=%BIOS_INSTALL_DIR%\packages\ti\rtdx\lib\c6000

Thanks a lot

  • Sorry, I forgot doing a question: I know that macro.ini is loaded on starting, but when is running CCS how/where I could check if CCS sets correctly this macros and their paths??

    thanks a lot

     

    Hi again!

    I 'm following WORKSHOP C6000 Embedded Design Workshop Using BIOS v5.46 and I notice I need macros.ini to set environment paths for files to compile/link, but I notice that the file downloaded has only some paths. I know how to do this file, but I don't know what is the path of the MACROs espeficied in lab6, anyone does it know?

    I need this:

    -i"$(EDMA)\inc" -i"$(PSP)\inc" -i"$(PSP_6437)"
    4. To locate all the builder paths used, replace the DspBiosBuilder section with:
    ["DspBiosBuilder" Settings: "Debug"]
    Options=-Dconfig.importPath="$(BIOS_Common);$(PSP_I2C);$(Echo_Code)"
    ["DspBiosBuilder" Settings: "Release"]
    Options=-Dconfig.importPath="$(BIOS_Common);$(PSP_I2C);$(Echo_Code)"
    5. To locate driver libraries for debug builds, add to ["Linker" Settings: "Debug"]:
    -i"$(BIOS_Common)" -i"$(PSP_Dbg)" -i"$(EDMA_Dbg)" -l"palos_bios.lib" -
    l"i2c_bios_drv.lib" -l"mcasp_bios_drv.lib" -l"mcbsp_bios_drv.lib" -
    l"audio_bios_drv.lib" -l"edma3_drv_bios.lib" -l"edma3_rm_bios.lib" -
    l"edma3_drv_sample.lib" -l"log8.a64P"
    6. To locate driver libraries for release builds, add to ["Linker" Settings: "Release"] :
    -i"$(BIOS_c6000)" -i"$(PSP_Rel)" -i"$(EDMA_Rel)" -l"palos_bios.lib" -
    l"i2c_bios_drv.lib" -l"mcasp_bios_drv.lib" -l"mcbsp_bios_drv.lib" -
    l"audio_bios_drv.lib" -l"edma3_drv_bios.lib"


    and in MACRO.ini there are these macros:

    BSL=C:\CCStudio_v3.3\boards\evmdm6437_v2\include
    PSP=C:\dvsdk_1_10_00_27\pspdrivers_1_10_00_09\packages
    BIOS_Common=%BIOS_INSTALL_DIR%\packages\ti\bios\examples\common
    BIOS_c6000=%BIOS_INSTALL_DIR%\packages\ti\rtdx\lib\c6000

  • Pablo,

    These should be set under the CCS menu.  Select "window -> preferences" then you should see it as shown in the below screen shot.

    Thanks,

    Steve

  • Pablo,

    My name is Eric Wilbur and I am the developer of the BIOS Workshop. The current wiki site is located here:

    http://processors.wiki.ti.com/index.php/C6000_Embedded_Design_Workshop_Using_BIOS

    The lab you are referencing is for CCSv3.3 using the DM6437 and incorporating a PSP driver (about 6 revisions old by now) and about 3 years old. That lab does not work in CCSv4 and later as is - it relies on the exact environment and settings back when that version of the workshop was published. The latest instructor setup guide is on the wiki page referenced above to create the latest workshop environment - OMAP-L138 using CCSv4.2.3.

    If you are migrating a 3.3 project to CCSv4, you have two options: migrate legacy 3.3 project (which has a macros.ini file) or, create a new project from scratch in CCSv4. I have found that creating a new project in CCSv4 is the more stable way to accomplish this. The problem with importing a legacy project is the macros.ini file - it doesn't work very well. You have to print out those path statements and add them to the Build Properties - Macros - for that project. Cumbersome and possibly error-prone.

    So, are you attempting to do this lab with CCSv3.3 or CCSv4 or CCSv5? Are you trying to get a PSP driver to work?

    Macros.ini simply specifies paths to tools (PSP, EDMA LLD, etc) as Steve mentions. In CCSv4/5, these are not really necessary unless you are importing a legacy 3.3 project to CCSv4/5. So, finding out exactly what you're trying to accomplish will help.

    Thanks,

    Eric

  • Hi!

    thanks for your response.

    Yes, I found this workshop in link that you mention. I got EVM6437 one month ago, and in the package I have CCS3.3. So, I installed all SW contents attached. On September I'm going to attend to an BIOS workshop in Munich, and I would know DSP/BIOS and CCS on my board before this appointment.I have PSP_1_00_02_00

    Do you think appropiate continuing with this versions (CCS 3.3 & PSP_1_00_02_00)? or would I need to change to another?? How can I check in CCS3.3 if macro.ini is loaded correctly (watching all macro-paths association)?.

    Thanks a lot.l

  • Pablo,

    The versions of software that you mention are outdated.  You should be using CCS4 and either DSP/BIOS 5.x or SYS/BIOS 6.x.

    Dave

  • Thanks, I will try!