shabaz , can you show a screen capture of your configurator's Clocks Table?

When I use NXP's SDK builder it sets the clock to 48. I'm trying to set the right positions to config it for a 24 MHz crystal

I'm trying to make an online SDK, and pins config seems to be straightforward:

The clock configurator is more complex.

I see the following for Tools->Clocks, I cannot seem to get the same display as you have with the online version.

Does the online version allow opening a .mex file? If so, the one I'm using is this one: ez_mcxn/mcx_projects/_boards/ez_mcxn/EZ_MCXN.mex at main · shabaz123/ez_mcxn

This view is what I was looking for. 

I downloaded the config tool, so I'll be able to check the .mex file.

I created a downloadable SDK, with the same PIN and Clock settings as your .mex:

https://mcuxpresso.nxp.com/download/f6f77f03cd2c195953272c1bb73481d5

Now checking if I can make a project from it ...

Interesting.. I just downloaded it, it creates an entire custom SDK?

Interesting.. I just downloaded it, it creates an entire custom SDK?

Yes, you can import it in the IDE (I use VS Code + extension) and you can create projects based on it.

I have it working, but not perfect. It takes some pin and clock definitions, but not all.

The example I created for it, builds:

That custom SDK doesn't do what I was expecting. It doesn't actually add the config settings I made online.

I'm studying further to understand how to create a project that doesn't use example code settings / artifacts.

They made it very hard to follow and I couldn't figure that out. I unfortunately didn't make a record of what I did the first time, but I believe I resorted to copying one of their example board folders, and then deleted files one-by-one to see what was used, and then used the GUI to create the autogenerated files to put there. But I kept one unused header file (just renamed it so it wouldn't be included in the build) since it might be useful if ever using FreeRTOS one day. Also the NXP examples use "west" which I had never heard of and it's another annoyance, because I found it very slow, the simplest of builds were taking 10 seconds. So for my build.ps1 I got AI to only use west for the first build, and then for all non-clean builds it skips that and just directly uses ninja. That made the simple builds occur within a second. But it did make me wonder, was west even necessary, probably not. But again perhaps the RTOS benefits from that, no idea, so I didn't completely get rid of west.

I 'm going to try and build a little project, using :

• the SDK where needed
• the output from a clean .mex, using your clocl settings
• CMake
• CMake and bash settings from your repo

and then, when a compile fails, look one step further to see what's missing ...

I got the build part working. 4 hours of sweat and anger:

cmake_minimum_required(VERSION 3.29)

set(CMAKE_VERBOSE_MAKEFILE OF)

set(CMAKE_C_STANDARD 11)
set(CMAKE_CXX_STANDARD 26)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

# SDK_ROOT set externally
set(SDK_ROOT $ENV{SDK_ROOT})
message(STATUS "SDK_ROOT: ${SDK_ROOT}")

set(CMAKE_SYSTEM_NAME Generic)
set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} --specs=nosys.specs") # else CMake throws toolchain error when using an embedded GCC

add_compile_definitions(
    CPU_MCXN236VKL
    MCXN236
)


project(ez_mcxn_minimal LANGUAGES C CXX ASM)

include_directories(
    ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/common
    ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/gpio
    ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/mcx_spc
    ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/port
    ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236
    ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/drivers
    ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/periph1
    ${SDK_ROOT}/mcxn236/mcuxsdk/arch/arm/CMSIS/Core/Include
    ${SDK_ROOT}/mcxn236/mcuxsdk/arch/arm/CMSIS/Core/Include/m-profile
    # project includes
    ${CMAKE_SOURCE_DIR}/board
)

add_executable( ${CMAKE_PROJECT_NAME})

set(MCXN_FLAGS
    -mcpu=cortex-m33
    -mthumb
    -mfloat-abi=hard
    -mfpu=fpv5-sp-d16
    --specs=nano.specs
)

target_sources(${CMAKE_PROJECT_NAME}
        PRIVATE
        ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/gcc/startup_MCXN236.S
        ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/system_MCXN236.c
        ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/drivers/fsl_clock.c
        ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/drivers/fsl_reset.c 
        ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/mcx_spc/fsl_spc.c
        ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/common/fsl_common.c
        ${SDK_ROOT}/mcxn236/mcuxsdk/drivers/gpio/fsl_gpio.c
        # project sources
        # MCUXpresso Cfg generated:
        ${CMAKE_SOURCE_DIR}/board/clock_config.c
        ${CMAKE_SOURCE_DIR}/board/pin_mux.c
        # stubs for functions not implemented in nano c lib
        ${CMAKE_SOURCE_DIR}/stub.c
        # application sources
        ${CMAKE_SOURCE_DIR}/main.c
)

target_compile_options(${CMAKE_PROJECT_NAME} PRIVATE
    $<$<COMPILE_LANGUAGE:CXX>:-fno-use-cxa-atexit>
    $<$<COMPILE_LANGUAGE:CXX>:-fno-exceptions>
    $<$<COMPILE_LANGUAGE:CXX>:-fno-rtti>
    $<$<COMPILE_LANGUAGE:CXX>:-fcommon>
    $<$<COMPILE_LANGUAGE:CXX>:-fmodules-ts>
    ${MCXN_FLAGS}
    -Wall
    -ffunction-sections 
    -fdata-sections
)

target_link_options(${CMAKE_PROJECT_NAME} PRIVATE
    ${MCXN_FLAGS}
    --specs=nano.specs
    -Wl,--gc-sections
    -Wl,--no-warn-rwx-segments
    -T ${SDK_ROOT}/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/gcc/MCXN236_flash.ld
)

add_custom_command(TARGET ${CMAKE_PROJECT_NAME} POST_BUILD
    COMMAND ${CMAKE_OBJCOPY} -O binary $<TARGET_FILE:${CMAKE_PROJECT_NAME}> ${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}.bin
    COMMENT "create  bin executable: ${CMAKE_PROJECT_NAME}.bin"
)

I needed to provide stub definitions (stub.c) for some functions that aren't implemented by GCC nano lib (similar as for MSPM0):

#include <sys/stat.h>

// bare-metal stubs to eliminate Newlib-nano noise and errors
int _close(int file) { (void)file; return -1; }
int _fstat(int file, struct stat *st) { (void)file; st->st_mode = S_IFCHR; return 0; }
int _isatty(int file) { (void)file; return 1; }
int _lseek(int file, int ptr, int dir) { (void)file; (void)ptr; (void)dir; return 0; }
int _read(int file, char *ptr, int len) { (void)file; (void)ptr; (void)len; return 0; }
int _write(int file, char *ptr, int len) { (void)file; (void)ptr; (void)len; return 0; }
void _exit(int status) { (void)status; while(1); }
int _kill(pid_t pid, int sig) { (void)pid; (void)sig; return -1; }
pid_t _getpid(void) { return 1; }

It builds without using West, MCUXpresso VS Extensions. 
I need to have an SDK on the develop PC, and point to it with a variable:

In my case, I defined a CMake environment variable SDK_ROOT, pointing to C:/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard

Results:

[main] Building folder: c:/Users/jancu/workspace_vscode_nxp/ez-mcxn_hello_world/ez_mcxn_minimal/build 
[build] Starting build
[proc] Executing command: C:/Users/jancu/.pico-sdk/cmake/v4.2.1/bin/cmake.exe --build c:/Users/jancu/workspace_vscode_nxp/ez-mcxn_hello_world/ez_mcxn_minimal/build --config Debug --target all --
[build] [11/12 8% :: 0.221] Building ASM object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/gcc/startup_MCXN236.S.obj
[build] [11/12 16% :: 0.341] Building C object CMakeFiles/ez_mcxn_minimal.dir/stub.c.obj
[build] [11/12 25% :: 0.449] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/drivers/common/fsl_common.c.obj
[build] [11/12 33% :: 0.450] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/system_MCXN236.c.obj
[build] [11/12 41% :: 0.451] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/drivers/fsl_reset.c.obj
[build] [11/12 50% :: 0.481] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/drivers/gpio/fsl_gpio.c.obj
[build] [11/12 58% :: 0.491] Building C object CMakeFiles/ez_mcxn_minimal.dir/main.c.obj
[build] [11/12 66% :: 0.499] Building C object CMakeFiles/ez_mcxn_minimal.dir/board/pin_mux.c.obj
[build] [11/12 75% :: 0.510] Building C object CMakeFiles/ez_mcxn_minimal.dir/board/clock_config.c.obj
[build] [11/12 83% :: 0.523] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/drivers/mcx_spc/fsl_spc.c.obj
[build] [11/12 91% :: 0.581] Building C object CMakeFiles/ez_mcxn_minimal.dir/C_/Users/jancu/Documents/elektronica/nxp/sdk/mcxn236_noboard/mcxn236/mcuxsdk/devices/MCX/MCXN/MCXN236/drivers/fsl_clock.c.obj
[build] [12/12 100% :: 0.769] Linking C executable ez_mcxn_minimal; create bin executable: ez_mcxn_minimal.bin
[driver] Build completed: 00:00:00.830
[build] Build finished with exit code 0