While I agree that I’d also like to see documentation for adc, i2c and serial communications etc, these are applications specific to individual micro-processors and related peripherals – they are NOT generic and most certainly NOT part of the documentation for the compiler – any compiler.  Documenting such applications requires far more scope than is likely to be found as an appendix in a compiler manual – there are numerous books on the subject, not to mention application notes from device manufacturers.  Each platform/micro has its own way of doing things, and therefore requires separate documentation detailing methodologies and approaches.


Such examples of applications are able to be found (‘google’ is your friend) and some of such are actually implemented using SDCC.  In fact there are a number of sites that specialize in SDCC related projects.


What you really want to have documented is efficient methods of manipulating memory/port-mapped devices, twiddling bits, writing ISR’s, banking memory etc for each of the support micros.  Armed with such information it is simpler to make use of available resources (app notes, projects etc) and translate/port them into SDCC on your chosen target.


The last time I had a good look the existing documentation was relatively detailed in some areas (lots on 8051 related stuff), but lacking in detail on other targets (although the PIC docos seem to be improving).  Please note: I am no complaining, as open source goes the documentation isn’t bad, and if I wasn’t a lazy sod I could make my own additions… :->


I offer no solutions, merely point out that selecting a high level language like C (SDCC) does not remove the need to grasp the fundamentals of the components involved, it just makes the code a bit more readable that the assembly (at least I hope so), and hopefully a little more portable.


Actually upon reflection I do have a suggestion:

Maybe there should be a challenge issued (all in fun) to the subscribers of this list to post ‘reference’ examples – complete with schematics if external devices are involved – to illustrate what has worked for them.  This list is usually about what doesn’t work and getting help to fix it – which is great – but rarely documents the final corrections/solutions.  Maybe we should take the time to document 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 []
Sent: Thursday, 5 March 2009 9:28 PM
Subject: Re: [Sdcc-user] May I offer a suggestion about the documentation?


I would like very much too. I don't know how to use sdcc, like adc, i2c, serial communication etc, because there isn't documentation explaining about that. It also can add on this wiki examples for how to use the microcontroler.
Once I tried to use the sdcc, but could not. I didn't get information on how to manipulate the pin, the ADC, the comparator so.

On Wed, Mar 4, 2009 at 9:20 PM, candida lopez rodriguez <> wrote:

Other open source projects allows the user to update the documentation (adding
comments) can this project move the documentation to a Wiki so users can
update/add comments


Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Sdcc-user mailing list

Lucas A. Tanure Alves

CONFIDENTIALITY NOTE: Please consider our environment before printing this email.This email and any attachments are confidential and may be subject to copyright, legal or some other professional privilege. They are intended solely for the attention and use of the named addressee(s). They may only be copied, distributed or disclosed with the consent of the copyright owner. If you have received this email by mistake or by breach of the confidentiality clause, please notify the sender immediately by return email and delete or destroy all copies of the email. Any confidentiality, privilege or copyright is not waived or lost because this email has been sent to you by mistake. ---------------------------------------------------------------------