From: Itay D. <baz...@gm...> - 2006-04-11 14:24:24
|
Hi, sorry for storming into this converstaion, but as I understand from sdcc.sourceforge.net, the pic ports are far from stable. Is it still the case nowadays? thanks Itay On 4/11/06, Ernst Bachmann <e.b...@xe...> wrote: > On Tuesday 11 April 2006 15:44, Philipp Klaus Krause wrote: > > Philipp Klaus Krause wrote: > > > I've read that support for lots of PIC14 devices has been added recen= tly. > > > device/include/pic looks as empty as ever though. > > > If I install the version from current CVS > > > /usr/local/share/sdcc/include/pic doesn't exist. > > > > > > Philipp > > > > And sdcc -mpic14 says that only > > p16f627 p16f628 p16f84 p16f873 p16f877 p16f819 > > are supported. > > I recently tried the pic14 port (Source snapshot from 6th April), the dev= ice I > was testing (pic12f683 *) wasn't supported. > > I tried patching it in by adding a entry for it to device.c/h, and creati= ng a > device header with the supplied perl script, but that didn't work as > intended: > > Lots of: > WARNING: Ignoring Out of Range register assignment at fixed address 127, = STK00 > or SDCC segfaults, depending on what registers I tried to access. > > When it did compile, the generated ASM code did look usable, however. > > /Ernst > > *) yep, it's named 12F..., but that chip actually has an pic14 core. > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |