I have eventually got round to creating a proper set of instructions that will show you how to set up a very professional development system for ColdFire, with a sample application to get you started.
The instructions are for a Windows XP hosted system, but if you are Linux friendly you may be able to translate the instructions. All of the software is available for Windows and Linux.
The Eclipse IDE is a fantastic application that can be used for all sorts of development languages. It integrates very well with source control and issue tracking software to create a development platform that rivals many commercially available systems.
The instructions are on my website:
http://www.cambridgeimaging.co.uk/whitepapers.php
Enjoy!
Paul.
target remote | m68k-elf-cfpe-stub -d USBMultilink# -t m5282evbset $myipsbar = 0x40000000# GPIOset $mypbcdpar = $myipsbar + 0x100050 set *(unsigned char *)$mypbcdpar=0xC0# SRAMset $myrambar = $myipsbar + 0x008 set *$myrambar = 0x20000021# External flashset $mycs0_csar = $myipsbar + 0x80 set $mycs0_csmr = $myipsbar + 0x84 set $mycs0_cscr = $myipsbar + 0x8A set *(unsigned short *)$mycs0_csar=0xFFE0set *(unsigned short *)$mycs0_cscr=0x1980set *(unsigned long *) $mycs0_csmr=0x001f0001# Disable Watchdog Timer Module (WTM)#set $wcr = $myipsbar + 0x140000#set *(unsigned short *)$wcr=0x0000# SDRAMset $mysdramc_dcr = $myipsbar + 0x40 set $mysdramc_dacr0 = $myipsbar + 0x48set $mysdramc_dmr0 = $myipsbar + 0x4Cdefine waitset $foo = 0while ($foo < 20000) set $foo += 1endendset *(unsigned short *)$mysdramc_dcr = 0x023cset * $mysdramc_dacr0 = 0x00001300set * $mysdramc_dmr0 = 0x00fc0001set * $mysdramc_dacr0 |= (0x00000008) # init prechargeset *(0x00000000) = 0xDEADBEEF# waitwait# set RE in dacrset * $mysdramc_dacr0 |= (0x00008000) # issue IMRSset * $mysdramc_dacr0 |= (0x00000040) # wait for 8 auto refreshwait # set modeset *(0x00000000 + 0x400 ) = 0xCAFEBABE
Can some one give me some information about the quality/size of the code (.s19) generated by the m68k-elf-gcc vs the generated by the codewarrior?.
The manage make in eclipse would, in theory, manage makefiles for your project as long as it understood how to call your build tools. Unfortunately, embedded projects usually vary dramatically between platforms and even within platforms. This means that someone has to customise the IDE so that it can manage projects for the platform you are working on.
The commercial IDEs do this - e.g. CodeWarrior and so do the commercial distributions of eclipse - see CodeSourcery for a good example.
If you are trying to create a toolchain and IDE from open source distributions then you generally have to write your own makefiles and linker scripts. The problem you have then is that the examples that you can find are usually far too complex to understand or far too simple to be useful.
Once you have your own makefile and linker script for a project it is not too difficult to tweak them for new projects - mostly you will just cut and paste your source file paths. I am currently working on a simple app that will relocate from flash to SDRAM and execute a simple hello world. If I can make sure there are no copyright issues with the FreeScale startup code I will post a link here for it.
However, the code will be designed for my board, which is similar but not identical to the 5282Lite. You will probably need to do some customisation yourself.
Paul.
mccp wrote:The manage make in eclipse would, in theory, manage makefiles for your project as long as it understood how to call your build tools. Unfortunately, embedded projects usually vary dramatically between platforms and even within platforms. This means that someone has to customise the IDE so that it can manage projects for the platform you are working on.
The commercial IDEs do this - e.g. CodeWarrior and so do the commercial distributions of eclipse - see CodeSourcery for a good example.
If you are trying to create a toolchain and IDE from open source distributions then you generally have to write your own makefiles and linker scripts. The problem you have then is that the examples that you can find are usually far too complex to understand or far too simple to be useful.
Once you have your own makefile and linker script for a project it is not too difficult to tweak them for new projects - mostly you will just cut and paste your source file paths. I am currently working on a simple app that will relocate from flash to SDRAM and execute a simple hello world. If I can make sure there are no copyright issues with the FreeScale startup code I will post a link here for it.
However, the code will be designed for my board, which is similar but not identical to the 5282Lite. You will probably need to do some customisation yourself.
Paul.