HIWAVE/P&E Debugger

Started by Jonathan Masters December 9, 2005
Does anyone else have a poor opinion of the HIWAVE/P& Debugger
combination. I am having to work around a number of problems and it is
beginning to impede my progress. Any suggestions as to how to eliminate
would be appreciated:

i) As I have posted before, the system goes off in its
head for periods of about 20s. No amount of jiggling/reinstalling the
drivers has made any difference to this. This only clue to the cause may
be that I am simultaneously using an SILABS USB interface. When I was
using an FTDI one, the system seemed much worse.
ii) The memory window in HIWAVE tells lies. It does not
refresh appropriately and can be very misleading. The only way I can see
the true contents of the memory is to try and edit the location and then
cancel the operation. This seems to cause the system to read the actual
value. This is one byte at a time and is more than a bit tedious. This
problem seems to reflect in the data windows that also fail to show the
correct contents of memory. There doesn't seem to be any way of telling
HIWAVE to refresh the windows manually.
iii) HIWAVE looses track of breakpoints. If I
"run-to-cursor" and the program never gets to where I expect, sometimes
the temporary breakpoint created by this process won't go away. The
debugger shows no knowledge of this temporary breakpoint in the
"controlpoints configuration" window. Resetting the system makes no
difference. The only way around the problem is to restart the debugger
which for me is a problem because memory is erased and I have to reload
the data files that are loaded into eeprom separate from the
application.

Plenty has been said about BDM vs emulators, please don't let this post
turn into another excuse for bagging BDM. My experience of BDM debugging
has been good (in fact I wouldn't ever have become an HC12 user without
it). Plenty of criticism has also been leveled at P&E. While I have been
the victim of one or two of P&E's problems, there cables are cheap and
work well enough. My feelings here are leveled at the HIWAVE debugger
which I have always felt to be somewhat below par as part of the
CodeWarrior package.

Jonathan Masters


Jonathan:

I can offer some advice to alleviate point (ii). If you right click on
the memory window, the popup menu has a "Mode" entry. If you choose
"Periodical..." instead of "Automatic" from the "Mode" submenu, you can
set the window to update on a set period rather than when it detects a
memory change (eg, an initation of a write to said memory location).

Point (i).... what's the behavior you're experiencing specifically? Is
it just locking up (software) or are you losing communication with the
debug interface (hardware)?

You have my e-mail, so feel free to contact me directly if you'd prefer.

Regards,
Mark
P&E

Jonathan Masters wrote:

>Does anyone else have a poor opinion of the HIWAVE/P& Debugger
>combination. I am having to work around a number of problems and it is
>beginning to impede my progress. Any suggestions as to how to eliminate
>would be appreciated:
>
>i) As I have posted before, the system goes off in its
>head for periods of about 20s. No amount of jiggling/reinstalling the
>drivers has made any difference to this. This only clue to the cause may
>be that I am simultaneously using an SILABS USB interface. When I was
>using an FTDI one, the system seemed much worse.
>ii) The memory window in HIWAVE tells lies. It does not
>refresh appropriately and can be very misleading. The only way I can see
>the true contents of the memory is to try and edit the location and then
>cancel the operation. This seems to cause the system to read the actual
>value. This is one byte at a time and is more than a bit tedious. This
>problem seems to reflect in the data windows that also fail to show the
>correct contents of memory. There doesn't seem to be any way of telling
>HIWAVE to refresh the windows manually.
>iii) HIWAVE looses track of breakpoints. If I
>"run-to-cursor" and the program never gets to where I expect, sometimes
>the temporary breakpoint created by this process won't go away. The
>debugger shows no knowledge of this temporary breakpoint in the
>"controlpoints configuration" window. Resetting the system makes no
>difference. The only way around the problem is to restart the debugger
>which for me is a problem because memory is erased and I have to reload
>the data files that are loaded into eeprom separate from the
>application.
>
>Plenty has been said about BDM vs emulators, please don't let this post
>turn into another excuse for bagging BDM. My experience of BDM debugging
>has been good (in fact I wouldn't ever have become an HC12 user without
>it). Plenty of criticism has also been leveled at P&E. While I have been
>the victim of one or two of P&E's problems, there cables are cheap and
>work well enough. My feelings here are leveled at the HIWAVE debugger
>which I have always felt to be somewhat below par as part of the
>CodeWarrior package.
>
>Jonathan Masters >Yahoo! Groups Links >
>


--

--

____________________________
*Mark L. Cukier*, /Design Engineer/
P&E Microcomputer Systems
656 Beacon Street, Floor 2
Boston, MA 02215
_________________________________
e-mail: mark@mark... <mailto:mark@mark...>
phone : (617) 353-9206 x19
fax : (617) 353-9205
_________________________________

visit us on the web at: http: //www.pemicro.com


I had an issue with the P&E USB multilink that was in a message a
few months ago. It boiled down to a bug in the driver where it
attempted to open a com port. My pc has no com ports, and it took
right about 20 seconds for it to realize that and attempt to open a
usb port. This 20 second delay happened every time I made the
project. The computer just sat there. Almost unusable.

I dug into the driver code on the PC and patched over the call to
open the com port. I also told P&E and Freescale about it but I
don't think it was ever fixed.

At the time I was using the freescale s12x demo board with built in
USB BDM, which uses the same driver as the P&E USB multilink.

As far as I can tell, this would happen to everyone who tried that
board without a (totally unused in this case) hardware com port on
their machine.

Not a good experience for someone evaluating the CW tool suite. >
> >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> >combination. I am having to work around a number of problems and
it is
> >beginning to impede my progress. Any suggestions as to how to
eliminate
> >would be appreciated:
> >
> >i) As I have posted before, the system goes off
in its
> >head for periods of about 20s. No amount of jiggling/reinstalling
the
> >drivers has made any difference to this. This only clue to the
cause may
> >be that I am simultaneously using an SILABS USB interface. When I
was
> >using an FTDI one, the system seemed much worse.
> >ii) The memory window in HIWAVE tells lies. It
does not
> >refresh appropriately and can be very misleading. The only way I
can see
> >the true contents of the memory is to try and edit the location
and then
> >cancel the operation. This seems to cause the system to read the
actual
> >value. This is one byte at a time and is more than a bit tedious.
This
> >problem seems to reflect in the data windows that also fail to
show the
> >correct contents of memory. There doesn't seem to be any way of
telling
> >HIWAVE to refresh the windows manually.
> >iii) HIWAVE looses track of breakpoints. If I
> >"run-to-cursor" and the program never gets to where I expect,
sometimes
> >the temporary breakpoint created by this process won't go away.
The
> >debugger shows no knowledge of this temporary breakpoint in the
> >"controlpoints configuration" window. Resetting the system makes
no
> >difference. The only way around the problem is to restart the
debugger
> >which for me is a problem because memory is erased and I have to
reload
> >the data files that are loaded into eeprom separate from the
> >application.
> >
> >Plenty has been said about BDM vs emulators, please don't let
this post
> >turn into another excuse for bagging BDM. My experience of BDM
debugging
> >has been good (in fact I wouldn't ever have become an HC12 user
without
> >it). Plenty of criticism has also been leveled at P&E. While I
have been
> >the victim of one or two of P&E's problems, there cables are
cheap and
> >work well enough. My feelings here are leveled at the HIWAVE
debugger
> >which I have always felt to be somewhat below par as part of the
> >CodeWarrior package.
> >
> >Jonathan Masters
> >
> >
> >
> >
> >
> >
> >
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
>
> --
>
> ____________________________
> *Mark L. Cukier*, /Design Engineer/
> P&E Microcomputer Systems
> 656 Beacon Street, Floor 2
> Boston, MA 02215
> _________________________________
> e-mail: mark@p... <mailto:mark@p...>
> phone : (617) 353-9206 x19
> fax : (617) 353-9205
> _________________________________
>
> visit us on the web at: http: //www.pemicro.com
>




Tim

I'd say for certain this is the issue. I'll see what P&E say. I've
neither the skills or inclination to start digging into driver code.

Jonathan.

-----Original Message-----
From: 68HC12@68HC... [mailto:68HC12@68HC...] On Behalf
Of timjenison
Sent: Saturday, 10 December 2005 10:02 AM
To: 68HC12@68HC...
Subject: [68HC12] Re: HIWAVE/P&E Debugger

I had an issue with the P&E USB multilink that was in a message a
few months ago. It boiled down to a bug in the driver where it
attempted to open a com port. My pc has no com ports, and it took
right about 20 seconds for it to realize that and attempt to open a
usb port. This 20 second delay happened every time I made the
project. The computer just sat there. Almost unusable.

I dug into the driver code on the PC and patched over the call to
open the com port. I also told P&E and Freescale about it but I
don't think it was ever fixed.

At the time I was using the freescale s12x demo board with built in
USB BDM, which uses the same driver as the P&E USB multilink.

As far as I can tell, this would happen to everyone who tried that
board without a (totally unused in this case) hardware com port on
their machine.

Not a good experience for someone evaluating the CW tool suite. >
> >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> >combination. I am having to work around a number of problems and
it is
> >beginning to impede my progress. Any suggestions as to how to
eliminate
> >would be appreciated:
> >
> >i) As I have posted before, the system goes off
in its
> >head for periods of about 20s. No amount of jiggling/reinstalling
the
> >drivers has made any difference to this. This only clue to the
cause may
> >be that I am simultaneously using an SILABS USB interface. When I
was
> >using an FTDI one, the system seemed much worse.
> >ii) The memory window in HIWAVE tells lies. It
does not
> >refresh appropriately and can be very misleading. The only way I
can see
> >the true contents of the memory is to try and edit the location
and then
> >cancel the operation. This seems to cause the system to read the
actual
> >value. This is one byte at a time and is more than a bit tedious.
This
> >problem seems to reflect in the data windows that also fail to
show the
> >correct contents of memory. There doesn't seem to be any way of
telling
> >HIWAVE to refresh the windows manually.
> >iii) HIWAVE looses track of breakpoints. If I
> >"run-to-cursor" and the program never gets to where I expect,
sometimes
> >the temporary breakpoint created by this process won't go away.
The
> >debugger shows no knowledge of this temporary breakpoint in the
> >"controlpoints configuration" window. Resetting the system makes
no
> >difference. The only way around the problem is to restart the
debugger
> >which for me is a problem because memory is erased and I have to
reload
> >the data files that are loaded into eeprom separate from the
> >application.
> >
> >Plenty has been said about BDM vs emulators, please don't let
this post
> >turn into another excuse for bagging BDM. My experience of BDM
debugging
> >has been good (in fact I wouldn't ever have become an HC12 user
without
> >it). Plenty of criticism has also been leveled at P&E. While I
have been
> >the victim of one or two of P&E's problems, there cables are
cheap and
> >work well enough. My feelings here are leveled at the HIWAVE
debugger
> >which I have always felt to be somewhat below par as part of the
> >CodeWarrior package.
> >
> >Jonathan Masters
> >
> >
> >
> >
> >
> >
> >
> >
> >> Terms of Service.

_____


I could send you the patched dll.
> Tim
>
> I'd say for certain this is the issue. I'll see what P&E say. I've
> neither the skills or inclination to start digging into driver
code.
>
> Jonathan.
>
> -----Original Message-----
> From: 68HC12@68HC... [mailto:68HC12@68HC...] On
Behalf
> Of timjenison
> Sent: Saturday, 10 December 2005 10:02 AM
> To: 68HC12@68HC...
> Subject: [68HC12] Re: HIWAVE/P&E Debugger
>
> I had an issue with the P&E USB multilink that was in a message a
> few months ago. It boiled down to a bug in the driver where it
> attempted to open a com port. My pc has no com ports, and it took
> right about 20 seconds for it to realize that and attempt to open
a
> usb port. This 20 second delay happened every time I made the
> project. The computer just sat there. Almost unusable.
>
> I dug into the driver code on the PC and patched over the call to
> open the com port. I also told P&E and Freescale about it but I
> don't think it was ever fixed.
>
> At the time I was using the freescale s12x demo board with built
in
> USB BDM, which uses the same driver as the P&E USB multilink.
>
> As far as I can tell, this would happen to everyone who tried that
> board without a (totally unused in this case) hardware com port on
> their machine.
>
> Not a good experience for someone evaluating the CW tool suite. > >
> > >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> > >combination. I am having to work around a number of problems
and
> it is
> > >beginning to impede my progress. Any suggestions as to how to
> eliminate
> > >would be appreciated:
> > >
> > >i) As I have posted before, the system goes off
> in its
> > >head for periods of about 20s. No amount of
jiggling/reinstalling
> the
> > >drivers has made any difference to this. This only clue to the
> cause may
> > >be that I am simultaneously using an SILABS USB interface. When
I
> was
> > >using an FTDI one, the system seemed much worse.
> > >ii) The memory window in HIWAVE tells lies. It
> does not
> > >refresh appropriately and can be very misleading. The only way
I
> can see
> > >the true contents of the memory is to try and edit the location
> and then
> > >cancel the operation. This seems to cause the system to read
the
> actual
> > >value. This is one byte at a time and is more than a bit
tedious.
> This
> > >problem seems to reflect in the data windows that also fail to
> show the
> > >correct contents of memory. There doesn't seem to be any way of
> telling
> > >HIWAVE to refresh the windows manually.
> > >iii) HIWAVE looses track of breakpoints. If I
> > >"run-to-cursor" and the program never gets to where I expect,
> sometimes
> > >the temporary breakpoint created by this process won't go away.
> The
> > >debugger shows no knowledge of this temporary breakpoint in the
> > >"controlpoints configuration" window. Resetting the system
makes
> no
> > >difference. The only way around the problem is to restart the
> debugger
> > >which for me is a problem because memory is erased and I have
to
> reload
> > >the data files that are loaded into eeprom separate from the
> > >application.
> > >
> > >Plenty has been said about BDM vs emulators, please don't let
> this post
> > >turn into another excuse for bagging BDM. My experience of BDM
> debugging
> > >has been good (in fact I wouldn't ever have become an HC12 user
> without
> > >it). Plenty of criticism has also been leveled at P&E. While I
> have been
> > >the victim of one or two of P&E's problems, there cables are
> cheap and
> > >work well enough. My feelings here are leveled at the HIWAVE
> debugger
> > >which I have always felt to be somewhat below par as part of the
> > >CodeWarrior package.
> > >
> > >Jonathan Masters
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> Terms of Service.
>
> _____




Jonathan Masters wrote:
> Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> combination. I am having to work around a number of problems and it is
> beginning to impede my progress. Any suggestions as to how to eliminate
> would be appreciated:
>
I agree entirely. I have been caught on numerous issue. If you
want an effective debugger use NOICE12. John Harman has added
functionality to support the ELF format. There are a couple of
format bugs that he is working out but I find it much better then
the HI wave system. You would have to ask him for the conversion
utility off line. You also need to reduce the optimization or you
can't track the variable in either debugger (they get stuck on
the stack more often then not). But NOICE12 works reliably with
the PE multilink.
> i) As I have posted before, the system goes off in its
> head for periods of about 20s. No amount of jiggling/reinstalling the
> drivers has made any difference to this. This only clue to the cause may
> be that I am simultaneously using an SILABS USB interface. When I was
> using an FTDI one, the system seemed much worse.
> ii) The memory window in HIWAVE tells lies. It does not
> refresh appropriately and can be very misleading. The only way I can see
> the true contents of the memory is to try and edit the location and then
> cancel the operation. This seems to cause the system to read the actual
> value. This is one byte at a time and is more than a bit tedious. This
> problem seems to reflect in the data windows that also fail to show the
> correct contents of memory. There doesn't seem to be any way of telling
> HIWAVE to refresh the windows manually.
I found the same thing. This can really mislead you if you are
working with the module routing register and memory mapping. If
the code isn't working as expected and the window is open on the
register base, it can look like the wrong addressing is selected.
> iii) HIWAVE looses track of breakpoints. If I
> "run-to-cursor" and the program never gets to where I expect, sometimes
> the temporary breakpoint created by this process won't go away. The
> debugger shows no knowledge of this temporary breakpoint in the
> "controlpoints configuration" window. Resetting the system makes no
> difference. The only way around the problem is to restart the debugger
> which for me is a problem because memory is erased and I have to reload
> the data files that are loaded into eeprom separate from the
> application.

This is also due to the optimization. You need to turn off as
much optimization as possible and debug with static variables a
lot of times.... or you can't trace anything.
>
> Plenty has been said about BDM vs emulators, please don't let this post
> turn into another excuse for bagging BDM. My experience of BDM debugging
> has been good (in fact I wouldn't ever have become an HC12 user without
> it). Plenty of criticism has also been leveled at P&E. While I have been
> the victim of one or two of P&E's problems, there cables are cheap and
> work well enough. My feelings here are leveled at the HIWAVE debugger
> which I have always felt to be somewhat below par as part of the
> CodeWarrior package.

Agreed this is a lame system. The variable windows shift and
change focus going from one function to the next, one module to
the next. You can't display a tree structure for the source
files. If there is an error 3 separate windows pop up telling you
about it. NOICE doesn't have any of these problems. NOICE doesn't
have the conditional watch points and enable /disable of
breakpoints. But then I never got the conditional stuff to work
anyway because the rest of the system was so restrictive. The
exotic bits and pieces never got used.
>
> Jonathan Masters




Tim,

I appreciate to give it a try.

Thanks,

Jonathan Masters

-----Original Message-----
From: 68HC12@68HC... [mailto:68HC12@68HC...] On Behalf
Of timjenison
Sent: Saturday, 10 December 2005 10:55 AM
To: 68HC12@68HC...
Subject: [68HC12] Re: HIWAVE/P&E Debugger

I could send you the patched dll.
> Tim
>
> I'd say for certain this is the issue. I'll see what P&E say. I've
> neither the skills or inclination to start digging into driver
code.
>
> Jonathan.
>
> -----Original Message-----
> From: 68HC12@68HC... [mailto:68HC12@68HC...] On
Behalf
> Of timjenison
> Sent: Saturday, 10 December 2005 10:02 AM
> To: 68HC12@68HC...
> Subject: [68HC12] Re: HIWAVE/P&E Debugger
>
> I had an issue with the P&E USB multilink that was in a message a
> few months ago. It boiled down to a bug in the driver where it
> attempted to open a com port. My pc has no com ports, and it took
> right about 20 seconds for it to realize that and attempt to open
a
> usb port. This 20 second delay happened every time I made the
> project. The computer just sat there. Almost unusable.
>
> I dug into the driver code on the PC and patched over the call to
> open the com port. I also told P&E and Freescale about it but I
> don't think it was ever fixed.
>
> At the time I was using the freescale s12x demo board with built
in
> USB BDM, which uses the same driver as the P&E USB multilink.
>
> As far as I can tell, this would happen to everyone who tried that
> board without a (totally unused in this case) hardware com port on
> their machine.
>
> Not a good experience for someone evaluating the CW tool suite. > >
> > >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> > >combination. I am having to work around a number of problems
and
> it is
> > >beginning to impede my progress. Any suggestions as to how to
> eliminate
> > >would be appreciated:
> > >
> > >i) As I have posted before, the system goes off
> in its
> > >head for periods of about 20s. No amount of
jiggling/reinstalling
> the
> > >drivers has made any difference to this. This only clue to the
> cause may
> > >be that I am simultaneously using an SILABS USB interface. When
I
> was
> > >using an FTDI one, the system seemed much worse.
> > >ii) The memory window in HIWAVE tells lies. It
> does not
> > >refresh appropriately and can be very misleading. The only way
I
> can see
> > >the true contents of the memory is to try and edit the location
> and then
> > >cancel the operation. This seems to cause the system to read
the
> actual
> > >value. This is one byte at a time and is more than a bit
tedious.
> This
> > >problem seems to reflect in the data windows that also fail to
> show the
> > >correct contents of memory. There doesn't seem to be any way of
> telling
> > >HIWAVE to refresh the windows manually.
> > >iii) HIWAVE looses track of breakpoints. If I
> > >"run-to-cursor" and the program never gets to where I expect,
> sometimes
> > >the temporary breakpoint created by this process won't go away.
> The
> > >debugger shows no knowledge of this temporary breakpoint in the
> > >"controlpoints configuration" window. Resetting the system
makes
> no
> > >difference. The only way around the problem is to restart the
> debugger
> > >which for me is a problem because memory is erased and I have
to
> reload
> > >the data files that are loaded into eeprom separate from the
> > >application.
> > >
> > >Plenty has been said about BDM vs emulators, please don't let
> this post
> > >turn into another excuse for bagging BDM. My experience of BDM
> debugging
> > >has been good (in fact I wouldn't ever have become an HC12 user
> without
> > >it). Plenty of criticism has also been leveled at P&E. While I
> have been
> > >the victim of one or two of P&E's problems, there cables are
> cheap and
> > >work well enough. My feelings here are leveled at the HIWAVE
> debugger
> > >which I have always felt to be somewhat below par as part of the
> > >CodeWarrior package.
> > >
> > >Jonathan Masters
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> Terms of Service.
>
> _____
SPONSORED LINKS

Freescale
<http://groups.yahoo.com/gads?t=ms&k=Freescale+semiconductor+inc&w1=Free
scale+semiconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8
051+microprocessor&c=4&s6&.sig=K2HGv-zFlv5OYUv_QxIq_Q> semiconductor
inc
Microcontrollers
<http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Freescale+semic
onductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+micropr
ocessor&c=4&s6&.sig=SYHwNJjjGQXRvtt_GybT4g>
Pic
<http://groups.yahoo.com/gads?t=ms&k=Pic+microcontrollers&w1=Freescale+s
emiconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+mic
roprocessor&c=4&s6&.sig=umVbbnUwsPzEzKKD_pQfUw> microcontrollers

8051
<http://groups.yahoo.com/gads?t=ms&k51+microprocessor&w1=Freescale+se
miconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+micr
oprocessor&c=4&s6&.sig=NO-nSKjHoAlh9XtZ8LB1_A> microprocessor
_____

> Terms of Service.

_____


I just emailed it to you. It is the unit_12z.dll. It goes in the
prog directory of CodeWarrior. --- In 68HC12@68HC..., "Jonathan Masters" <jon@j...> wrote:
>
> Tim,
>
> I appreciate to give it a try.
>
> Thanks,
>
> Jonathan Masters
>
> -----Original Message-----
> From: 68HC12@68HC... [mailto:68HC12@68HC...] On
Behalf
> Of timjenison
> Sent: Saturday, 10 December 2005 10:55 AM
> To: 68HC12@68HC...
> Subject: [68HC12] Re: HIWAVE/P&E Debugger
>
> I could send you the patched dll. >
> > Tim
> >
> > I'd say for certain this is the issue. I'll see what P&E say.
I've
> > neither the skills or inclination to start digging into driver
> code.
> >
> > Jonathan.
> >
> > -----Original Message-----
> > From: 68HC12@68HC... [mailto:68HC12@68HC...] On
> Behalf
> > Of timjenison
> > Sent: Saturday, 10 December 2005 10:02 AM
> > To: 68HC12@68HC...
> > Subject: [68HC12] Re: HIWAVE/P&E Debugger
> >
> > I had an issue with the P&E USB multilink that was in a message
a
> > few months ago. It boiled down to a bug in the driver where it
> > attempted to open a com port. My pc has no com ports, and it
took
> > right about 20 seconds for it to realize that and attempt to
open
> a
> > usb port. This 20 second delay happened every time I made the
> > project. The computer just sat there. Almost unusable.
> >
> > I dug into the driver code on the PC and patched over the call
to
> > open the com port. I also told P&E and Freescale about it but I
> > don't think it was ever fixed.
> >
> > At the time I was using the freescale s12x demo board with built
> in
> > USB BDM, which uses the same driver as the P&E USB multilink.
> >
> > As far as I can tell, this would happen to everyone who tried
that
> > board without a (totally unused in this case) hardware com port
on
> > their machine.
> >
> > Not a good experience for someone evaluating the CW tool suite.
> >
> >
> >
> >
> >
> > >
> > > >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> > > >combination. I am having to work around a number of problems
> and
> > it is
> > > >beginning to impede my progress. Any suggestions as to how to
> > eliminate
> > > >would be appreciated:
> > > >
> > > >i) As I have posted before, the system goes
off
> > in its
> > > >head for periods of about 20s. No amount of
> jiggling/reinstalling
> > the
> > > >drivers has made any difference to this. This only clue to
the
> > cause may
> > > >be that I am simultaneously using an SILABS USB interface.
When
> I
> > was
> > > >using an FTDI one, the system seemed much worse.
> > > >ii) The memory window in HIWAVE tells lies. It
> > does not
> > > >refresh appropriately and can be very misleading. The only
way
> I
> > can see
> > > >the true contents of the memory is to try and edit the
location
> > and then
> > > >cancel the operation. This seems to cause the system to read
> the
> > actual
> > > >value. This is one byte at a time and is more than a bit
> tedious.
> > This
> > > >problem seems to reflect in the data windows that also fail
to
> > show the
> > > >correct contents of memory. There doesn't seem to be any way
of
> > telling
> > > >HIWAVE to refresh the windows manually.
> > > >iii) HIWAVE looses track of breakpoints. If I
> > > >"run-to-cursor" and the program never gets to where I
expect,
> > sometimes
> > > >the temporary breakpoint created by this process won't go
away.
> > The
> > > >debugger shows no knowledge of this temporary breakpoint in
the
> > > >"controlpoints configuration" window. Resetting the system
> makes
> > no
> > > >difference. The only way around the problem is to restart the
> > debugger
> > > >which for me is a problem because memory is erased and I have
> to
> > reload
> > > >the data files that are loaded into eeprom separate from the
> > > >application.
> > > >
> > > >Plenty has been said about BDM vs emulators, please don't let
> > this post
> > > >turn into another excuse for bagging BDM. My experience of
BDM
> > debugging
> > > >has been good (in fact I wouldn't ever have become an HC12
user
> > without
> > > >it). Plenty of criticism has also been leveled at P&E. While
I
> > have been
> > > >the victim of one or two of P&E's problems, there cables are
> > cheap and
> > > >work well enough. My feelings here are leveled at the HIWAVE
> > debugger
> > > >which I have always felt to be somewhat below par as part of
the
> > > >CodeWarrior package.
> > > >
> > > >Jonathan Masters
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >> Terms of Service.
> >
> > _____
> >
> >
> >
> >
> >
> SPONSORED LINKS
>
> Freescale
> <http://groups.yahoo.com/gads?
t=ms&k=Freescale+semiconductor+inc&w1=Free
>
scale+semiconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w
4=8
> 051+microprocessor&c=4&s6&.sig=K2HGv-zFlv5OYUv_QxIq_Q>
semiconductor
> inc
> Microcontrollers
> <http://groups.yahoo.com/gads?
t=ms&k=Microcontrollers&w1=Freescale+semic
>
onductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+micr
opr
> ocessor&c=4&s6&.sig=SYHwNJjjGQXRvtt_GybT4g>
> Pic
> <http://groups.yahoo.com/gads?
t=ms&k=Pic+microcontrollers&w1=Freescale+s
>
emiconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+
mic
> roprocessor&c=4&s6&.sig=umVbbnUwsPzEzKKD_pQfUw>
microcontrollers
>
> 8051
> <http://groups.yahoo.com/gads?
t=ms&k51+microprocessor&w1=Freescale+se
>
miconductor+inc&w2=Microcontrollers&w3=Pic+microcontrollers&w451+m
icr
> oprocessor&c=4&s6&.sig=NO-nSKjHoAlh9XtZ8LB1_A> microprocessor >
> _____
>
> > Terms of Service.
>
> _____




Hi Tim.

The debugger actually tries to open a connection with a Cyclone Pro which
can be connected via RS232.
I will make sure to avoid this if no serial port is available, or if
disabled by an option.

Regards,
Gilles At 12:01 AM 12/10/2005, you wrote:
>I had an issue with the P&E USB multilink that was in a message a
>few months ago. It boiled down to a bug in the driver where it
>attempted to open a com port. My pc has no com ports, and it took
>right about 20 seconds for it to realize that and attempt to open a
>usb port. This 20 second delay happened every time I made the
>project. The computer just sat there. Almost unusable.
>
>I dug into the driver code on the PC and patched over the call to
>open the com port. I also told P&E and Freescale about it but I
>don't think it was ever fixed.
>
>At the time I was using the freescale s12x demo board with built in
>USB BDM, which uses the same driver as the P&E USB multilink.
>
>As far as I can tell, this would happen to everyone who tried that
>board without a (totally unused in this case) hardware com port on
>their machine.
>
>Not a good experience for someone evaluating the CW tool suite. > >
> > >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> > >combination. I am having to work around a number of problems and
>it is
> > >beginning to impede my progress. Any suggestions as to how to
>eliminate
> > >would be appreciated:
> > >
> > >i) As I have posted before, the system goes off
>in its
> > >head for periods of about 20s. No amount of jiggling/reinstalling
>the
> > >drivers has made any difference to this. This only clue to the
>cause may
> > >be that I am simultaneously using an SILABS USB interface. When I
>was
> > >using an FTDI one, the system seemed much worse.
> > >ii) The memory window in HIWAVE tells lies. It
>does not
> > >refresh appropriately and can be very misleading. The only way I
>can see
> > >the true contents of the memory is to try and edit the location
>and then
> > >cancel the operation. This seems to cause the system to read the
>actual
> > >value. This is one byte at a time and is more than a bit tedious.
>This
> > >problem seems to reflect in the data windows that also fail to
>show the
> > >correct contents of memory. There doesn't seem to be any way of
>telling
> > >HIWAVE to refresh the windows manually.
> > >iii) HIWAVE looses track of breakpoints. If I
> > >"run-to-cursor" and the program never gets to where I expect,
>sometimes
> > >the temporary breakpoint created by this process won't go away.
>The
> > >debugger shows no knowledge of this temporary breakpoint in the
> > >"controlpoints configuration" window. Resetting the system makes
>no
> > >difference. The only way around the problem is to restart the
>debugger
> > >which for me is a problem because memory is erased and I have to
>reload
> > >the data files that are loaded into eeprom separate from the
> > >application.
> > >
> > >Plenty has been said about BDM vs emulators, please don't let
>this post
> > >turn into another excuse for bagging BDM. My experience of BDM
>debugging
> > >has been good (in fact I wouldn't ever have become an HC12 user
>without
> > >it). Plenty of criticism has also been leveled at P&E. While I
>have been
> > >the victim of one or two of P&E's problems, there cables are
>cheap and
> > >work well enough. My feelings here are leveled at the HIWAVE
>debugger
> > >which I have always felt to be somewhat below par as part of the
> > >CodeWarrior package.
> > >
> > >Jonathan Masters
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> >
> > --
> >
> > ____________________________
> > *Mark L. Cukier*, /Design Engineer/
> > P&E Microcomputer Systems
> > 656 Beacon Street, Floor 2
> > Boston, MA 02215
> > _________________________________
> > e-mail: mark@p... <mailto:mark@p...>
> > phone : (617) 353-9206 x19
> > fax : (617) 353-9205
> > _________________________________
> >
> > visit us on the web at: http: //www.pemicro.com
> >Yahoo! Groups Links >
>




Gilles,

This would be very good. Cheers to Tim for modifying the DLL and helping
me out.

Jonathan Masters

-----Original Message-----
From: 68HC12@68HC... [mailto:68HC12@68HC...] On Behalf
Of Gilles Blanquin
Sent: Monday, 12 December 2005 7:48 PM
To: 68HC12@68HC...
Subject: Re: [68HC12] Re: HIWAVE/P&E Debugger

Hi Tim.

The debugger actually tries to open a connection with a Cyclone Pro
which
can be connected via RS232.
I will make sure to avoid this if no serial port is available, or if
disabled by an option.

Regards,
Gilles At 12:01 AM 12/10/2005, you wrote:
>I had an issue with the P&E USB multilink that was in a message a
>few months ago. It boiled down to a bug in the driver where it
>attempted to open a com port. My pc has no com ports, and it took
>right about 20 seconds for it to realize that and attempt to open a
>usb port. This 20 second delay happened every time I made the
>project. The computer just sat there. Almost unusable.
>
>I dug into the driver code on the PC and patched over the call to
>open the com port. I also told P&E and Freescale about it but I
>don't think it was ever fixed.
>
>At the time I was using the freescale s12x demo board with built in
>USB BDM, which uses the same driver as the P&E USB multilink.
>
>As far as I can tell, this would happen to everyone who tried that
>board without a (totally unused in this case) hardware com port on
>their machine.
>
>Not a good experience for someone evaluating the CW tool suite. > >
> > >Does anyone else have a poor opinion of the HIWAVE/P& Debugger
> > >combination. I am having to work around a number of problems and
>it is
> > >beginning to impede my progress. Any suggestions as to how to
>eliminate
> > >would be appreciated:
> > >
> > >i) As I have posted before, the system goes off
>in its
> > >head for periods of about 20s. No amount of jiggling/reinstalling
>the
> > >drivers has made any difference to this. This only clue to the
>cause may
> > >be that I am simultaneously using an SILABS USB interface. When I
>was
> > >using an FTDI one, the system seemed much worse.
> > >ii) The memory window in HIWAVE tells lies. It
>does not
> > >refresh appropriately and can be very misleading. The only way I
>can see
> > >the true contents of the memory is to try and edit the location
>and then
> > >cancel the operation. This seems to cause the system to read the
>actual
> > >value. This is one byte at a time and is more than a bit tedious.
>This
> > >problem seems to reflect in the data windows that also fail to
>show the
> > >correct contents of memory. There doesn't seem to be any way of
>telling
> > >HIWAVE to refresh the windows manually.
> > >iii) HIWAVE looses track of breakpoints. If I
> > >"run-to-cursor" and the program never gets to where I expect,
>sometimes
> > >the temporary breakpoint created by this process won't go away.
>The
> > >debugger shows no knowledge of this temporary breakpoint in the
> > >"controlpoints configuration" window. Resetting the system makes
>no
> > >difference. The only way around the problem is to restart the
>debugger
> > >which for me is a problem because memory is erased and I have to
>reload
> > >the data files that are loaded into eeprom separate from the
> > >application.
> > >
> > >Plenty has been said about BDM vs emulators, please don't let
>this post
> > >turn into another excuse for bagging BDM. My experience of BDM
>debugging
> > >has been good (in fact I wouldn't ever have become an HC12 user
>without
> > >it). Plenty of criticism has also been leveled at P&E. While I
>have been
> > >the victim of one or two of P&E's problems, there cables are
>cheap and
> > >work well enough. My feelings here are leveled at the HIWAVE
>debugger
> > >which I have always felt to be somewhat below par as part of the
> > >CodeWarrior package.
> > >
> > >Jonathan Masters
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> Terms of Service.

_____