Hi Raphael,
Thanks for the answer.
I just apply the patch for my gpasm, so now it supports 16f88x as I can see
in the "gpasm -l" list.
Then I renamed the device/lib/pic/libdev/disabled_pic16f88[67].c, removing
the "disabled_".
When trying to compile
$ cd /path/to/sdcc/device/lib
$ make model-pic14
$ make install
I got following error message when it compile pic16f886.c and 16f887c.
blabla
...
[ CC ] ==> pic16f886.o
'16f886' was not found.
PIC14 processors and their characteristics:
processor program RAM EEPROM I/O
-----------------------------------------------------
16f72 2K 128 0 22
16f73 4K 192 0 22
16f74 4K 192 0 33
...
blabla
----
16c774 16c781 16c782 16c925 16c926 12f629 12f675
12f635 12f683
make[3]: [pic16f886.o] Error 1 (ignored)
error: "pic16f886.o" is not a valid object file
make[3]: [../bin/pic16f886.lib] Error 1 (ignored)
[ CC ] ==> pic16f887.o
'16f887' was not found.
PIC14 processors and their characteristics:
processor program RAM EEPROM I/O
-----------------------------------------------------
16f72 2K 128 0 22
...
blabla
Is it sdcc which could not found '16f886' and '16f887' or the problem lies
on gpasm. But gpasm -l already show the 16f886 and 16f887.
By the way, other device's lib compiled well without any problem. Do I need
to edit certain list so that my sdcc will found '16f886' and '16f887' when I
supply -p16f886 or -p16f887 in its option?
TIA.
--
soliton
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
