forked from Masmiseim36/nxpSDK
-
Notifications
You must be signed in to change notification settings - Fork 0
/
FRDM-K64F_manifest_v3_4.xml
11613 lines (11613 loc) · 792 KB
/
FRDM-K64F_manifest_v3_4.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<ksdk:manifest xmlns:ksdk="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="SDK_2.x_FRDM-K64F" name="FRDM-K64F" brief="This is SDK version 2.5.0 manifest file. It describes the content of the FRDM-K64F and additional settings for tools that support SDK version 2.5.0" format_version="3.4" api_version="2.0.0" configuration="78104fe283edf941d18a73e3ac7d8c2b" xsi:schemaLocation="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd http://nxp.com/mcuxpresso/sdk/sdk_manifest_v3.4.xsd">
<!--Timestamp (UTC): 2018-12-17 23:04:10.998962-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<externalDefinitions>
<definition extID="twrk64f120m"/>
<definition extID="hexiwear"/>
</externalDefinitions>
<ksdk id="MCUXpresso250" name="MCUXpresso250" version="2.5.0"/>
<compilers>
<compiler id="compiler_arm" name="arm" type="arm"/>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
<compiler id="compiler_iar" name="iar" type="iar"/>
</compilers>
<toolchainSettings>
<toolchainSetting id="com.nxp.mcuxpresso" name="mcuxpresso" version="10.3.0" full_name="MCUXpresso IDE" compiler="compiler_gcc" toolchain="mcuxpresso">
<option id="gnu.cpp.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.c.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.cpp.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.cpp.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="gnu.c.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
</toolchainSetting>
</toolchainSettings>
<toolchains>
<toolchain id="armgcc" name="GCC_ARM_Embedded" version="7.3.1" full_name="GCC ARM Embedded" compiler="compiler_gcc" type="armgcc" vendor="GCC ARM Embedded" vendor_url="http://launchpad.net/gcc-arm-embedded"/>
<toolchain id="mdk" name="Keil_MDK" version="5.26" full_name="Keil MDK" compiler="compiler_arm" type="mdk" vendor="ARM" vendor_url="http://www.arm.com"/>
<toolchain id="iar" name="IAR_Embedded_Workbench_for_ARM" version="8.32.1" full_name="IAR Embedded Workbench for ARM" compiler="compiler_iar" type="iar" vendor="IAR Systems" vendor_url="http://www.iar.com"/>
<toolchain id="mcuxpresso" name="MCUXpresso_IDE" version="10.3.0" full_name="MCUXpresso IDE" compiler="compiler_gcc" type="mcuxpresso" vendor="NXP Semiconductors" vendor_url="http://www.nxp.com">
<debug>
<debug_configuration id="com.crt.advproject.config.exe.release" name="Release Configuration" probe="LinkServer">
<scripts>
<script type="init" silent="false" emulators="${gdb.stub} -mi -info-emu">
<script>
set remotetimeout 60000
##target_extended_remote##
set mem inaccessible-by-default ${mem.access}
mon ondisconnect ${ondisconnect}
set arm force-mode thumb
${load}</script>
</script>
<script type="run" silent="false" emulators="${gdb.stub} -mi -info-emu">
<script>${run}</script>
</script>
</scripts>
<params>
<params id="vector.catch.release.mcuxpresso" name="vector.catch" value="false"/>
<params id="internal.cache.release.mcuxpresso" name="internal.cache" value="Disable"/>
</params>
</debug_configuration>
<debug_configuration id="com.crt.advproject.config.exe.debug" name="Debug Configuration" probe="LinkServer">
<scripts>
<script type="init" silent="false" emulators="${gdb.stub} -mi -info-emu">
<script>
set remotetimeout 60000
##target_extended_remote##
set mem inaccessible-by-default ${mem.access}
mon ondisconnect ${ondisconnect}
set arm force-mode thumb
${load}</script>
</script>
<script type="run" silent="false" emulators="${gdb.stub} -mi -info-emu">
<script>${run}</script>
</script>
</scripts>
<params>
<params id="vector.catch.debug.mcuxpresso" name="vector.catch" value="false"/>
<params id="internal.cache.debug.mcuxpresso" name="internal.cache" value="Disable"/>
</params>
</debug_configuration>
<debug_configuration id="com.nxp.mcuxpresso.core.debug.support.segger.debug" name="Debug Configuration" probe="Segger"/>
<debug_configuration id="com.nxp.mcuxpresso.core.debug.support.segger.release" name="Release Configuration" probe="Segger"/>
</debug>
</toolchain>
</toolchains>
<boards>
<board id="frdmk64f" name="FRDM-K64F" href="http://www.nxp.com/frdm-k64f" version="1.0.0" package="MK64FN1M0VLL12">
<description>FRDM-K64F: Freedom Development Platform for Kinetis K64, K63, and K24 MCUs</description>
<image path="docs/images" type="image">
<files mask="FRDM-K64F.gif"/>
</image>
<metadataSet>
<metadata key="html">
<specific>
<content>The Freedom-K64F is an ultra-low-cost development platform for Kinetis K64, K63, and K24 MCUsForm-factor compatible with the Arduino R3 pin layout. Peripherals enable rapid prototyping, including a 6-axis digital accelerometer and magnetometer to create full eCompass capabilities, a tri-colored LED and 2 user push-buttons for direct interaction, a microSD card slot, and connectivity using onboard Ethernet port and headers for use with Bluetooth® and 2.4 GHz radio add-on modules. OpenSDAv2, the NXP open source hardware embedded serial and debug adapter running an open source bootloader, offers options for serial communication, flash programming, and run-control debugging.</content>
</specific>
</metadata>
</metadataSet>
<examples>
<example id="frdmk64f_host_audio_speaker_freertos" name="host_audio_speaker_freertos" brief="The Host Audio example supports the audio speaker device. @n The application prints the audio speaker information when the USB speaker device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_audio_speaker/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_audio_speaker/freertos" type="xml">
<files mask="host_audio_speaker_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_cdc_freertos" name="host_cdc_freertos" brief="The host CDC project is a simple demonstration program based on the MCUXpresso SDK. It enumerates a COM port and echoes back the data from the UART ." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_cdc/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_cdc/freertos" type="xml">
<files mask="host_cdc_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_mouse_freertos" name="host_hid_mouse_freertos" brief="The application supports the mouse device. It prints the mouse operation when the mouse device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_mouse/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_mouse/freertos" type="xml">
<files mask="host_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_generic_freertos" name="host_hid_generic_freertos" brief="This application implements a simple HID interrupt in-and-out endpoint bi-directional communication.The application sends one test string to the device. The device receives and sends back the string. The application receives the string and prints it." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_generic/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_generic/freertos" type="xml">
<files mask="host_hid_generic_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_mouse_keyboard_freertos" name="host_hid_mouse_keyboard_freertos" brief="This example supports the mouse device and the keyboard device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_mouse_keyboard/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_mouse_keyboard/freertos" type="xml">
<files mask="host_hid_mouse_keyboard_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_msd_command_freertos" name="host_msd_command_freertos" brief="This Host MSD example supports the UFI and SCSI U-disk device. The application prints the attached device information when the U-disk device is attached.The application executes UFI commands to test the attached device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_msd_command/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_msd_command/freertos" type="xml">
<files mask="host_msd_command_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_msd_fatfs_freertos" name="host_msd_fatfs_freertos" brief="This Host FatFs example supports UFI and SCSI U-disk device. The application prints the attached device information when U-disk device is attached.The application executes some FatFs APIs to test the attached device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_msd_fatfs/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_msd_fatfs/freertos" type="xml">
<files mask="host_msd_fatfs_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_phdc_manager_freertos" name="host_phdc_manager_freertos" brief="The Host PHDC Manager Example is a simple demonstration program based on the MCUXpresso SDK.The application supports the USB weight scale device. It prints out the body mass and body mass index information when the USB weight scale device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_phdc_manager/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_phdc_manager/freertos" type="xml">
<files mask="host_phdc_manager_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_suspend_resume_hid_mouse_freertos" name="host_suspend_resume_hid_mouse_freertos" brief="This is one example support suspend/resume." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_suspend_resume_host_hid_mouse/freertos">
<external path="boards/frdmk64f/usb_examples/usb_suspend_resume_host_hid_mouse/freertos" type="xml">
<files mask="host_suspend_resume_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_printer_plain_text_freertos" name="host_printer_plain_text_freertos" brief="The host printer example demonstrates how to get the status of the printer deviceand how to print a certain test string.." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_printer_plain_text/freertos">
<external path="boards/frdmk64f/usb_examples/usb_host_printer_plain_text/freertos" type="xml">
<files mask="host_printer_plain_text_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_host_audio_speaker_bm" name="host_audio_speaker_bm" brief="The Host Audio example supports the audio speaker device. @n The application prints the audio speaker information when the USB speaker device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_audio_speaker/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_audio_speaker/bm" type="xml">
<files mask="host_audio_speaker_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_cdc_bm" name="host_cdc_bm" brief="The host CDC project is a simple demonstration program based on the MCUXpresso SDK. It enumerates a COM port and echoes back the data from the UART." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_cdc/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_cdc/bm" type="xml">
<files mask="host_cdc_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_mouse_bm" name="host_hid_mouse_bm" brief="The application supports the mouse device. It prints the mouse operation when the mouse device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_mouse/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_mouse/bm" type="xml">
<files mask="host_hid_mouse_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_generic_bm" name="host_hid_generic_bm" brief="This application implements a simple HID interrupt in-and-out endpoint bi-directional communication.The application sends one test string to the device. The device receives and sends back the string. The application receives the string and prints it." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_generic/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_generic/bm" type="xml">
<files mask="host_hid_generic_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_hid_mouse_keyboard_bm" name="host_hid_mouse_keyboard_bm" brief="This example supports the mouse device and the keyboard device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_hid_mouse_keyboard/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_hid_mouse_keyboard/bm" type="xml">
<files mask="host_hid_mouse_keyboard_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_msd_command_bm" name="host_msd_command_bm" brief="This Host MSD example supports the UFI and SCSI U-disk device. The application prints the attached device information when the U-disk device is attached.The application executes UFI commands to test the attached device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_msd_command/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_msd_command/bm" type="xml">
<files mask="host_msd_command_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_msd_fatfs_bm" name="host_msd_fatfs_bm" brief="This Host FatFs example supports UFI and SCSI U-disk device. The application prints the attached device information when U-disk device is attached.The application executes some FatFs APIs to test the attached device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_msd_fatfs/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_msd_fatfs/bm" type="xml">
<files mask="host_msd_fatfs_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_phdc_manager_bm" name="host_phdc_manager_bm" brief="The Host PHDC Manager Example is a simple demonstration program based on the MCUXpresso SDK.The application supports the USB weight scale device. It prints out the body mass and body mass index information when the USB weight scale device is attached." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_phdc_manager/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_phdc_manager/bm" type="xml">
<files mask="host_phdc_manager_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_suspend_resume_hid_mouse_bm" name="host_suspend_resume_hid_mouse_bm" brief="This is one example support suspend/resume." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_suspend_resume_host_hid_mouse/bm">
<external path="boards/frdmk64f/usb_examples/usb_suspend_resume_host_hid_mouse/bm" type="xml">
<files mask="host_suspend_resume_hid_mouse_bm.xml"/>
</external>
</example>
<example id="frdmk64f_host_printer_plain_text_bm" name="host_printer_plain_text_bm" brief="The host printer example demonstrates how to get the status of the printer deviceand how to print a certain test string." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_host_printer_plain_text/bm">
<external path="boards/frdmk64f/usb_examples/usb_host_printer_plain_text/bm" type="xml">
<files mask="host_printer_plain_text_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_mouse_freertos_static" name="dev_hid_mouse_freertos_static" brief="The USB HID mouse application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a mouse. Users can see the mouse arrow moving on the PC screen according in a rectangular fashion." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/freertos_static">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/freertos_static" type="xml">
<files mask="dev_hid_mouse_freertos_static.xml"/>
</external>
</example>
<example id="frdmk64f_dev_audio_generator_freertos" name="dev_audio_generator_freertos" brief="The USB Audio Generator application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a recording device and users can record the sound from this device via the "Sound Recorder" in the Windows Accessories." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_audio_generator/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_audio_generator/freertos" type="xml">
<files mask="dev_audio_generator_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vcom_freertos" name="dev_cdc_vcom_freertos" brief="The Virtual COM project is enumerated as a COM port, which the users can open using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom/freertos" type="xml">
<files mask="dev_cdc_vcom_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_vcom_cdc_vcom_freertos" name="dev_composite_cdc_vcom_cdc_vcom_freertos" brief="The Composite CDC_VCOM_CDC_VCOM project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as two COM port, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/freertos" type="xml">
<files mask="dev_composite_cdc_vcom_cdc_vcom_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vnic_freertos" name="dev_cdc_vnic_freertos" brief="The Virtual NIC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a network adapter. Users can access the network by properly configuring this network adapter." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic/freertos" type="xml">
<files mask="dev_cdc_vnic_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_freertos" name="dev_composite_cdc_msc_freertos" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a RAM disk, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The RAM disk can be formatted." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc/freertos" type="xml">
<files mask="dev_composite_cdc_msc_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_sdcard_freertos" name="dev_composite_cdc_msc_sdcard_freertos" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a RAM disk, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The RAM disk can be formatted." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard/freertos" type="xml">
<files mask="dev_composite_cdc_msc_sdcard_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_audio_freertos" name="dev_composite_hid_audio_freertos" brief="The USB Composite device application is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a recording device. Users can record the sound from this device via the "Sound Recorder" in the Windows Accessories with an HID mouse device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio/freertos" type="xml">
<files mask="dev_composite_hid_audio_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_mouse_hid_keyboard_freertos" name="dev_composite_hid_mouse_hid_keyboard_freertos" brief="The application is a simple demonstration program based on the MCUXpresso SDK. The application is enumerated as HID-compliant mouse and keyboard devices." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/freertos" type="xml">
<files mask="dev_composite_hid_mouse_hid_keyboard_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_mouse_freertos" name="dev_hid_mouse_freertos" brief="The USB HID mouse application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a mouse. Users can see the mouse arrow moving on the PC screen according in a rectangular fashion." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/freertos" type="xml">
<files mask="dev_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_generic_freertos" name="dev_hid_generic_freertos" brief="The USB HID generic application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a HID-compliant device. A PC application can be used to exchange data with the device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_generic/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_generic/freertos" type="xml">
<files mask="dev_hid_generic_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_ramdisk_freertos" name="dev_msc_ramdisk_freertos" brief="The USB MSC RAM disk application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk and can be read and written to as a normal U-disk ." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk/freertos" type="xml">
<files mask="dev_msc_ramdisk_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_sdcard_freertos" name="dev_msc_sdcard_freertos" brief="The USB MSC RAM SD card application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk. Users can read and write the SD card as a standard U-disk." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard/freertos" type="xml">
<files mask="dev_msc_sdcard_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_video_virtual_camera_freertos" name="dev_video_virtual_camera_freertos" brief="The USB video virtual camera application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a camera and users can see the video of the device by using a PC test tool." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera/freertos" type="xml">
<files mask="dev_video_virtual_camera_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_phdc_weighscale_freertos" name="dev_phdc_weighscale_freertos" brief="The USB PHDC WeighScale application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a weight scale device and the HealthLink software is used to interact with thisdevice to simulate the personal weight scale data, such as body mass and body mass index." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale/freertos" type="xml">
<files mask="dev_phdc_weighscale_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_suspend_resume_hid_mouse_freertos" name="dev_suspend_resume_hid_mouse_freertos" brief="the application is enumerated as a mouse. When host releases the USB Bus, the device will enter into low power mode. The device can be waked up when resume signal is detected on the bus. Or the device can remote wake-up the host by delivering the resume signal when the remote wake-up is enabled by the host." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse/freertos">
<external path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse/freertos" type="xml">
<files mask="dev_suspend_resume_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_printer_virtual_plain_text_freertos" name="dev_printer_virtual_plain_text_freertos" brief="The USB virtual printer application is a simple application to demonstrate a virtual printer functionality.Because there is no printer language parsing, the received raw data is output directly in the debug console.As a result, only plain text is suitable for testing. For other printer language support, such as postscript, implement the corresponding parser." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text/freertos">
<external path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text/freertos" type="xml">
<files mask="dev_printer_virtual_plain_text_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_mouse_bm" name="dev_hid_mouse_bm" brief="The USB HID mouse application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a mouse. Users can see the mouse arrow moving on the PC screen according in a rectangular fashion." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_mouse/bm" type="xml">
<files mask="dev_hid_mouse_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_audio_generator_bm" name="dev_audio_generator_bm" brief="The USB Audio Generator application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a recording device and users can record the sound from this device via the "Sound Recorder" in the Windows Accessories." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_audio_generator/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_audio_generator/bm" type="xml">
<files mask="dev_audio_generator_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_audio_generator_lite_bm" name="dev_audio_generator_lite_bm" brief="The USB Audio Generator application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a recording device and users can record the sound from this device via the "Sound Recorder" in the Windows Accessories." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_audio_generator_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_audio_generator_lite/bm" type="xml">
<files mask="dev_audio_generator_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_vcom_cdc_vcom_bm" name="dev_composite_cdc_vcom_cdc_vcom_bm" brief="The Composite CDC_VCOM_CDC_VCOM project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as two COM port, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/bm" type="xml">
<files mask="dev_composite_cdc_vcom_cdc_vcom_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_vcom_cdc_vcom_lite_bm" name="dev_composite_cdc_vcom_cdc_vcom_lite_bm" brief="The Composite CDC_VCOM_CDC_VCOM project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as two COM port, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom_lite/bm" type="xml">
<files mask="dev_composite_cdc_vcom_cdc_vcom_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vcom_bm" name="dev_cdc_vcom_bm" brief="The Virtual COM project is enumerated as a COM port, which the users can open using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom/bm" type="xml">
<files mask="dev_cdc_vcom_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vcom_lite_bm" name="dev_cdc_vcom_lite_bm" brief="The Virtual COM project enumerated as a COM port, which the users can open using terminal tools, such as TeraTerm. The demo echoes back any character it receives." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vcom_lite/bm" type="xml">
<files mask="dev_cdc_vcom_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vnic_bm" name="dev_cdc_vnic_bm" brief="The Virtual NIC project is enumerated as a network adapter. Users can access the network by properly configuring this network adapter." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic/bm" type="xml">
<files mask="dev_cdc_vnic_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_cdc_vnic_lite_bm" name="dev_cdc_vnic_lite_bm" brief="The Virtual NIC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a network adapter. Users can access the network by properly configuring this network adapter." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_cdc_vnic_lite/bm" type="xml">
<files mask="dev_cdc_vnic_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_bm" name="dev_composite_cdc_msc_bm" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a RAM disk, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The RAM disk can be formatted.." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc/bm" type="xml">
<files mask="dev_composite_cdc_msc_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_lite_bm" name="dev_composite_cdc_msc_lite_bm" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a RAM disk, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The RAM disk can be formatted." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_lite/bm" type="xml">
<files mask="dev_composite_cdc_msc_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_sdcard_bm" name="dev_composite_cdc_msc_sdcard_bm" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a RAM disk, which can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The RAM disk can be formatted." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard/bm" type="xml">
<files mask="dev_composite_cdc_msc_sdcard_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_cdc_msc_sdcard_lite_bm" name="dev_composite_cdc_msc_sdcard_lite_bm" brief="The Composite CDC_MSC project is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a COM port and a U-disk. The COM port can be opened using terminal tools, such as TeraTerm. The demo echoes back any character it receives. The U-disk can be read and write as a standard SD card." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_cdc_msc_sdcard_lite/bm" type="xml">
<files mask="dev_composite_cdc_msc_sdcard_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_audio_bm" name="dev_composite_hid_audio_bm" brief="The USB Composite device application is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a recording device. Users can record the sound from this device via the "Sound Recorder" in the Windows Accessories with an HID mouse device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio/bm" type="xml">
<files mask="dev_composite_hid_audio_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_audio_lite_bm" name="dev_composite_hid_audio_lite_bm" brief="The USB Composite device application is a simple demonstration program based on the MCUXpresso SDK. It is enumerated as a recording device. Users can record the sound from this device via the "Sound Recorder" in the Windows Accessories with an HID mouse device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_audio_lite/bm" type="xml">
<files mask="dev_composite_hid_audio_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_mouse_hid_keyboard_bm" name="dev_composite_hid_mouse_hid_keyboard_bm" brief="The application is a simple demonstration program based on the MCUXpresso SDK. The application is enumerated as HID-compliant mouse and keyboard devices." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/bm" type="xml">
<files mask="dev_composite_hid_mouse_hid_keyboard_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_composite_hid_mouse_hid_keyboard_lite_bm" name="dev_composite_hid_mouse_hid_keyboard_lite_bm" brief="The application is a simple demonstration program based on the MCUXpresso SDK. The application is enumerated as HID-compliant mouse and keyboard devices." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_composite_hid_mouse_hid_keyboard_lite/bm" type="xml">
<files mask="dev_composite_hid_mouse_hid_keyboard_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_mouse_lite_bm" name="dev_hid_mouse_lite_bm" brief="The USB HID mouse application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a mouse. Users can see the mouse arrow moving on the PC screen according in a rectangular fashion." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_mouse_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_mouse_lite/bm" type="xml">
<files mask="dev_hid_mouse_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_generic_bm" name="dev_hid_generic_bm" brief="The USB HID generic application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a HID-compliant device. A PC application can be used to exchange data with the device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_generic/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_generic/bm" type="xml">
<files mask="dev_hid_generic_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_hid_generic_lite_bm" name="dev_hid_generic_lite_bm" brief="The USB HID generic application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a HID-compliant device. A PC application can be used to exchange data with the device." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_hid_generic_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_hid_generic_lite/bm" type="xml">
<files mask="dev_hid_generic_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_ramdisk_bm" name="dev_msc_ramdisk_bm" brief="The USB MSC RAM disk application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk and can be read and written to as a normal U-disk ." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk/bm" type="xml">
<files mask="dev_msc_ramdisk_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_ramdisk_lite_bm" name="dev_msc_ramdisk_lite_bm" brief="The USB MSC RAM disk application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk and can be read and written to as a normal U-disk ." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_ramdisk_lite/bm" type="xml">
<files mask="dev_msc_ramdisk_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_sdcard_bm" name="dev_msc_sdcard_bm" brief="The USB MSC RAM SD card application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk. Users can read and write the SD card as a standard U-disk." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard/bm" type="xml">
<files mask="dev_msc_sdcard_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_msc_sdcard_lite_bm" name="dev_msc_sdcard_lite_bm" brief="The USB MSC RAM SD card application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a U-disk. Users can read and write the SD card as a standard U-disk." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_msc_sdcard_lite/bm" type="xml">
<files mask="dev_msc_sdcard_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_video_virtual_camera_bm" name="dev_video_virtual_camera_bm" brief="The USB video virtual camera application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a camera and users can see the video of the device by using a PC test tool." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera/bm" type="xml">
<files mask="dev_video_virtual_camera_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_video_virtual_camera_lite_bm" name="dev_video_virtual_camera_lite_bm" brief="The USB video virtual camera application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a camera and users can see the video of the device by using a PC test tool." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_video_virtual_camera_lite/bm" type="xml">
<files mask="dev_video_virtual_camera_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_phdc_weighscale_bm" name="dev_phdc_weighscale_bm" brief="The USB PHDC WeighScale application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a weight scale device and the HealthLink software is used to interact with thisdevice to simulate the personal weight scale data, such as body mass and body mass index." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale/bm" type="xml">
<files mask="dev_phdc_weighscale_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_phdc_weighscale_lite_bm" name="dev_phdc_weighscale_lite_bm" brief="The USB PHDC WeighScale application is a simple demonstration program based on the MCUXpresso SDK.It is enumerated as a weight scale device and the HealthLink software is used to interact with thisdevice to simulate the personal weight scale data, such as body mass and body mass index." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_phdc_weighscale_lite/bm" type="xml">
<files mask="dev_phdc_weighscale_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_suspend_resume_hid_mouse_bm" name="dev_suspend_resume_hid_mouse_bm" brief="the application is enumerated as a mouse. When host releases the USB Bus, the device will enter into low power mode. The device can be waked up when resume signal is detected on the bus. Or the device can remote wake-up the host by delivering the resume signal when the remote wake-up is enabled by the host." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse/bm">
<external path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse/bm" type="xml">
<files mask="dev_suspend_resume_hid_mouse_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_suspend_resume_hid_mouse_lite_bm" name="dev_suspend_resume_hid_mouse_lite_bm" brief="the application is enumerated as a mouse. When host releases the USB Bus, the device will enter into low power mode. The device can be waked up when resume signal is detected on the bus. Or the device can remote wake-up the host by delivering the resume signal when the remote wake-up is enabled by the host." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_suspend_resume_device_hid_mouse_lite/bm" type="xml">
<files mask="dev_suspend_resume_hid_mouse_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_printer_virtual_plain_text_bm" name="dev_printer_virtual_plain_text_bm" brief="The USB virtual printer application is a simple application to demonstrate a virtual printer functionality.Because there is no printer language parsing, the received raw data is output directly in the debug console.As a result, only plain text is suitable for testing. For other printer language support, such as postscript, implement the corresponding parser." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text/bm" type="xml">
<files mask="dev_printer_virtual_plain_text_bm.xml"/>
</external>
</example>
<example id="frdmk64f_dev_printer_virtual_plain_text_lite_bm" name="dev_printer_virtual_plain_text_lite_bm" brief="The USB virtual printer application is a simple application to demonstrate a virtual printer functionality.Because there is no printer language parsing, the received raw data is output directly in the debug console.As a result, only plain text is suitable for testing. For other printer language support, such as postscript, implement the corresponding parser." toolchain="armgcc iar mcuxpresso mdk" category="usb_examples" path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text_lite/bm">
<external path="boards/frdmk64f/usb_examples/usb_device_printer_virtual_plain_text_lite/bm" type="xml">
<files mask="dev_printer_virtual_plain_text_lite_bm.xml"/>
</external>
</example>
<example id="frdmk64f_led_demo_freedom_0000" name="led_demo_freedom_0000" brief="The led_demo_freedom_0000 is a led blinky application load at the beginning of the target flash memory on the Freedom platform. The led demo project is an example demo firmware applications used to demonstrate how the MCU bootloader can load and launch user applications." toolchain="iar mcuxpresso mdk" category="bootloader_examples/demo_apps" path="boards/frdmk64f/bootloader_examples/demo_apps/led_demo_freedom_0000">
<external path="boards/frdmk64f/bootloader_examples/demo_apps/led_demo_freedom_0000" type="xml">
<files mask="led_demo_freedom_0000.xml"/>
</external>
</example>
<example id="frdmk64f_led_demo_freedom_a000" name="led_demo_freedom_a000" brief="The led_demo_freedom_a000 is a led blinky application load at offset 0xa000 of the target flash memory on the Freedom platform. The led demo project is an example demo firmware applications used to demonstrate how the MCU bootloader can load and launch user applications." toolchain="iar mcuxpresso mdk" category="bootloader_examples/demo_apps" path="boards/frdmk64f/bootloader_examples/demo_apps/led_demo_freedom_a000">
<external path="boards/frdmk64f/bootloader_examples/demo_apps/led_demo_freedom_a000" type="xml">
<files mask="led_demo_freedom_a000.xml"/>
</external>
</example>
<example id="frdmk64f_flashloader_loader" name="flashloader_loader" brief="The flashloader_loader is a bootstrap loader that executes from flash memory on either the Freedom or Tower platform. This loader copies an image of the flashloader into RAM, then executes the flashloader from RAM. The flashloader_loader project uses the output of the flashloader build to create the flashloader image to load into RAM. Therefore, the flashloader project must be built before building the flashloader_loader project. Also, install Python27 for successful flashloader image generation." toolchain="iar mcuxpresso mdk" category="bootloader_examples" path="boards/frdmk64f/bootloader_examples/flashloader_loader">
<external path="boards/frdmk64f/bootloader_examples/flashloader_loader" type="xml">
<files mask="flashloader_loader.xml"/>
</external>
</example>
<example id="frdmk64f_freedom_bootloader" name="freedom_bootloader" brief="The freedom_bootloader is a bootloader that executes from target flash memory on the Freedom platform. The bootloader is a configurable flash programming utility that operates over a serial connection on MCU devices. It enables quick and easy programming of MCU devices through the entire product life cycle, including application development, final product manufacturing, and more.Host-side command line and GUI tools are available to communicate with the bootloader. Users can utilize host tools to upload and/or download application code via the bootloader." toolchain="iar mcuxpresso mdk" category="bootloader_examples" path="boards/frdmk64f/bootloader_examples/freedom_bootloader">
<external path="boards/frdmk64f/bootloader_examples/freedom_bootloader" type="xml">
<files mask="freedom_bootloader.xml"/>
</external>
</example>
<example id="frdmk64f_flashloader" name="flashloader" brief="The flashloader is a bootloader that executes from target RAM memory on the platform. The bootloader is a configurable flash programming utility that operates over a serial connection on MCU devices. It enables quick and easy programming of MCU devices through the entire product life cycle, including application development, final product manufacturing, and more.Host-side command line and GUI tools are available to communicate with the bootloader. Users can utilize host tools to upload and/or download application code via the bootloader." toolchain="iar mcuxpresso mdk" category="bootloader_examples" path="boards/frdmk64f/bootloader_examples/flashloader">
<external path="boards/frdmk64f/bootloader_examples/flashloader" type="xml">
<files mask="flashloader.xml"/>
</external>
</example>
<example id="frdmk64f_sigfox_console" name="sigfox_console" toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/sigfox_console">
<external path="boards/frdmk64f/demo_apps/sigfox_console" type="xml">
<files mask="sigfox_console.xml"/>
</external>
</example>
<example id="frdmk64f_hello_world" name="hello_world" brief="The Hello World demo application provides a sanity check for the new SDK build environments and board bring up. The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers. The purpose of this demo is toshow how to use the UART, and to provide a simple project for debugging and further development." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/hello_world">
<external path="boards/frdmk64f/demo_apps/hello_world" type="xml">
<files mask="hello_world.xml"/>
</external>
</example>
<example id="frdmk64f_hello_world_virtual_com" name="hello_world_virtual_com" brief="The Hello World demo application provides a sanity check for the new SDK build environments and board bring up. The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers. The purpose of this demo is toshow how to use the UART, and to provide a simple project for debugging and further development." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/hello_world_virtual_com">
<external path="boards/frdmk64f/demo_apps/hello_world_virtual_com" type="xml">
<files mask="hello_world_virtual_com.xml"/>
</external>
</example>
<example id="frdmk64f_sdcard_polling" name="sdcard_polling" brief="The SDCARD Polling project is a demonstration program that uses the SDK software. It reads/writes/erases the SD card continusly. The purpose of this example is to show how to use SDCARD driver andshow how to use polling based transfer API in SDHC driver in SDK software to access SD card.Note: If DATA3 is used as the card detect PIN, please make sure DATA3 is pull down, no matter internal or external, at the same time, make sure the card can pull DATA3 up, then host can detect card through DATA3.And SDHC do not support detect card through CD by host, card can be detected through DATA3 or GPIO.No matter detect card through host or gpio, make sure the pinmux configuration is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/sdcard" path="boards/frdmk64f/driver_examples/sdcard/polling">
<external path="boards/frdmk64f/driver_examples/sdcard/polling" type="xml">
<files mask="sdcard_polling.xml"/>
</external>
</example>
<example id="frdmk64f_sdcard_interrupt" name="sdcard_interrupt" brief="The SDCARD Interrupt project is a demonstration program that uses the SDK software. It reads/writes/erases the SD card continusly. The purpose of this example is to show how to use SDCARD driver andshow how to use interrupt based transfer API in SDHC driver in SDK software to access SD card.Note: If DATA3 is used as the card detect PIN, please make sure DATA3 is pull down, no matter internal or external, at the same time, make sure the card can pull DATA3 up, then host can detect card through DATA3.And SDHC do not support detect card through CD by host, card can be detected through DATA3 or GPIO.No matter detect card through host or gpio, make sure the pinmux configuration is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/sdcard" path="boards/frdmk64f/driver_examples/sdcard/interrupt">
<external path="boards/frdmk64f/driver_examples/sdcard/interrupt" type="xml">
<files mask="sdcard_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_fatfs_sdcard" name="fatfs_sdcard" brief="The SDCARD FATFS project is a demonstration program that uses the SDK software. Tt mounts a file system based on a SD card then does "creat directory/read directory/create file/write file/read file"operation. The file sdhc_config.h has default SDHC configuration which can be adjusted to let carddriver has different performance. The purpose of this example is to show how to use SDCARD driver based FATFS disk in SDK software." toolchain="armgcc iar mcuxpresso mdk" category="fatfs_examples/fatfs_sdcard" path="boards/frdmk64f/fatfs_examples/fatfs_sdcard">
<external path="boards/frdmk64f/fatfs_examples/fatfs_sdcard" type="xml">
<files mask="fatfs_sdcard.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_dspi" name="freertos_dspi" brief="The freertos_dspi example shows how to use DSPI driver in FreeRTOS:In this example , one dspi instance used as DSPI master with blocking and another dspi instance used as DSPI slave .1. DSPI master sends/receives data using task blocking calls to/from DSPI slave. (DSPI Slave uses interrupt to receive/send the data)" toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_dspi">
<external path="boards/frdmk64f/rtos_examples/freertos_dspi" type="xml">
<files mask="freertos_dspi.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_event" name="freertos_event" brief="This document explains the freertos_event example. It shows how task waits for an event (defined setof bits in event group). This event can be set by any other process or interrupt in the system.The example application creates three tasks. Two write tasks write_task_1 and write_task_2continuously setting event bit 0 and bit 1.Read_task is waiting for any event bit and printing actual state on console. Event bits areautomatically cleared after read task is entered.Three possible states can occurre:Both bits are set.zBit B0 is set.Bit B1 is set." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_event">
<external path="boards/frdmk64f/rtos_examples/freertos_event" type="xml">
<files mask="freertos_event.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_generic" name="freertos_generic" brief="This document explains the freertos_generic example. It is based on code FreeRTOS documentation fromhttp://www.freertos.org/Hardware-independent-RTOS-example.html. It shows combination of severaltasks with queue, software timer, tick hook and semaphore.The example application creates three tasks. The prvQueueSendTask periodically sending data toxQueue queue. The prvQueueReceiveTask is waiting for incoming message and counting number ofreceived messages. Task prvEventSemaphoreTask is waiting for xEventSemaphore semaphore given fromvApplicationTickHook. Tick hook give semaphore every 500 ms.Other hook types used for RTOS and resource statistics are also demonstrated in example:* vApplicationIdleHook* vApplicationStackOverflowHook* vApplicationMallocFailedHook" toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_generic">
<external path="boards/frdmk64f/rtos_examples/freertos_generic" type="xml">
<files mask="freertos_generic.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_hello" name="freertos_hello" brief="The Hello World project is a simple demonstration program that uses the SDK UART drivere incombination with FreeRTOS. The purpose of this demo is to show how to use the debug console and toprovide a simple project for debugging and further development.The example application creates one task called hello_task. This task print "Hello world." messagevia debug console utility and suspend itself." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_hello">
<external path="boards/frdmk64f/rtos_examples/freertos_hello" type="xml">
<files mask="freertos_hello.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_i2c" name="freertos_i2c" brief="The freertos_i2c example shows an application using RTOS tasks with I2C driver:The example supports 2 different connections:On board connection and board to board connection.With one board connection, 2 I2C instances of the same board are used. One i2c instance used as I2C master and another I2C instance used as I2C slave . Default settings in freertos_i2c.c (in folder boards/<board>/rtos_examples/freertos_i2c) is applied. Two tasks are created. One task is associated with an I2C master operation and another task deals with I2C slave operation. 1. I2C master task sends data to I2C slave task. 2. I2C master task reads data sent back from I2C slave task. The transmit data and the receive data of both I2C master task and I2C slave task are printed out on terminal.With board to board connection, one I2C instance on one board is used as I2C master and the I2C instance on other board is used as I2C slave. Tasks are created to run on each board to handle I2C communication. File freertos_i2c.c should have following definitions: #define EXAMPLE_CONNECT_I2C BOARD_TO_BOARD For board used as I2C master: #define I2C_MASTER_SLAVE isMASTER For board used as I2C slave: #define I2C_MASTER_SLAVE isSLAVE" toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_i2c">
<external path="boards/frdmk64f/rtos_examples/freertos_i2c" type="xml">
<files mask="freertos_i2c.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_mutex" name="freertos_mutex" brief="This document explains the freertos_mutex example. It shows how mutex manage access to commonresource (terminal output).The example application creates two identical instances of write_task. Each task will lock the mutexbefore printing and unlock it after printing to ensure that the outputs from tasks are not mixedtogether.The test_task accept output message during creation as function parameter. Output message have twoparts. If xMutex is unlocked, the write_task_1 acquire xMutex and print first part of message. Thenrescheduling is performed. In this moment scheduler check if some other task could run, but secondtask write_task+_2 is blocked because xMutex is already locked by first write task. The firstwrite_task_1 continue from last point by printing of second message part. Finaly the xMutex isunlocked and second instance of write_task_2 is executed." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_mutex">
<external path="boards/frdmk64f/rtos_examples/freertos_mutex" type="xml">
<files mask="freertos_mutex.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_queue" name="freertos_queue" brief="This document explains the freertos_queue example. This example introduce simple logging mechanismbased on message passing.Example could be devided in two parts. First part is logger. It contain three tasks:log_add().....Add new message into the log. Call xQueueSend function to pass new message into message queue.log_init()....Initialize logger (create logging task and message queue log_queue).log_task()....Task responsible for printing of log output.Second part is application of this simple logging mechanism. Each of two tasks write_task_1 andwrite_task_2 print 5 messages into log." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_queue">
<external path="boards/frdmk64f/rtos_examples/freertos_queue" type="xml">
<files mask="freertos_queue.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_sem" name="freertos_sem" brief="This document explains the freertos_sem example, what to expect when running it and a briefintroduction to the API. The freertos_sem example code shows how semaphores works. Two differenttasks are synchronized in bilateral rendezvous model.The example uses four tasks. One producer_task and three consumer_tasks. The producer_task starts bycreating of two semaphores (xSemaphore_producer and xSemaphore_consumer). These semaphores controlaccess to virtual item. The synchronization is based on bilateral rendezvous pattern. Both ofconsumer and producer must be prepared to enable transaction." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_sem">
<external path="boards/frdmk64f/rtos_examples/freertos_sem" type="xml">
<files mask="freertos_sem.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_sem_static" name="freertos_sem_static" brief="This document explains the freertos_sem example, what to expect when running it and a briefintroduction to the API. The freertos_sem example code shows how semaphores works. Two differenttasks are synchronized in bilateral rendezvous model.The example uses four tasks. One producer_task and three consumer_tasks. The producer_task starts bycreating of two semaphores (xSemaphore_producer and xSemaphore_consumer). These semaphores controlaccess to virtual item. The synchronization is based on bilateral rendezvous pattern. Both ofconsumer and producer must be prepared to enable transaction." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_sem_static">
<external path="boards/frdmk64f/rtos_examples/freertos_sem_static" type="xml">
<files mask="freertos_sem_static.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_swtimer" name="freertos_swtimer" brief="This document explains the freertos_swtimer example. It shows usage of software timer and itscallback.The example application creates one software timer SwTimer. The timer’s callback SwTimerCallback isperiodically executed and text “Tick.” is printed to terminal." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_swtimer">
<external path="boards/frdmk64f/rtos_examples/freertos_swtimer" type="xml">
<files mask="freertos_swtimer.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_tickless" name="freertos_tickless" brief="This document explains the freertos_tickless example. It shows the CPU enter at sleep mode and then it is waked up by expired time delay that using GPT module." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_tickless">
<external path="boards/frdmk64f/rtos_examples/freertos_tickless" type="xml">
<files mask="freertos_tickless.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_uart" name="freertos_uart" brief="The UART example for FreeRTOS demonstrates the possibility to use the UART driver in the RTOS.The example uses single instance of UART IP and writes string into, then reads back chars.After every 4B received, these are sent back on UART." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples" path="boards/frdmk64f/rtos_examples/freertos_uart">
<external path="boards/frdmk64f/rtos_examples/freertos_uart" type="xml">
<files mask="freertos_uart.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_percepio_snapshot" name="freertos_percepio_snapshot" brief="Percepio_snapshot demo shows the basic capabilities of Percepio tool.Required Segger software - J-Link Software and Documentation Pack ( https://www.segger.com/downloads/jlink ) - J-Link OpenSDA - Board-Specific Firmwares ( https://www.segger.com/downloads/jlink ) - Tracealyzer for FreeRTOS ( http://percepio.com/download/ )Demo requires JLink connected. The JLink can be external probe or on board SDA debugger.In case of SDA debugger you have to change firmware to J-Link OpenSDA by holding board RESET button while power up board. The board is then detected as USB mass storage device and it's required to copy the .bin firmware to the device. When it's done you have to reset the board once more." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples/visualization" path="boards/frdmk64f/rtos_examples/visualization/freertos_percepio_snapshot">
<external path="boards/frdmk64f/rtos_examples/visualization/freertos_percepio_snapshot" type="xml">
<files mask="freertos_percepio_snapshot.xml"/>
</external>
</example>
<example id="frdmk64f_freertos_segger_sysview" name="freertos_segger_sysview" brief="Segger Sysview demo shows the basic capabilities of Segger System Viewer tool.Required software: - J-Link Software and Documentation Pack - SystemView - Real-time analysis and visualization - J-Link OpenSDA - Board-Specific Firmwarescan be downloaded from https://www.segger.com/downloads/jlinkDemo requires JLink connected. The JLink can be external probe or on board SDA debugger.In case of SDA debugger you have to change firmware to J-Link OpenSDA by holding board RESET button while power up board. The board is then detected as USB mass storage device and it's required to copy the .bin firmware to the device. When it's done you have to reset the board once more." toolchain="armgcc iar mcuxpresso mdk" category="rtos_examples/visualization" path="boards/frdmk64f/rtos_examples/visualization/freertos_segger_sysview">
<external path="boards/frdmk64f/rtos_examples/visualization/freertos_segger_sysview" type="xml">
<files mask="freertos_segger_sysview.xml"/>
</external>
</example>
<example id="frdmk64f_rnga_random" name="rnga_random" brief="The RNGA is a digital integrated circuit capable of generating the 32-bit random numbers. The RNGAExample project is a demonstration program that uses the KSDK software to generate random numbersand prints them to the terminal." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/rnga" path="boards/frdmk64f/driver_examples/rnga/random">
<external path="boards/frdmk64f/driver_examples/rnga/random" type="xml">
<files mask="rnga_random.xml"/>
</external>
</example>
<example id="frdmk64f_crc" name="crc" brief="The CRC Example project is a demonstration program that uses the KSDK software to generate checksumsfor an ASCII string. Several CRC protocols are implemented using the CRC driver API." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/crc">
<external path="boards/frdmk64f/driver_examples/crc" type="xml">
<files mask="crc.xml"/>
</external>
</example>
<example id="frdmk64f_mmcau" name="mmcau" brief="Memory-Mapped Cryptographic Acceleration Unit (MMCAU)This project is a demonstration program that uses the KSDK software for encryption/decryption sampledata using AES-CBC, DES3-CBC and Hash algorithms MD5, SHA1 and SHA256." toolchain="armgcc iar mcuxpresso mdk" category="mmcau_examples" path="boards/frdmk64f/mmcau_examples/mmcau_api">
<external path="boards/frdmk64f/mmcau_examples/mmcau_api" type="xml">
<files mask="mmcau.xml"/>
</external>
</example>
<example id="frdmk64f_dspi_interrupt" name="dspi_interrupt" brief="The dspi_interrupt example shows how to use DSPI driver in interrupt way:In this example , one dspi instance used as DSPI master and another dspi instance used as DSPI slave in the same board.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/dspi" path="boards/frdmk64f/driver_examples/dspi/interrupt">
<external path="boards/frdmk64f/driver_examples/dspi/interrupt" type="xml">
<files mask="dspi_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_mcg_pee_blpi" name="mcg_pee_blpi" brief="The pee_bpli example shows how to use MCG driver to change from PEE mode to BLPI mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to PEE mode from default reset mode Change mode PEE -> PBE ->FBE -> FBI -> BLPI Change back BLPI -> FBI -> FBE -> PBE -> PEE Get System clock in PEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/mcg" path="boards/frdmk64f/driver_examples/mcg/pee_blpi">
<external path="boards/frdmk64f/driver_examples/mcg/pee_blpi" type="xml">
<files mask="mcg_pee_blpi.xml"/>
</external>
</example>
<example id="frdmk64f_mcg_fee_blpi" name="mcg_fee_blpi" brief="The fee_bpli example shows how to use MCG driver to change from FEE mode to BLPI mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to FEE mode from default reset mode Change from FEE -> FBI -> BLPI Change back BLPI -> FBI -> FEE Get System clock in FEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/mcg" path="boards/frdmk64f/driver_examples/mcg/fee_blpi">
<external path="boards/frdmk64f/driver_examples/mcg/fee_blpi" type="xml">
<files mask="mcg_fee_blpi.xml"/>
</external>
</example>
<example id="frdmk64f_mcg_fei_blpi" name="mcg_fei_blpi" brief="The fei_bpli example shows how to use MCG driver to change from FEI mode to BLPI mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to FEI mode from default reset mode Change mode FEI -> FBI -> BLPI Change back BLPE -> FBI -> FEI Get System clock in FEI mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/mcg" path="boards/frdmk64f/driver_examples/mcg/fei_blpi">
<external path="boards/frdmk64f/driver_examples/mcg/fei_blpi" type="xml">
<files mask="mcg_fei_blpi.xml"/>
</external>
</example>
<example id="frdmk64f_mcg_pee_blpe" name="mcg_pee_blpe" brief="The pee_bple example shows how to use MCG driver to change from PEE mode to BLPE mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to PEE mode from default reset mode Change mode PEE -> PBE -> BLPE Change back BLPE -> PBE -> PEE Get System clock in PEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/mcg" path="boards/frdmk64f/driver_examples/mcg/pee_blpe">
<external path="boards/frdmk64f/driver_examples/mcg/pee_blpe" type="xml">
<files mask="mcg_pee_blpe.xml"/>
</external>
</example>
<example id="frdmk64f_mcg_fee_blpe" name="mcg_fee_blpe" brief="The fee_bple example shows how to use MCG driver to change from FEE mode to BLPE mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to Fee mode from default reset mode Change from FEE -> FBE -> BLPE Change back BLPE -> FBE -> FEE Get System clock in FEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/mcg" path="boards/frdmk64f/driver_examples/mcg/fee_blpe">
<external path="boards/frdmk64f/driver_examples/mcg/fee_blpe" type="xml">
<files mask="mcg_fee_blpe.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_pwm_twochannel" name="ftm_pwm_twochannel" brief="The FTM pwm two channel Example project is a demonstration program that uses the KSDK software to generate a square pulse PWM on 2 channel to control the LED brightness.- FTM generates a PWM with the increasing and decreasing duty cycle.- LED brightness is increasing and then dimming. This is a continuous process." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/pwm_twochannel">
<external path="boards/frdmk64f/driver_examples/ftm/pwm_twochannel" type="xml">
<files mask="ftm_pwm_twochannel.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_simple_pwm" name="ftm_simple_pwm" brief="The FTM project is a simple demonstration program of the SDK FTM driver. It sets up the FTMhardware block to output a center-aligned PWM signal. The PWM dutycycle is periodically updated.On boards that have an LED connected to the FTM pins, the user will see a change in LED brightness." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/simple_pwm">
<external path="boards/frdmk64f/driver_examples/ftm/simple_pwm" type="xml">
<files mask="ftm_simple_pwm.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_timer" name="ftm_timer" brief="The FTM project is a simple demonstration program of the SDK FTM driver to use FTM as a timer.It sets up the FTM hardware block to trigger an interrupt every 1 millisecond.When the FTM interrupt is triggered a message a printed on the UART terminal." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/timer">
<external path="boards/frdmk64f/driver_examples/ftm/timer" type="xml">
<files mask="ftm_timer.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_combine_pwm" name="ftm_combine_pwm" brief="The FTM project is a demonstration program of generating a combined PWM signal by the SDK FTM driver. It sets up the FTMhardware block to output PWM signals on two TPM channels. The example also shows the complementary mode of operationand deadtime insertion.On boards that have 2 LEDs connected to the FTM pins, the user will see a change in LED brightness.And if the board do not support LEDs to show, the outputs can be observed by oscilloscope." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/combine_pwm">
<external path="boards/frdmk64f/driver_examples/ftm/combine_pwm" type="xml">
<files mask="ftm_combine_pwm.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_dual_edge_capture" name="ftm_dual_edge_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's dual-edge capture feature.This feature is available only on certain SoC's.The example sets up a FTM channel-pair for dual-edge capture. Once the input signal is received,this example will print the capture values and period of the input signal on the terminal window." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/dual_edge_capture">
<external path="boards/frdmk64f/driver_examples/ftm/dual_edge_capture" type="xml">
<files mask="ftm_dual_edge_capture.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_input_capture" name="ftm_input_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's input capture feature.The example sets up a FTM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/input_capture">
<external path="boards/frdmk64f/driver_examples/ftm/input_capture" type="xml">
<files mask="ftm_input_capture.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_output_compare" name="ftm_output_compare" brief="The FTM project is a demonstration program of the SDK FTM driver's output compare feature.It sets up one FTM channel to toggle the output when a match occurs with the channel value. The usershould probe the FTM output with a oscilloscope to see the signal toggling." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/ftm" path="boards/frdmk64f/driver_examples/ftm/output_compare">
<external path="boards/frdmk64f/driver_examples/ftm/output_compare" type="xml">
<files mask="ftm_output_compare.xml"/>
</external>
</example>
<example id="frdmk64f_rtc" name="rtc" brief="The RTC project is a simple demonstration program of the SDK RTC driver. It sets up the RTChardware block to trigger an alarm after a user specified time period. The test will set the currentdate and time to a predefined value. The alarm will be set with reference to this predefined dateand time." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/rtc">
<external path="boards/frdmk64f/driver_examples/rtc" type="xml">
<files mask="rtc.xml"/>
</external>
</example>
<example id="frdmk64f_cmp_polling" name="cmp_polling" brief="The CMP polling Example shows the simplest way to use CMP driver and help user with a quick start.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user's voltage crosses the internal DAC's value. The endless loop in main() functionwould detect the logic value of comparator's output, and change the LED. The LED would be turned on when the compareoutput is logic one, or turned off when zero." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/cmp" path="boards/frdmk64f/driver_examples/cmp/polling">
<external path="boards/frdmk64f/driver_examples/cmp/polling" type="xml">
<files mask="cmp_polling.xml"/>
</external>
</example>
<example id="frdmk64f_cmp_interrupt" name="cmp_interrupt" brief="The CMP interrupt Example shows how to use interrupt with CMP driver.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user-defined channel's voltage crosses the internal DAC's value. The change ofcomparator's output would generate the falling and rising edge events with their interrupts enabled. When any CMP interrupt happens, the CMP's ISR would turn on the LED light if detecting the output's rising edge, or turn off it whendetecting the output's falling edge." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/cmp" path="boards/frdmk64f/driver_examples/cmp/interrupt">
<external path="boards/frdmk64f/driver_examples/cmp/interrupt" type="xml">
<files mask="cmp_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_dac_basic" name="dac_basic" brief="The dac_basic example shows how to use DAC module simply as the general DAC converter.When the DAC's buffer feature is not enabled, the first item of the buffer is used as the DAC output data register.The converter would always output the value of the first item. In this example, it gets the value from terminal,outputs the DAC output voltage through DAC output pin." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/dac" path="boards/frdmk64f/driver_examples/dac/basic">
<external path="boards/frdmk64f/driver_examples/dac/basic" type="xml">
<files mask="dac_basic.xml"/>
</external>
</example>
<example id="frdmk64f_dac_buffer_interrupt" name="dac_buffer_interrupt" brief="The dac_buffer_interrupt example shows how to use DAC buffer with interrupts.When the DAC's buffer feature is enabled, user can benefit from the automation of updating DAC output by hardware/software trigger. As we know, the DAC converter outputs the value of item pointed by current read pointer. Once the buffer is triggered by software or hardware, the buffer's read pointer would move automatically as the work mode is set,like normal (cycle) mode, swing mode, one-time-scan mode or FIFO mode.In this example, it captures the user's type-in operation from terminal and does the software trigger to the buffer.The terminal would also display the log that shows the current buffer pointer's position with buffer events." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/dac" path="boards/frdmk64f/driver_examples/dac/buffer_interrupt">
<external path="boards/frdmk64f/driver_examples/dac/buffer_interrupt" type="xml">
<files mask="dac_buffer_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_pdb_delay_interrupt" name="pdb_delay_interrupt" brief="The pdb_delay_interrupt example show how to use the PDB as a general programmable interrupt timer.The PDB is triggered by software, and other external triggers are generated from PDB in this project,so that user can see just a general counter is working with interrupt." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/pdb" path="boards/frdmk64f/driver_examples/pdb/delay_interrupt">
<external path="boards/frdmk64f/driver_examples/pdb/delay_interrupt" type="xml">
<files mask="pdb_delay_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_pdb_adc16_trigger" name="pdb_adc16_trigger" brief="The pdb_adc16_trigger example shows how to use the PDB to generate a ADC trigger.Based on the basic counter, to use the ADC trigger, just to enable the ADC trigger's "milestone" and set the user-defined value for it.After the PDB counter is triggered to start, when the counter pass the "milestone", the ADC's Pre-Trigger would begenerated and sent to the ADC module.In this example, the ADC16 is configured with hardware trigger and conversion complete interrupt enabled.Once it gets the trigger from the PDB, the conversion goes, then the ISR would be executed." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/pdb" path="boards/frdmk64f/driver_examples/pdb/adc16_trigger">
<external path="boards/frdmk64f/driver_examples/pdb/adc16_trigger" type="xml">
<files mask="pdb_adc16_trigger.xml"/>
</external>
</example>
<example id="frdmk64f_pdb_dac_trigger" name="pdb_dac_trigger" brief="The pdb_dac_trigger example shows how to use the PDB to generate a DAC trigger.Based on the basic counter, to use the DAC trigger, just to enable the DAC trigger's "milestone" and set the user-defined value for it.The DAC's "milestone" is called as "interval". Multiple DAC trigger intervals can be included into one PDB counter's cycle.DAC trigger's counter would reset after the trigger is created and start counting again to the interval value.In this example, the DAC is configured with hardware buffer enabled in normal work mode. Once it gets the trigger from the PDB, the buffer read pointer increases." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/pdb" path="boards/frdmk64f/driver_examples/pdb/dac_trigger">
<external path="boards/frdmk64f/driver_examples/pdb/dac_trigger" type="xml">
<files mask="pdb_dac_trigger.xml"/>
</external>
</example>
<example id="frdmk64f_uart_polling" name="uart_polling" brief="The uart_polling example shows how to use uart driver in polling way:In this example, one uart instance connect to PC through uart, the board will send back all characters that PCsend to the board." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/polling">
<external path="boards/frdmk64f/driver_examples/uart/polling" type="xml">
<files mask="uart_polling.xml"/>
</external>
</example>
<example id="frdmk64f_uart_interrupt_transfer" name="uart_interrupt_transfer" brief="The uart_interrupt example shows how to use uart driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/interrupt_transfer">
<external path="boards/frdmk64f/driver_examples/uart/interrupt_transfer" type="xml">
<files mask="uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_uart_interrupt" name="uart_interrupt" brief="The uart_functioncal_interrupt example shows how to use uart driver functionalAPI to receive data with interrupt method:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/interrupt">
<external path="boards/frdmk64f/driver_examples/uart/interrupt" type="xml">
<files mask="uart_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_uart_edma_transfer" name="uart_edma_transfer" brief="The uart_edma example shows how to use uart driver with EDMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/edma_transfer">
<external path="boards/frdmk64f/driver_examples/uart/edma_transfer" type="xml">
<files mask="uart_edma_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_uart_interrupt_rb_transfer" name="uart_interrupt_rb_transfer" brief="The uart_interrupt_ring_buffer example shows how to use uart driver in interrupt way withRX ring buffer enabled:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/interrupt_rb_transfer">
<external path="boards/frdmk64f/driver_examples/uart/interrupt_rb_transfer" type="xml">
<files mask="uart_interrupt_rb_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_ewm" name="ewm" brief="The EWM Example project is to demonstrate usage of the KSDK EWM driver.In the example, EWM counter is continuously refreshed until button is pressed.Once the button is pressed, EWM counter will expire and interrupt will be generated.After the first pressing, another interrupt can be triggered by pressing button again." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/ewm">
<external path="boards/frdmk64f/driver_examples/ewm" type="xml">
<files mask="ewm.xml"/>
</external>
</example>
<example id="frdmk64f_wdog" name="wdog" brief="The WDOG Example project is to demonstrate usage of the KSDK wdog driver.In this example,quick test is first implemented to test the wdog.And then after 10 times of refreshing the watchdog in None-window mode, a timeout reset is generated.We also try to refresh out of window to trigger reset after 10 times of refreshing in Window mode." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/wdog">
<external path="boards/frdmk64f/driver_examples/wdog" type="xml">
<files mask="wdog.xml"/>
</external>
</example>
<example id="frdmk64f_gpio_input_interrupt" name="gpio_input_interrupt" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example uses the software button to control/toggle the LED." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/gpio" path="boards/frdmk64f/driver_examples/gpio/input_interrupt">
<external path="boards/frdmk64f/driver_examples/gpio/input_interrupt" type="xml">
<files mask="gpio_input_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_gpio_led_output" name="gpio_led_output" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example take turns to shine the LED." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/gpio" path="boards/frdmk64f/driver_examples/gpio/led_output">
<external path="boards/frdmk64f/driver_examples/gpio/led_output" type="xml">
<files mask="gpio_led_output.xml"/>
</external>
</example>
<example id="frdmk64f_adc16_interrupt" name="adc16_interrupt" brief="The adc16_interrupt example shows how to use interrupt with ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. ADC interrupt would be asserted once the conversion is completed. In ADC ISR, the conversion completed flag would be cleared by reading the conversion result value. Also, the conversion result value is stored, and the ISR counter is increased. These information would be printed when the execution return to the main loop.The point is that the ADC16 interrupt configuration is set when configuring the ADC16's conversion channel. When in software trigger mode, the conversion would be launched by the operation of configuring channel, just like writing aconversion command. So if user wants to generate the interrupt every time the conversion is completed, the channel's configuration with enabling interrupt setting would be used for each conversion." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/adc16" path="boards/frdmk64f/driver_examples/adc16/interrupt">
<external path="boards/frdmk64f/driver_examples/adc16/interrupt" type="xml">
<files mask="adc16_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_adc16_polling" name="adc16_polling" brief="The adc16_polling example shows the simplest way to use ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. The execution would check the conversion completed flag in loop until the flag is asserted, which means the conversion is completed. Then read the conversion result value and print it to debug console.Note, the default setting of initialization for the ADC converter is just an available configuration. User can changethe configuration structure's setting in application to fit the special requirement.The auto-calibration is not essential but strongly recommended. It can help to adjust the converter itself and improvethe ADC16's performance." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/adc16" path="boards/frdmk64f/driver_examples/adc16/polling">
<external path="boards/frdmk64f/driver_examples/adc16/polling" type="xml">
<files mask="adc16_polling.xml"/>
</external>
</example>
<example id="frdmk64f_lptmr" name="lptmr" brief="The LPTMR project is a simple demonstration program of the SDK LPTMR driver. It sets up the LPTMRhardware block to trigger a periodic interrupt after every 1 second. When the LPTMR interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/lptmr">
<external path="boards/frdmk64f/driver_examples/lptmr" type="xml">
<files mask="lptmr.xml"/>
</external>
</example>
<example id="frdmk64f_enet_txrx_transfer" name="enet_txrx_transfer" brief="The enet_rxtx example shows the simplest way to use ENET driver for simple frame receive and transmit.1. This example shows how to initialize the ENET MAC.2. How to use ENET MAC to receive and transmit frame.The example transmits 20 number broadcast frame, print the frame length, source MAC addressand destination MAC address when receive frame.Note, The RMII mode is used for default setting to initialize the ENET interface between MAC and the external PHY. youcan change it to MII mode as you wish. Please make sure the MII Mode setting in the MAC is synchronize to the settingin TWR-SERIAL board for the external PHY." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/enet" path="boards/frdmk64f/driver_examples/enet/txrx_transfer">
<external path="boards/frdmk64f/driver_examples/enet/txrx_transfer" type="xml">
<files mask="enet_txrx_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_enet_txrx_ptp1588_transfer" name="enet_txrx_ptp1588_transfer" brief="The enet_rxtx_ptp1588 example shows the way to use ENET driver to receive and transmit frame in the 1588 feature required cases.1. This example shows how to initialize the ENET MAC.2. How to use ENET MAC to receive and transmit frame.3. How to add to the multicast group to receive PTP 1588 message.4. How to get the time stamp of the PTP 1588 timer.4. How to use Get the ENET transmit and receive frame time stamp.The example transmits 20 number PTP event frame, shows the timestamp of the transmitted frame.The length, source MAC address and destination MAC address of the received frame will be print. The time stamp of the received timestamp will be print when the PTP message frame is received. Note, The RMII mode is used for default setting to initialize the ENET interface between MAC and the external PHY. you can change it to MII mode as you wish. Please make sure the MII Mode setting in the MAC is synchronize to the settingin TWR-SERIAL board for the external PHY." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/enet" path="boards/frdmk64f/driver_examples/enet/txrx_ptp1588_transfer">
<external path="boards/frdmk64f/driver_examples/enet/txrx_ptp1588_transfer" type="xml">
<files mask="enet_txrx_ptp1588_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_pit" name="pit" brief="The PIT project is a simple demonstration program of the SDK PIT driver. It sets up the PIThardware block to trigger a periodic interrupt after every 1 second. When the PIT interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/pit">
<external path="boards/frdmk64f/driver_examples/pit" type="xml">
<files mask="pit.xml"/>
</external>
</example>
<example id="frdmk64f_edma_memory_to_memory" name="edma_memory_to_memory" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It excuates one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/edma" path="boards/frdmk64f/driver_examples/edma/memory_to_memory">
<external path="boards/frdmk64f/driver_examples/edma/memory_to_memory" type="xml">
<files mask="edma_memory_to_memory.xml"/>
</external>
</example>
<example id="frdmk64f_edma_scatter_gather" name="edma_scatter_gather" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It excuates one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/edma" path="boards/frdmk64f/driver_examples/edma/scatter_gather">
<external path="boards/frdmk64f/driver_examples/edma/scatter_gather" type="xml">
<files mask="edma_scatter_gather.xml"/>
</external>
</example>
<example id="frdmk64f_pflash" name="pflash" brief="The pflash example shows how to use flash driver to operate program flash:" toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/flash" path="boards/frdmk64f/driver_examples/flash/pflash">
<external path="boards/frdmk64f/driver_examples/flash/pflash" type="xml">
<files mask="pflash.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_read_accel_value_transfer" name="i2c_read_accel_value_transfer" brief="The i2c_read_accel_value example shows how to use I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmk64f/driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_interrupt" name="i2c_interrupt" brief="The i2c_functional_interrupt example shows how to use I2C functional driver to build a interrupt based application:In this example , one i2c instance used as I2C master and another i2c instance used as I2C slave .1. I2C master send data to I2C slave in interrupt . (I2C Slave using interrupt to receive the data)2. I2C master read data from I2C slave in interrupt . (I2C Slave using interrupt to send the data)3. The example assumes that the connection is OK between master and slave, so there's NO error handling code." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/interrupt">
<external path="boards/frdmk64f/driver_examples/i2c/interrupt" type="xml">
<files mask="i2c_interrupt.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_interrupt_b2b_transfer_master" name="i2c_interrupt_b2b_transfer_master" brief="The i2c_interrupt_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/interrupt_b2b_transfer/master">
<external path="boards/frdmk64f/driver_examples/i2c/interrupt_b2b_transfer/master" type="xml">
<files mask="i2c_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_interrupt_b2b_transfer_slave" name="i2c_interrupt_b2b_transfer_slave" brief="The i2c_interrupt_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with interrupt:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/interrupt_b2b_transfer/slave">
<external path="boards/frdmk64f/driver_examples/i2c/interrupt_b2b_transfer/slave" type="xml">
<files mask="i2c_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_polling_b2b_transfer_master" name="i2c_polling_b2b_transfer_master" brief="The i2c_polling_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer using polling method:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/polling_b2b_transfer/master">
<external path="boards/frdmk64f/driver_examples/i2c/polling_b2b_transfer/master" type="xml">
<files mask="i2c_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmk64f_i2c_polling_b2b_transfer_slave" name="i2c_polling_b2b_transfer_slave" brief="The i2c_polling_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with a polling master:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/i2c" path="boards/frdmk64f/driver_examples/i2c/polling_b2b_transfer/slave">
<external path="boards/frdmk64f/driver_examples/i2c/polling_b2b_transfer/slave" type="xml">
<files mask="i2c_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmk64f_cmt" name="cmt" brief="The cmt example shows the simplest way to use CMT driver.In this example, the CMT is work as Time mode and used to modulation 11 bit numbers of data.The CMT is configured to generate a 40000hz carrier generator signal through a modulator gateconfigured with different mark/space time period to represent bit 1 and bit 0. The modulated data rate is 9600.Note, The end of cycle interrupt provides a means for the user to reload new mark/space valuesinto the modulator data registers. Modulator data register updates will take effect at the end of the current modulation cycle. The CMT internal down-counter and space period register areupdated at the end of every modulation cycle, irrespective of interrupt handling and the stateof the interrupt. so please make sure the IRQ handler process is shorter than the modulationcycle to ensure the new mark/space counter is prepared before each end of modulation cycle." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/cmt">
<external path="boards/frdmk64f/driver_examples/cmt" type="xml">
<files mask="cmt.xml"/>
</external>
</example>
<example id="frdmk64f_flexcan_loopback_transfer" name="flexcan_loopback_transfer" brief="The flexcan_loopback example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrough internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/flexcan" path="boards/frdmk64f/driver_examples/flexcan/loopback_transfer">
<external path="boards/frdmk64f/driver_examples/flexcan/loopback_transfer" type="xml">
<files mask="flexcan_loopback_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_flexcan_loopback" name="flexcan_loopback" brief="The flexcan_loopback_functional example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrouth internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/flexcan" path="boards/frdmk64f/driver_examples/flexcan/loopback">
<external path="boards/frdmk64f/driver_examples/flexcan/loopback" type="xml">
<files mask="flexcan_loopback.xml"/>
</external>
</example>
<example id="frdmk64f_sysmpu" name="sysmpu" brief="The SYSMPU example defines protected/unprotected memory region for the core access.First, the SYSMPU will capture the hardware information and show it on theterminal. Then, a memory region is configured as the non-writable region. Thebus fault interrupt is enabled to report the memory protection interrupt eventfor this non-writable region. If an operation writes to this region, the busfault interrupt happens. Then the bus fault interrupt handler provides aprevention alert by outputting a message on terminal, then the write rightswill be given to this region for core access. After the write access enabled,the writing to the region becomes successful. When the bus fault happen, thedetails of the error information will be captured and printed on the terminal.This example provides the terminal input control to give the example show for several regions access test. Just press any key to the terminal when theterminal show "Press any key to continue"." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples" path="boards/frdmk64f/driver_examples/sysmpu">
<external path="boards/frdmk64f/driver_examples/sysmpu" type="xml">
<files mask="sysmpu.xml"/>
</external>
</example>
<example id="frdmk64f_sdcard_freertos" name="sdcard_freertos" brief="The SDCARD FreeRTOS project is a demonstration program that uses the SDK software. It reads/writes/erases the SD card continusly. The purpose of this example is to show how to use SDCARD driver with FreeRTOS in SDK software to access SD card.Note: If DATA3 is used as the card detect PIN, please make sure DATA3 is pull down, no matter internal or external, at the same time, make sure the card can pull DATA3 up, then host can detect card through DATA3.And SDHC do not support detect card through CD by host, card can be detected through DATA3 or GPIO.No matter detect card through host or gpio, make sure the pinmux configuration is correct." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/sdcard" path="boards/frdmk64f/driver_examples/sdcard/freertos">
<external path="boards/frdmk64f/driver_examples/sdcard/freertos" type="xml">
<files mask="sdcard_freertos.xml"/>
</external>
</example>
<example id="frdmk64f_bubble" name="bubble" brief="The EEPROM flash demo application demonstrates the use of the LPI2C IP and driver to read and write data from anexternal EEPROM device." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/bubble">
<external path="boards/frdmk64f/demo_apps/bubble" type="xml">
<files mask="bubble.xml"/>
</external>
</example>
<example id="frdmk64f_bubble_peripheral" name="bubble_peripheral" brief="The EEPROM flash demo application demonstrates the use of the LPI2C IP and driver to read and write data from anexternal EEPROM device." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/bubble_peripheral">
<external path="boards/frdmk64f/demo_apps/bubble_peripheral" type="xml">
<files mask="bubble_peripheral.xml"/>
</external>
</example>
<example id="frdmk64f_dac_adc" name="dac_adc" brief="The DAC / ADC demo application demonstrates the use of the DAC and ADC peripherals. This application demonstrates how toconfigure the DAC and set the output on the DAC. This demo also demonstrates how to configure the ADC in 'Blocking Mode'and how to read ADC values." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/dac_adc">
<external path="boards/frdmk64f/demo_apps/dac_adc" type="xml">
<files mask="dac_adc.xml"/>
</external>
</example>
<example id="frdmk64f_ecompass" name="ecompass" brief="The E-Compass demo application demonstrates the use of the FXOS8700 sensor. The tilt-compensated algorithm calculatesall three angles (pitch, roll, and yaw or compass heading)." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/ecompass">
<external path="boards/frdmk64f/demo_apps/ecompass" type="xml">
<files mask="ecompass.xml"/>
</external>
</example>
<example id="frdmk64f_ecompass_peripheral" name="ecompass_peripheral" brief="The E-Compass demo application demonstrates the use of the FXOS8700 sensor. The tilt-compensated algorithm calculatesall three angles (pitch, roll, and yaw or compass heading)." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/ecompass_peripheral">
<external path="boards/frdmk64f/demo_apps/ecompass_peripheral" type="xml">
<files mask="ecompass_peripheral.xml"/>
</external>
</example>
<example id="frdmk64f_adc16_low_power" name="adc16_low_power" brief="The ADC Low Power demo application demonstrates the usage of the ADC peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 500 ms, an interrupt wakes up the ADC module andreads the current temperature of the microcontroller. While the temperature remains within boundaries, both LEDs are on.If the core temperature is higher or lower than average, the LEDs change state respectively." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/adc16_low_power">
<external path="boards/frdmk64f/demo_apps/adc16_low_power" type="xml">
<files mask="adc16_low_power.xml"/>
</external>
</example>
<example id="frdmk64f_adc16_low_power_peripheral" name="adc16_low_power_peripheral" brief="The ADC Low Power demo application demonstrates the usage of the ADC peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 500 ms, an interrupt wakes up the ADC module andreads the current temperature of the microcontroller. While the temperature remains within boundaries, both LEDs are on.If the core temperature is higher or lower than average, the LEDs change state respectively." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/adc16_low_power_peripheral">
<external path="boards/frdmk64f/demo_apps/adc16_low_power_peripheral" type="xml">
<files mask="adc16_low_power_peripheral.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_pdb_adc16" name="ftm_pdb_adc16" brief="The FTM / PDB demo application demonstrates how to use the FTM external trigger to start the ADC conversion using thePDB. FTM0 is configured as a complementary combined mode, and each channel output frequency is 16 KHz. The complementarychannel dead time is 1 µs. The PDB pre-trigger works in back-to-back mode. The ADC0 and ADC1 work in single-end mode.The ADC0 uses channel 1 and channel 5, and ADC1 uses channel 1 and channel 7." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/ftm_pdb_adc16">
<external path="boards/frdmk64f/demo_apps/ftm_pdb_adc16" type="xml">
<files mask="ftm_pdb_adc16.xml"/>
</external>
</example>
<example id="frdmk64f_ftm_quad_decoder" name="ftm_quad_decoder" brief="This demo describes the usage of Quad Decoder feature in FTM module, which can be used to count the position of decoder.An external decoder is used to generate the PHA and PHB's signal. These two signals are feed to the FTM pins with Quad Decoder feature (FTMx_QD_PHA and FTMx_QD_PHB). Then, the counter value and direction would be displayed in terminal window predically." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/ftm_quad_decoder">
<external path="boards/frdmk64f/demo_apps/ftm_quad_decoder" type="xml">
<files mask="ftm_quad_decoder.xml"/>
</external>
</example>
<example id="frdmk64f_power_manager" name="power_manager" brief="The Power manager demo application demonstrates the use of power modes in the KSDK. The demo use the notification mechanismand prints the power mode menu through the debug console, where the user can set the MCU to a specific power mode. The usercan also set the wakeup source by following the debug console prompts. The purpose of this demo is to demonstrate theimplementation of a power mode manager. The callback can be registered to the framework. If a power mode transition happens,the callback will be called and user can do something. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/power_manager">
<external path="boards/frdmk64f/demo_apps/power_manager" type="xml">
<files mask="power_manager.xml"/>
</external>
</example>
<example id="frdmk64f_power_mode_switch" name="power_mode_switch" brief="The Power mode switch demo application demonstrates the use of power modes in the KSDK. The demo prints the power mode menuthrough the debug console, where the user can set the MCU to a specific power mode. The user can also set the wakeupsource by following the debug console prompts. The purpose of this demo is to show how to switch between different power modes, and how to configure a wakeup source and wakeup the MCU from low power modes. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware. - Debug pins(e.g SWD_DIO) would consume addtional power, had better to disable related pins or disconnect them. " toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/power_mode_switch">
<external path="boards/frdmk64f/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch.xml"/>
</external>
</example>
<example id="frdmk64f_rtc_func" name="rtc_func" brief="The RTC demo application demonstrates the important features of the RTC Module by using the RTC Peripheral Driver.The RTC demo supports the following features:- Calendar + Get the current date time with Year, Month, Day, Hour, Minute, and Second. + Set the current date time with Year, Month, Day, Hour, Minute, and Second.- Alarm + Set the alarm based on the current time. + Application prints a notification when the alarm expires.- Seconds interrupt + Use second interrupt function to display a digital time blink every second." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/rtc_func">
<external path="boards/frdmk64f/demo_apps/rtc_func" type="xml">
<files mask="rtc_func.xml"/>
</external>
</example>
<example id="frdmk64f_shell" name="shell" brief="The Shell Demo application demonstrates to control Leds by commands." toolchain="armgcc iar mcuxpresso mdk" category="demo_apps" path="boards/frdmk64f/demo_apps/shell">
<external path="boards/frdmk64f/demo_apps/shell" type="xml">
<files mask="shell.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_uart_interrupt_transfer" name="cmsis_uart_interrupt_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_interrupt_transfer example shows how to use uart cmsis driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/uart" path="boards/frdmk64f/cmsis_driver_examples/uart/interrupt_transfer">
<external path="boards/frdmk64f/cmsis_driver_examples/uart/interrupt_transfer" type="xml">
<files mask="cmsis_uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_uart_edma_transfer" name="cmsis_uart_edma_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_edma_transfer example shows how to use uart cmsis driver with EDMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/uart" path="boards/frdmk64f/cmsis_driver_examples/uart/edma_transfer">
<external path="boards/frdmk64f/cmsis_driver_examples/uart/edma_transfer" type="xml">
<files mask="cmsis_uart_edma_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_i2c_read_accel_value_transfer" name="cmsis_i2c_read_accel_value_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_read_accel_value example shows how to use CMSIS I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/i2c" path="boards/frdmk64f/cmsis_driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmk64f/cmsis_driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="cmsis_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_i2c_int_b2b_transfer_master" name="cmsis_i2c_int_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The i2c_interrupt_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/i2c" path="boards/frdmk64f/cmsis_driver_examples/i2c/int_b2b_transfer/master">
<external path="boards/frdmk64f/cmsis_driver_examples/i2c/int_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_i2c_int_b2b_transfer_slave" name="cmsis_i2c_int_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The i2c_interrupt_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/i2c" path="boards/frdmk64f/cmsis_driver_examples/i2c/int_b2b_transfer/slave">
<external path="boards/frdmk64f/cmsis_driver_examples/i2c/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_i2c_edma_b2b_transfer_master" name="cmsis_i2c_edma_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_edma_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with EDMA:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/i2c" path="boards/frdmk64f/cmsis_driver_examples/i2c/edma_b2b_transfer/master">
<external path="boards/frdmk64f/cmsis_driver_examples/i2c/edma_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmk64f_cmsis_i2c_edma_b2b_transfer_slave" name="cmsis_i2c_edma_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_edma_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with a EDMA master:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar mcuxpresso mdk" category="cmsis_driver_examples/i2c" path="boards/frdmk64f/cmsis_driver_examples/i2c/edma_b2b_transfer/slave">
<external path="boards/frdmk64f/cmsis_driver_examples/i2c/edma_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_client_matrix_multiply_uart" name="erpc_client_matrix_multiply_uart" brief="This example demonstrates usage of eRPC between PC and board using UART transport layer.Board acts like a client and the PC as server. When client starts, it generates two randommatrixes and sends them to server. Server then performs matrix multiplication and sendsresult data back to client. Result matrix is then printed on the PC side.eRPC documentation eRPC specific files are stored in: middleware/multicore/erpc eRPC documentation is stored in: middleware/multicore/erpc/doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.io PC Side Setup (Python)1. Make sure you have Python installed on your PC2. Install serial module by executing following command in command line: "python -m pip install pyserial"3. Install eRPC module to Python by executing setup.py located in: middleware/multicore/erpc/erpc_python - "python setup.py install"Usage of run_uart.pyusage: run_uart.py [-h] [-c] [-s] [-p PORT] [-b BD]eRPC Matrix Multiply exampleoptional arguments: -h, --help show this help message an -c, --client Run client -s, --server Run server -p PORT, --port PORT Serial port -b BD, --bd BD Baud rate (default value is 115200)Either server or client has to be selected to runExample:To run PC side as a server with a board connected as a client to COM3 execute:"run_uart.py --server --port COM3"" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_client_matrix_multiply_uart">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_client_matrix_multiply_uart" type="xml">
<files mask="erpc_client_matrix_multiply_uart.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_server_matrix_multiply_uart" name="erpc_server_matrix_multiply_uart" brief="This example demonstrates usage of eRPC between PC and board using UART transport layer.Board acts like a server and the PC as client. When client starts, it generates two randommatrixes and sends them to server. Server then performs matrix multiplication and sendsresult data back to client. Result matrix is then printed on the PC side.eRPC documentation eRPC specific files are stored in: middleware/multicore/erpc eRPC documentation is stored in: middleware/multicore/erpc/doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.io PC Side Setup (Python)1. Make sure you have Python installed on your PC2. Install eRPC module to Python by executing setup.py located in: middleware/multicore/erpc/erpc_python3. Install serial module by executing following command in command line: "python -m pip install pyserial"Usage of run_uart.pyusage: run_uart.py [-h] [-c] [-s] [-p PORT] [-b BD]eRPC Matrix Multiply exampleoptional arguments: -h, --help show this help message an -c, --client Run client -s, --server Run server -p PORT, --port PORT Serial port -b BD, --bd BD Baud rate (default value is 115200)Either server or client has to be selected to runExample:To run PC side as a client with a board connected as a server to COM3 execute:"run_uart.py --client --port COM3"" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_server_matrix_multiply_uart">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_server_matrix_multiply_uart" type="xml">
<files mask="erpc_server_matrix_multiply_uart.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_server_dac_adc" name="erpc_server_dac_adc" brief="This example demonstrates usage of eRPC between PC and board using UART transport layer.Board acts like a server and the PC as client. When server starts, it waits fordata being send from client over UART. Server then performs action (DAC/ADC conversion, light LEDs,read data from magnetometer senzor) and sends result data back to client (or lights LED).eRPC documentation eRPC specific files are stored in: middleware//multicore//erpc eRPC documentation is stored in: middleware//multicore//erpc//doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.ioRunning with i.MX7D Sabre SD board- First, download L4.1.15_2.0.0_iMX6UL7D board support package from nxp.com- Then uncompress it and locate file fsl-image-validation-imx-imx7dsabresd.sdcard- Insert an SD card and run: sudo dd if=fsl-image-validation-imx-imx7dsabresd.sdcardof=/dev/mmcblk0 bs=1M - Flush disk IO operations, run command: sync- Download enum34, erpc and pyserial packages from pypi, uncompress them and copy to/home/root, respective links are:/t/t- enum34: https://pypi.python.org/packages/bf/3e/31d502c25302814a7c2f1d3959d2a3b3f78e509002ba91aea64993936876/enum34-1.1.6.tar.gz#md5=5f13a0841a61f7fc295c514490d120d0/t/t- erpc: https://pypi.python.org/packages/fd/0d/64425e9d5258fa5ea9cef7de879e3ae8be6c0d50a7e215ba791d0a32d77e/erpc--1.4.0.tar.gz#md5=1387082dab3af4067fdfe01c98b09dee/t/t- pyserial: https://pypi.python.org/packages/df/c9/d9da7fafaf2a2b323d20eee050503ab08237c16b0119c7bbf1597d53f793/pyserial-2.7.tar.gz#md5=794506184df83ef2290de0d18803dd11- Insert SD card in the board, connect to USB debug console- Once you boot and login (user root), enter enum34, erpc and pyserial directoriesand run in each of them: python setup.py install- now you can use: python run.py -p <PORT> -b <BAUDRATE>, to run the example" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_server_dac_adc">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_server_dac_adc" type="xml">
<files mask="erpc_server_dac_adc.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_remote_control" name="erpc_remote_control" brief="This example demonstrates usage of eRPC between PC and board using UART transport layer.Both board and the PC acts like server and client thanks to eRPC arbitrator.When both servers starts, they waits for data being send from client over UART. A. Server on the board performs action (DAC/ADC conversion, turn on selected LEDs, read data from magnetometer and accelerometer sensor) and sends result data back to client (or lights LED).B. Server on the PC displays which SW button was pressed on the board.eRPC documentation eRPC specific files are stored in: middleware/multicore/erpc eRPC documentation is stored in: middleware/multicore/erpc/doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.io" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_remote_control">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_remote_control" type="xml">
<files mask="erpc_remote_control.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_server_matrix_multiply_spi" name="erpc_server_matrix_multiply_spi" brief="This example demonstrates usage of eRPC between two boards using SPI transport layer. One board acts like a server and the second as client. When client starts, it generates two randommatrixes and sends them to server. Server then performs matrix multiplication and sendsresult data back to client. Client then prints the result matrix.eRPC documentation eRPC specific files are stored in: middleware/multicore/erpc eRPC documentation is stored in: middleware/multicore/erpc/doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.io" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_server_matrix_multiply_spi">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_server_matrix_multiply_spi" type="xml">
<files mask="erpc_server_matrix_multiply_spi.xml"/>
</external>
</example>
<example id="frdmk64f_erpc_client_matrix_multiply_spi" name="erpc_client_matrix_multiply_spi" brief="This example demonstrates usage of eRPC between two boards using SPI transport layer. One board acts like a server and the second as client. When client starts, it generates two randommatrixes and sends them to server. Server then performs matrix multiplication and sendsresult data back to client. Client then prints the result matrix.eRPC documentation eRPC specific files are stored in: middleware/multicore/erpc eRPC documentation is stored in: middleware/multicore/erpc/doc eRPC is open-source project stored on github: https://github.com/EmbeddedRPC/erpc eRPC documentation can be also found in: http://embeddedrpc.github.io" toolchain="armgcc iar mcuxpresso mdk" category="multiprocessor_examples" path="boards/frdmk64f/multiprocessor_examples/erpc_client_matrix_multiply_spi">
<external path="boards/frdmk64f/multiprocessor_examples/erpc_client_matrix_multiply_spi" type="xml">
<files mask="erpc_client_matrix_multiply_spi.xml"/>
</external>
</example>
<example id="frdmk64f_qca_demo" name="qca_demo" brief="The qca_demo example provides basic commands to show the functionality of qca_wifi stack.The default IP configuration is "addr: 192.168.1.10 mask: 255.255.255.0 gw: 192.168.1.1".To obtain a valid IP configuration from DHCP server, press 'd' after WiFi connection is established." toolchain="armgcc iar mcuxpresso mdk" category="wifi_qca_examples" path="boards/frdmk64f/wifi_qca_examples/qca_demo">
<external path="boards/frdmk64f/wifi_qca_examples/qca_demo" type="xml">
<files mask="qca_demo.xml"/>
</external>
</example>
<example id="frdmk64f_qca_throughput" name="qca_throughput" brief="The qca_throughput demo tests transfer throughput." toolchain="armgcc iar mcuxpresso mdk" category="wifi_qca_examples" path="boards/frdmk64f/wifi_qca_examples/qca_throughput">
<external path="boards/frdmk64f/wifi_qca_examples/qca_throughput" type="xml">
<files mask="qca_throughput.xml"/>
</external>
</example>
<example id="frdmk64f_qca_fwupdate" name="qca_fwupdate" brief="No special requirements/n/n" toolchain="armgcc iar mcuxpresso mdk" category="wifi_qca_examples" path="boards/frdmk64f/wifi_qca_examples/qca_fwupdate">
<external path="boards/frdmk64f/wifi_qca_examples/qca_fwupdate" type="xml">
<files mask="qca_fwupdate.xml"/>
</external>
</example>
<example id="frdmk64f_wolfssl_benchmark" name="wolfssl_benchmark" brief="The wolfssl_benchmark demo application demonstrates cryptographic acceleration on supported platforms that have MMCAU,LTC or similar accelerator peripheral. The hardware acceleration is enabled by default, and can be configured at build time inthe middleware/wolfssl/wolfssl/wolfcrypt/settings.h header file. FREESCALE_USE_MMCAU, FREESCALE_USE_LTC, FREESCALE_USE_LPC_AESand FREESCALE_USE_LPC_SHA macros can be used to compile the wolfssl_benchmark project source code with support forthe Freescale hardware cryptographic accelerator, or when none of these macros is defined, all algorithms are implemented in software only." toolchain="armgcc iar mcuxpresso mdk" category="wolfssl_examples" path="boards/frdmk64f/wolfssl_examples/wolfssl_benchmark">
<external path="boards/frdmk64f/wolfssl_examples/wolfssl_benchmark" type="xml">
<files mask="wolfssl_benchmark.xml"/>
</external>
</example>
<example id="frdmk64f_wolfssl_selftest" name="wolfssl_selftest" brief="The wolfssl_selftest demo application demonstrates cryptographic acceleration on supported platforms that have eitheran MMCAU or LTC peripheral. The hardware acceleration is enabled by default and can be configured at build time inthe middleware/wolfssl/wolfssl/wolfcrypt/settings.h header file. FREESCALE_USE_MMCAU and FREESCALE_USE_LTC macros canbe used to compile the wolfssl_benchmark project source code with support for the Freescale hardware cryptographicaccelerator, or when none of these macros is defined, all algorithms are implemented in software only." toolchain="armgcc iar mcuxpresso mdk" category="wolfssl_examples" path="boards/frdmk64f/wolfssl_examples/wolfssl_selftest">
<external path="boards/frdmk64f/wolfssl_examples/wolfssl_selftest" type="xml">
<files mask="wolfssl_selftest.xml"/>
</external>
</example>
<example id="frdmk64f_uart_hardware_flow_control" name="uart_hardware_flow_control" brief="The uart_hardware_flow_control example project is to demonstrate usage of the hardware flow control function.This example will send data to itself(loopback), and hardware flow control will be enabled in the example.The CTS(clear-to-send) pin is for transmiter to check if receiver is ready, if the CTS pin is assert, transmiter startto send data. The RTS(request-to-send) is a pin for receiver to inform the transmiter if receiver is ready to receivedata. So, please connect RTS to CTS pin directly." toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/uart" path="boards/frdmk64f/driver_examples/uart/hardware_flow_control">
<external path="boards/frdmk64f/driver_examples/uart/hardware_flow_control" type="xml">
<files mask="uart_hardware_flow_control.xml"/>
</external>
</example>
<example id="frdmk64f_adc16_continuous_edma" name="adc16_continuous_edma" brief="The ADC16 continuous EDMA demo application demonstrates the usage of the ADC and EDMA peripheral while in a continuous mode. TheADC16 is first set to continuous mode. In continuous convert configuration, only the initial rising-edge to launch continuous conversions isobserved, and until conversion is aborted, the ADC16 continues to do conversions on the same SCn register that initiated the conversion. EDMA request will be asserted during an ADC16 conversion complete event noted when any of the SC1n[COCO] flags is asserted. EDMA will transferADC16 results to memory and if users press any key, demo will average ADC16 results stored in memory and print average on the terminal. " toolchain="armgcc iar mcuxpresso mdk" category="driver_examples/adc16" path="boards/frdmk64f/driver_examples/adc16/continuous_edma">