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]

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);

[Hui_Ma]

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!
-----------------------------------------------------------------------------------------------------------------------

[wyflsxy]

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?

[Hui_Ma]

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

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

[wyflsxy]

MK64FN1M0VLL12

[Hui_Ma]

MK64 is using the RTC module.

So customer need to call the KSDK RTC driver.

Wish it helps.

Have a great day,
Ma Hui

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

[wyflsxy]

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

[Hui_Ma]

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

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

[wyflsxy]

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

[Hui_Ma · Accepted solution]

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

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

[wyflsxy]

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?

[Hui_Ma]

Hi,

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

Wish it helps.

Have a great day,
Ma Hui

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

[wyflsxy]

But I didn't found it in KSDK API 1.2,and there was not examples in the The directory？could you please tell me where or the Number of pages In the api about the usb,TCP/IP,filesystem stack and log?

[Hui_Ma]

Hi,

USB stack located at C:\Freescale\KSDK_1.2.0\usb, you could find USB example at [demo_apps] of each board.

Filesystem example could be found at C:\Freescale\KSDK_1.2.0\middleware\filesystem\mfs\examples

TCP/IP example could be found at C:\Freescale\KSDK_1.2.0\middleware\tcpip\rtcs\examples

Wish it helps.

Have a great day,
Ma Hui

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

[wyflsxy]

how about the API of log ?? I include the "log.h",and use the function about _log_write(), _log_read();

THE compiler error that:

"E:\Freescale\KSDK_1.2.0\rtos\mqx\mqx\source\include/log.h:36:2: error: #error LOG component is currently disabled in MQX kernel. Please set MQX_USE_LOGS to 1 in mqx_sdk_config.h and recompile kernel.

#error LOG component is currently disabled in MQX kernel. Please set MQX_USE_LOGS to 1 in mqx_sdk_config.h and recompile kernel.

"

but I didn't found MQX_USE_LOGS  in mqx_sdk_config.h

Does this belong to MQX API? can't I  use it ? If  I can't use the it of MQX API where I call use the API of  log in ksdk?

[Hui_Ma]

It just need manually add MQX_USE_LOGS definition in <mqx_sdk_config.h> file.

#define MQX_USE_LOGS 1

Have a great day,
Ma Hui

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

[wyflsxy]

Did it  belong to MQX API? you said that Customer can not use MQX provided driver???

[Hui_Ma]

Log  belongs to MQX RTOS component, which is not IO driver.

I said the MQX need to use KSDK driver, which could not call the MQX IO driver.

So, you could find log example at KSDK below folder:

C:\Freescale\KSDK_1.2.0\rtos\mqx\mqx\examples\log

Wish it helps.

Have a great day,
Ma Hui

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

[wyflsxy]

OK,I get it ,thank you~

[wyflsxy]

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?

[Hui_Ma]

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

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