-
Notifications
You must be signed in to change notification settings - Fork 24
/
Copy pathMKE14Z64xxx4_manifest_v3_10.xml
8373 lines (8373 loc) · 475 KB
/
MKE14Z64xxx4_manifest_v3_10.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_MKE14Z64xxx4" name="MKE14Z64xxx4" brief="This is SDK version 2.12.0 manifest file. It describes the content of the MKE14Z64xxx4 and additional settings for tools that support SDK version 2.12.0" format_version="3.10" api_version="2.0.0" configuration="4bc1a6852e233b3525d95eccefea9ec0" xsi:schemaLocation="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd http://nxp.com/mcuxpresso/sdk/sdk_manifest_v3.10.xsd">
<!--Timestamp (UTC): 2022-07-15 12:16:15.875045-->
<!--This manifest is generated based on sdk repo commit: 45d71c921a1dd3e0403549aa377535344ed9bc97-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<ksdk id="MCUXpresso2120" name="MCUXpresso2120" version="2.12.0" revision="epluginsite611 2022-07-14"/>
<compilers>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
</compilers>
<toolchainSettings>
<toolchainSetting id="com.nxp.mcuxpresso" name="mcuxpresso" version="11.6.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="11.6.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="frdmke16z" name="FRDM-KE16Z" href="https://www.nxp.com/pip/FRDM-KE16Z" version="1.0.0" package="MKE16Z64VLF4">
<description>FRDM-KE16Z: Freedom Development Platform for Kinetis KE1xMCUs</description>
<image path="boards/frdmke16z" type="image">
<files mask="frdmke16z.png"/>
</image>
<examples>
<example id="frdmke16z_acmp_interrupt" name="acmp_interrupt" brief="The ACMP Interrupt project is a simple demonstration program that uses the SDK software. Itcompares the selected analog input with ACMP internal DAC output continuously and toggle the LEDwhen the final comparison result changed. The purpose of this demo is to show how to use theACMP driver in SDK software by interrupt way. The ACMP can be configured based on defaultconfiguration returned by the API ACMP_GetDefaultConfig(). The default configuration is: highspeed is not enabled, invert output is not enabled, unfiltered output is not enabled, pin outis not enabled, offset level is level 0, hysteresis level is level 0." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/acmp" path="boards/frdmke16z/driver_examples/acmp/interrupt">
<external path="boards/frdmke16z/driver_examples/acmp/interrupt" type="xml">
<files mask="acmp_interrupt_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_acmp_polling" name="acmp_polling" brief="The ACMP Polling project is a simple demonstration program that uses the SDK software. It comparesthe selected analog input with ACMP internal DAC output continuously and toggle the LED when thefinal comparison result changed. The purpose of this demo is to show how to use the ACMP driverin SDK software by polling way. The ACMP can be configured based on default configuration returnedby the API ACMP_GetDefaultConfig(). The default configuration is: high speed is not enabled, invertoutput is not enabled, unfiltered output is not enabled, pin out is not enabled, offset level islevel 0, hysteresis level is level 0." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/acmp" path="boards/frdmke16z/driver_examples/acmp/polling">
<external path="boards/frdmke16z/driver_examples/acmp/polling" type="xml">
<files mask="acmp_polling_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_acmp_round_robin" name="acmp_round_robin" brief="The ACMP Round-Robin project is a simple demonstration program that uses the SDK software. Usermust set the round-robin mode trigger in specific board properly according to the board resourcebefore running the example. When the example running, it sets positive port as fixed channel andinternal DAC output as comparison reference in positive port and sets the channels input by useras round-robin checker channel. The example will enter stop mode and wait user to change the voltageof round-robin checker channel. It will exit stop mode after the voltage of round-robin checkerchannel changed by user." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/acmp" path="boards/frdmke16z/driver_examples/acmp/round_robin">
<external path="boards/frdmke16z/driver_examples/acmp/round_robin" type="xml">
<files mask="acmp_round_robin_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_adc12_interrupt" name="adc12_interrupt" brief="The adc12_interrupt example shows how to use interrupt with ADC12 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC12's sample 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 ADC12 interrupt configuration is set when configuring the ADC12's conversion channel. When in software trigger mode, the conversion would be launched by the operation of configuring channel, just like writing a conversion 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" compiler="compiler_gcc" category="driver_examples/adc12" path="boards/frdmke16z/driver_examples/adc12/interrupt">
<external path="boards/frdmke16z/driver_examples/adc12/interrupt" type="xml">
<files mask="adc12_interrupt_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_adc12_low_power" name="adc12_low_power" brief="The ADC Low Power Demo project is a demonstration program that uses the KSDK software. Themicrocontroller is set to a very low power stop (VLPS) mode, and every 500 ms an interrupt wakes upthe ADC module and takes the current temperature sensor value of the microcontroller. While the temperature remains within boundaries, both LEDs are on. If the temperature is higher or lower thanaverage, a led comes off. This demo provides an example to show how ADC works during a VLPS mode anda simple debugging." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/adc12_low_power">
<external path="boards/frdmke16z/demo_apps/adc12_low_power" type="xml">
<files mask="adc12_low_power_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_adc12_lpit_trgmux" name="adc12_lpit_trgmux" brief="The adc12_lpit_trgmux example shows how to use the LPIT and TRGMUX to generate a ADC trigger.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC12'ssample input. When run the example, the ADC is triggered by TRGMUX and gets the ADC conversion result in the ADCConversion Complete (COCO) Interrupt. The LPIT is configured as periodic counter which will output pre-trigger andtigger signal to TRGMUX periodically." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc12" path="boards/frdmke16z/driver_examples/adc12/lpit_trgmux">
<external path="boards/frdmke16z/driver_examples/adc12/lpit_trgmux" type="xml">
<files mask="adc12_lpit_trgmux_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_adc12_polling" name="adc12_polling" brief="The adc12_polling example shows the simplest way to use ADC12 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC12's sample 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 change theconfiguration 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 improve theADC12's performance." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc12" path="boards/frdmke16z/driver_examples/adc12/polling">
<external path="boards/frdmke16z/driver_examples/adc12/polling" type="xml">
<files mask="adc12_polling_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_bubble" name="bubble" brief="The bubble level demo demonstrates basic usage of the on-board accelerometer to implement a bubble level. A bubble level utilizes two axes to visually show deviation from a level plane (0 degrees) on a given axis." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/bubble">
<external path="boards/frdmke16z/demo_apps/bubble" type="xml">
<files mask="bubble_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_cmsis_lpi2c_int_b2b_transfer_master" name="cmsis_lpi2c_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 lpi2c_int_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 lpi2c instance as master and another lpi2c 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" compiler="compiler_gcc" category="cmsis_driver_examples/lpi2c" path="boards/frdmke16z/cmsis_driver_examples/lpi2c/int_b2b_transfer/master">
<external path="boards/frdmke16z/cmsis_driver_examples/lpi2c/int_b2b_transfer/master" type="xml">
<files mask="cmsis_lpi2c_int_b2b_transfer_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_cmsis_lpi2c_int_b2b_transfer_slave" name="cmsis_lpi2c_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 lpi2c_int_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 lpi2c instance as master and another lpi2c 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" compiler="compiler_gcc" category="cmsis_driver_examples/lpi2c" path="boards/frdmke16z/cmsis_driver_examples/lpi2c/int_b2b_transfer/slave">
<external path="boards/frdmke16z/cmsis_driver_examples/lpi2c/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_lpi2c_int_b2b_transfer_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_cmsis_lpspi_int_b2b_transfer_master" name="cmsis_lpspi_int_b2b_transfer_master" brief="The cmsis_lpspi_int_b2b_transfer example shows how to use LPSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'cmsis_lpspi_int_b2b_transfer_master.c' includes the LPSPI master code.This example uses the transactional API in LPSPI driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpspi" path="boards/frdmke16z/cmsis_driver_examples/lpspi/int_b2b_transfer/master">
<external path="boards/frdmke16z/cmsis_driver_examples/lpspi/int_b2b_transfer/master" type="xml">
<files mask="cmsis_lpspi_int_b2b_transfer_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_cmsis_lpspi_int_b2b_transfer_slave" name="cmsis_lpspi_int_b2b_transfer_slave" brief="The lpspi_int_b2b_transfer example shows how to use LPSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'cmsis_lpspi_int_b2b_transfer_slave.c' includes the LPSPI slave code.This example uses the transactional API in LPSPI driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpspi" path="boards/frdmke16z/cmsis_driver_examples/lpspi/int_b2b_transfer/slave">
<external path="boards/frdmke16z/cmsis_driver_examples/lpspi/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_lpspi_int_b2b_transfer_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="cmsis_driver_examples/lpuart" path="boards/frdmke16z/cmsis_driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmke16z/cmsis_driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="cmsis_lpuart_interrupt_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/crc" path="boards/frdmke16z/driver_examples/crc">
<external path="boards/frdmke16z/driver_examples/crc" type="xml">
<files mask="crc_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/ecompass">
<external path="boards/frdmke16z/demo_apps/ecompass" type="xml">
<files mask="ecompass_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/ewm" path="boards/frdmke16z/driver_examples/ewm">
<external path="boards/frdmke16z/driver_examples/ewm" type="xml">
<files mask="ewm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_fmstr_example_any" name="fmstr_example_any" brief="FreeMASTER example fully configured by MCUXpresso ConfigTools. Serial communication is used by default, but it can be changed easily to CAN or other in the MCUXpresso Peripheral Tool. Also FreeMASTER driver features are configured graphically in this tool. The Pins and Clock Tool are used to configure pin multiplexers and clocks. Just like other FreeMASTER examples, the application demonstrates use of FreeMASTER tool to visualize internal variables and to control the application flow by modifying variables. The application also shows use of advanced FreeMASTER features like TSA tables and Pipes." toolchain="mcuxpresso" compiler="compiler_gcc" category="FreeMASTER_examples" path="boards/frdmke16z/freemaster_examples/fmstr_any">
<external path="boards/frdmke16z/freemaster_examples/fmstr_any" type="xml">
<files mask="fmstr_example_any_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_fmstr_example_can" name="fmstr_example_can" brief="FreeMASTER example using the CAN bus to communicate with target microcontroller. This example application demonstrates use of FreeMASTER tool to visualize internal variables and to control the application flow by modifying variables. The application also shows use of advanced FreeMASTER features like TSA tables and Pipes." toolchain="mcuxpresso" compiler="compiler_gcc" category="FreeMASTER_examples" path="boards/frdmke16z/freemaster_examples/fmstr_can">
<external path="boards/frdmke16z/freemaster_examples/fmstr_can" type="xml">
<files mask="fmstr_example_can_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_fmstr_example_pdbdm" name="fmstr_example_pdbdm" brief="FreeMASTER example using a special packet-driven protocol on top of JTAG or BDM direct memory access. This example application demonstrates use of FreeMASTER tool to visualize internal variables and to control the application flow by modifying variables. The application also shows use of advanced FreeMASTER features like TSA tables and Pipes." toolchain="mcuxpresso" compiler="compiler_gcc" category="FreeMASTER_examples" path="boards/frdmke16z/freemaster_examples/fmstr_pdbdm">
<external path="boards/frdmke16z/freemaster_examples/fmstr_pdbdm" type="xml">
<files mask="fmstr_example_pdbdm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_fmstr_example_uart" name="fmstr_example_uart" brief="FreeMASTER example using Serial-UART communication with the target microcontroller. This example application demonstrates use of FreeMASTER tool to visualize internal variables and to control the application flow by modifying variables. The application also shows use of advanced FreeMASTER features like TSA tables and Pipes." toolchain="mcuxpresso" compiler="compiler_gcc" category="FreeMASTER_examples" path="boards/frdmke16z/freemaster_examples/fmstr_uart">
<external path="boards/frdmke16z/freemaster_examples/fmstr_uart" type="xml">
<files mask="fmstr_example_uart_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_freedom_bootloader" name="freedom_bootloader" brief="The freedom_bootloader is a bootloader that executes from target flash memory on the Freedom platform. The bootloader is a configurable flash programming utility that operates over a serial connection on MCU devices. It enables quick and easy programming of MCU devices through the entire product life cycle, including application development, final product manufacturing, and more.Host-side command line and GUI tools are available to communicate with the bootloader. Users can utilize host tools to upload and/or download application code via the bootloader." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples" path="boards/frdmke16z/bootloader_examples/freedom_bootloader">
<external path="boards/frdmke16z/bootloader_examples/freedom_bootloader" type="xml">
<files mask="freedom_bootloader_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_event">
<external path="boards/frdmke16z/rtos_examples/freertos_event" type="xml">
<files mask="freertos_event_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_generic">
<external path="boards/frdmke16z/rtos_examples/freertos_generic" type="xml">
<files mask="freertos_generic_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_hello">
<external path="boards/frdmke16z/rtos_examples/freertos_hello" type="xml">
<files mask="freertos_hello_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_freertos_lpi2c" name="freertos_lpi2c" brief="The LPI2C Example project is a demonstration program that uses the KSDK software to manipulate the Low Power Inter-Integrated Circuit.The example uses two instances of LPI2C, one in configured as master and the other one as slave.The LPI2C master sends data to LPI2C slave. The slave will check the data it receives and shows the log." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_lpi2c">
<external path="boards/frdmke16z/rtos_examples/freertos_lpi2c" type="xml">
<files mask="freertos_lpi2c_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_freertos_lpspi_b2b_master" name="freertos_lpspi_b2b_master" brief="The freertos_lpspi_b2b_master example shows how to use LPSPI driver in FreeRTOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_lpspi_b2b/master">
<external path="boards/frdmke16z/rtos_examples/freertos_lpspi_b2b/master" type="xml">
<files mask="freertos_lpspi_b2b_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_freertos_lpspi_b2b_slave" name="freertos_lpspi_b2b_slave" brief="The freertos_lpspi_b2b_slave example shows how to use LPSPI driver in FreeRTOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_lpspi_b2b/slave">
<external path="boards/frdmke16z/rtos_examples/freertos_lpspi_b2b/slave" type="xml">
<files mask="freertos_lpspi_b2b_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_lpuart">
<external path="boards/frdmke16z/rtos_examples/freertos_lpuart" type="xml">
<files mask="freertos_lpuart_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_mutex">
<external path="boards/frdmke16z/rtos_examples/freertos_mutex" type="xml">
<files mask="freertos_mutex_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_queue">
<external path="boards/frdmke16z/rtos_examples/freertos_queue" type="xml">
<files mask="freertos_queue_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_sem">
<external path="boards/frdmke16z/rtos_examples/freertos_sem" type="xml">
<files mask="freertos_sem_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_swtimer">
<external path="boards/frdmke16z/rtos_examples/freertos_swtimer" type="xml">
<files mask="freertos_swtimer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmke16z/rtos_examples/freertos_tickless">
<external path="boards/frdmke16z/rtos_examples/freertos_tickless" type="xml">
<files mask="freertos_tickless_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_combine_pwm" name="ftm_combine_pwm" brief="The FTM project is a demonstration program of generating a combined PWM signal by the SDK FTM driver. It sets up the FTMhardware block to output PWM signals on two TPM channels. The example also shows the complementary mode of operationand deadtime insertion.On boards that have 2 LEDs connected to the FTM pins, the user will see a change in LED brightness.And if the board do not support LEDs to show, the outputs can be observed by oscilloscope." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/combine_pwm">
<external path="boards/frdmke16z/driver_examples/ftm/combine_pwm" type="xml">
<files mask="ftm_combine_pwm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_dual_edge_capture" name="ftm_dual_edge_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's dual-edge capture feature.This feature is available only on certain SoC's.The example sets up a FTM channel-pair for dual-edge capture. Once the input signal is received,this example will print the capture values and period of the input signal on the terminal window." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/dual_edge_capture">
<external path="boards/frdmke16z/driver_examples/ftm/dual_edge_capture" type="xml">
<files mask="ftm_dual_edge_capture_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_input_capture" name="ftm_input_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's input capture feature.The example sets up a FTM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/input_capture">
<external path="boards/frdmke16z/driver_examples/ftm/input_capture" type="xml">
<files mask="ftm_input_capture_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_output_compare" name="ftm_output_compare" brief="The FTM project is a demonstration program of the SDK FTM driver's output compare feature.It sets up one FTM channel to toggle the output when a match occurs with the channel value. The usershould probe the FTM output with a oscilloscope to see the signal toggling." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/output_compare">
<external path="boards/frdmke16z/driver_examples/ftm/output_compare" type="xml">
<files mask="ftm_output_compare_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_pdb_adc12" name="ftm_pdb_adc12" brief="This application demonstrates how to use the trigger signal generated by FTM to trigger the ADCconversion through PDB module.For instance, the FTM0 is configured to work in PWM mode. And its channel 0 monitors the FTM counterand compares with the channel value. Once the FTM counter matches the channel value, an externaltrigger would be generated. TRGMUX would capture this trigger and route it to PDB module. When thePDB is triggered, the PDB counter increase. Once the PDB matches the ADC pre-trigger value, a triggersignal would generated and sent to ADC module. Finally, the ADC gets the trigger signal and start theconversion." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/ftm_pdb_adc12">
<external path="boards/frdmke16z/demo_apps/ftm_pdb_adc12" type="xml">
<files mask="ftm_pdb_adc12_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_pwm_twochannel" name="ftm_pwm_twochannel" brief="The FTM pwm two channel Example project is a demonstration program that uses the KSDK software to generate a square pulse PWM on 2 channel to control the LED brightness.- FTM generates a PWM with the increasing and decreasing duty cycle.- LED brightness is increasing and then dimming. This is a continuous process." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/pwm_twochannel">
<external path="boards/frdmke16z/driver_examples/ftm/pwm_twochannel" type="xml">
<files mask="ftm_pwm_twochannel_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_simple_pwm" name="ftm_simple_pwm" brief="The FTM project is a simple demonstration program of the SDK FTM driver. It sets up the FTMhardware block to output a center-aligned PWM signal. The PWM dutycycle is periodically updated.On boards that have an LED connected to the FTM pins, the user will see a change in LED brightness." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/simple_pwm">
<external path="boards/frdmke16z/driver_examples/ftm/simple_pwm" type="xml">
<files mask="ftm_simple_pwm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_ftm_timer" name="ftm_timer" brief="The FTM project is a simple demonstration program of the SDK FTM driver to use FTM as a timer.It sets up the FTM hardware block to trigger an interrupt every 1 millisecond.When the FTM interrupt is triggered a message a printed on the UART terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ftm" path="boards/frdmke16z/driver_examples/ftm/timer">
<external path="boards/frdmke16z/driver_examples/ftm/timer" type="xml">
<files mask="ftm_timer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmke16z/driver_examples/gpio/input_interrupt">
<external path="boards/frdmke16z/driver_examples/gpio/input_interrupt" type="xml">
<files mask="gpio_input_interrupt_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmke16z/driver_examples/gpio/led_output">
<external path="boards/frdmke16z/driver_examples/gpio/led_output" type="xml">
<files mask="gpio_led_output_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_hello_world" name="hello_world" brief="The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers and repeat what user input. The purpose of this demo is to show how to use the UART, and to provide a simple project for debugging and further development." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/hello_world">
<external path="boards/frdmke16z/demo_apps/hello_world" type="xml">
<files mask="hello_world_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_led_blinky" name="led_blinky" brief="The LED Blinky demo application provides a sanity check for the new SDK build environments and board bring up. The LED Blinky demo uses the systick interrupt to realize the function of timing delay. The example takes turns to shine the LED. The purpose of this demo is to provide a simple project for debugging and further development." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/led_blinky">
<external path="boards/frdmke16z/demo_apps/led_blinky" type="xml">
<files mask="led_blinky_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_log_bm" name="log_bm" brief="The log demo is used to demonstrate how to use log component. The main function of the demo is to prompt the LOG level string according to the user input log level command." toolchain="mcuxpresso" compiler="compiler_gcc" category="component_examples" path="boards/frdmke16z/component_examples/log/bm">
<external path="boards/frdmke16z/component_examples/log/bm" type="xml">
<files mask="log_bm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpi2c_interrupt_b2b_transfer_master" name="lpi2c_interrupt_b2b_transfer_master" brief="The lpi2c_interrupt_b2b_transfer_master example shows how to use lpi2c driver as master to do board to board transfer with interrupt:In this example, one lpi2c instance as master and another lpi2c 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" compiler="compiler_gcc" category="driver_examples/lpi2c" path="boards/frdmke16z/driver_examples/lpi2c/interrupt_b2b_transfer/master">
<external path="boards/frdmke16z/driver_examples/lpi2c/interrupt_b2b_transfer/master" type="xml">
<files mask="lpi2c_interrupt_b2b_transfer_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpi2c_interrupt_b2b_transfer_slave" name="lpi2c_interrupt_b2b_transfer_slave" brief="The lpi2c_interrupt_b2b_transfer_slave example shows how to use lpi2c driver as slave to do board to board transfer with interrupt:In this example, one lpi2c instance as slave and another lpi2c 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" compiler="compiler_gcc" category="driver_examples/lpi2c" path="boards/frdmke16z/driver_examples/lpi2c/interrupt_b2b_transfer/slave">
<external path="boards/frdmke16z/driver_examples/lpi2c/interrupt_b2b_transfer/slave" type="xml">
<files mask="lpi2c_interrupt_b2b_transfer_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpi2c_polling_b2b_master" name="lpi2c_polling_b2b_master" brief="The lpi2c_polling_b2b_master example shows how to use lpi2c driver as master to do board to board transfer using polling method:In this example, one lpi2c instance as master and another lpi2c 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" compiler="compiler_gcc" category="driver_examples/lpi2c" path="boards/frdmke16z/driver_examples/lpi2c/polling_b2b/master">
<external path="boards/frdmke16z/driver_examples/lpi2c/polling_b2b/master" type="xml">
<files mask="lpi2c_polling_b2b_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpi2c_polling_b2b_slave" name="lpi2c_polling_b2b_slave" brief="The lpi2c_polling_b2b_slave example shows how to use lpi2c driver as slave to do board to board transfer with a polling master:In this example, one lpi2c instance as slave and another lpi2c 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" compiler="compiler_gcc" category="driver_examples/lpi2c" path="boards/frdmke16z/driver_examples/lpi2c/polling_b2b/slave">
<external path="boards/frdmke16z/driver_examples/lpi2c/polling_b2b/slave" type="xml">
<files mask="lpi2c_polling_b2b_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpi2c_read_accel_value_transfer" name="lpi2c_read_accel_value_transfer" brief="The lpi2c_read_accel_value example shows how to use LPI2C driver to communicate with an lpi2c device: 1. How to use the lpi2c driver to read a lpi2c device who_am_I register. 2. How to use the lpi2c 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" compiler="compiler_gcc" category="driver_examples/lpi2c" path="boards/frdmke16z/driver_examples/lpi2c/read_accel_value_transfer">
<external path="boards/frdmke16z/driver_examples/lpi2c/read_accel_value_transfer" type="xml">
<files mask="lpi2c_read_accel_value_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpit_chained_channel" name="lpit_chained_channel" brief="The LPIT chained channel project is a simple example of the SDK LPIT driver. It sets up the LPIT hardware block to trigger a periodic interrupt after every 1 second in the channel No.0, the channel No.1 chained with channel No.0, if LPIT contain more than two channels, the channel No.2 chained with channel No.1....the channel No.N chained with Channel No.N-1. When the LPIT interrupt is triggered." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpit" path="boards/frdmke16z/driver_examples/lpit/chained_channel">
<external path="boards/frdmke16z/driver_examples/lpit/chained_channel" type="xml">
<files mask="lpit_chained_channel_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpit_single_channel" name="lpit_single_channel" brief="The LPIT single channel project is a simple example of the SDK LPIT driver. It sets up the LPIThardware block to trigger a periodic interrupt after every 1 second. When the LPIT interrupt is triggereda message a printed on the serial terminal and an LED is toggled on the board." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpit" path="boards/frdmke16z/driver_examples/lpit/single_channel">
<external path="boards/frdmke16z/driver_examples/lpit/single_channel" type="xml">
<files mask="lpit_single_channel_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_interrupt_b2b_master" name="lpspi_interrupt_b2b_master" brief="The lpspi_interrupt_b2b example shows how to use LPSPI driver in interrupt way:In this example , we need two boards , one board used as LPSPI master and another board used as LPSPI slave.The file 'lpspi_interrupt_b2b_master.c' includes the LPSPI master code.This example does not use the transactional API in LPSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b/master">
<external path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b/master" type="xml">
<files mask="lpspi_interrupt_b2b_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_interrupt_b2b_slave" name="lpspi_interrupt_b2b_slave" brief="The lpspi_interrupt_b2b example shows how to use LPSPI driver in interrupt way:In this example , we need two boards , one board used as LPSPI master and another board used as LPSPI slave.The file 'dspi_interrupt_b2b_slave.c' includes the LPSPI slave code.This example does not use the transactional API in LPSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b/slave">
<external path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b/slave" type="xml">
<files mask="lpspi_interrupt_b2b_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_interrupt_b2b_transfer_master" name="lpspi_interrupt_b2b_transfer_master" brief="The lpspi_interrupt_b2b_transfer example shows how to use LPSPI driver in interrupt way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'lpspi_interrupt_b2b_transfer_master.c' includes the LPSPI master code.This example uses the transactional API in LPSPI driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b_transfer/master">
<external path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b_transfer/master" type="xml">
<files mask="lpspi_interrupt_b2b_transfer_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_interrupt_b2b_transfer_slave" name="lpspi_interrupt_b2b_transfer_slave" brief="The lpspi_interrupt_b2b_transfer example shows how to use LPSPI driver in interrupt way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'lpspi_interrupt_b2b_transfer_slave.c' includes the LPSPI slave code.This example uses the transactional API in LPSPI driver.1. LPSPI master send/received data to/from LPSPI slave in interrupt . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b_transfer/slave">
<external path="boards/frdmke16z/driver_examples/lpspi/interrupt_b2b_transfer/slave" type="xml">
<files mask="lpspi_interrupt_b2b_transfer_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_polling_b2b_transfer_master" name="lpspi_polling_b2b_transfer_master" brief="The lpspi_polling_b2b_transfer example shows how to use LPSPI driver in polling way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'lpspi_polling_b2b_transfer_master.c' includes the LPSPI master code.1. LPSPI master send/received data to/from LPSPI slave in polling . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/polling_b2b_transfer/master">
<external path="boards/frdmke16z/driver_examples/lpspi/polling_b2b_transfer/master" type="xml">
<files mask="lpspi_polling_b2b_transfer_master_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpspi_polling_b2b_transfer_slave" name="lpspi_polling_b2b_transfer_slave" brief="The lpspi_polling_b2b_transfer example shows how to use LPSPI driver in polling way:In this example , we need two boards, one board used as LPSPI master and another board used as LPSPI slave.The file 'lpspi_polling_b2b_transfer_slave.c' includes the LPSPI slave code.1. LPSPI master send/received data to/from LPSPI slave in polling . (LPSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpspi" path="boards/frdmke16z/driver_examples/lpspi/polling_b2b_transfer/slave">
<external path="boards/frdmke16z/driver_examples/lpspi/polling_b2b_transfer/slave" type="xml">
<files mask="lpspi_polling_b2b_transfer_slave_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/lptmr" path="boards/frdmke16z/driver_examples/lptmr">
<external path="boards/frdmke16z/driver_examples/lptmr" type="xml">
<files mask="lptmr_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpuart_9bit_interrupt_transfer" name="lpuart_9bit_interrupt_transfer" brief="The lpuart_9bit_interrupt_transfer example shows how to use lpuart driver in 9-bit mode in multi-slave system. Master can send data to slave with certain address specifically, and slave can only receive data when it is addressed. In this example, one lpuart instance is used with address configured. Its TX and RX pins are connected together. First it sends a piece of data out, then addresses itself, after that sends the other piece of data. Only data sent after the address can be received by itself." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/9bit_interrupt_transfer">
<external path="boards/frdmke16z/driver_examples/lpuart/9bit_interrupt_transfer" type="xml">
<files mask="lpuart_9bit_interrupt_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/interrupt">
<external path="boards/frdmke16z/driver_examples/lpuart/interrupt" type="xml">
<files mask="lpuart_interrupt_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/interrupt_rb_transfer">
<external path="boards/frdmke16z/driver_examples/lpuart/interrupt_rb_transfer" type="xml">
<files mask="lpuart_interrupt_rb_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmke16z/driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="lpuart_interrupt_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpuart_interrupt_transfer_seven_bits" name="lpuart_interrupt_transfer_seven_bits" brief="The lpuart_interrupt_transfer_seven_bits Example project is to demonstrate usage of the KSDK lpuart driver with seven data bits feature enabled.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.NOTE: Please set com port format to "7 data bits without parity bit" in PC's com port tool" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/interrupt_transfer_seven_bits">
<external path="boards/frdmke16z/driver_examples/lpuart/interrupt_transfer_seven_bits" type="xml">
<files mask="lpuart_interrupt_transfer_seven_bits_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/polling">
<external path="boards/frdmke16z/driver_examples/lpuart/polling" type="xml">
<files mask="lpuart_polling_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_lpuart_polling_seven_bits" name="lpuart_polling_seven_bits" brief="The lpuart_polling_seven_bits Example project is to demonstrate usage of the KSDK lpuart driver with seven data bits feature enabled.In the example, you can send characters to the console back and they will be printed out onto console instantly.NOTE: Please set com port format to "7 data bits without parity bit" in PC's com port tool" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmke16z/driver_examples/lpuart/polling_seven_bits">
<external path="boards/frdmke16z/driver_examples/lpuart/polling_seven_bits" type="xml">
<files mask="lpuart_polling_seven_bits_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_mmdvsq" name="mmdvsq" brief="The MMDVSQ Example project is a demonstration program that uses the KSDK software to Calculation square root and QuotientMMDVSQ Peripheral Driver ExampleStart MMDVSQ ExampleCalculation square root, please enter radicandSquare root of 9 is 3Calculation division to get remainder and quotientEnter dividend and divisorRemainder of 10 and 5 is 0Quotient of 10 and 5 is 2" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mmdvsq" path="boards/frdmke16z/driver_examples/mmdvsq">
<external path="boards/frdmke16z/driver_examples/mmdvsq" type="xml">
<files mask="mmdvsq_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_mscan_interrupt_transfer" name="mscan_interrupt_transfer" brief="The mscan_interrupt_transfer example shows how to use MSCAN driver in none-blocking interrupt way. In this example, 2 boards are connected through CAN bus. Endpoint A(board A) send a CAN Message to Endpoint B(board B) when user press space key in terminal. Endpoint B receive the message, print the message content to terminal and echo back the message. Endpoint A will increase the received message and waiting for the next transmission of the user initiated." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mscan/interrupt_transfer" path="boards/frdmke16z/driver_examples/mscan/interrupt_transfer">
<external path="boards/frdmke16z/driver_examples/mscan/interrupt_transfer" type="xml">
<files mask="mscan_interrupt_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_mscan_loopback" name="mscan_loopback" brief="The mscan_loopback_functional example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will configure one MSCAN Message Txbuffer and Rx buffer with same ID.After that, the example will send a CAN Message from the Tx Buffer to the Rx Bufferthrouth internal loopback interconnect and print out the Message payload to terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mscan" path="boards/frdmke16z/driver_examples/mscan/loopback">
<external path="boards/frdmke16z/driver_examples/mscan/loopback" type="xml">
<files mask="mscan_loopback_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_mscan_loopback_transfer" name="mscan_loopback_transfer" brief="The mscan_loopback example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one MSCAN MessageBuffer to Rx Message Buffer and the other MSCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrough internal loopback interconnect and print out the Message payload to terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mscan/loopback_transfer" path="boards/frdmke16z/driver_examples/mscan/loopback_transfer">
<external path="boards/frdmke16z/driver_examples/mscan/loopback_transfer" type="xml">
<files mask="mscan_loopback_transfer_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_pdb_adc12_trigger" name="pdb_adc12_trigger" brief="The pdb_adc12_trigger example shows how to use the PDB to generate a ADC trigger.Based on the basic counter, to use the ADC trigger, just to enable the ADC trigger's "milestone" and set the user-defined value for it.After the PDB counter is triggered to start, when the counter pass the "milestone", the ADC's Pre-Trigger would be generated and sentto the ADC12 module.In this example, the ADC12 is configured with hardware trigger and conversion complete interrupt enabled.Once it gets the trigger from the PDB, the conversion goes, then the ISR would be executed." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/pdb" path="boards/frdmke16z/driver_examples/pdb/adc12_trigger">
<external path="boards/frdmke16z/driver_examples/pdb/adc12_trigger" type="xml">
<files mask="pdb_adc12_trigger_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_pdb_delay_interrupt" name="pdb_delay_interrupt" brief="The pdb_delay_interrupt example show how to use the PDB as a general programmable interrupt timer.The PDB is triggered by software, and other external triggers are generated from PDB in this project,so that user can see just a general counter is working with interrupt." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/pdb" path="boards/frdmke16z/driver_examples/pdb/delay_interrupt">
<external path="boards/frdmke16z/driver_examples/pdb/delay_interrupt" type="xml">
<files mask="pdb_delay_interrupt_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_pflash" name="pflash" brief="The pflash example shows how to use flash driver to operate program flash:" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmke16z/driver_examples/flash/pflash">
<external path="boards/frdmke16z/driver_examples/flash/pflash" type="xml">
<files mask="pflash_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/power_manager">
<external path="boards/frdmke16z/demo_apps/power_manager" type="xml">
<files mask="power_manager_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/power_mode_switch">
<external path="boards/frdmke16z/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_pwt_example" name="pwt_example" brief="The PWT project is a simple demonstration program of the SDK PWT driver. It sets up the PWThardware block to edge detection, capture control part and detects measurement trigger edges andcontrols when and which pulse width register(s) will be updated. Once the input signal is received,this example will print overflow flag status, positive pulse width and negative pulse width." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/pwt" path="boards/frdmke16z/driver_examples/pwt">
<external path="boards/frdmke16z/driver_examples/pwt" type="xml">
<files mask="pwt_example_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="driver_examples/rtc" path="boards/frdmke16z/driver_examples/rtc">
<external path="boards/frdmke16z/driver_examples/rtc" type="xml">
<files mask="rtc_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_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" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/rtc_func">
<external path="boards/frdmke16z/demo_apps/rtc_func" type="xml">
<files mask="rtc_func_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_scg" name="scg" brief="The SCG example shows how to use SCG driver: 1. How to setup the SCG clock source. 2. How to use SCG clock while power mode switch. 3. How to use SCG APIs to get clock frequency.This example prints the clock frequency through the terminal using the SDK driver." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/scg" path="boards/frdmke16z/driver_examples/scg">
<external path="boards/frdmke16z/driver_examples/scg" type="xml">
<files mask="scg_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_shell" name="shell" brief="The Shell Demo application demonstrates to control Leds by commands." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/shell">
<external path="boards/frdmke16z/demo_apps/shell" type="xml">
<files mask="shell_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_touch_sensing" name="touch_sensing" brief="This example demonstrates the NXP Touch sensing library usage." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmke16z/demo_apps/touch_sensing">
<external path="boards/frdmke16z/demo_apps/touch_sensing" type="xml">
<files mask="touch_sensing_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_trgmux_clone_pwm" name="trgmux_clone_pwm" brief="The TRGMUX project is a simple demonstration program of the SDK TRGMUX driver. It generatesa 10KHz PWM by LPIT0 CH0, and clone by TRGMUX to output this PWM to eight TRGMUX_OUTx pins." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/trgmux" path="boards/frdmke16z/driver_examples/trgmux/clone_pwm">
<external path="boards/frdmke16z/driver_examples/trgmux/clone_pwm" type="xml">
<files mask="trgmux_clone_pwm_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_tsi_v5_mutual_cap" name="tsi_v5_mutual_cap" brief="The tsi_v5_mutual_cap example shows how to use TSI_V5 driver in mutual-cap mode: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" compiler="compiler_gcc" category="driver_examples/tsi_v5" path="boards/frdmke16z/driver_examples/tsi_v5/mutual_cap">
<external path="boards/frdmke16z/driver_examples/tsi_v5/mutual_cap" type="xml">
<files mask="tsi_v5_mutual_cap_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_tsi_v5_mutualmode" name="tsi_v5_mutualmode" brief="The tsi_v5_mutualmode demo shows how to use TSI_V5 driver in mutual-cap mode:In this example , available electrodes on FRDM-TOUCH board are used to show how to realize touch key.1. Firstly, get the non-touch calibration results as baseline electrode counter;2. Then, start the periodical Software-Trigger scan using polling method to detect finger touch;3. Wait for the electrodes touched and deal with the event." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps/tsi_v5" path="boards/frdmke16z/demo_apps/tsi_v5/tsi_v5_mutualmode">
<external path="boards/frdmke16z/demo_apps/tsi_v5/tsi_v5_mutualmode" type="xml">
<files mask="tsi_v5_mutualmode_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_tsi_v5_self_cap" name="tsi_v5_self_cap" brief="The tsi_v5_self_cap example shows how to use TSI_V5 driver in self-cap mode: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" compiler="compiler_gcc" category="driver_examples/tsi_v5" path="boards/frdmke16z/driver_examples/tsi_v5/self_cap">
<external path="boards/frdmke16z/driver_examples/tsi_v5/self_cap" type="xml">
<files mask="tsi_v5_self_cap_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_tsi_v5_selfmode" name="tsi_v5_selfmode" brief="The tsi_v5_selfmode demo shows how to use TSI_V5 driver in self-cap mode:In this example , available electrodes on board is used to show how to realize touch key.1. Firstly, get the non-touch calibration results as baseline electrode counter;2. Then, start the periodical Software-Trigger scan using polling method to detect finger touch;3. Wait for the electrodes touched and deal with the event." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps/tsi_v5" path="boards/frdmke16z/demo_apps/tsi_v5/tsi_v5_selfmode">
<external path="boards/frdmke16z/demo_apps/tsi_v5/tsi_v5_selfmode" type="xml">
<files mask="tsi_v5_selfmode_v3_10.xml"/>
</external>
</example>
<example id="frdmke16z_wdog32" name="wdog32" brief="The WDOG32 Example project is to demonstrate usage of the KSDK wdog32 driver.In this example, fast testing is first implemented to test the wdog32.After this, refreshing the watchdog in None-window mode and window mode is executed.Note wdog32 is disabled in SystemInit function which means wdog32 is disabledafter chip emerges from reset." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/wdog32" path="boards/frdmke16z/driver_examples/wdog32">
<external path="boards/frdmke16z/driver_examples/wdog32" type="xml">
<files mask="wdog32_v3_10.xml"/>
</external>
</example>
</examples>
</board>
</boards>
<devices>
<device id="MKE16Z64xxx4" name="MKE16Z4" version="1.0.0" full_name="MKE16Z64xxx4" family="KE1x" platform="Kinetis">
<description>KE1xZ: Kinetis KE1xZ-48 MHz, 5V main stream CM0+ MCU with NXP Touch(TSI) and CAN control</description>
<metadataSet>
<metadata key="vendor" value="NXP"/>
</metadataSet>
<core id="core0_MKE16Z64xxx4" name="core0" fpu="false" type="cm0plus"/>
<memory>
<memoryBlock id="PROGRAM_FLASH_MKE16Z64xxx4" name="PROGRAM_FLASH" addr="00000000" size="00010000" type="Flash" access="RO"/>
<memoryBlock id="SRAM_MKE16Z64xxx4" name="SRAM" addr="1ffff800" size="00002000" type="RAM" access="RW"/>
</memory>
<total_memory flash_size_kb="64" ram_size_kb="8"/>
<package id="MKE16Z64VLF4" name="MKE16Z64VLF4"/>
<package id="MKE16Z64VLD4" name="MKE16Z64VLD4"/>
<evaluation_boards>
<evaluation_board name="frdmke16z"/>
</evaluation_boards>
<debug_configurations>
<debug_configuration id_refs="com.crt.advproject.config.exe.debug com.crt.advproject.config.exe.release">
<params>
<params id="internal.wiretype.release.MKE16Z64xxx4" name="internal.wiretype" value="SWD"/>
<params id="internal.has_swo.release.MKE16Z64xxx4" name="internal.has_swo" value="false"/>
<params id="internal.connect.script.debug.mcuxpresso.MKE16Z64xxx4" name="internal.connect.script" value="kinetisconnect.scp"/>
</params>
<drivers>
<driver id_refs="PROGRAM_FLASH_MKE16Z64xxx4">
<driverBinary path="devices/MKE16Z4/mcuxpresso" type="binary">
<files mask="FTFA_1K.cfx"/>
</driverBinary>
</driver>
</drivers>
</debug_configuration>
</debug_configurations>
<linkerSettings nature="c_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="flash_security_address" value="0x400"/>
<linker property="mtb_supported" value="true"/>
</linkerSettings>
<linkerSettings nature="cpp_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="flash_security_address" value="0x400"/>
<linker property="mtb_supported" value="true"/>
</linkerSettings>
</device>
<device id="MKE14Z64xxx4" name="MKE14Z4" version="1.0.0" full_name="MKE14Z64xxx4" family="KE1x" platform="Kinetis">
<description>KE1xZ: Kinetis KE1xZ-48 MHz, 5V main stream CM0+ MCU with NXP Touch(TSI) and CAN control</description>
<metadataSet>
<metadata key="vendor" value="NXP"/>
</metadataSet>
<core id="core0_MKE14Z64xxx4" name="core0" fpu="false" type="cm0plus"/>
<memory>
<memoryBlock id="PROGRAM_FLASH_MKE14Z64xxx4" name="PROGRAM_FLASH" addr="00000000" size="00010000" type="Flash" access="RO"/>
<memoryBlock id="SRAM_MKE14Z64xxx4" name="SRAM" addr="1ffff800" size="00002000" type="RAM" access="RW"/>
</memory>
<total_memory flash_size_kb="64" ram_size_kb="8"/>
<package id="MKE14Z64VLF4" name="MKE14Z64VLF4"/>
<package id="MKE14Z64VLD4" name="MKE14Z64VLD4"/>
<package id="MKE14Z64VFP4" name="MKE14Z64VFP4"/>
<evaluation_boards>
<evaluation_board name="frdmke16z"/>
</evaluation_boards>
<debug_configurations>
<debug_configuration id_refs="com.crt.advproject.config.exe.debug com.crt.advproject.config.exe.release">
<params>
<params id="internal.wiretype.release.MKE14Z64xxx4" name="internal.wiretype" value="SWD"/>
<params id="internal.has_swo.release.MKE14Z64xxx4" name="internal.has_swo" value="false"/>
<params id="internal.connect.script.debug.mcuxpresso.MKE14Z64xxx4" name="internal.connect.script" value="kinetisconnect.scp"/>
</params>
<drivers>
<driver id_refs="PROGRAM_FLASH_MKE14Z64xxx4">
<driverBinary path="devices/MKE14Z4/mcuxpresso" type="binary">
<files mask="FTFA_1K.cfx"/>
</driverBinary>
</driver>
</drivers>
</debug_configuration>
</debug_configurations>
<linkerSettings nature="c_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="flash_security_address" value="0x400"/>
<linker property="mtb_supported" value="true"/>
</linkerSettings>
<linkerSettings nature="cpp_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="flash_security_address" value="0x400"/>
<linker property="mtb_supported" value="true"/>
</linkerSettings>
</device>
</devices>
<components>
<component id="project_template.frdmke16z.MKE16Z4" name="frdmke16z" brief="Board_project_template frdmke16z" version="1.0.0" full_name="Board_project_template frdmke16z" devices="MKE16Z64xxx4" device_cores="core0_MKE16Z64xxx4" category="Board Support/SDK Project Template" user_visible="true" type="project_template" package_base_path="boards/frdmke16z/project_template" project_base_path="board">
<dependencies>
<all>
<component_dependency value="platform.drivers.lpuart.MKE16Z4"/>
<component_dependency value="component.lpuart_adapter.MKE16Z4"/>
<component_dependency value="platform.drivers.port.MKE16Z4"/>
<component_dependency value="platform.drivers.common.MKE16Z4"/>
<component_dependency value="platform.drivers.gpio.MKE16Z4"/>
<component_dependency value="platform.drivers.smc.MKE16Z4"/>
<component_dependency value="device.MKE16Z4_startup.MKE16Z4"/>
<component_dependency value="platform.drivers.lpi2c.MKE16Z4"/>
<any_of>
<all>
<component_dependency value="utility.debug_console.MKE16Z4"/>
<component_dependency value="platform.utilities.assert.MKE16Z4"/>
<component_dependency value="component.serial_manager.MKE16Z4"/>
</all>
<all>
<component_dependency value="utility.debug_console_lite.MKE16Z4"/>
<component_dependency value="platform.utilities.assert_lite.MKE16Z4"/>
</all>
</any_of>
</all>
</dependencies>
<source relative_path="./" type="c_include">
<files mask="board.h"/>
<files mask="clock_config.h"/>
<files mask="pin_mux.h"/>
<files mask="peripherals.h"/>
</source>
<source relative_path="./" type="src">
<files mask="board.c"/>
<files mask="clock_config.c"/>
<files mask="pin_mux.c"/>
<files mask="peripherals.c"/>
</source>
<include_paths>
<include_path relative_path="./" type="c_include"/>
<include_path relative_path="./" type="c_include"/>
</include_paths>
</component>
<component id="CMSIS_DSP_Include.MKE16Z4" name="CMSIS_DSP_Library_Header" brief="CMSIS-DSP Library Header" version="1.9.0" full_name="CMSIS DSP Library Header" devices="MKE16Z64xxx4" user_visible="true" type="CMSIS_driver" package_base_path="CMSIS/DSP" project_base_path="CMSIS/DSP">
<source exclude="true" relative_path="./" type="other">
<files mask="README.md" hidden="true"/>
</source>
<source relative_path="Include" type="c_include">
<files mask="arm_common_tables.h"/>
<files mask="arm_const_structs.h"/>
<files mask="arm_math.h"/>
<files mask="arm_common_tables_f16.h"/>
<files mask="arm_const_structs_f16.h"/>
<files mask="arm_helium_utils.h"/>
<files mask="arm_math_f16.h"/>
<files mask="arm_math_memory.h"/>
<files mask="arm_math_types.h"/>
<files mask="arm_math_types_f16.h"/>
<files mask="arm_mve_tables.h"/>
<files mask="arm_mve_tables_f16.h"/>
<files mask="arm_vec_math.h"/>
<files mask="arm_vec_math_f16.h"/>
</source>
<source relative_path="Include/dsp" type="c_include">
<files mask="basic_math_functions.h"/>
<files mask="basic_math_functions_f16.h"/>
<files mask="bayes_functions.h"/>
<files mask="bayes_functions_f16.h"/>
<files mask="complex_math_functions.h"/>
<files mask="complex_math_functions_f16.h"/>
<files mask="controller_functions.h"/>
<files mask="controller_functions_f16.h"/>
<files mask="distance_functions.h"/>
<files mask="distance_functions_f16.h"/>
<files mask="fast_math_functions.h"/>
<files mask="fast_math_functions_f16.h"/>
<files mask="filtering_functions.h"/>
<files mask="filtering_functions_f16.h"/>
<files mask="interpolation_functions.h"/>
<files mask="interpolation_functions_f16.h"/>
<files mask="matrix_functions.h"/>
<files mask="matrix_functions_f16.h"/>
<files mask="none.h"/>
<files mask="quaternion_math_functions.h"/>
<files mask="statistics_functions.h"/>
<files mask="statistics_functions_f16.h"/>
<files mask="support_functions.h"/>
<files mask="support_functions_f16.h"/>
<files mask="svm_defines.h"/>
<files mask="svm_functions.h"/>
<files mask="svm_functions_f16.h"/>
<files mask="transform_functions.h"/>
<files mask="transform_functions_f16.h"/>
<files mask="utils.h"/>
</source>
<source relative_path="PrivateInclude" type="c_include">
<files mask="arm_sorting.h"/>
<files mask="arm_vec_fft.h"/>
<files mask="arm_vec_filtering.h"/>
</source>
<include_paths>
<include_path relative_path="Include" type="c_include"/>
<include_path relative_path="PrivateInclude" type="c_include"/>
</include_paths>
</component>
<component id="CMSIS_DSP_Source.MKE16Z4" name="CMSIS_DSP_Library_Source" brief="CMSIS-DSP Library" version="1.9.0" full_name="CMSIS DSP Library Source" devices="MKE16Z64xxx4" user_visible="true" type="CMSIS_driver" package_base_path="CMSIS/DSP" project_base_path="CMSIS/DSP">
<source exclude="true" relative_path="./" type="other">
<files mask="README.md" hidden="true"/>
</source>
<source relative_path="Include" type="c_include">
<files mask="arm_common_tables.h"/>
<files mask="arm_const_structs.h"/>
<files mask="arm_math.h"/>
<files mask="arm_common_tables_f16.h"/>
<files mask="arm_const_structs_f16.h"/>
<files mask="arm_helium_utils.h"/>
<files mask="arm_math_f16.h"/>
<files mask="arm_math_memory.h"/>
<files mask="arm_math_types.h"/>
<files mask="arm_math_types_f16.h"/>
<files mask="arm_mve_tables.h"/>
<files mask="arm_mve_tables_f16.h"/>
<files mask="arm_vec_math.h"/>
<files mask="arm_vec_math_f16.h"/>
</source>
<source relative_path="Include/dsp" type="c_include">
<files mask="basic_math_functions.h"/>
<files mask="basic_math_functions_f16.h"/>
<files mask="bayes_functions.h"/>
<files mask="bayes_functions_f16.h"/>
<files mask="complex_math_functions.h"/>
<files mask="complex_math_functions_f16.h"/>
<files mask="controller_functions.h"/>
<files mask="controller_functions_f16.h"/>
<files mask="distance_functions.h"/>
<files mask="distance_functions_f16.h"/>
<files mask="fast_math_functions.h"/>
<files mask="fast_math_functions_f16.h"/>
<files mask="filtering_functions.h"/>
<files mask="filtering_functions_f16.h"/>
<files mask="interpolation_functions.h"/>
<files mask="interpolation_functions_f16.h"/>
<files mask="matrix_functions.h"/>
<files mask="matrix_functions_f16.h"/>
<files mask="none.h"/>
<files mask="quaternion_math_functions.h"/>
<files mask="statistics_functions.h"/>
<files mask="statistics_functions_f16.h"/>
<files mask="support_functions.h"/>
<files mask="support_functions_f16.h"/>
<files mask="svm_defines.h"/>
<files mask="svm_functions.h"/>
<files mask="svm_functions_f16.h"/>
<files mask="transform_functions.h"/>
<files mask="transform_functions_f16.h"/>
<files mask="utils.h"/>
</source>
<source relative_path="PrivateInclude" type="c_include">
<files mask="arm_sorting.h"/>
<files mask="arm_vec_fft.h"/>
<files mask="arm_vec_filtering.h"/>
</source>
<source relative_path="Source/BasicMathFunctions" type="src">
<files mask="BasicMathFunctions.c"/>
<files mask="BasicMathFunctionsF16.c"/>
</source>
<source exclude="true" relative_path="Source/BasicMathFunctions" type="src">
<files mask="arm_abs_f32.c" hidden="true"/>
<files mask="arm_abs_q15.c" hidden="true"/>
<files mask="arm_abs_q31.c" hidden="true"/>
<files mask="arm_abs_q7.c" hidden="true"/>
<files mask="arm_add_f32.c" hidden="true"/>
<files mask="arm_add_q15.c" hidden="true"/>
<files mask="arm_add_q31.c" hidden="true"/>
<files mask="arm_add_q7.c" hidden="true"/>
<files mask="arm_and_u16.c" hidden="true"/>
<files mask="arm_and_u32.c" hidden="true"/>
<files mask="arm_and_u8.c" hidden="true"/>
<files mask="arm_clip_f32.c" hidden="true"/>
<files mask="arm_clip_q15.c" hidden="true"/>
<files mask="arm_clip_q31.c" hidden="true"/>
<files mask="arm_clip_q7.c" hidden="true"/>
<files mask="arm_dot_prod_f32.c" hidden="true"/>
<files mask="arm_dot_prod_q15.c" hidden="true"/>
<files mask="arm_dot_prod_q31.c" hidden="true"/>
<files mask="arm_dot_prod_q7.c" hidden="true"/>
<files mask="arm_mult_f32.c" hidden="true"/>
<files mask="arm_mult_q15.c" hidden="true"/>
<files mask="arm_mult_q31.c" hidden="true"/>
<files mask="arm_mult_q7.c" hidden="true"/>
<files mask="arm_negate_f32.c" hidden="true"/>
<files mask="arm_negate_q15.c" hidden="true"/>
<files mask="arm_negate_q31.c" hidden="true"/>
<files mask="arm_negate_q7.c" hidden="true"/>
<files mask="arm_not_u16.c" hidden="true"/>
<files mask="arm_not_u32.c" hidden="true"/>
<files mask="arm_not_u8.c" hidden="true"/>
<files mask="arm_offset_f32.c" hidden="true"/>
<files mask="arm_offset_q15.c" hidden="true"/>
<files mask="arm_offset_q31.c" hidden="true"/>
<files mask="arm_offset_q7.c" hidden="true"/>
<files mask="arm_or_u16.c" hidden="true"/>
<files mask="arm_or_u32.c" hidden="true"/>
<files mask="arm_or_u8.c" hidden="true"/>
<files mask="arm_scale_f32.c" hidden="true"/>
<files mask="arm_scale_q15.c" hidden="true"/>
<files mask="arm_scale_q31.c" hidden="true"/>
<files mask="arm_scale_q7.c" hidden="true"/>
<files mask="arm_shift_q15.c" hidden="true"/>
<files mask="arm_shift_q31.c" hidden="true"/>
<files mask="arm_shift_q7.c" hidden="true"/>
<files mask="arm_sub_f32.c" hidden="true"/>
<files mask="arm_sub_q15.c" hidden="true"/>
<files mask="arm_sub_q31.c" hidden="true"/>
<files mask="arm_sub_q7.c" hidden="true"/>
<files mask="arm_xor_u16.c" hidden="true"/>
<files mask="arm_xor_u32.c" hidden="true"/>
<files mask="arm_xor_u8.c" hidden="true"/>
<files mask="arm_abs_f16.c" hidden="true"/>
<files mask="arm_add_f16.c" hidden="true"/>
<files mask="arm_clip_f16.c" hidden="true"/>
<files mask="arm_dot_prod_f16.c" hidden="true"/>
<files mask="arm_mult_f16.c" hidden="true"/>
<files mask="arm_negate_f16.c" hidden="true"/>
<files mask="arm_offset_f16.c" hidden="true"/>
<files mask="arm_scale_f16.c" hidden="true"/>
<files mask="arm_sub_f16.c" hidden="true"/>
</source>
<source relative_path="Source/BayesFunctions" type="src">
<files mask="BayesFunctions.c"/>
<files mask="BayesFunctionsF16.c"/>
</source>
<source exclude="true" relative_path="Source/BayesFunctions" type="src">
<files mask="arm_gaussian_naive_bayes_predict_f32.c" hidden="true"/>
<files mask="arm_gaussian_naive_bayes_predict_f16.c" hidden="true"/>
</source>
<source relative_path="Source/CommonTables" type="src">
<files mask="CommonTables.c"/>
<files mask="CommonTablesF16.c"/>
</source>
<source exclude="true" relative_path="Source/CommonTables" type="src">
<files mask="arm_common_tables.c" hidden="true"/>
<files mask="arm_const_structs.c" hidden="true"/>
<files mask="arm_mve_tables.c" hidden="true"/>
<files mask="arm_common_tables_f16.c" hidden="true"/>
<files mask="arm_const_structs_f16.c" hidden="true"/>
<files mask="arm_mve_tables_f16.c" hidden="true"/>
</source>
<source relative_path="Source/ComplexMathFunctions" type="src">
<files mask="ComplexMathFunctions.c"/>
<files mask="ComplexMathFunctionsF16.c"/>
</source>
<source exclude="true" relative_path="Source/ComplexMathFunctions" type="src">
<files mask="arm_cmplx_conj_f32.c" hidden="true"/>
<files mask="arm_cmplx_conj_q15.c" hidden="true"/>
<files mask="arm_cmplx_conj_q31.c" hidden="true"/>
<files mask="arm_cmplx_dot_prod_f32.c" hidden="true"/>
<files mask="arm_cmplx_dot_prod_q15.c" hidden="true"/>
<files mask="arm_cmplx_dot_prod_q31.c" hidden="true"/>
<files mask="arm_cmplx_mag_f32.c" hidden="true"/>
<files mask="arm_cmplx_mag_q15.c" hidden="true"/>
<files mask="arm_cmplx_mag_q31.c" hidden="true"/>
<files mask="arm_cmplx_mag_squared_f32.c" hidden="true"/>
<files mask="arm_cmplx_mag_squared_q15.c" hidden="true"/>
<files mask="arm_cmplx_mag_squared_q31.c" hidden="true"/>
<files mask="arm_cmplx_mult_cmplx_f32.c" hidden="true"/>
<files mask="arm_cmplx_mult_cmplx_q15.c" hidden="true"/>
<files mask="arm_cmplx_mult_cmplx_q31.c" hidden="true"/>
<files mask="arm_cmplx_mult_real_f32.c" hidden="true"/>
<files mask="arm_cmplx_mult_real_q15.c" hidden="true"/>
<files mask="arm_cmplx_mult_real_q31.c" hidden="true"/>
<files mask="arm_cmplx_conj_f16.c" hidden="true"/>
<files mask="arm_cmplx_dot_prod_f16.c" hidden="true"/>
<files mask="arm_cmplx_mag_f16.c" hidden="true"/>
<files mask="arm_cmplx_mag_squared_f16.c" hidden="true"/>
<files mask="arm_cmplx_mult_cmplx_f16.c" hidden="true"/>
<files mask="arm_cmplx_mult_real_f16.c" hidden="true"/>
</source>
<source relative_path="Source/ControllerFunctions" type="src">
<files mask="ControllerFunctions.c"/>
</source>
<source exclude="true" relative_path="Source/ControllerFunctions" type="src">
<files mask="arm_pid_init_f32.c" hidden="true"/>
<files mask="arm_pid_init_q15.c" hidden="true"/>
<files mask="arm_pid_init_q31.c" hidden="true"/>
<files mask="arm_pid_reset_f32.c" hidden="true"/>
<files mask="arm_pid_reset_q15.c" hidden="true"/>
<files mask="arm_pid_reset_q31.c" hidden="true"/>
<files mask="arm_sin_cos_f32.c" hidden="true"/>
<files mask="arm_sin_cos_q31.c" hidden="true"/>
</source>
<source relative_path="Source/DistanceFunctions" type="src">
<files mask="DistanceFunctions.c"/>
<files mask="DistanceFunctionsF16.c"/>
</source>
<source relative_path="Source/DistanceFunctions" type="c_include">
<files mask="arm_boolean_distance_template.h"/>
</source>
<source exclude="true" relative_path="Source/DistanceFunctions" type="src">
<files mask="arm_boolean_distance.c" hidden="true"/>
<files mask="arm_braycurtis_distance_f32.c" hidden="true"/>
<files mask="arm_canberra_distance_f32.c" hidden="true"/>
<files mask="arm_chebyshev_distance_f32.c" hidden="true"/>
<files mask="arm_cityblock_distance_f32.c" hidden="true"/>
<files mask="arm_correlation_distance_f32.c" hidden="true"/>
<files mask="arm_cosine_distance_f32.c" hidden="true"/>
<files mask="arm_dice_distance.c" hidden="true"/>
<files mask="arm_euclidean_distance_f32.c" hidden="true"/>
<files mask="arm_hamming_distance.c" hidden="true"/>
<files mask="arm_jaccard_distance.c" hidden="true"/>
<files mask="arm_jensenshannon_distance_f32.c" hidden="true"/>
<files mask="arm_kulsinski_distance.c" hidden="true"/>
<files mask="arm_minkowski_distance_f32.c" hidden="true"/>
<files mask="arm_rogerstanimoto_distance.c" hidden="true"/>
<files mask="arm_russellrao_distance.c" hidden="true"/>
<files mask="arm_sokalmichener_distance.c" hidden="true"/>
<files mask="arm_sokalsneath_distance.c" hidden="true"/>
<files mask="arm_yule_distance.c" hidden="true"/>
<files mask="arm_braycurtis_distance_f16.c" hidden="true"/>
<files mask="arm_canberra_distance_f16.c" hidden="true"/>
<files mask="arm_chebyshev_distance_f16.c" hidden="true"/>
<files mask="arm_cityblock_distance_f16.c" hidden="true"/>
<files mask="arm_correlation_distance_f16.c" hidden="true"/>
<files mask="arm_cosine_distance_f16.c" hidden="true"/>
<files mask="arm_euclidean_distance_f16.c" hidden="true"/>
<files mask="arm_jensenshannon_distance_f16.c" hidden="true"/>
<files mask="arm_minkowski_distance_f16.c" hidden="true"/>
</source>
<source relative_path="Source/FastMathFunctions" type="src">
<files mask="FastMathFunctions.c"/>
<files mask="FastMathFunctionsF16.c"/>
</source>
<source exclude="true" relative_path="Source/FastMathFunctions" type="src">
<files mask="arm_cos_f32.c" hidden="true"/>
<files mask="arm_cos_q15.c" hidden="true"/>
<files mask="arm_cos_q31.c" hidden="true"/>
<files mask="arm_divide_q15.c" hidden="true"/>
<files mask="arm_sin_f32.c" hidden="true"/>
<files mask="arm_sin_q15.c" hidden="true"/>
<files mask="arm_sin_q31.c" hidden="true"/>
<files mask="arm_sqrt_q15.c" hidden="true"/>
<files mask="arm_sqrt_q31.c" hidden="true"/>
<files mask="arm_vexp_f32.c" hidden="true"/>
<files mask="arm_vlog_f32.c" hidden="true"/>
<files mask="arm_vexp_f16.c" hidden="true"/>
<files mask="arm_vinverse_f16.c" hidden="true"/>
<files mask="arm_vlog_f16.c" hidden="true"/>
</source>
<source relative_path="Source/FilteringFunctions" type="src">
<files mask="FilteringFunctions.c"/>
<files mask="FilteringFunctionsF16.c"/>
</source>
<source exclude="true" relative_path="Source/FilteringFunctions" type="src">
<files mask="arm_biquad_cascade_df1_32x64_init_q31.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_32x64_q31.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_f32.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_fast_q15.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_fast_q31.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_init_f32.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_init_q15.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_init_q31.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_q15.c" hidden="true"/>
<files mask="arm_biquad_cascade_df1_q31.c" hidden="true"/>
<files mask="arm_biquad_cascade_df2T_f32.c" hidden="true"/>
<files mask="arm_biquad_cascade_df2T_f64.c" hidden="true"/>
<files mask="arm_biquad_cascade_df2T_init_f32.c" hidden="true"/>
<files mask="arm_biquad_cascade_df2T_init_f64.c" hidden="true"/>
<files mask="arm_biquad_cascade_stereo_df2T_f32.c" hidden="true"/>