gnupic: PIC18F47J53
Subject:
Re: PIC18F47J53
From:
Mauricio Giovagnini ####@####.####
Date:
17 Aug 2013 22:58:14 -0000
Message-Id: <52100023.9050103@yahoo.com.ar>
Hi Luis, I'm not familiar with the sdd linker but on the microchip
linker the files that end with an 'i' do reserve some resources for an
external debugger like the ICD2, ICD3, pickit3, etc.
If that is also the case for the sdcc linker and if you are not using a
debugger as a debugger (you are using it only as a programmer), then you
shouldn't use the i files.
Regards,
--
Mauricio Giovagnini (Maunix)
Sitio Web: www.maunix.com.ar
El 12/08/2013 05:09 p.m., Luis de Arquer escribió:
> Problem 2:
>
> This is the scary one. In the gplink line, if I change "crt0.o" by
> "crt0i.o", the clock settings go random on startup. Again, I'll
> probably post it in the sdcc maillist, but the crt0i.c is almost
> entirely written in asm (it comes bundled with sdcc in
> "device/lib/pic16/startup/", but I can post it here if you want).
> So basically, the blink frequency is different with every power on
> reset; sometimes visible, sometimes you need the oscilloscope.
> Obviously I am not asking for anyone to dig into crt0i.c (it seems to
> be the same basic stack initialization than crt0.c plus data
> initialization (.cinit), reading stuff from program memory and copying
> to RAM). The question is, what sort of thing could cause a random
> clock setting with every hard reset? -soft reset not tested yet.
>
> It has to be electrical, hasn't it?
>
> Regards,
>
> Luis
>
