When using the Simulink embedded coder app to generate C code to run on the TI F28379D Launchpad, the build process would generate a hyperlink (in the diagnostics output) I could use to launch Code Compser Studio (CCS) to debug the code directly on the hardware. For some reason, it stopped generating the hyperlink. Using the MATLAB Answers, I discovered that the following command generates this hyperlink (where 'ccspath' and 'proj folder' need to point to the CCS installation and the CCS_Project folder for the project):
>> Simulink.output.info(DAStudio.message('TIC2000:codegen:OpenCCSProject','ccspath','proj folder'))
The hyperlink represents the following command:
>> codertarget.tic2000.internal.openCCSproject('ccspath','proj folder')
In my case, (1) this command does not work and (2) the previously working hyperlink is no longer being generated in diagnostics output.
I have to believe that I should be able to use CCS to open the project generated by the embedded coder toolchain without relying on Simulink or MATLAB. All MathWorks on-line help information I could locate regarding opening CCS from Simulink appears to rely on this hyperlink (and its underlying command). Interestingly, I can execute this command with garbage path infomation and obtain the same result as I get from proper path information: nothing. Yes, no error message such as "CCS cannot be found" or "Project cannot be found", just nothing.
So, my question is how can I open my embedded coder generated output in CCS so that I can debug the process without using the supiciously absent and/or non-working hyperlink command?
