Thanks a lot Raphael.
On Oct 24, 2011 7:03 PM, "Raphael Neider" wrote:
> Hi,
>
> > One day I had the impression that using unsigned char or uint8_t worked
> even
> > if config word was bigger than 8 bits. Am I right?
>
> That's right: the data type is ignored if the address (__at()) refers
> to a
> Just for me, if the code is backward compatible, it should be no problem to
> support enhanced architecture chips. Or did I miss something? What are
> drawbacks of supporting these devices?
The enhanced devices use 14-bit instructions but address more memory
banks -- and for this they use diff
Hi,
> One day I had the impression that using unsigned char or uint8_t worked even
> if config word was bigger than 8 bits. Am I right?
That's right: the data type is ignored if the address (__at()) refers
to a config location. I noticed this when I looked into the problem
with the enhanced pic14
Speaking about config:
One day I had the impression that using unsigned char or uint8_t worked even
if config word was bigger than 8 bits. Am I right?
Thanks
On Mon, Oct 24, 2011 at 9:40 AM, Vaclav Peroutka wrote:
>
>
> > > So, please do not disable or exclude pic14 enh. support in the
> forth
> > So, please do not disable or exclude pic14 enh. support in the forthcoming
> > next sdcc release.
>
> OK -- I was indeed considering to remove "support" for these devices;
> now I will just leave it as it is.
>
Just for me, if the code is backward compatible, it should be no problem to
su
Dear Borut Razem, Thank you for the fast work.Hopefully it fix the problem. I
tried to build gputils by myself but I had no success.I tried it on Ubuntu
11.04. I checked out the trunk from sourceforge svn, next downloaded the Byacc
and flex packeges.Executed ./configure then make and it failed.I
Hi,
> At the PIC12F1822 part the config location should be modified to 0x8007 and
> 0x8008. (I checked the actual datasheet actually.)
You are right, fixed in r6990.
> This device is in the same family of PIC16F1936. They are 14 bit enhanced
> core devices.
While at it, I also added description
On 10/23/2011 08:21 PM, Butuza Tamas wrote:
> Dear Borut Razem,
> Thank you for the fast work.
> Hopefully it fix the problem.
> I tried to build gputils by myself but I had no success.
> I tried it on Ubuntu 11.04.
> I checked out the trunk from sourceforge svn, next downloaded the
> Byacc and fl
On 10/22/2011 11:25 PM, Butuza Tamas wrote:
>
> Ps: I realized that there is also a severe bug in gputils with this
> class of pic devices.
> At the moment it is impossible to create even a trivially simple
> program to these pics.
> Ps2:
> However I'm trying to figure out some workaround.
> Mayb
Dear Raphael, Thank you for fix config problem in sdcc.I checked the
pic14devices.c file and found a small bug in it: At the PIC12F1822 part the
config location should be modified to 0x8007 and 0x8008. (I checked the actual
datasheet actually.)This device is in the same family of PIC16F1936. The
Hello again,
__code unsigned short __at(_CONFIG1) config1Reg = (_FCMEN_OFF &
_IESO_OFF & _BOREN_ON & _CPD_ON & _CP_ON & _MCLRE_OFF & _PWRTE_ON &
_WDTE_OFF & _FOSC_HS);
> __code unsigned short __at(_CONFIG2) config2Reg = (_LVP_ON & _BORV_25 &
> _STVREN_ON & _PLLEN_ON & _WRT_ALL);
Since SDCC r698
Hi,
> __code unsigned short __at(_CONFIG1) config1Reg = (_FCMEN_OFF & _IESO_OFF &
> _BOREN_ON & _CPD_ON & _CP_ON & _MCLRE_OFF & _PWRTE_ON & _WDTE_OFF & _FOSC_HS);
> __code unsigned short __at(_CONFIG2) config2Reg = (_LVP_ON & _BORV_25 &
> _STVREN_ON & _PLLEN_ON & _WRT_ALL);
>
> And it generated
Dear Raphael and Vaclav,
I tried this:
__code unsigned short __at(_CONFIG1) config1Reg = (_FCMEN_OFF & _IESO_OFF &
_BOREN_ON & _CPD_ON & _CP_ON & _MCLRE_OFF & _PWRTE_ON & _WDTE_OFF & _FOSC_HS);
__code unsigned short __at(_CONFIG2) config2Reg = (_LVP_ON & _BORV_25 &
_STVREN_ON & _PLLEN_ON & _WRT_
Hi,
>> First try:unsigned short __at(_CONFIG1) config1Reg = (_FCMEN_OFF
>> & _IESO_OFF & _BOREN_ON & _CPD_ON & _CP_ON & _MCLRE_OFF & _PWRTE_ON &
>> _WDTE_OFF
>> & _FOSC_HS);
I cannot check right now, but you might be missing a __code modifier:
__code unsigned short __at(0x8007) _conf1 = 0x1234;
> Pic14enh. devices has two config word at 0x8007 and 0x8008.I tried with the
> following ways: First try:unsigned short __at(_CONFIG1) config1Reg =
> (_FCMEN_OFF
> & _IESO_OFF & _BOREN_ON & _CPD_ON & _CP_ON & _MCLRE_OFF & _PWRTE_ON &
> _WDTE_OFF
> & _FOSC_HS);
Hi Tamas,
have you tried
unsigne
Dear SDCC users and developers, I'd like to use SDCC to compile some code
for a PIC14 enhanced core device, (PIC16F1936) This mcu is supported by recent
gputils, but apparently there is no support in sdcc.Because other similar
device (with same cpu core) is supported: 12f1822, i decided to patch
16 matches
Mail list logo
