From: barryc <ba...@rj...> - 2003-07-28 19:31:59
|
How is the Microchip PIC support? I didn't see a response in the list archive. The main page of the website makes the statement that "Work is in progress on supporting the ... Microchip PIC series." I was wondering if somebody would be able to tell me how far along the PIC support happens to be. From a look through the list archive over the past year, and the small amount of PIC-related traffic makes me a bit wary, but I see from CVS that work IS still being done. |
From: The S. <st...@ch...> - 2003-07-28 23:28:02
|
Greetings, I know that SDCC is a generic compiler and technically works for any 8051 derivative, this question is really tailored to peoples specific experience with this chip derivative. Has anyone gotten this chip to work with SDCC ? My code runs perfect in the simulator, but for some reason when i execute it on the real target it has strtok, and strchr issues ! I am using the ERAM which should act just like External RAM, but i am not sure. My interrupt code is working, and i dont really have any timing related code which would present a difference between a simulator and the real target. Sorry about the generic nature of the question, i am sort of looking for any ideas anyone would have. Thanks in Advance for your Help, Lenny Story PS : And yes, i have RTFM.. 8^) |
From: Nick Craig-W. <nc...@ax...> - 2003-07-29 09:59:24
|
On Mon, Jul 28, 2003 at 07:29:57PM -0400, The Storys wrote: > My code runs perfect in the simulator, but for some reason when i execute it > on the real target it has strtok, and strchr issues ! You might be being bitten by this bug... http://sourceforge.net/tracker/?func=detail&aid=597164&group_id=599&atid=350599 It has similar symptoms... -- Nick Craig-Wood nc...@ax... |
From: Greg H. <gr...@hi...> - 2003-07-29 00:33:22
|
I've been using it with reasonable success. Of course there are some problems/quirks you'll have to get used to. For example, I can't figure out how to make it pass more than one parameter to a function. It seems that only the first gets through, all others become 0's. The workaround I came up with is to declare a global variable and use it for passing a second argument through a function call. Version 2.3.5 supports the following: 16F627, 16F628, 16F84, 16F873, 16F877, 16F819. Note that devices similar to these can be used, also. For example, the 16F876 has the same memory structure as the 877, but comes in a smaller package because it has fewer I/O pins. I wrote my code and told SDCC to compile for the 16F877, and then I edited the resulting .asm file to change it to 16F876 and then assembled. It sounds tedious, but if you put all the steps (sdcc, then sed to fix the .asm file, then gpasm) into a makefile, it's no harder than targetting one of the directly supported devices. Another thing that's broken is inline assembly. The easy work-around for that is to put your assembly code into functions in a separate .asm file, which you can turn into a .o file and later link with your work from sdcc. Greg On Mon, 28 Jul 2003, barryc wrote: > How is the Microchip PIC support? I didn't see a response in the list > archive. > > The main page of the website makes the statement that "Work is in > progress on supporting the ... Microchip PIC series." > > I was wondering if somebody would be able to tell me how far along the > PIC support happens to be. From a look through the list archive over > the past year, and the small amount of PIC-related traffic makes me a > bit wary, but I see from CVS that work IS still being done. |
From: <bra...@ca...> - 2003-07-29 05:16:45
|
There is also the mpic16 which works on the PIC18XXX (I forget which ones - I am going to try a couple in the next few days). In the PIC14 version, the interrupt code also has a problem. You have to edit the asm file to add a nop and to remove a go_to_ + 1 instruction for it to work. I have been using it on the PIC76 by telling SDCC it is a 16F877, the changing the asm file to saty 16F76 (the assembler supports a lot more pic variaties). \ On 28 Jul 2003 at 18:32, Greg Hill wrote: > I've been using it with reasonable success. Of course there are some > problems/quirks you'll have to get used to. For example, I can't figure > out how to make it pass more than one parameter to a function. It seems > that only the first gets through, all others become 0's. The workaround I > came up with is to declare a global variable and use it for passing a > second argument through a function call. > > Version 2.3.5 supports the following: 16F627, 16F628, 16F84, 16F873, > 16F877, 16F819. Note that devices similar to these can be used, also. For > example, the 16F876 has the same memory structure as the 877, but comes in > a smaller package because it has fewer I/O pins. I wrote my code and told > SDCC to compile for the 16F877, and then I edited the resulting .asm file > to change it to 16F876 and then assembled. It sounds tedious, but if you > put all the steps (sdcc, then sed to fix the .asm file, then gpasm) into a > makefile, it's no harder than targetting one of the directly supported > devices. > > Another thing that's broken is inline assembly. The easy work-around for > that is to put your assembly code into functions in a separate .asm file, > which you can turn into a .o file and later link with your work from sdcc. > > Greg > > > On Mon, 28 Jul 2003, barryc wrote: > > > How is the Microchip PIC support? I didn't see a response in the list > > archive. > > > > The main page of the website makes the statement that "Work is in > > progress on supporting the ... Microchip PIC series." > > > > I was wondering if somebody would be able to tell me how far along the > > PIC support happens to be. From a look through the list archive over > > the past year, and the small amount of PIC-related traffic makes me a > > bit wary, but I see from CVS that work IS still being done. > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user |
From: <bra...@ca...> - 2003-08-12 06:00:55
|
Just thought those running windows might be interested in how I was able to use inc2h.pl on windows 98. Using inc2h.pl in Windows: Download and install ActivePerl. Make sure you have gputils installed in c:\gputils. Open an MSDOS window. Go to the directory you have inc2h.pl in. If it is in C:\SDCC type CD c:\SDCC For the 18f252 as an example(for other processors, substitute for the 18f252) enter the following command line: perl inc2h.pl 18f252 c:\gputils >p18f252.h This will convert the .inc file to SDCC format and redirect output to the file "p18f252.h" Dave Brainerd |