Re: bringing ARM CPUs into the RCM modules

I speculate that the reason this hasn't been done to date (I've thought about this idea several years ago) is because it would be practically impossible to match the Rabbit module pricing, especially the Ethernet modules.

Also, under the current license, you cannot port Dynamic C libs to an ARM (even with DC-specific changes removed).  TCP/IP isn't an issue because the Open Source lwIP stack is far superior to DC's TCP/IP stack and they have a beta with IPv6 as well.  Making a wireless ARM module would be a huge undertaking.  End user code could relatively easily be ported - I wrote DC2ANSI which is used to convert the DC stack to ANSI C for Softools.  There were still some changes required but it did 95% of the job.

Just my 3 cents worth...

Bill

--- In [email protected], "hemonserrat"  wrote:
>
> yes! sound good, interesting for me. 
> Take in consideration RCM2xxx parts too.
> But the real issue for my market, is the price.
> 
> Hernan - Embedded Systems Developer.
> Country: Argentina.
> 
> --- In [email protected], "basicnode"  wrote:
> >
> > We've used Rabbit based modules in the past, but have moved onto ARM CPUs, and have now done a couple of ports of RCM3xxx based modules to ARM CPUs.
> > 
> > We're wondering if there is enough interest out there to do a RCM3xxx pin compatible module with an ARM processor.
> > 
> > While Dynamic C is not ANSI standard, in many cases it's close enough to move code, and in the ARM the RAM paging is not an issue.
> >
>