which 32bit mcu for automotive application?

Apr 16, 2006 18 Replies

Hello



I'm trying to choose a microcontroller for an automotive application. I spent couple days digging through lots of pdfs but... I'm just a programmer;) Now, for the first time, I have to choose mcu so I thought asking for help of more experienced people would be good idea;)



Criteria are pretty simple:



- reliable



- efficient (about 50MIPS) 32bit mcu (preferably RISC, arm-based?)



- operating in -40 to 125 oC temp. range



- at least 8 external interrupts



- at least 8 independent pwm outputs (some timers or specialized units)



- at least 8 independant general purpose timers (16 would be great)



- can, uart, adc



- having jtag onboard would be great;)



seems easy to find? maybe it is, but take under consideration availability of well written documentation, starterkits, developement tools, good IDE with reliable compiler and debugger...



thanks in advance, any suggestion (even name of a company that is worthy of trust) would be great help for me:)



Best regards, Kuba


You may want to consider TI TMS470 family; it sports a so-called high-end timer which is in a way a high-speed I/O coprocessor.

- Ark

Motorola/Freescale MPC555. With its dual Time Processing Units (TPU), it has 32 channels available for precise timing and/or PWM generation. It has dual CAN 2.0 ports, 32 10-bit A/D channels, dual serial ports and a Queued SPI module. It is rated for -40 to +125 C (automotive) operation. It has a JTAG port, and a Background Debug Mode (BDM) port for low-cost debugging. There are several commercial compilers/IDEs available, and GNU-based tools.

Read all about it at:

formatting link

--Gene

Deprecated in favour of the 55xx family now, I believe?

It certainly used to be a challenge getting silicon out of Motorola/Freescale unless you were a *big* customer, but I think things have changed a little.

The Diab toolchain (now owned by Wind River) is very nice. And there's a Green Hills toolchain.... if you're into self-flagellation. ;P

From what I recall, About the only thing I didn't like about the

555 was the way the interrupt sources attached to SIU and UIMB were interspersed and wired to the same exception vector. It meant knitting rather a complex set of software demuxing and 'pseudo-vectors', but a fair amount of that was because of the way the lead customer for the RTOS we were building wanted things doing...

The 56x family is a lot nicer from the point of view of interrupts, the

55xx nicer still.

pete

pete@fenelon.com "That is enigmatic. That is textbook enigmatic..." - Dr Who "There's no room for engimas in built-up areas." - N Blackwell

I'm considering this one too. This HET thing looks really interesting. I'm just not sure if I will be able to generate 8 independent waveforms using it (not exactly pwms). Have you ever done anything on this mcu? I must be really sure the peripherials are good enough for my needs and HET's documentation isn't quite easy to analyze. If you have done something with HET, I would have one or two questions for you:)

lots of thanks, kuba

p.s. sorry for my English;)

Definitely have. Freescale have supplied me with samples of fairly expensive parts (MPC5200, MPC8271, and various sensors) for my projects, which I clearly stated would not be big volume, ever. Very painless sample ordering process.

These look very nice, but I'm looking for a mcu that costs about 10-20$ (in large quantities). Sorry I forgot to write about it;)

thanks a lot kuba

The MPC5200 was announced at $22.50/10K in 2003. One distributor has it (commercial grade) for $17.50. If you ask for the moon, expect to pay for it.

--Gene

Sorry, out of automotive for several years now. I know though that this family is used by major Tier I suppliers worldwide, so

- they won't disappear overnight

- they are good enough for Tier I I haven't done anything worthy with the HET. ARM compiler vendors may support HET as an add-on (as, I believe, is the case with IAR).

- Ark

Thanks a lot, I'll do some further research into this topic.

best regards kuba

automotive almost always use floating point hardware for the main engine controllers, you didn't mention that requirement, MPC55x, 55xx, for instance are standard automotive micros for engine control and have floating point hardware, ARM is lacking in that area, but it depends what automotive application you are talking about, many smaller micros in an auto with limited functionality don't need the floating point hw, but if you do, your selection goes way down

....I think the OP misread my post - I suggested the 55xx family not the

52xx ;)

pete

pete@fenelon.com "That is enigmatic. That is textbook enigmatic..." - Dr Who "There's no room for engimas in built-up areas." - N Blackwell

Is code security an issue? ie is there a risk that someone will reverse-engineer your product, & send it to SE Asia to copy?

Since no-one has yet mentioned it here, there's also the Infineon TC1796.

You might try the Freescale 683xx controllers using the CPU32X core (aka Excalibur). Has two 16-channel TPUs, an 8-channel CTM, CAN, UART, Class2, and ADC. In use on a lot of GM vehicles in engine controllers.

C compiler from Diab.

~Dave~

No, it's actually the opposite--most don't use floating point. Until perhaps the latest model year or so, variants of the Freescale 683xx processors (CPU32 and CPU32X) went into the engine and powertrain (combined engine and transmission) controllers of most GM vehicles. These processors have no floating point capability. They used fixed point arithmetic. These ECMs and PCMs are still in production as the PowerPC-based controllers are being phased in.

~Dave~

yep, don't disagree, they are phasing out fixed point, Ford is doing the same, just suggesting that the OP should get on the floating point bandwagon if he is starting a new design now, as its increases productivity, that's all

Check for support in your area first...

\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/ /\/\/ chris@phaedsys.org www.phaedsys.org \/\/\ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Check out the MPC533.

It is a cut down version of the MPC563 without a TPU, which makes it significantly cheaper.

The TPU is essential for injection scheduling, but is not required for normal PWM outputs.

Andy

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required