Dear support,
On installation of the MCSDK, the pdk_C6670_1_1_0_3 was created. We made a copy of this source code into our work environment and modify the platform to match our board rather that the EVM. So far so good.
All our code is stored on a source code controller server (including the modified platform) and is built on a build machine. I have a few questions regarding rebuilding the CSL and LLD. Following the process described in http://processors.wiki.ti.com/index.php/BIOS_MCSDK_2.0_User_Guide#Building_CSL_and_the_Low_Level_Device_Drivers, I had some issues but got to rebuilding most of it and I have 2 questions to resolve what is missing:
1) how is the documentation regenerated? ex:c:\TI_MCSDK\pdk_C6670_1_1_0_3\packages\ti\drv\hyplnk\docs\
2) how is the eclipse RTSC package recreated (ex:***\ti\drv\aif2\package\). I mean the part that enables me to do the following in a cfg file: var hlink = xdc.useModule('ti.drv.hyplnk.Settings');
or var cslSettings = xdc.useModule ('ti.csl.Settings'); or var Pcie = xdc.loadPackage('ti.drv.pcie'); or var PlatformLib = xdc.loadPackage('ti.platform.evmc6670l');
Can I regenerate the package and the correct documentation after modification of the platform library?
Alternatively, a project can always link against the library but using RTSC is the way that TI uses the "PDK" libraries and I would like to do it the same way.
Thanks for your help
PS: here are the definition that I am using before running pdksetupenv.bat and then pdkbuilder.sh and you can see that XDC and DOXYGEN are defined
set C6X_GEN_INSTALL_PATH=c:\TI_CCS\ccsv5\tools\compiler\c6000_7.3.4
set XDC_INSTALL_PATH=c:\TI_MCSDK\xdctools_3_23_02_47
set CG_XML_BIN_INSTALL_PATH=c:\TI_MCSDK\cg_xml
set EDMA3_LLD_INSTALL_PATH=c:\TI_MCSDK\edma3_lld_02_11_05_02\packages
set PDK_INSTALL_PATH=%SSP_PDK_C6670%
set DOXYGEN_INSTALL_PATH=%SSP_DOXYGEN_DOT%