ARMmite Evaluation Kit

[rocky79]

Have any of you guys tried this development kit from coridium?

I have been using picbasic pro on a pic.
I want to try the AVR s with a c compiler
http://www.coridiumcorp.com/catalog/product_info.php?products_id=58
any feedback is appreciated

Thanks for looking

[mmormota]

It's an ARM (32 bit) board, not AVR (8 bit Atmel core).

[rmteo]

Here is a low-cost ($20) AVR board:
http://www.futurlec.com/ET-AVR_Stamp.shtml

They also do an ARM board ($25):
http://www.futurlec.com/ET-ARM_Stamp.shtml

[Tom Harper]

Nice spec - that's a lotta computer for twenty bucks!

[AndyKunz]

Just finished up a product using an Atmel AT91SAM7X256 at work. Great chip.

Andy

[Wulffy]

Have any of you guys tried this development kit from coridium?

I have been using picbasic pro on a pic.
I want to try the AVR s with a c compiler
http://www.coridiumcorp.com/catalog/product_info.php?products_id=58
any feedback is appreciated

Thanks for looking

Actually, I have gone radio silent here for nearly a month. The reason is that I am heavily into coding up a project using Coridium's products (http://www.coridiumcorp.com/Products.php).

I have the horizontal navigation stuff working - not as well as I'd like, but none-the-less working. It appears that I am getting sub-meter (~.1% with respect to GPS-reported position) accuracy with my navigation solutions, when the waypoint distances are closer than ~15KM. When the distances are greather than that, the accuracy degrades. Angular accuracy for Desired Track/Course is accurate to .1 degrees, I believe (rolling tests have confirmmed).

I have also successfully demonstrated simultaneous control of 5 Futaba Servos using the hardware - more is very feasible.

I must say that I have had tremendous support from the principles at Coridium. I have worked with them over the last couple of weeks to refine the IDE.

My source-code is here (http://tech.groups.yahoo.com/group/ARMexpress/files/UAV_Project_Files/). It is VERY MUCH A WORK IN PROGRESS, and is in dire need of having the comments cleaned up. I have just came to the realization that I will most likely need to integrate a Floating Point Unit in order to get the GeoNav solutions truly working the way that I want. More on that in a minute.

The GPS module that I am using is the USGlobalSat EM-411, however, with the code, I am confident that it can be altered to parse any NMEA GPS receiver. The EM-411 is a 1hz unit. I will eventually get a 4+ Hz unit as the production module of choice. I have configured and am successfully parsing the GPS sentences that are being transmitted at 115.2K.:D

The latest ARMbasic IDE software has just been released yesterday (and he was kind enough to throw a thanks my way for all of the effort). It allows for pausing the source code execution, looking at variable contents, and resuming execution.

Regarding the FPU. Today I have spent several hours researching and I have made a selection. The unit I will order is the MicroMega uM-FPU-v3 (http://www.micromegacorp.com/umfpu-v3.html). It seems that it may actually have its roots in a project similar to what I am involved in. Regardless, it seems to be the best solution for an embedded FPU coprocessor. It will also allow for me to dump some of my horribly inefficient code and be able to focus on the main application functionality and not worry about developing integer based navigation algorithims...

Regarding the IDE - the Coridium product line can be either ARMbasic or C. With the latest enhancements, ARMbasic has a much friendlier Development environment cycle than what C does, at the moment. Coridium is also looking to enhance the debugging capabilities of their IDE further, as well.

I'd recommend evaluation of their hardware in any embedded control application. The true value is that one doesn't have to pay a penalty for a learning curve if they already are comfortable with BASIC...

I hope that this helps.

Have a good one!

-t

EDIT: Oh, one thing to note is that I am planning on using both an ARMexpress and an ARMmite. The 'mite will be my Airframe Interface/Flight Data Acquisition Unit/Flight Data Recorder (see the data logging thread on Coridium's yahoo group). The 'express will be interfaced to the telemetry transceiver, the 'mite, the FPU, and other nodes of the system. The 'mite is based on the NXP LCP2103F MCU. While having a nice set of I/O capabilities, it does not have the memory that my application will be needing. This is why I have also secured a NXP LCP2106F based 'express and am using that as the Master with the 'mite/FPU/etc. being Slaves. I am also working to determine if I want to use I2C or SPI as the communication medium between the Master/Slave modules. I'll attach a picture in a minute...

[rmteo]

Wulffy, have you seen the new GPS receiver from the Sparkfun guys?

[Wulffy]

Wulffy, have you seen the new GPS receiver from the Sparkfun guys?

Oh yeah... :)

Actually, I'm all about the ones with the integrated antenna and an option for an external one as well.

However, when I finally PCB up my project, I will most likely go with something like you have pointed out...

[treehog]

thanks

Ralf

[rmteo]

Wulffy, I just came across a press release about 2 new GPS receivers chips from SiGE. They are 2.2x2.2x0.4mm, draw just 10mA and in quantity are about $2.50 each. Amazing world we live in. :p :p :p