CCSv4 and EVM6455

TimHarron said:

I just tried connecting to the Mezzanine card and had no problems in doing so.

Thanks for trying that for me!

I will get another PC and just install CCSv4 Platinum.

Hopefully my other PC has some driver issues as a result of the various versions that have been installed, uninstalled, re-installed, etc!

Thanks,

Matt

Let us know if the behavior changes at all on the other PC.

Hi Tim,

Here's what I've done:

• Fresh install of CCSv4.0.1.01001
• Create New Target Configuration
• Selected SD DSK-EVM-eZdsp and EVM6455
• Created 2 new CCS DSP/BIOS V5.4 projects
• In both projects I created a new DSP/BIOS 5.x Configuration File based on DSK6455. Same config for DSK and Mezz!
• Added source files to the projects that had LOG_printf in main and a task function with a TSK_sleep loop.
• I linked the target configuration to both projects
• Right-click the DSK project and select Debug As|Debug Session
• The Debug window opens showing the 2 DSPs and the DSK project running in the first one.

The debug session works until I Terminate. If I terminate a session I have great difficulty starting a new one, the only sure fire way is to restart the PC with the EVM off. But I have this problem in CCSv3.2 as well, if I disconnect I can't connect again. It hasn't really been causing me a problem in CCSv3.2 because I know what I'm doing and I don't ever disconnect.

So if I don't terminate I can talk to the Mezz but my project doesn't run currectly!

The Mezz project should run to main and stop but it loads and runs without getting to main. I can click Run, Halt, toggle break points and the disassembly window updates but I never get to main.

I think the DSK and Mezz are identical in terms on the DSP/BIOS configuration so I don't understand why it doesn't just run normally!

I'm also a vague on how to debug the second project on the second target because I don't right-click Debug As|Debug Session is the correct route.

I'm going to restart my PC and have another go! :-}

Thanks for your help,

Matt

Hi Matt, 

CCS v3.2 is a relatively old release. Compiler is probably quite a bit different between 3.2 and v4. Link below has information on how to use a different version of the compiler. I would try to use CCS v3.2's compiler to see if that makes a difference. 

http://tiexpressdsp.com/index.php/Compiler_Installation_and_Selection

Once you start a debugger on two processors using the procedure that you use, then select second processor that does not have program loaded and click on Load Program button, which should be available in main toolbar. (This is equivalent to File->Load Program in CCSv3.x). You may need to associate a source lookup paths to find your source files for second processor. After debug session is started, select second processor in Debug View, right click and select Edit Source Lookup, add second project. CCS should be able to find source files associated with second project. This information should be preserved next time you start a debugger. 

Launching and terminating a debug session in CCSv4 is roughly equivalent to opening and closing CCSv3.2 (at least from debugger perspective). 

Martin

MartinS said:

CCS v3.2 is a relatively old release...

Yeah, the compilers probably are a bit different but it doesn't feel like a compiler issue to me - things only start going wrong when I try and involve the Mezz.

MartinS said:

Once you start a debugger on two processors using the procedure that you use...

Thanks! I had tried 'Load program' but hadn't gone on to 'Edit Source Lookup'. Now the procedure is clear in my mind I will have another go.

Thanks,

Matt

I've had another go and I still can't talk to the Mezz correctly.

I can only think that either I'm doing something so stupid it hasn't even occurred to you lot or there is something wrong with my EVM.

Vote now for the most likely option!! :-}

I believe we're getting another EVM this week so I'll be able to have yet another go.

Thanks,

Matt

I have never used EVM6455, and both suggestions are a long shot: 

a) Try executing some reset GEL commands or quick test on both cpus. GEL functions appear under Scripts menu after you start a debug session. Please note that script will execute on cpu selected in debug view. 

b)... looking at evm6455 board file, I noticed that cpu's are named C64xp_0 and C64xp_1. I am not sure how they were called in 3.2, but I am not sure how to tell which one is mezz and which one is not.  Could it be that they are being mixed up? 

Martin

I think my problems are something to do with gel files and board revisions!

The PCBs are labelled with 2 revisions, one in the art work and one hand written, and I don't understand what they mean.

I've just received a second EVM.

Both the DSK boards I have are REV C/D2.

The Mezz boards are different, 1 Mezz is REV C/D2 and the other is REV F/F (this is the one I just received).

I started up CCSv4 with the newer EVM (DSK C/D2, Mezz F/F) and it just worked.

Then I went back to the older EVM (DSK C/D2, Mezz C/D2) and changed the CCSv4 target configuration to use the gel files from CCSv3.2 and it appears to be happy like this.

There is a difference between the CCSv3.2 gels and the CCSv4 gels but it doesn't mean anything to me!

Matt