First time I have a strange error.
I made target configuration file for c6678 and attach gel file from ../../emulation/boards/evmc6678l/gel/evmc6678l.gel
whenever I connect I get following error...
C66xx_0: GEL Output: Connecting Target...C66xx_0: GEL: Error while executing OnTargetConnect(): identifier not found: DNUM
at GEL_TextOut("DSP core #%d\n", 0, 1, 0, 0, DNUM) [evmc6678l.gel:1961] at Core_Info() [evmc6678l.gel:610] at OnTargetConnect() .
Note that I didn't change anything from gel file, I suppose this should always work unless I did something wrong?
Could you please help me out?
please see provided suggestions on silimar post vailable at:
Thank you for your reply.
But I am not even loading program, trying to connect to target.
Any ideas, why this could be happening?
It appears to me that DNUM register is not getting recognized in your CCS setup (for some reason). Can you do the following experiment?
1. Open CCS and connect to the target
2. Open Register tab (using View->Register menu option in CCS 5.1)
3. Find out if you are seeing DNUM under CoreRegisters group.
I did follow steps yes indeed I have no DNUM there.
Just to mention, error is occurring while connection to the target! What would be the case?
connect target error:
C66xx_0: GEL: Error while executing OnTargetConnect(): identifier not found: DNUM at GEL_TextOut("DSP core #%d\n", 0, 1, 0, 0, DNUM) [evmc6678l.gel:1961] at Core_Info() [evmc6678l.gel:610] at OnTargetConnect() .
after this I guess I will stay connected, but then load program error altogether:
Connecting Target...C66xx_0: GEL: Error while executing OnTargetConnect(): identifier not found: DNUM at GEL_TextOut("DSP core #%d\n", 0, 1, 0, 0, DNUM) [evmc6678l.gel:1961] at Core_Info() [evmc6678l.gel:610] at OnTargetConnect() .C66xx_0: GEL Output: Invalidate All Cache...C66xx_0: GEL Output: Invalidate All Cache... Done.C66xx_0: GEL: Error calling OnPreFileLoaded(): identifier not found: IER at IER=0 [evmc6678l.gel:681] at OnPreFileLoaded()C66xx_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.C66xx_0: Trouble Writing Register PC: (Error -1176 @ 0xD720) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.623.0) C66xx_0: GEL: Error while executing OnRestart(0): identifier not found: DNUM at (DNUM==0) [evmc6678l.gel:822] at OnRestart(0) .C66xx_0: GEL: Error while executing OnFileLoaded(0, 0): identifier not found: DNUM at (DNUM==0) [evmc6678l.gel:718] at OnFileLoaded(0, 0) .
If you don't have the register there then the GEL file can not read/write to those Registers. AFAIK, all versions of CCS should have this register in core register. Not sure if something got corrupted in your CCS setup? (just guessing).
What is the CCS version you are using? Is it possible for you to update to later CCS versions?
Note: When you are uninstalling the current CCSV5 version, please delete ccsv5 directory after you uninstalled it manually. (Just to make sure everything got cleaned up) and then reinstall it.
It is latest I guess....
Code Composer Studio Version: 188.8.131.52201061800 Build id: N201201061800
Thanks, I try to reinstall! Though I wish there would be other way!?
I will discuss this internally. However, it is better to give another try by reinstalling the CCS. If it works, I assume there was some issue while installing the CCS.
Feruz,I believe you've installed a patch on top of CCS which defines additional registers for the 6678, mostly for all of its peripherals. As part of that patch, some of the registers originally defined in the core registers group were moved to another group. Unfortunately GEL requires that registers are accessed using <register group name>_<register name> unless it's in the core registers group (in which case it's just <register name>), and the GEL file hasn't been updated to do that.
We're aware of this issue and are planning a fix for the updated xml files so that original GEL files will continue to work. In the mean time, you have three options:
It looked from your one post that you had a similar issue with the IER register. The same 3 options would apply to it.
Thank you for your answer!
I did follow 2. option and did some changes in xml file, then IER not found, same sort of error, I add IER as well.
Now, it seem to working fine!
I'm getting this same issue, btw, but only on my Linux install. It works fine on my Windows install. Both were downloaded from the site (not used from the included CD) in the past week, so they're as current as can be.
I also used option 2, and the demo (image edge detect) now works.
You are right, Rob G.
Only on Linux install!
Same for me, only see this in Linux version. Option 2 fix also did the trick for me.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.