On 14.02.2013 23:12, Raphael Neider wrote:
>
> Can you verify that your sdcc build passed cleanly? I assume that
> gputils were not found when you built sdcc, so no libraries nor
> crt*.o files could be built. While this is strange, as the build
> system used to bail out with an error in that si
Hello all,
I try compile my printf_pokus.c :
#include
unsigned long a=14430;
void putchar(char c)
{
//LCD_putc(c);
}
void main(void)
{
printf("%ld",a);
}
after compile
sdcc -mpic16 -p18f2550 -c printf_pokus.c
I see this error:
printf_pokus.c:14: error 98: conflict with previous definit
Hello everybody
Is there a way to tell the compiler to place one or more variables in
the udata_shr segment? I am aware of linker option
--preplace-udata-with=[kword], but that will just put everything in one
place - or?
I could use absolute adressing, eg. uint8_t xx __at 0x70, but this
exact
Hello Erlo,
As I know that area is used by STKxx regs as a STACK and context
saving for interrupt routine. So I think, you cant put any variable on
that area.
Zsolt
2013/2/15 Erlo Haugen :
> Hello everybody
> Is there a way to tell the compiler to place one or more variables in
> the udata_shr s
On 02/15/2013 04:53 PM, Gál Zsolt wrote:
> Hello Erlo,
>
> As I know that area is used by STKxx regs as a STACK and context
> saving for interrupt routine. So I think, you cant put any variable on
> that area.
>
> Zsolt
>
That is correct, but the stack size can be adjusted, making room for
other
Thank you for your help.
I had not included -p18f47j53 because the code has a "#define
__18f47j53" statement, and sdcc complained about it being defined
twice (I guess now I should do it the other way around, remove the
#define and leave it on the command line to make the option available
to the l
