MATLAB: Does HILTUTORIAL stop and time out

codecomposerEmbedded IDE Link CCforlinkMATLABstudio

The HILTUTORIAL stops and times out.

Best Answer

If the HILTUTORIAL stops or times out and all of the following are true:

 a. You are using a C54x simulator.
 b. The demo stopped at the following code: 
run(cc,'main')   % Ensured embedded C variables are initialized  
 c. The following message appears in the CCS standard output window:

 Breakpoint Manager: Unable to move breakpoint to a valid line at source    line: ccstut.c line 64 It has been disabled. 
 d. You just ran CCSTUTORIAL before this demo

If all (a through d) of these conditions are true, then you have left a breakpoint in the program. Go to the Code Composer Studio and remove all breakpoints (click on the "hand with x-mark " icon) and re-run the demo.

Related Solutions

MATLAB: Is MATLAB Link for Code Composer Studio 1.2 (R13.0.1+) compatible with Code Composer Studio 2.2

To make MATLAB Link for Code Composer Studio 1.2 (R13.0.1+) fully compatible with Code Composer Studio 2.2, you need to download a patch.

Following are the steps for downloading the patch:

1. Download Link1p2PatchForCCS2p2.exe from the bottom of the page and copy it into the $MATLABROOT\toolbox\ccslink directory

(where $MATLABROOT is the root MATLAB directory)

2. Double-click on the executable Link1p2PatchForCCS2p2.exe' and click on 'Unzip'.

3. A window displaying "6 file(s) unzipped succesfully" will appear. Click OK and close the WinZip window.

4. Restart MATLAB

--------------------------------------------------------------------------------

Following are some of the issues you may come across when using MATLAB Link for Code Composer Studio 1.2 (R13.0.1+) with Code Composer Studio 2.2 and the corresponding solutions for these issues.

--------------------------------------------------------------------------------

1. Time-out issue with demos on OMAP Simulator

Problem:

Setup OMAP CCS 2.2 for OMAP3.1 Platform Simulator and run ccstutorial/ccsfirdemo/multiproctutorial
At some point the demo seems to stop and a time out error is thrown in MATLAB.

Solution:

This is due to a bug in the OMAP3.1 Platform Simulator on CCS 2.2 - if you open and load any ARM or C55x program, it takes a long time to run to any point in the program.

--------------------------------------------------------------------------------

2. Demo issues on the C5416 DSK using XDS-510

Problem 1:

When running rtdxtutorial, the demo terminates and you get the error:

Enable: Enable failed on channel: ichan

Problem 2:

When running rtdxlmsdemo, at the point when the following text is displayed in MATLAB

 Reading coefficient updates and filtered results from target - frame 1...

the process takes a long time and eventually errors out: ERROR: ReadMsg: Timeout waiting for CCS to confirm completion: waiting for 1 message 50 seconds might not be enough time for reading the data messages. Hit the 'view script' button and increase the value of the 'TimeOut' variable at the beginning of the script.

Solution:

Open the CCS IDE
At the left pane, click (+) on GEL Files and remove the existing GEL file(s) loaded.
Left-click GEL Files again and choose Load GEL… Go to TIROOT\cc\gel and choose c5416_dsk.gel. (where TIROOT is the root folder for TI)
Re-run the demo.

--------------------------------------------------------------------------------

3. ccsfirdemo times out on the C2812 DSK using XDS-510

Problem:

When running ccsfirdemo, it times out during the Run Target stage.

Solution:

Download the patch Link1p2PatchForCCS2p2.exe.

--------------------------------------------------------------------------------

4. RTDXTUTORIAL/RTDXLMSDEMO on OMAP Simulator

Problem:

Setup OMAP CCS 2.2 for OMAP3.1 Platform Simulator

Problem description:

Run rtdxtutorial (or rtdxlmsdemo) and choose the C5500 processor when prompted to select a target.
During 'load', a dialog box pops up in the CCS IDE:

 RTDX target application does not match emulation protocol!
 Loaded program was created with an rtdx library which does not match the target device.

If you hit OK and continue with the demo, eventually the demo errors out and exits. Error thrown in MATLAB is:

ERROR: "CCSDSP:The server threw an exception."

This error is related to demo issue no.1 (Time-out issue with demos in OMAP

simulator). You can still run RTDXLMSDEMO or RTDXTUTORIAL on a C55x

simulator by configuring a single C55x simulator in your CCS Set-up instead

of using the OMAP simulator and then running the demo.

--------------------------------------------------------------------------------

5. CCSTUTORIAL/CCSFIRDEMO on ARM 7 Big Endian Simulator

Problem:

During 'load', a dialog box pops up in the CCS IDE:

 Data verification failed at address 0x20.
 Please verify target memory and memory map."

Solution:

Before running ccstutorial or ccsfirdemo, open CCS IDE and do the following:
Go to the Option menu
Select Memory Map...
Enable Memory Mapping
Enter a Starting Address of 0x20
Enter a Length of 0x7FFE0
Enter Attributes of RAM
Click the Add button
Click Done to leave the dialog

Also, when running the ccstutorial, CCS IDE throws the message: "Can't Run Target CPU: Error number -2164 Error address 0" in the Messages window. This does not affect the demo.

--------------------------------------------------------------------------------

6. RTDXLMSDEMO on C6211 Big Endian Simulator

Problem:

During load, a dialog box pops up in the CCS IDE:

 File C:\MATLAB6p5\toolbox\ccslink\ccsdemos\rtdxlms\c6x\rtdxdemo_sim6xe.out
 Does not match the target type, not loaded.

Solution:

You have to rebuild the project rtddemo_sim6xe.pjt in $MATLAB\toolbox\ccslink\ccsdemos\rtdxlms\c6x:
Open the project in the CCS IDE. Go to Project->Build Options. Under the Compiler tab, select C621x (-mv6210) under Target Version. Click OK.
Build the project and re-run the demo.

Note: Since other processors use the same demo project, make sure you to return the Build Options to its original settings and rebuild the project.

MATLAB: Do the demos not work on the C6701 EVM board with Link for Code Composer Studio 1.3.1 (R14)

This bug has been fixed in Release 14 Service Pack 2 (R14SP2). For previous releases, please read below for any possible workarounds:

We have verified that there is a bug in Link for Code Composer Studio 1.3.1 (R14) in the way that the demos run on the C6701 EVM. The link product demos do not run on the C6701 EVM because certain files in the project file are not correct.

To workaround this issue, follow the steps below to build the project correctly for the C6701 EVM:

1. Open the CCS project used for the demo.

2. Check the output filename and make sure it matches the demo output filename. You do this by going to Project->Build Options... Go to Linker, select Category 'Basic', and check the entry under "Output Filename (-o):". Refer to the list below for the correct filenames for the project file (.pjt) and .out file for each demo.

3. Remove the existing .cmd file from the project and replace with the correct .cmd file. For rtdxtutorial and rtdxlmsdemo, replace the .cmd file in the project with $TIDIR\examples\evm6201\rtdx\shared\c6201EVM.cmd, where TIDIR is the CCS installation directory.

For other demos, replace the existing .cmd file in the project with $TIDIR\examples\evm6201\shared\c6201EVM.cmd, where TIDIR is the CCS installation directory.

4. Build the project.

Important: Make sure you rebuild the output file using the old settings and files to run the demo on other boards or simulators.

5. Rerun the demo from MATLAB.

Below is a list of demos and their corresponding CCS demo files. Note that $CCS_DEMOS_ROOT is $MATLAB\toolbox\ccslink\ccsdemos, where $MATLAB is the MATLAB installation directory.

CCSTUTORIAL:

- Project name: $CCS_DEMOS_ROOT\ccstutorial\ccstut_67x.pjt

- Output filename: $CCS_DEMOS_ROOT\ccstutorial\ccstut_67x.out

HILTUTORIAL/CCSHILDEMO:

- Project name: $CCS_DEMOS_ROOT\hiltutorial\hiltut_67x.pjt

- Output filename: $CCS_DEMOS_ROOT\hiltutorial\hiltut_67x.out

CCSFIRDEMO:

- Project name: $CCS_DEMOS_ROOT\ccsfir\ccsfir_67x.pjt

- Output filename: $CCS_DEMOS_ROOT\ccsfir\a67x.out

RTDXTUTORIAL:

- Project name: $CCS_DEMOS_ROOT\rtdxtutorial\c6x\rtdxtutorial_67x.pjt

- Output filename: $CCS_DEMOS_ROOT\rtdxtutorial\c6x\rtdxtutorial_67x.out

RTDXLMSDEMO:

- Project name: $CCS_DEMOS_ROOT\rtdxdemo\c6x\rtdxdemo_67x.pjt

- Output filename: $CCS_DEMOS_ROOT\rtdxdemo\c6x\rtdxdemo_67x.out

CCSDEBUGDEMO:

- Project name: $CCS_DEMOS_ROOT\debug\FilterFFT_c6700\FilterFFT.pjt

- Output filename: $CCS_DEMOS_ROOT\debug\FilterFFT_c6700\FilterFFT.out

Best Answer

Related Solutions

MATLAB: Is MATLAB Link for Code Composer Studio 1.2 (R13.0.1+) compatible with Code Composer Studio 2.2

MATLAB: Do the demos not work on the C6701 EVM board with Link for Code Composer Studio 1.3.1 (R14)

Related Question