From: Richard H. <hug...@gm...> - 2012-05-25 14:19:21
|
Hi all, I'm the main developer for ColorHug, an open source colorimeter device. I'm looking to port away from the Microchip tools, and compile natively using Linux. I'm using a PIC18F46J50 in the hardware, and need to set certain config fuses to do things like turning on the watch dog timer and setting the clock PLL mode. I noticed that the file device/non-free/include/pic16/pic18f46j50.h is missing all the fuse #defines, unlike other files like device/non-free/include/pic16/pic18f2455.h which do have the constants, e.g. pic18f2455.h: /* Configuration register locations */ #define __CONFIG1L 0x300000 #define __CONFIG1H 0x300001 ... /* Full-Speed USB Clock Source Selection 1L options */ #define _USBPLL_CLOCK_SRC_FROM_96MHZ_PLL_2_1L 0xFF /* Clock src from 96MHz PLL/2 */ #define _USBPLL_CLOCK_SRC_FROM_OSC1_OSC2_1L 0xDF /* Clock src from OSC1/OSC2 */ pic18f46j50.h: #define __CONFIG1L 0xFFF8 #define __CONFIG1H 0xFFF9 ... Now, i see both files were created by inc2h-pic16.pl which must use the gputils/header/p18f2455.inc and gputils/lkr/18f46j50.lkr files as inputs. Looking at these files, it looks like the former has the _PLLDIV_1_1L type #defines created manually, and the other does not. To correct the pic18f46j50.h shipped with sdcc, I'm guessing I have to "fix" the 18f46j50.lkr file in gputils, and then re-run inc2h-pic16.pl -- does that sound about correct? Richard |
From: Borut R. <bor...@gm...> - 2012-05-25 15:34:32
|
In p18f45j50.inc from gputils and from mpasm is written: ; IMPORTANT: For the PIC18 devices, the __CONFIG directive has been ; superseded by the CONFIG directive. The following settings ; are available for this device. This is why there are no __config definitions in the gputils *.inc and consequently in sdcc pic16 device *.h files. Have you tried to use #pragma config as described in sdccman? Be careful: #pragma config was introduced 2012-03-16, which means that it exists only in the sdcc snapshot builds. Borut On 25. 05. 2012 16:19, Richard Hughes wrote: > Hi all, > > I'm the main developer for ColorHug, an open source colorimeter > device. I'm looking to port away from the Microchip tools, and compile > natively using Linux. > > I'm using a PIC18F46J50 in the hardware, and need to set certain > config fuses to do things like turning on the watch dog timer and > setting the clock PLL mode. I noticed that the file > device/non-free/include/pic16/pic18f46j50.h is missing all the fuse > #defines, unlike other files like > device/non-free/include/pic16/pic18f2455.h which do have the > constants, e.g. > > pic18f2455.h: > > /* Configuration register locations */ > #define __CONFIG1L 0x300000 > #define __CONFIG1H 0x300001 > ... > /* Full-Speed USB Clock Source Selection 1L options */ > #define _USBPLL_CLOCK_SRC_FROM_96MHZ_PLL_2_1L 0xFF /* Clock src > from 96MHz PLL/2 */ > #define _USBPLL_CLOCK_SRC_FROM_OSC1_OSC2_1L 0xDF /* Clock src > from OSC1/OSC2 */ > > pic18f46j50.h: > > #define __CONFIG1L 0xFFF8 > #define __CONFIG1H 0xFFF9 > ... > > Now, i see both files were created by inc2h-pic16.pl which must use > the gputils/header/p18f2455.inc and gputils/lkr/18f46j50.lkr files as > inputs. Looking at these files, it looks like the former has the > _PLLDIV_1_1L type #defines created manually, and the other does not. > To correct the pic18f46j50.h shipped with sdcc, I'm guessing I have to > "fix" the 18f46j50.lkr file in gputils, and then re-run inc2h-pic16.pl > -- does that sound about correct? > > Richard > |
From: Richard H. <hug...@gm...> - 2012-05-25 16:43:09
|
On 25 May 2012 16:34, Borut Ražem <bor...@gm...> wrote: > This is why there are no __config definitions in the gputils *.inc and > consequently in sdcc pic16 device *.h files. Ahh, right. > Have you tried to use #pragma config as described in sdccman? Be > careful: #pragma config was introduced 2012-03-16, which means that it > exists only in the sdcc snapshot builds. I've built master, and tried that. On initial try it worked fine, but trying to build my firmware image I'm getting: test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored It seems sdcc expects: #pragma config WDTEN=ON and the Microchip compiler accepts: #pragma config WDTEN = ON (i.e. '<tab>', '=', '<space>') Should sdcc could just ignore the white space for compatibility? MPLAB seems to accept either. I'll do some more testing later tonight and find out how things go with sdcc from master. Thanks, Richard. |
From: Borut R. <bor...@gm...> - 2012-05-25 19:27:30
|
On 25. 05. 2012 18:43, Richard Hughes wrote: > I've built master, and tried that. On initial try it worked fine, but > trying to build my firmware image I'm getting: > > test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored > > It seems sdcc expects: > > #pragma config WDTEN=ON > > and the Microchip compiler accepts: > > #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>') > > Should sdcc could just ignore the white space for compatibility? MPLAB > seems to accept either. I'll do some more testing later tonight and > find out how things go with sdcc from master. OK, so for now you have something to play with. In the mean time I'll correct the white space handling. Borut |
From: Diego H. <die...@di...> - 2012-05-26 01:27:08
|
sdccman says: #pragma config setting=value [, setting=value] but just after: #pragma configure CP0=OFF,OSCS=ON The former is the correct one, isn't it? Thanks On Fri, May 25, 2012 at 9:27 PM, Borut Ražem <bor...@gm...> wrote: > On 25. 05. 2012 18:43, Richard Hughes wrote: > > I've built master, and tried that. On initial try it worked fine, but > > trying to build my firmware image I'm getting: > > > > test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored > > > > It seems sdcc expects: > > > > #pragma config WDTEN=ON > > > > and the Microchip compiler accepts: > > > > #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>') > > > > Should sdcc could just ignore the white space for compatibility? MPLAB > > seems to accept either. I'll do some more testing later tonight and > > find out how things go with sdcc from master. > > OK, so for now you have something to play with. In the mean time I'll > correct the white space handling. > > Borut > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Borut R. <bor...@gm...> - 2012-05-26 08:37:41
|
#pragma config is correct. #pragma configure was a mistake in sdccman. I alredy corrected it. Borut On Sat, May 26, 2012 at 3:26 AM, Diego Herranz < die...@di...> wrote: > sdccman says: > > #pragma config setting=value [, setting=value] > > but just after: > > #pragma configure CP0=OFF,OSCS=ON > > The former is the correct one, isn't it? > > Thanks > > > On Fri, May 25, 2012 at 9:27 PM, Borut Ražem <bor...@gm...>wrote: > >> On 25. 05. 2012 18:43, Richard Hughes wrote: >> > I've built master, and tried that. On initial try it worked fine, but >> > trying to build my firmware image I'm getting: >> > >> > test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored >> > >> > It seems sdcc expects: >> > >> > #pragma config WDTEN=ON >> > >> > and the Microchip compiler accepts: >> > >> > #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>') >> > >> > Should sdcc could just ignore the white space for compatibility? MPLAB >> > seems to accept either. I'll do some more testing later tonight and >> > find out how things go with sdcc from master. >> >> OK, so for now you have something to play with. In the mean time I'll >> correct the white space handling. >> >> Borut >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > |
From: Diego H. <die...@di...> - 2012-05-26 08:58:55
|
Thanks! On Sat, May 26, 2012 at 10:37 AM, Borut Ražem <bor...@gm...> wrote: > #pragma config is correct. #pragma configure was a mistake in sdccman. I > alredy corrected it. > > Borut > > > On Sat, May 26, 2012 at 3:26 AM, Diego Herranz < > die...@di...> wrote: > >> sdccman says: >> >> #pragma config setting=value [, setting=value] >> >> but just after: >> >> #pragma configure CP0=OFF,OSCS=ON >> >> The former is the correct one, isn't it? >> >> Thanks >> >> >> On Fri, May 25, 2012 at 9:27 PM, Borut Ražem <bor...@gm...>wrote: >> >>> On 25. 05. 2012 18:43, Richard Hughes wrote: >>> > I've built master, and tried that. On initial try it worked fine, but >>> > trying to build my firmware image I'm getting: >>> > >>> > test.c:7: warning 191: #pragma config: bad argument(s); pragma ignored >>> > >>> > It seems sdcc expects: >>> > >>> > #pragma config WDTEN=ON >>> > >>> > and the Microchip compiler accepts: >>> > >>> > #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>') >>> > >>> > Should sdcc could just ignore the white space for compatibility? MPLAB >>> > seems to accept either. I'll do some more testing later tonight and >>> > find out how things go with sdcc from master. >>> >>> OK, so for now you have something to play with. In the mean time I'll >>> correct the white space handling. >>> >>> Borut >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Sdcc-user mailing list >>> Sdc...@li... >>> https://lists.sourceforge.net/lists/listinfo/sdcc-user >>> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> >> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > |
From: Borut R. <bor...@gm...> - 2012-05-26 18:18:02
|
"allow space characters in #pragma config" problem fixed in svn revision #7792. Borut On 26. 05. 2012 10:58, Diego Herranz wrote: > Thanks! > > On Sat, May 26, 2012 at 10:37 AM, Borut Ražem <bor...@gm... > <mailto:bor...@gm...>> wrote: > > #pragma config is correct. #pragma configure was a mistake in > sdccman. I alredy corrected it. > > Borut > > > On Sat, May 26, 2012 at 3:26 AM, Diego Herranz > <die...@di... > <mailto:die...@di...>> wrote: > > sdccman says: > > #pragma config setting=value [, setting=value] > > but just after: > > #pragma configure CP0=OFF,OSCS=ON > > The former is the correct one, isn't it? > > Thanks > > > On Fri, May 25, 2012 at 9:27 PM, Borut Ražem > <bor...@gm... <mailto:bor...@gm...>> wrote: > > On 25. 05. 2012 18 <tel:25.%2005.%202012%2018>:43, Richard > Hughes wrote: > > I've built master, and tried that. On initial try it > worked fine, but > > trying to build my firmware image I'm getting: > > > > test.c:7: warning 191: #pragma config: bad argument(s); > pragma ignored > > > > It seems sdcc expects: > > > > #pragma config WDTEN=ON > > > > and the Microchip compiler accepts: > > > > #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>') > > > > Should sdcc could just ignore the white space for > compatibility? MPLAB > > seems to accept either. I'll do some more testing later > tonight and > > find out how things go with sdcc from master. > > OK, so for now you have something to play with. In the > mean time I'll > correct the white space handling. > > Borut > |
From: Richard H. <hug...@gm...> - 2012-05-27 08:09:05
|
On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: > "allow space characters in #pragma config" problem fixed in svn revision > #7792. Great, thanks dude. Richard. |
From: Diego H. <die...@di...> - 2012-05-27 11:43:53
|
With 18f4550 and sdcc #7792: [...] 26 #pragma config PLLDIV = 1 27 #pragma config CPUDIV = OSC1_PLL2 28 #pragma config USBDIV = 2 29 30 31 #pragma config FOSC USBDIV = HSPLL_HS [...] Warnings: MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); pragma ignored MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); pragma ignored Maybe a problem with underscores? Thanks a lot On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: > On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: > > "allow space characters in #pragma config" problem fixed in svn revision > > #7792. > > Great, thanks dude. > > Richard. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Diego H. <die...@di...> - 2012-05-27 11:50:30
|
Sorry, line 31 was: 31 #pragma config FOSC = HSPLL_HS On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < die...@di...> wrote: > With 18f4550 and sdcc #7792: > > [...] > 26 #pragma config PLLDIV = 1 > 27 #pragma config CPUDIV = OSC1_PLL2 > 28 #pragma config USBDIV = 2 > 29 > 30 > 31 #pragma config FOSC USBDIV = HSPLL_HS > [...] > > Warnings: > MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); > pragma ignored > MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); > pragma ignored > > Maybe a problem with underscores? > > Thanks a lot > > > On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: > >> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >> > "allow space characters in #pragma config" problem fixed in svn revision >> > #7792. >> >> Great, thanks dude. >> >> Richard. >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> > > |
From: Borut R. <bor...@gm...> - 2012-05-27 20:47:33
|
Yes, the problem are underscores :-(. I'll fix it ASAP. Borur On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < die...@di...> wrote: > Sorry, line 31 was: > > 31 #pragma config FOSC = HSPLL_HS > > > On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < > die...@di...> wrote: > >> With 18f4550 and sdcc #7792: >> >> [...] >> 26 #pragma config PLLDIV = 1 >> 27 #pragma config CPUDIV = OSC1_PLL2 >> 28 #pragma config USBDIV = 2 >> 29 >> 30 >> 31 #pragma config FOSC USBDIV = HSPLL_HS >> [...] >> >> Warnings: >> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); >> pragma ignored >> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); >> pragma ignored >> >> Maybe a problem with underscores? >> >> Thanks a lot >> >> >> On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: >> >>> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >>> > "allow space characters in #pragma config" problem fixed in svn >>> revision >>> > #7792. >>> >>> Great, thanks dude. >>> >>> Richard. >> >> |
From: Diego H. <die...@di...> - 2012-05-27 21:51:59
|
Great! Thank you. On Sun, May 27, 2012 at 10:47 PM, Borut Ražem <bor...@gm...> wrote: > Yes, the problem are underscores :-(. I'll fix it ASAP. > > Borur > > > On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < > die...@di...> wrote: > >> Sorry, line 31 was: >> >> 31 #pragma config FOSC = HSPLL_HS >> >> >> On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < >> die...@di...> wrote: >> >>> With 18f4550 and sdcc #7792: >>> >>> [...] >>> 26 #pragma config PLLDIV = 1 >>> 27 #pragma config CPUDIV = OSC1_PLL2 >>> 28 #pragma config USBDIV = 2 >>> 29 >>> 30 >>> 31 #pragma config FOSC USBDIV = HSPLL_HS >>> [...] >>> >>> Warnings: >>> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); >>> pragma ignored >>> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); >>> pragma ignored >>> >>> Maybe a problem with underscores? >>> >>> Thanks a lot >>> >>> >>> On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: >>> >>>> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >>>> > "allow space characters in #pragma config" problem fixed in svn >>>> revision >>>> > #7792. >>>> >>>> Great, thanks dude. >>>> >>>> Richard. >>> >>> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > |
From: Borut R. <bor...@gm...> - 2012-05-28 07:24:33
|
#pragma config accepts underscore characters in svn revision #7797. Borut On Sun, May 27, 2012 at 11:51 PM, Diego Herranz < die...@di...> wrote: > Great! Thank you. > > On Sun, May 27, 2012 at 10:47 PM, Borut Ražem <bor...@gm...>wrote: > >> Yes, the problem are underscores :-(. I'll fix it ASAP. >> >> Borur >> >> >> On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < >> die...@di...> wrote: >> >>> Sorry, line 31 was: >>> >>> 31 #pragma config FOSC = HSPLL_HS >>> >>> >>> On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < >>> die...@di...> wrote: >>> >>>> With 18f4550 and sdcc #7792: >>>> >>>> [...] >>>> 26 #pragma config PLLDIV = 1 >>>> 27 #pragma config CPUDIV = OSC1_PLL2 >>>> 28 #pragma config USBDIV = 2 >>>> 29 >>>> 30 >>>> 31 #pragma config FOSC USBDIV = HSPLL_HS >>>> [...] >>>> >>>> Warnings: >>>> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); >>>> pragma ignored >>>> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); >>>> pragma ignored >>>> >>>> Maybe a problem with underscores? >>>> >>>> Thanks a lot >>>> >>>> >>>> On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: >>>> >>>>> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >>>>> > "allow space characters in #pragma config" problem fixed in svn >>>>> revision >>>>> > #7792. >>>>> >>>>> Great, thanks dude. >>>>> >>>>> Richard. >>>> >>>> |
From: Diego H. <die...@di...> - 2012-05-28 09:04:43
|
Great. I'll test it as soon as the snapshot is built. Thank you very much! On Mon, May 28, 2012 at 9:24 AM, Borut Ražem <bor...@gm...> wrote: > #pragma config accepts underscore characters in svn revision #7797. > > Borut > > > > On Sun, May 27, 2012 at 11:51 PM, Diego Herranz < > die...@di...> wrote: > >> Great! Thank you. >> >> On Sun, May 27, 2012 at 10:47 PM, Borut Ražem <bor...@gm...>wrote: >> >>> Yes, the problem are underscores :-(. I'll fix it ASAP. >>> >>> Borur >>> >>> >>> On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < >>> die...@di...> wrote: >>> >>>> Sorry, line 31 was: >>>> >>>> 31 #pragma config FOSC = HSPLL_HS >>>> >>>> >>>> On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < >>>> die...@di...> wrote: >>>> >>>>> With 18f4550 and sdcc #7792: >>>>> >>>>> [...] >>>>> 26 #pragma config PLLDIV = 1 >>>>> 27 #pragma config CPUDIV = OSC1_PLL2 >>>>> 28 #pragma config USBDIV = 2 >>>>> 29 >>>>> 30 >>>>> 31 #pragma config FOSC USBDIV = HSPLL_HS >>>>> [...] >>>>> >>>>> Warnings: >>>>> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); >>>>> pragma ignored >>>>> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); >>>>> pragma ignored >>>>> >>>>> Maybe a problem with underscores? >>>>> >>>>> Thanks a lot >>>>> >>>>> >>>>> On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm...>wrote: >>>>> >>>>>> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >>>>>> > "allow space characters in #pragma config" problem fixed in svn >>>>>> revision >>>>>> > #7792. >>>>>> >>>>>> Great, thanks dude. >>>>>> >>>>>> Richard. >>>>> >>>>> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > |
From: Diego H. <die...@di...> - 2012-05-29 12:28:03
|
Tested. It seems to work like a charm. Thanks again! On Mon, May 28, 2012 at 11:03 AM, Diego Herranz < die...@di...> wrote: > Great. > > I'll test it as soon as the snapshot is built. > > Thank you very much! > > On Mon, May 28, 2012 at 9:24 AM, Borut Ražem <bor...@gm...>wrote: > >> #pragma config accepts underscore characters in svn revision #7797. >> >> Borut >> >> >> >> On Sun, May 27, 2012 at 11:51 PM, Diego Herranz < >> die...@di...> wrote: >> >>> Great! Thank you. >>> >>> On Sun, May 27, 2012 at 10:47 PM, Borut Ražem <bor...@gm...>wrote: >>> >>>> Yes, the problem are underscores :-(. I'll fix it ASAP. >>>> >>>> Borur >>>> >>>> >>>> On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < >>>> die...@di...> wrote: >>>> >>>>> Sorry, line 31 was: >>>>> >>>>> 31 #pragma config FOSC = HSPLL_HS >>>>> >>>>> >>>>> On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < >>>>> die...@di...> wrote: >>>>> >>>>>> With 18f4550 and sdcc #7792: >>>>>> >>>>>> [...] >>>>>> 26 #pragma config PLLDIV = 1 >>>>>> 27 #pragma config CPUDIV = OSC1_PLL2 >>>>>> 28 #pragma config USBDIV = 2 >>>>>> 29 >>>>>> 30 >>>>>> 31 #pragma config FOSC USBDIV = HSPLL_HS >>>>>> [...] >>>>>> >>>>>> Warnings: >>>>>> MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); >>>>>> pragma ignored >>>>>> MIDI_PEDAL_fuses.h:31: warning 191: #pragma config: bad argument(s); >>>>>> pragma ignored >>>>>> >>>>>> Maybe a problem with underscores? >>>>>> >>>>>> Thanks a lot >>>>>> >>>>>> >>>>>> On Sun, May 27, 2012 at 10:08 AM, Richard Hughes <hug...@gm... >>>>>> > wrote: >>>>>> >>>>>>> On 26 May 2012 19:17, Borut Ražem <bor...@gm...> wrote: >>>>>>> > "allow space characters in #pragma config" problem fixed in svn >>>>>>> revision >>>>>>> > #7792. >>>>>>> >>>>>>> Great, thanks dude. >>>>>>> >>>>>>> Richard. >>>>>> >>>>>> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> >> > |