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
On Sunday 16 September 2007 19:33, Philipp Klaus Krause wrote:
I just want to say: guys you are wonderfull
> Place another .area _CODE before the .area _GSINIT?
>
> Philipp
>
> -
> This SF.net email is sponsored by: Microsoft
Place another .area _CODE before the .area _GSINIT?
Philipp
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
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
Hi Stanley,
> main.c:4: Undefined identifier '_OSC_INT_Port_on_RA6_Port_on_RA7_1H'
> main.c:5: Undefined identifier '_BODEN_OFF_2L'
> main.c:7: Undefined identifier '_MCLRE_MCLR_disabled_RA5_input_en_3H'
The values to be put into the configuration words are defined in the
device-specific header
