topic Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M in Kinetis Microcontrollers

Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

MAPC — Thu, 20 Aug 2015 01:09:16 GMT

Hello,

I'm trying to run USB Stack v. 4.1.1 msd_mfs_generic demo on FRDM-K20D50M. This will be reference to develop a USB memory stick Datalogger for my application with this MCU.

Since this demo was developed for TWR-K20D50M, I changed the sci initialization in order to properly configure the SGC and MUX registers and meet Freedom hardware setup and select the correct UART associated with Open SDA CDC.

But it didn't work. Not even Attach event was detected. I still couldn't find where and how the failure ocurred during debugging.

When I run the same demo for TWR-K70 for example, it works perfectly.

Could anybody help me with this issue?

Thanks and regards,

Marco Coelho

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

yasuhikokoumoto — Thu, 20 Aug 2015 03:02:35 GMT

Hello Marco,

I am not sure I might be correct.

Did you connect J21 jumper pin?

Best regards,

Yasuhiko Koumoto.

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

MAPC — Thu, 20 Aug 2015 20:53:11 GMT

Hello, Dear Yasuhiko

Thanks for the tips.

I really forgot to mount this jumper on FRDM-K20D50M. But I just did it now and tried to run again. After mounting and shortening it I got the following screen:

Have you ever experienced something like that?

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

yasuhikokoumoto — Thu, 20 Aug 2015 23:57:39 GMT

Hello Paul,

it seems to occur the hard fault by some reasons.

Honestly speaking I have only an experience which I executes the simple USB sample codes which are included in the freescale package.

The hard fauld would hapen by several reason.

A USB sample code is too complicated to analyze if errors had occurred.

I'm very sorry but I cannot help you.

I would expect that experts will help you.

Best regards,

Yasuhiko Koumoto.

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

MAPC — Fri, 21 Aug 2015 00:24:54 GMT

Dear Yasuhiko,

I just ran the msd_mfs_generic demo code on a FRDM-K20D50M kit, as it is. So, I really can't understand this failure.

I'm trying to find the cause of this Hard Fault interrupt by debugging the code. But it is not easy!

Anyway, thank you very much!

Best regards,

Marco Coelho

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

Kan_Li — Fri, 21 Aug 2015 05:34:20 GMT

Hi Marco Coelho,

This case reminds me some bug I reported before, please kindly refer to [USB stack ver 4.1.1] a code issue in msd_mfs_generic host demo for details.

Hope that helps,

Have a great day,
Kan

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

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

MAPC — Fri, 21 Aug 2015 13:30:45 GMT

Dear Kan_Li

Thanks for the response.

Strange! This part appears in grey to me! What does this mean? And how can I fix it?

It seems like "__CWCC__" macro is not defined in the demo. Should I force it and just touch to see it?

Thanks and regards,

Marco Coelho

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

Kan_Li — Mon, 24 Aug 2015 05:46:32 GMT

Hi Marco Coelho,

The __CWCC__ is a predefined macro in CW IDE, and it is integrated in the compiler , and active during the compiling, so it might be inconvenient to read the code, but actually there is no need to define it in a project.

Have a great day,
Kan

Re: Problems to run USB stack v 4.1.1 msd_mfs_generic demo on FRDM-K20D50M

MAPC — Mon, 24 Aug 2015 15:40:36 GMT

Hi, Kan_Li

I still don't understand why this __CWCC__ is not automatically set in the demo. Do you have an idea of what might be causing this issue and how can I fix it?

Marco Coelho