Re: want an sdcc howto?
Martyn Welch <[email protected]>
| Newsgroups | gmane.comp.hardware.microcontrollers.gnupic |
|---|---|
| Organization | Lancaster University |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi David, I see Byron has already pointed to my page :-) http://ubicomp.lancs.ac.uk/~martyn/sdcc_linux/ I've just revisited it and realised I had neglected to include the serial comms examples I had! I have added them now, though haven't provided much in the way of an explaination of how they work. There is an example which uses a simple putchar function I wrote and an example showing it working with printf_tiny. Good luck, Martyn - ------ Original message ------ On Friday 15 Jul 2005 01:58, David McNab wrote: > Hi, > > My preference for high-level langages puts me at odds with much of this > list's membership, but there are those who feel the same as I do. > > The problem with high level languages on PIC micros has been the lack of > a usable, free/opensource implementation. > > sdcc has suffered a bad rap because it's very newbie-unfriendly to set > up and get going. Also, its binary packaging has been botched, at least > on Debian. > > But with a bit of doco, this problem can go away, to the point where > sdcc's accessibility is on a par with that of the commercial compilers. > > I'm willing to write an 'sdcc on PIC Howto', which takes the user step > by easy step through: > > - downloading the source tarball > - configuring the build > - building the core toolchain and extras > - installing the toolchain, libs, headers and support files > - writing a 'hello, world' LED blinker program in C > - turning that into a valid and working .hex binary (including > a fix for the broken crt0 module) > - setting up and using usart-based stdio (so 'printf()' works) > - practicalities of C hacking on PIC > > Question is - is any interested in actually seeing/using such a > document? I'd rather get some votes of support before launching in and > expending several hours on something that might not be used. > > I'd really like to see more interest in sdcc on this list, because it's > the only viable free/opensource high-level language compiler that spans > both 16F and 18F, and deserves a place as the 'reference' high level > language for PIC. > > Thoughts? - -- Martyn Welch ([email protected]) PGP Key : http://ubicomp.lancs.ac.uk/~martyn/pgpkey/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFC12HGQPzYXciChNcRAsUZAJ4stS/ocbZfJ64NrJeV6jUqhHdokQCfRZ5c 9JZ80yHMYlpp1N+Fh9KZ6M0= =fe9u -----END PGP SIGNATURE-----