• State Accepted Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 23 subscribers
  • Views 1238 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?

eMMC 5.1 Middleware

Stephan Hilchenbach

Hello,

I connected an eMMC 5.1 memory of type KLMAG1JETD-B041 to a XMC4700 Relax-Kit evaluation board. Wehn I call fformat() or fmount() from the file system API, the functions return fsMediaError. I am using an SD-Card adapter to connect it. The memory ist working when connected to a PC. I tried a FAT32 formatted memory and a blank memory. Does the Middleware (v7.16)  file system support eMMC devices?

Best Regards,

Stephan

Parents
  • 0 in reply to Vladimir Umek

    Hello,

     

    when testing with our new hardware having eMMC populated, I get stuck in a function called mc_wfe() in the fs_mc_mci.c file. The description says, "Wait for event from MCI driver till 3 second timeout". The function calls fs_get_sys_tick_us(3000000) which returns the MCU clock frequency multiplied with 3 seconds, which is 432.000 on our 144MHz CPU. Then the function calls fs_get_sys_tick() which returns the RTOS ticks in milli-seconds. Then the functions wait's 432 seconds to timeout instead of 3 seconds. Can anybody confirm this behavior?

     

    Thanks in advance,

    Stephan

Reply
  • 0 in reply to Vladimir Umek

    Hello,

     

    when testing with our new hardware having eMMC populated, I get stuck in a function called mc_wfe() in the fs_mc_mci.c file. The description says, "Wait for event from MCI driver till 3 second timeout". The function calls fs_get_sys_tick_us(3000000) which returns the MCU clock frequency multiplied with 3 seconds, which is 432.000 on our 144MHz CPU. Then the function calls fs_get_sys_tick() which returns the RTOS ticks in milli-seconds. Then the functions wait's 432 seconds to timeout instead of 3 seconds. Can anybody confirm this behavior?

     

    Thanks in advance,

    Stephan

Children
No data