From: David E <3d...@gm...> - 2006-05-18 10:31:08
|
Hi, I've been reading that there has been a great deal of progress with the PIC port, I went over the webpage but couldn't find any information regarding the status of the port. I just wanted to know if it's usable (I use the PIC18F452), and is there anything I can do to help. Thanks, Best Regards David Elentok 3d...@gm... http://www.ee.bgu.ac.il/~elentok |
From: Laurent <lol...@fr...> - 2006-05-19 15:29:44
|
David E a =E9crit : > Hi, > I've been reading that there has been a great deal of progress with > the PIC port, > I went over the webpage but couldn't find any information regarding > the status of the port. >=20 > I just wanted to know if it's usable (I use the PIC18F452), and is > there anything I can do to help. >=20 > Thanks, > Best Regards > David Elentok > 3d...@gm... > http://www.ee.bgu.ac.il/~elentok Hi ! I've been using the PIC16 port (you may notice that PIC16 is for 18F and=20 PIC14 is for 16F !) for a little time now. For what I do, I can say that this port is functionnal, but I still need=20 more and more tests, and you must make yours for determining if it can=20 be used in production ! Now, just I can say is that it's perfect for experimental purposes... Like you, I also want to know more about this port : who maintain it ?=20 what is fully functionnal, or what features are planned for the future ? I can provide some help, but I have to know how ? Best regards Laurent |
From: Raphael N. <rn...@we...> - 2006-05-19 17:26:29
|
> > I've been reading that there has been a great deal of progress with > > the PIC port, > > I went over the webpage but couldn't find any information regarding > > the status of the port. > > I just wanted to know if it's usable (I use the PIC18F452), and is > > there anything I can do to help. "Port status" is somewhat subjective: It is not quite stable or usable for mission-critical projects (see open bugs on the sourceforge tracker system), but pretty close to the spot. The port is somewhat feature complete, there are currently no plans to introduce major changes to the port besides bug fixes (plus support for more devices, see below). As stated below, the port *should* do fine for leisure projects. I would propose to just give it a try. Any feedback (errors, unpredictable behaviour, missing features, goodies ;-)) can/will help to get the port to suit your needs. > I've been using the PIC16 port (you may notice that PIC16 is for 18F and > PIC14 is for 16F !) for a little time now. > For what I do, I can say that this port is functionnal, but I still need > more and more tests, and you must make yours for determining if it can > be used in production ! > Now, just I can say is that it's perfect for experimental purposes... > Like you, I also want to know more about this port : who maintain it ? For the moment, I am the official maintainer of the pic ports (both pic14 and pic16). > what is fully functionnal, or what features are planned for the future ? Concerning "fully functional", I don't quite understand the question. There are open bugs, so it is not fully functional, but all required functionality is implemented for the pic16 port (pic14 has still some way to go, most importantly initialized variables do only work in the source file that provides the main() routine). The pic16 port has no planned "features", except improved support for more devices, which forces a re-thought library build system. Currently, Zik Saleeba is working on this (he already did a great job on adding this functionality to the pic14 port, so I am quite confident that he will come up with a good solution). Another work-in-progress is the inclusion of the pic16 port into SDCC's regression test framework, which is currently pushed on mainly by Borut Razem. For pic14, handling initialized variables from all source files as on the TODO list---without schedule due to lack of time. > I can provide some help, but I have to know how ? Help is possible in several ways: (1) post bug reports into the tracker system, including (small) code samples that reproduce the bug (2) post bug fixes/patches/feature requests via the tracker system (3) use the compiler and provide feedback about possible improvements on one of the mailing lists (sdcc-user/sdcc-devel) (4) each of the above holds equally well for source code and documentation (admittedly not one of my strengths) If there are any questions left unanswered, feel free to ask back. Regards, Raphael |