-
Notifications
You must be signed in to change notification settings - Fork 24
/
Copy pathMKL82Z128xxx7_manifest_v3_4.xml
6455 lines (6455 loc) · 530 KB
/
MKL82Z128xxx7_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_MKL82Z128xxx7" name="MKL82Z128xxx7" brief="This is SDK version 2.5.0 manifest file. It describes the content of the MKL82Z128xxx7 and additional settings for tools that support SDK version 2.5.0" format_version="3.4" api_version="2.0.0" configuration="c760910218b39e8e707fa2d860e0e63a" 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): 2019-11-26 14:36:04.671003-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<ksdk id="MCUXpresso250" name="MCUXpresso250" version="2.5.0" revision="150 2018-12-17"/>
<compilers>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
</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="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="twrkl82z72m" name="TWR-KL82Z72M" href="http://www.nxp.com/twr-kl82z72m" version="1.0.0" package="MKL82Z128VMC7">
<description>TWR-KL82Z72M: Tower System Development Board for Kinetis Ultra-Low-Power KL82 MCUs</description>
<image path="docs/images" type="image">
<files mask="TWR-KL82Z72M.gif"/>
</image>
<metadataSet>
<metadata key="html">
<specific>
<content>The TWR-KL82Z72M is a development board for Kinetis KL82 32-bit MCUs. It features the Kinetis MKL82Z128VMC7 MCU 72 MHz ARM® Cortex®-M0+ core, 128 KB flash, 96 KB SCRAM, 121 MAPBGA and USB.The TWR-KL82Z72M operates as a standalone debug tool and can also be combined and used as part of the modular Tower System development platform.</content>
</specific>
</metadata>
</metadataSet>
<examples>
<example id="twrkl82z72m_otg_hid_mouse_freertos" name="otg_hid_mouse_freertos" brief="This OTG HID example is a simple demonstration program based on the MCUXpresso SDK. User can test the OTG functions by using the menu that is printed in the vcom." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_otg_hid_mouse/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_otg_hid_mouse/freertos" type="xml">
<files mask="otg_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_otg_hid_mouse_bm" name="otg_hid_mouse_bm" brief="This OTG HID example is a simple demonstration program based on the MCUXpresso SDK. User can test the OTG functions by using the menu that is printed in the vcom." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_otg_hid_mouse/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_otg_hid_mouse/bm" type="xml">
<files mask="otg_hid_mouse_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_audio_speaker/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_audio_speaker/freertos" type="xml">
<files mask="host_audio_speaker_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_cdc/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_cdc/freertos" type="xml">
<files mask="host_cdc_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse/freertos" type="xml">
<files mask="host_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_generic/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_generic/freertos" type="xml">
<files mask="host_hid_generic_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_host_hid_mouse_keyboard_freertos" name="host_hid_mouse_keyboard_freertos" brief="This example supports the mouse device and the keyboard device." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse_keyboard/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse_keyboard/freertos" type="xml">
<files mask="host_hid_mouse_keyboard_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_msd_command/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_msd_command/freertos" type="xml">
<files mask="host_msd_command_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_msd_fatfs/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_msd_fatfs/freertos" type="xml">
<files mask="host_msd_fatfs_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_phdc_manager/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_phdc_manager/freertos" type="xml">
<files mask="host_phdc_manager_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_printer_plain_text/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_host_printer_plain_text/freertos" type="xml">
<files mask="host_printer_plain_text_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_host_suspend_resume_hid_mouse_freertos" name="host_suspend_resume_hid_mouse_freertos" brief="This is one example support suspend/resume." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_host_hid_mouse/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_host_hid_mouse/freertos" type="xml">
<files mask="host_suspend_resume_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_audio_speaker/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_audio_speaker/bm" type="xml">
<files mask="host_audio_speaker_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_cdc/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_cdc/bm" type="xml">
<files mask="host_cdc_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse/bm" type="xml">
<files mask="host_hid_mouse_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_generic/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_generic/bm" type="xml">
<files mask="host_hid_generic_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_host_hid_mouse_keyboard_bm" name="host_hid_mouse_keyboard_bm" brief="This example supports the mouse device and the keyboard device." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse_keyboard/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_hid_mouse_keyboard/bm" type="xml">
<files mask="host_hid_mouse_keyboard_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_msd_command/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_msd_command/bm" type="xml">
<files mask="host_msd_command_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_msd_fatfs/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_msd_fatfs/bm" type="xml">
<files mask="host_msd_fatfs_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_phdc_manager/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_phdc_manager/bm" type="xml">
<files mask="host_phdc_manager_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_host_printer_plain_text/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_host_printer_plain_text/bm" type="xml">
<files mask="host_printer_plain_text_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_host_suspend_resume_hid_mouse_bm" name="host_suspend_resume_hid_mouse_bm" brief="This is one example support suspend/resume." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_host_hid_mouse/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_host_hid_mouse/bm" type="xml">
<files mask="host_suspend_resume_hid_mouse_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/freertos_static">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/freertos_static" type="xml">
<files mask="dev_hid_mouse_freertos_static.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator/freertos" type="xml">
<files mask="dev_audio_generator_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_dev_ccid_smart_card_freertos" name="dev_ccid_smart_card_freertos" brief="The USB CCID smart card application is a simple demonstration program based on the MCUXpresso SDK and EMV library. It is enumerated as a smart card reader." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card/freertos" type="xml">
<files mask="dev_ccid_smart_card_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom/freertos" type="xml">
<files mask="dev_cdc_vcom_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/freertos">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc/freertos" type="xml">
<files mask="dev_composite_cdc_msc_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio/freertos" type="xml">
<files mask="dev_composite_hid_audio_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/freertos">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/freertos" type="xml">
<files mask="dev_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic/freertos" type="xml">
<files mask="dev_hid_generic_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk/freertos" type="xml">
<files mask="dev_msc_ramdisk_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera/freertos" type="xml">
<files mask="dev_video_virtual_camera_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale/freertos" type="xml">
<files mask="dev_phdc_weighscale_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_printer_virtual_plain_text/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_device_printer_virtual_plain_text/freertos" type="xml">
<files mask="dev_printer_virtual_plain_text_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_device_hid_mouse/freertos">
<external path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_device_hid_mouse/freertos" type="xml">
<files mask="dev_suspend_resume_hid_mouse_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator/bm" type="xml">
<files mask="dev_audio_generator_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_audio_generator_lite/bm" type="xml">
<files mask="dev_audio_generator_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_dev_ccid_smart_card_bm" name="dev_ccid_smart_card_bm" brief="The USB CCID smart card application is a simple demonstration program based on the MCUXpresso SDK and EMV library. It is enumerated as a smart card reader." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card/bm" type="xml">
<files mask="dev_ccid_smart_card_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_dev_ccid_smart_card_lite_bm" name="dev_ccid_smart_card_lite_bm" brief="The USB CCID smart card application is a simple demonstration program based on the MCUXpresso SDK and EMV library. It is enumerated as a smart card reader." toolchain="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_ccid_smart_card_lite/bm" type="xml">
<files mask="dev_ccid_smart_card_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom/bm" type="xml">
<files mask="dev_cdc_vcom_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_cdc_vcom_lite/bm" type="xml">
<files mask="dev_cdc_vcom_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_vcom_cdc_vcom_lite/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc/bm" type="xml">
<files mask="dev_composite_cdc_msc_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_cdc_msc_lite/bm" type="xml">
<files mask="dev_composite_cdc_msc_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio/bm" type="xml">
<files mask="dev_composite_hid_audio_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_audio_lite/bm" type="xml">
<files mask="dev_composite_hid_audio_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_mouse_hid_keyboard/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_composite_hid_mouse_hid_keyboard_lite/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse/bm" type="xml">
<files mask="dev_hid_mouse_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_mouse_lite/bm" type="xml">
<files mask="dev_hid_mouse_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic/bm" type="xml">
<files mask="dev_hid_generic_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_hid_generic_lite/bm" type="xml">
<files mask="dev_hid_generic_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk/bm" type="xml">
<files mask="dev_msc_ramdisk_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_msc_ramdisk_lite/bm" type="xml">
<files mask="dev_msc_ramdisk_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera/bm" type="xml">
<files mask="dev_video_virtual_camera_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_video_virtual_camera_lite/bm" type="xml">
<files mask="dev_video_virtual_camera_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale/bm" type="xml">
<files mask="dev_phdc_weighscale_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale_lite/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_phdc_weighscale_lite/bm" type="xml">
<files mask="dev_phdc_weighscale_lite_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_printer_virtual_plain_text/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_device_printer_virtual_plain_text/bm" type="xml">
<files mask="dev_printer_virtual_plain_text_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_device_printer_virtual_plain_text_lite/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_device_hid_mouse/bm">
<external path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_device_hid_mouse/bm" type="xml">
<files mask="dev_suspend_resume_hid_mouse_bm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="usb_examples" path="boards/twrkl82z72m/usb_examples/usb_suspend_resume_device_hid_mouse_lite/bm">
<external path="boards/twrkl82z72m/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="twrkl82z72m_led_demo_pflash_a000" name="led_demo_pflash_a000" brief="The led_demo_pflash_a000 is a led blinky application load at offset 0xa000 of the target pflash memory on the 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="mcuxpresso" category="bootloader_examples/demo_apps" path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_pflash_a000">
<external path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_pflash_a000" type="xml">
<files mask="led_demo_pflash_a000.xml"/>
</external>
</example>
<example id="twrkl82z72m_led_demo_qspi_a000" name="led_demo_qspi_a000" brief="The led_demo_qspi_a000 is a led blinky application load at offset 0xa000 of the QuadSPI memory on the 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="mcuxpresso" category="bootloader_examples/demo_apps" path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_qspi_a000">
<external path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_qspi_a000" type="xml">
<files mask="led_demo_qspi_a000.xml"/>
</external>
</example>
<example id="twrkl82z72m_led_demo_tower_a000" name="led_demo_tower_a000" brief="The led_demo_tower_a000 is a led blinky application load at offset 0xa000 of the target flash memory on the Tower 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="mcuxpresso" category="bootloader_examples/demo_apps" path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_tower_a000">
<external path="boards/twrkl82z72m/bootloader_examples/demo_apps/led_demo_tower_a000" type="xml">
<files mask="led_demo_tower_a000.xml"/>
</external>
</example>
<example id="twrkl82z72m_tower_bootloader" name="tower_bootloader" brief="The tower_bootloader is a bootloader that executes from target flash memory on the Tower 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="mcuxpresso" category="bootloader_examples" path="boards/twrkl82z72m/bootloader_examples/tower_bootloader">
<external path="boards/twrkl82z72m/bootloader_examples/tower_bootloader" type="xml">
<files mask="tower_bootloader.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/hello_world">
<external path="boards/twrkl82z72m/demo_apps/hello_world" type="xml">
<files mask="hello_world.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/hello_world_virtual_com">
<external path="boards/twrkl82z72m/demo_apps/hello_world_virtual_com" type="xml">
<files mask="hello_world_virtual_com.xml"/>
</external>
</example>
<example id="twrkl82z72m_trng_random" name="trng_random" brief="The True Random Number Generator (TRNG) is a hardware accelerator module that generates a 512-bitentropy as needed by an entropy consuming module or by other post processing functions. The TRNGExample project is a demonstration program that uses the KSDK software to generate random numbersand prints them to the terminal." toolchain="mcuxpresso" category="driver_examples/trng" path="boards/twrkl82z72m/driver_examples/trng/random">
<external path="boards/twrkl82z72m/driver_examples/trng/random" type="xml">
<files mask="trng_random.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_dspi">
<external path="boards/twrkl82z72m/rtos_examples/freertos_dspi" type="xml">
<files mask="freertos_dspi.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_event">
<external path="boards/twrkl82z72m/rtos_examples/freertos_event" type="xml">
<files mask="freertos_event.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_generic">
<external path="boards/twrkl82z72m/rtos_examples/freertos_generic" type="xml">
<files mask="freertos_generic.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_hello">
<external path="boards/twrkl82z72m/rtos_examples/freertos_hello" type="xml">
<files mask="freertos_hello.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_i2c">
<external path="boards/twrkl82z72m/rtos_examples/freertos_i2c" type="xml">
<files mask="freertos_i2c.xml"/>
</external>
</example>
<example id="twrkl82z72m_freertos_lpuart" name="freertos_lpuart" brief="The LPUART example for FreeRTOS demonstrates the possibility to use the LPUART driver in the RTOS.The example uses single instance of LPUART IP and writes string into, then reads back chars.After every 4B received, these are sent back on LPUART." toolchain="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_lpuart">
<external path="boards/twrkl82z72m/rtos_examples/freertos_lpuart" type="xml">
<files mask="freertos_lpuart.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_mutex">
<external path="boards/twrkl82z72m/rtos_examples/freertos_mutex" type="xml">
<files mask="freertos_mutex.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_queue">
<external path="boards/twrkl82z72m/rtos_examples/freertos_queue" type="xml">
<files mask="freertos_queue.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_sem">
<external path="boards/twrkl82z72m/rtos_examples/freertos_sem" type="xml">
<files mask="freertos_sem.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_swtimer">
<external path="boards/twrkl82z72m/rtos_examples/freertos_swtimer" type="xml">
<files mask="freertos_swtimer.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="rtos_examples" path="boards/twrkl82z72m/rtos_examples/freertos_tickless">
<external path="boards/twrkl82z72m/rtos_examples/freertos_tickless" type="xml">
<files mask="freertos_tickless.xml"/>
</external>
</example>
<example id="twrkl82z72m_ltc_aes" name="ltc_aes" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption sampledata using AES-CBC, AES-CCM, and XCBC-MAC algorithm." toolchain="mcuxpresso" category="driver_examples/ltc" path="boards/twrkl82z72m/driver_examples/ltc/aes">
<external path="boards/twrkl82z72m/driver_examples/ltc/aes" type="xml">
<files mask="ltc_aes.xml"/>
</external>
</example>
<example id="twrkl82z72m_ltc_des" name="ltc_des" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption somedata using DES-cbc and DES3-cbc method." toolchain="mcuxpresso" category="driver_examples/ltc" path="boards/twrkl82z72m/driver_examples/ltc/des">
<external path="boards/twrkl82z72m/driver_examples/ltc/des" type="xml">
<files mask="ltc_des.xml"/>
</external>
</example>
<example id="twrkl82z72m_ltc_aes_edma" name="ltc_aes_edma" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption sample data using EDMA forAES-CBC algorithm." toolchain="mcuxpresso" category="driver_examples/ltc" path="boards/twrkl82z72m/driver_examples/ltc/aes_edma">
<external path="boards/twrkl82z72m/driver_examples/ltc/aes_edma" type="xml">
<files mask="ltc_aes_edma.xml"/>
</external>
</example>
<example id="twrkl82z72m_ltc_des_edma" name="ltc_des_edma" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption some data using EDMA for DES-cbc and DES3-cbc algorithm." toolchain="mcuxpresso" category="driver_examples/ltc" path="boards/twrkl82z72m/driver_examples/ltc/des_edma">
<external path="boards/twrkl82z72m/driver_examples/ltc/des_edma" type="xml">
<files mask="ltc_des_edma.xml"/>
</external>
</example>
<example id="twrkl82z72m_smartcard" name="smartcard" brief="This example demonstrates the SDK Peripheral drivers working with different methods.This example demonstrates use of smartcard driver API to read GSM sim card ICC-ID (Integrated circuit card identifier,which should be placed on the card). Please be aware, that this example is just simple demonstration of smartcard driver API. It may not work with all typesof GSM sim cards." toolchain="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/smartcard">
<external path="boards/twrkl82z72m/driver_examples/smartcard" type="xml">
<files mask="smartcard.xml"/>
</external>
</example>
<example id="twrkl82z72m_emvl1" name="emvl1" brief="The EMVL1 demo application demonstrates the interaction between the KSDK peripheral drivers and EMVL1 stack. The demoillustrates how to use the EMVL1 stack with the following methods:- CPU transfer using T0 / T1 protocolsThe example is intended to demonstrate a Point of Sale (POS) terminal, working with payment (credit/debit) cards.The example completes the transfer using both T0 and T1 modes and reads basic smart card information, like the card holder name, PAN,and expiration date.Note that this demo is just simple demonstration of the usage of the EMVL1 stack and smart card driver. Not all typesof payment cards are supported, and not all cards support the T1 protocol. This demo supports just one generic typeof MasterCard, Visa, Visa Electron, Amex and Europay, UnionPay Credit, and UnionPay Debit AIDs. If your credit carddoes not work, try another card." toolchain="mcuxpresso" category="emv_examples" path="boards/twrkl82z72m/emv_examples/emvl1">
<external path="boards/twrkl82z72m/emv_examples/emvl1" type="xml">
<files mask="emvl1.xml"/>
</external>
</example>
<example id="twrkl82z72m_emvl1_freertos" name="emvl1_freertos" brief="The EMVL1 demo application demonstrates the interaction between the KSDK peripheral drivers and EMVL1 stack withFreeRTOS. The demo illustrates how to use the EMVL1 stack with the following methods:- CPU transfer using T0 / T1 protocolsThe example is intended to demonstrate a Point of Sale (POS) terminal, working with payment (credit/debit) cards.The example completes the transfer using both T0 and T1 modes and reads basic smart card information, like the card holder name,PAN, and expiration date.Note that this demo is just a simple demonstration of the usage of the EMVL1 stack and smart card driver. Not all typesof payment cards are supported, and not all cards support the T1 protocol. This demo supports just one generic typeof MasterCard, Visa, Visa Electron, Amex and Europay, UnionPay Credit, and UnionPay Debit AIDs. If your credit carddoes not work, try another card." toolchain="mcuxpresso" category="emv_examples" path="boards/twrkl82z72m/emv_examples/emvl1_freertos">
<external path="boards/twrkl82z72m/emv_examples/emvl1_freertos" type="xml">
<files mask="emvl1_freertos.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/gpio" path="boards/twrkl82z72m/driver_examples/gpio/led_output">
<external path="boards/twrkl82z72m/driver_examples/gpio/led_output" type="xml">
<files mask="gpio_led_output.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/gpio" path="boards/twrkl82z72m/driver_examples/gpio/input_interrupt">
<external path="boards/twrkl82z72m/driver_examples/gpio/input_interrupt" type="xml">
<files mask="gpio_input_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/lptmr">
<external path="boards/twrkl82z72m/driver_examples/lptmr" type="xml">
<files mask="lptmr.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/pit">
<external path="boards/twrkl82z72m/driver_examples/pit" type="xml">
<files mask="pit.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/sysmpu">
<external path="boards/twrkl82z72m/driver_examples/sysmpu" type="xml">
<files mask="sysmpu.xml"/>
</external>
</example>
<example id="twrkl82z72m_tsi_v4_normal_mode" name="tsi_v4_normal_mode" brief="The tsi_v4_normal example shows how to use TSI_V4 driver in normal modes:In this example , we make use of the available electrodes on board to show driver usage.1. Firstly, we get the non-touch calibration results as baseline electrode counter;2. Then, we start the Software-Trigger scan using polling method and interrupt method;3. Then, we start the Hardware-Trigger scan using interrupt method." toolchain="mcuxpresso" category="driver_examples/tsi_v4" path="boards/twrkl82z72m/driver_examples/tsi_v4/normal">
<external path="boards/twrkl82z72m/driver_examples/tsi_v4/normal" type="xml">
<files mask="tsi_v4_normal_mode.xml"/>
</external>
</example>
<example id="twrkl82z72m_tsi_v4_low_power_mode" name="tsi_v4_low_power_mode" brief="The tsi_v4_low_power example shows how to use TSI_V4 driver in low power modes:In this example , we make use of the available electrodes on board to show driver usage.1. Firstly, we get the non-touch calibration results as baseline electrode counter;2. Then, we start the Hardware-Trigger scan using interrupt method to wakeup from low power modes through pad touch;3. Note: you can select which low power mode you want to enter into." toolchain="mcuxpresso" category="driver_examples/tsi_v4" path="boards/twrkl82z72m/driver_examples/tsi_v4/low_power">
<external path="boards/twrkl82z72m/driver_examples/tsi_v4/low_power" type="xml">
<files mask="tsi_v4_low_power_mode.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/cmp" path="boards/twrkl82z72m/driver_examples/cmp/polling">
<external path="boards/twrkl82z72m/driver_examples/cmp/polling" type="xml">
<files mask="cmp_polling.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/cmp" path="boards/twrkl82z72m/driver_examples/cmp/interrupt">
<external path="boards/twrkl82z72m/driver_examples/cmp/interrupt" type="xml">
<files mask="cmp_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/wdog">
<external path="boards/twrkl82z72m/driver_examples/wdog" type="xml">
<files mask="wdog.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/crc">
<external path="boards/twrkl82z72m/driver_examples/crc" type="xml">
<files mask="crc.xml"/>
</external>
</example>
<example id="twrkl82z72m_lpuart_interrupt_transfer" name="lpuart_interrupt_transfer" brief="The lpuart_interrupt Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" category="driver_examples/lpuart" path="boards/twrkl82z72m/driver_examples/lpuart/interrupt_transfer">
<external path="boards/twrkl82z72m/driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_lpuart_interrupt" name="lpuart_interrupt" brief="The lpuart_functioncal_interrupt example shows how to use lpuart driver functionalAPI to receive data with interrupt method:In this example, one lpuart instance connect to PC, the board willsend back all characters that PC send to the board." toolchain="mcuxpresso" category="driver_examples/lpuart" path="boards/twrkl82z72m/driver_examples/lpuart/interrupt">
<external path="boards/twrkl82z72m/driver_examples/lpuart/interrupt" type="xml">
<files mask="lpuart_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_lpuart_polling" name="lpuart_polling" brief="The lpuart_polling Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console instantly." toolchain="mcuxpresso" category="driver_examples/lpuart" path="boards/twrkl82z72m/driver_examples/lpuart/polling">
<external path="boards/twrkl82z72m/driver_examples/lpuart/polling" type="xml">
<files mask="lpuart_polling.xml"/>
</external>
</example>
<example id="twrkl82z72m_lpuart_interrupt_rb_transfer" name="lpuart_interrupt_rb_transfer" brief="The lpuart_interrupt_ring_buffer Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" category="driver_examples/lpuart" path="boards/twrkl82z72m/driver_examples/lpuart/interrupt_rb_transfer">
<external path="boards/twrkl82z72m/driver_examples/lpuart/interrupt_rb_transfer" type="xml">
<files mask="lpuart_interrupt_rb_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_lpuart_edma_transfer" name="lpuart_edma_transfer" brief="The lpuart_edma Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" category="driver_examples/lpuart" path="boards/twrkl82z72m/driver_examples/lpuart/edma_transfer">
<external path="boards/twrkl82z72m/driver_examples/lpuart/edma_transfer" type="xml">
<files mask="lpuart_edma_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/dac_adc">
<external path="boards/twrkl82z72m/demo_apps/dac_adc" type="xml">
<files mask="dac_adc.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/dac" path="boards/twrkl82z72m/driver_examples/dac/basic">
<external path="boards/twrkl82z72m/driver_examples/dac/basic" type="xml">
<files mask="dac_basic.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/dac" path="boards/twrkl82z72m/driver_examples/dac/buffer_interrupt">
<external path="boards/twrkl82z72m/driver_examples/dac/buffer_interrupt" type="xml">
<files mask="dac_buffer_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_dac_continuous_pit_edma" name="dac_continuous_pit_edma" brief="The demo shows how to use the PIT to generate a DAC trigger and use the EDMA to transfer data into DAC buffer.In this example, DAC is first set to normal buffer mode. PIT is as DAC hardware trigger source and EDMA would work when DAC read pointer is zero. When run the example, the DAC is triggered by PIT and the read pointer increases by one,every time the trigger occurs. When the read pointer reaches the upper limit, it goes to zero directly in the next trigger event.While read pointer goes to zero, EDMA request will be triggered and transfer data into DAC buffer. The user should probethe DAC output with a oscilloscope to see the Half-sine signal." toolchain="mcuxpresso" category="driver_examples/dac" path="boards/twrkl82z72m/driver_examples/dac/continuous_pit_edma">
<external path="boards/twrkl82z72m/driver_examples/dac/continuous_pit_edma" type="xml">
<files mask="dac_continuous_pit_edma.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/adc16" path="boards/twrkl82z72m/driver_examples/adc16/interrupt">
<external path="boards/twrkl82z72m/driver_examples/adc16/interrupt" type="xml">
<files mask="adc16_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/adc16" path="boards/twrkl82z72m/driver_examples/adc16/polling">
<external path="boards/twrkl82z72m/driver_examples/adc16/polling" type="xml">
<files mask="adc16_polling.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/adc16" path="boards/twrkl82z72m/driver_examples/adc16/continuous_edma">
<external path="boards/twrkl82z72m/driver_examples/adc16/continuous_edma" type="xml">
<files mask="adc16_continuous_edma.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/edma" path="boards/twrkl82z72m/driver_examples/edma/memory_to_memory">
<external path="boards/twrkl82z72m/driver_examples/edma/memory_to_memory" type="xml">
<files mask="edma_memory_to_memory.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/edma" path="boards/twrkl82z72m/driver_examples/edma/scatter_gather">
<external path="boards/twrkl82z72m/driver_examples/edma/scatter_gather" type="xml">
<files mask="edma_scatter_gather.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_polling_b2b_transfer_master" name="dspi_polling_b2b_transfer_master" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/polling_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/dspi/polling_b2b_transfer/master" type="xml">
<files mask="dspi_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_polling_b2b_transfer_slave" name="dspi_polling_b2b_transfer_slave" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/polling_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/dspi/polling_b2b_transfer/slave" type="xml">
<files mask="dspi_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_interrupt_b2b_transfer_master" name="dspi_interrupt_b2b_transfer_master" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_master.c' includes the DSPI master code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b_transfer/master" type="xml">
<files mask="dspi_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_interrupt_b2b_transfer_slave" name="dspi_interrupt_b2b_transfer_slave" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_slave.c' includes the DSPI slave code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b_transfer/slave" type="xml">
<files mask="dspi_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_interrupt_b2b_master" name="dspi_interrupt_b2b_master" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_master.c' includes the DSPI master code.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="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b/master">
<external path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b/master" type="xml">
<files mask="dspi_interrupt_b2b_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_interrupt_b2b_slave" name="dspi_interrupt_b2b_slave" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_slave.c' includes the DSPI slave code.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="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b/slave">
<external path="boards/twrkl82z72m/driver_examples/dspi/interrupt_b2b/slave" type="xml">
<files mask="dspi_interrupt_b2b_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_edma_b2b_transfer_master" name="dspi_edma_b2b_transfer_master" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/edma_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/dspi/edma_b2b_transfer/master" type="xml">
<files mask="dspi_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_edma_b2b_transfer_slave" name="dspi_edma_b2b_transfer_slave" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/edma_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/dspi/edma_b2b_transfer/slave" type="xml">
<files mask="dspi_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/rtc">
<external path="boards/twrkl82z72m/driver_examples/rtc" type="xml">
<files mask="rtc.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/ewm">
<external path="boards/twrkl82z72m/driver_examples/ewm" type="xml">
<files mask="ewm.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/read_accel_value_transfer">
<external path="boards/twrkl82z72m/driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/interrupt">
<external path="boards/twrkl82z72m/driver_examples/i2c/interrupt" type="xml">
<files mask="i2c_interrupt.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/interrupt_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/i2c/interrupt_b2b_transfer/master" type="xml">
<files mask="i2c_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/interrupt_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/i2c/interrupt_b2b_transfer/slave" type="xml">
<files mask="i2c_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/polling_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/i2c/polling_b2b_transfer/master" type="xml">
<files mask="i2c_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/polling_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/i2c/polling_b2b_transfer/slave" type="xml">
<files mask="i2c_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_i2c_edma_b2b_transfer_master" name="i2c_edma_b2b_transfer_master" brief="The 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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/edma_b2b_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/i2c/edma_b2b_transfer/master" type="xml">
<files mask="i2c_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_i2c_edma_b2b_transfer_slave" name="i2c_edma_b2b_transfer_slave" brief="The 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="mcuxpresso" category="driver_examples/i2c" path="boards/twrkl82z72m/driver_examples/i2c/edma_b2b_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/i2c/edma_b2b_transfer/slave" type="xml">
<files mask="i2c_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_qspi_polling_transfer" name="qspi_polling_transfer" brief="The qspi_polling example shows how to use qspi driver with polling:In this example, qspi will send data and operate the external flash connected with QSPI. Some simple flash command willbe executed, such as Write Enable, Erase sector, Program page.Example will first erase the sector and programe a page into the flash, at last check if the data in flash is correct.Notice: While do program, it is not suggested to make the flash write frequency bigger than the core clock frequency.In some tool chain's Debug version, this may cause core do not have enough speed to send data to flash.The flash write frequency equals to QSPI working frequency plus data line number. For example, if QSPI working in 48MHz,program command uses quad mode, the write frequency is 48MHz * 4 = 192MHz." toolchain="mcuxpresso" category="driver_examples/qspi" path="boards/twrkl82z72m/driver_examples/qspi/polling_transfer">
<external path="boards/twrkl82z72m/driver_examples/qspi/polling_transfer" type="xml">
<files mask="qspi_polling_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_qspi_edma_transfer" name="qspi_edma_transfer" brief="The qspi_edma example shows how to use qspi driver with EDMA:In this example, qspi will send data and operate the external flash connected with QSPI. Some simple flash command willbe executed, such as Write Enable, Erase sector, Program page.Example will first erase the sector and programe a page into the flash, at last check if the data in flash is correct." toolchain="mcuxpresso" category="driver_examples/qspi" path="boards/twrkl82z72m/driver_examples/qspi/edma_transfer">
<external path="boards/twrkl82z72m/driver_examples/qspi/edma_transfer" type="xml">
<files mask="qspi_edma_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_uart_polling_transfer" name="flexio_uart_polling_transfer" brief="The flexio_uart_polling example shows how to use flexio uart driver in polling way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send backall characters that PC send to the board." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/uart/polling_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/uart/polling_transfer" type="xml">
<files mask="flexio_uart_polling_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_uart_interrupt_transfer" name="flexio_uart_interrupt_transfer" brief="The flexio_uart_interrupt example shows how to use flexio uart driver in interrupt way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send back all charactersthat PC send to the board. Note: two queued transfer in this example, so please input even number characters." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/uart/interrupt_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/uart/interrupt_transfer" type="xml">
<files mask="flexio_uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_uart_int_rb_transfer" name="flexio_uart_int_rb_transfer" brief="The flexio_uart_interrupt_ring_buffer example shows how to use flexio uart driver in interrupt way withRX ring buffer enabled:In this example, a flexio simulated uart connect to PC through USB-Serial, 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="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/uart/int_rb_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/uart/int_rb_transfer" type="xml">
<files mask="flexio_uart_int_rb_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_pflash" name="pflash" brief="The pflash example shows how to use flash driver to operate program flash:" toolchain="mcuxpresso" category="driver_examples/flash" path="boards/twrkl82z72m/driver_examples/flash/pflash">
<external path="boards/twrkl82z72m/driver_examples/flash/pflash" type="xml">
<files mask="pflash.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/mcg" path="boards/twrkl82z72m/driver_examples/mcg/pee_blpi">
<external path="boards/twrkl82z72m/driver_examples/mcg/pee_blpi" type="xml">
<files mask="mcg_pee_blpi.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/mcg" path="boards/twrkl82z72m/driver_examples/mcg/fei_blpi">
<external path="boards/twrkl82z72m/driver_examples/mcg/fei_blpi" type="xml">
<files mask="mcg_fei_blpi.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="driver_examples/mcg" path="boards/twrkl82z72m/driver_examples/mcg/pee_blpe">
<external path="boards/twrkl82z72m/driver_examples/mcg/pee_blpe" type="xml">
<files mask="mcg_pee_blpe.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_uart_edma_transfer" name="flexio_uart_edma_transfer" brief="The flexio_uart_edma example shows how to use flexio uart driver in edma way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send back all charactersthat PC send to the board." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/uart/edma_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/uart/edma_transfer" type="xml">
<files mask="flexio_uart_edma_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_spi_int_dspi_transfer_master" name="flexio_spi_int_dspi_transfer_master" brief="The flexio_spi_master_interrupt_dspi_slave example shows how to use flexio spi master driver in interrupt way:In this example, a flexio simulated master connect to a dspi slave ." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/spi/int_dspi_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/flexio/spi/int_dspi_transfer/master" type="xml">
<files mask="flexio_spi_int_dspi_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_spi_int_dspi_transfer_slave" name="flexio_spi_int_dspi_transfer_slave" brief="The flexio_spi_slave_interrupt_dspi_master example shows how to use flexio spi slave driver in interrupt way:In this example, a flexio simulated slave connect to a dspi master." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/spi/int_dspi_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/flexio/spi/int_dspi_transfer/slave" type="xml">
<files mask="flexio_spi_int_dspi_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_spi_edma_dspi_transfer_master" name="flexio_spi_edma_dspi_transfer_master" brief="The flexio_spi_master_edma_dspi_slave example shows how to use flexio spi master driver in edma way:In this example, a flexio simulated master connect to a dspi slave ." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/spi/edma_dspi_transfer/master">
<external path="boards/twrkl82z72m/driver_examples/flexio/spi/edma_dspi_transfer/master" type="xml">
<files mask="flexio_spi_edma_dspi_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_spi_edma_dspi_transfer_slave" name="flexio_spi_edma_dspi_transfer_slave" brief="The flexio_spi_slave_edma_dspi_master example shows how to use flexio spi slave driver in dma way:In this example, a flexio simulated slave connect to a dspi master." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/spi/edma_dspi_transfer/slave">
<external path="boards/twrkl82z72m/driver_examples/flexio/spi/edma_dspi_transfer/slave" type="xml">
<files mask="flexio_spi_edma_dspi_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_i2c_interrupt_i2c_transfer" name="flexio_i2c_interrupt_i2c_transfer" brief="The flexio_i2c_interrupt example shows how to use flexio i2c master driver in interrupt way:In this example, a flexio simulated i2c master connect to an I2C slave." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/i2c/interrupt_i2c_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/i2c/interrupt_i2c_transfer" type="xml">
<files mask="flexio_i2c_interrupt_i2c_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_i2c_read_accel_value_transfer" name="flexio_i2c_read_accel_value_transfer" brief="The flexio_i2c_read_accel_value example shows how to use FLEXIO I2C Master driver to communicate with an i2c device: 1. How to use the flexio i2c master driver to read a i2c device who_am_I register. 2. How to use the flexio i2c master 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="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/i2c/read_accel_value_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/i2c/read_accel_value_transfer" type="xml">
<files mask="flexio_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_pwm_twochannel" name="tpm_pwm_twochannel" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The PWM dutycycle on both channelsis manually updated. On boards that have an LED connected to the TPM pins, the user will seea change in LED brightness if user enter different values." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/pwm_twochannel">
<external path="boards/twrkl82z72m/driver_examples/tpm/pwm_twochannel" type="xml">
<files mask="tpm_pwm_twochannel.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/adc16_low_power">
<external path="boards/twrkl82z72m/demo_apps/adc16_low_power" type="xml">
<files mask="adc16_low_power.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/rtc_func">
<external path="boards/twrkl82z72m/demo_apps/rtc_func" type="xml">
<files mask="rtc_func.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/power_manager">
<external path="boards/twrkl82z72m/demo_apps/power_manager" type="xml">
<files mask="power_manager.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/power_mode_switch">
<external path="boards/twrkl82z72m/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/ecompass">
<external path="boards/twrkl82z72m/demo_apps/ecompass" type="xml">
<files mask="ecompass.xml"/>
</external>
</example>
<example id="twrkl82z72m_hello_world_qspi" name="hello_world_qspi" brief="The Hello World QSPI demo application provides a sanity check for new SDK build environments and board bring up. Itprints the "Hello World" string to the terminal using the SDK UART drivers. The purpose of this demo is to show how tocompile SDK applications to run and boot from QSPI flash or a QSPI alias region.This example can generate two different demos using a different linker file and a startup file:Program boot from QSPI region.Program boot from QSPI alias region (if the chip supports QSPI alias region)." toolchain="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/hello_world_qspi">
<external path="boards/twrkl82z72m/demo_apps/hello_world_qspi" type="xml">
<files mask="hello_world_qspi.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_simple_pwm" name="tpm_simple_pwm" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output a center-aligned PWM signal. The PWM dutycycle is manually updated.On boards that have an LED connected to the TPM pins, the user will see a change in LEDbrightness if user enter different values." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/simple_pwm">
<external path="boards/twrkl82z72m/driver_examples/tpm/simple_pwm" type="xml">
<files mask="tpm_simple_pwm.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_timer" name="tpm_timer" brief="The TPM project is a simple demonstration program of the SDK TPM driver to use TPM as a timer.It sets up the TPM hardware block to trigger an interrupt every 1 millisecond.When the TPM interrupt is triggered a message a printed on the UART terminal." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/timer">
<external path="boards/twrkl82z72m/driver_examples/tpm/timer" type="xml">
<files mask="tpm_timer.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_output_compare" name="tpm_output_compare" brief="The TPM project is a demonstration program of the SDK TPM driver's output compare feature.It sets up one TPM channel to toggle the output when a match occurs with the channel value. The usershould probe the TPM output with a oscilloscope to see the signal toggling." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/output_compare">
<external path="boards/twrkl82z72m/driver_examples/tpm/output_compare" type="xml">
<files mask="tpm_output_compare.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_input_capture" name="tpm_input_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's input capture feature.The example sets up a TPM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/input_capture">
<external path="boards/twrkl82z72m/driver_examples/tpm/input_capture" type="xml">
<files mask="tpm_input_capture.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_combine_pwm" name="tpm_combine_pwm" brief="The TPM project is a demonstration program of generating a combined PWM signal by the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The example also show's the complementary mode of operationand deadtime insertion.On boards that have 2 LEDs connected to the TPM pins, the user will seea change in LED brightness if user enter different values.And if the board do not support LEDs to show, the outputs can be observed by oscilloscope." toolchain="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/combine_pwm">
<external path="boards/twrkl82z72m/driver_examples/tpm/combine_pwm" type="xml">
<files mask="tpm_combine_pwm.xml"/>
</external>
</example>
<example id="twrkl82z72m_tpm_dual_edge_capture" name="tpm_dual_edge_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's dual-edge capture feature.This feature is available only on certain SoC's.The example sets up a TPM 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="mcuxpresso" category="driver_examples/tpm" path="boards/twrkl82z72m/driver_examples/tpm/dual_edge_capture">
<external path="boards/twrkl82z72m/driver_examples/tpm/dual_edge_capture" type="xml">
<files mask="tpm_dual_edge_capture.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_i2s_interrupt_transfer" name="flexio_i2s_interrupt_transfer" brief="The flexio_i2s_interrupt example shows how to use flexio_i2s driver with interrupt:In this example, flexio acts as I2S module to record data from line-in line and playbacks the recorded data at the same time using interrupt." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/i2s/interrupt_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/i2s/interrupt_transfer" type="xml">
<files mask="flexio_i2s_interrupt_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_i2s_edma_transfer" name="flexio_i2s_edma_transfer" brief="The flexio_i2s_EDMA example shows how to use flexio_i2s driver with EDMA:In this example, flexio acts as I2S module to record data from line-in line and playbacks the recorded data at the same time using EDMA." toolchain="mcuxpresso" category="driver_examples/flexio" path="boards/twrkl82z72m/driver_examples/flexio/i2s/edma_transfer">
<external path="boards/twrkl82z72m/driver_examples/flexio/i2s/edma_transfer" type="xml">
<files mask="flexio_i2s_edma_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_flexio_pwm" name="flexio_pwm" brief="This demo describes how to use SDK drivers to implement the PWM feature by FLEXIO IP module. It outputs the PWM singal with fixed frequency defined by "DEMO_FLEXIO_FREQUENCY" in source code and dynamic duty from 99 to 1 to one of the FLEXIO pin." toolchain="mcuxpresso" category="driver_examples" path="boards/twrkl82z72m/driver_examples/flexio/pwm">
<external path="boards/twrkl82z72m/driver_examples/flexio/pwm" type="xml">
<files mask="flexio_pwm.xml"/>
</external>
</example>
<example id="twrkl82z72m_adc16_potentiometer" name="adc16_potentiometer" brief="The ADC potentiometer demo application demonstrates how to read the analog value from a hardware potentiometer via theADC peripheral." toolchain="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/adc16_potentiometer">
<external path="boards/twrkl82z72m/demo_apps/adc16_potentiometer" type="xml">
<files mask="adc16_potentiometer.xml"/>
</external>
</example>
<example id="twrkl82z72m_adc16_low_power_async_edma" name="adc16_low_power_async_edma" brief="The ADC Low Power Async DMA demo application demonstrates the usage of the ADC and DMA peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 100 ms, low power timer trigger the ADC module convertvalue on ADC channel. After 16 times(1,6s) the DMA transfer finish interrupt wake up the CPU to process sampled data, print result touser and toggle LED." toolchain="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/adc16_low_power_async_edma">
<external path="boards/twrkl82z72m/demo_apps/adc16_low_power_async_edma" type="xml">
<files mask="adc16_low_power_async_edma.xml"/>
</external>
</example>
<example id="twrkl82z72m_shell" name="shell" brief="The Shell Demo application demonstrates to control Leds by commands." toolchain="mcuxpresso" category="demo_apps" path="boards/twrkl82z72m/demo_apps/shell">
<external path="boards/twrkl82z72m/demo_apps/shell" type="xml">
<files mask="shell.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_lpuart_interrupt_transfer" name="cmsis_lpuart_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="mcuxpresso" category="cmsis_driver_examples/lpuart" path="boards/twrkl82z72m/cmsis_driver_examples/lpuart/interrupt_transfer">
<external path="boards/twrkl82z72m/cmsis_driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="cmsis_lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_lpuart_edma_transfer" name="cmsis_lpuart_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="mcuxpresso" category="cmsis_driver_examples/lpuart" path="boards/twrkl82z72m/cmsis_driver_examples/lpuart/edma_transfer">
<external path="boards/twrkl82z72m/cmsis_driver_examples/lpuart/edma_transfer" type="xml">
<files mask="cmsis_lpuart_edma_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_dspi_edma_b2b_transfer_master" name="cmsis_dspi_edma_b2b_transfer_master" brief="The dspi_edma_b2b_transfer example shows how to use DSPI CMSIS driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in edma . " toolchain="mcuxpresso" category="cmsis_driver_examples/dspi" path="boards/twrkl82z72m/cmsis_driver_examples/dspi/edma_b2b_transfer/master">
<external path="boards/twrkl82z72m/cmsis_driver_examples/dspi/edma_b2b_transfer/master" type="xml">
<files mask="cmsis_dspi_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_dspi_edma_b2b_transfer_slave" name="cmsis_dspi_edma_b2b_transfer_slave" brief="The dspi_edma_b2b_transfer example shows how to use DSPI CMSIS driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in edma . " toolchain="mcuxpresso" category="cmsis_driver_examples/dspi" path="boards/twrkl82z72m/cmsis_driver_examples/dspi/edma_b2b_transfer/slave">
<external path="boards/twrkl82z72m/cmsis_driver_examples/dspi/edma_b2b_transfer/slave" type="xml">
<files mask="cmsis_dspi_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_dspi_int_b2b_transfer_master" name="cmsis_dspi_int_b2b_transfer_master" brief="The dspi_int_b2b_transfer example shows how to use DSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_int_b2b_transfer_master.c' includes the DSPI master code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . " toolchain="mcuxpresso" category="cmsis_driver_examples/dspi" path="boards/twrkl82z72m/cmsis_driver_examples/dspi/int_b2b_transfer/master">
<external path="boards/twrkl82z72m/cmsis_driver_examples/dspi/int_b2b_transfer/master" type="xml">
<files mask="cmsis_dspi_int_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_cmsis_dspi_int_b2b_transfer_slave" name="cmsis_dspi_int_b2b_transfer_slave" brief="The dspi_int_b2b_transfer example shows how to use DSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_int_b2b_transfer_slave.c' includes the DSPI slave code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . " toolchain="mcuxpresso" category="cmsis_driver_examples/dspi" path="boards/twrkl82z72m/cmsis_driver_examples/dspi/int_b2b_transfer/slave">
<external path="boards/twrkl82z72m/cmsis_driver_examples/dspi/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_dspi_int_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="cmsis_driver_examples/i2c" path="boards/twrkl82z72m/cmsis_driver_examples/i2c/read_accel_value_transfer">
<external path="boards/twrkl82z72m/cmsis_driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="cmsis_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="cmsis_driver_examples/i2c" path="boards/twrkl82z72m/cmsis_driver_examples/i2c/int_b2b_transfer/master">
<external path="boards/twrkl82z72m/cmsis_driver_examples/i2c/int_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="cmsis_driver_examples/i2c" path="boards/twrkl82z72m/cmsis_driver_examples/i2c/int_b2b_transfer/slave">
<external path="boards/twrkl82z72m/cmsis_driver_examples/i2c/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="cmsis_driver_examples/i2c" path="boards/twrkl82z72m/cmsis_driver_examples/i2c/edma_b2b_transfer/master">
<external path="boards/twrkl82z72m/cmsis_driver_examples/i2c/edma_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_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="mcuxpresso" category="cmsis_driver_examples/i2c" path="boards/twrkl82z72m/cmsis_driver_examples/i2c/edma_b2b_transfer/slave">
<external path="boards/twrkl82z72m/cmsis_driver_examples/i2c/edma_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_half_duplex_polling_master" name="dspi_half_duplex_polling_master" brief="The dspi_half_duplex_polling_transfer_master example shows how to use driver API to transfer in half-duplex way. In this example, one spi instance as master and another spi instance on the other board as slave. Master sends apiece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct. Besides, master will transfer in polling way. " toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/half_duplex_transfer/polling/master">
<external path="boards/twrkl82z72m/driver_examples/dspi/half_duplex_transfer/polling/master" type="xml">
<files mask="dspi_half_duplex_polling_master.xml"/>
</external>
</example>
<example id="twrkl82z72m_dspi_half_duplex_polling_slave" name="dspi_half_duplex_polling_slave" brief="The dspi_half_duplex_polling_transfer_slave example shows how to receive and transmit data to master board.Notice: The SPI slave of this example uses interrupt mode. The data transfer size(not buffer size) is twice ofthe master's transfer size. The first half of the transmission will receive data, and the second half will senddata back to master, so the address of the receive buffer is &rxDataPolling[64].In this example, one spi instance as slave and another spi 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 master is correct. And slave will print what it received." toolchain="mcuxpresso" category="driver_examples/dspi" path="boards/twrkl82z72m/driver_examples/dspi/half_duplex_transfer/polling/slave">
<external path="boards/twrkl82z72m/driver_examples/dspi/half_duplex_transfer/polling/slave" type="xml">
<files mask="dspi_half_duplex_polling_slave.xml"/>
</external>
</example>