Hi Everyone,
First off, my apology for any silly questions as I am new to the world of programming MCU’s (I've taken some classes in C programming & some experience programming Arduinos). I’ve been reading around and watching YouTube tutorials, but still feel stranded, so I would be extremely grateful for any tips/suggestions, or if you know a more appropriate place to seek help.
An ex-employee worked on a project that I am picking up on. I have been trying to figure out how to compile and load the firmware onto MK20FX512VLQ12 using codewarrior & U-MULTILINK-FX-ND USB multilink debugger. I thought this would be a simple task, but I am running into problems building/compiling the project that I have not been able to resolve on my own.
I have all the c-source/ header files the ex-employee created, and I assume all of the code is correct since the employee had recently successfully programmed several boards. One limitation however is these files do not have an existing project folder, thus I am unable to import the project into codewarrior and have opted to trying to copy the files into a new project.
Upon attempting to build the project, I encountered a number of errors. I am thinking perhaps compiler paths are not set-up correctly in codewarrior or maybe the source/header files in the project are not organized in the correct folders. I've included details & screenshots below of how I have setup the project, and errors encountered:
Setting up the new project in codewarrior (screen shot attached):
Organizing files:
As I mentioned above, I already have all source & header files.
I copied all header files (.h) into “Project_Headers” folder & all source files (.c) into “Sources” folder.
Building the project (screenshot attached):
This is where I encounter a ton of errors; majority of build the errors are:
I have found UART_PDD.h & GPIO_PDD.h located in
C:\Freescale\CW MCU v10.7\MCU\ProcessorExpert\lib\Kinetis\pdd_100404\inc
The closest I could find to SPI_PDD.h is QSPI_PDD.h
From reading online, it seems maybe the problem is a compiler path is not set up correctly.
However I have not been able to figure out how to fix this.
Thank you again & regards,
Kayvon
Hello Kayvon
Your old project was based on Processor Expert.
Is it possible to get the whole project folder from your colleague? And copy it into your workspace, then import it into CodeWarrior.
For how to import the project, please refer to these links:
https://community.nxp.com/thread/395889
https://mcuoneclipse.com/2012/05/07/exporting-and-importing-projects-in-eclipse/
Best Regards
Fiona Kuang
TIC - Technical Information Center
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Mark Correct button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Fiona,
Thank you so much for your response. Seeing your reply, I now recall I had also looked into trying to import the project, until I realized there is no existing project folder to import. And unfortunately I am unable to get in touch with the colleague regarding said project folder, which is why I have opted to create a new project. Do you have any suggestions on how I might be able to compile the source/header files into a new project?
Thank you!
Kayvon
Hi,
the files such as xxx_LDD.h are generated by processor expert. if you create a normal project without processor expert and import those files, normally your project can not pass build.
I suggest you first try import your entire project directly. If you still can not do it, please create a case and send your project to NXP support. we will check the problem directly with the project.
https://community.nxp.com/docs/DOC-329745
Have a great day,
Jennie Zhang
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------