Hello
I have problem witch creating custom board based on mimxrt1060_evk.
I do everything like was described in instruction (copy all files to my working_directory/boards/arm/board_name and changed all sample board names).
The application builds but does not link and returns an error: "... undefined reference to `dcd_data'"
It seems that creating a border in this way still requires linking sources:
zephyrproject/modules/hal/nxp/mcux/mcux-sdk/boards/evkmimxrt1060
Maybe there is a better, more generic way to do this?
@gronoarona Please take a look at this answer.
https://github.com/zephyrproject-rtos/zephyr/discussions/48746
Hi @gronoarona
Thanks a lot for reaching our technical support. I really appreciate your patience.
Regarding your issue, I would like to help you of course, but my best suggestion is to check with Zephyr forum or technical support on its site, because you will need those linking sources that we do not have.
Please let me know if you have more questions.
Best Regards.
Pablo Avalos.
Hello.
I think i found where is the problem.
~/zephyrproject/modules/hal/nxp/mcux/ there is quite a lot of CmakeList files which allow to handle only known dev-boards.
So if i'm right there are two solution:
1.Fast: Use config of known dev-board and if this don't makes problem leave this.
2. Slow and need quite wok: Create own board, basing on boards from: ~/zephyrproject/modules/hal/nxp/mcux/mcux-sdk/boards/.
Please tell me if i'm right and if there is better solution.
Hi @gronoarona
Thanks a lot for share your workaround.
I think you are correct, and there's not a better solution, so please, do you think you may mark you answer as solution or this one, please? I would highly appreciate it.
Thanks in advance.
Pablo Avalos.
Yes, I came to the same conclusion as you @gronoarona.
Creating a new board folder based on EVK could work from within ~/zephyrproject/modules/hal/nxp/mcux/mcux-sdk/boards/.
I am not sure how we can take it out of the tree for better tracking.
I am of the opinion that operating on source files provided by the manufacturer is not a good idea.
I think the best idea is to create your own CmakeList file in the custom board directories which will contain all the necessary sources.