Issue in SDK, maybe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue in SDK, maybe

Jump to solution
604 Views
pietrodicastri
Senior Contributor II

Good morning

Building the SDK library with KDS, I see the ewm drivers are not part of the project, if built for processor K02F12810, but they are part if the processor is the K64.

The EWM module is present in both as well, so it seems a bug in the preparation of the library process... Is it??

 

 

Pietro

Labels (1)
0 Kudos
1 Solution
425 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Pietro:

I apologize for the long delay, it is hard to keep track of many posts.

I think there is indeed a defect with the K02 KSDK library projects. I reported this to our developers already (ticket KPSDK-5460).

The solution is very simple, just add the EWM driver and rebuild the platform library. For KDS these are the steps:

1. Open the library project.

2. Create a new folder inside of the platform folder called "ewm".

3. Create a virtual folder called "drivers" inside of the "ewm" folder.

4. Create a virtual folder called "hal" inside of the "ewm" folder.

5. Drag and drop the next files to the "drivers" folder:

C:\Freescale\KSDK_1.2.0\platform\drivers\inc\fsl_ewm_driver.h

C:\Freescale\KSDK_1.2.0\platform\drivers\src\ewm\fsl_ewm_common.c

C:\Freescale\KSDK_1.2.0\platform\drivers\src\ewm\fsl_ewm_driver.c

6. Drag and drop the next files to the "hal" folder:

C:\Freescale\KSDK_1.2.0\platform\hal\inc\fsl_ewm_hal.h

C:\Freescale\KSDK_1.2.0\platform\hal\src\ewm\fsl_ewm_hal.c

7. Finally build the library project.

With this you should be able to use the EWM driver from your application project once you link the platform library.

If I receive feedback from the developers I will let you know.

Regards!
Jorge Gonzalez

View solution in original post

0 Kudos
4 Replies
425 Views
pietrodicastri
Senior Contributor II

Ok

Thank You

0 Kudos
425 Views
pietrodicastri
Senior Contributor II

Hello Jorge

Did You analize the situation?

Thank You

0 Kudos
426 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Pietro:

I apologize for the long delay, it is hard to keep track of many posts.

I think there is indeed a defect with the K02 KSDK library projects. I reported this to our developers already (ticket KPSDK-5460).

The solution is very simple, just add the EWM driver and rebuild the platform library. For KDS these are the steps:

1. Open the library project.

2. Create a new folder inside of the platform folder called "ewm".

3. Create a virtual folder called "drivers" inside of the "ewm" folder.

4. Create a virtual folder called "hal" inside of the "ewm" folder.

5. Drag and drop the next files to the "drivers" folder:

C:\Freescale\KSDK_1.2.0\platform\drivers\inc\fsl_ewm_driver.h

C:\Freescale\KSDK_1.2.0\platform\drivers\src\ewm\fsl_ewm_common.c

C:\Freescale\KSDK_1.2.0\platform\drivers\src\ewm\fsl_ewm_driver.c

6. Drag and drop the next files to the "hal" folder:

C:\Freescale\KSDK_1.2.0\platform\hal\inc\fsl_ewm_hal.h

C:\Freescale\KSDK_1.2.0\platform\hal\src\ewm\fsl_ewm_hal.c

7. Finally build the library project.

With this you should be able to use the EWM driver from your application project once you link the platform library.

If I receive feedback from the developers I will let you know.

Regards!
Jorge Gonzalez

0 Kudos
425 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Pietro di Castri:

That seems indeed strange. Let me investigate it with the developers and I will let you know about any feedback I get.

Regards!

Jorge Gonzalez

0 Kudos