The Freescale MQX RTOS is transitioning to use the Kinetis Software Development Kit (KSDK), and there is a Beta release of MQX for KSDK available now. See Beta version of MQX RTOS for Kinetis SDK - Now Available. Processor Expert (PEx) is a code generation and configuration tool that is already integrated with KSDK. This post shows how PEx can be used with MQX for KSDK. This method is good for simple MQX projects just needing the kernel. PEx simplifies the project by adding the KSDK and MQX kernel files directly to the project.
These steps are written using MQX for KSDK v1.0.0 Beta. The Kinetis Design Studio (KDS) v1.1.1 toolchain is used, with example project attached. KDS has PEx integrated in the IDE and is used for this example, although the stand-alone tool Processor Expert Driver Suite v10.4 can be used with other toolchains. For help getting started with PEx, check out the videos at Processor Expert Tools in CodeWarrior 10.3 - Training Videos.
MQX for KSDK does not yet have any PEx projects installed with the release, but PEx can be used to create a project from scratch. First, ensure to follow the KDS release notes to have the KSDK plugins installed. Also, refer to the MQX documentation to ensure the latest MQX plugins are installed in KDS as well.
Now create a new project using the menu File->New. The New Project Wizard will walkthrough the project creation. Be sure to specify a Kinetis device that is supported by the KSDK, refer to KSDK release notes to see the available list of devices. For the "Rapid Application Development" screen, be sure to check both Kinetis SDK and Processor Expert.
Finish creating the project. After the project is created, use the Component Library to add the components MQX_KSDK and MQX_KSDK_Task. The project needs at least one MQX_KSDK_Task component, and more can be added for multiple tasks in the application.
After adding the MQX components, the Components View will show them included in the project. The MQX_KSDK properties can be customized if needed using the Component Inspector View. Each Task should be customized using the properties for the MQX_KSDK_Task components.
MQX uses stdin/stdout typically through a UART for IO functions like printf(). This can also be easily customized for the board being used. In this example, the project is written for the FRDM-K64F board, and uses the UART connected to the OpenSDA USB COM port. That board uses UART0 on pins PTB16 and PTB17. To configure in PEx, select the fsl_uart component, which is included as a sub-component under the MQX_KSDK component. Then, in the Component Inspector, change the Properties to use the needed UART peripheral and specify the pins. The other UART properties can also be customized if needed.
Other PEx components can be added as well to configure the peripheral drivers. Once the PEx configuration is complete, generate the code by clicking the Generate Code button in the Components View. This will generate the KSDK and MQX kernel code and add it directly to the project.
With the current releases, PEx will generate a warning in KDS when the code is generated. The GNU ISO C99 standard should be used when building MQX.
To change this compiler setting, right-click the project and select Properties. Then use this screenshot to find the Language Standard in the Compiler Optimization settings, and change to GNU ISO C99. Click OK to save the change.
Now the MQX application can be written. The MQX_KSDK_Task components will create function stubs for the tasks. The task routine prototypes are located in the project header file Sources/mqx_tasks.h and stubs of task functions are in source file Sources/mqx_tasks.c. Add the application code to these tasks. Then use the toolchain to build the project, and download to the target hardware.
The attached project is an example following these steps for KDS. It has a single MQX task that prints "Hello World!" out the UART using printf(). It's written for the FRDM-K64F board, and setup to use the Segger JLink OpenSDA V2 debugger app.
Original Attachment has been moved to: MQX_KSDK_PEx.zip
Hi Jason,
Processor Expert (PEx) does not provide the ability with MQX to add the other libraries for you, like the shell, MFS file system, RTCS TCP/IP or USB stacks. But you can manually add these libraries to the MQX project generated by PEx. That means changing the linker settings to add the library and change the compiler include paths for the library header files. You can refer to our MQX examples that use the shell or these libraries as an example for these settings, and as a reference for the source code in your application to use the library.
Below is an example of these project settings. I no longer have this older version of MQX for KSDK installed, which was the version used at the beginning of this post. But I'll use the latest MQX for KSDK v1.3 as an example. This is using the RTCS shell example installed at \KSDK_1.3.0\middleware\tcpip\rtcs\examples\shell\build\kds\shell_frdmk64f, and uses the Kinetis Design Studio (KDS) toolchain.
Here are the linker settings including the nshell library, and the path to that library:
And the compiler settings for the include path
Hello Derek Snell,
I followed your instructions but I have errors when building project.
Anybody could help me?
Regards,
Rémi
I wrote a walkthrough on my company's internal wiki. Here are the excerpts. I suppose you can probably just copy and paste into whatever eclipse's equivalent of a "solution" file is, but I am new to eclipse so I don't know.
Regarding something working out of the box, in some ways I agree, and in other ways I don't. If you want to just test the environment and libraries to see if they are capable of what you are looking for (before spending a lot of time on it), then yes, having something work out of the box is a plus. However, if you intend to work with an IDE long-term, it's probably best to figure out for yourself how to resolve all of the issues, so that you gain the background / insight / intuition to solve problems down the road.
Here's the text from my post:
In order to proceed, you'll need to install the following two packages:
In addition, you will need to overwrite the mbed firmware with one provided by Segger.
Now open KDS and import an existing project, and point to C:\Freescale\MQX_KSDK_1.0.0\tcpip\rtcs\examples\httpsrv\build\kds\httpsrv_frdmk64f120m. Try building it, and you'll end up with a bunch of compiler errors because gcc won't be able to find several header files. You need to add a bunch of file paths to the includes list.
To include the paths, go to Project Properties -> C/C++ Build -> Settings -> Cross ARM C Compiler -> Includes and then add the following paths:
"${KSDK_PATH}/rtos/mqx/mqx/source/bsp/K64F12"
"${KSDK_PATH}/boards/frdmk64f120m"
"${KSDK_PATH}/platform/system/hwtimer"
"${KSDK_PATH}/platform/osa"
"${KSDK_PATH}/rtos/mqx/mqx/source/bsp"
"${KSDK_PATH}/rtos/mqx/mqx/source/psp/cortex_m/compiler/gcc_arm"
"${KSDK_PATH}/rtos/mqx/mqx/source/psp/cortex_m"
"${KSDK_PATH}/rtos/mqx/mqx/source/include"
"${KSDK_PATH}/rtos/mqx/config/common"
"${KSDK_PATH}/rtos/mqx/config/mcu/mk64f120m"
"${KSDK_PATH}/rtos/mqx/config/board/frdmk64f120m"
"${KSDK_PATH}/tcpip/rtcs/source/include"
"${KSDK_PATH}/rtos/mqx/nshell/source/include"
where ${KSDK_PATH} is likely C:\Freescale\MQX_KSDK_1.0.0.
Build again, and you'll end up with the following linker errors:
arm-none-eabi-gcc: error: ..\..\..\..\..\..\..\..\lib\ksdk_mqx_lib\kds\K64F12\debug\ksdk_mqx_lib.a: No such file or directory
arm-none-eabi-gcc: error: ..\..\..\..\..\..\lib\frdmk64f120m.kds\debug\rtcs\rtcs.a: No such file or directory
arm-none-eabi-gcc: error: ..\..\..\..\..\..\..\..\rtos\mqx\lib\frdmk64f120m.kds\debug\nshell\nshell.a: No such file or directory
arm-none-eabi-gcc: error: ..\..\..\..\..\..\..\..\rtos\mqx\lib\frdmk64f120m.kds\debug\bsp\bsp.a: No such file or directory
arm-none-eabi-gcc: error: ..\..\..\..\..\..\..\..\rtos\mqx\lib\frdmk64f120m.kds\debug\psp\psp.a: No such file or directory
arm-none-eabi-gcc: error: ..\..\..\..\..\..\..\..\rtos\mqx\lib\frdmk64f120m.kds\debug\mqx_stdlib\mqx_stdlib.a: No such file or directory
Add the following projects to your KDS workspace and build them:
C:\Freescale\MQX_KSDK_1.0.0\lib\ksdk_mqx_lib\kds\K64F12
C:\Freescale\MQX_KSDK_1.0.0\tcpip\rtcs\build\kds\rtcs_frdmk64f120m
C:\Freescale\MQX_KSDK_1.0.0\rtos\mqx\nshell\build\kds\nshell_frdmk64f120m
C:\Freescale\MQX_KSDK_1.0.0\rtos\mqx\mqx\build\kds\bsp_frdmk64f120m
C:\Freescale\MQX_KSDK_1.0.0\rtos\mqx\mqx\build\kds\psp_frdmk64f120m
C:\Freescale\MQX_KSDK_1.0.0\rtos\mqx\mqx_stdlib\build\kds\mqx_stdlib_frdmk64f120m
Now go back and build httpsrv. You shouldn't get any errors. At this point, you need to change the IP address of the K64F. This is found in config.h.
To debug/run the application, right click httpsrv in the project view, then go to Debug As.. -> Debug Configurations. Double-click the "GDB SEGGER J-Link Debugging" node and it will auto-generate a configuration called "httpsrv_frdmk64f120m In Flash Debug" with all of the relevant information auto-populated.
Click Debug. You'll know it's working if you get this dialog:
Ignore this warning:
The debugger should have started in the paused state in main. Just click the Run icon to continue running. If you ping the IP that you had specified in config.h, it should work. In addition, you should be able to reach the mbed device via a web browser!
