There was a time where these looked like a nice way to do business. These days I have completely lost interest in them, and have moved on to AVR microcontrollers for small projects, and embedded linux on things like ARM processors when I need ethernet. The absolute worst thing about the rabbit was that the development system was only Windows hosted. Pretty narrow minded.
There are a whole series of rabbit core modules (RCM's) and rabbit processors. A typical RCM has an ethernet port, processor, memory, and bunch of IO. An RCM sells for around $50, which makes them attractive for small embedded projects that need a network interface.
I am playing with an RCM5700. The main reason is that I could buy a module with a development kit for a little more than $100 in late 2009. The RCM5700 does not have a RJ-45 on the module (you need to buy a RCM5710 to get that). Not to worry though, there is an RJ-45 on the development board.
An attractive module is the RCM3700. The main attraction is that this module communicates with your project via a standard 0.1 inch center IDC connector (like the one on every ribbon cable on the planet) on the bottom of the module.
No big surprise, but Dynamic C expects to run on Windows. I strive to never run Windows (and you should too!) My first thought was to see what wine might do for me. I installed Dynamic C 10.60 under wine, which was easy enough, and Dynamic C fires up just fine, but there is no joy as far as communication to the rabbit module via USB.
You can read all the details via this link:
My experiences with the RCM5700 and the Dynamic C 10.60 compiler under linux/wine.
Wow, it worked!! And it wasn't impossibly hard. After installing virtual box, I had
to set up a USB filter to recognize the usb to serial chip in the rabbit. Then after starting
windows in the VM, I plug in the USB cable to the rabbit and windows says it sees new hardware
and installs a driver. Then I start up Dynamic C 10.60 and at first I was getting communications
errors, but I use Options->Project Options and change the serial port from COM1 to COM3 (USB) and
away things go!!! First I use Compile->Reset Target and Compile BIOS, then I select their DEMO1.c
program. Use the Compile button to compile it, and the Run button to run it.
It works! Away I go! Hooray!!
wine f:/DCRABBIT_8.51/dccl_cmp.exe hello.c -h+ -brWhat I use on my system to launch dynamic C in its GUI form is:
wine "c:\dcrabbit_10.05\dcrab_10.05.exe"I also have a Dccl_cmp.exe executable, so I can do the same trick. Once I find out what all the command line options for that are, who knows! And it turns out if I do:
wine "c:\dcrabbit_10.05\dccl_cmp.exe"It gives me a list of all the options!
The rti parameters may be given via online argument and specify a CPU id and revision, base frequency, ram and flash.
Just in case this guy goes away with all his goodies, I have stashed them here on my machine, but you should go to his site to see if he is continuing his work. (Since this is 12/2009 and these files were last updated 7/2004 he seem to have found other things to do with himself).
I was not interested in another time consuming never ending hobby project.Sound like many of the enterprises I am and have been involved in!!
Tom's Computer Info / firstname.lastname@example.org