On Dienstag, 24. Juli 2007, Robert Bergfors wrote:
> Quoting Ernst Bachmann <[EMAIL PROTECTED]>:
> > It looks to me like you scramble the flash contents while uploading it.
> >
> > Some ideas where to start looking:
> >
> > Did you try to re-read the flas
On Dienstag, 24. Juli 2007, Robert Bergfors wrote:
> Hello,
>
> I have recently moved to SDCC and even more recently started using PIC18*,
> more specifically 18f2550. I have two problems that I canät seem to figure
> out;
>
> 1. Whenever power is applied, the device seems to start up in a random
>
On Mittwoch, 18. Juli 2007, [EMAIL PROTECTED] wrote:
> I have a problem where i couldnt find a clear answer in the manual/list.
> I want to initialize an 4x4 array like:
>
> char state_table[4][4]={{0,1,-1,0},{-1,0,0,1},{1,0,0,-1},{0,-1,1,0}};
> but this only works if i add the code keyword infron
On Donnerstag, 15. März 2007, Matt Bauman wrote:
> Thank you, Mark. I've been pouring over all the datasheets, and
> couldn't quite seem to grasp these details.
>
> On Mar 14, 2007, at 10:56 PM, Mark Rages wrote:
> > ...
> > So the code ends up looking like this:
> >
> > void isr_high interrupt 1
On Freitag, 9. März 2007, Dave McGuire wrote:
>I'm reading the datasheet for the PIC18F252. On page 259, it
> states that the maximum voltage on any pin (with a few exceptions) is
> Vdd+0.3V. Later, on page 287, it specifies more specifically that
> the maximum voltage for Vref (parameter A21
On Dienstag, 6. Februar 2007, Luit van Drongelen wrote:
> Allright, seems like I finally found my problem... somehow the compiler
> refuses to pass the linker the used/required libraries. Adding -l
> libm18f.lib to my linker options in piklab Fixes everything... Does anybody
> know why this doesn't
On Dienstag, 6. Februar 2007, Luit van Drongelen wrote:
> Hello,
>
> I just started using SDCC, and got nearly everything to work, eventually.
> But one thing still won't do what I want. I can't get the default libraries
> (like libc and math and libio) to work properly. I think I forgot to
> inclu
On Thursday 25 January 2007 12:10, Raphael Neider wrote:
> Am Donnerstag, den 25.01.2007, 15:57 +0530 schrieb george john:
> > But the problem is with the compiler if we compile the above code
> > with sdcc 2.6.0 it will work but with sdcc 2.6.3 it will not work.
>
And I'd say its not as much a p
On Thursday 25 January 2007 08:50, george john wrote:
> > EECON2 = 0x55; // Write "password" to EECON2
> > EECON2 = 0xAA;
> > WR = 1; // Initiate a write cycle
> >
Well, the PIC Datasheet claims that an exact timed sequence is ne
On Sunday 14 January 2007 10:48, Rodrigo Guerra wrote:
> > On 1/14/07, Borut Razem < [EMAIL PROTECTED]> wrote:
> > > Rodrigo Guerra wrote:
> > > >
> > > > void main(void)
> > > > {
> > > > unsigned char c = 0x34;
> > > > unsigned char *p;
> > > >
> > > > p = &c;
> > > > p = 0x1
Hi,
I'm using sdcc with an pic18f2550 (with varying success), maybe I can provide
some help (Not for win95 or USART, I don't use them).
On Tuesday 09 January 2007 14:26, Gyorgy Horvath wrote:
> 3. /sdcc/lib/src/pic16/startup
>Since startup code does not reflect to linker script
>
>CODE
On Thursday 04 January 2007 19:27, polly wrote:
>Thanks for the snippet, Ernst, I've been trying to locate the
> descriptors in flash a la uChip Demo code rather than in RAM
> as your code seems to do.
>
> regards, p
Well, I keep the descriptors in flash. (note the "code" keyword)
I just don
On Thursday 04 January 2007 16:14, polly wrote:
> Hello,
>This is a bit of a puzzle, trying to locate decriptors in flas seems to
> result in
> byte swapping ...
>
>typedef unsigned char byte;
> typedef unsigned int word;
> []
Hrm, which µC? PIC16 Port?
and what exactly goes wrong?
H
On Monday 13 November 2006 22:55, launay wrote:
> Hello,
>
> I update my Ubuntu to Edgy and now i work with sdcc 2.6.0 before i was
> working with sdcc2.5.4
>
> Why do you remove the ports' bits and tris' bits ?
> For example you can put
> #define IR PA0
> and after put IR=1
> It's more easy to wor
On Friday 13 October 2006 12:09, Marius Kintel wrote:
> > I'm using that bootloader with sdcc-compiled code, here's what I did:
> >
> > - add a local copy of the crt0*.c file to your project.
>
> Thanks for the feedback. This is exactly what I resorted to in the
> end - it just feels a little hack
On Friday 13 October 2006 00:11, Marius Kintel wrote:
> Hi,
>
> I'm trying to find a convenient way to relocate interrupt vectors to
> allow for a bootloader to be placed at 0x. The bootloader in
> question is the USB bootloader from Microchip. This bootloader lives
> in 0x-0x07ff and calls
On Wednesday 02 August 2006 17:17, Jean-Sebastien Stoezel wrote:
> I would like to know what is the current support of SDCC for PIC
> microcontrollers? What about 16F628A?
I'm using it with great success for pic18F[24]550 devices, the only bigger
issues I noticed came from the aged version of gpu
Hi,
On Wednesday 26 July 2006 06:00, [EMAIL PROTECTED] wrote:
> Dear listers,
>
> I thank you all for your responses.
>
> I have resolved my original problem. Now I am happily compiling using
> modular feature and make the best of it.
[...]
> SYS.H
> =
> #ifndef SYS_H
> #define
Hi List,
I'm coding some firmware for a pic18f2550 device with sdcc, using the
bootloader firmware provided by microchip.
The bootloader occupies 0x0 - 0x7FF, and expects the reset/interrupt vectors
to be at 0x800, 0x808, etc.
But sdcc/gplink seem to hardcode their location to 0x00, 0x08, 0x18
19 matches
Mail list logo
