Hello SDCC users,
I'm doing a project with the famous Z80 just for fun, and decided to use
the sdasz80 assembler. My project consists of multiple source files to
keep everything modular. I'm having a problem with the linking step.
I've 2 source files: boot.asm and numconv.asm:
; boot.asm:
.g
I've tried what you suggested, linking the boot.rel first results in the
opposite effect, the _START area gets overwritten by the _CODE area.
Here a small showcase for the problem I'm having:
; boot.asm:
.globl HexToU8
.area _START (ABS,OVR)
.org 0
ldSP, #0x
call
linker
> manual or just try removing it and see if your problem goes away.
>
> Peter Van Epp
>
> On Wed, Aug 17, 2016 at 11:01:05PM -0300, Augusto Fraga Giachero wrote:
>> I've tried what you suggested, linking the boot.rel first results in the
>> opposite effec
Well done!
Do you have any hint on how to debug STM8 targets with free tools?
On 01-01-2017 07:54, Philipp Klaus Krause wrote:
> Based on my experience in getting started with various STM8 and MCS-51
> boards, I wrote a few simple tutorials to help others. They use free
> tools only. For various
> SDCC can generate ELF with DWARF. AFAIK, ST has a gdb fork that could be
> used for debugging (I've read they ship it with ST Visual develop).
> AFAIK some people got that combination to work. But I haven't read about
> any successes in getting the gdb source code from ST (there are posts
> abou
Nice!
On 14-02-2017 16:26, Miklos Marton wrote:
>> I've found an recent post on ST forums that has a link to an old version
>> of the GDB source code modified by ST to support STM8 targets. I've
>> uploaded to GitLab for convenience. Maybe one day I'll try to compile it.
>>
>> Here is the link fo
k that! Thanks!
>
> Best regards,
> Miklos Marton
>
> 2017-02-21 19:56 keltezéssel, Augusto Fraga Giachero írta:
>> Nice!
>>
>>
>> On 14-02-2017 16:26, Miklos Marton wrote:
>>>> I've found an recent post on ST forums that has a link to
PIC microcontrollers (PIC12/PIC14/PIC16) doesn't have a general purpose
stack (it has a hardware stack used only to sub-routines and interrupts
return). I don't known how the sdcc implements local variables for these
targets (may be a software stack or fixed allocation).
Augusto
On 08/06/2017
