Sign in

username:

password:



Not a member?

Search Comp.Arch.Embedded



Search tips

embedded by Keywords

68HC11 | 68HC12 | 8051 | 8052 | ARM | ARM7 | Asic | AT91 | AT91RM9200 | Atmel | AVR | AVRStudio | Bootloader | CFP | CompactFlash | Cygnal | Cypress | Dataflash | DSP | eCos | EEPROM | Embedded Linux | Emulator | Endian | Ethernet | Firewire | FPGA | Freescale | GCC | GNUARM | GSM | H8 | HDLC | I2C | Infineon | Interrupts | Java | JTAG | LCD | LED | LPC2000 | MCU | Microchip | MMC | MPLAB | MSP430 | PC104 | PCB | PCI | PCMCIA | PowerPC | Rabbit | RS232 | RS485 | RTOS | SBC | SDRAM | Sensor | SPI | STK500 | UART | UML | USART | USB | Verilog | VHDL | VxWorks | Xilinx

Ads

Discussion Groups

Discussion Groups | Comp.Arch.Embedded | Embedded processor selection for long-life product

There are 42 messages in this thread.

You are currently looking at messages 40 to 42.

Re: Embedded processor selection for long-life product - rickman - 16:53 30-07-08

On Jul 28, 6:04 pm, "JeffR" <jeffreyram...@e2atechnology.com> wrote:
> >I am faced with selecting a replacement processor/uC for a re-design of
> >some industrial controller/safety equipment. The technical requirements
> >can be satisfied by just about any 32bit risc style uP/uC, but one key
> >requirement is that since the product life is decades long, the
> >particular part or at least the architecture should continue to be
> >supported by the vendor for as long as possible.
>
> >This seems a pretty tough requirement. Years ago, the x86 would have
> >been a good choice, but probably not today. I also think this pretty
> >much rules out any Microchip or Atmel parts as their 32bit line is too
> >new and they have already obsoleted their earliest parts. The latest
> >architectures may be too new to say anything about longevity. I am
> >leaning towards the ARM architecture or perhaps MIPs - something that
> >already has a very large installed base to guarantee continued support.
> >Thoughts?
>
> I wouldn't expect any ARM derivative to have anywhere near a long
> lifespan.  It's a licensed core with all kinds of peripherals glued around
> it.  These processors don't seem to last long.  I would lean toward
> Freescale (e.g. PowerPC).  They carry their processor parts for a good long
> while, they're technically as good or better than most and
> support/documentation is excellent.  The company is also likely to be
> around, even if they change their name again (Moto Semi => Freescale =>
> ?).
>
> Jeffhttp://www.e2atechnology.com

I have no idea why you say the ARM chips don't last a long time.
There are ARM parts from Atmel that have been in production for over
10 years that I know of.  I expect the time has been considerably
longer as they were not new when I first looked at them.

Rick



Re: Embedded processor selection for long-life product - Michael C - 10:23 31-07-08

>I am faced with selecting a replacement processor/uC for a re-design of 
>some industrial controller/safety equipment. The technical requirements 
>can be satisfied by just about any 32bit risc style uP/uC, but one key 
>requirement is that since the product life is decades long, the 
>particular part or at least the architecture should continue to be 
>supported by the vendor for as long as possible.
>
>This seems a pretty tough requirement. Years ago, the x86 would have 
>been a good choice, but probably not today. I also think this pretty 
>much rules out any Microchip or Atmel parts as their 32bit line is too 
>new and they have already obsoleted their earliest parts. The latest 
>architectures may be too new to say anything about longevity. I am 
>leaning towards the ARM architecture or perhaps MIPs - something that 
>already has a very large installed base to guarantee continued support. 
>Thoughts?
>
>

One solution - not the cheapest though - is to build your own chip using a
Soft IP core. (A more expensive solution is to buy the processor company!)

Make sure you go for one where you can get full source code for the core
and for all the compilers, linkers, assemblers, IDE's etc etc. And then
make sure that the vendor is capable of training you in how everything is
built and works. Make sure you can rebuild all the software tools
yourself.

You then control everything. You can change foundaries, process
technologies and anything else.

You could look at http://www.cortus.com who will do that kind of thing.





previous | 1 | 2 | 3 | 4 | 5