gnupic: Re: [gnupic] Re: [Sdcc-user] USB compilation for PIC16 - strange errors
Subject:
Re: [gnupic] Re: [Sdcc-user] USB compilation for PIC16 - strange errors
From:
Vaclav ####@####.####
Date:
6 Dec 2007 07:26:11 +0000
Message-Id: <1352.1872-1488-958380354-1196925967@seznam.cz>
Hello David (and others as well),
> > ...
> > Strange is the EVELYN stuff - I can't find "SET_DESCRIPTOR" (line 704) in
> > the ASM ... Is it correct ?
>
> I'm pretty sure EVELYN is something in sdcc, not gputils. If that's the
> case, I can't tell you much about it, but I remember it was a strange
> undocumented warning.
>
Yes it is. Honestly I took GNUPIC list as a general list for PIC users focused on GPL tools. So I thought somebody met such messages.
> >
> >
> > Regarding mismatches - I don't know. Maybe libraries were generated for
> > different PIC processor - hopefully register addresses are OK. Should I
> > re-generate them ?
>
> The "maximum range" warnings use data compiled into gpasm, not from any
> libraries or linker scripts. It is only affected by what processor sdcc
> tells gpasm to use, which in turn comes from the sdcc -m and -p options.
>
> I hope that answers your question. I wasn't positive exactly what the
> question was.
>
Yes you helped me :-)
Vaclav
