Zephyr ProjectのトピックRe: MCUXPRESSO Zephyr Custom Device Driver

MCUXPRESSO Zephyr Custom Device Driver

bretts — Tue, 25 Mar 2025 17:37:00 GMT

I'm trying to add support for a custom board and custom device drivers (I have an FRAM chip that is not supported). I have been able to get the custom board to build, but I cannot get my custom driver to build (or to get Kconfig invoked). I have the following tree:

Or alternate view:

I just need a template to get started with the custom drivers. I have found an example that is using west directly, but not the mcuxpresso build system. Does anyone have any experience with this?

Thank you,

Brett Swimley

Re: MCUXPRESSO Zephyr Custom Device Driver

Alondra — Tue, 25 Mar 2025 20:21:57 GMT

Hello Brett,
Which part number are you using?

Best regards

Re: MCUXPRESSO Zephyr Custom Device Driver

bretts — Tue, 25 Mar 2025 20:38:12 GMT

I am basing my custom board off the MIMXRT1024 (we have successfully used this in a previous project with MCUXpresso SDK and FreeRTOS). As a test, because I know we will eventually need it, I want to build a custom board, and I am trying to interface it to an SPI FRAM part (again, we have used this part previously). I cannot figure out how to get the project to recognize my custom driver directory. I looked at the example-application as part of the Zephyr project, but that uses west as the build system, and the application has a Kconfig file. Everytime I add a Kconfig file to my application root directory, I run into build errors.

Any thoughts?

Re: MCUXPRESSO Zephyr Custom Device Driver

bretts — Tue, 25 Mar 2025 20:39:20 GMT

I am tempted to just move to the "out of the box" zephyr development, rather than trying to use the visual studio code mcuxpresso extension.

Re: MCUXPRESSO Zephyr Custom Device Driver

diego_charles — Tue, 15 Apr 2025 16:53:46 GMT

Hi @bretts

My apologies for the delayed response.

To add custom driver, the simplest way is to edit the Cmakelist associated to your project.

This way, I created the most simple driver on the drivers folder.

Then I called the driver function on main and it worked. This is related to this.

https://cmake.org/cmake/help/latest/command/target_sources.html

I think it is okay for a single file, but for a complete directory not. So I think this could do better the job

https://cmake.org/cmake/help/latest/command/include_directories.html

If you want to include an nxp sdk driver , you could check out this post from Derek

https://community.nxp.com/t5/Zephyr-Project-Knowledge-Base/Using-MCUXpresso-SDK-drivers-in-a-Zephyr-application/ta-p/2077778

I hope this could help you!

Diego

Re: MCUXPRESSO Zephyr Custom Device Driver

ARosman — Thu, 12 Jun 2025 11:27:21 GMT

Hi,

Is this even supported in MCUXpresso for VSCODE? I followed some tutorial and it seems that the driver compiles correctly, but it doesn't link to the main app, returning undefined reference to '__device_dts_ord_xx'.

Any new information about how to build Custom drivers?

Ales