Dear Maarten:

Thanx for the welcome. 

In addition to the register definition header files I am also going to write libraries that implement some but not all of the functionality of the nRF series. I am facing a dilemma when I am writing the header file. I am including the basic 8052 core in my header file for nRF24LU1. Now some of the addresses defined in the 8051 and 8052 core are defined differently for the nRF series. e.g.  0xA0 is the address of P1 in 8051 but in nRF24LU1 the  address is for USBCON register. Now what do I do so that when I am inheriting the definitions from 8051.h, the new addresses defined in nRF header file override the 8051.h definitions. The other obvious solution is to make an independent header file for nRF24LU1 but I would like to know if it can be done in this way. If yes, how can it be done?

Another question is what is the size of int defined by sdcc compiler? 2bytes or 4 bytes. Is there any way to redefine it as 1byte (short int)??!! or do we have use char instead?

Awaiting your reply,

Koustubh Sinkar
कौस्तुभ सिनकर


On 11 October 2010 23:45, <sdcc-devel-request@lists.sourceforge.net> wrote:
Send sdcc-devel mailing list submissions to
       sdcc-devel@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.sourceforge.net/lists/listinfo/sdcc-devel
or, via email, send a message with subject or body 'help' to
       sdcc-devel-request@lists.sourceforge.net

You can reach the person managing the list at
       sdcc-devel-owner@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sdcc-devel digest..."


Today's Topics:

  1. [ sdcc-Bugs-3084967 ] Missing processor header files
     (SourceForge.net)
  2. newbie-developer (Koustubh Sinkar)
  3. Re: newbie-developer (Maarten Brock)
  4. Re: sdcc 3.0.0 release (S?bastien Lorquet)
  5. Re: [Sdcc-user] SDCC 3.0.0 Release Candidate 1 (Claude Sylvain)
  6. Re: sdcc 3.0.0 release (Borut Razem)


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Oct 2010 05:17:07 +0000
From: "SourceForge.net" <noreply@sourceforge.net>
Subject: [sdcc-devel] [ sdcc-Bugs-3084967 ] Missing processor header
       files
To: noreply@sourceforge.net
Message-ID: <E1P5Al1-00077x-6L@sfs-web-3.v29.ch3.sourceforge.com>
Content-Type: text/plain; charset="UTF-8"

Bugs item #3084967, was opened at 2010-10-11 01:27
Message generated for change (Comment added) made by borutr
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3084967&group_id=599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pic16 target
>Group: fixed
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Christopher Head (hawk777)
>Assigned to: Borut Ra?em (borutr)
Summary: Missing processor header files

Initial Comment:
In attempting to check the outcome of bug <https://sourceforge.net/tracker/?func=detail&aid=3037428&group_id=599&atid=100599>, I decided to install a recent snapshot build (namely sdcc-snapshot-amd64-unknown-linux2.5-20101010-6017.tar.bz2). When I compile a simple test program, I get the message "/usr/local/bin/../share/sdcc/include/pic16/pic18fregs.h:234:26: error: pic18f4550.h: No such file or directory". In fact, looking in the /usr/local/share/sdcc/include/pic16 directory, I see that *none* of the processor header files were included in the snapshot! The doc/INSTALL.txt file suggests all I should have done was copy the tarball files into /usr/local (which is what I did); if that's true, then the tarball would have to include all those headers?but it doesn't.

----------------------------------------------------------------------

>Comment By: Borut Ra?em (borutr)
Date: 2010-10-11 07:17

Message:
Pic device definition header and library files are now in the
non-free/include and non-free/lib directories. Use --use-non-free sdcc
commad line option.

Borut

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3084967&group_id=599



------------------------------

Message: 2
Date: Mon, 11 Oct 2010 16:06:20 +0530
From: Koustubh Sinkar <ksinkar@gmail.com>
Subject: [sdcc-devel] newbie-developer
To: sdcc-devel@lists.sourceforge.net
Message-ID:
       <AANLkTi=DoTEdzFQD-86o3SNxo6BEd_O6o4YkFem1hKfz@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I want to contribute to the sdcc project. I have downloaded the sdcc source
files by svn. There are so many branches and trunks in the downloaded folder
that I do not know where to add my changes and how to submit them. I am
working on the nRF24LU microcontroller (x51 based) family and would like to
contribute an SDK that I am developing right now. Please guide me. Also
there are so many branches. To which branch should I contribute my code to?
SHould I contribute to the branch or to the trunk.

This is my first opensource project, so please answer my irritating newbie
questions in detail.

Thanx in advance.

Regards,
Koustubh Sinkar
??????? ?????
??????? ?????
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Mon, 11 Oct 2010 15:26:19 +0200 (CEST)
From: "Maarten Brock" <sourceforge.brock@dse.nl>
Subject: Re: [sdcc-devel] newbie-developer
To: "Development chatter about sdcc"
       <sdcc-devel@lists.sourceforge.net>
Message-ID: <40876.212.129.198.86.1286803579.squirrel@www.dse.nl>
Content-Type: text/plain;charset=iso-8859-1

Hello Koustubh,

Welcome.

I doubt you will need to update much to the compiler. The basic x51 is
already covered. The first thing you need is a header file containing the
SFR's of this mcu (in SDCC format!). Please make use of the macros in
compiler.h. For an example see C8051F360.h. You can submit a patch in the
tracker to get it included in the distribution.

Next, I think you need a modified crtxinit.asm as it uses MOVX @Ri to
initialize global variables, yet this mcu has no P2 nor _XPAGE equivalent.
Luckily crtxinit.asm already contains an alternative which uses dual dptr
that only needs to be enabled.

Currently SDCC does not use dual datapointers during code generation, but
generated code will work on this mcu.

If you want you could rewrite some arithmetic routines to use the MDU, but
it will work without as well.

All work is done in the trunk. The branches are mostly tags for releases.

Greetings,
Maarten

> I want to contribute to the sdcc project. I have downloaded the sdcc
> source files by svn. There are so many branches and trunks in the
> downloaded folder that I do not know where to add my changes and how to
> submit them. I am working on the nRF24LU microcontroller (x51 based)
> family and would like to contribute an SDK that I am developing right
> now. Please guide me. Also there are so many branches. To which branch
> should I contribute my code to? SHould I contribute to the branch or to
> the trunk.
>
> This is my first opensource project, so please answer my irritating
> newbie questions in detail.
>
> Thanx in advance.
>
> Regards,
> Koustubh Sinkar




------------------------------

Message: 4
Date: Mon, 11 Oct 2010 18:12:35 +0200
From: S?bastien Lorquet <squalyl@gmail.com>
Subject: Re: [sdcc-devel] sdcc 3.0.0 release
To: Development chatter about sdcc <sdcc-devel@lists.sourceforge.net>
Message-ID:
       <AANLkTinig4aP412frKnoaFq7-C7BtikBgXQue2QZbAOp@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

No regression for me on winxp, using mplab and mplab-sdcc. Just had to add
the --use-non-free for PIC libraries.

about the doc:
is the pic port still considered "in development"?
the -mavr option is still documented. Is that port still included?
there is a right-aligned extra "!" at the end of page 39. and also at the
first paragraph of "tips" page 82
at end of page 76 there is: on a single channel oscilloscope you could f.e.
if that means "for example", then I think the proper abbreviation is "e.g."

Thanks.
Sebastien

On Sun, Oct 10, 2010 at 5:24 PM, Borut Razem <borut.razem@siol.net> wrote:

> Please review the documentation.
>
> Raphael, please review / update the table of supported pic devices in
> sdccman.lyx
>
> Borut
>
>
> On 10/10/2010 05:15 PM, Borut Razem wrote:
> > Dear sdcc developers,
> >
> > please consider the svn main branch as frozen, which means that only
> > fixes for high severity bugs (after an agreement on this mailing list)
> > and changes in the documentation can be committed.
> >
> > The SDCC 3.0.0 release schedule is published at
> > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release
> >
> >
> > Borut
> >
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> sdcc-devel mailing list
> sdcc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 5
Date: Mon, 11 Oct 2010 12:23:02 -0400
From: Claude Sylvain <csylvain@electro-technica.com>
Subject: Re: [sdcc-devel] [Sdcc-user] SDCC 3.0.0 Release Candidate 1
To: sdcc-devel@lists.sourceforge.net
Message-ID: <BLU0-SMTP101B2681AEBC8BC00684CC0DD530@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed

Hello Borut,


- Just to says that sdcc-20101011-6022 built correctly on the following
  platform:
       - Cygwin 1.7.x on Windows XP Professionnal.


- However, when installing ("make install"), the following (non-fatal)
  errors are displayed:

                                     +++
...

make[5]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib/pic'
cp: cannot stat `pic/bin/*.*': No such file or directory
make[4]: [port-specific-objects-pic14] Error 1 (ignored)
make[4]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib'

...

source='delay/delay100ktcy.S' object='delay100ktcy.o' libtool=no \
        DEPDIR=.deps depmode=none /bin/sh ../depcomp \
        ':' -DHAVE_CONFIG_H -I. -I..    -I../../../include/pic16 -I../../../non-
free/include/pic16 -I. -p18f452 -c -o delay100ktcy.o `test -f 'delay/delay100ktc
y.S' || echo './'`delay/delay100ktcy.S
../depcomp: line 611: exec: :: not found
make[7]: *** [delay100ktcy.o] Error 127
make[7]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib/pic16/libc'
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib/pic16'
make[5]: *** [all] Error 2
make[5]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib/pic16'
cp: cannot stat `pic16/*/lib*.a': No such file or directory
cp: cannot stat `pic16/*/crt0*.o': No such file or directory
make[4]: [port-specific-objects-pic16] Error 1 (ignored)
make[4]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/lib'

...

make[5]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/non-free/lib/pic'
cp: cannot stat `pic/bin/*.*': No such file or directory
make[4]: [port-specific-objects-pic14] Error 1 (ignored)
make[4]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/non-free/lib'
make clean_intermediate-pic14

...

make[5]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/non-free/lib/pic16'
cp: cannot stat `pic16/*/lib*.a': No such file or directory
make[4]: [port-specific-objects-pic16] Error 1 (ignored)
make[4]: Leaving directory `/home/claude/work/software/pc/SDCC/sdcc-20101011-602
2/device/non-free/lib'

...
                                     +++


Regards,
Claude




------------------------------

Message: 6
Date: Mon, 11 Oct 2010 20:15:46 +0200
From: Borut Razem <borut.razem@siol.net>
Subject: Re: [sdcc-devel] sdcc 3.0.0 release
To: Development chatter about sdcc <sdcc-devel@lists.sourceforge.net>
Message-ID: <4CB35452.6080301@siol.net>
Content-Type: text/plain; charset="utf-8"

On 10/11/2010 06:12 PM, S?bastien Lorquet wrote:
> Hi,
>
> No regression for me on winxp, using mplab and mplab-sdcc. Just had to
> add the --use-non-free for PIC libraries.
>

Great!

> about the doc:
> is the pic port still considered "in development"?

On my opinion it will be "in development" until it passes the regression
tests.

> the -mavr option is still documented. Is that port still included?
> there is a right-aligned extra "!" at the end of page 39. and also at
> the first paragraph of "tips" page 82
> at end of page 76 there is: on a single channel oscilloscope you could
> f.e.
> if that means "for example", then I think the proper abbreviation is
> "e.g."
>

Fixed.

Thanks,
Borut


> Thanks.
> Sebastien
>
> On Sun, Oct 10, 2010 at 5:24 PM, Borut Razem <borut.razem@siol.net
> <mailto:borut.razem@siol.net>> wrote:
>
>     Please review the documentation.
>
>     Raphael, please review / update the table of supported pic devices in
>     sdccman.lyx
>
>     Borut
>
>
>     On 10/10/2010 05:15 PM, Borut Razem wrote:
>     > Dear sdcc developers,
>     >
>     > please consider the svn main branch as frozen, which means that only
>     > fixes for high severity bugs (after an agreement on this mailing
>     list)
>     > and changes in the documentation can be committed.
>     >
>     > The SDCC 3.0.0 release schedule is published at
>     > http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release
>     >
>     >
>     > Borut
>     >
>
>     ------------------------------------------------------------------------------
>     Beautiful is writing same markup. Internet Explorer 9 supports
>     standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>     Spend less time writing and  rewriting code and more time creating
>     great
>     experiences on the web. Be a part of the beta today.
>     http://p.sf.net/sfu/beautyoftheweb
>     _______________________________________________
>     sdcc-devel mailing list
>     sdcc-devel@lists.sourceforge.net
>     <mailto:sdcc-devel@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
>
>
> _______________________________________________
> sdcc-devel mailing list
> sdcc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb

------------------------------

_______________________________________________
sdcc-devel mailing list
sdcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-devel


End of sdcc-devel Digest, Vol 53, Issue 6
*****************************************