My apologies if this topic has been beaten to a pulp, but my casual
search has not yet led me to the answers I need.
We have developed a small system based on the redoubtable Cygnal/SILabs
C8051F311 processor. While all of the current functionality fits into
the 16 KBytes of onboard FLASH, it's tight, and we are just one
validated feature request from being out of luck.
As a result, I'm on the hunt for a replacement processor. Our needs in
priority order are:
* size - it can't be much bigger than the 'F311 (5x5 mm)
* code space - more than 16K bytes (or equivalent for a different
architecture)
* I/O speed - the 'F311 is 25 MHz, which gives us ~4 MHz max on I/O;
faster would be useful
Desirable:
* low voltage operation - 1.5 V
* UART
* integrated crystal
* on-chip JTAG/debug
The system doesn't need much in the way of specialized features; we
only use one UART, and could do that in software if we had to. If we
need to shift architectures (e.g., ARM, AVR), that's an option.
What devices would you suggest I look into?
Thanks in advance,
Zig
Reply by Jim Granville●April 6, 20052005-04-06
AssemblyZig wrote:
> My apologies if this topic has been beaten to a pulp, but my casual
> search has not yet led me to the answers I need.
>
> We have developed a small system based on the redoubtable Cygnal/SILabs
> C8051F311 processor. While all of the current functionality fits into
> the 16 KBytes of onboard FLASH, it's tight, and we are just one
> validated feature request from being out of luck.
>
> As a result, I'm on the hunt for a replacement processor. Our needs in
> priority order are:
> * size - it can't be much bigger than the 'F311 (5x5 mm)
> * code space - more than 16K bytes (or equivalent for a different
> architecture)
> * I/O speed - the 'F311 is 25 MHz, which gives us ~4 MHz max on I/O;
> faster would be useful
>
> Desirable:
> * low voltage operation - 1.5 V
> * UART
> * integrated crystal
> * on-chip JTAG/debug
>
> The system doesn't need much in the way of specialized features; we
> only use one UART, and could do that in software if we had to. If we
> need to shift architectures (e.g., ARM, AVR), that's an option.
>
> What devices would you suggest I look into?
Depends on your timeframe.
Ask SiLabs for info on their upcomming C8051F410/C8051F411.
32KF/~66MHz/5x5mm/Wider supply than F311.
There was short-form info on the web, but strangely, that has gone.
Supposedly ~June timeframe.
Goal semi are talking of a VRS2000, 40 mips, 64KF, but that
is std TQFP44/64, so will not be 5x5mm, and is some way off...
Two uC can sometimes also be a viable design solution ?
-jg
Reply by ●April 7, 20052005-04-07
AssemblyZig wrote:
> My apologies if this topic has been beaten to a pulp, but my casual
> search has not yet led me to the answers I need.
>
> We have developed a small system based on the redoubtable
Cygnal/SILabs
> C8051F311 processor. While all of the current functionality fits
into
> the 16 KBytes of onboard FLASH, it's tight, and we are just one
> validated feature request from being out of luck.
>
> As a result, I'm on the hunt for a replacement processor. Our needs
in
> priority order are:
> * size - it can't be much bigger than the 'F311 (5x5 mm)
> * code space - more than 16K bytes (or equivalent for a different
> architecture)
> * I/O speed - the 'F311 is 25 MHz, which gives us ~4 MHz max on
I/O;
> faster would be useful
>
> Desirable:
> * low voltage operation - 1.5 V
> * UART
> * integrated crystal
> * on-chip JTAG/debug
>
> The system doesn't need much in the way of specialized features; we
> only use one UART, and could do that in software if we had to. If we
> need to shift architectures (e.g., ARM, AVR), that's an option.
>
> What devices would you suggest I look into?
>
> Thanks in advance,
> Zig
Hi, are you sure your not wasting code space? Are you using an
appropriate language?
Reply by AssemblyZig●April 7, 20052005-04-07
Hmmm.... an 'F411? I hadn't seen that. And its disappearance
doesn't bode well. But one can always hope.
As for code space, the application is written in C, 8051-cognizant
and heavily tweaked (converted from an initial assembly
representation). So I am sure I'm wasting code space, but not much
more than is required by virtue of the language.
Zig
Reply by Jim Granville●April 7, 20052005-04-07
AssemblyZig wrote:
> Hmmm.... an 'F411? I hadn't seen that. And its disappearance
> doesn't bode well. But one can always hope.
Im sure you know the problems with 8051s running C. You might consider
a diffferent language. As with all these problems it depends on exactly
what your trying to do. You should look carefully at your map files and
see just exactly what is using up the space, you may find ways around
it.
Reply by Ulf Samuelsson●April 15, 20052005-04-15
> We have developed a small system based on the redoubtable Cygnal/SILabs
> C8051F311 processor. While all of the current functionality fits into
> the 16 KBytes of onboard FLASH, it's tight, and we are just one
> validated feature request from being out of luck.
>
> The system doesn't need much in the way of specialized features; we
> only use one UART, and could do that in software if we had to. If we
> need to shift architectures (e.g., ARM, AVR), that's an option.
>
> What devices would you suggest I look into?
>
> Desirable:
> Chip
Signal Processing Engineer Seeking a DSP Engineer to tackle complex technical challenges. Requires expertise in DSP algorithms, EW, anti-jam, and datalink vulnerability. Qualifications: Bachelor's degree, Secret Clearance, and proficiency in waveform modulation, LPD waveforms, signal detection, MATLAB, algorithm development, RF, data links, and EW systems. The position is on-site in Huntsville, AL and can support candidates at 3+ or 10+ years of experience.