Arthur Skowronek wrote:
> I tried to write a Makefile for use with sdcc 2.9.0 to
> compile multifile z80 projects.
I tried out your makefile, and it seems the problem is
your options to link-z80. I was not able to figure out what
it did not like, so I changed it to use sdcc to link, and it
w
- prateeksikka wrote:
> On Linux I do,
> sddc test.c(compiling the code , this gives me .ihx file)
> and then
> packihx test.ihx > test.hex (This gives me a hex file).
Instead of packihx, try:
makebin -p test.bin
I don't believe it is necessary to use packihx before makebin (I could b
- Alistair Buxton wrote:
> When I use my custom crt0, in the final binary, gsinit: is pointing to
> GSFINAL instead of GSINIT.
crt0 needs to be the first module in the list of modules you link.
If it is not first, then the gsinit label will not be ahead of the stuff
the compiler puts in th
- bob...@comcast.net wrote:
> Now if you really want to know what the SP was when it
> hit a breakpoint (IOW, which breakpoint did you hit?), then
> the standard way to do that on z80 is to use restart inst.,
> and then look on top of stack.
Make that:
Now if you really want to know what the
- Richard Gray wrote:
> I think this example puts the stack-pointer into HL, doesn't it?
> Sorry! (I just woke up, and there is no pepsi in the house...)
But isn't this sort of a trick question??? You usually know
exactly what the PC is at every point in your program!
The stack pointer is
- candida lopez rodriguez wrote:
>
> I need to obtain the PC address (one of the commands that I want to have is
> dump the registers). My problem is that I can not see a way to obtain the PC,
>
> I can set it using HL but I do not have a way to obtain its value. There is a
> way to do s
- Kustaa Nyholm wrote:
> Hi,
>
> according to SDCC manual .mem and .map are automatically genereated,
> and indeed I recall them being generated when I was working with HC08.
>
> But now I have a multifile PIC project and I cannot see the.map nor
> .mem
> files anywhere. And I can't find a
> $TOOL_BASE/sdcc --xram-loc 0x1F40 --code-loc 0 --stack-loc
> 0x3e80 /home/crodrigu/projects/debugger/debugger.rel
> /home/crodrigu/projects/debugger/uart.rel
> /home/crodrigu/projects/debugger/CTC.rel
You need -mz80 in your link command line. I think SDCC might
default to using the 8051 lin
> > Did you try to compile anything yet
>
> Certainly not! One has to know what the outcome will be before one runs a
> program.
Why? Whatcha afraid of?
> > What happened?
>
> I got a virus warning when I downloaded the v2.8.2 files.
>
> I didn't get that warning after a second
> >> It is true that nobody force me to use SDCC, but the deficiency in the
> >> documentation actually prevents me from using it.
> >
> > Have you even installed it yet?
>
> Yes, reluctantly, since I don't like to install things when the resulting
> conditions are not well defined.
OK.
Have yo
> It is true that nobody force me to use SDCC, but the deficiency in the
> documentation actually prevents me from using it.
Have you even installed it yet?
Randy
-
This SF.Net email is sponsored by the Moblin Your Move De
I'm gonna pretend I did not read most of the crap posted
in last couple days, and instead that someone asked
"Hey, what IDE are people using with SDCC",
and I'll tell what works for me.
If you are using windows, and happen to have winavr
installed, then you already have an IDE that works with S
[EMAIL PROTECTED] wrote:
>I use "$< -o $@"
>where you have "$+ -o $(@)".
>
oops, I have confused my compile and link commands.
My link command uses "$^ -o $@"
$^ is like $+, but with no duplicates.
Randy
-
This SF.net em
Stanley Lee wrote:
> #for the .c.o directive below, do I need to replace it with the
> .c .o instead of .c.o? i.e. how would I know which
> source code to compile and build?
>
> .c.o:
>$(CC) $(CFLAGS) $(INC) -c $<
I'm no expert on makefiles, but perhaps you want to use
%.o : %.c
I thi
I figured out what I was doing wrong! I was putting my example.o file
(with main() in it)
first in my link command. When I put crt0.o first, and example.o
second, _GSINIT
landed in the code section!!! :-)
The sdcc manual, in section 3.1.3 says:
"The file containing the main() function
Philipp Klaus Krause wrote:
>Place another .area _CODE before the .area _GSINIT?
>
OK, I tried that, but it didn't make any difference, _GSINIT is still
in RAM.
But thanks for trying!
Randy
-
This SF.net email is sp
Hi,
I am probably doing something wrong, but I can't figure out how
to get _GSINIT into the code section. I'm compiling for z80, and
using link options:
-mz80 --no-std-crt0 --code-loc 0x4100 --data-loc 0x8000
The target z80 based system has existing firmware at 0x-3fff.
That firmware has
17 matches
Mail list logo
