Kinetis Software Development KitのトピックRe: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Wed, 22 Jul 2015 08:31:57 GMT

Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

An example is defined in the API documentation

Void IRTC_DRV_Init ();

Void IRTC_DRV_Deinit ();

But KSDK repository "fsl_rtc_driver.h" file defined in indeed

Rtc_status_t RTC_DRV_Init (uint32_t instance);

Void RTC_DRV_Deinit (uint32_t instance);

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 03:04:33 GMT

Hi,

For Kinetis product with two RTC modules, most Kinetis product using RTC module, while such as KM family is using iRTC module.

That's why customer could find two RTC chapters at KSDK API Reference Manual document (Chpater 22 about IRTC; Chapter 33 about RTC).

Wish it helps.

Have a great day,
Ma Hui

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 03:18:24 GMT

In a project of MQX RTOS for Kinetis SDK in SDK3.0, could I use both API of MQX and KSDK?

which API should I priority to use?

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 04:38:13 GMT

It depends on which Kinetis product you are using.

Please let me know the Kinetis product part number, thank you.

Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 04:47:52 GMT

MK64FN1M0VLL12

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 05:08:02 GMT

MK64 is using the RTC module.

So customer need to call the KSDK RTC driver.

Wish it helps.

Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 05:33:33 GMT

How about other modules?

Such as the definition of "DATE_STRUCT" in MQX

The definition of "rtc_datetime_t" in KSDK

both of them Can be used, and with the similar definition

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 05:36:41 GMT

When integrate MQX with KSDK software, it can only use KSDK provided driver, not MQX I/O subsystem driver be supported.

Wish it helps.

Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 05:47:08 GMT

However I follow the MQXKSDKPUG.pkf to build the The static link library and associated with the project，could I use the MQX provided driver ？

MQX RTOS Lib

${KSDK_PATH}/rtos/mqx/mqx/build/kds/mqx_frdmk64f

${KSDK_PATH}/rtos/mqx/lib/frdmk64f.kds/debug/mqx/lib_mqx.a

MQX RTOS stdlib

${KSDK_PATH}/rtos/mqx/mqx_stdlib/build/kds/mqx_stdlib_frdmk64f

${KSDK_PATH}/rtos/mqx/lib/frdmk64f.kds/debug/mqx_stdlib/lib_mqx_stdlib.a

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 06:57:11 GMT

No, Customer can not use MQX provided driver.

5.3 Drivers

As MQX RTOS now uses the Kinetis SDK peripheral drivers and hardware abstraction layer, the application code needs to be updated for the Kinetis SDK driver APIs. The Kinetis SDK drivers offer similar functionality, and the porting effort involves changing the initialization of the drivers in the application, and changing the APIs used in the tasks.

Wish it helps.

Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 07:08:25 GMT

OK，thank you

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 07:59:37 GMT

I still have a question want to consult, the introduced of function for KSDK API don't tell me which head file it was definition in, how can I quickly find the header file I need to contains to call the function?

For example I want to call FlashInit () the function, which contains header files do I need?

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 08:23:38 GMT

Hi,

The KSDK driver with two level, one is HAL driver (low level), the other one is peripheral driver(high level).

The HAL driver header file name with *_hal.h, the peripheral driver header file name with _driver.h

Your mentioned FlashInit() function isn't a standard KSDK driver, there doesn't obey with this rule.

Wish it helps.

Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 08:45:59 GMT

the HAL driver is low level, the peripheral driver is high level, so usually I do the application development should be based on the peripheral driver, right?

Your mentioned FlashInit() function isn't a standard KSDK driver, there doesn't obey with this rule.

Since KSDK does not provide a certain module API interface, so what should I to do when I want to use these modules?

Such as FLASH module, what should I call FLASH read and write function,I didn't found it in ksdk_platform_lib_K64F12 library files.

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Thu, 23 Jul 2015 08:54:30 GMT

Usually, customer just need to call the peripheral driver.

While, for the special application, customer also could call the HAL driver.

The Flash driver is located at peripheral driver with different structure, which located at C:\Freescale\KSDK_1.2.0\platform\drivers\src\flash\C90TFS\drvsrc folder.

Customer could refer Flash example located at C:\Freescale\KSDK_1.2.0\examples\twrk64f120m\driver_examples\flash folder.

Wish it helps.
Have a great day,
Ma Hui

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Thu, 23 Jul 2015 09:08:25 GMT

when I include the # include "SSD_FTFx. h" according to the example , the compiler error said can't find the header files?

I have been configuration all these static library below in my project

Is there anything else I need to add?

MQX RTOS for KSDK Platform Lib
${KSDK_PATH}/lib/ksdk_mqx_lib/kds/K64F12
${KSDK_PATH}/lib/ksdk_mqx_lib/kds/K64F12/Debug/libksdk_platform_mqx.a
MQX RTOS Lib
${KSDK_PATH}/rtos/mqx/mqx/build/kds/mqx_frdmk64f
${KSDK_PATH}/rtos/mqx/lib/frdmk64f.kds/debug/mqx/lib_mqx.a
MQX RTOS stdlib
${KSDK_PATH}/rtos/mqx/mqx_stdlib/build/kds/mqx_stdlib_frdmk64f
${KSDK_PATH}/rtos/mqx/lib/frdmk64f.kds/debug/mqx_stdlib/lib_mqx_stdlib.a
MQX RTOS nShell Lib
${KSDK_PATH}/rtos/mqx/nshell/build/kds/nshell_frdmk64f
${KSDK_PATH}/rtos/mqx/lib/frdmk64f.kds/debug/nshell/lib_nshell.a
MFS File System
${KSDK_PATH}/filesystem/mfs/build/kds/mfs_frdmk64f
${KSDK_PATH}/filesystem/mfs/lib/frdmk64f.kds/debug/mfs/lib_mfs.a
RTCS
${KSDK_PATH}/tcpip/rtcs/build/kds/rtcs_frdmk64f
${KSDK_PATH}/tcpip/rtcs/lib/frdmk64f.kds/debug/rtcs/lib_rtcs.a
USB Host Lib
Porting an MQX RTOS Application to MQX RTOS for Kinetis SDK User’s Guide, Rev. 0, 03/2015
Freescale Semiconductor, Inc. 11
${KSDK_PATH}/usb/usb_core/host/build/kds/usbh_sdk_frdmk64f_mqx
${KSDK_PATH}/usb/usb_core/host/build/kds/usbh_sdk_frdmk64f_mqx/Debug/libusbh_mqx.

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Fri, 24 Jul 2015 02:39:15 GMT

It need to include the C90TFS driver with below path:

$PROJ_DIR$/../../../../../platform/drivers/src/flash/C90TFS/drvsrc/include

Wish it helps.

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Fri, 24 Jul 2015 02:53:24 GMT

i get it ,thank you very much!

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

wyflsxy — Mon, 27 Jul 2015 01:23:12 GMT

hello,As you said that Customer can not use MQX provided driver,what should I do when I want to used the USB or MFS or TCPIP whice support by MQX but not support by KSDK?

Re: Why the Kinetis SDK v. 1.2 API Reference Manual with code defined in function of the library file name will not be the same??

Hui_Ma — Mon, 27 Jul 2015 06:46:01 GMT

Hi,

KSDK also provides USB, TCP/IP and filesystem stack.

Wish it helps.

Have a great day,
Ma Hui