Dear Tim,
I got the same problem with 14bit enhanced core (PIC16F1XXX) devices.
I tried to define config values and received the similar error message.
I think it is not a proper way to define config in c source. I also do not know
how to do it correctly in sdcc.
However, it works when you specif
Thanks a lot
On Oct 20, 2011 11:54 PM, "Raphael Neider" wrote:
> > Then it's not related to Tim's code at all, is it? I thought it was and I
> > didn't see the reason why.
>
> Yes, the deprecation warning on the use of __CONFIG is completely
> unrelated.
>
>
>
> Then it's not related to Tim's code at all, is it? I thought it was and I
> didn't see the reason why.
Yes, the deprecation warning on the use of __CONFIG is completely unrelated.
--
The demand for IT networking profess
Thanks for your answer.
Then it's not related to Tim's code at all, is it? I thought it was and I
didn't see the reason why.
Thanks
On Thu, Oct 20, 2011 at 10:22 PM, Raphael Neider wrote:
> asm bails out with an error ("__CONFIG directive is not
> supported/rec
>
---
> Why is there a warning on the __CONFIG directive?
Well, Microchip (and thus gputils) probably decided to change syntax
and semantics of the __CONFIG directive from a simple
__CONFIG
to a more flexible
CONFIG =
style. To give compiler vendors and assembly-by-hand writers time to
adjust, they d
Why is there a warning on the __CONFIG directive?
Thanks
On Wed, Oct 19, 2011 at 8:58 PM, Raphael Neider wrote:
> and you should be fine, although the deprecation warning on the
> __CONFIG directive remains :-( Seems to work, though.
>
---
Hi,
> sudo sdcc -mpic16 -I /usr/local/share/sdcc/non-free/include/ -L
> /usr/local/share/sdcc/non-free/lib/pic16 --use-non-free test1.c
Using "sudo" here is not necessary and even dangerous: sdcc could
decide to overwrite important files ...
Additionally (and more towards your problem), you are
