From: SourceForge.net <no...@so...> - 2005-05-15 19:26:43
|
Bugs item #1202440, was opened at 2005-05-15 12:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 Category: pic16 target Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: missing pic16 includes Initial Comment: The PIC16 port claims to support the 18F2550, 18F4331, and 18F4455, but pic18fregs.h gives the error "Unsupported processor" because there are no corresponding header files for these chips. Also, can building and installing the pic16 libraries and includes be an option through the configure script? Having to build and install them manually in the source tree seems unnecessary when the autoconf facility already exists for this type of compile-time configuration. This is SDCC 2.5.0.... would love to see a 2.5.1 with cleaner pic16 support. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 |
From: SourceForge.net <no...@so...> - 2005-05-17 21:35:51
|
Bugs item #1202440, was opened at 2005-05-15 19:26 Message generated for change (Comment added) made by tecodev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 Category: pic16 target >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Raphael Neider (tecodev) Summary: missing pic16 includes Initial Comment: The PIC16 port claims to support the 18F2550, 18F4331, and 18F4455, but pic18fregs.h gives the error "Unsupported processor" because there are no corresponding header files for these chips. Also, can building and installing the pic16 libraries and includes be an option through the configure script? Having to build and install them manually in the source tree seems unnecessary when the autoconf facility already exists for this type of compile-time configuration. This is SDCC 2.5.0.... would love to see a 2.5.1 with cleaner pic16 support. ---------------------------------------------------------------------- >Comment By: Raphael Neider (tecodev) Date: 2005-05-17 21:35 Message: Logged In: YES user_id=1115835 I have added support for 18F{2550,4331,4455,4520}, they should be fully functional by now. As I needed to develop a new script for creating the header files I am sure there are still open issues (changes in names, missing names...) -- please report back! Building the pic16 library on the sourceforge compile farm is currently not possible due to lacking gputils (needed to assemble and link...). For home use it should suffice to un-comment l. 653 in configure.in and rerun make (the feature is there, but disabled)... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 |
From: SourceForge.net <no...@so...> - 2005-05-17 21:58:04
|
Bugs item #1202440, was opened at 2005-05-15 15:26 Message generated for change (Comment added) made by jimatjtan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 Category: pic16 target Group: fixed Status: Closed Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Raphael Neider (tecodev) Summary: missing pic16 includes Initial Comment: The PIC16 port claims to support the 18F2550, 18F4331, and 18F4455, but pic18fregs.h gives the error "Unsupported processor" because there are no corresponding header files for these chips. Also, can building and installing the pic16 libraries and includes be an option through the configure script? Having to build and install them manually in the source tree seems unnecessary when the autoconf facility already exists for this type of compile-time configuration. This is SDCC 2.5.0.... would love to see a 2.5.1 with cleaner pic16 support. ---------------------------------------------------------------------- Comment By: Jim Paris (jimatjtan) Date: 2005-05-17 17:58 Message: Logged In: YES user_id=175928 Thank you! Will try out the 2550 support later tonight. For the pic16 library, would you accept a patch to add a configure option to enable the build, or perhaps detect gputils and build the library automatically if it's present? ---------------------------------------------------------------------- Comment By: Raphael Neider (tecodev) Date: 2005-05-17 17:35 Message: Logged In: YES user_id=1115835 I have added support for 18F{2550,4331,4455,4520}, they should be fully functional by now. As I needed to develop a new script for creating the header files I am sure there are still open issues (changes in names, missing names...) -- please report back! Building the pic16 library on the sourceforge compile farm is currently not possible due to lacking gputils (needed to assemble and link...). For home use it should suffice to un-comment l. 653 in configure.in and rerun make (the feature is there, but disabled)... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1202440&group_id=599 |