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.
Hi,
I am new to Code Composer and the whole TI dev environment, so excuse any trivial questions. I am missing a lot of cmds on script console on my CCS installation.
I am using CCS Version: 4.2.0.09000 to connect to a C6A816x EVM. Everything works just fine and I can connect to different cores on the chip, step through code etc.
But I am missing a lot of commands on the script console. I found that out when I was trying to run an example that required the use of loadRaw. Did I miss something in my installation for cmds not to show up in script console? Or do I have to enable something? Below are the cmds that ARE actually present when I do a tab on the script console prompt.
js:>
cls disableLog enableLog execCmdFile help listJSFiles loadJSFile loadKeyword print services setWindowBuffer unloadJSFile unloadKeyword
Thanks.
You do seem to be missing a lot of commands if that is all the commands you see after hitting tab. Could you try two things? First, your installation of CCSv4.2 is a beta install. Please update to the latest release (4.2.1.00004). Second, try using a new workspace.
Thanks
ki
Ki,
I tried your suggestion but no luck. :(
I upgraded to 4.2.1.00004 and even created a new workspace but I still do not get as many cmds on my scripting console.
Additionally here is what I observed.
- Another team member has my same old version(4.2.0.09000) of CCS and he gets all the cmds. Seems weird.
Is there a way to manually add these cmds so that I can use them in script console by copying it from my team mmeber's CCS installation. If so which files should I copy?
Thanks
Its resolved now. I guess something was wrong with my initial installation. I had to uninstall CCSv4 and install it in another location than the previous one. Now I see all the std cmds on scripting console.
Note that I had to install in a new location for this to work. Re-installing it in the same folder which I tried before did not work. I guess the initial uninstall did not clean everything up.