FM4 - FR60 compatibility ?

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
zzz_3221081
Level 5
Level 5
25 solutions authored 100 sign-ins 10 likes received

Hi,

my company is using FR60 controllers for some years now.

They are fine technically, but clearly on the way to discontinuation.

Thus, we ponder porting our ECU application to a ARM core, with a M4F looking sufficient.

I'm well aware that the FR60 is/was a Fujitsu proprietary core, and shares very little resemblance with a Cortex M core.

But since the FM4 family originated within Fujitsu as well, there is a good chance both families share common peripheral components.

In other words, was the IP of peripherals from the FR60 re-used for the FM3/FM3 family ?

Especially the CAN peripheral unit would be interesting, but timers and serial units as well.

I realized similar reuse of periphery blocks with MCUs from other vendors - often even old 8-bit periphery ends up on Cortex M4 cores.

Perhaps anyone can share some insights.

0 Likes
1 Solution
HongyanW_86
Moderator
Moderator
Moderator
100 solutions authored 100 replies posted 50 solutions authored

Hello,

FM4 is targeted for non-Automotive application. For your ECU application, I would like to suggest you check our Traveo (ARM cortex-R5) MCU and upcoming Traveo II (ARM Cortex M) MCU.

https://www.cypress.com/products/cypress-traveo-32-bit-arm-automotive-microcontrollers-mcus

For more information about Traveo II or part selection of your application, please kindly get in touch with Cypress sales team or distributors.

https://www.cypress.com/cypress-franchised-distributors

Best regards,

Amy Wang

View solution in original post

0 Likes
6 Replies
HongyanW_86
Moderator
Moderator
Moderator
100 solutions authored 100 replies posted 50 solutions authored

Hello,

FM4 is targeted for non-Automotive application. For your ECU application, I would like to suggest you check our Traveo (ARM cortex-R5) MCU and upcoming Traveo II (ARM Cortex M) MCU.

https://www.cypress.com/products/cypress-traveo-32-bit-arm-automotive-microcontrollers-mcus

For more information about Traveo II or part selection of your application, please kindly get in touch with Cypress sales team or distributors.

https://www.cypress.com/cypress-franchised-distributors

Best regards,

Amy Wang

0 Likes

Thanks for the quick response.

You are correct - our ECU application is safety-related, and a Cortex R would be more appropriate.

My question would be the same - are the peripheral units of the Traveo MCUs similar/identical ?

Taking a brief look a the FM4 peripheral manuals, the CAN unit register mapping looks identical to the FR60 one, apart from the different endianess.

0 Likes

Hello,

Some peripherals are similar and please kindly check Traveo Hardware Manual for details.

https://www.cypress.com/documentation/technical-reference-manuals/32-bit-microcontroller-traveotm-fa...

For CAN, Traveo can support CAN FD.

Best regards

Amy Wang

0 Likes

The Traveo site left me a bit confused, actually.

But I assume all information refers to the "old" Traveo, unless it explicitly states Traveo II.

For evaluating the costs and practicality of a FR60 -> Traveo II porting, we would need more detailed information.

The Cortex M4/M7 part is interesting, but I guess I have to wait for the official release for more details.

Can I ask when the this official release is scheduled ?

0 Likes

Hello Frank,

Yes, your assumption is correct. Those information or materials about S6J3xxx on the product web-page are for Traveo family(ARM cortex R5), which is available now.

Please kindly get in touch with Cypress sales team or distributors for release schedule or preliminary information/documentations of Traveo II.

https://www.cypress.com/cypress-franchised-distributors

Best regards,

Amy Wang

0 Likes

Thanks,

this clarifies the Traveo website a bit.

I had been discussing our idea briefly with a distributor I'm in touch with currently (for other reasons...).

As mentioned, there is nothing "cut and dried" yet, just the idea of an update project.

In our sector, there is usually some significant inertia + lag involved, due to safety certifications and replacement guaranties.

0 Likes