m (Docs/Beats/Embedded moved to Documentation Embedded Development Beat: Natural language name change.)
|Line 1:||Line 1:|
==== Embedded Development ====
==== Embedded Development ====
Revision as of 01:35, 29 January 2009
Keep this for F10 update
Fedora 10 includes a range of packages to support development of embedded applications on various targets. There is broad support for the AVR and related parts as well as for the Microchip PIC. In addition, there are packages to support development on older, less popular parts such as the Z80, 8051, and others. For a more complete description see Packages for embedded development on the wiki .
This release includes version 2.18 of avr-binutils. In addition to a large number of bugfixes, this release includes a new tool,
windmc, to provide a Windows-compatible message compiler. Details of these changes can be found at http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/binutils/NEWS?rev=1.71&content-type=text/plain&cvsroot=src&only_with_tag=binutils-2_18.
Version 0.4.6 of dfu-programmer is included in Fedora 10. 4k bootloaders are now supported and eeprom-flash and eeprom-dump are now supported. Release information as well as a forum specific to this version can be found at http://dfu-programmer.sourceforge.net/
gputils has been updated to version 0.13.6 which includes support for many more PIC18 processors as well as support for Microchip's new COFF file format. Find details at http://gputils.sourceforge.net/.
Fedora 10 includes version 3.5.10 of the popular IDE piklab. This version now supports the Microchip ICD2 and PICkit in-circuit debuggers, as well as a number of other improvements. Piklab now supports the following toolchains; gputils, C30 and C18, PICC, JAL, BoostC, CCS, MPC and CC5X. Many of the toolchains use Windows executables via Wine. See http://piklab.sourceforge.net/ for complete details.
Note that the executable names for sdcc have changed (see below). Since piklab does not provide for configuring executable names, but does provide for configuring paths, the piklab/sdcc user should copy files beginning with sdcc- from /usr/bin to /usr/local/bin and adjust the paths in piklab until this issue is resolved.
Microchip has a tendency to have a lot of spaces in their default installation directories. Getting those paths configured in piklab can be quite confusing, so the dual-boot user may choose to copy files to the /usr/local tree rather than simply mounting the Windows drive and directly referencing the files in the Microchip installation. This affects not only executables, but linker scripts, headers and libraries.
Version 2.8.0 of the Small Device C Compiler is included in Fedora 10. This version offers a number of improvements to the version in Fedora 9. Some of these changes will result in changes to source code, so users should review the SDCC manual carefully for their target. In addition, due to some conflicts, all the executable names have been prefixed with
sdcc-, which will require changes to makefiles. See the SDCC page at http://sdcc.sourceforge.net/ for complete details.