G'day folks
I am trying to write some code for an lcd module to put in a library. I
seem to need to be able to read/write from a port in the library. I
would like to be able to refer to it as, say lcdport so different
hardware set-ups can use the same code. I can create a lcd structure thus:
G'day Raphael
>
>
> Subject:
> Re: [Sdcc-user] pic14 port alternative name
> From:
> Raphael Neider <[EMAIL PROTECTED]>
> Date:
> Sun, 07 Sep 2008 21:13:04 +0200
> To:
> sdcc-user@lists.sourceforge.net
>
> To:
> sdcc-user@list
not
write it as a full time job.
- The difference wrt. a commercial compiler (written by full time
jobbers) shows. Mostly as code size but not only.
- In despite of this, SDCC is one of the best C compilers for embedded,
and one of the very few which are free and open sourced.
You can't have
Hi List,
I'm very new to SDCC. I'm just starting to develop a project using a
pic18f66j60 device to connect a motor drive to an ip network. MY plan is to
have a webserver (http/tcp) control protocol that can be accessed through a
web browser or other software. So far i've had an attempt at getting
Thanks Pedro, Thats a shame. I wonder if its possible to compile the
microchip stack into asm, and then wrap them up into functons that sdcc can
handle?
Regards
Peter
2009/1/26 Ov3rM1nd
> Hi Peter,
>
> I've tried to do what you are doing but without success. It would give a
&g
Thanks Tristan, I'm wondering if the pic18f is the best chip for this as it
doesn't seem to have too many ports. Would I be better off with an 8051, arm
or coldfire?
Regards
Peter
2009/1/26 Tristan Willy
> When I was looking for small networking stacks, uIP
> <http://ww
#x27;m having to remember
alot of the details too.
On a slightly different note, i'm considering rewriting the tcp/ip stack
myself, as i could also (maybe) put in ipv6 support at the same time. Is
this as silly an idea as I think it is? or is it quite straightforward once
i've got som
Unless the structures
are packed by default in SDCC.
Peter
2009/1/28 Vaclav Peroutka
> Hi Peter,
>
> > I agree with you in part on this, but it is useful to have a clear
> answer
> > about the state of the compiler you're working with so you know what you
> can
> &
Hi,
How to make a default pointer type xdata pointer and not generic as it is
currently.
Cheers,
Peter Kuhar
http://www.pkuhar.com/
skype: pkuhar
--
Create and Deploy Rich Internet Apps outside the browser with Adobe
unqulified
pointers xdata.
Cheers,
Peter
http://www.pkuhar.com/
http://www.modula.si
skype: pkuhar
On Wed, Feb 11, 2009 at 9:39 AM, Maarten Brock wrote:
> Peter,
>
> That is currently impossible because how would you
> otherwise create a generic pointer? There is no
> 'generic
ocument those techniques that are working for us The
collection/collation of results such as these should represent a valuable
reference for all SDCC users.
Peter Townson
From: Lucas Tanure [mailto:ltan...@gmail.com]
Sent: Thursday, 5 March 2009 9:28 PM
To: sd
bit 0 switches between DPTR0 and DPTR1
Cheers,
Peter
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
where bit 0 switches between DPTR0 and DPTR1
Cheers,
Peter
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc
_reserved1[2048]={ 0xAA,0x55 ... }
but is doesn't initialize the variable at that location.
Cheers,
Peter
--
___
Sdcc-user mailing list
Sdcc-user@lists.source
sdcc 2.8.0 msc51
--model-large --stack-auto
Thanks,
Peter
Maarten Brock wrote:
Peter,
Please include SDCC version and target for which you
compile. For mcs51 this should work I think.
Maarten
Hi,
Is it possible to make linker skip a part of code memory?
I'd like t
It turns out, that the problem with conversion from ihex to binary with
objcopy. The sdcc generated hex file looks ok.
Maarten Brock wrote:
Peter,
Please include SDCC version and target for which you
compile. For mcs51 this should work I think.
Maarten
Hi,
Is it possible
Kevin,
My best guess is that your local variable definitions are VERY wrong - you
might want to try:
void putchar( char ch )
{
unsinged char *pScreen;
unsinged char *pX;
unsinged char *pY;
char x;
char y;
pScreen = (unsigned char *)video;
pX
is faster than
generic access.
Cheers,
Peter
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry
How do I do that? I've looked at all crtxxx.asm files and there doesn't
seem to be any const area defined there. Or is it there by different
name?
This is what is in the .map file now. And i'd like to move this
area lower than 0xC000.
Target is mcs51
Area Ad
hanks.
Peter
On Sat, Sep 19, 2009 at 9:06 PM, Maarten Brock wrote:
> Hello Peter,
>
> This method only works for z80 I think. For mcs51 the
> best option is to absolutely locate the CONST area while
> linking. Remember that the lowest address is used by the
> reset and interrupt
Phillip,
My primary interest is in the 'bog' standard Z80 and the Z180
(HD64180/HD647180).
I am also intrigued by the possibilities of the T80 but haven't gotten
there yet.
PeterT :->
On 8/31/11, Philipp Klaus Krause wrote:
> Dear users of sdcc,
>
> there are many Z80-based architectures out t
On 9/3/11, Philipp Klaus Krause wrote:
> And if yes, why?
>
> As far as I can see this just ensures that the upper 8 bits of the
> address bus are 0 whenever doing I/O, instead of undefined as in the
> default --portmode=z80. Is there a use case for this?
>
> Philipp
Phillipp,
I'm the loon that
to if/then in order to get rid of
this bug. This means faster assembly code, but I think this bug should
be identified (or at least communicated to other) and fixed.
Best regards,
Peter
sdcc --version
SDCC :
mcs51/z80/z180/r2k/r3ka/gbz80/tlcs90/ds390/pic16/pic14/TININative/ds400/hc08/s08
I'm trying to compile the following function for the PIC14 port:
void Writef( char *string) {
while(*string != 0) {
putchar(*string);
string++;
}
}
Note, no printf in the PIC14 port.
I call it as:
Writef('The quick brown fo
On Sunday 01 October 2006 11:53, Eric Rullens wrote:
> > Hmm, I see two problems here:
> > 1) You used ' instead of "
> > Writef("The quick brown fox jumps over the lazy dog.\0");
>
> 1b) And of course it is not necessary to explicitly add the \0.
Thank to you and also Philipp and Maarten. A rapi
Chaps,
I'm getting the following error from gpsim and the code does not work on a
PIC. My suspicion is that my variables have run out of file registers or
are attempting to overright ones they should not. I'm attemping to write
code for the PIC 16F877.
Any hints?
>From GPSIM, as it stops:
On Saturday 07 October 2006 16:13, Scott Dattalo wrote:
>
> I'm really pleased to see that you're using gpsim for your development!
>
Not as pleased as I am to have such a useful tool available. I rather like
the breadboard facility, allows you to see what is happening in real (or
realish) tim
On Monday 09 October 2006 09:34, Raphael Neider wrote:
> The problem might be the newly introduced -r option, which is now passed
> on by SDCC to gplink to circumvent problems with devices with all memory
> locations being in shared banks; probably gplink now allocates r0xB0 to
> the (shared) loca
On Friday 13 October 2006 12:48, Raphael Neider wrote:
> As this seems (to me) to be some kind of register allocation problem, I
> would require the complete code base to reproduce the bug.
> Alternatively (or as a preparation...), you might post/send me the
> generated .map/.lst files for inspect
On Sunday 15 October 2006 02:05, Raphael Neider wrote:
> Hi Pete,
>
> > > As this seems (to me) to be some kind of register allocation
> > > problem, I
>
> Actually, it was a BANKSEL problem in __uchar2fs, already reported in
> #1570934, and now (SDCC r4409) fixed.
> Please update your SDCC, recomp
On Sunday 15 October 2006 14:50, Raphael Neider wrote:
> For me, gpsim just runs forever; does it stop with some kind of message
> at your site? Or does it simply loop forever and when you interrupt it,
> you happen to find it execute in half_bit_delay?
>
It runs forever with no error message. H
On Sunday 15 October 2006 15:37, Peter Chant wrote:
> I'm just wondering if I ought to rewrite my main program loop to see if
> it goes away as I cannot see any error. However, although it appears to
> get stuck around the time the program enters my main program loop I
> cannot
Hi chaps,
I'm getting the following from sdcc when trying to compile some code, I
assume this is a message passed from gplink to sdcc:
error: no target memory available for section "code_autothermal"
I'm currently using a 16f877.
Anything I can do about this, apart from maybe going to a PIC wi
On Saturday 21 October 2006 22:04, Olgierd Eysymontt wrote:
> Hi Pete,
> I think your problem may be to have a big variable, in the compiler
> model you can't have variables that use more than 256 bytes and this
> counts for arrays, for example you can't have:
Nope, the largest is a buffer
On Sunday 22 October 2006 12:34, Raphael Neider wrote:
>Got another idea: Your project total might exceed the 8k assumed by
> gplink. So you might want to patch the linker script, adding two more
> CODEBANKs to fully use your device. IFF this turns out to be a bug in
>the linker scripts, you shoul
On Sunday 22 October 2006 12:22, Raphael Neider wrote:
> Probably gplink tries to map code sections to banks, which fails for
> your code. If you went and split yout file into smaller pieces, gplink
> could fill up the banks with code from different sections.
> !!! Beware, splitting your code will
Using the following (on PIC14):
var_u_char_8_b = (unsigned char) (var_int_16 / 8);
where:
var_u_char_8_b is unsigned char
var_int_16 is int
var_u_char_8_b always seems to be zero.
If I get rid of the /8 bit var_u_char_8_b appears (I assume) to hold the
least significant
On Wednesday 25 October 2006 00:58, Peter Chant wrote:
Hmm, found a funny with __data __at working with unsigned char but not with
int when looking at the following:
> Using the following (on PIC14):
>
> var_u_char_8_b = (unsigned char) (var_int_16 / 8);
>
> where:
>
On Saturday 28 October 2006 17:02, Raphael Neider wrote:
> sdcc -mpic14 -p16f877 bDIV.c
Weird, it gets stuck in gpsim about [] here:
BCF STATUS,5
BCF STATUS,6
MOVWF_var_u_char_8_b
; .line 14; "bDIV.c" return v
On Sunday 29 October 2006 23:54, Raphael Neider wrote:
> > Weird, it gets stuck in gpsim about [] here:
> >
> > BCF STATUS,5
> > BCF STATUS,6
> > MOVWF_var_u_char_8_b
> > ; .line 14; "bDIV.c"return var_u_char_8_b;
> > MOVF_var_u_char_8_b,W
> >
On Monday 30 October 2006 21:45, Peter Chant wrote:
> I will report back shortly on how I get on with the new installation.
> Of course slightly disturbed that reinstallation is usually the cop out
> when you don't know how to fix the problem...
OK, some success, some failure. D
On Tuesday 31 October 2006 22:10, Scott Dattalo wrote:
> So you mean that gpsim runs fine without the gui? If so I wonder if your
> gpsim problem is really a gtkextra problem:
>
Appears to, though to my shame I'm not really good at using it without the
gui. The breadboard view is the killer app
On Saturday 28 October 2006 17:02, Raphael Neider wrote:
> I cannot reproduce this behaviour (unless I fail to initialize
> var_int_16 to something != 0 that is...). I get beautiful results, gpsim
> loops happily in my catch-all loop in
As of tonight the code you posted fails (gpsim stops) on the
On Wednesday 01 November 2006 00:08, Scott Dattalo wrote:
> This has been fixed in more recent versions of gpsim. You said at one
> point you had a recent SVN version of gpsim. I'd suggest using that
> instead of the old 0.21.11.
Looks a lot better, but is this message important:
(gpsim:12227):
On Wednesday 01 November 2006 01:35, Scott Dattalo wrote:
>
> This is from the program memory window. I plan on removing this window and
> just making it a tab in the source browser. For now, just ignore the
> error, it causes no known side effects (other than that annoying message).
I already wa
> You use the GUI version of gpsim; however, you might try to build gpsim
> again with --disable-gui, install it or make sure you execute the
> correct binary, and use
> gpsim -s bDIV.cod
> run
> [Crtl]+[c] // after some time
> quit
>
Just by running it with the -i option I can see it gets to 0x0
On Saturday 16 December 2006 12:01, Raphael Neider wrote:
> The pic14 library is close to non-existent, there are nearly no built-in
> functions available from the SDCC/pic14 distribution alone.
> You may try to use library sources from the device/lib tree, but for
> your needs, you will just have
I need to have SDCC support the 18f2520
Is anyone else working on support for it that I could build off of?
Any howto's on adding support for a PIC?
Otherwise, expect patches... :)
--
http://petertodd.org
signature.asc
Description: Digital signature
-
On Sat, Jun 16, 2007 at 12:02:28AM +0200, Raphael Neider wrote:
> Hi Peter,
>
> > I need to have SDCC support the 18f2520
> >
> > Is anyone else working on support for it that I could build off of?
>
> Support for the 18f[24][45]20 series (18f4520 was already s
MAP, #0x02 ; select bank 2
lcall _led ;call _led in bank 2
pop _FMAP ;restore bank
ret
FMAP is the bank selecting SFR on CC2430
the modifications are made in lkmain.c(making a 3 pass link) and
lkrloc.c(generating
proxys and relocation lcall calls)
Any comments/suggestions.
Che
MAP, #0x02 ; select bank 2
lcall _led ;call _led in bank 2
pop _FMAP ;restore bank
ret
FMAP is the bank selecting SFR on CC2430
the modifications are made in lkmain.c(making a 3 pass link) and
lkrloc.c(generating proxys and relocation lcall calls)
Any comments/suggestions.
Che
this "template" and replaces template symbols once for
every proxy needed.
The whole proxy code is in the template provided by the programmer( so you
can switch the banks even with the serial port if you want to )
-
Peter
--
On Sep 3, 2007, at 12:30 PM, Maarten Brock wrot
Hi,
How can I get a number of parameters a reentrant function gets from stack in
gen.c function genFunction()
I need for the codebanking patch.
Thanks,
Peter
--
http://www.pkuhar.com/
-
This SF.net email is sponsored by
You should use winarm ( avr-gcc) it's much better.
http://winavr.sourceforge.net/
Go to http://www.avrfreaks.net/ for more info.
Peter
On 9/12/07, Denny Putra Private <[EMAIL PROTECTED]> wrote:
> Guy, I have a problem using SDCC to AVR Microcontroller such as
> ATMega8535, Can
sorry, i meant winavr ( not winarm )
On 9/13/07, Peter Kuhar <[EMAIL PROTECTED]> wrote:
> You should use winarm ( avr-gcc) it's much better.
> http://winavr.sourceforge.net/
> Go to http://www.avrfreaks.net/ for more info.
> Peter
>
> On 9/12/07, Denny Putra Priv
.area GSINIT (CODE)
On 9/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Philipp Klaus Krause wrote:
>
> >Place another .area _CODE before the .area _GSINIT?
> >
> OK, I tried that, but it didn't make any difference, _GSINIT is still
> in RAM.
>
> But thanks for trying!
>
> Randy
>
>
>
>
Is this a global variable???
On 9/30/07, David Lucena <[EMAIL PROTECTED]> wrote:
>
> I am using SDCC to program a z80 machine. When I create this code:
>
> unsigned char test = 0;
>
> It is assembled as follows:
>
> ld iy,#_test
> ld 0(iy),#0x00
>
> But I would like that
le and run the nanostack from sensinode.
http://www.sensinode.com/top/newsdesk_info.php?newsdesk_id=23
Would this be possible to include in the main branch?
Thanks,
Peter
On 9/4/07, Peter Kuhar <[EMAIL PROTECTED]> wrote:
> 1.) parameter passing on stack and stack misalignment
> I'
le and run the nanostack from sensinode.
http://www.sensinode.com/top/newsdesk_info.php?newsdesk_id=23
Would this be possible to include in the main branch?
Thanks,
Peter
On 9/4/07, Peter Kuhar <[EMAIL PROTECTED]> wrote:
> 1.) parameter passing on stack and stack misalignment
> I'
de is tested and works ok as far as I know.
I've be able to compile and run the nanostack from sensinode.
http://www.sensinode.com/top/newsdesk_info.php?newsdesk_id=23
Would this be possible to include in the main branch?
Tha
in
which bank to put which file.
I'll post that changes on Sunday.
Regards,
Peter
On 10/18/07, Frieder Ferlemann <[EMAIL PROTECTED]> wrote:
> Hi Peter,
>
> Peter Kuhar schrieb:
> > This is a follow up from the previous e-mails about code banking.
> > I've
Hi,
Hi although it's probably not the thing that is cosing you this
problems, but XRAM starts at location 0x on your device.
--
Peter
On Nov 10, 2007 2:58 AM, Eric Jonas <[EMAIL PROTECTED]> wrote:
> Okay, I've reduced this to the smallest possible example that
It would be better to use ++(&descromarea) or &(&descromarea)[1] if
this was you intention.
anyway, you should avoid this kind of hacking, why dont you just
directly access the structure?
--
Peter
-
This SF.net
ethodology described.
> >
> > If I try it with just "sdcc pic18f2455.c" - it does not work for me.
> >
> > Vaclav
> >
> If you work with windows, you should install cygwin (http://www.cygwin.com
> )
> wh
any case you'll need cygwin environment to compile sdcc on windows, mingw
is just a way to compile/link it, to work without cygwin.
--
Peter
On Dec 6, 2007 9:42 AM, soliton <[EMAIL PROTECTED]> wrote:
> I am using mingw to compile it under Windows. You can find it here:
> htt
can modify it to exclude support for non-pic
> > processors )
> >
> > It should get you running, when everything is compiled ( before make
> install
> > ) go to lib directory and compile the libs for your pic.
> > In any case you'll need cygwin environment to compile
All of this works. The type casting (unsigned char) isn't needed but it
doesn't hurt either
On Jan 31, 2008 11:31 AM, Félix Buhlmann <[EMAIL PROTECTED]> wrote:
> Hello,
>
>
>
> I see in the SDCC manual that to obtain the higher order byte, I must use
>
>
>
> unsigned int gint;
>
> unsigned char
Hi,
Afaik ZStack downloaded from TI site does not include full source code. The
other issue is that sdcc main branch does not fully support code banking so
only 64k of the flash is available. Which is certanlly not enought for the
whole zstack.
The version with code banking support is available h
(I am happy to be corrected), the SDCC builds are
limited to the normal Z80 64K linear address space. This is not to say
that you cannot implement your own methods to make it work for you - it
will simply take more work.
Peter Townson
From: [EMAIL PROTECTED]
[m
particular interest was in the HD647180 - the embedded
microcontroller version of the HD64180/Z180. He spoke at the time of
doing a Z180 specific port of SDCC. He may have some help to offer...
Peter Townson
##
CONFIDENT
will likely take a LONG time...
So, it certainly aint dead as far as I'm concerned.
Peter Townson :->
##
CONFIDENTIALITY NOTE: Please consider our environment before printing this
email.This email and any attachm
Guys,
On the general topic of Z80 development/support:
Is anyone out there targeting the eZ80 with SDCC ?
Peter Townson
##
CONFIDENTIALITY NOTE: Please consider our environment before printing this
email.This email and
use Windows here.
I don't suppose it would run under X/WINE ?? (Linux IS a wonderful thing
- most of the time :->)
Peter Townson
##
CONFIDENTIALITY NOTE: Please consider our environment before printing this
helps.
Pete
--
Peter Chant
http://www.petezilla.co.uk
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your
ng.
CCP1CON = 0;
Unfortunately it did not seem to help.
>
> I use the following code to enable both pwm channels on my 18f2XXX devices:
Thanks,
maybe I'll have to look to see if I have any 18f2 devices and see if I can
get your routine to work.
;
; BCF PIR1, TMR2IF
_endasm;
}
--
Peter Chant
http://www.petezilla.co.uk
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healt
t running it against gpsim at the moment. Not built the board yet. Would
be a good plan to do so just to check the PWM bit. Next thing to do is to
get a to d working, however, I have had that working already on a 16f877, so
I hopefully am ahead of the game a little there.
Than
e to the limits, it is time to consider different hardware.
Is there much of a jump coding wise? I've been using 16F various as I started
with those. Just curious.
Pete
--
Peter Chant
http://www.petezilla.co.uk
-
On Monday 28 July 2008, George M. Gallant wrote:
> Peter,
>
> The coding is similar. The RAM is organized in banks of 256 bytes, the
> stack is 31 entries deep, three index registers with 4 addressing modes,
> the stack is usable for data storage, and a 10MHz oscillator can be X4,
Richard,
Glad to hear that you solved your problem.
I was literally composing a response for you when your message arrived a
few minutes ago - good timing. (I'm no expert but no one else seemed to
be jumping in so I was going to have a go based on faded memories of a
much earlier project :->)
C
that the addressable
(static) data be in the same logical address space as the code; but I
don't
know really.
I must confess, I don't really understand what I've done; but it does
work.
I would be happy to have any further light shed upon this...?
On Thursday 04 September
ode generation to need to know that
there isn't a P2 or XPAGE sfr present which may mean that I have missed some
higher level setting.
Peter Van Epp
--
The Planet: dedicated and managed hosting, cloud storag
ization that make me think
thats where my problem lies.
Peter Van Epp
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Cho
return from main will lock up
sjmp .
;----
...
Peter Van Epp
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing an
On Thu, Feb 11, 2010 at 08:22:57PM +0100, Brandon Fosdick wrote:
>
> On Feb 11, 2010, at 20:04 , Peter Van Epp wrote:
>
> > On Thu, Feb 11, 2010 at 12:27:04PM +0100, Brandon Fosdick wrote:
> >> Well, it looks like I spoke too soon.
> >>
> >> SDCC is
While I'm here attached is a modified copy of the w7100.h file in
SDCC. I sent a copy to the author some time back but haven't heard anything.
I don't quarantee this is entirely correct, but it at least builds and runs
on the W7100.
n is refused by the
stack-auto compiled code). I'm just about to add printf statements to try and
figure out whats wrong (and therefore a fix) but thought I'd inquire in case
I'm just missing some needed step in this process.
Peter Van Epp
Maarten:
Thanks for the reply!
On Tue, Mar 16, 2010 at 09:18:40AM +0100, Maarten Brock wrote:
> Peter,
>
> > I'm compiling stuff for the Wiznet W7100 8051 varient and hit the
> > dreaded "can't allocate DSEG" error. A search through the forum i
On Tue, Mar 16, 2010 at 11:23:35PM +0100, Maarten Brock wrote:
> Peter,
>
> > The overflow in DSEG is all
> > sloc variables and I don't know how to move those (thats what stack-auto
> > is supposed to do I think?) out of the internal ram.
>
> Yes, stack-aut
On Wed, Mar 17, 2010 at 10:29:37AM +0100, Maarten Brock wrote:
> Peter,
>
> >> Yes, stack-auto puts the sloc's on stack too. And you
> >> cannot move slocs to any other memory, because then SDCC
> >> would need sloc's to access those sloc's.
& *s >= '0' && *s <= '9') {
rv = (rv * 10) + (*s - '0');
s++;
}
return (rv);
}
/*---*/
Peter Van Epp
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
-opts.c:
SDCPP synchronized with GCC CPP release version 4.5.0
Peter Van Epp
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net
701 ;function lcd_set_text
702 ; ----
...
Peter Van Epp
--
___
Sdcc-user mailing li
On Sun, May 02, 2010 at 10:22:12AM +0200, Maarten Brock wrote:
> Peter,
>
> > Can someone suggest how to avoid the allocation in DSEG (which is
> > overfull) in the following code snippet?
> >
> > ...
> > void lcd_puts (char xdata *str)
> > {
>
On Tue, May 04, 2010 at 10:02:38AM +0200, Borut Razem wrote:
> Now it is fixed.
> Sorry that it took so long!
>
> Borut
>
Not a problem :-), I thought you may already know it was broken but
pointed it out just in case you didn
char demo4[20];
strcpy(demo1,"+--+");
strcpy(demo2,"| Ceng 336 |");
strcpy(demo3,"| SDCC LCD demo|");
strcpy(demo4,"+--+");
> lcdGoto(START_OF_LINE1);
> for(i = 0; demo1[i]; i++)
> lcdWrite(demo1[i]);
Peter Van Epp
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
ay.asm"
*** the call to the linker starts here ***
"c:/program files/sdcc"/bin/sdcc -V main.rel wiz.rel wizmemcpy.rel socket.rel l
cd.rel sio.rel console.rel delay.rel
+ C:\PROGRA~1\sdcc\bin\sdld.exe -nf "main.lnk"
"c
dptr with unfortunate results.
So is this a compiler bug that I should be reporting or bad C code
(neither the vendor's programmers or me are particularly good C programmers
and I think I may be
er in the
attached tcp engine not the pointer which is actually the lower 16 bits of
the 24 bit pointer that gets to the tcp engine.
Peter Van Epp
--
___
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
in the
startup code that P2 is set to 0 and nothing thereafter seems to change it
so I'm assuming that the compiler expects to things stored by movx @r0
to be in the first 256 bytes of XDATA and thus I need to make sure that
P2 is set to 0 most of the time.
Peter Vs
1 - 100 of 121 matches
Mail list logo