-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathMKL17Z32xxx4_manifest_v3_6.xml
3125 lines (3125 loc) · 224 KB
/
MKL17Z32xxx4_manifest_v3_6.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_MKL17Z32xxx4" name="MKL17Z32xxx4" brief="This is SDK version 2.8.0 manifest file. It describes the content of the MKL17Z32xxx4 and additional settings for tools that support SDK version 2.8.0" format_version="3.6" api_version="2.0.0" configuration="0207b9f10e4f3d495b4e78e7726624ac" xsi:schemaLocation="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd http://nxp.com/mcuxpresso/sdk/sdk_manifest_v3.6.xsd">
<!--Timestamp (UTC): 2020-08-12 12:16:48.247800-->
<!--This manifest is generated based on sdk repo commit: 5df5022c7426188357d0e69b4ff94b58f0d1b557-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<ksdk id="MCUXpresso280" name="MCUXpresso280" version="2.8.0" revision="366 2020-07-21"/>
<compilers>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
</compilers>
<toolchainSettings>
<toolchainSetting id="com.nxp.mcuxpresso" name="mcuxpresso" version="11.2.0" full_name="MCUXpresso IDE" compiler="compiler_gcc" toolchain="mcuxpresso">
<option id="gnu.cpp.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.c.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.cpp.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.cpp.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="gnu.c.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
</toolchainSetting>
</toolchainSettings>
<toolchains>
<toolchain id="armgcc" name="GCC_ARM_Embedded" version="9.2.1" full_name="GCC ARM Embedded" compiler="compiler_gcc" type="armgcc" vendor="GCC ARM Embedded" vendor_url="http://launchpad.net/gcc-arm-embedded"/>
<toolchain id="mcuxpresso" name="MCUXpresso_IDE" version="11.2.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="frdmkl27z" name="FRDM-KL27Z" href="https://www.nxp.com/pip/FRDM-KL27Z" version="1.0.0" package="MKL27Z64VLH4">
<description>Freedom Development Board for Kinetis KL17/KL27 (32-64 KB Flash) MCUs</description>
<image path="MIR/marketing_data/1.0/boards/images" type="image">
<files mask="22-FRDM-KL27Z.gif"/>
</image>
<examples>
<example id="frdmkl27z_adc16_continuous_dma" name="adc16_continuous_dma" brief="The ADC16 continuous DMA demo application demonstrates the usage of the ADC and DMA peripheral while in a continuous mode. TheADC16 is first set to continuous mode. In continuous convert configuration, only the initial rising-edge to launch continuous conversions isobserved, and until conversion is aborted, the ADC16 continues to do conversions on the same SCn register that initiated the conversion. DMA request will be asserted during an ADC16 conversion complete event noted when any of the SC1n[COCO] flags is asserted. DMA will transferADC16 results to memory and if users press any key, demo will average ADC16 results stored in memory and print average on the terminal. " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc16" path="boards/frdmkl27z/driver_examples/adc16/continuous_dma">
<external path="boards/frdmkl27z/driver_examples/adc16/continuous_dma" type="xml">
<files mask="adc16_continuous_dma.xml"/>
</external>
</example>
<example id="frdmkl27z_adc16_interrupt" name="adc16_interrupt" brief="The adc16_interrupt example shows how to use interrupt with ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. ADC interrupt would be asserted once the conversion is completed. In ADC ISR, the conversion completed flag would be cleared by reading the conversion result value. Also, the conversion result value is stored, and the ISR counter is increased. These information would be printed when the execution return to the main loop.The point is that the ADC16 interrupt configuration is set when configuring the ADC16's conversion channel. When in software trigger mode, the conversion would be launched by the operation of configuring channel, just like writing aconversion command. So if user wants to generate the interrupt every time the conversion is completed, the channel's configuration with enabling interrupt setting would be used for each conversion." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc16" path="boards/frdmkl27z/driver_examples/adc16/interrupt">
<external path="boards/frdmkl27z/driver_examples/adc16/interrupt" type="xml">
<files mask="adc16_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_adc16_low_power_async_dma" name="adc16_low_power_async_dma" brief="The ADC Low Power Async DMA demo application demonstrates the usage of the ADC and DMA peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 100 ms, low power timer trigger the ADC module convertvalue on ADC channel. After 16 times(1,6s) the DMA transfer finish interrupt wake up the CPU to process sampled data, print result touser and toggle LED." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/adc16_low_power_async_dma">
<external path="boards/frdmkl27z/demo_apps/adc16_low_power_async_dma" type="xml">
<files mask="adc16_low_power_async_dma.xml"/>
</external>
</example>
<example id="frdmkl27z_adc16_low_power_async_dma_peripheral" name="adc16_low_power_async_dma_peripheral" brief="The ADC Low Power Async DMA demo application demonstrates the usage of the ADC and DMA peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 100 ms, low power timer trigger the ADC module convertvalue on ADC channel. After 16 times(1,6s) the DMA transfer finish interrupt wake up the CPU to process sampled data, print result touser and toggle LED." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/adc16_low_power_async_dma_peripheral">
<external path="boards/frdmkl27z/demo_apps/adc16_low_power_async_dma_peripheral" type="xml">
<files mask="adc16_low_power_async_dma_peripheral.xml"/>
</external>
</example>
<example id="frdmkl27z_adc16_low_power_peripheral" name="adc16_low_power_peripheral" brief="The ADC Low Power demo application demonstrates the usage of the ADC peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 500 ms, an interrupt wakes up the ADC module andreads the current temperature of the microcontroller. While the temperature remains within boundaries, both LEDs are on.If the core temperature is higher or lower than average, the LEDs change state respectively. You can open the mex file with MCUXpresso Config Tool to do further configuration of pin, clock and peripheral." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/adc16_low_power_peripheral">
<external path="boards/frdmkl27z/demo_apps/adc16_low_power_peripheral" type="xml">
<files mask="adc16_low_power_peripheral.xml"/>
</external>
</example>
<example id="frdmkl27z_adc16_polling" name="adc16_polling" brief="The adc16_polling example shows the simplest way to use ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. The execution would check the conversion completed flag in loop until the flag is asserted, which means the conversion is completed. Then read the conversion result value and print it to debug console.Note, the default setting of initialization for the ADC converter is just an available configuration. User can changethe configuration structure's setting in application to fit the special requirement.The auto-calibration is not essential but strongly recommended. It can help to adjust the converter itself and improvethe ADC16's performance." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc16" path="boards/frdmkl27z/driver_examples/adc16/polling">
<external path="boards/frdmkl27z/driver_examples/adc16/polling" type="xml">
<files mask="adc16_polling.xml"/>
</external>
</example>
<example id="frdmkl27z_bubble_peripheral" name="bubble_peripheral" 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. You can open the mex file with MCUXpresso Config Tool to do further configuration of pin, clock and peripheral." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/bubble_peripheral">
<external path="boards/frdmkl27z/demo_apps/bubble_peripheral" type="xml">
<files mask="bubble_peripheral.xml"/>
</external>
</example>
<example id="frdmkl27z_cmp_interrupt" name="cmp_interrupt" brief="The CMP interrupt Example shows how to use interrupt with CMP driver.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user-defined channel's voltage crosses the internal DAC's value. The change ofcomparator's output would generate the falling and rising edge events with their interrupts enabled. When any CMP interrupt happens, the CMP's ISR would turn on the LED light if detecting the output's rising edge, or turn off it whendetecting the output's falling edge." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/cmp" path="boards/frdmkl27z/driver_examples/cmp/interrupt">
<external path="boards/frdmkl27z/driver_examples/cmp/interrupt" type="xml">
<files mask="cmp_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_cmp_polling" name="cmp_polling" brief="The CMP polling Example shows the simplest way to use CMP driver and help user with a quick start.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user's voltage crosses the internal DAC's value. The endless loop in main() functionwould detect the logic value of comparator's output, and change the LED. The LED would be turned on when the compareoutput is logic one, or turned off when zero." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/cmp" path="boards/frdmkl27z/driver_examples/cmp/polling">
<external path="boards/frdmkl27z/driver_examples/cmp/polling" type="xml">
<files mask="cmp_polling.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_i2c_dma_b2b_transfer_master" name="cmsis_i2c_dma_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_dma_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with DMA:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkl27z/cmsis_driver_examples/i2c/dma_b2b_transfer/master">
<external path="boards/frdmkl27z/cmsis_driver_examples/i2c/dma_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_dma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_i2c_dma_b2b_transfer_slave" name="cmsis_i2c_dma_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_dma_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with a DMA master:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkl27z/cmsis_driver_examples/i2c/dma_b2b_transfer/slave">
<external path="boards/frdmkl27z/cmsis_driver_examples/i2c/dma_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_dma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_i2c_int_b2b_transfer_master" name="cmsis_i2c_int_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The i2c_interrupt_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkl27z/cmsis_driver_examples/i2c/int_b2b_transfer/master">
<external path="boards/frdmkl27z/cmsis_driver_examples/i2c/int_b2b_transfer/master" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_i2c_int_b2b_transfer_slave" name="cmsis_i2c_int_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The i2c_interrupt_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkl27z/cmsis_driver_examples/i2c/int_b2b_transfer/slave">
<external path="boards/frdmkl27z/cmsis_driver_examples/i2c/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_i2c_int_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_i2c_read_accel_value_transfer" name="cmsis_i2c_read_accel_value_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_read_accel_value example shows how to use CMSIS I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkl27z/cmsis_driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmkl27z/cmsis_driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="cmsis_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_lpuart_dma_transfer" name="cmsis_lpuart_dma_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_edma_transfer example shows how to use uart cmsis driver with EDMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpuart" path="boards/frdmkl27z/cmsis_driver_examples/lpuart/dma_transfer">
<external path="boards/frdmkl27z/cmsis_driver_examples/lpuart/dma_transfer" type="xml">
<files mask="cmsis_lpuart_dma_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpuart" path="boards/frdmkl27z/cmsis_driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmkl27z/cmsis_driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="cmsis_lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_spi_dma_b2b_transfer_master" name="cmsis_spi_dma_b2b_transfer_master" brief="The spi_dma_b2b_transfer example shows how to use SPI CMSIS driver in dma way:In this example , we need two boards, one board used as SPI master and another board used as SPI slave.The file 'spi_dma_b2b_transfer_master.c' includes the SPI master code.1. SPI master send/received data to/from SPI slave in dma . " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/spi" path="boards/frdmkl27z/cmsis_driver_examples/spi/dma_b2b_transfer/master">
<external path="boards/frdmkl27z/cmsis_driver_examples/spi/dma_b2b_transfer/master" type="xml">
<files mask="cmsis_spi_dma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_spi_dma_b2b_transfer_slave" name="cmsis_spi_dma_b2b_transfer_slave" brief="The spi_dma_b2b_transfer example shows how to use SPI CMSIS driver in dma way:In this example , we need two boards, one board used as SPI master and another board used as SPI slave.The file 'spi_dma_b2b_transfer_slave.c' includes the SPI slave code.1. SPI master send/received data to/from SPI slave in dma . " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/spi" path="boards/frdmkl27z/cmsis_driver_examples/spi/dma_b2b_transfer/slave">
<external path="boards/frdmkl27z/cmsis_driver_examples/spi/dma_b2b_transfer/slave" type="xml">
<files mask="cmsis_spi_dma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_spi_interrupt_b2b_transfer_master" name="cmsis_spi_interrupt_b2b_transfer_master" brief="The spi_interrupt_b2b_transfer example shows how to use spi CMSIS driver in interrupt way:In this example , we need two boards, one board used as spi master and another board used as spi slave.The file 'spi_interrupt_b2b_transfer_master.c' includes the spi master code.This example uses the transactional API in spi driver.1. spi master send/received data to/from spi slave in interrupt . " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/spi" path="boards/frdmkl27z/cmsis_driver_examples/spi/interrupt_b2b_transfer/master">
<external path="boards/frdmkl27z/cmsis_driver_examples/spi/interrupt_b2b_transfer/master" type="xml">
<files mask="cmsis_spi_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_spi_interrupt_b2b_transfer_slave" name="cmsis_spi_interrupt_b2b_transfer_slave" brief="The spi_interrupt_b2b_transfer example shows how to use SPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as SPI master and another board used as SPI slave.The file 'spi_interrupt_b2b_transfer_slave.c' includes the SPI slave code.This example uses the transactional API in SPI driver.1. SPI master send/received data to/from SPI slave in interrupt . " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/spi" path="boards/frdmkl27z/cmsis_driver_examples/spi/interrupt_b2b_transfer/slave">
<external path="boards/frdmkl27z/cmsis_driver_examples/spi/interrupt_b2b_transfer/slave" type="xml">
<files mask="cmsis_spi_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_uart_dma_transfer" name="cmsis_uart_dma_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_edma_transfer example shows how to use uart cmsis driver with EDMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/uart" path="boards/frdmkl27z/cmsis_driver_examples/uart/dma_transfer">
<external path="boards/frdmkl27z/cmsis_driver_examples/uart/dma_transfer" type="xml">
<files mask="cmsis_uart_dma_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_cmsis_uart_interrupt_transfer" name="cmsis_uart_interrupt_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_interrupt_transfer example shows how to use uart cmsis driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/uart" path="boards/frdmkl27z/cmsis_driver_examples/uart/interrupt_transfer">
<external path="boards/frdmkl27z/cmsis_driver_examples/uart/interrupt_transfer" type="xml">
<files mask="cmsis_uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_cop" name="cop" brief="The COP Example project is to demonstrate usage of the KSDK cop driver.In this example, after 10 times of refreshing, a timeout reset is generated.Please notice that because COP control registers are write-once only, so the COP_Init function and the COP_Disable function can be called only once after reset.In SystemInit() function which is called in startup code, there is an operation to disable the watchdog if macro DISABLE_WDOG is defined as 0, and by default if the DISABLE_WDOG is not defined, the DISABLE_WDOG is defined as 1. So this example has a special project setting that defines the DISABLE_WDOG macro to 0 so the startup code will skip the disable COP WDOG operation." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/cop">
<external path="boards/frdmkl27z/driver_examples/cop" type="xml">
<files mask="cop.xml"/>
</external>
</example>
<example id="frdmkl27z_crc" name="crc" brief="The CRC Example project is a demonstration program that uses the KSDK software to generate checksumsfor an ASCII string. Several CRC protocols are implemented using the CRC driver API." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/crc">
<external path="boards/frdmkl27z/driver_examples/crc" type="xml">
<files mask="crc.xml"/>
</external>
</example>
<example id="frdmkl27z_dma_memory_to_memory" name="dma_memory_to_memory" brief="The DMA memory to memory example is a simple demonstration program that uses the SDK software.It executes one shot transfer from source buffer to destination buffer using the SDK DMA drivers.The purpose of this example is to show how to use the DMA and to provide a simple example fordebugging and further development." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/dma" path="boards/frdmkl27z/driver_examples/dma/memory_to_memory">
<external path="boards/frdmkl27z/driver_examples/dma/memory_to_memory" type="xml">
<files mask="dma_memory_to_memory.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_i2c_interrupt_i2c_transfer" name="flexio_i2c_interrupt_i2c_transfer" brief="The flexio_i2c_interrupt example shows how to use flexio i2c master driver in interrupt way:In this example, a flexio simulated i2c master connect to an I2C slave." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/i2c/interrupt_i2c_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/i2c/interrupt_i2c_transfer" type="xml">
<files mask="flexio_i2c_interrupt_i2c_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_i2c_read_accel_value_transfer" name="flexio_i2c_read_accel_value_transfer" brief="The flexio_i2c_read_accel_value example shows how to use FLEXIO I2C Master driver to communicate with an i2c device: 1. How to use the flexio i2c master driver to read a i2c device who_am_I register. 2. How to use the flexio i2c master driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/i2c/read_accel_value_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/i2c/read_accel_value_transfer" type="xml">
<files mask="flexio_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_pwm" name="flexio_pwm" brief="This demo describes how to use SDK drivers to implement the PWM feature by FLEXIO IP module. It outputs the PWM singal with fixed frequency defined by "DEMO_FLEXIO_FREQUENCY" in source code and dynamic duty from 99 to 1 to one of the FLEXIO pin." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/pwm">
<external path="boards/frdmkl27z/driver_examples/flexio/pwm" type="xml">
<files mask="flexio_pwm.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_spi_dma_spi_transfer_master" name="flexio_spi_dma_spi_transfer_master" brief="The flexio_spi_master_dma_spi_slave example shows how to use flexio spi master driver in dma way:In this example, a flexio simulated master connect to a spi slave ." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/spi/dma_spi_transfer/master">
<external path="boards/frdmkl27z/driver_examples/flexio/spi/dma_spi_transfer/master" type="xml">
<files mask="flexio_spi_dma_spi_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_spi_dma_spi_transfer_slave" name="flexio_spi_dma_spi_transfer_slave" brief="The flexio_spi_slave_dma_spi_master example shows how to use flexio spi slave driver in dma way:In this example, a flexio simulated slave connect to a spi master." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/spi/dma_spi_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/flexio/spi/dma_spi_transfer/slave" type="xml">
<files mask="flexio_spi_dma_spi_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_spi_int_spi_transfer_master" name="flexio_spi_int_spi_transfer_master" brief="The flexio_spi_master_interrupt_spi_slave example shows how to use flexio spi master driver in interrupt way:In this example, a flexio simulated master connect to a spi slave ." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/spi/int_spi_transfer/master">
<external path="boards/frdmkl27z/driver_examples/flexio/spi/int_spi_transfer/master" type="xml">
<files mask="flexio_spi_int_spi_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_spi_int_spi_transfer_slave" name="flexio_spi_int_spi_transfer_slave" brief="The flexio_spi_slave_interrupt_spi_master example shows how to use flexio spi slave driver in interrupt way:In this example, a flexio simulated slave connect to a spi master." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/spi/int_spi_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/flexio/spi/int_spi_transfer/slave" type="xml">
<files mask="flexio_spi_int_spi_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_uart_dma_transfer" name="flexio_uart_dma_transfer" brief="The flexio_uart_dma example shows how to use flexio uart driver in dma way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send back all charactersthat PC send to the board. Note: two queued transfer in this example, so please input even number characters." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/uart/dma_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/uart/dma_transfer" type="xml">
<files mask="flexio_uart_dma_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_uart_int_rb_transfer" name="flexio_uart_int_rb_transfer" brief="The flexio_uart_interrupt_ring_buffer example shows how to use flexio uart driver in interrupt way withRX ring buffer enabled:In this example, a flexio simulated uart connect to PC through USB-Serial, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/uart/int_rb_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/uart/int_rb_transfer" type="xml">
<files mask="flexio_uart_int_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_uart_interrupt_transfer" name="flexio_uart_interrupt_transfer" brief="The flexio_uart_interrupt example shows how to use flexio uart driver in interrupt way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send back all charactersthat PC send to the board. Note: two queued transfer in this example, so please input even number characters." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/uart/interrupt_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/uart/interrupt_transfer" type="xml">
<files mask="flexio_uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_flexio_uart_polling_transfer" name="flexio_uart_polling_transfer" brief="The flexio_uart_polling example shows how to use flexio uart driver in polling way:In this example, a flexio simulated uart connect to PC through USB-Serial, the board will send backall characters that PC send to the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexio" path="boards/frdmkl27z/driver_examples/flexio/uart/polling_transfer">
<external path="boards/frdmkl27z/driver_examples/flexio/uart/polling_transfer" type="xml">
<files mask="flexio_uart_polling_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_gpio_input_interrupt" name="gpio_input_interrupt" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example uses the software button to control/toggle the LED." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmkl27z/driver_examples/gpio/input_interrupt">
<external path="boards/frdmkl27z/driver_examples/gpio/input_interrupt" type="xml">
<files mask="gpio_input_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_gpio_led_output" name="gpio_led_output" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example take turns to shine the LED." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmkl27z/driver_examples/gpio/led_output">
<external path="boards/frdmkl27z/driver_examples/gpio/led_output" type="xml">
<files mask="gpio_led_output.xml"/>
</external>
</example>
<example id="frdmkl27z_hello_world" name="hello_world" brief="The Hello World demo application provides a sanity check for the new SDK build environments and board bring up. The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers. The purpose of this demo is toshow how to use the UART, and to provide a simple project for debugging and further development." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/hello_world">
<external path="boards/frdmkl27z/demo_apps/hello_world" type="xml">
<files mask="hello_world.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_dma_b2b_transfer_master" name="i2c_dma_b2b_transfer_master" brief="The i2c_dma_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with DMA:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/dma_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/i2c/dma_b2b_transfer/master" type="xml">
<files mask="i2c_dma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_dma_b2b_transfer_slave" name="i2c_dma_b2b_transfer_slave" brief="The i2c_dma_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with a DMA master:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/dma_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/i2c/dma_b2b_transfer/slave" type="xml">
<files mask="i2c_dma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_interrupt" name="i2c_interrupt" brief="The i2c_functional_interrupt example shows how to use I2C functional driver to build a interrupt based application:In this example , one i2c instance used as I2C master and another i2c instance used as I2C slave .1. I2C master send data to I2C slave in interrupt . (I2C Slave using interrupt to receive the data)2. I2C master read data from I2C slave in interrupt . (I2C Slave using interrupt to send the data)3. The example assumes that the connection is OK between master and slave, so there's NO error handling code." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/interrupt">
<external path="boards/frdmkl27z/driver_examples/i2c/interrupt" type="xml">
<files mask="i2c_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_interrupt_b2b_transfer_master" name="i2c_interrupt_b2b_transfer_master" brief="The i2c_interrupt_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with interrupt:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/interrupt_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/i2c/interrupt_b2b_transfer/master" type="xml">
<files mask="i2c_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_interrupt_b2b_transfer_slave" name="i2c_interrupt_b2b_transfer_slave" brief="The i2c_interrupt_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with interrupt:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/interrupt_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/i2c/interrupt_b2b_transfer/slave" type="xml">
<files mask="i2c_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_polling_b2b_transfer_master" name="i2c_polling_b2b_transfer_master" brief="The i2c_polling_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer using polling method:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/polling_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/i2c/polling_b2b_transfer/master" type="xml">
<files mask="i2c_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_polling_b2b_transfer_slave" name="i2c_polling_b2b_transfer_slave" brief="The i2c_polling_b2b_transfer_slave example shows how to use i2c driver as slave to do board to board transfer with a polling master:In this example, one i2c instance as slave and another i2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/polling_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/i2c/polling_b2b_transfer/slave" type="xml">
<files mask="i2c_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_i2c_read_accel_value_transfer" name="i2c_read_accel_value_transfer" brief="The i2c_read_accel_value example shows how to use I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkl27z/driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmkl27z/driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/led_blinky">
<external path="boards/frdmkl27z/demo_apps/led_blinky" type="xml">
<files mask="led_blinky.xml"/>
</external>
</example>
<example id="frdmkl27z_led_control_bm" name="led_control_bm" brief="The LED demo is used to demonstrate how to use new components. The main function of the demo is to control the led by using the shell or button. For shell, please enter \"help\" to get the help information firstly. Turn on LED by using command \"led on\". And turn off LED by using command \"led off\". For button, please press the corresponding button to control LED. Turn on LED when the button is pressed with long press or double click event. And turn off LED when the button is pressed with short press or one click event." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="component_examples" path="boards/frdmkl27z/component_examples/led_control/bm">
<external path="boards/frdmkl27z/component_examples/led_control/bm" type="xml">
<files mask="led_control_bm.xml"/>
</external>
</example>
<example id="frdmkl27z_lptmr" name="lptmr" brief="The LPTMR project is a simple demonstration program of the SDK LPTMR driver. It sets up the LPTMRhardware block to trigger a periodic interrupt after every 1 second. When the LPTMR interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/lptmr">
<external path="boards/frdmkl27z/driver_examples/lptmr" type="xml">
<files mask="lptmr.xml"/>
</external>
</example>
<example id="frdmkl27z_lpuart_dma_rb_transfer" name="lpuart_dma_rb_transfer" brief="The lpuart_dma 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." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/dma_rb_transfer">
<external path="boards/frdmkl27z/driver_examples/lpuart/dma_rb_transfer" type="xml">
<files mask="lpuart_dma_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_lpuart_dma_transfer" name="lpuart_dma_transfer" brief="The lpuart_dma 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="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/dma_transfer">
<external path="boards/frdmkl27z/driver_examples/lpuart/dma_transfer" type="xml">
<files mask="lpuart_dma_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/interrupt">
<external path="boards/frdmkl27z/driver_examples/lpuart/interrupt" type="xml">
<files mask="lpuart_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/interrupt_rb_transfer">
<external path="boards/frdmkl27z/driver_examples/lpuart/interrupt_rb_transfer" type="xml">
<files mask="lpuart_interrupt_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmkl27z/driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_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="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkl27z/driver_examples/lpuart/polling">
<external path="boards/frdmkl27z/driver_examples/lpuart/polling" type="xml">
<files mask="lpuart_polling.xml"/>
</external>
</example>
<example id="frdmkl27z_mcglite" name="mcglite" brief="The MCG_Lite example shows how to use MCG_Lite driver: 1. How to use the mode functions for MCG_Lite mode switch. 2. How to use the frequency functions to get current MCG_Lite frequency. 3. Work flow Reset mode --> LIRC8M LIRC8M --> HIRC HIRC --> LIRC2M LIRC2M --> EXT EXT --> HIRC HIRC --> LIRC8M LIRC8M --> EXT EXT --> LIRC2M LIRC2M --> HIRC HIRC --> EXT EXT --> LIRC8M LIRC8M --> LIRC2M LIRC2M --> LIRC8MIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/mcglite">
<external path="boards/frdmkl27z/driver_examples/mcglite" type="xml">
<files mask="mcglite.xml"/>
</external>
</example>
<example id="frdmkl27z_pflash" name="pflash" brief="The pflash example shows how to use flash driver to operate program flash:" toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmkl27z/driver_examples/flash/pflash">
<external path="boards/frdmkl27z/driver_examples/flash/pflash" type="xml">
<files mask="pflash.xml"/>
</external>
</example>
<example id="frdmkl27z_pit" name="pit" brief="The PIT project is a simple demonstration program of the SDK PIT driver. It sets up the PIThardware block to trigger a periodic interrupt after every 1 second. When the PIT interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/pit">
<external path="boards/frdmkl27z/driver_examples/pit" type="xml">
<files mask="pit.xml"/>
</external>
</example>
<example id="frdmkl27z_power_manager" name="power_manager" brief="The Power manager demo application demonstrates the use of power modes in the KSDK. The demo use the notification mechanismand prints the power mode menu through the debug console, where the user can set the MCU to a specific power mode. The usercan also set the wakeup source by following the debug console prompts. The purpose of this demo is to demonstrate theimplementation of a power mode manager. The callback can be registered to the framework. If a power mode transition happens,the callback will be called and user can do something. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/power_manager">
<external path="boards/frdmkl27z/demo_apps/power_manager" type="xml">
<files mask="power_manager.xml"/>
</external>
</example>
<example id="frdmkl27z_power_mode_switch" name="power_mode_switch" brief="The Power mode switch demo application demonstrates the use of power modes in the KSDK. The demo prints the power mode menuthrough the debug console, where the user can set the MCU to a specific power mode. The user can also set the wakeupsource by following the debug console prompts. The purpose of this demo is to show how to switch between different power modes, and how to configure a wakeup source and wakeup the MCU from low power modes. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware. - Debug pins(e.g SWD_DIO) would consume addtional power, had better to disable related pins or disconnect them. " toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/power_mode_switch">
<external path="boards/frdmkl27z/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch.xml"/>
</external>
</example>
<example id="frdmkl27z_rtc" name="rtc" brief="The RTC project is a simple demonstration program of the SDK RTC driver. It sets up the RTChardware block to trigger an alarm after a user specified time period. The test will set the currentdate and time to a predefined value. The alarm will be set with reference to this predefined dateand time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkl27z/driver_examples/rtc">
<external path="boards/frdmkl27z/driver_examples/rtc" type="xml">
<files mask="rtc.xml"/>
</external>
</example>
<example id="frdmkl27z_rtc_func" name="rtc_func" brief="The RTC demo application demonstrates the important features of the RTC Module by using the RTC Peripheral Driver.The RTC demo supports the following features:- Calendar + Get the current date time with Year, Month, Day, Hour, Minute, and Second. + Set the current date time with Year, Month, Day, Hour, Minute, and Second.- Alarm + Set the alarm based on the current time. + Application prints a notification when the alarm expires.- Seconds interrupt + Use second interrupt function to display a digital time blink every second." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/rtc_func">
<external path="boards/frdmkl27z/demo_apps/rtc_func" type="xml">
<files mask="rtc_func.xml"/>
</external>
</example>
<example id="frdmkl27z_rtc_func_peripheral" name="rtc_func_peripheral" brief="The RTC demo application demonstrates the important features of the RTC Module by using the RTC Peripheral Driver.The RTC demo supports the following features:- Calendar + Get the current date time with Year, Month, Day, Hour, Minute, and Second. + Set the current date time with Year, Month, Day, Hour, Minute, and Second.- Alarm + Set the alarm based on the current time. + Application prints a notification when the alarm expires.- Seconds interrupt + Use second interrupt function to display a digital time blink every second." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/rtc_func_peripheral">
<external path="boards/frdmkl27z/demo_apps/rtc_func_peripheral" type="xml">
<files mask="rtc_func_peripheral.xml"/>
</external>
</example>
<example id="frdmkl27z_shell" name="shell" brief="The Shell Demo application demonstrates to control Leds by commands." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkl27z/demo_apps/shell">
<external path="boards/frdmkl27z/demo_apps/shell" type="xml">
<files mask="shell.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_3wire_interrupt_transfer" name="spi_3wire_interrupt_transfer" brief="The spi_3wire_interrupt_transfer example shows how to use spi driver in 3-wire mode:In this example, one spi instance as master and another spi instance as slave. Master sends a piece of data to slave,and check if the data slave received is correct. Actually, spi 3-wire mode can also support DMA transfer." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/3wire_interrupt_transfer">
<external path="boards/frdmkl27z/driver_examples/spi/3wire_interrupt_transfer" type="xml">
<files mask="spi_3wire_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_dma_b2b_transfer_master" name="spi_dma_b2b_transfer_master" brief="The spi_dma_board2board_master example shows how to use spi driver as master to do board to board transfer with DMA:In this example, one spi instance as master and another spi instance on othereboard as slave. Master sends a piece ofdata to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/dma_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/spi/dma_b2b_transfer/master" type="xml">
<files mask="spi_dma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_dma_b2b_transfer_slave" name="spi_dma_b2b_transfer_slave" brief="The spi_dma_board2board_slave example shows how to use spi driver as slave to do board to board transfer with DMA:In this example, one spi instance as slave and another spi instance on other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from master is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/dma_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/spi/dma_b2b_transfer/slave" type="xml">
<files mask="spi_dma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_interrupt" name="spi_interrupt" brief="The spi_interrupt example shows how to use spi functional API to do interrupt transfer:In this example, one spi instance as master and another spi instance as slave. Master sends a piece of data to slave,and check if the data slave received is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/interrupt">
<external path="boards/frdmkl27z/driver_examples/spi/interrupt" type="xml">
<files mask="spi_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_interrupt_b2b_master" name="spi_interrupt_b2b_master" brief="The spi_interrupt_b2b_master example shows how to use spi functional API to do interrupt transfer as a master:In this example, the spi instance as master. Master sends a piece of data to slave, receive data from slave,and checkif the data master received is correct. This example needs to work with spi_interrupt_b2b_slave example." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b/master">
<external path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b/master" type="xml">
<files mask="spi_interrupt_b2b_master.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_interrupt_b2b_slave" name="spi_interrupt_b2b_slave" brief="The spi_interrupt_b2b_slave example shows how to use spi functional API to do interrupt transfer as a slave:In this example, the spi instance as slave. Slave receives data froma master and send a peiece of data to master,and check if the data slave received is correct. This example needs to work with spi_interrupt_b2b_master example." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b/slave">
<external path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b/slave" type="xml">
<files mask="spi_interrupt_b2b_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_interrupt_b2b_transfer_master" name="spi_interrupt_b2b_transfer_master" brief="The spi_interrupt_board2board_master example shows how to use spi driver as master to do board to board transfer withinterrupt:In this example, one spi instance as master and another spi instance on othereboard as slave. Master sends a piece ofdata to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b_transfer/master" type="xml">
<files mask="spi_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_interrupt_b2b_transfer_slave" name="spi_interrupt_b2b_transfer_slave" brief="The spi_interrupt_board2board_slave example shows how to use spi driver as slave to do board to board transfer with interrupt:In this example, one spi instance as slave and another spi instance on other board as master. Master sends a piece ofdata to slave, and receive a piece of data from slave. This example checks if the data received from master is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/spi/interrupt_b2b_transfer/slave" type="xml">
<files mask="spi_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_polling_b2b_transfer_master" name="spi_polling_b2b_transfer_master" brief="The spi_polling_board2board_master example shows how to use spi driver as master to do board to board transfer with polling:In this example, one spi instance as master and another spi instance on othereboard as slave. Master sends a piece ofdata to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/polling_b2b_transfer/master">
<external path="boards/frdmkl27z/driver_examples/spi/polling_b2b_transfer/master" type="xml">
<files mask="spi_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkl27z_spi_polling_b2b_transfer_slave" name="spi_polling_b2b_transfer_slave" brief="The spi_polling_board2board_slave example shows how to use spi driver as slave to do board to board transfer withpolling:Notice: The SPI slave of this example uses interrupt mode, as there is no polling mode for SPI slave.In this example, one spi instance as slave and another spi instance on other board as master. Master sends a piece ofdata to slave, and receive a piece of data from slave. This example checks if the data received from master is correct." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/spi" path="boards/frdmkl27z/driver_examples/spi/polling_b2b_transfer/slave">
<external path="boards/frdmkl27z/driver_examples/spi/polling_b2b_transfer/slave" type="xml">
<files mask="spi_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkl27z_tpm_input_capture" name="tpm_input_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's input capture feature.The example sets up a TPM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkl27z/driver_examples/tpm/input_capture">
<external path="boards/frdmkl27z/driver_examples/tpm/input_capture" type="xml">
<files mask="tpm_input_capture.xml"/>
</external>
</example>
<example id="frdmkl27z_tpm_output_compare" name="tpm_output_compare" brief="The TPM project is a demonstration program of the SDK TPM driver's output compare feature.It sets up one TPM channel to toggle the output when a match occurs with the channel value. The usershould probe the TPM output with a oscilloscope to see the signal toggling." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkl27z/driver_examples/tpm/output_compare">
<external path="boards/frdmkl27z/driver_examples/tpm/output_compare" type="xml">
<files mask="tpm_output_compare.xml"/>
</external>
</example>
<example id="frdmkl27z_tpm_pwm_twochannel" name="tpm_pwm_twochannel" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The PWM dutycycle on both channelsis manually updated. On boards that have an LED connected to the TPM pins, the user will seea change in LED brightness if user enter different values." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkl27z/driver_examples/tpm/pwm_twochannel">
<external path="boards/frdmkl27z/driver_examples/tpm/pwm_twochannel" type="xml">
<files mask="tpm_pwm_twochannel.xml"/>
</external>
</example>
<example id="frdmkl27z_tpm_simple_pwm" name="tpm_simple_pwm" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output a center-aligned PWM signal. The PWM dutycycle is manually updated.On boards that have an LED connected to the TPM pins, the user will see a change in LEDbrightness if user enter different values." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkl27z/driver_examples/tpm/simple_pwm">
<external path="boards/frdmkl27z/driver_examples/tpm/simple_pwm" type="xml">
<files mask="tpm_simple_pwm.xml"/>
</external>
</example>
<example id="frdmkl27z_tpm_timer" name="tpm_timer" brief="The TPM project is a simple demonstration program of the SDK TPM driver to use TPM as a timer.It sets up the TPM hardware block to trigger an interrupt every 1 millisecond.When the TPM interrupt is triggered a message a printed on the UART terminal." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkl27z/driver_examples/tpm/timer">
<external path="boards/frdmkl27z/driver_examples/tpm/timer" type="xml">
<files mask="tpm_timer.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_dma_rb_transfer" name="uart_dma_rb_transfer" brief="The uart_dma example shows how to use uart driver with DMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/dma_rb_transfer">
<external path="boards/frdmkl27z/driver_examples/uart/dma_rb_transfer" type="xml">
<files mask="uart_dma_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_dma_transfer" name="uart_dma_transfer" brief="The uart_dma example shows how to use uart driver with DMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/dma_transfer">
<external path="boards/frdmkl27z/driver_examples/uart/dma_transfer" type="xml">
<files mask="uart_dma_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_interrupt" name="uart_interrupt" brief="The uart_functioncal_interrupt example shows how to use uart driver functionalAPI to receive data with interrupt method:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/interrupt">
<external path="boards/frdmkl27z/driver_examples/uart/interrupt" type="xml">
<files mask="uart_interrupt.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_interrupt_rb_transfer" name="uart_interrupt_rb_transfer" brief="The uart_interrupt_ring_buffer example shows how to use uart driver in interrupt way withRX ring buffer enabled:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/interrupt_rb_transfer">
<external path="boards/frdmkl27z/driver_examples/uart/interrupt_rb_transfer" type="xml">
<files mask="uart_interrupt_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_interrupt_transfer" name="uart_interrupt_transfer" brief="The uart_interrupt example shows how to use uart driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/interrupt_transfer">
<external path="boards/frdmkl27z/driver_examples/uart/interrupt_transfer" type="xml">
<files mask="uart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkl27z_uart_polling" name="uart_polling" brief="The uart_polling example shows how to use uart driver in polling way:In this example, one uart instance connect to PC through uart, the board will send back all characters that PCsend to the board." toolchain="armgcc mcuxpresso" compiler="compiler_gcc" category="driver_examples/uart" path="boards/frdmkl27z/driver_examples/uart/polling">
<external path="boards/frdmkl27z/driver_examples/uart/polling" type="xml">
<files mask="uart_polling.xml"/>
</external>
</example>
</examples>
</board>
</boards>
<devices>
<device id="MKL27Z64xxx4" name="MKL27Z644" version="1.0.0" full_name="MKL27Z64xxx4" family="KL2x" platform="Kinetis">
<description>Kinetis KL2x-48 MHz, USB Ultra-Low-Power Microcontrollers (MCUs) based on ARM Cortex-M0+ Core</description>
<metadataSet>
<metadata key="USB_KHCI_COUNT" value="1"/>
<metadata key="vendor" value="NXP"/>
</metadataSet>
<core id="core0_MKL27Z64xxx4" name="core0" fpu="false" type="cm0plus"/>
<memory>
<memoryBlock id="PROGRAM_FLASH_MKL27Z64xxx4" name="PROGRAM_FLASH" addr="00000000" size="00010000" type="Flash" access="RO"/>
<memoryBlock id="SRAM_MKL27Z64xxx4" name="SRAM" addr="1ffff000" size="00004000" type="RAM" access="RW"/>
<memoryBlock id="USB_RAM_MKL27Z64xxx4" name="USB_RAM" addr="400fe000" size="00000200" type="RAM" access="RW"/>
</memory>
<total_memory flash_size_kb="64" ram_size_kb="16"/>
<package id="MKL27Z64VDA4" name="MKL27Z64VDA4"/>
<package id="MKL27Z64VFT4" name="MKL27Z64VFT4"/>
<package id="MKL27Z64VMP4" name="MKL27Z64VMP4"/>
<package id="MKL27Z64VFM4" name="MKL27Z64VFM4"/>
<package id="MKL27Z64VLH4" name="MKL27Z64VLH4"/>
<evaluation_boards>
<evaluation_board name="frdmkl27z"/>
</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.MKL27Z64xxx4" name="internal.wiretype" value="SWD"/>
<params id="internal.has_swo.release.MKL27Z64xxx4" name="internal.has_swo" value="false"/>
<params id="internal.connect.script.debug.mcuxpresso.MKL27Z64xxx4" name="internal.connect.script" value="kinetisconnect.scp"/>
</params>
<drivers>
<driver id_refs="PROGRAM_FLASH_MKL27Z64xxx4">
<driverBinary 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="MKL17Z32xxx4" name="MKL17Z644" version="1.0.0" full_name="MKL17Z32xxx4" family="KL1x" platform="Kinetis">
<description>Kinetis KL1x-48 MHz, Mainstream Small Ultra-Low Power Microcontrollers (MCUs) based on ARM Cortex-M0+ Core</description>
<metadataSet>
<metadata key="vendor" value="NXP"/>
</metadataSet>
<core id="core0_MKL17Z32xxx4" name="core0" fpu="false" type="cm0plus"/>
<memory>
<memoryBlock id="PROGRAM_FLASH_MKL17Z32xxx4" name="PROGRAM_FLASH" addr="00000000" size="00008000" type="Flash" access="RO"/>
<memoryBlock id="SRAM_MKL17Z32xxx4" name="SRAM" addr="1ffff800" size="00002000" type="RAM" access="RW"/>
</memory>
<total_memory flash_size_kb="32" ram_size_kb="8"/>
<package id="MKL17Z32VDA4" name="MKL17Z32VDA4"/>
<package id="MKL17Z32VFT4" name="MKL17Z32VFT4"/>
<package id="MKL17Z32VLH4" name="MKL17Z32VLH4"/>
<package id="MKL17Z32VFM4" name="MKL17Z32VFM4"/>
<package id="MKL17Z32VMP4" name="MKL17Z32VMP4"/>
<evaluation_boards>
<evaluation_board name="frdmkl27z"/>
</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.MKL17Z32xxx4" name="internal.wiretype" value="SWD"/>
<params id="internal.has_swo.release.MKL17Z32xxx4" name="internal.has_swo" value="false"/>
<params id="internal.connect.script.debug.mcuxpresso.MKL17Z32xxx4" name="internal.connect.script" value="kinetisconnect.scp"/>
</params>
<drivers>
<driver id_refs="PROGRAM_FLASH_MKL17Z32xxx4">
<driverBinary 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.frdmkl27z.MKL27Z644" name="frdmkl27z" brief="Board_project_template frdmkl27z" version="1.0.0" full_name="Board_project_template frdmkl27z" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" category="Board Support/SDK Project Template" user_visible="true" type="project_template">
<dependencies>
<all>
<component_dependency value="platform.drivers.lpuart.MKL27Z644"/>
<component_dependency value="component.lpuart_adapter.MKL27Z644"/>
<component_dependency value="platform.drivers.port.MKL27Z644"/>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="utility.debug_console.MKL27Z644"/>
<component_dependency value="component.serial_manager.MKL27Z644"/>
<component_dependency value="platform.drivers.gpio.MKL27Z644"/>
<component_dependency value="platform.drivers.smc.MKL27Z644"/>
<component_dependency value="device.MKL27Z644_startup.MKL27Z644"/>
<component_dependency value="platform.drivers.i2c.MKL27Z644"/>
</all>
</dependencies>
<source path="boards/frdmkl27z/project_template" target_path="board" type="src">
<files mask="board.c"/>
<files mask="clock_config.c"/>
<files mask="peripherals.c"/>
<files mask="pin_mux.c"/>
</source>
<source path="boards/frdmkl27z/project_template" target_path="board" type="c_include">
<files mask="board.h"/>
<files mask="clock_config.h"/>
<files mask="peripherals.h"/>
<files mask="pin_mux.h"/>
</source>
</component>
<component id="platform.CMSIS.MKL27Z644" name="CMSIS" brief="Cmsis" version="5.6.0" full_name="Cmsis" devices="MKL27Z64xxx4" user_visible="true" type="CMSIS">
<dependencies>
<all>
<component_dependency value="platform.Include_common.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver"/>
<component_dependency value="platform.CMSIS_Driver_Include.CAN_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_MAC_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_PHY_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.Flash_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.I2C_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.MCI_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.NAND_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.SAI_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.SPI_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.USART_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_Device_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_Host_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.CMSIS_Driver_Include.WiFi_CMSISInclude.MKL27Z644"/>
<component_dependency value="platform.Include_dsp.MKL27Z644"/>
</all>
</dependencies>
<source path="CMSIS/Include" target_path="Include" type="c_include">
<files mask="arm_common_tables.h"/>
<files mask="arm_const_structs.h"/>
<files mask="arm_math.h"/>
<files mask="cmsis_armcc.h"/>
<files mask="cmsis_armclang.h"/>
<files mask="cmsis_armclang_ltm.h"/>
<files mask="cmsis_compiler.h"/>
<files mask="cmsis_gcc.h"/>
<files mask="cmsis_iccarm.h"/>
<files mask="cmsis_version.h"/>
<files mask="core_armv81mml.h"/>
<files mask="core_armv8mbl.h"/>
<files mask="core_armv8mml.h"/>
<files mask="core_cm0.h"/>
<files mask="core_cm0plus.h"/>
<files mask="core_cm1.h"/>
<files mask="core_cm23.h"/>
<files mask="core_cm3.h"/>
<files mask="core_cm33.h"/>
<files mask="core_cm35p.h"/>
<files mask="core_cm4.h"/>
<files mask="core_cm7.h"/>
<files mask="core_dsp.h"/>
<files mask="core_sc000.h"/>
<files mask="core_sc300.h"/>
<files mask="mpu_armv7.h"/>
<files mask="mpu_armv8.h"/>
<files mask="tz_context.h"/>
</source>
<source path="CMSIS" target_path="CMSIS" type="doc">
<files mask="LICENSE.txt"/>
</source>
</component>
<component id="platform.CMSIS_Driver" name="CMSIS_Driver" brief="Cmsis_driver" version="2.7.1" full_name="Cmsis_driver" user_visible="true" type="CMSIS">
<source path="CMSIS/Driver/DriverTemplates" target_path="Driver/DriverTemplates" type="src">
<files mask="Driver_CAN.c"/>
<files mask="Driver_ETH_MAC.c"/>
<files mask="Driver_ETH_PHY.c"/>
<files mask="Driver_Flash.c"/>
<files mask="Driver_I2C.c"/>
<files mask="Driver_MCI.c"/>
<files mask="Driver_SAI.c"/>
<files mask="Driver_SPI.c"/>
<files mask="Driver_Storage.c"/>
<files mask="Driver_USART.c"/>
<files mask="Driver_USBD.c"/>
<files mask="Driver_USBH.c"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.CAN_CMSISInclude.MKL27Z644" name="CAN" brief="Cmsis_driver_include can" version="1.2.0" full_name="Cmsis_driver_include can" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_CAN.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644" name="Common" brief="Cmsis_driver_include common" version="2.7.1" full_name="Cmsis_driver_include common" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_Common.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.Ethernet_CMSISInclude.MKL27Z644" name="Ethernet" brief="Cmsis_driver_include ethernet" version="2.1.0" full_name="Cmsis_driver_include ethernet" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_ETH.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.Ethernet_MAC_CMSISInclude.MKL27Z644" name="Ethernet_MAC" brief="Cmsis_driver_include ethernet_mac" version="2.1.0" full_name="Cmsis_driver_include ethernet_mac" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_ETH_MAC.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.Ethernet_PHY_CMSISInclude.MKL27Z644" name="Ethernet_PHY" brief="Cmsis_driver_include ethernet_phy" version="2.1.0" full_name="Cmsis_driver_include ethernet_phy" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_ETH_PHY.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.Flash_CMSISInclude.MKL27Z644" name="Flash" brief="Cmsis_driver_include flash" version="2.2.0" full_name="Cmsis_driver_include flash" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_Flash.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.I2C_CMSISInclude.MKL27Z644" name="I2C" brief="Cmsis_driver_include i2c" version="2.3.0" full_name="Cmsis_driver_include i2c" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_I2C.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.MCI_CMSISInclude.MKL27Z644" name="MCI" brief="Cmsis_driver_include mci" version="2.3.0" full_name="Cmsis_driver_include mci" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_MCI.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.NAND_CMSISInclude.MKL27Z644" name="NAND" brief="Cmsis_driver_include nand" version="2.3.0" full_name="Cmsis_driver_include nand" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_NAND.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.SAI_CMSISInclude.MKL27Z644" name="SAI" brief="Cmsis_driver_include sai" version="1.1.0" full_name="Cmsis_driver_include sai" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_SAI.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.SPI_CMSISInclude.MKL27Z644" name="SPI" brief="Cmsis_driver_include spi" version="2.2.0" full_name="Cmsis_driver_include spi" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_SPI.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.USART_CMSISInclude.MKL27Z644" name="USART" brief="Cmsis_driver_include usart" version="2.3.0" full_name="Cmsis_driver_include usart" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_USART.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.USB_CMSISInclude.MKL27Z644" name="USB" brief="Cmsis_driver_include usb" version="2.2.0" full_name="Cmsis_driver_include usb" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_USB.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.USB_Device_CMSISInclude.MKL27Z644" name="USB_Device" brief="Cmsis_driver_include usb_device" version="2.2.0" full_name="Cmsis_driver_include usb_device" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.USB_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_USBD.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.USB_Host_CMSISInclude.MKL27Z644" name="USB_Host" brief="Cmsis_driver_include usb_host" version="2.2.0" full_name="Cmsis_driver_include usb_host" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.USB_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_USBH.h"/>
</source>
</component>
<component id="platform.CMSIS_Driver_Include.WiFi_CMSISInclude.MKL27Z644" name="WiFi" brief="Cmsis_driver_include wifi" version="1.0.0" full_name="Cmsis_driver_include wifi" devices="MKL27Z64xxx4" user_visible="false" type="CMSIS_driver">
<dependencies>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MKL27Z644"/>
</dependencies>
<source path="CMSIS/Driver/Include" target_path="CMSIS_driver" type="c_include">
<files mask="Driver_WiFi.h"/>
</source>
</component>
<component id="platform.Include_common.MKL27Z644" name="CMSIS_Include_common" brief="Cmsis_include_common" version="5.3.0" full_name="Cmsis_include_common" devices="MKL27Z64xxx4" user_visible="true" type="CMSIS_Include">
<source path="CMSIS/Include" target_path="CMSIS" type="c_include">
<files mask="cmsis_armcc.h"/>
<files mask="cmsis_armclang.h"/>
<files mask="cmsis_armclang_ltm.h"/>
<files mask="cmsis_compiler.h"/>
<files mask="cmsis_gcc.h"/>
<files mask="cmsis_iccarm.h"/>
<files mask="cmsis_version.h"/>
</source>
</component>
<component id="platform.Include_core_cm0plus.MKL27Z644" name="CMSIS_Include_core_cm0plus" brief="Cmsis_include_core_cm0plus" version="5.3.0" full_name="Cmsis_include_core_cm0plus" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="CMSIS_Include">
<dependencies>
<all>
<component_dependency value="platform.Include_common.MKL27Z644"/>
<component_dependency value="platform.Include_dsp.MKL27Z644"/>
</all>
</dependencies>
<source path="CMSIS/Include" target_path="CMSIS" type="c_include">
<files mask="core_cm0plus.h"/>
<files mask="mpu_armv7.h"/>
</source>
</component>
<component id="platform.Include_dsp.MKL27Z644" name="CMSIS_Include_dsp" brief="Cmsis_include_dsp" version="1.7.0" full_name="Cmsis_include_dsp" devices="MKL27Z64xxx4" user_visible="true" type="CMSIS_Include">
<source path="CMSIS/Include" target_path="CMSIS" type="c_include">
<files mask="arm_common_tables.h"/>
<files mask="arm_const_structs.h"/>
<files mask="arm_math.h"/>
</source>
</component>
<component id="COPY_BSD_License.MKL27Z644" name="COPY_BSD_License" brief="COPY of BSD-3-Clause license" version="1.0.0" full_name="COPY of BSD-3-Clause license" devices="MKL27Z64xxx4" user_visible="true" type="other">
<source path="." target_path="src" type="other">
<files mask="COPYING-BSD-3"/>
</source>
</component>
<component id="project_template.MKL27Z644.MKL27Z644" name="MKL27Z644" brief="Devices_project_template MKL27Z644" version="1.0.0" full_name="Devices_project_template MKL27Z644" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" category="Board Support/SDK Project Template" user_visible="true" type="project_template">
<dependencies>
<all>
<component_dependency value="platform.drivers.lpuart.MKL27Z644"/>
<component_dependency value="component.lpuart_adapter.MKL27Z644"/>
<component_dependency value="platform.drivers.port.MKL27Z644"/>
<component_dependency value="platform.drivers.gpio.MKL27Z644"/>
<component_dependency value="platform.drivers.smc.MKL27Z644"/>
<component_dependency value="device.MKL27Z644_startup.MKL27Z644"/>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="utility.debug_console.MKL27Z644"/>
<component_dependency value="component.serial_manager.MKL27Z644"/>
<component_dependency value="platform.drivers.clock.MKL27Z644"/>
<component_dependency value="platform.drivers.i2c.MKL27Z644"/>
</all>
</dependencies>
<source path="devices/MKL27Z644/project_template" target_path="board" type="src">
<files mask="board.c"/>
<files mask="clock_config.c"/>
<files mask="peripherals.c"/>
<files mask="pin_mux.c"/>
</source>
<source path="devices/MKL27Z644/project_template" target_path="board" type="c_include">
<files mask="board.h"/>
<files mask="clock_config.h"/>
<files mask="peripherals.h"/>
<files mask="pin_mux.h"/>
</source>
</component>
<component id="RTE_Device.MKL27Z644" name="RTE_Device" brief="Rte_device" version="1.0.0" full_name="Rte_device" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" category="Device/SDK Project Template" user_visible="true" type="project_template">
<dependencies>
<all>
<component_dependency value="platform.drivers.dma.MKL27Z644"/>
<component_dependency value="platform.drivers.dmamux.MKL27Z644"/>
</all>
</dependencies>
<source path="devices/MKL27Z644/template" target_path="board" type="c_include">
<files mask="RTE_Device.h"/>
</source>
</component>
<component id="tools.MKL27Z644" name="cmake_toolchain" brief="Cmake_toolchain" version="1.0.0" full_name="Cmake_toolchain" devices="MKL27Z64xxx4" user_visible="true" type="other">
<source path="tools/cmake_toolchain_files" target_path="cmake_toolchain_files" type="script">
<files mask="armgcc.cmake"/>
<files mask="armgcc_force_cpp.cmake"/>
<files mask="xcc.cmake"/>
</source>
</component>
<component id="component.button.MKL27Z644" name="button" brief="Component button" version="1.0.0" full_name="Component button" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="software_component">
<dependencies>
<all>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="component.timer_manager.MKL27Z644"/>
<component_dependency value="component.gpio_adapter.MKL27Z644"/>
</all>
</dependencies>
<source path="components/button" target_path="component/button" type="src">
<files mask="button.c"/>
</source>
<source path="components/button" target_path="component/button" type="c_include">
<files mask="button.h"/>
</source>
</component>
<component id="component.common_task.MKL27Z644" name="common_task" brief="Component common_task" version="1.0.0" full_name="Component common_task" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="software_component">
<dependencies>
<all>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="component.osa.MKL27Z644"/>
</all>
</dependencies>
<source path="components/common_task" target_path="component/common_task" type="src">
<files mask="common_task.c"/>
</source>
<source path="components/common_task" target_path="component/common_task" type="c_include">
<files mask="common_task.h"/>
</source>
</component>
<component id="component.crc_adapter.MKL27Z644" name="crc_adapter" brief="Component crc_adapter" version="1.0.0" full_name="Component crc_adapter" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="abstraction_layer">
<dependencies>
<all>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="platform.drivers.crc.MKL27Z644"/>
</all>
</dependencies>
<source path="components/crc" target_path="component/crc" type="c_include">
<files mask="crc.h"/>
</source>
<source path="components/crc" target_path="component/crc" type="src">
<files mask="crc_adapter.c"/>
</source>
</component>
<component id="component.flash_adapter.MKL27Z644" name="flash_adapter" brief="Component flash_adapter" version="1.0.0" full_name="Component flash_adapter" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="abstraction_layer">
<dependencies>
<all>
<component_dependency value="platform.drivers.common.MKL27Z644"/>
<component_dependency value="platform.drivers.flash.MKL27Z644"/>
</all>
</dependencies>
<source path="components/internal_flash" target_path="component/internal_flash" type="c_include">
<files mask="flash.h"/>
</source>
<source path="components/internal_flash" target_path="component/internal_flash" type="src">
<files mask="flash_adapter.c"/>
</source>
</component>
<component id="component.gpio_adapter.MKL27Z644" name="gpio_adapter" brief="Component gpio_adapter" version="1.0.0" full_name="Component gpio_adapter" devices="MKL27Z64xxx4" device_cores="core0_MKL27Z64xxx4" user_visible="true" type="abstraction_layer">
<dependencies>