Don't think SDCC has built in support for it. I built a utility to convert
ihx into Verilog memory dump format (TV80 project), but it looks like GNU
objcopy can convert from intel hex to raw output (objcopy -O binary).
Guy
On Mon, Dec 23, 2013 at 1:55 AM, Ben Shi wrote:
> Hello,
>
> The sdcc
Unless this increases the I/O address space beyond 8 bits I don't see a need
for it, upper 8 bits are ignored.
Guy
On Sep 3, 2011, at 2:55 AM, Philipp Klaus Krause wrote:
> And if yes, why?
>
> As far as I can see this just ensures that the upper 8 bits of the
> address bus are 0 whenever doi
Hi Philipp,
I use the TV80 implementation, and the test suites are written for the standard
instruction set. All bug reports have been from users using the standard
instruction set as well.
Guy
On Aug 31, 2011, at 2:21 AM, Philipp Klaus Krause wrote:
> Dear users of sdcc,
>
> there are many
Another long-overdue thanks from a Z80 user -- I have used SDCC as the
compiler/assembler for my open-source TV80 core. It has been used in 4-5
different chips so far and has saved us at least one chip spin. :)
--
Special
I have gotten the best results by writing the entire routine in assembly and
then linking it with C code. The calling convention isn't well documented,
but not hard to understand by looking at the list files.
Here is a sample routine that takes a single 16 bit argument and returns a
32 bit result
If you do a function call, the called routine can examine the stack and find
the PC of where it was called from. With a function entry like:
_copy_ident:
pushix
ldix,#0
addix,sp
ldc, 4(ix)
ldb, 5(ix)
...
0(ix) and 1(ix) should be the origina
Haven't used a library, I've only done explicit linking, and my target
applications have little need of standard I/O. I pretty much always run
with a custom crt0, although I used the one from the library as a starting
point. Typical command line:
CC=$(SDCC_ROOT)/bin/sdcc -mz80
bintr.ihx : bintr.
