Prev: starn matlab with crontab
Next: copy figure for scope plot in simulink?
From: Samuel Dorrell on 30 Jul 2010 13:29
"Rafael do Carmo Pinto" <rafael.carmo.pinto(a)gmail.com> wrote in message <ho8hv9$93i$1(a)fred.mathworks.com>...
> Hello,
>
> I am trying to generate code using simulink in Code Composer with a simple model
> for DSK6713, with a ADC directly connected to a DAC.
>
> I have Matlab 7.9.0 (R2009b), Code Composer 3.3, DSK 3.1.
>
> When I try to generate code in Code Composer appears:
>
> "untitled.h", line 25: fatal error: could not open source file "untitledcfg.h"
> and
> "untitled_main.h", line 3: fatal error: could not open source file "untitledcfg.h"
>
> I'm not sure of the meaning of this message.
>
> File cfg.h is a reader file?
> What are making that problem happen, Matlab or Code Composer?
> What I can do to resolve that problem and generate code?
>
> If someone can help please send a message to rafael.carmo.pinto(a)gmail.com
>
> Thanks for all informations.

Hi Rafael,

I'm not sure if I've got the answer I'm afraid but am having a related problem. Since this post has gone dead I hope you dont mind me hijacking it, I also thought perhaps you might have made some progress, or had some advice that you might be able to share!

I seem to remember having a problem like yours before and my guess (and that's all it is really) is that your problem of the modelcfg.h file not being created is something to do with the simulink configuration parameters (i.e. Is your harware implementation pane set up correctly, your rtw/target selection set to ccslink_ert.tlc, your rtw/interface set to the tfl for our processor and your rtw/embeddedIdeLink set to Build_and_execute)

I am a bit puzzled though at why this file is sometimes generated and sometimes not. For instance if I set the build action to 'create project' the modelcfg.h file isn't created and no header files are included in the CCS project (but are generated). When I the the build action to build, the modelcfg.h file is included and the CCS project contains all thye relevant header files. When I set the build action to Archive_library a modelcfg.h file isn't created, but nore is the model_main.c function (so the cfg.h file isn't needed). There is a modelcfg.h64 file though (???) but this isn't included in the CCS project. What does it all mean??

Also, I've been looking at using the 'rightClick:export function' instead (which creates code for a triggered subsystem). I'm not sure I really understand the difference between building a subsytem and exporting a triggered function, aren't these very similar things? But again hit a brick wall when I got the following error message (I don't have a _ExpFcn_3 block in my model and have already replaced all my initial output parameters with initial conditions blocks (I'm not even really sure why this is necessary anyway)):
The parameter 'Source of initial output value:' of Outport block 'segmentImage/__ExpFcn__3/Out1' must be set to 'Input signal' because a function-call trigger signal from output port 1 of block 'segmentImage/__ExpFcn__3/expFcn' is passing through the Outport block

If anyone could shed any light on any of these thing it would be appreciated. Rafael, perhaps if you recieved some information that helped you could forward it on. My email is sdorrell at aslvision.co.uk.

Best Regards
Sam
From: news.mathworks.com on 30 Jul 2010 14:27
<model name>cfg.h is an auto-generated file for DSP/BIOS based CCS projects.
MATLAB/Simulink creates a <model name>.tcf file that DSP/BIOS TCONF utility
uses to generate a couple of source / header files. <model name>cfg.h is one
of them. If you just create a project, you will not see this file because
this file is generated as a pre-build step by the CCS.

The fact that you are missing this file indicates something wrong with your
CCS configuration. Open CCS Component Manager and set the "Build Tools",
"Target Content (DSP/BIOS)" to the values MATLAB supports. You may need to
upgrade Build tool and DSP/BIOS revision to the ones MATLAB advertises as
supported. After this step, run a DSP/BIOS example project from Code Try to
compile a DSP/BIOS based project shipped by TI. For example:

....\CCStudio_v3.3\bios_5_33_06\packages\ti\bios\examples\basic\hello\dsk6713

If this compiles and runs correctly you should have no problem generating
code from MATLAB / Simulink. While building the project, in the CCS Build
window, look at the messages displayed. It should say something like:

------------------------ c6713dskafxr.pjt -
ustomMW ------------------------
[c6713dskafxr.tcf]
"C:\Applications\CCStudio_v3.3\bios_5_33_06\xdctools\tconf" -b -Dconfig.importPath="C:/Applications/CCStudio_v3.3/bios_5_33_06/packages"
c6713dskafxr.tcf

This is the step where the *cg.h file is generated. Make sure you see this
line while the project build is going on.

Cheers,

MiB

"Samuel Dorrell" <sdorrell(a)asl-vision.co.uk> wrote in message
news:i2v251$ejo$1(a)fred.mathworks.com...
> "Rafael do Carmo Pinto" <rafael.carmo.pinto(a)gmail.com> wrote in message
> <ho8hv9$93i$1(a)fred.mathworks.com>...
>> Hello,
>>
>> I am trying to generate code using simulink in Code Composer with a
>> simple model for DSK6713, with a ADC directly connected to a DAC.
>>
>> I have Matlab 7.9.0 (R2009b), Code Composer 3.3, DSK 3.1.
>>
>> When I try to generate code in Code Composer appears:
>>
>> "untitled.h", line 25: fatal error: could not open source file
>> "untitledcfg.h"
>> and
>> "untitled_main.h", line 3: fatal error: could not open source file
>> "untitledcfg.h"
>>
>> I'm not sure of the meaning of this message. File cfg.h is a reader
>> file?
>> What are making that problem happen, Matlab or Code Composer?
>> What I can do to resolve that problem and generate code?
>>
>> If someone can help please send a message to
>> rafael.carmo.pinto(a)gmail.com Thanks for all informations.
>
> Hi Rafael,
>
> I'm not sure if I've got the answer I'm afraid but am having a related
> problem. Since this post has gone dead I hope you dont mind me hijacking
> it, I also thought perhaps you might have made some progress, or had some
> advice that you might be able to share!
>
> I seem to remember having a problem like yours before and my guess (and
> that's all it is really) is that your problem of the modelcfg.h file not
> being created is something to do with the simulink configuration
> parameters (i.e. Is your harware implementation pane set up correctly,
> your rtw/target selection set to ccslink_ert.tlc, your rtw/interface set
> to the tfl for our processor and your rtw/embeddedIdeLink set to
> Build_and_execute)
>
> I am a bit puzzled though at why this file is sometimes generated and
> sometimes not. For instance if I set the build action to 'create project'
> the modelcfg.h file isn't created and no header files are included in the
> CCS project (but are generated). When I the the build action to build, the
> modelcfg.h file is included and the CCS project contains all thye relevant
> header files. When I set the build action to Archive_library a modelcfg.h
> file isn't created, but nore is the model_main.c function (so the cfg.h
> file isn't needed). There is a modelcfg.h64 file though (???) but this
> isn't included in the CCS project. What does it all mean??
>
> Also, I've been looking at using the 'rightClick:export function' instead
> (which creates code for a triggered subsystem). I'm not sure I really
> understand the difference between building a subsytem and exporting a
> triggered function, aren't these very similar things? But again hit a
> brick wall when I got the following error message (I don't have a
> _ExpFcn_3 block in my model and have already replaced all my initial
> output parameters with initial conditions blocks (I'm not even really sure
> why this is necessary anyway)):
> The parameter 'Source of initial output value:' of Outport block
> 'segmentImage/__ExpFcn__3/Out1' must be set to 'Input signal' because a
> function-call trigger signal from output port 1 of block
> 'segmentImage/__ExpFcn__3/expFcn' is passing through the Outport block
>
> If anyone could shed any light on any of these thing it would be
> appreciated. Rafael, perhaps if you recieved some information that helped
> you could forward it on. My email is sdorrell at aslvision.co.uk.
> Best Regards
> Sam
>


From: Samuel Dorrell on 2 Aug 2010 11:14
> The fact that you are missing this file indicates something wrong with your
> CCS configuration. Open CCS Component Manager and set the "Build Tools",
> "Target Content (DSP/BIOS)" to the values MATLAB supports. You may need to
> upgrade Build tool and DSP/BIOS revision to the ones MATLAB advertises as
> supported.

In the help there's a nice function checkEnvSetup('ccs',<board/processor name>) (<board/processor name> is the board name as it appears in the library browser for instance) which sets up the matlab environment for code generation and checks your current versions of CCS etc!
Regards
Sam
 | 
Pages: 1
Prev: starn matlab with crontab
Next: copy figure for scope plot in simulink?