Okay,

I've been setting up a test case using the crossworks tasking library. 
I've included the ctl_api.h header, and during the build, none of the 
tasking functions are found. Here's the error:

Build active project  230 ms  9 errors
Building Portacom Tasking in configuration Debug  9 errors
Compiling main.c
Linking Portacom Tasking.hzx  9 errors
undefined symbol '_ctl_interrupt_count'
undefined symbol '_ctl_exit_isr'
undefined symbol '_ctl_increment_tick_from_isr'
undefined symbol '_ctl_task_init'
undefined symbol '_ctl_get_current_time'
undefined symbol '_ctl_timeout_wait'
undefined symbol '_ctl_events_set_clear'
undefined symbol '_ctl_task_run'
undefined symbol '_ctl_events_wait'
Build failed

So obviously I'm not including something that I should be? I verified 
that the ctl_api.h file is being found by crossworks. Any suggestions?

-Micah

Hi Micah,

Did you create a new CTL project using the project wizard?  We suspect
not.

If not, don't worry, you'll need to do a couple of things so that it
will link successfully:

(a) Click the project node in the Project explorer.
(b) Show the Properties Window.
(c) In the Linker Options group, set Use Multi Threaded Libraries to
Yes.
(e) In the Linker Options group, set the Additional Input Files to
"$(StudioDir)/ctl/lib/libctl$(LibExt).hza".

You can also set the User Include Directories to
"$(StudioDir)/ctl/include;." and that will find the CTL API for you.

This is all set up for you if you use select CTL Executable from the CTL
Projects folder in the New Project wizard.

Regards,

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

> -----Original Message-----
> From: Micah [mailto:micah@mica...] 
> Sent: 24 March 2005 16:26
> To: msp430@msp4...
> Subject: [msp430] Crossworks tasking library
> 
> 
> Okay,
> 
> I've been setting up a test case using the crossworks tasking 
> library. 
> I've included the ctl_api.h header, and during the build, 
> none of the tasking functions are found. Here's the error:
> 
> Build active project - 230 ms - 9 errors Building "Portacom 
> Tasking" in configuration "Debug" - 9 errors Compiling
main.c 
> Linking Portacom Tasking.hzx - 9 errors undefined symbol 
> '_ctl_interrupt_count'
> undefined symbol '_ctl_exit_isr'
> undefined symbol '_ctl_increment_tick_from_isr'
> undefined symbol '_ctl_task_init'
> undefined symbol '_ctl_get_current_time'
> undefined symbol '_ctl_timeout_wait'
> undefined symbol '_ctl_events_set_clear'
> undefined symbol '_ctl_task_run'
> undefined symbol '_ctl_events_wait'
> Build failed
> 
> So obviously I'm not including something that I should be? I 
> verified that the ctl_api.h file is being found by 
> crossworks. Any suggestions?
> 
> -Micah
> 
> 
> .
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 
> 

That was indeed the problem. Thanks again for a prompt response. Back to 
my code!

-Micah

Paul Curtis wrote:

> Hi Micah,
>
> Did you create a new CTL project using the project wizard?  We suspect
> not.
>
> If not, don't worry, you'll need to do a couple of things so that
it
> will link successfully:
>
> (a) Click the project node in the Project explorer.
> (b) Show the Properties Window.
> (c) In the Linker Options group, set Use Multi Threaded Libraries to
> Yes.
> (e) In the Linker Options group, set the Additional Input Files to
> "$(StudioDir)/ctl/lib/libctl$(LibExt).hza".
>
> You can also set the User Include Directories to
> "$(StudioDir)/ctl/include;." and that will find the CTL API for
you.
>
> This is all set up for you if you use select CTL Executable from the CTL
> Projects folder in the New Project wizard.
>
> Regards,
>
> --
> Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
>
> > -----Original Message-----
> > From: Micah [mailto:micah@mica...]
> > Sent: 24 March 2005 16:26
> > To: msp430@msp4...
> > Subject: [msp430] Crossworks tasking library
> >
> >
> > Okay,
> >
> > I've been setting up a test case using the crossworks tasking
> > library.
> > I've included the ctl_api.h header, and during the build,
> > none of the tasking functions are found. Here's the error:
> >
> > Build active project - 230 ms - 9 errors Building "Portacom
> > Tasking" in configuration "Debug" - 9 errors Compiling
main.c
> > Linking Portacom Tasking.hzx - 9 errors undefined symbol
> > '_ctl_interrupt_count'
> > undefined symbol '_ctl_exit_isr'
> > undefined symbol '_ctl_increment_tick_from_isr'
> > undefined symbol '_ctl_task_init'
> > undefined symbol '_ctl_get_current_time'
> > undefined symbol '_ctl_timeout_wait'
> > undefined symbol '_ctl_events_set_clear'
> > undefined symbol '_ctl_task_run'
> > undefined symbol '_ctl_events_wait'
> > Build failed
> >
> > So obviously I'm not including something that I should be? I
> > verified that the ctl_api.h file is being found by
> > crossworks. Any suggestions?
> >
> > -Micah
> >
> >
> > .
> >
> > 
> > >.
>
>

Hi again Paul,

I'm running tasking successfully now, thanks for your help, but
there's 
some questions that I'm having. Here's my test case (based pretty 
heavily on your example code):

Main task starts at 255 priority
Initialize IO, and tasks (memset and all that)
run task timer_task priority 2 (does nothing, just sets event so that 
blink will execute as in the example)
run task blink_task priority 2 (flashed the LED)
run task button_task priority 1 (checks to see if the button is pushed, 
if so, light second LED)
switch main priority to 0
while (1) {}

I also have a timer interrupt on A0 that is calling the increment 
current time CTL function.

Now, questions:
The CTL time doesn't seem to increment. I'm watching the global
variabl, 
and although the timer ISR is calling the function to increment it, 
nothing happens? For some reason it just sits at 0x3da.

two of my functions have priority 2 and run back and forth. The lower 
priority function button never seems to run. Is this normal? I would 
assume it would just run less often, but apparently as the priority 2 
functions always are doing something, they will never relinquish 
control. To allow them to pause occasionally, I was going to try making 
them wait a bit. But as the CTL timer never increments, the function 
never execute if I put in a ctl_timeout_wait(ctl_get_current_time() + 
10) command.

I'm turning off interrupts in the timer ISR as suggested.

Any clue as to why the current time never increments? Any suggestion on 
what to check? Thank you!
-Micah


Micah wrote:

> That was indeed the problem. Thanks again for a
prompt response. Back to
> my code!
>
> -Micah
>
> Paul Curtis wrote:
>
> > Hi Micah,
> >
> > Did you create a new CTL project using the project wizard?  We suspect
> > not.
> >
> > If not, don't worry, you'll need to do a couple of things so
that it
> > will link successfully:
> >
> > (a) Click the project node in the Project explorer.
> > (b) Show the Properties Window.
> > (c) In the Linker Options group, set Use Multi Threaded Libraries to
> > Yes.
> > (e) In the Linker Options group, set the Additional Input Files to
> > "$(StudioDir)/ctl/lib/libctl$(LibExt).hza".
> >
> > You can also set the User Include Directories to
> > "$(StudioDir)/ctl/include;." and that will find the CTL API
for you.
> >
> > This is all set up for you if you use select CTL Executable from the
CTL
> > Projects folder in the New Project wizard.
> >
> > Regards,
> >
> > --
> > Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
> >
> > > -----Original Message-----
> > > From: Micah [mailto:micah@mica...]
> > > Sent: 24 March 2005 16:26
> > > To: msp430@msp4...
> > > Subject: [msp430] Crossworks tasking library
> > >
> > >
> > > Okay,
> > >
> > > I've been setting up a test case using the crossworks
tasking
> > > library.
> > > I've included the ctl_api.h header, and during the build,
> > > none of the tasking functions are found. Here's the error:
> > >
> > > Build active project - 230 ms - 9 errors Building "Portacom
> > > Tasking" in configuration "Debug" - 9 errors
Compiling main.c
> > > Linking Portacom Tasking.hzx - 9 errors undefined symbol
> > > '_ctl_interrupt_count'
> > > undefined symbol '_ctl_exit_isr'
> > > undefined symbol '_ctl_increment_tick_from_isr'
> > > undefined symbol '_ctl_task_init'
> > > undefined symbol '_ctl_get_current_time'
> > > undefined symbol '_ctl_timeout_wait'
> > > undefined symbol '_ctl_events_set_clear'
> > > undefined symbol '_ctl_task_run'
> > > undefined symbol '_ctl_events_wait'
> > > Build failed
> > >
> > > So obviously I'm not including something that I should be? I
> > > verified that the ctl_api.h file is being found by
> > > crossworks. Any suggestions?
> > >
> > > -Micah
> > >
> > >
> > > .
> > >
> > >
> > > >.
> >
> >
>
>
>
> .
>
>
>
>
> *
> click here 
>
<http://www.netflix.com/Default?mqso`190075>" target="_blank" rel="nofollow">http://us.ard.yahoo.com/SIG9mqt6g3/M)8184.6191685.7192823.3001176/D=groups/S05005378:HM/EXP11769600/A%93423/R=0/SIGel9gslf/*http://www.netflix.com/Default?mqso`190075>

>
>
>
> 
> *>.
>
>

Micah,

I am not the best person to ask about CTL as Michael implemented it.  I
expect he'll respond at some point over Easter.

-- Paul.

> -----Original Message-----
> From: Micah [mailto:micah@mica...]
> Sent: 24 March 2005 18:16
> To: msp430@msp4...
> Subject: Re: [msp430] Crossworks tasking library
> 
> 
> 
> Hi again Paul,
> 
> I'm running tasking successfully now, thanks for your help, 
> but there's 
> some questions that I'm having. Here's my test case (based pretty

> heavily on your example code):
> 
> Main task starts at 255 priority
> Initialize IO, and tasks (memset and all that)
> run task timer_task priority 2 (does nothing, just sets event so that 
> blink will execute as in the example)
> run task blink_task priority 2 (flashed the LED)
> run task button_task priority 1 (checks to see if the button 
> is pushed, 
> if so, light second LED)
> switch main priority to 0
> while (1) {}
> 
> I also have a timer interrupt on A0 that is calling the increment 
> current time CTL function.
> 
> Now, questions:
> The CTL time doesn't seem to increment. I'm watching the 
> global variabl, 
> and although the timer ISR is calling the function to increment it, 
> nothing happens? For some reason it just sits at 0x3da.
> 
> two of my functions have priority 2 and run back and forth. The lower 
> priority function button never seems to run. Is this normal? I would 
> assume it would just run less often, but apparently as the priority 2 
> functions always are doing something, they will never relinquish 
> control. To allow them to pause occasionally, I was going to 
> try making 
> them wait a bit. But as the CTL timer never increments, the function 
> never execute if I put in a ctl_timeout_wait(ctl_get_current_time() + 
> 10) command.
> 
> I'm turning off interrupts in the timer ISR as suggested.
> 
> Any clue as to why the current time never increments? Any 
> suggestion on 
> what to check? Thank you!
> -Micah
> 
> 
> Micah wrote:
> 
> > That was indeed the problem. Thanks again for a prompt 
> response. Back to
> > my code!
> >
> > -Micah
> >
> > Paul Curtis wrote:
> >
> > > Hi Micah,
> > >
> > > Did you create a new CTL project using the project 
> wizard?  We suspect
> > > not.
> > >
> > > If not, don't worry, you'll need to do a couple of
things 
> so that it
> > > will link successfully:
> > >
> > > (a) Click the project node in the Project explorer.
> > > (b) Show the Properties Window.
> > > (c) In the Linker Options group, set Use Multi Threaded 
> Libraries to
> > > Yes.
> > > (e) In the Linker Options group, set the Additional Input Files
to
> > > "$(StudioDir)/ctl/lib/libctl$(LibExt).hza".
> > >
> > > You can also set the User Include Directories to
> > > "$(StudioDir)/ctl/include;." and that will find the CTL

> API for you.
> > >
> > > This is all set up for you if you use select CTL 
> Executable from the CTL
> > > Projects folder in the New Project wizard.
> > >
> > > Regards,
> > >
> > > --
> > > Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> > > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
> > >
> > > > -----Original Message-----
> > > > From: Micah [mailto:micah@mica...]
> > > > Sent: 24 March 2005 16:26
> > > > To: msp430@msp4...
> > > > Subject: [msp430] Crossworks tasking library
> > > >
> > > >
> > > > Okay,
> > > >
> > > > I've been setting up a test case using the crossworks
tasking
> > > > library.
> > > > I've included the ctl_api.h header, and during the
build,
> > > > none of the tasking functions are found. Here's the
error:
> > > >
> > > > Build active project - 230 ms - 9 errors Building
"Portacom
> > > > Tasking" in configuration "Debug" - 9 errors
Compiling main.c
> > > > Linking Portacom Tasking.hzx - 9 errors undefined symbol
> > > > '_ctl_interrupt_count'
> > > > undefined symbol '_ctl_exit_isr'
> > > > undefined symbol '_ctl_increment_tick_from_isr'
> > > > undefined symbol '_ctl_task_init'
> > > > undefined symbol '_ctl_get_current_time'
> > > > undefined symbol '_ctl_timeout_wait'
> > > > undefined symbol '_ctl_events_set_clear'
> > > > undefined symbol '_ctl_task_run'
> > > > undefined symbol '_ctl_events_wait'
> > > > Build failed
> > > >
> > > > So obviously I'm not including something that I should
be? I
> > > > verified that the ctl_api.h file is being found by
> > > > crossworks. Any suggestions?
> > > >
> > > > -Micah
> > > >
> > > >
> > > > .
> > > >
> > > >
> > > > >.
> > >
> > >
> >
> >
> >
> > .
> >
> >
> >
> >
> > *
> > click here 
> > 
> <http://us.ard.yahoo.com/SIG9mqt6g3/M)8184.6191685.719282
3.3001176/D=groups/S05005378:HM/EXP11769600/A%93423/R=0/SIGel
9gslf/*http://www.netflix.com/Default?mqso`190075> 
>
>
>
>

> *>.
>
>



.

 
Yahoo! Groups Links



 

Thank you Paul.

Paul Curtis wrote:

> Micah,
>
> I am not the best person to ask about CTL as Michael implemented it.  I
> expect he'll respond at some point over Easter.
>
> -- Paul.
>
> > -----Original Message-----
> > From: Micah [mailto:micah@mica...]
> > Sent: 24 March 2005 18:16
> > To: msp430@msp4...
> > Subject: Re: [msp430] Crossworks tasking library
> >
> >
> >
> > Hi again Paul,
> >
> > I'm running tasking successfully now, thanks for your help,
> > but there's
> > some questions that I'm having. Here's my test case (based
pretty
> > heavily on your example code):
> >
> > Main task starts at 255 priority
> > Initialize IO, and tasks (memset and all that)
> > run task timer_task priority 2 (does nothing, just sets event so that
> > blink will execute as in the example)
> > run task blink_task priority 2 (flashed the LED)
> > run task button_task priority 1 (checks to see if the button
> > is pushed,
> > if so, light second LED)
> > switch main priority to 0
> > while (1) {}
> >
> > I also have a timer interrupt on A0 that is calling the increment
> > current time CTL function.
> >
> > Now, questions:
> > The CTL time doesn't seem to increment. I'm watching the
> > global variabl,
> > and although the timer ISR is calling the function to increment it,
> > nothing happens? For some reason it just sits at 0x3da.
> >
> > two of my functions have priority 2 and run back and forth. The lower
> > priority function button never seems to run. Is this normal? I would
> > assume it would just run less often, but apparently as the priority 2
> > functions always are doing something, they will never relinquish
> > control. To allow them to pause occasionally, I was going to
> > try making
> > them wait a bit. But as the CTL timer never increments, the function
> > never execute if I put in a ctl_timeout_wait(ctl_get_current_time() +
> > 10) command.
> >
> > I'm turning off interrupts in the timer ISR as suggested.
> >
> > Any clue as to why the current time never increments? Any
> > suggestion on
> > what to check? Thank you!
> > -Micah
> >
> >
> > Micah wrote:
> >
> > > That was indeed the problem. Thanks again for a prompt
> > response. Back to
> > > my code!
> > >
> > > -Micah
> > >
> > > Paul Curtis wrote:
> > >
> > > > Hi Micah,
> > > >
> > > > Did you create a new CTL project using the project
> > wizard?  We suspect
> > > > not.
> > > >
> > > > If not, don't worry, you'll need to do a couple of
things
> > so that it
> > > > will link successfully:
> > > >
> > > > (a) Click the project node in the Project explorer.
> > > > (b) Show the Properties Window.
> > > > (c) In the Linker Options group, set Use Multi Threaded
> > Libraries to
> > > > Yes.
> > > > (e) In the Linker Options group, set the Additional Input
Files to
> > > > "$(StudioDir)/ctl/lib/libctl$(LibExt).hza".
> > > >
> > > > You can also set the User Include Directories to
> > > > "$(StudioDir)/ctl/include;." and that will find
the CTL
> > API for you.
> > > >
> > > > This is all set up for you if you use select CTL
> > Executable from the CTL
> > > > Projects folder in the New Project wizard.
> > > >
> > > > Regards,
> > > >
> > > > --
> > > > Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> > > > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
> > > >
> > > > > -----Original Message-----
> > > > > From: Micah [mailto:micah@mica...]
> > > > > Sent: 24 March 2005 16:26
> > > > > To: msp430@msp4...
> > > > > Subject: [msp430] Crossworks tasking library
> > > > >
> > > > >
> > > > > Okay,
> > > > >
> > > > > I've been setting up a test case using the
crossworks tasking
> > > > > library.
> > > > > I've included the ctl_api.h header, and during the
build,
> > > > > none of the tasking functions are found. Here's
the error:
> > > > >
> > > > > Build active project - 230 ms - 9 errors Building
"Portacom
> > > > > Tasking" in configuration "Debug" - 9
errors Compiling main.c
> > > > > Linking Portacom Tasking.hzx - 9 errors undefined
symbol
> > > > > '_ctl_interrupt_count'
> > > > > undefined symbol '_ctl_exit_isr'
> > > > > undefined symbol
'_ctl_increment_tick_from_isr'
> > > > > undefined symbol '_ctl_task_init'
> > > > > undefined symbol '_ctl_get_current_time'
> > > > > undefined symbol '_ctl_timeout_wait'
> > > > > undefined symbol '_ctl_events_set_clear'
> > > > > undefined symbol '_ctl_task_run'
> > > > > undefined symbol '_ctl_events_wait'
> > > > > Build failed
> > > > >
> > > > > So obviously I'm not including something that I
should be? I
> > > > > verified that the ctl_api.h file is being found by
> > > > > crossworks. Any suggestions?
> > > > >
> > > > > -Micah
> > > > >
> > > > >
> > > > > .
> > > > >
> > > > >
> > > > > >.
> > > >
> > > >
> > >
> > >
> > >
> > > .
> > >
> > >
> > >
> > >
> > > *
> > > click here
> > >
> > <http://us.ard.yahoo.com/SIG9mqt6g3/M)8184.6191685.719282
> 3.3001176/D=groups/S05005378:HM/EXP11769600/A%93423/R=0/SIGel
> 9gslf/*http://www.netflix.com/Default?mqso`190075>
> >
> >
> >
> >
> 
> > *>.
> >
> >
>
>
>
> .
>
>
> >.
>
>

Hi Micah

> Micah,
>
> I am not the best person to ask about CTL as Michael implemented it.  
> I expect he'll respond at some point over Easter.
>
> -- Paul.
>
> > -----Original Message-----
> > From: Micah [mailto:micah@mica...]
> > Sent: 24 March 2005 18:16
> > To: msp430@msp4...
> > Subject: Re: [msp430] Crossworks tasking library
> >
> >
> >
> > Hi again Paul,
> >
> > I'm running tasking successfully now, thanks for your help,
> > but there's
> > some questions that I'm having. Here's my test case (based
pretty
> > heavily on your example code):
> >
> > Main task starts at 255 priority
> > Initialize IO, and tasks (memset and all that)
> > run task timer_task priority 2 (does nothing, just sets event so that
> > blink will execute as in the example)
> > run task blink_task priority 2 (flashed the LED)
> > run task button_task priority 1 (checks to see if the button
> > is pushed,
> > if so, light second LED)
> > switch main priority to 0
> > while (1) {}
> >
> > I also have a timer interrupt on A0 that is calling the increment
> > current time CTL function.
> >
> > Now, questions:
> > The CTL time doesn't seem to increment. I'm watching the
> > global variabl,
> > and although the timer ISR is calling the function to increment it,
> > nothing happens? For some reason it just sits at 0x3da.
>
Sounds like a stack allocation problem -  try increasing the stack sizes 
of your threads.

> >
> > two of my functions have priority 2 and run back and forth. The lower
> > priority function button never seems to run. Is this normal? I would
> > assume it would just run less often, but apparently as the priority 2
> > functions always are doing something, they will never relinquish
> > control. To allow them to pause occasionally, I was going to
> > try making
> > them wait a bit. But as the CTL timer never increments, the function
> > never execute if I put in a ctl_timeout_wait(ctl_get_current_time() +
> > 10) command.
>
The CTL will not preempt a task for one of the same priority. If you 
have multiple tasks of the same priority and you want them to share the 
CPU then you have to call the CTL function that does a reschedule (no 
timer waiting is required). I considered putting a timeslice option into 
the CTL that enables the preempting of tasks of the same priority based 
on a timeout - but it didn't happen.

> >
> > I'm turning off interrupts in the timer ISR as suggested.
> >
> > Any clue as to why the current time never increments? Any
> > suggestion on
> > what to check? Thank you!
>
Check the stack sizes - if that doesn't cure the problem then get
back 
to me.

Regards
Michael

> > -Micah
> >
> >
> > Micah wrote:
> >
> > > That was indeed the problem. Thanks again for a prompt
> > response. Back to
> > > my code!
> > >
> > > -Micah
> > >
> > > Paul Curtis wrote:
> > >
> > > > Hi Micah,
> > > >
> > > > Did you create a new CTL project using the project
> > wizard?  We suspect
> > > > not.
> > > >
> > > > If not, don't worry, you'll need to do a couple of
things
> > so that it
> > > > will link successfully:
> > > >
> > > > (a) Click the project node in the Project explorer.
> > > > (b) Show the Properties Window.
> > > > (c) In the Linker Options group, set Use Multi Threaded
> > Libraries to
> > > > Yes.
> > > > (e) In the Linker Options group, set the Additional Input
Files to
> > > > "$(StudioDir)/ctl/lib/libctl$(LibExt).hza".
> > > >
> > > > You can also set the User Include Directories to
> > > > "$(StudioDir)/ctl/include;." and that will find
the CTL
> > API for you.
> > > >
> > > > This is all set up for you if you use select CTL
> > Executable from the CTL
> > > > Projects folder in the New Project wizard.
> > > >
> > > > Regards,
> > > >
> > > > --
> > > > Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> > > > CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
> > > >
> > > > > -----Original Message-----
> > > > > From: Micah [mailto:micah@mica...]
> > > > > Sent: 24 March 2005 16:26
> > > > > To: msp430@msp4...
> > > > > Subject: [msp430] Crossworks tasking library
> > > > >
> > > > >
> > > > > Okay,
> > > > >
> > > > > I've been setting up a test case using the
crossworks tasking
> > > > > library.
> > > > > I've included the ctl_api.h header, and during the
build,
> > > > > none of the tasking functions are found. Here's
the error:
> > > > >
> > > > > Build active project - 230 ms - 9 errors Building
"Portacom
> > > > > Tasking" in configuration "Debug" - 9
errors Compiling main.c
> > > > > Linking Portacom Tasking.hzx - 9 errors undefined
symbol
> > > > > '_ctl_interrupt_count'
> > > > > undefined symbol '_ctl_exit_isr'
> > > > > undefined symbol
'_ctl_increment_tick_from_isr'
> > > > > undefined symbol '_ctl_task_init'
> > > > > undefined symbol '_ctl_get_current_time'
> > > > > undefined symbol '_ctl_timeout_wait'
> > > > > undefined symbol '_ctl_events_set_clear'
> > > > > undefined symbol '_ctl_task_run'
> > > > > undefined symbol '_ctl_events_wait'
> > > > > Build failed
> > > > >
> > > > > So obviously I'm not including something that I
should be? I
> > > > > verified that the ctl_api.h file is being found by
> > > > > crossworks. Any suggestions?
> > > > >
> > > > > -Micah
> > > > >
> > > > >
> > > > > .
> > > > >
> > > > >
> > > > > >.
> > > >
> > > >
> > >
> > >
> > >
> > > .
> > >
> > >
> > >
> > >
> > > *
> > > click here
> > >
> > <http://us.ard.yahoo.com/SIG9mqt6g3/M)8184.6191685.719282
>
3.3001176/D=groups/S05005378:HM/EXP11769600/A%93423/R=0/SIGel9gslf/*http://www.netflix.com/Default?mqso`190075>

>
>
> >
> >
> >
> > 
> 
> > *>.
> >
> >
>
>
>
> .
>
>  
> Yahoo! Groups Links
>
>
>
>  
>
>
>