MCU availability

[a8Chcx]

Hi,

I am using "MK64FN1M0VLL12" for my product. Now, it has long lead-time and will be available by end of 2023.

Could anybody tell me if there is similar MCU that is available to order from NXP? If so, I am going to change my board...

Or is there anyone who can help me buy this MCU?

Thanks,

Christie

[jingpan]

Hi @a8Chcx ,

Yes, the lead time is really long. In fact, all Kinetis family devices have the same problem. If you needn't enet, you can turn to LPC55. If you want ENET, please take i,mxRT1020/RT1024 into consider. They have short lead time.

LPC55 and RT102x has same drive structure as kinetis. Porting K64 code to them should be easier than port to other MCU.

Regards,

Jing

[a8Chcx]

HI Jing,

Thank you.

I checked i.MX RT1020/1024 and see some of them have long lead time as well, or not recommended for new design.

Could you recommend any PN that is popular used and easy to order in i.MX RT series?

Thanks,

Christie

[a8Chcx]

Hi Jing,

I an not using ENET. Can you tell me which one is popularly used from LPC55 series?

M33 is newly introduced. Any big difference from M4 or M7?

Thanks,

Christie

[a8Chcx]

Hi Jing,

I have to use CANBUS 2.0.

Can you tell me CAN-FD can work with CAN 2.0?

Thanks,

Christie

[jingpan]

Hi @a8Chcx ,

1. To explain it, CAN 2.0 is supported on all LPC55s1x/LPC551x devices. LPC5512JBD100 and LPC5512JBD64 support CAN 2.0 only. The other LPC55s1x/LPC551x devices support both CAN 2.0 and CAN FD. CAN FD is based on CAN 2.0. As to the RT1024, FlexCAN can support CAN 2.0B.

2. (Which one is popularly?) I can only say Please select base on your requirement.

3. M33 and M4 have approximate computational power. M7 is more powerful. M33 has more security feature than M4.

4. I'm sorry I don't know about the lead time. You can consult to local agent. 

Regards,

Jing

[a8Chcx]

Hi Jing,

Thank you.

I want to use "LPC55S16JBD100" for my product. But, it only supports CAN FD.

1) Can you tell me if I can use CAN FD to work with CAN 2.0 because all other devices are using CAN 2.0 for now?

2) Can I configure CAN FD as CAN 2.0 to work with other devices with CAN 2.0?

Regards,

Christie

[jingpan]

Hi @a8Chcx ,

1. yes, you can use CAN FD to work with CAN 2.0.

2. yes

Regards,

Jing

[mjbcswitzerland]

Hi

I would use an i.MX RT 1051/52/61/62/64.
They are all footprint compatible (when only up to 1 Ethernet and no eLCD is used) and have the same FlexCAN module in them as the Kinetis K64. They can often be found at distributors (sometimes for extortionate prices unfortunately) in several hundred quantities and so for small product runs are not a big problem to use almost immediately. They are also popular for K66 replacements that are  virtually impossible to get for the foreseeable future as they also have identical HS USB to the one in the K66 (but two for even better performance when two are used).

A lot of uTasker project users have moved their Kinetis products over to the i.MX since Kinetis developments can be built to run on i.MX RT parts with only a few define adjustments for the new pin out so needs very little learning and, if all goes well, only a few hours to get existing Kinetis FW ported and running compatibly.

uTasker users share designs and parts stock so even if urgent quantities of these are needed (several thousand in a short time frame) it is often possible.

Note that a number of projects are using the Teensy 4.0 / Teensy 4.1 modules that are quite readily available between $20 and $26 for urgent HW requirements as they are small and can be plugged into new designs. These have the 600 MHz  i.MX RT 1062 on them with 8Meg QSPI (and Ethernet if needed, with pre-programmed official MAC addresses). I have also heard of rumors of their processor being removed and put into other HW, although that would be the exception.

Although the i.MX RT 116x/117x support has not yet been released in the uTasker project these are interesting parts due to the fact that they essentially offer the same capabilities (up to 1GHz) and simple path from Kinetis. They potentially have the best availability as NXP is pushing them hard and they are quite readily available at reasonable prices at distributors with not that many actual products using them just yet. The down side is that they are 256 BGAs and so a bit larger.

Regards

Mark

Although a little overwhelmed by the quantity of product conversions presently in progress the uTasker project offers such services which have proven to give fairly simple routes to ensure product continuation security for companies worried about surviving the chip shortage period. Capacity is however available (including standard proven HW/FW designs that are exchanged) for those nervous about surviving the next year or so.