question about CCSv5 connecting target error

Nick,

The emulator or Code Composer Forum people may know better, but my first thought is that you are not using the right target configuration. DNUM should be available naturally through the GEL system. If it is not available, that implies to me that CCS does not have the right hooks through the target configuration to know about DNUM.

Please check your target configuration file.

Are you using your own board or the EVMC6670L/LE (which one?) or some other development board?

What emulator are you using?

Regards,
RandyP

Hi RandyP,

I'm using our own board and the emulator is XDS100. After a target configuration file has been set up, I only configured the type of emulator I used, selected the type of DSP

and add GEL file. All other configuration is default. But it didn't work. And I also tried XDS560v2 emulator, the result is the same.

I wonder if the  "The emulator or Code Composer Forum" is in the E2E forum?

Thanks

Best regards,

Nick

Nick,

Yes, on the E2E Home Page under Support is a list of forum groups, and under Development Tools is Code Composer Studio. I will get this thread moved there for their advice. They may end up sending you somewhere else or back here to the C66x Multicore Forum, but someone will be able to help, I suspect.

It will help to know exactly which version of CCSvx.xx.xx.xx you are using and it will be good to do Check for Updates under the Help menu to see if there are emulation driver updates for you.

Also, tell us what results you can get with the Test Connection button in the Target Configuration window for your target configuration, and whether you can see valid internal memory if you ignore the DNUM error (or remove the GEL file).

Regards,
RandyP

Please look at the following e2e posting:

http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/106033.aspx

See if it helps.  I think that moving to a new version of CCS might help as well

Ran

There are other posting for the same problem.   Do Web serach on "Identifier Not Found:  DNUM".  There are several posting.  Read them

regards

Ran

Hi RandyP,

The version of CCSv5 is 5.1.0.09000 and the version of bios_mcsdk is 02_00_05_17.

As you said, I did the test connection work. The result was all test passed. And if I right click on the target configuration file and selected the launch selected target item, the

console would display:

C66xx_0: GEL Output: Setup_Memory_Map...

C66xx_0: GEL Output: Setup_Memory_Map... Done.

From the register window, I could find the DNUM register, but it was in unable to read state. After this, I clicked the connect target button, and the console would display:

OnTargetConnect():idetifier not found: DNUM

From other post, I got three ways to solve it:

"1.Find out where DNUM is now defined in your setup.  You can hit ctrl + f to search in the register view for "DNUM" (expect the search to take a while to load the first time).  Once found, you can modify the GEL files to access it using groupname_DNUM instead of just DNUM.  

2.Define DNUM as a hidden register, as hidden registers can also be accessed without a group name.  You can do this by editing <install>\ccsv5\ccs_base\common\targetdb\Modules\64x+NotVisible.xml and adding a new line like the following: <register id="DNUM" acronym="DNUM" width="32" description="">. 

3.If you know that you don't need the step in the GEL file that's using DNUM, then you can just comment out that line.  (I'm guessing this isn't the case, but I thought I'd mention it just in case...)"

I tried the second one. But it didn't work.

Is it possible that something wrong with the bios_mcsdk? Or the version of bios_mcsdk is not compatible with ccsv5.1?

Thanks

Best regards,

Nick