| Jan Waclawek 03/06/10 03:16 Read: 231 times Bratislava Slovakia |
#173900 - documentation Responding to: Richard Erlacher's previous message |
Documentation of SDCC is basically a single file, sdccman.pdf, from the zipfile I mentioned above; the same can be seen online at http://sdcc.sourceforge.net/doc/sdccman.html/ (linked to directly from the SDCC homepage).
While chapter 1 is some boring intro and chapter 2 is indeed the configuration/installation stuff (boring enough, too :-) ), from chapter 3 on it is the "real" user manual you might be looking for (with more boring stuff in chapters 8 and 9). Richard said:
[...] not one that clearly tells you how to use SDCC in order to produce useable output, simulate it, and install it in your target environment without clobbering you with countless configuration options. Okay, let's try to come up with some remedy. I think what I've written in my previous post is a concise enough version of "how to install" (assuming the typical user is Win-oriented - anyway, the Linux folks appear to be used to more complicated ways of doing things :-) ). So now for the producing useable output etc. Chapter 3, first verse of sdcc manual said:
For single source file 8051 projects the process is very simple. Compile your programs with the following command sdcc sourcefile.c. This will compile, assemble and link your source file. The output hexfile is called sourcefile.ihx - the not-that-standard .ihx extension appears to be one of the major gotchas of SDCC as far as new users are concerned. Simulation might be a problem. The simulator which comes with SDCC is NOT intended for "human" use (it is used mainly for automated "quality testing" by the development team). There appears to be a convoluted way how to plug it in into a human-usable GUI, called ddd, but that's available only under Linux. Jens Altman's free '51 simulator, jsim claims to support SDCC, but I could not get it working - I did not try very hard, though, I am not really interested in simulations. So, as far as simulation is concerned, you are left with assembler-level simulation in your favourite '51 simulator (jsim is capable to do that, at least), as if you would program in assembler. Now for downloading to target and running, that's entirely dependent on your target of course... SiLabs, Ramtron Versa, and maybe also others, provide development environment where you can debug SDCC-based applications comfortably, source-level. Note that these are chipmaker-provided tools, so they won't work on *any* '51 - there's a lot of reasons why. Did this help to clear up the picture a bit? Jan |
| Topic | Author | Date |
| SDCC download | Erik Malund | 03/05/10 11:53 |
| Here you go... | Robert Revens | 03/05/10 12:13 |
| newest | Jan Waclawek | 03/05/10 12:30 |
| Has any effort gone into documentation? | Richard Erlacher | 03/05/10 18:20 |
| documentation | Jan Waclawek | 03/06/10 03:16 |
| Just to add... | Robert Revens | 03/06/10 04:02 |
| more howto-s | Jan Waclawek | 03/06/10 05:13 |
| the first 'oddity' is ... | Erik Malund | 03/06/10 06:46 |
| I think you dreamt that one eric | Jez Smith | 03/06/10 07:27 |
| No - it's a well-known Gotcha! in SDCC! | Andy Neil | 03/06/10 11:46 |
| Reference: ISRs (or prototypes) must be in same file as main | Andy Neil | 03/07/10 01:04 |
| linking | Jan Waclawek | 03/06/10 14:36 |
| I see it not correct | Erik Malund | 03/06/10 14:51 |
| I don't understand | Jan Waclawek | 03/06/10 15:04 |
| what is it you do not understand? | Erik Malund | 03/07/10 07:11 |
| Does it not recognise... | Andy Neil | 03/07/10 07:25 |
| Surely not... | Robert Revens | 03/07/10 08:42 |
| "magic" | Jan Waclawek | 03/07/10 10:44 |
| That's not the fault of 'C'!! | Andy Neil | 03/07/10 13:14 |
| highly unusal, but | Erik Malund | 03/07/10 18:42 |
| Try java etc | Oliver Sedlacek | 03/08/10 07:54 |
| I now see why is this confusing | Jan Waclawek | 03/07/10 10:27 |
| emulation? | Andy Peters | 03/11/10 15:53 |
| Source-level debug | Robert Revens | 03/11/10 16:15 |
| symbol information | Maarten Brock | 03/12/10 04:05 |
| re: symbol information | Andy Peters | 03/15/10 18:40 |
| hex-file download? | Maarten Brock | 03/16/10 05:46 |
hex vs omf | Andy Peters | 03/16/10 12:08 |
| Keil proprietary stuff? | Andy Neil | 03/12/10 05:01 |
| extended omf51 | Juergen Christoph | 03/12/10 07:11 |
| omf51 vs cdb | Jan Waclawek | 03/15/10 16:48 |
| proprietary file format? | James Hinnant | 03/15/10 01:22 |
| I don't see why not | Andy Neil | 03/15/10 01:33 |
| So, what do *you* mean by, "proprietary" ? | Andy Neil | 03/16/10 02:15 |
| AutoCAD | Per Westermark | 03/16/10 03:15 |
| Yes | Per Westermark | 03/15/10 01:37 |
| patentable vs proprietary | James Hinnant | 03/15/10 23:39 |
| Proprietary is a questin of ownership, not protection | Per Westermark | 03/16/10 01:06 |
| bouncing email | Maarten Brock | 03/07/10 14:38 |



