EmbeddedRelated.com
Forums

PCBug11 on fast PC

Started by Velja March 7, 2003
Does anybody use PCBUG11b on Duron 1.3GHz? I always get message that can't
change regs and then lost communication.

Thanks

Velja




Hi,

Put now PCBug11 to trash and use JBug11.

JBug11 works on all Windows OS flavours (NT...) and with fast PCs...
JBug11 accepts almost PCBUG11 commands...

see here : http://freespace.virgin.net/john.beatty/index.html
thanks to John for his great tool;

Pat.

Velja wrote:

>Does anybody use PCBUG11b on Duron 1.3GHz? I always get message that can't
>change regs and then lost communication.
>
>Thanks
>
>Velja >To unsubscribe from this group, send an email to: >
>
>">http://docs.yahoo.com/info/terms/ >


--
Patrice Kadionik. F6KQH / F4CUQ
-----------

+---------------------------------+
+"Tout doit etre aussi simple que possible, pas seulement plus simple"+
+---------------------------------+
+ Patrice Kadionik http://www.enseirb.fr/~kadionik +
+ ENSEIRB fax : +33 5.56.37.20.23 +
+ PO BOX 99 voice : +33 5.56.84.23.47 +
+ 33402 TALENCE Cedex http://www.enseirb.fr +
+ FRANCE mailto: +
+---------------------------------+


On Friday 07 March 2003 09:36, Velja wrote:
> Does anybody use PCBUG11b on Duron 1.3GHz? I always get message that can't
> change regs and then lost communication.

PCBUG11 uses an old dos way of using the cpu clock speed for timing. It will
not work on computers above 200MHz (i believe)

follow the link to JBug11 given previously....works great,...

just wish there was a linux port ! (hint, hint) bd



Velja wrote:
> Does anybody use PCBUG11b on Duron 1.3GHz? I always get message that can't
> change regs and then lost communication.

Hi,

The original version of PCBUG11 was developped years ago and used CPU loops for timing purposes. With the continuous increase in CPU speeds over years, this leaded to overflows.

A workaround was found with PCBUG11a, which was a hack allowing to use the software on faster PCs (but not too much).

At the end of 2002, I encountered the same problem when I replaced my old Pentium 166 with a brand new Athlon XP 1600, and of course, PCBUG11b did not work.

Then, as PCBUG11 was written in Turbo Pascal, I took back my old programming tools and docs. I managed to patch it, so that it could run on faaaast CPUs (at least, it ran on my 1.6 GHz Athlon). I called this version 'PCBUG11b'.

Anyway, if you're using a 'modern' OS (Windows 2000 or XP), you'll get another problem : the way these system handle serial ports will definitely prevent PCBUG11 from running. This is because DOS software access directly the hardware components, which is forbidden under modern OS. I didn't find any workaround about that.

=> As said in previous answers, you should consider switching to JBUG11, which is a great piece of software and is continuously improved. Also, it's completely free !

=> If you still need some features which were in PCBUG11 but are not (yet) present in JBUG11 (such as macro and batch-loader capabilities), then I can send you my patched *PCBUG11b*, which *starts* at frequencies over 1 GHz, but which is completely *untested* and provided 'as is'. If you can install some DOS or Windows 9x on your machine, you should be able to use it, and, of course, I would be happy to know how it works...

Hope this helps...

Toussaint.

--
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Toussaint OTTAVI (TK1BI) WWW : http://kalliste.fr.fm
Phone : (+33) 6.10.28.41.72 (GSM) Email :
Mail : B.P. 223, F-20179 AJACCIO Packet:


OK! send it to me. I use win98.

Velja
http://solair.eunet.yu/~cveve/index.html

----- Original Message -----
From: "Toussaint OTTAVI (TK1BI)" <>
To: <>
Sent: Friday, March 07, 2003 7:52 PM
Subject: Re: [m68HC11] PCBug11 on fast PC > Velja wrote:
> > Does anybody use PCBUG11b on Duron 1.3GHz? I always get message that
can't
> > change regs and then lost communication.
>
> Hi,
>
> The original version of PCBUG11 was developped years ago and used CPU
loops for timing purposes. With the continuous increase in CPU speeds over
years, this leaded to overflows.
>
> A workaround was found with PCBUG11a, which was a hack allowing to use the
software on faster PCs (but not too much).
>
> At the end of 2002, I encountered the same problem when I replaced my old
Pentium 166 with a brand new Athlon XP 1600, and of course, PCBUG11b did not
work.
>
> Then, as PCBUG11 was written in Turbo Pascal, I took back my old
programming tools and docs. I managed to patch it, so that it could run on
faaaast CPUs (at least, it ran on my 1.6 GHz Athlon). I called this version
'PCBUG11b'.
>
> Anyway, if you're using a 'modern' OS (Windows 2000 or XP), you'll get
another problem : the way these system handle serial ports will definitely
prevent PCBUG11 from running. This is because DOS software access directly
the hardware components, which is forbidden under modern OS. I didn't find
any workaround about that.
>
> => As said in previous answers, you should consider switching to JBUG11,
which is a great piece of software and is continuously improved. Also, it's
completely free !
>
> => If you still need some features which were in PCBUG11 but are not (yet)
present in JBUG11 (such as macro and batch-loader capabilities), then I can
send you my patched *PCBUG11b*, which *starts* at frequencies over 1 GHz,
but which is completely *untested* and provided 'as is'. If you can install
some DOS or Windows 9x on your machine, you should be able to use it, and,
of course, I would be happy to know how it works...
>
> Hope this helps...
>
> Toussaint.
>
> --
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> Toussaint OTTAVI (TK1BI) WWW : http://kalliste.fr.fm
> Phone : (+33) 6.10.28.41.72 (GSM) Email :
> Mail : B.P. 223, F-20179 AJACCIO Packet: >
> To unsubscribe from this group, send an email to: >
>
> ">http://docs.yahoo.com/info/terms/ >
>



I install JBug11 but now I have now problem. I lost communication with
target board very often. Sometimes I can read some locations sometime not

Velja
http://solair.eunet.yu/~cveve/index.html