68300

I am thinking about upgrading to a different compiler, but since I have
already spent a lot of time, I want the next change to be the right one.  I
am using XTools now with the Cygnus GNU C compiler/assembler.  I haven't
been able to get the source debugging working with P&E's ICD32Z.  So I have
a few questions:

Is anyone using this enviroment and using C source debugging?

What do you think of the Hi-Tech C development environment?

Is there another compiler that works well in the $1000 price range?

I have read that GNU C doesn't handle interrupts well on the 683xx.  Is this
still a problem, or is that an historical issue that is now changed?

Bruce Partridge
http://www.rebreather.ca
Vancouver, Canada
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.445 / Virus Database: 250 - Release Date: 1/21/2003

On Mon, Jan 27, 2003 at 10:06:49AM -0800, Bruce Partridge wrote:

> I have read that GNU C doesn't handle interrupts well on the 683xx.
> Is this still a problem, or is that an historical issue that is now
> changed?

it's not built into gcc.  there have been patches floating around to add
__attribute__ ((interrupt)) support for 68k, but as far as I know, they
haven't made their way back into the main code.

certainly not an insurmountable issue.  you can write ISR wedges in
assembly, insert inline assembly into the C source, or track down the
version of gcc which supports interrupt attributes for functions.

-- 
  Aaron J. Grier  |   Frye Electronics, Tigard, OR   |  aaron@...

Hello All
This posting reminded me of our attempts to get the GNU source level
debugger working under Windows NT with an ARM7 target a while ago. We, like
Bruce, did not suceed.

I, and I suspect others, may consider the GNU route in the future and would
be interested to find out how many of the group are now using "Gnu" source
level debugging and if so if it is running under: -
1) Linux/Unix.
2) Microsoft Windows - any variant.

And what BDM pod they are using.

It would be useful to know how long it took to get this working from
installation (and how many patches were required, and where obtained) and
how the final result  compares with commercial offerings such as SingleStep
and Diab for example.

I have no commercial axe to grind, just a genuine interest.
I am using the Microtec Compiler and the Noral Flex BDM debugger, which
considerably exceed the $1000 limit, but did work striaght out of the box on
a 68331 target.

Robert
----- Original Message -----
From: "Bruce Partridge" <bgpartri@...>
To: <68300@yahoogroups.com>
Sent: Monday, January 27, 2003 6:06 PM
Subject: [68300] 68331 Compiler


> I am thinking about upgrading to a different compiler, but since I have
> already spent a lot of time, I want the next change to be the right one.
I
> am using XTools now with the Cygnus GNU C compiler/assembler.  I haven't
> been able to get the source debugging working with P&E's ICD32Z.  So I
have
> a few questions:
>
> Is anyone using this enviroment and using C source debugging?
>
> What do you think of the Hi-Tech C development environment?
>
> Is there another compiler that works well in the $1000 price range?
>
> I have read that GNU C doesn't handle interrupts well on the 683xx.  Is
this

> still a problem, or is that an historical issue that is now changed?
>
> Bruce Partridge
> http://www.rebreather.ca
> Vancouver, Canada
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.445 / Virus Database: 250 - Release Date: 1/21/2003
>
>
> ---------------------------------------------------
> To unsubscribe from this group, send an email to:
> 68300-unsubscribe@yahoogroups.com
>
> To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

In my day job I use DIAB DCC and SDS with either a Macraigor wiggler or a 
P&E ICD. They work. We tried CodeWarrior but (2 years ago) it wouldn't do 
things like change the VBR, promising but a non-starter.

In my hobby life I tried to put together the pieces for a low low price. 
Cheap is good. Free is better.

I didn't have much luck porting GCC and GDB for 68k to Cygwin. The problem 
stemmed from the patches needed not matching the release available. Even if 
I went back to the release that (supposedly) matched the patches...it 
didn't. The various people that maintained the patches did not have the 
associated base releases as well.

If I remember correctly, the problem was especially bad with GDB for BDM. I 
managed to get a standalone program written with the BDM libraries to 
exercise my target board with my wiggler (and managed to find that my SRAM 
would go offline if the board was turned upside down) but I was not able to 
make gdb talk bdm.

BD32 under '95 with the EFI332 PD BDM works but there is no source level 
debugging. On the other hand it does do op-code disassembly, which is more 
helpful than Macraigors OCD (Macraigor said that they do not have a 
disassembly section for CPU32 and they would not release anything that 
would allow me to make one).

Eventually I downloaded Ashware GCC, which worked straight out of the box 
and am still looking for a debugger. Perhaps the BD32 for NT will pan out 
this time.

I sent a message to Metrowerks asking if they had educational prices on 
CodeWarrior for hobbiests and they flatly refused. DIAB wanted US$5K (erk) 
for a license. Jean Labrosse suggested that I call MicroCross. Perhaps when 
I get back to the project I shall.

Andrei

(Bruce Partridge, did you go to the U of A in the early '80s?)

At 09:23 AM 1/28/2003 +0000, you wrote:

>Hello All
>This posting reminded me of our attempts to get the GNU source level
>debugger working under Windows NT with an ARM7 target a while ago. We, like
>Bruce, did not suceed.
>
>I, and I suspect others, may consider the GNU route in the future and would
>be interested to find out how many of the group are now using "Gnu" source
>level debugging and if so if it is running under: -
>1) Linux/Unix.
>2) Microsoft Windows - any variant.
>
>And what BDM pod they are using.
>
>It would be useful to know how long it took to get this working from
>installation (and how many patches were required, and where obtained) and
>how the final result  compares with commercial offerings such as SingleStep
>and Diab for example.
>
>I have no commercial axe to grind, just a genuine interest.
>I am using the Microtec Compiler and the Noral Flex BDM debugger, which
>considerably exceed the $1000 limit, but did work striaght out of the box on
>a 68331 target.
>
>Robert
>----- Original Message -----
>From: "Bruce Partridge" <bgpartri@...>
>To: <68300@yahoogroups.com>
>Sent: Monday, January 27, 2003 6:06 PM
>Subject: [68300] 68331 Compiler
>
>
> > I am thinking about upgrading to a different compiler, but since I have
> > already spent a lot of time, I want the next change to be the right one.
>I
> > am using XTools now with the Cygnus GNU C compiler/assembler.  I haven't
> > been able to get the source debugging working with P&E's ICD32Z.  So I
>have
> > a few questions:
> >
> > Is anyone using this enviroment and using C source debugging?
> >
> > What do you think of the Hi-Tech C development environment?
> >
> > Is there another compiler that works well in the $1000 price range?
> >
> > I have read that GNU C doesn't handle interrupts well on the 683xx.  Is
>this
> > still a problem, or is that an historical issue that is now changed?
> >
> > Bruce Partridge
> > http://www.rebreather.ca
> > Vancouver, Canada
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.445 / Virus Database: 250 - Release Date: 1/21/2003
> >
> >
> > ---------------------------------------------------
> > To unsubscribe from this group, send an email to:
> > 68300-unsubscribe@yahoogroups.com
> >
> > To learn more about Motorola Microcontrollers, please visit
> > http://www.motorola.com/mcu
> >
> >
> >
> > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> >
> >
>
>
>---------------------------------------------------
>To unsubscribe from this group, send an email to:
>68300-unsubscribe@yahoogroups.com
>
>To learn more about Motorola Microcontrollers, please visit
>http://www.motorola.com/mcu
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/