Thanks Robert
I've added the link to my book marks. :+)
When PK2 goes Beta I might try. I'm not brave enough to try Alpha code.
Matt
--
My opinions may have changed, but not the fact that I am right.
-- Ashleigh Brilliant
-
Quoting "Matt Baker" :
>
>
> Thanks all
> My target is a PIC 16F690 so I did get the right tar ball for my Ubuntu 8.10
> I now get it to compile and link :+)
690 is a pretty OK chip, I like it,
>
> Now to write real code and then find a way to get it onto the Pic with my
> PicKit2. (Without reso
2009/3/5 Frieder Ferlemann
> Hi Matt,
>
> Matt Baker schrieb:
> > With sdcc -mz80 test.c I get
> > at 1: error 131: cannot generate code for target 'z80'
>
> >>> *"sdcc --version *reports
> >>> SDCC : avr/pic16/pic14/xa51 2.8.0 #5117 (Jun 2 2008) (UNIX)
>
> The SDCC you are using had been compil
Hi Matt,
Matt Baker schrieb:
> With sdcc -mz80 test.c I get
> at 1: error 131: cannot generate code for target 'z80'
>>> *"sdcc --version *reports
>>> SDCC : avr/pic16/pic14/xa51 2.8.0 #5117 (Jun 2 2008) (UNIX)
The SDCC you are using had been compiled for a subset of SDCC's
target CPUs. And Z80
Hi Matt,
I only mention the (Zilog) Z80 option because that's what I've been using
myself lately. Obviously, you'll have to substitute the appropriate option
for the target CPU you're aiming to program. I haven't had any experience
with SDCC for other than the Z80, so I'm rather limited in what
Richard
Thanks for the reply.
Was from the documentation "sdcc -c test.c" section 2.7 sdccman.html
char test;
void main(void) {
test=0;
}
With sdcc -mz80 test.c I get
at 1: error 131: cannot generate code for target 'z80'
Sorry to be a pain but I am struggling with this.
Matt
2009/3/4
Hi
Matt: Assuming you are using Debian/Ubuntu, you can install sdcc-nf
http://packages.debian.org/sid/sdcc-nf
which contains the full sdcc compiler.
Sorry about the default target, I will change that in the next release.
Cheers
Gudjon
On Thursday 05 March 2009 01:23:42 Maarten Brock wrote:
> To
To install SDCC you probably used a linux package which contains the FREE
parts only. The NONFREE parts as they were labeled contain the mcs51
target. I guess they forgot to change the default target (mcs51) even
though they disabled it.
Maarten
> It would be useful to know the actual command tha
It would be useful to know the actual command that you entered...?
I used something like this when I started off...
sdcc -mz80 test.c
the -mz80 tells sdcc what the target machine CPU is and therefore fairly
essential ;-)
On Wednesday 04 March 2009 22:17:22 Matt Baker wrote:
> Hi
> I can't comp
Hi
I can't compile the test.c file following the instructions in the
documentations.
I am new to sdcc and Linux...
Report is
sdcc: SDCCglue.c:1855: glue: Assertion `mcs51_like' failed.
Caught signal 6: SIGABRT
I installed sdcc not built it from source. But I don't remember where I
downloaded it f
10 matches
Mail list logo
