HIWAVE/P&E Debugger
Started by ●December 9, 2005
Reply by ●December 12, 20052005-12-12
I disabled the COM port in the BIOS and in my Win2000 PRO OS, but I could
not reproduce this issue so far.
I know that the driver checks also if a Cyclone Pro is on the LAN so I
wonder if that could not be the source of the problem.
I will check also with P&E
Regards,
Gilles At 10:57 AM 12/12/2005, you wrote:
>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.
>
> _____ >
>Yahoo! Groups Links >
>
