FRDM-KL25Z: SDK missing a couple of files --?

[aaronm]

Hi

• FRDM-KL25Z
• SDK 2.2.0.

I'm trying to write an app that uses SPI SD & FatFS, but I can't even get the base program to compile: It's complaining of missing header files.  I've gone through the SDK selection tool a number of times, and I've searched through the SDK zip file looking for these two headers, in particular - there might be additional errors, once I resolve these two files - and I can't find them.  I see fsl_dspi.h exists in the SDK for the K66 board, and I could probably copy the missing files from there, but that seems a grievous hack.  The SDK should have whatever files it needs.

Or am I doing something wrong?

Thanks, Aaron

[aaronm]

Update: I copied the K66 fsl_dspi.c and fsl_dspi.h files from the K66 project to the K25, and that just caused a number of errors in missing definitions, and such.  So that didn't help.

[Celeste_Liu · Accepted solution]

Hello @aaronm ,

Thanks for your post and sorry for the late reply. I've been really busy recently.

I looked into it and found that the KL25Z indeed doesn't have a dspi driver file. This board is rather old and there probably won't be any plans to update it. Using the dspi driver from the K6x SDK is one option, but as you mentioned, it will lead to a lot of errors and we need to modify the code one by one to fix them. Another feasible approach is to look for open-source driver files, which might be more efficient.

Could you tell me where you are in the process now, or if you have any new ideas?

BRs,

Celeste

[aaronm]

Hi Celeste, and thanks for getting back to me.  Thanks for confirming the SDK omission: it's good to know I'm looking for something that doesn't exist.

I understand the chip is old, but the status says, "Active."  A buyer would think that that means it's safe to use the product.  I know this is not your call on product lines, so I don't hold you responsible, but that's how customers see it.

I'm going to plunge ahead and see if I can't get the SDK contents to work, anyway - somehow.  Barring that, I'll try the mbed libraries.  I remember mbed 2.0 used to be pretty useful.  I'll post back here if I get something to work so others can benefit.

Aaron