gnupic: PIC18F47J53
Subject:
Re: PIC18F47J53
From:
Luis de Arquer ####@####.####
Date:
13 Aug 2013 20:29:24 -0000
Message-Id: <CAD_DGvmkNor1Vq1G9eLmkXoS-k515W+49wmyVWYp6YK9NiTSxA@mail.gmail.com>
I think I am giving up on this one.
I have put all the right SMD capacitors as close as I could, including
a 10uF ceramic for vddcore, but still the same issue.
I am using pickit2 for this pic (18f47j53), and although I found a
.dat file which supports it, I couldn't find anywhere in the microchip
website saying it is supported really... so that could be the source
of the grief.
Thank you all anyway :)
On Mon, Aug 12, 2013 at 10:54 PM, Bob Jacobsen ####@####.#### wrote:
>
> On Aug 12, 2013, at 1:09 PM, Luis de Arquer ####@####.#### wrote:
>
>> Problem number 1 is surely a C issue, which is the sleep function I made:
>>
>> ****************************
>>
>> typedef unsigned char byte;
>>
>> void sleep_a_while(byte c) /* A */
>> {
>> byte i,j; /* B */
>>
>> for(i=0; i<200; i++)
>> for(j=0; j<c; j++) ;
>> }
>>
>>
>> **************************
>>
>> Changing "byte" for "int" in any of those lines changes the timing. It
>> makes the sleep time not only different -which makes sense since int
>> is translated to int16 apparently, with its overhead-, but independent
>> on c (the input parameter ! ).
>
>
> Do you mean if you change (A) but not (B) or vice-versa?
>
> I'd check the assembler code to see what's happening to the upper byte of the int values. If it's being left unchanged, all sorts of interesting things can happen, particularly if you call sleep-a-while with a value greater than 127.
>
> Bob
> --
> Bob Jacobsen, LBNL Physics Division
> ####@####.#### +1-510-486-7355 AIM, Skype JacobsenRG
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
