From: bigbrownbeastie on
See

http://www.energymicro.com/



From: aleksa on
> The new toolkit was (and still is) the GNU compiler suite, GCC and
> binutils. The original GCC version was 2.95, and the one currently
> in use is 4.3.2.

As "Nobody" suggested, I will translate my x86 code to C and compile it with GNU.

Of course, I will first have to learn C.

And before that, I'll have to check the speed of
ARM @ 200MHz compared to PI @ 166MHz, especially the software FPU speed.
Are there any tables like: FPU ADD/DIV/COS/etc per second?

I've started by downloading the winarm from
www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/WinARM-20060606.exe
and created a small C sample that can be compiled and linked.

The GCC version in winarm is outdated, and these are listed as newer:
www.codesourcery.com/sgpp/lite/arm/portal/subscription?@template=lite
www.devkitpro.org/category/devkitarm
www.yagarto.de
which one should I get? (Using windows XP)


Thanks everyone for your replies!



From: -jg on
On Jan 17, 9:01 am, "aleksa" <aleks...(a)gmail.com> wrote:
> And before that, I'll have to check the speed of
> ARM @ 200MHz compared to PI @ 166MHz, especially the software FPU speed.
> Are there any tables like: FPU ADD/DIV/COS/etc per second?

Not across that combination.

Your best approach is probably to get you hands on a simple ARM
toolchain, and use the silicon hardware to time things for you.

eg The LPCxpresso's start under $30, and will give real numbers.

-jg
From: Ulf Samuelsson on
aleksa skrev:
> I've looked at farnell, there are some 450 MPUs and thousands of MCUs,
> which one should I learn, considering:
>
> I'm currently using a standard x86-32 PC for my project,
> but would like to replace the whole motherboard with
> just two chips: cpu and memory.
>
> The code for x86 is written (by me) in ASM, about 64k in size.
>
> This is what I need:
>
> 1. 32-bit CPU
>
> 2. 128k of internal CODE memory, ISP and IAP.
> (in-system, in-application programmable)
>
> 3. min 32MB of DATA memory.
> (maybe SDRAM, directly connected to CPU)
>
> 4. embedded FPU (or a free, precise library).
>
> 5. QFP package (not BGAs).
>
> 6. price: under 30 EUR.
>
> 7. free develepment tools.
>
>
> My knowledge is: Z80, C51 and x86, ASM only.
>
>

You can add the AT32UC3C0xxx later this year
Some lucky guys are already working with the parts.

* 32 bit AVR32 core
* 128-512 kB Flash
* TQFP-144 (with external bus)
* Floating Point Unit (single precision)
* External Bus Interface
* AVR32 Studio is Free (Eclipse + GCC)

BR
Ulf Samuelsson


From: Ulf Samuelsson on
Stef skrev:
> In comp.arch.embedded,
> Grant Edwards <invalid(a)invalid.invalid> wrote:
>> On 2010-01-13, Stef <stef33d(a)yahooI-N-V-A-L-I-D.com.invalid> wrote:
>>
>>> Dataflashes are available in much larger sizes and since he
>>> wants SDRAM, I suspect that will be at least several MB large.
>>> So booting from dataflash and copying code to SDRAM should
>>> also not be a problem for >MB apps. (you may have to write
>>> some second level loader code yourself, the standard loader
>>> may only load a few KB to get you started).
>> The bootloader built in to the AT91SAM9 parts will only load
>> into internal SRAM (typically 8 or 16KB). That means you need
>> a small second-stage bootloader than enables/configures SDRAM
>> and copys either your application or a larger bootloader (e.g.
>> U-Boot) into SDRAM and executes. Atmel provieds a sample
>> bootloader than is set up to load U-Boot from dataflash,
>> nand-flash, nor-flash, SD-Card, etc.
>
> Ah yes, now I remember (amazing how soon you forget that stuff if
> you're not working on it anymore). The one we use has 16KB of
> internal SRAM. But make sure you limit the first load to somewhere
> around 12K. The ROM bootloader uses the upper part of the SRAM for
> it's variables and other stuff. If you get in that area the result
> gets 'unpredictable'. (mostly just hangs up).
>
>

With the AT91SAM9260, it is limited to 4 kB.
I have my own version of AT91bootstrap at:
ftp://www.at91.com/pub/buildroot/at91bootstrap-2.13.tar.bz2

BR
Ulf Samuelsson