Add support for the NXP FRDM-K32L2A4S eval board. #1858
Conversation
There was a problem hiding this comment.
thank you for your PR. The K32L2AXX is similar to K32L2BXX, that we could merge them together as K32L2 family. If you are not familiar, just simply use the K32L2BXX for this new board. I will make a rename later on.
PS: BSP need to use the git submodule nxp mcux as mentioned in the review of #1854
|
I will copy frdm_k32l2b to frdm_k32l2a and start from there using the submodules. For you to rename later. I know in board.mk I can use $(BOARD) and I could CFG_TUSB_MCU in the C code to tell which MCU is being used by adding 1202 for the K32L2A. That would require changing the various CFG_TUSB_MCU == K32Lxxxs everyplace as I did in this current pull request. I'm not feeling that is the direction you want to go. What I'm unclear on is how to use this to build either target from a single directory. Can you point me to a device family example please? I did not see such an example in the porting docs. |
src/portable/nxp/khci/hcd_khci.c
Outdated
| #if CFG_TUH_ENABLED && ( \ | ||
| ( CFG_TUSB_MCU == OPT_MCU_MKL25ZXX ) || ( CFG_TUSB_MCU == OPT_MCU_K32L2BXX ) \ | ||
| ) | ||
| #if CFG_TUD_ENABLED && \ |
hw/bsp/board_mcu.h
Outdated
| @@ -47,7 +47,7 @@ | |||
|
|
|||
| #elif CFG_TUSB_MCU == OPT_MCU_LPC51UXX || CFG_TUSB_MCU == OPT_MCU_LPC54XXX || \ | |||
| CFG_TUSB_MCU == OPT_MCU_LPC55XX || CFG_TUSB_MCU == OPT_MCU_MKL25ZXX || \ | |||
| CFG_TUSB_MCU == OPT_MCU_K32L2BXX | |||
| CFG_TUSB_MCU == OPT_MCU_K32L2AXX || OPT_MCU_K32L2BXX | |||
hw/bsp/frdm_k32l2a4s/board.mk
Outdated
| endif | ||
|
|
||
| SDK_DIR = hw/mcu/nxp/mcux-sdk | ||
| MCU_DIR = $(SDK_DIR)/devices/K32L2A4S |
There was a problem hiding this comment.
the mcu on this board should be K32L2A41A though
Add support NXP FRDM-K32L2A4S evaluation board.
The K32L2A4S uses a different core, and in some cases different I/O configuration registers, than the existing FRDM-K32L2B3 evaluation board port.