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
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
I hope this could help you!
Diego
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
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?
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.