PSoC 5 EETIMES article and CAN status

[Anonymous]

I just read the article about "HW/SW co-development (with finally some emphasis on software)" written by Mark Saunders from Cypress. Nicely done!

   

Mark is using a PSoC 5 and on page 3 / figure 4 he refers to CAN implementation. Then I checked CAN component in a sample project and was surprised by an "obsolete" watermark.

   

Can somebody from Cypress (Mark?) can shed some light into the CAN mystery?

[Anonymous]

 Hey,nice article..thanks for the link!

[HeLi_263931]

The CAN component has been removed in the production silicon of PSoC5. So the article might be based on the ES1 prototypes.

[Bob_Marlowe]

Oh, what was the reason for that decision? Licences? Issues?? Prices???

   

CAN is (here in europe) widely used and it is a must in ever truck and truck-trailer (ISO 11898). 

   

Bob

[HeLi_263931]

As far as I understood there were hardware problems which could not be corrected in time. So the CAN component would not have been reliable enough. Same happend to the SAR ADCS (speed reduced, and some constraints added) and the boost converter. The component are avilable with the old Creator 1.0 and ES1 revisions of the chips. But I havent used CAN on them, so I cannot comment on the issues.

[markgsaunders]

I didn't know that article had been published yet! Glad you enjoyed it.

   

Unfortunately, we had to remove CAN from the PSoC 5 devices we are releasing right now because the implementation failed a certification test and we could not work around the problem. My article was written before I knew about that - sorry for the mis-information.

   

We're working on new chips right now that will have CAN but, for now, it is not available on PSoC 5.

   

-- Mark.

[Bob_Marlowe]

Thank you, glad to hear that!

   

Bob

[HuEl_264296]

Have you thought of trying to implement UDB based CAN? This would be a potential work-around. It would also mean being able to have dual-CAN on devices when they eventually get working CAN.

[OlPe_282281]

hli posted on 01 Jan 2012 12:35 PM PST Top Contributor 111 Forum Posts

   

As far as I understood there were hardware problems which could not be corrected in time. So the CAN component would not have been reliable enough. Same happend to the SAR ADCS (speed reduced, and some constraints added) and the boost converter. The component are avilable with the old Creator 1.0 and ES1 revisions of the chips. But I havent used CAN on them, so I cannot comment on the issues.

   

---------------------------------

   

From where do you have this information? I wasn't able to find them.

[HeLi_263931]

This was more about the SAR ADC than the CAN component. Both were mentioned in another thread, but I cannot find it right now. But yfs confirmed the CAN problems.

[HeLi_263931]

Funny thing - i just noticed that the thread in question was actually this one 🙂 So just scroll up to yfs' comment.