Reply by jdw_atx January 7, 20032003-01-07
Art,

> Thanks, John, I will send you a test case, that will run on the
>DSP56F805EVM module, hopefully this morning. I was a bit rushed
>last night, had an early dinner engagement, so I couldn't work on it
>last night...

Art, that would be great. I have received the necessary header files
from Greg this morning to be able to at least disassemble the task.c
file, but a test case on the DSP56F805EVM would be even better.
Please email me the test case as soon as you can get time to create
it. We will get you a response then as soon as we determine
something.

Regards,
John

--- In , "Art Johnson" <art@p...> wrote:
> Thanks, John, I will send you a test case, that will run on the
DSP56F805EVM module, hopefully this morning. I was a bit rushed last
night, had an early dinner engagement, so I couldn't work on it last
night...
>
> I do appreciate your very fast responses to our problems, and I'm
sure we can work together to quickly solve this problem.
>
> Regards,
> Art > -----Original Message-----
> From: jdw_atx <jdw_atx@y...> [mailto:jdw_atx@y...]
> Sent: Monday, January 06, 2003 5:36 PM
> To:
> Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem > Art,
>
> I have sent an email to Greg Coonley to follow up on your bug
> report. However, I must say that I can't determine too much from
> just the source and the raw assembly output. I can't disassemble
the
> file and I don't know enough about what the behavior should be that
I
> can't really begin a true investigation at this point. Perhaps if
> you could provide a mixed view or something it might help me to
> investigate more. In the meantime, I will await what Greg says to
> guide my actions. Just wanted to let you know I was following
up....
>
> Regards,
> John
>
> --- In , "Art Johnson" <art@p...> wrote:
> > John,
> >
> > I have found the source of the problem, and it is very serious.
In
> order to initialize the DSPOS RTOS, you call the function
> Initialize_Os(). This function sets up all of the variables and
> structures that are required for the RTOS to function.
> >
> > I have compared the source code for the function Initialize_Os(),
> to the object code produced by CodeWarrior version 5.0.3, and they
> are drastically different. The assembly code for the function
starts
> out OK, correctly following the C source code, but after the first
20
> lines, any similarity between the assembly code and the original C
> source code completely vanishes.
> >
> > I will send you privately the files with the source code and the
> assembly output code, so your team can start working on this
> problem. You will probably want to work closely with Greg Coonley
at
> DSPOS, as the bad code is being produced for a DSPOS library
> function, so it has nothing to do with our project here.
> >
> > I hope this problem can be resolved quickly, as my work is
> completely at a standstill until this bug is fixed. Please let me
> know if there is anything more I can do, to expedite the solution
for
> this very serious problem. Thank you.
> >
> > Regards,
> >
> > Art Johnson
> > Senior Systems Analyst
> > PMC Prime Mover Controls Inc.
> > 3600 Gilmore Way
> > Burnaby, B.C., Canada
> > V5G 4R8
> > Phone: 604 433-4644
> > FAX: 604 433-5570
> > Email: art@p...
> > http://www.pmc-controls.com
> >
> >
> >
> > -----Original Message-----
> > From: jdw_atx <jdw_atx@y...> [mailto:jdw_atx@y...]
> > Sent: Monday, January 06, 2003 12:24 PM
> > To:
> > Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem
> >
> >
> > Art,
> >
> > Sorry to hear about the problem with your project. Please let us
> > know here at Metrowerks if we can do anything to help when you
> > discover something or if you believe that possibly there is
> something
> > that we can address.
> >
> > Either send to support@m... or you can email me separately.
> >
> > Regards,
> > John
> >
> > --- In , "Art Johnson" <art@p...>
wrote:
> > > Just thought I should warn everyone, I just compiled and
> downloaded
> > one of our projects using Codewarrior version 5.0.3, and it
locked
> up
> > solid, the Watchdog Timer times out, and keeps resetting the
CPU.
> > I'm just starting to troubleshoot it now. This program was
working
> > perfectly under CodeWarrior version 5.0.2, and in fact I
downloaded
> > it to my test boards less than 30 minutes ago (using 5.0.2), and
it
> > works OK. I downloaded the identical program (ie *NO* source
code
> > changes, only recompiled (including all libraries)), using
> > CodeWarrior version 5.0.3, and it locks up solid.
> > >
> > > Also, the code bloat has become considerably worse, this
> particular
> > program just got 0x0230 (560 decimal) words larger, the only
change
> > being the upgrade to CodeWarrior version 5.0.3.
> > >
> > > I will keep everyone advised on my progress in troubleshooting
> and
> > solving this problem.
> > >
> > > Regards,
> > >
> > > Art Johnson
> > > Senior Systems Analyst
> > > PMC Prime Mover Controls Inc.
> > > 3600 Gilmore Way
> > > Burnaby, B.C., Canada
> > > V5G 4R8
> > > Phone: 604 433-4644
> > > FAX: 604 433-5570
> > > Email: art@p...
> > > http://www.pmc-controls.com
> > >
> > >
> > > _____________________________________
> > > Note: If you do a simple "reply" with your email client, only
the
> > author of this message will receive your answer. You need to do
> > a "reply all" if you want your answer to be distributed to the
> entire
> > group.
> > >
> > > _____________________________________
> > > About this discussion group:
> > >
> > > To Join:
> > >
> > > To Post:
> > >
> > > To Leave:
> > >
> > > Archives: http://www.yahoogroups.com/group/motoroladsp
> > >
> > > More Groups: http://www.dsprelated.com/groups.php3
> > >
> > >
> > > ">http://docs.yahoo.com/info/terms/
> >
> >
> > _____________________________________
> > Note: If you do a simple "reply" with your email client, only the
> author of this message will receive your answer. You need to do
> a "reply all" if you want your answer to be distributed to the
entire
> group.
> >
> > _____________________________________
> > About this discussion group:
> >
> > To Join:
> >
> > To Post:
> >
> > To Leave:
> >
> > Archives: http://www.yahoogroups.com/group/motoroladsp
> >
> > More Groups: http://www.dsprelated.com/groups.php3
> >
> >
> > ">http://docs.yahoo.com/info/terms/ >
> _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author of this message will receive your answer. You need to do
a "reply all" if you want your answer to be distributed to the entire
group.
>
> _____________________________________
> About this discussion group:
>
> To Join:
>
> To Post:
>
> To Leave:
>
> Archives: http://www.yahoogroups.com/group/motoroladsp
>
> More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/


Reply by Art Johnson January 7, 20032003-01-07
Thanks, John, I will send you a test case, that will run on the DSP56F805EVM
module, hopefully this morning. I was a bit rushed last night, had an early
dinner engagement, so I couldn't work on it last night...

I do appreciate your very fast responses to our problems, and I'm sure we can
work together to quickly solve this problem.

Regards,
Art -----Original Message-----
From: jdw_atx <> [mailto:]
Sent: Monday, January 06, 2003 5:36 PM
To:
Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem Art,

I have sent an email to Greg Coonley to follow up on your bug
report. However, I must say that I can't determine too much from
just the source and the raw assembly output. I can't disassemble the
file and I don't know enough about what the behavior should be that I
can't really begin a true investigation at this point. Perhaps if
you could provide a mixed view or something it might help me to
investigate more. In the meantime, I will await what Greg says to
guide my actions. Just wanted to let you know I was following up....

Regards,
John

--- In , "Art Johnson" <art@p...> wrote:
> John,
>
> I have found the source of the problem, and it is very serious. In
order to initialize the DSPOS RTOS, you call the function
Initialize_Os(). This function sets up all of the variables and
structures that are required for the RTOS to function.
>
> I have compared the source code for the function Initialize_Os(),
to the object code produced by CodeWarrior version 5.0.3, and they
are drastically different. The assembly code for the function starts
out OK, correctly following the C source code, but after the first 20
lines, any similarity between the assembly code and the original C
source code completely vanishes.
>
> I will send you privately the files with the source code and the
assembly output code, so your team can start working on this
problem. You will probably want to work closely with Greg Coonley at
DSPOS, as the bad code is being produced for a DSPOS library
function, so it has nothing to do with our project here.
>
> I hope this problem can be resolved quickly, as my work is
completely at a standstill until this bug is fixed. Please let me
know if there is anything more I can do, to expedite the solution for
this very serious problem. Thank you.
>
> Regards,
>
> Art Johnson
> Senior Systems Analyst
> PMC Prime Mover Controls Inc.
> 3600 Gilmore Way
> Burnaby, B.C., Canada
> V5G 4R8
> Phone: 604 433-4644
> FAX: 604 433-5570
> Email: art@p...
> http://www.pmc-controls.com >
> -----Original Message-----
> From: jdw_atx <jdw_atx@y...> [mailto:jdw_atx@y...]
> Sent: Monday, January 06, 2003 12:24 PM
> To:
> Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem > Art,
>
> Sorry to hear about the problem with your project. Please let us
> know here at Metrowerks if we can do anything to help when you
> discover something or if you believe that possibly there is
something
> that we can address.
>
> Either send to support@m... or you can email me separately.
>
> Regards,
> John
>
> --- In , "Art Johnson" <art@p...> wrote:
> > Just thought I should warn everyone, I just compiled and
downloaded
> one of our projects using Codewarrior version 5.0.3, and it locked
up
> solid, the Watchdog Timer times out, and keeps resetting the CPU.
> I'm just starting to troubleshoot it now. This program was working
> perfectly under CodeWarrior version 5.0.2, and in fact I downloaded
> it to my test boards less than 30 minutes ago (using 5.0.2), and it
> works OK. I downloaded the identical program (ie *NO* source code
> changes, only recompiled (including all libraries)), using
> CodeWarrior version 5.0.3, and it locks up solid.
> >
> > Also, the code bloat has become considerably worse, this
particular
> program just got 0x0230 (560 decimal) words larger, the only change
> being the upgrade to CodeWarrior version 5.0.3.
> >
> > I will keep everyone advised on my progress in troubleshooting
and
> solving this problem.
> >
> > Regards,
> >
> > Art Johnson
> > Senior Systems Analyst
> > PMC Prime Mover Controls Inc.
> > 3600 Gilmore Way
> > Burnaby, B.C., Canada
> > V5G 4R8
> > Phone: 604 433-4644
> > FAX: 604 433-5570
> > Email: art@p...
> > http://www.pmc-controls.com
> >
> >
> > _____________________________________
> > Note: If you do a simple "reply" with your email client, only the
> author of this message will receive your answer. You need to do
> a "reply all" if you want your answer to be distributed to the
entire
> group.
> >
> > _____________________________________
> > About this discussion group:
> >
> > To Join:
> >
> > To Post:
> >
> > To Leave:
> >
> > Archives: http://www.yahoogroups.com/group/motoroladsp
> >
> > More Groups: http://www.dsprelated.com/groups.php3
> >
> >
> > ">http://docs.yahoo.com/info/terms/ > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author of this message will receive your answer. You need to do
a "reply all" if you want your answer to be distributed to the entire
group.
>
> _____________________________________
> About this discussion group:
>
> To Join:
>
> To Post:
>
> To Leave:
>
> Archives: http://www.yahoogroups.com/group/motoroladsp
>
> More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/
_____________________________________
Note: If you do a simple "reply" with your email client, only the author of this
message will receive your answer. You need to do a "reply all" if you want your
answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/



Reply by jdw_atx January 7, 20032003-01-07
Art,

I have sent an email to Greg Coonley to follow up on your bug
report. However, I must say that I can't determine too much from
just the source and the raw assembly output. I can't disassemble the
file and I don't know enough about what the behavior should be that I
can't really begin a true investigation at this point. Perhaps if
you could provide a mixed view or something it might help me to
investigate more. In the meantime, I will await what Greg says to
guide my actions. Just wanted to let you know I was following up....

Regards,
John

--- In , "Art Johnson" <art@p...> wrote:
> John,
>
> I have found the source of the problem, and it is very serious. In
order to initialize the DSPOS RTOS, you call the function
Initialize_Os(). This function sets up all of the variables and
structures that are required for the RTOS to function.
>
> I have compared the source code for the function Initialize_Os(),
to the object code produced by CodeWarrior version 5.0.3, and they
are drastically different. The assembly code for the function starts
out OK, correctly following the C source code, but after the first 20
lines, any similarity between the assembly code and the original C
source code completely vanishes.
>
> I will send you privately the files with the source code and the
assembly output code, so your team can start working on this
problem. You will probably want to work closely with Greg Coonley at
DSPOS, as the bad code is being produced for a DSPOS library
function, so it has nothing to do with our project here.
>
> I hope this problem can be resolved quickly, as my work is
completely at a standstill until this bug is fixed. Please let me
know if there is anything more I can do, to expedite the solution for
this very serious problem. Thank you.
>
> Regards,
>
> Art Johnson
> Senior Systems Analyst
> PMC Prime Mover Controls Inc.
> 3600 Gilmore Way
> Burnaby, B.C., Canada
> V5G 4R8
> Phone: 604 433-4644
> FAX: 604 433-5570
> Email: art@p...
> http://www.pmc-controls.com >
> -----Original Message-----
> From: jdw_atx <jdw_atx@y...> [mailto:jdw_atx@y...]
> Sent: Monday, January 06, 2003 12:24 PM
> To:
> Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem > Art,
>
> Sorry to hear about the problem with your project. Please let us
> know here at Metrowerks if we can do anything to help when you
> discover something or if you believe that possibly there is
something
> that we can address.
>
> Either send to support@m... or you can email me separately.
>
> Regards,
> John
>
> --- In , "Art Johnson" <art@p...> wrote:
> > Just thought I should warn everyone, I just compiled and
downloaded
> one of our projects using Codewarrior version 5.0.3, and it locked
up
> solid, the Watchdog Timer times out, and keeps resetting the CPU.
> I'm just starting to troubleshoot it now. This program was working
> perfectly under CodeWarrior version 5.0.2, and in fact I downloaded
> it to my test boards less than 30 minutes ago (using 5.0.2), and it
> works OK. I downloaded the identical program (ie *NO* source code
> changes, only recompiled (including all libraries)), using
> CodeWarrior version 5.0.3, and it locks up solid.
> >
> > Also, the code bloat has become considerably worse, this
particular
> program just got 0x0230 (560 decimal) words larger, the only change
> being the upgrade to CodeWarrior version 5.0.3.
> >
> > I will keep everyone advised on my progress in troubleshooting
and
> solving this problem.
> >
> > Regards,
> >
> > Art Johnson
> > Senior Systems Analyst
> > PMC Prime Mover Controls Inc.
> > 3600 Gilmore Way
> > Burnaby, B.C., Canada
> > V5G 4R8
> > Phone: 604 433-4644
> > FAX: 604 433-5570
> > Email: art@p...
> > http://www.pmc-controls.com
> >
> >
> > _____________________________________
> > Note: If you do a simple "reply" with your email client, only the
> author of this message will receive your answer. You need to do
> a "reply all" if you want your answer to be distributed to the
entire
> group.
> >
> > _____________________________________
> > About this discussion group:
> >
> > To Join:
> >
> > To Post:
> >
> > To Leave:
> >
> > Archives: http://www.yahoogroups.com/group/motoroladsp
> >
> > More Groups: http://www.dsprelated.com/groups.php3
> >
> >
> > ">http://docs.yahoo.com/info/terms/ > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author of this message will receive your answer. You need to do
a "reply all" if you want your answer to be distributed to the entire
group.
>
> _____________________________________
> About this discussion group:
>
> To Join:
>
> To Post:
>
> To Leave:
>
> Archives: http://www.yahoogroups.com/group/motoroladsp
>
> More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/


Reply by Art Johnson January 7, 20032003-01-07
John,

I have found the source of the problem, and it is very serious. In order to
initialize the DSPOS RTOS, you call the function Initialize_Os(). This function
sets up all of the variables and structures that are required for the RTOS to
function.

I have compared the source code for the function Initialize_Os(), to the object
code produced by CodeWarrior version 5.0.3, and they are drastically different.
The assembly code for the function starts out OK, correctly following the C
source code, but after the first 20 lines, any similarity between the assembly
code and the original C source code completely vanishes.

I will send you privately the files with the source code and the assembly output
code, so your team can start working on this problem. You will probably want to
work closely with Greg Coonley at DSPOS, as the bad code is being produced for a
DSPOS library function, so it has nothing to do with our project here.

I hope this problem can be resolved quickly, as my work is completely at a
standstill until this bug is fixed. Please let me know if there is anything
more I can do, to expedite the solution for this very serious problem. Thank
you.

Regards,

Art Johnson
Senior Systems Analyst
PMC Prime Mover Controls Inc.
3600 Gilmore Way
Burnaby, B.C., Canada
V5G 4R8
Phone: 604 433-4644
FAX: 604 433-5570
Email:
http://www.pmc-controls.com
-----Original Message-----
From: jdw_atx <> [mailto:]
Sent: Monday, January 06, 2003 12:24 PM
To:
Subject: [motoroladsp] Re: CodeWarrior version 5.0.3 problem Art,

Sorry to hear about the problem with your project. Please let us
know here at Metrowerks if we can do anything to help when you
discover something or if you believe that possibly there is something
that we can address.

Either send to or you can email me separately.

Regards,
John

--- In , "Art Johnson" <art@p...> wrote:
> Just thought I should warn everyone, I just compiled and downloaded
one of our projects using Codewarrior version 5.0.3, and it locked up
solid, the Watchdog Timer times out, and keeps resetting the CPU.
I'm just starting to troubleshoot it now. This program was working
perfectly under CodeWarrior version 5.0.2, and in fact I downloaded
it to my test boards less than 30 minutes ago (using 5.0.2), and it
works OK. I downloaded the identical program (ie *NO* source code
changes, only recompiled (including all libraries)), using
CodeWarrior version 5.0.3, and it locks up solid.
>
> Also, the code bloat has become considerably worse, this particular
program just got 0x0230 (560 decimal) words larger, the only change
being the upgrade to CodeWarrior version 5.0.3.
>
> I will keep everyone advised on my progress in troubleshooting and
solving this problem.
>
> Regards,
>
> Art Johnson
> Senior Systems Analyst
> PMC Prime Mover Controls Inc.
> 3600 Gilmore Way
> Burnaby, B.C., Canada
> V5G 4R8
> Phone: 604 433-4644
> FAX: 604 433-5570
> Email: art@p...
> http://www.pmc-controls.com > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author of this message will receive your answer. You need to do
a "reply all" if you want your answer to be distributed to the entire
group.
>
> _____________________________________
> About this discussion group:
>
> To Join:
>
> To Post:
>
> To Leave:
>
> Archives: http://www.yahoogroups.com/group/motoroladsp
>
> More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/ _____________________________________
Note: If you do a simple "reply" with your email client, only the author of this
message will receive your answer. You need to do a "reply all" if you want your
answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/



Reply by jdw_atx January 6, 20032003-01-06
Art,

Sorry to hear about the problem with your project. Please let us
know here at Metrowerks if we can do anything to help when you
discover something or if you believe that possibly there is something
that we can address.

Either send to or you can email me separately.

Regards,
John

--- In , "Art Johnson" <art@p...> wrote:
> Just thought I should warn everyone, I just compiled and downloaded
one of our projects using Codewarrior version 5.0.3, and it locked up
solid, the Watchdog Timer times out, and keeps resetting the CPU.
I'm just starting to troubleshoot it now. This program was working
perfectly under CodeWarrior version 5.0.2, and in fact I downloaded
it to my test boards less than 30 minutes ago (using 5.0.2), and it
works OK. I downloaded the identical program (ie *NO* source code
changes, only recompiled (including all libraries)), using
CodeWarrior version 5.0.3, and it locks up solid.
>
> Also, the code bloat has become considerably worse, this particular
program just got 0x0230 (560 decimal) words larger, the only change
being the upgrade to CodeWarrior version 5.0.3.
>
> I will keep everyone advised on my progress in troubleshooting and
solving this problem.
>
> Regards,
>
> Art Johnson
> Senior Systems Analyst
> PMC Prime Mover Controls Inc.
> 3600 Gilmore Way
> Burnaby, B.C., Canada
> V5G 4R8
> Phone: 604 433-4644
> FAX: 604 433-5570
> Email: art@p...
> http://www.pmc-controls.com > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author of this message will receive your answer. You need to do
a "reply all" if you want your answer to be distributed to the entire
group.
>
> _____________________________________
> About this discussion group:
>
> To Join:
>
> To Post:
>
> To Leave:
>
> Archives: http://www.yahoogroups.com/group/motoroladsp
>
> More Groups: http://www.dsprelated.com/groups.php3 > ">http://docs.yahoo.com/info/terms/


Reply by Art Johnson January 6, 20032003-01-06
Just thought I should warn everyone, I just compiled and downloaded one of our
projects using Codewarrior version 5.0.3, and it locked up solid, the Watchdog
Timer times out, and keeps resetting the CPU. I'm just starting to troubleshoot
it now. This program was working perfectly under CodeWarrior version 5.0.2, and
in fact I downloaded it to my test boards less than 30 minutes ago (using
5.0.2), and it works OK. I downloaded the identical program (ie *NO* source
code changes, only recompiled (including all libraries)), using CodeWarrior
version 5.0.3, and it locks up solid.

Also, the code bloat has become considerably worse, this particular program just
got 0x0230 (560 decimal) words larger, the only change being the upgrade to
CodeWarrior version 5.0.3.

I will keep everyone advised on my progress in troubleshooting and solving this
problem.

Regards,

Art Johnson
Senior Systems Analyst
PMC Prime Mover Controls Inc.
3600 Gilmore Way
Burnaby, B.C., Canada
V5G 4R8
Phone: 604 433-4644
FAX: 604 433-5570
Email:
http://www.pmc-controls.com _____________________________________
Note: If you do a simple "reply" with your email client, only the author of this
message will receive your answer. You need to do a "reply all" if you want your
answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/