Slow writing fails on K64 with MFS and SDCard

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

Slow writing fails on K64 with MFS and SDCard

Jump to solution
1,630 Views
intertronic
Contributor II

Hi,

the MFS (KSDK 1.1.0) works without a problem if I open a file on sdcard, write to it and close it without delays.

But if I open it and then write every x seconds 32/64 bytes, the caching seems to catch it till 512 bytes.

The write command which matches the 512 byte limit, fails with errno 1.

Any suggestions?

Regards

Labels (1)
Tags (3)
0 Kudos
Reply
1 Solution
1,312 Views
intertronic
Contributor II

Hi Sol,

thanks for the suggestions but I think I found my problem.

I haven't noticed that the mfs-nio-driver also does some initializiation of the sdhc and sdcard.

My fault was to add a sdhc-pe-component to init it, but this causes some errors. It is curious that the system worked 90%.

If in the future the MFS will also be a pe-component, this combination should be checked/excluded.

I don't know if a check is now possible when pe and non-pe is mixed.

Regards

PS: I read some posts about people who changed clock and bit-width of the sdhc without any changes in performance. Maybe they also did the same like I and configured the sdhc-driver instead of the nio-sdhc-driver. ;-)

View solution in original post

0 Kudos
Reply
3 Replies
1,312 Views
soledad
NXP Employee
NXP Employee

Hello,

Are you using a Freescale board or a custom board?

Could you please share the code you are using? This is in order to test it.

Could you please test the example located at the path: \KSDK_1.1.0\filesystem\mfs\examples\sdcard?

Regards

Sol

0 Kudos
Reply
1,313 Views
intertronic
Contributor II

Hi Sol,

thanks for the suggestions but I think I found my problem.

I haven't noticed that the mfs-nio-driver also does some initializiation of the sdhc and sdcard.

My fault was to add a sdhc-pe-component to init it, but this causes some errors. It is curious that the system worked 90%.

If in the future the MFS will also be a pe-component, this combination should be checked/excluded.

I don't know if a check is now possible when pe and non-pe is mixed.

Regards

PS: I read some posts about people who changed clock and bit-width of the sdhc without any changes in performance. Maybe they also did the same like I and configured the sdhc-driver instead of the nio-sdhc-driver. ;-)

0 Kudos
Reply
1,312 Views
soledad
NXP Employee
NXP Employee

Thank you for your feedback.

Regards

Sol

0 Kudos
Reply