Hi, I have a custom board with MK22FX512AVLK12. The MCUXpresso Pins and Clocks tools recognize this MCU however the Peripherals tool does not. It reports the following message:
This is surprising since the MCUXpresso Supported Devices Table (July2021) states Peripheral Tool is available for K22 product family.
Have I misconfigured something? I am not sure where to check other than project settings:
The real issue behind the need for peripheral tool is to get USB working on this MCU. I have tried example projects form FRDM-k22 and twrk21 and the code compiles, but I get "A request for the USB device descriptor failed." during enumeration attempt.
I think the clocks are ok:
but, from what I've read, K22 used in FRDM board does not have memory protection unit and I am not sure if the examples from K21 can run on K22. Any help would be greatly appreciated. Thanks!
Thanks to @myke_predko and @ErichStyger for quick response and getting me out of a ditch!
Starting from scratch with twrk21f120m_dev_cdc_vcom_lite_bm example proved to be a good strategy. As you can see COM7 showed up.
Here are the differences worth mentioning:
1) I had to copy sources folder in addition to copying usb and osa folders.
2) This time I used the lite version of the twrk21f120m_dev_cdc_vcom example. I am not sure if this is part of the reason it works now.
In summary here is what I have done to make this work (took around 30min, not counting days of previous work ;-))
Hopefully this will be helpful to the next person.
- download twrk21f120m_dev_cdc_vcom_lite_bm example
- create new project selecting processor used on my board K22FX512AVLK
- Configured MCU and package in project explorer
- Configure preprocessor terms
- Created the following source folders
- usb
- osa
- sources
- Copied files from the example to these folders
- Update includes to list the following folders
- Find virtual_com.c and comment out main function (you will have your own)
- Update clock config (see previous posts)
- Compile
- If you still have errors then then make sure that includes are all correct.
The short answer is that different Kinetis parts (even if they appear to be in the same series, ie MK22) have different SDKs and each SDK has access to different tools. Personally, I find the situation quite infuriating because the Freedom boards tend to have the latest (and greatest) SDK versions with full access to the various wizards (like the peripheral tool) while the vast majority of part numbers do not. I consider the most up to date SDKs only available on Freedom and, in some limited cases Tower, boards to be a form of bait and switch and I have been incredibly frustrated by it.
Now that I've had my rant let's talk about your situation.
I've done what you're trying to do and it's a non trivial exercise. You didn't say which USB device class you are trying to implement and that may be an issue, but in my experience implementing CDC on the MK22FX512xxxx & MK22FN1M0zxxx the "A request for the USB device descriptor failed." is most likely a clocking error but there could be other issues and it looks like you're on the right path to solving your problem.
First off, you didn't show the full clock wizard - Having a 48MHz USB clock out doesn't show the full story. Here is my clocking diagram for my MK221M0Axxxx implementation:
I personally find the clock wizard in MCUXpresso to be somewhat frustrating to work with as clicking different options does not always get the response you want or expect. You need a pretty good understanding of the clock module from the Reference Manual as well as the patience of Job to get a correct clock configuration.
Next you have to make sure your build preprocessor and includes have to be correct. You're looking in the right spot.
Finally, you have to have the right driver and resource includes available to your application.
As I said, it's a non-trivial exercise.
Fortunately there is a relatively easy solution to all this and that is to start with the example USB application from the TWRK-MK21F (which is what I believe is the recommended resource for the MK22FX but I'll leave it to the NXP support staff to confirm it) and start working from there.
Download the example application and verify that works on your device. From there, I recommend you create a new project with the same files taking note that you copy in "clock_config.c/.h" from the working project, the "usb" and "osa" folders (making sure they are "source folders" in your project) the USB source files and, finally, make sure your build preprocessor and includes match the example application. Test what you've done to make sure it still works, DOCUMENT WHAT YOU'VE DONE and then you can start modifying it to your own application.
As I was creating my (FreeRTOS) application, I maintained a list of setup/configuration instructions for each project, here's one from an early one to give you an idea of what's involved.
0. Have MK22_FRTOS_7a project available
1. Create Project:
SDK: MK22FN1M0Axxx12
Name: MK22_FRTOS_USB_8
Device Packages: MK22FN1M0AVMD12
Operating Systems: FreeRTOS
Drivers: adc
- clock
- common
- flash
- ftm
- gpio
- port
- sim
- smc
- sysmpu
- uart
CMSIS Drviers:
Utilities: assert
- debug_console
Middleware:
2. Setup IO Pins
Copy in MK22_FRTOS_USB_7a.mex
- Rename to renumber to "8" (the current project number)
- NOTE: No Clock Specification
- "Update Code" from the Pin Specification
3. Build and test.
- See "Hello World" in Debug Console
4. Replace "source" folder contents with "MK22_FRTOS_USB_7a" project's contents
- Rename "MK22_FRTOS_USB_7a" to "MK22_FRTOS_USB_8"
- Update "versionTracking.h" to indicate new project
5. Create "source folders" for:
- osa
- usb
And copy in the contents from the respective folders in "MK22_FRTOS_USB_8" project's folders
6. Replace in "board" folder:
- clock_config.c
- clock_config.h
With the files from the previous project
7. Open "Properties"=>"C/C++ Build"=>"Settings"=>"Preprocessor" and match the following terms:
__REDLIB__
CPU_MK22FN1M0AVMC12_cm4
CPU_MK22FN1M0AVMC12
_DEBUG=1
USB_STACK_FREERTOS
USB_STACK_FREERTOS_HEAP_SIZE=32768
FSL_RTOS_FREE_RTOS
SDK_DEBUGCONSOLE=0
CR_INTEGER_PRINTF
PRINTF_FLOAT_ENABLE=0
__MCUXPRESSO
__USE_CMSIS
DEBUG
8. Open "Properties"=>"C/C++ Build"=>"Settings"=>"Includes" and match the following includes:
"${workspace_loc:/${ProjName}/board}"
"${workspace_loc:/${ProjName}/source}"
"${workspace_loc:/${ProjName}/}"
"${workspace_loc:/${ProjName}/usb/device/source/khci}"
"${workspace_loc:/${ProjName}/usb/include}"
"${workspace_loc:/${ProjName}/osa}"
"${workspace_loc:/${ProjName}/drivers}"
"${workspace_loc:/${ProjName}/CMSIS}"
"${workspace_loc:/${ProjName}/freertos/include}"
"${workspace_loc:/${ProjName}/freertos/portable}"
"${workspace_loc:/${ProjName}/utilities}"
"${workspace_loc:/${ProjName}/startup}"
"${workspace_loc:/${ProjName}/usb/device/class/cdc}"
"${workspace_loc:/${ProjName}/usb/device/class}"
"${workspace_loc:/${ProjName}/usb/device/source}"
"${workspace_loc:/${ProjName}/usb/device/include}"
9. Build and test
- Check the operation of USB
Good luck!
@myke_predko, Thanks for the detailed explanation.
My project is a cdc virtual com device.
I reviewed my clock tree and it was very close to the one you posted. The only difference was the PLL (/2 *30) instead of (/3 * 45). I am not sure if it makes any difference.
I also went through my preprocessor terms and there were several diffs. One major diff is that I do not use RTOS in my project hence I had USB_STACK_BM. However I am not sure what to do about USB_STACK_FREERTOS_HEAP_SIZE=32768. I could spend time on converting my project to RTOS (this was something I always wanted to do), but I had my bare metal project already running on MK66 and this was an attempt to port it to a cheaper hardware. The process on MK66 was flawless, the example worked almost right out of the box. This also means I did not learn much
I did try the project with updated clock config and preprocessor terms, but there was no difference in behavior.
I wonder if part of the USB example is overriding the clock config. I'll try to decipher these two functions next:
In my adaptation of the twrk21 example I created a fresh project for my uC and then copied usb and osa folders and the virtual_com.c and virtual_com.h files. I did mark new folders as "source folders". After this the project compiled successfully. However the usb device would not enumerate.
I played with some breakpoints and I realized that USB_DeviceGetDeviceDescriptor function does not get called so the process is breaking before it hits this step.
Here is my clock config:
