CCSv4 XDCtools build errors

Simon,

Sorry you're having this problem. I've not been able to replicate it, but the output you gave shows that there's something weird going on. The error message names the XDCROOT directory as "C:/PROGRA~1/Texas Instruments/xdctools_3_16_01_27", but the tools should have already removed all the spaces in the directory name by this point. Internally it should have translated it into something like "C:/PROGRA~1/TEXASI~1/xdctools_3_16_01_27". For some reason it's translated only "Program Files" part, and not also the "Texas Instruments" part.

Could you please open up a dos command window, manually execute the helper app that does this translation, and post the result?

C:\>cd "C:\Program Files\Texas Instruments\xdctools_3_16_01_27\packages\xdc\services\io\release"
C:\Program Files\Texas Instruments\xdctools_3_16_01_27\packages\xdc\services\io\release>path2dos "%CD%"
C:\PROGRA~1\TEXASI~1\xdctools_3_16_01_27\packages\xdc\services\io\release

Above is what's produced on my machine.  Bold stuff is for you to type, and red stuff is the expected result.

Please bear with me, this might take a few rounds to solve.

thanks,
Jon

Simon,

Actually I might have found it, there's a Windows registry setting that would break the path2dos helper app in this fashion. In addition to posting the result of the test above, can you also please open regedit, and verify that the following setting is non-zero on your machine?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation

The comp.os... reference below implies that this is Vista-specific, but it's not. My XP machine has this registry entry also.

thanks,
Jon

References:

• http://technet.microsoft.com/en-us/library/cc959352.aspx
• http://groups.google.com/group/comp.os.ms-windows.programmer.win32/browse_thread/thread/71d71d819f6e6df0

John,

Thanks for your suggestions.  I have run the test you asked, result below:

C:\PROGRA~1\Texas Instruments\xdctools_3_16_01_27\packages\xdc\services\io\release

I have also checked the registry and the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation is 1.  I changed it to 0 and still things didn't work, even after a reboot.  After some more reading on the web I found that the change only takes affect on new files, so I uninstalled all TI tools and reinstalled them.  I am now able to get the tutorial to work.

The aim of this tutorial was to try and follow the instructions from your collogue, AmitMookerjee, in this post: http://e2e.ti.com/support/development_tools/f/81/t/28675.aspx  However I am still not able to get the DVSDK example projects to work in CCSv4, either by  AmitMookerjee method of creating two new projects and copying the files to them, or by using the import wizard for legacy 3.3 projects.  Specifically it is the EVMDM6437 board that I am using and I'm trying to get the video_encdec example to run. I see on http://wiki.msp430.com/index.php/Migrating_to_CCSv4 that it says the DVSDK projects couldn't be imported with beta 2.  Is this now fixed?

I have been doing a lot of reading of the forum and it seems I am not the only persone struggling.  Could you please post some detailed steps on how to get a DVSDK project that uses xdc to work in CCSv4.  What tool and BIOS version do you recommend I use for a new project?

I am about to start developing a new product using a Davinci DSP so thought it was an ideal time to change from CCSv3.3 to CCSv4, but it might be best to go back to v3.3 afterall.

Many thanks,

Simon.

Simon,

Thanks for the info on that problem. On your second question about using the DVSDK for 6437 in CCSv4, it'll take me another day to figure this out. Sorry, and thanks for your patience.

By the way, which version of the DVSDK are you using?

thanks,
Jon 

Simon,

I was able to get a DVSDK example working with CCSv4. It's probably about the same difficulty as creating a project from scratch in CCSv4. Not to overstate the case, it still took a few hours and some head-scratching. I'm not that familiar with the DVSDK so it would have either way. To keep the information on DVSDK + CCSv4 together I continued the discussion on the other thread, here.

Jon

Jon,

That worked well and I am now able to recreate a v3.3 project in v4.1 using your instructions. 

Many thanks for your help.

Simon