cancel
Showing results for 
Search instead for 
Did you mean: 

I need to make a decision between the SPC5X (or RPC5X) and the STM32 for a long-term high reliability project where I need to develop a working platform quickly.

EShar
Associate II
 
1 ACCEPTED SOLUTION

Accepted Solutions
Jack Peacock_2
Senior III

I like to eat fruit. Should I buy guavas or cactus apples? This is in the "how high is up" category of question.

If it's a hi-rel automotive project the SPC5X makes sense...unless you don;t have any experience working with the architecture. In that case an R series ARM part might make sense...if you are knowledgeable on ARM lockstep execution architecture and building hi-rel safety critical designs.

Are you using 3rd party automotive libraries? Then you have to go with the SPC5X, no point in even asking the question. Do you have all the development tools and expertise in place to go with that family? If not, but you do know STM32, climbing the learning curve eliminates anything getting done quickly. Same for the reverse, if you know SPC5X but not ARM the only quick solution is to stay with what you know.

You might start by making a list of your specific design goals, with a column on how each family best fits the goal. That can give you a better picture on how to make the decision.

Jack Peacock

View solution in original post

2 REPLIES 2
Jack Peacock_2
Senior III

I like to eat fruit. Should I buy guavas or cactus apples? This is in the "how high is up" category of question.

If it's a hi-rel automotive project the SPC5X makes sense...unless you don;t have any experience working with the architecture. In that case an R series ARM part might make sense...if you are knowledgeable on ARM lockstep execution architecture and building hi-rel safety critical designs.

Are you using 3rd party automotive libraries? Then you have to go with the SPC5X, no point in even asking the question. Do you have all the development tools and expertise in place to go with that family? If not, but you do know STM32, climbing the learning curve eliminates anything getting done quickly. Same for the reverse, if you know SPC5X but not ARM the only quick solution is to stay with what you know.

You might start by making a list of your specific design goals, with a column on how each family best fits the goal. That can give you a better picture on how to make the decision.

Jack Peacock

EShar
Associate II

​Thanks,

Longevity is my first concern and reliability but full functionality and ease of development are both high on the list of selection criteria. I had an interesting talk to someone but haven't been able to speak directly to an ST technical specialist as of yet. It appears that the SPC57 might well be the most suitable choice provided we have a rapid development path.