-
Notifications
You must be signed in to change notification settings - Fork 24
/
Copy pathMKW39A512xxx4_manifest_v3_5.xml
9222 lines (9222 loc) · 646 KB
/
MKW39A512xxx4_manifest_v3_5.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_MKW39A512xxx4" name="MKW39A512xxx4" brief="This is SDK version 2.6.5 manifest file. It describes the content of the MKW39A512xxx4 and additional settings for tools that support SDK version 2.6.5" format_version="3.5" api_version="2.0.0" configuration="39b17060679acfc6766b640cff849315" xsi:schemaLocation="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd http://nxp.com/mcuxpresso/sdk/sdk_manifest_v3.5.xsd">
<!--Timestamp (UTC): 2020-05-11 13:54:04.616084-->
<!--This manifest is generated based on sdk repo commit: cb5b9010adbb9222e1a7277f0ad768dfcd5e557f-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<externalDefinitions>
<definition extID="fpga_kw38"/>
<definition extID="fpgakw38"/>
</externalDefinitions>
<ksdk id="MCUXpresso265" name="MCUXpresso265" version="2.6.5" revision="347 2020-05-07"/>
<compilers>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
</compilers>
<toolchainSettings>
<toolchainSetting id="com.nxp.mcuxpresso" name="mcuxpresso" version="11.1.0" full_name="MCUXpresso IDE" compiler="compiler_gcc" toolchain="mcuxpresso">
<option id="gnu.cpp.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.c.compiler.option.optimization.flags" type="string" user_name="">
<value>-fno-common</value>
</option>
<option id="gnu.cpp.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.cpp.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="com.crt.advproject.link.flashconfigenable" type="boolean" user_name="">
<value>true</value>
</option>
<option id="gnu.c.link.option.nostdlibs" type="boolean" user_name="">
<value>true</value>
</option>
</toolchainSetting>
</toolchainSettings>
<toolchains>
<toolchain id="mcuxpresso" name="MCUXpresso_IDE" version="11.1.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="frdmkw38" name="FRDM-KW38" href="http://www.nxp.com/frdm-kw38" version="1.0.0" package="MKW38A512VFT4">
<description>FRDM-KW38: Freedom Development Platform for Kinetis KW37, KW38, and KW39 MCUs</description>
<image path="docs/images" type="image">
<files mask="FRDM-KW38.gif"/>
</image>
<metadataSet>
<metadata key="html">
<specific>
<content>The FRDM-KW38 is a development platform enabled by the Kinetis W series KW39/38/37 family built on ARM Cortex-M0+ processor with integrated 2.4 GHz transceiver supporting Bluetooth Smart/Bluetooth Low Energy (BLE) v4.2, Generic FSK.The FRDM-KW38 is form-factor compatible with the Arduino R3 pin layout for more expansion options.</content>
</specific>
</metadata>
</metadataSet>
<examples>
<example id="frdmkw38_adc16_interrupt" name="adc16_interrupt" brief="The adc16_interrupt example shows how to use interrupt with ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. ADC interrupt would be asserted once the conversion is completed. In ADC ISR, the conversion completed flag would be cleared by reading the conversion result value. Also, the conversion result value is stored, and the ISR counter is increased. These information would be printed when the execution return to the main loop.The point is that the ADC16 interrupt configuration is set when configuring the ADC16's conversion channel. When in software trigger mode, the conversion would be launched by the operation of configuring channel, just like writing aconversion command. So if user wants to generate the interrupt every time the conversion is completed, the channel's configuration with enabling interrupt setting would be used for each conversion." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc16" path="boards/frdmkw38/driver_examples/adc16/interrupt">
<external path="boards/frdmkw38/driver_examples/adc16/interrupt" type="xml">
<files mask="adc16_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_adc16_low_power" name="adc16_low_power" brief="The ADC Low Power demo application demonstrates the usage of the ADC peripheral while in a low power mode. Themicrocontroller is first set to very low power stop (VLPS) mode. Every 500 ms, an interrupt wakes up the ADC module andreads the current temperature of the microcontroller. While the temperature remains within boundaries, both LEDs are on.If the core temperature is higher or lower than average, the LEDs change state respectively." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/adc16_low_power">
<external path="boards/frdmkw38/demo_apps/adc16_low_power" type="xml">
<files mask="adc16_low_power.xml"/>
</external>
</example>
<example id="frdmkw38_adc16_polling" name="adc16_polling" brief="The adc16_polling example shows the simplest way to use ADC16 driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the ADC16'ssample input. When running the project, typing any key into debug console would trigger the conversion. The execution would check the conversion completed flag in loop until the flag is asserted, which means the conversion is completed. Then read the conversion result value and print it to debug console.Note, the default setting of initialization for the ADC converter is just an available configuration. User can changethe configuration structure's setting in application to fit the special requirement.The auto-calibration is not essential but strongly recommended. It can help to adjust the converter itself and improvethe ADC16's performance." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/adc16" path="boards/frdmkw38/driver_examples/adc16/polling">
<external path="boards/frdmkw38/driver_examples/adc16/polling" type="xml">
<files mask="adc16_polling.xml"/>
</external>
</example>
<example id="frdmkw38_adv_ext_central_bm" name="adv_ext_central_bm" brief="The BLE Extended advertising central application is a simple demonstration program that can exercise Extended Advertising and Periodic Advertising with Low Power Support based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/adv_ext_central/bm" path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_central/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_central/bm" type="xml">
<files mask="adv_ext_central_bm.xml"/>
</external>
</example>
<example id="frdmkw38_adv_ext_central_freertos" name="adv_ext_central_freertos" brief="The BLE Extended advertising central application is a simple demonstration program that can exercise Extended Advertising and Periodic Advertising with Low Power Support based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/adv_ext_central/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_central/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_central/freertos" type="xml">
<files mask="adv_ext_central_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_adv_ext_peripheral_bm" name="adv_ext_peripheral_bm" brief="The BLE Extended advertising peripheral application is a simple demonstration program that can exercise Extended Advertising and Periodic Advertising with Low Power Support based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/adv_ext_peripheral/bm" path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_peripheral/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_peripheral/bm" type="xml">
<files mask="adv_ext_peripheral_bm.xml"/>
</external>
</example>
<example id="frdmkw38_adv_ext_peripheral_freertos" name="adv_ext_peripheral_freertos" brief="The BLE Extended advertising peripheral application is a simple demonstration program that can exercise Extended Advertising and Periodic Advertising with Low Power Support based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/adv_ext_peripheral/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_peripheral/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/adv_ext_peripheral/freertos" type="xml">
<files mask="adv_ext_peripheral_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_alert_notification_server_bm" name="alert_notification_server_bm" brief="The BLE alert notification server application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Alert Notification Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ans/bm" path="boards/frdmkw38/wireless_examples/bluetooth/ans/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ans/bm" type="xml">
<files mask="alert_notification_server_bm.xml"/>
</external>
</example>
<example id="frdmkw38_alert_notification_server_freertos" name="alert_notification_server_freertos" brief="The BLE alert notification server application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Alert Notification Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ans/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/ans/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ans/freertos" type="xml">
<files mask="alert_notification_server_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_ancs_client_bm" name="ancs_client_bm" brief="The BLE ancs client application is a simple demonstration program based on the MCUXpresso SDK.This application implements an ANCS Client.To test the service/profile a GAP Central device is required which has the ANCS service available." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ancs_c/bm" path="boards/frdmkw38/wireless_examples/bluetooth/ancs_c/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ancs_c/bm" type="xml">
<files mask="ancs_client_bm.xml"/>
</external>
</example>
<example id="frdmkw38_ancs_client_freertos" name="ancs_client_freertos" brief="The BLE ancs client application is a simple demonstration program based on the MCUXpresso SDK.This application implements an ANCS Client.To test the service/profile a GAP Central device is required which has the ANCS service available." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ancs_c/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/ancs_c/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ancs_c/freertos" type="xml">
<files mask="ancs_client_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_beacon_bm" name="beacon_bm" brief="The BLE beacon application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Beacon BLE Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/beacon/bm" path="boards/frdmkw38/wireless_examples/bluetooth/beacon/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/beacon/bm" type="xml">
<files mask="beacon_bm.xml"/>
</external>
</example>
<example id="frdmkw38_beacon_freertos" name="beacon_freertos" brief="The BLE beacon application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Beacon BLE Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/beacon/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/beacon/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/beacon/freertos" type="xml">
<files mask="beacon_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_ble_fsci_black_box_bm" name="ble_fsci_black_box_bm" brief="The BLE ble fsci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooth Low Energy Host Black Box which can communicate using the FSCI protocol over a serial interface.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_fscibb/bm" path="boards/frdmkw38/wireless_examples/bluetooth/ble_fscibb/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_fscibb/bm" type="xml">
<files mask="ble_fsci_black_box_bm.xml"/>
</external>
</example>
<example id="frdmkw38_ble_fsci_black_box_freertos" name="ble_fsci_black_box_freertos" brief="The BLE ble fsci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooth Low Energy Host Black Box which can communicate using the FSCI protocol over a serial interface.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_fscibb/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/ble_fscibb/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_fscibb/freertos" type="xml">
<files mask="ble_fsci_black_box_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_ble_relay_proxy_bm" name="ble_relay_proxy_bm" brief="The BLE ble relay proxy application is a simple demonstration program based on the MCUXpresso SDK.The application implements a BLE node that proxies a connected GAP Peripheral for any connnected GAP Central and relays communication between the 2 active connections.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_rproxy/bm" path="boards/frdmkw38/wireless_examples/bluetooth/ble_rproxy/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_rproxy/bm" type="xml">
<files mask="ble_relay_proxy_bm.xml"/>
</external>
</example>
<example id="frdmkw38_ble_relay_proxy_freertos" name="ble_relay_proxy_freertos" brief="The BLE ble relay proxy application is a simple demonstration program based on the MCUXpresso SDK.The application implements a BLE node that proxies a connected GAP Peripheral for any connnected GAP Central and relays communication between the 2 active connections.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_rproxy/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/ble_rproxy/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_rproxy/freertos" type="xml">
<files mask="ble_relay_proxy_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_ble_shell_bm" name="ble_shell_bm" brief="The BLE ble shell application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Bluetooth Low Energy Host with a shell inteface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_shell/bm" path="boards/frdmkw38/wireless_examples/bluetooth/ble_shell/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_shell/bm" type="xml">
<files mask="ble_shell_bm.xml"/>
</external>
</example>
<example id="frdmkw38_ble_shell_freertos" name="ble_shell_freertos" brief="The BLE ble shell application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Bluetooth Low Energy Host with a shell inteface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_shell/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/ble_shell/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/ble_shell/freertos" type="xml">
<files mask="ble_shell_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_ble_w_uart_gfsk_bm" name="ble_w_uart_gfsk_bm" brief="The ble w_uart application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Hybrid Bluetooth Generic FSK demo." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/hybrid/ble_w_uart_gfsk/bm" path="boards/frdmkw38/wireless_examples/hybrid/ble_w_uart_gfsk/bm">
<external path="boards/frdmkw38/wireless_examples/hybrid/ble_w_uart_gfsk/bm" type="xml">
<files mask="ble_w_uart_gfsk_bm.xml"/>
</external>
</example>
<example id="frdmkw38_ble_w_uart_gfsk_freertos" name="ble_w_uart_gfsk_freertos" brief="The ble w_uart application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Hybrid Bluetooth Generic FSK demo." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/hybrid/ble_w_uart_gfsk/freertos" path="boards/frdmkw38/wireless_examples/hybrid/ble_w_uart_gfsk/freertos">
<external path="boards/frdmkw38/wireless_examples/hybrid/ble_w_uart_gfsk/freertos" type="xml">
<files mask="ble_w_uart_gfsk_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_blood_pressure_sensor_bm" name="blood_pressure_sensor_bm" brief="The BLE blood pressure sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Blood Pressure Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/bps/bm" path="boards/frdmkw38/wireless_examples/bluetooth/bps/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/bps/bm" type="xml">
<files mask="blood_pressure_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_blood_pressure_sensor_freertos" name="blood_pressure_sensor_freertos" brief="The BLE blood pressure sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Blood Pressure Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/bps/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/bps/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/bps/freertos" type="xml">
<files mask="blood_pressure_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_bootloader_fsci" name="bootloader_fsci" brief="Framework bootloader otap unitility." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/framework/bootloader_fsci/bm" path="boards/frdmkw38/wireless_examples/framework/bootloader_fsci/bm">
<external path="boards/frdmkw38/wireless_examples/framework/bootloader_fsci/bm" type="xml">
<files mask="bootloader_fsci.xml"/>
</external>
</example>
<example id="frdmkw38_bootloader_otap" name="bootloader_otap" brief="Framework bootloader otap unitility." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/framework/bootloader_otap/bm" path="boards/frdmkw38/wireless_examples/framework/bootloader_otap/bm">
<external path="boards/frdmkw38/wireless_examples/framework/bootloader_otap/bm" type="xml">
<files mask="bootloader_otap.xml"/>
</external>
</example>
<example id="frdmkw38_bubble" name="bubble" brief="The bubble level demo demonstrates basic usage of the on-board accelerometer to implement a bubble level. A bubble level utilizes two axes to visually show deviation from a level plane (0 degrees) on a given axis." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/bubble">
<external path="boards/frdmkw38/demo_apps/bubble" type="xml">
<files mask="bubble.xml"/>
</external>
</example>
<example id="frdmkw38_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="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/bubble_peripheral">
<external path="boards/frdmkw38/demo_apps/bubble_peripheral" type="xml">
<files mask="bubble_peripheral.xml"/>
</external>
</example>
<example id="frdmkw38_cmp_interrupt" name="cmp_interrupt" brief="The CMP interrupt Example shows how to use interrupt with CMP driver.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user-defined channel's voltage crosses the internal DAC's value. The change ofcomparator's output would generate the falling and rising edge events with their interrupts enabled. When any CMP interrupt happens, the CMP's ISR would turn on the LED light if detecting the output's rising edge, or turn off it whendetecting the output's falling edge." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/cmp" path="boards/frdmkw38/driver_examples/cmp/interrupt">
<external path="boards/frdmkw38/driver_examples/cmp/interrupt" type="xml">
<files mask="cmp_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_cmp_polling" name="cmp_polling" brief="The CMP polling Example shows the simplest way to use CMP driver and help user with a quick start.In this example, user should indicate an input channel to capture a voltage signal (can be controlled by user) as the CMP's positive channel input. On the negative side, the internal 6-bit DAC is used to generate the fixed voltage abouthalf value of reference voltage.When running the project, change the input voltage of user-defined channel, then the comparator's output would changebetween logic one and zero when the user's voltage crosses the internal DAC's value. The endless loop in main() functionwould detect the logic value of comparator's output, and change the LED. The LED would be turned on when the compareoutput is logic one, or turned off when zero." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/cmp" path="boards/frdmkw38/driver_examples/cmp/polling">
<external path="boards/frdmkw38/driver_examples/cmp/polling" type="xml">
<files mask="cmp_polling.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_dspi_edma_b2b_transfer_master" name="cmsis_dspi_edma_b2b_transfer_master" brief="The dspi_edma_b2b_transfer example shows how to use DSPI CMSIS driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in edma . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/dspi" path="boards/frdmkw38/cmsis_driver_examples/dspi/edma_b2b_transfer/master">
<external path="boards/frdmkw38/cmsis_driver_examples/dspi/edma_b2b_transfer/master" type="xml">
<files mask="cmsis_dspi_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_dspi_edma_b2b_transfer_slave" name="cmsis_dspi_edma_b2b_transfer_slave" brief="The dspi_edma_b2b_transfer example shows how to use DSPI CMSIS driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in edma . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/dspi" path="boards/frdmkw38/cmsis_driver_examples/dspi/edma_b2b_transfer/slave">
<external path="boards/frdmkw38/cmsis_driver_examples/dspi/edma_b2b_transfer/slave" type="xml">
<files mask="cmsis_dspi_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_dspi_int_b2b_transfer_master" name="cmsis_dspi_int_b2b_transfer_master" brief="The dspi_int_b2b_transfer example shows how to use DSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_int_b2b_transfer_master.c' includes the DSPI master code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/dspi" path="boards/frdmkw38/cmsis_driver_examples/dspi/int_b2b_transfer/master">
<external path="boards/frdmkw38/cmsis_driver_examples/dspi/int_b2b_transfer/master" type="xml">
<files mask="cmsis_dspi_int_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_dspi_int_b2b_transfer_slave" name="cmsis_dspi_int_b2b_transfer_slave" brief="The dspi_int_b2b_transfer example shows how to use DSPI CMSIS driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_int_b2b_transfer_slave.c' includes the DSPI slave code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . " toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/dspi" path="boards/frdmkw38/cmsis_driver_examples/dspi/int_b2b_transfer/slave">
<external path="boards/frdmkw38/cmsis_driver_examples/dspi/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_dspi_int_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_i2c_read_accel_value_transfer" name="cmsis_i2c_read_accel_value_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_read_accel_value example shows how to use CMSIS I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/i2c" path="boards/frdmkw38/cmsis_driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmkw38/cmsis_driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="cmsis_i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_lpuart_edma_transfer" name="cmsis_lpuart_edma_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_edma_transfer example shows how to use uart cmsis driver with EDMA:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpuart" path="boards/frdmkw38/cmsis_driver_examples/lpuart/edma_transfer">
<external path="boards/frdmkw38/cmsis_driver_examples/lpuart/edma_transfer" type="xml">
<files mask="cmsis_lpuart_edma_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_cmsis_lpuart_interrupt_transfer" name="cmsis_lpuart_interrupt_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_interrupt_transfer example shows how to use uart cmsis driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="mcuxpresso" compiler="compiler_gcc" category="cmsis_driver_examples/lpuart" path="boards/frdmkw38/cmsis_driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmkw38/cmsis_driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="cmsis_lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_cmt" name="cmt" brief="The cmt example shows the simplest way to use CMT driver.In this example, the CMT is work as Time mode and used to modulation 11 bit numbers of data.The CMT is configured to generate a 40000hz carrier generator signal through a modulator gateconfigured with different mark/space time period to represent bit 1 and bit 0. The modulated data rate is 9600.Note, The end of cycle interrupt provides a means for the user to reload new mark/space valuesinto the modulator data registers. Modulator data register updates will take effect at the end of the current modulation cycle. The CMT internal down-counter and space period register areupdated at the end of every modulation cycle, irrespective of interrupt handling and the stateof the interrupt. so please make sure the IRQ handler process is shorter than the modulationcycle to ensure the new mark/space counter is prepared before each end of modulation cycle." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkw38/driver_examples/cmt">
<external path="boards/frdmkw38/driver_examples/cmt" type="xml">
<files mask="cmt.xml"/>
</external>
</example>
<example id="frdmkw38_connectivity_test_bm" name="connectivity_test_bm" brief="The connectivity test application is a simple demonstration program based on the MCUXpresso SDK.After power on, the board will start flashing all LEDs and will print the application logo into a serial port terminal, signalling an idle state.To start the application the [ENTER] key on the keyboard. Then follow the onscreen instructions to configure and run available tests." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/connectivity_test/bm" path="boards/frdmkw38/wireless_examples/genfsk/connectivity_test/bm">
<external path="boards/frdmkw38/wireless_examples/genfsk/connectivity_test/bm" type="xml">
<files mask="connectivity_test_bm.xml"/>
</external>
</example>
<example id="frdmkw38_connectivity_test_freertos" name="connectivity_test_freertos" brief="The connectivity test application is a simple demonstration program based on the MCUXpresso SDK.After power on, the board will start flashing all LEDs and will print the application logo into a serial port terminal, signalling an idle state.To start the application the [ENTER] key on the keyboard. Then follow the onscreen instructions to configure and run available tests." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/connectivity_test/freertos" path="boards/frdmkw38/wireless_examples/genfsk/connectivity_test/freertos">
<external path="boards/frdmkw38/wireless_examples/genfsk/connectivity_test/freertos" type="xml">
<files mask="connectivity_test_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_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="mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkw38/driver_examples/cop">
<external path="boards/frdmkw38/driver_examples/cop" type="xml">
<files mask="cop.xml"/>
</external>
</example>
<example id="frdmkw38_cycling_power_sensor_bm" name="cycling_power_sensor_bm" brief="The BLE cycling power sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Cycling Power Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/cycl_pwrs/bm" path="boards/frdmkw38/wireless_examples/bluetooth/cycl_pwrs/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/cycl_pwrs/bm" type="xml">
<files mask="cycling_power_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_cycling_power_sensor_freertos" name="cycling_power_sensor_freertos" brief="The BLE cycling power sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Cycling Power Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/cycl_pwrs/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/cycl_pwrs/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/cycl_pwrs/freertos" type="xml">
<files mask="cycling_power_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_cycling_speed_cadence_sensor_bm" name="cycling_speed_cadence_sensor_bm" brief="The BLE cycling speed cadence sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Cycling Speed and Cadence Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/cycl_scs/bm" path="boards/frdmkw38/wireless_examples/bluetooth/cycl_scs/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/cycl_scs/bm" type="xml">
<files mask="cycling_speed_cadence_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_cycling_speed_cadence_sensor_freertos" name="cycling_speed_cadence_sensor_freertos" brief="The BLE cycling speed cadence sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Cycling Speed and Cadence Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/cycl_scs/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/cycl_scs/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/cycl_scs/freertos" type="xml">
<files mask="cycling_speed_cadence_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_edma_b2b_transfer_master" name="dspi_edma_b2b_transfer_master" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/edma_b2b_transfer/master">
<external path="boards/frdmkw38/driver_examples/dspi/edma_b2b_transfer/master" type="xml">
<files mask="dspi_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_edma_b2b_transfer_slave" name="dspi_edma_b2b_transfer_slave" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/edma_b2b_transfer/slave">
<external path="boards/frdmkw38/driver_examples/dspi/edma_b2b_transfer/slave" type="xml">
<files mask="dspi_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_interrupt" name="dspi_interrupt" brief="The dspi_interrupt example shows how to use DSPI driver in interrupt way:In this example , one dspi instance used as DSPI master and another dspi instance used as DSPI slave in the same board.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/interrupt">
<external path="boards/frdmkw38/driver_examples/dspi/interrupt" type="xml">
<files mask="dspi_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_interrupt_b2b_master" name="dspi_interrupt_b2b_master" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_master.c' includes the DSPI master code.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b/master">
<external path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b/master" type="xml">
<files mask="dspi_interrupt_b2b_master.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_interrupt_b2b_slave" name="dspi_interrupt_b2b_slave" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_slave.c' includes the DSPI slave code.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b/slave">
<external path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b/slave" type="xml">
<files mask="dspi_interrupt_b2b_slave.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_interrupt_b2b_transfer_master" name="dspi_interrupt_b2b_transfer_master" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_master.c' includes the DSPI master code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b_transfer/master">
<external path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b_transfer/master" type="xml">
<files mask="dspi_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_interrupt_b2b_transfer_slave" name="dspi_interrupt_b2b_transfer_slave" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_slave.c' includes the DSPI slave code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b_transfer/slave">
<external path="boards/frdmkw38/driver_examples/dspi/interrupt_b2b_transfer/slave" type="xml">
<files mask="dspi_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_polling_b2b_transfer_master" name="dspi_polling_b2b_transfer_master" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/polling_b2b_transfer/master">
<external path="boards/frdmkw38/driver_examples/dspi/polling_b2b_transfer/master" type="xml">
<files mask="dspi_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="frdmkw38_dspi_polling_b2b_transfer_slave" name="dspi_polling_b2b_transfer_slave" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/frdmkw38/driver_examples/dspi/polling_b2b_transfer/slave">
<external path="boards/frdmkw38/driver_examples/dspi/polling_b2b_transfer/slave" type="xml">
<files mask="dspi_polling_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="frdmkw38_ecompass" name="ecompass" brief="The E-Compass demo application demonstrates the use of the FXOS8700 sensor. The tilt-compensated algorithm calculatesall three angles (pitch, roll, and yaw or compass heading)." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/ecompass">
<external path="boards/frdmkw38/demo_apps/ecompass" type="xml">
<files mask="ecompass.xml"/>
</external>
</example>
<example id="frdmkw38_edma_memory_to_memory" name="edma_memory_to_memory" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It excuates one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/edma" path="boards/frdmkw38/driver_examples/edma/memory_to_memory">
<external path="boards/frdmkw38/driver_examples/edma/memory_to_memory" type="xml">
<files mask="edma_memory_to_memory.xml"/>
</external>
</example>
<example id="frdmkw38_edma_scatter_gather" name="edma_scatter_gather" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It excuates one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/edma" path="boards/frdmkw38/driver_examples/edma/scatter_gather">
<external path="boards/frdmkw38/driver_examples/edma/scatter_gather" type="xml">
<files mask="edma_scatter_gather.xml"/>
</external>
</example>
<example id="frdmkw38_flashloader" name="flashloader" brief="The flashloader is a bootloader that executes from target RAM memory on the platform. The bootloader is a configurable flash programming utility that operates over a serial connection on MCU devices. It enables quick and easy programming of MCU devices through the entire product life cycle, including application development, final product manufacturing, and more.Host-side command line and GUI tools are available to communicate with the bootloader. Users can utilize host tools to upload and/or download application code via the bootloader." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples" path="boards/frdmkw38/bootloader_examples/flashloader">
<external path="boards/frdmkw38/bootloader_examples/flashloader" type="xml">
<files mask="flashloader.xml"/>
</external>
</example>
<example id="frdmkw38_flashloader_loader" name="flashloader_loader" brief="The flashloader_loader is a bootstrap loader that executes from flash memory on either the Freedom or Tower platform. This loader copies an image of the flashloader into RAM, then executes the flashloader from RAM. The flashloader_loader project uses the output of the flashloader build to create the flashloader image to load into RAM. Therefore, the flashloader project must be built before building the flashloader_loader project. Also, install Python27 for successful flashloader image generation." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples" path="boards/frdmkw38/bootloader_examples/flashloader_loader">
<external path="boards/frdmkw38/bootloader_examples/flashloader_loader" type="xml">
<files mask="flashloader_loader.xml"/>
</external>
</example>
<example id="frdmkw38_flexcan_interrupt_transfer" name="flexcan_interrupt_transfer" brief="The flexcan_interrupt example shows how to use FlexCAN driver in none-blocking interrupt way:In this example, 2 boards are connected through CAN bus. Endpoint A(board A) send a CAN Message toEndpoint B(board B) when user press space key in terminal. Endpoint B receive the message, printthe message content to terminal and echo back the message. Endpoint A will increase the receivedmessage and waiting for the next transmission of the user initiated." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexcan" path="boards/frdmkw38/driver_examples/flexcan/interrupt_transfer">
<external path="boards/frdmkw38/driver_examples/flexcan/interrupt_transfer" type="xml">
<files mask="flexcan_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_flexcan_loopback" name="flexcan_loopback" brief="The flexcan_loopback_functional example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrouth internal loopback interconnect and print out the Message payload to terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexcan" path="boards/frdmkw38/driver_examples/flexcan/loopback">
<external path="boards/frdmkw38/driver_examples/flexcan/loopback" type="xml">
<files mask="flexcan_loopback.xml"/>
</external>
</example>
<example id="frdmkw38_flexcan_loopback_edma_transfer" name="flexcan_loopback_edma_transfer" brief="The flexcan_loopback_edma example shows how to use the EDMA version transactional driver to receiveCAN Message from Rx FIFO:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Tx Message Buffer and also setup Rx FIFO. After that, the example will send 4 CAN Messagesfrom Tx Message Buffer to Rx FIFO through internal loopback interconnect and read them out usingEDMA version FlexCAN transactional driver. The Sent and received message will be print out to terminalat last." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexcan" path="boards/frdmkw38/driver_examples/flexcan/loopback_edma_transfer">
<external path="boards/frdmkw38/driver_examples/flexcan/loopback_edma_transfer" type="xml">
<files mask="flexcan_loopback_edma_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_flexcan_loopback_transfer" name="flexcan_loopback_transfer" brief="The flexcan_loopback example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrough internal loopback interconnect and print out the Message payload to terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flexcan" path="boards/frdmkw38/driver_examples/flexcan/loopback_transfer">
<external path="boards/frdmkw38/driver_examples/flexcan/loopback_transfer" type="xml">
<files mask="flexcan_loopback_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_flexnvm_dflash" name="flexnvm_dflash" brief="The flexnvm_dflash example shows how to use flash driver to operate data flash:" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmkw38/driver_examples/flash/flexnvm_dflash">
<external path="boards/frdmkw38/driver_examples/flash/flexnvm_dflash" type="xml">
<files mask="flexnvm_dflash.xml"/>
</external>
</example>
<example id="frdmkw38_flexnvm_eeprom" name="flexnvm_eeprom" brief="The flexnvm_eeprom example shows how to use flash driver to operate eeprom:" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmkw38/driver_examples/flash/flexnvm_eeprom">
<external path="boards/frdmkw38/driver_examples/flash/flexnvm_eeprom" type="xml">
<files mask="flexnvm_eeprom.xml"/>
</external>
</example>
<example id="frdmkw38_flexnvm_flexram" name="flexnvm_flexram" brief="The flexnvm_flexram example shows how to use flash driver to operate eeprom:" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmkw38/driver_examples/flash/flexnvm_flexram">
<external path="boards/frdmkw38/driver_examples/flash/flexnvm_flexram" type="xml">
<files mask="flexnvm_flexram.xml"/>
</external>
</example>
<example id="frdmkw38_freedom_bootloader" name="freedom_bootloader" brief="The freedom_bootloader is a bootloader that executes from target flash memory on the Freedom platform. The bootloader is a configurable flash programming utility that operates over a serial connection on MCU devices. It enables quick and easy programming of MCU devices through the entire product life cycle, including application development, final product manufacturing, and more.Host-side command line and GUI tools are available to communicate with the bootloader. Users can utilize host tools to upload and/or download application code via the bootloader." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples" path="boards/frdmkw38/bootloader_examples/freedom_bootloader">
<external path="boards/frdmkw38/bootloader_examples/freedom_bootloader" type="xml">
<files mask="freedom_bootloader.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_dspi" name="freertos_dspi" brief="The freertos_dspi example shows how to use DSPI driver in FreeRTOS:In this example , one dspi instance used as DSPI master with blocking and another dspi instance used as DSPI slave .1. DSPI master sends/receives data using task blocking calls to/from DSPI slave. (DSPI Slave uses interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_dspi">
<external path="boards/frdmkw38/rtos_examples/freertos_dspi" type="xml">
<files mask="freertos_dspi.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_event" name="freertos_event" brief="This document explains the freertos_event example. It shows how task waits for an event (defined setof bits in event group). This event can be set by any other process or interrupt in the system.The example application creates three tasks. Two write tasks write_task_1 and write_task_2continuously setting event bit 0 and bit 1.Read_task is waiting for any event bit and printing actual state on console. Event bits areautomatically cleared after read task is entered.Three possible states can occurre:Both bits are set.zBit B0 is set.Bit B1 is set." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_event">
<external path="boards/frdmkw38/rtos_examples/freertos_event" type="xml">
<files mask="freertos_event.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_generic" name="freertos_generic" brief="This document explains the freertos_generic example. It is based on code FreeRTOS documentation fromhttp://www.freertos.org/Hardware-independent-RTOS-example.html. It shows combination of severaltasks with queue, software timer, tick hook and semaphore.The example application creates three tasks. The prvQueueSendTask periodically sending data toxQueue queue. The prvQueueReceiveTask is waiting for incoming message and counting number ofreceived messages. Task prvEventSemaphoreTask is waiting for xEventSemaphore semaphore given fromvApplicationTickHook. Tick hook give semaphore every 500 ms.Other hook types used for RTOS and resource statistics are also demonstrated in example:* vApplicationIdleHook* vApplicationStackOverflowHook* vApplicationMallocFailedHook" toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_generic">
<external path="boards/frdmkw38/rtos_examples/freertos_generic" type="xml">
<files mask="freertos_generic.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_hello" name="freertos_hello" brief="The Hello World project is a simple demonstration program that uses the SDK UART drivere incombination with FreeRTOS. The purpose of this demo is to show how to use the debug console and toprovide a simple project for debugging and further development.The example application creates one task called hello_task. This task print "Hello world." messagevia debug console utility and suspend itself." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_hello">
<external path="boards/frdmkw38/rtos_examples/freertos_hello" type="xml">
<files mask="freertos_hello.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_i2c" name="freertos_i2c" brief="The freertos_i2c example shows an application using RTOS tasks with I2C driver:The example supports 2 different connections:On board connection and board to board connection.With one board connection, 2 I2C instances of the same board are used. One i2c instance used as I2C master and another I2C instance used as I2C slave . Default settings in freertos_i2c.c (in folder boards/<board>/rtos_examples/freertos_i2c) is applied. Two tasks are created. One task is associated with an I2C master operation and another task deals with I2C slave operation. 1. I2C master task sends data to I2C slave task. 2. I2C master task reads data sent back from I2C slave task. The transmit data and the receive data of both I2C master task and I2C slave task are printed out on terminal.With board to board connection, one I2C instance on one board is used as I2C master and the I2C instance on other board is used as I2C slave. Tasks are created to run on each board to handle I2C communication. File freertos_i2c.c should have following definitions: #define EXAMPLE_CONNECT_I2C BOARD_TO_BOARD For board used as I2C master: #define I2C_MASTER_SLAVE isMASTER For board used as I2C slave: #define I2C_MASTER_SLAVE isSLAVE" toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_i2c">
<external path="boards/frdmkw38/rtos_examples/freertos_i2c" type="xml">
<files mask="freertos_i2c.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_lpuart" name="freertos_lpuart" brief="The LPUART example for FreeRTOS demonstrates the possibility to use the LPUART driver in the RTOS.The example uses single instance of LPUART IP and writes string into, then reads back chars.After every 4B received, these are sent back on LPUART." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_lpuart">
<external path="boards/frdmkw38/rtos_examples/freertos_lpuart" type="xml">
<files mask="freertos_lpuart.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_mutex" name="freertos_mutex" brief="This document explains the freertos_mutex example. It shows how mutex manage access to commonresource (terminal output).The example application creates two identical instances of write_task. Each task will lock the mutexbefore printing and unlock it after printing to ensure that the outputs from tasks are not mixedtogether.The test_task accept output message during creation as function parameter. Output message have twoparts. If xMutex is unlocked, the write_task_1 acquire xMutex and print first part of message. Thenrescheduling is performed. In this moment scheduler check if some other task could run, but secondtask write_task+_2 is blocked because xMutex is already locked by first write task. The firstwrite_task_1 continue from last point by printing of second message part. Finaly the xMutex isunlocked and second instance of write_task_2 is executed." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_mutex">
<external path="boards/frdmkw38/rtos_examples/freertos_mutex" type="xml">
<files mask="freertos_mutex.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_percepio_snapshot" name="freertos_percepio_snapshot" brief="Percepio_snapshot demo shows the basic capabilities of Percepio tool.Required Segger software - J-Link Software and Documentation Pack ( https://www.segger.com/downloads/jlink ) - J-Link OpenSDA - Board-Specific Firmwares ( https://www.segger.com/downloads/jlink ) - Tracealyzer for FreeRTOS ( http://percepio.com/download/ )Demo requires JLink connected. The JLink can be external probe or on board SDA debugger.In case of SDA debugger you have to change firmware to J-Link OpenSDA by holding board RESET button while power up board. The board is then detected as USB mass storage device and it's required to copy the .bin firmware to the device. When it's done you have to reset the board once more." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples/visualization" path="boards/frdmkw38/rtos_examples/visualization/freertos_percepio_snapshot">
<external path="boards/frdmkw38/rtos_examples/visualization/freertos_percepio_snapshot" type="xml">
<files mask="freertos_percepio_snapshot.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_queue" name="freertos_queue" brief="This document explains the freertos_queue example. This example introduce simple logging mechanismbased on message passing.Example could be devided in two parts. First part is logger. It contain three tasks:log_add().....Add new message into the log. Call xQueueSend function to pass new message into message queue.log_init()....Initialize logger (create logging task and message queue log_queue).log_task()....Task responsible for printing of log output.Second part is application of this simple logging mechanism. Each of two tasks write_task_1 andwrite_task_2 print 5 messages into log." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_queue">
<external path="boards/frdmkw38/rtos_examples/freertos_queue" type="xml">
<files mask="freertos_queue.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_segger_sysview" name="freertos_segger_sysview" brief="Segger Sysview demo shows the basic capabilities of Segger System Viewer tool.Required software: - J-Link Software and Documentation Pack - SystemView - Real-time analysis and visualization - J-Link OpenSDA - Board-Specific Firmwarescan be downloaded from https://www.segger.com/downloads/jlinkDemo requires JLink connected. The JLink can be external probe or on board SDA debugger.In case of SDA debugger you have to change firmware to J-Link OpenSDA by holding board RESET button while power up board. The board is then detected as USB mass storage device and it's required to copy the .bin firmware to the device. When it's done you have to reset the board once more." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples/visualization" path="boards/frdmkw38/rtos_examples/visualization/freertos_segger_sysview">
<external path="boards/frdmkw38/rtos_examples/visualization/freertos_segger_sysview" type="xml">
<files mask="freertos_segger_sysview.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_sem" name="freertos_sem" brief="This document explains the freertos_sem example, what to expect when running it and a briefintroduction to the API. The freertos_sem example code shows how semaphores works. Two differenttasks are synchronized in bilateral rendezvous model.The example uses four tasks. One producer_task and three consumer_tasks. The producer_task starts bycreating of two semaphores (xSemaphore_producer and xSemaphore_consumer). These semaphores controlaccess to virtual item. The synchronization is based on bilateral rendezvous pattern. Both ofconsumer and producer must be prepared to enable transaction." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_sem">
<external path="boards/frdmkw38/rtos_examples/freertos_sem" type="xml">
<files mask="freertos_sem.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_sem_static" name="freertos_sem_static" brief="This document explains the freertos_sem example, what to expect when running it and a briefintroduction to the API. The freertos_sem example code shows how semaphores works. Two differenttasks are synchronized in bilateral rendezvous model.The example uses four tasks. One producer_task and three consumer_tasks. The producer_task starts bycreating of two semaphores (xSemaphore_producer and xSemaphore_consumer). These semaphores controlaccess to virtual item. The synchronization is based on bilateral rendezvous pattern. Both ofconsumer and producer must be prepared to enable transaction." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_sem_static">
<external path="boards/frdmkw38/rtos_examples/freertos_sem_static" type="xml">
<files mask="freertos_sem_static.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_swtimer" name="freertos_swtimer" brief="This document explains the freertos_swtimer example. It shows usage of software timer and itscallback.The example application creates one software timer SwTimer. The timer's callback SwTimerCallback isperiodically executed and text "Tick." is printed to terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_swtimer">
<external path="boards/frdmkw38/rtos_examples/freertos_swtimer" type="xml">
<files mask="freertos_swtimer.xml"/>
</external>
</example>
<example id="frdmkw38_freertos_tickless" name="freertos_tickless" brief="This document explains the freertos_tickless example. It shows the CPU enter at sleep mode and then it is waked up by expired time delay that using GPT module." toolchain="mcuxpresso" compiler="compiler_gcc" category="rtos_examples" path="boards/frdmkw38/rtos_examples/freertos_tickless">
<external path="boards/frdmkw38/rtos_examples/freertos_tickless" type="xml">
<files mask="freertos_tickless.xml"/>
</external>
</example>
<example id="frdmkw38_glucose_sensor_bm" name="glucose_sensor_bm" brief="The BLE glucose sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Glucose Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/glucose_s/bm" path="boards/frdmkw38/wireless_examples/bluetooth/glucose_s/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/glucose_s/bm" type="xml">
<files mask="glucose_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_glucose_sensor_freertos" name="glucose_sensor_freertos" brief="The BLE glucose sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Glucose Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/glucose_s/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/glucose_s/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/glucose_s/freertos" type="xml">
<files mask="glucose_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_gpio_input_interrupt" name="gpio_input_interrupt" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example uses the software button to control/toggle the LED." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmkw38/driver_examples/gpio/input_interrupt">
<external path="boards/frdmkw38/driver_examples/gpio/input_interrupt" type="xml">
<files mask="gpio_input_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_gpio_led_output" name="gpio_led_output" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example take turns to shine the LED." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/gpio" path="boards/frdmkw38/driver_examples/gpio/led_output">
<external path="boards/frdmkw38/driver_examples/gpio/led_output" type="xml">
<files mask="gpio_led_output.xml"/>
</external>
</example>
<example id="frdmkw38_hci_black_box_bm" name="hci_black_box_bm" brief="The BLE hci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooh Low Energy HCI Black Box which can communicate over a serial interface.To use the pplication Test Tool 12 or any other application which supports the HCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hci_bb/bm" path="boards/frdmkw38/wireless_examples/bluetooth/hci_bb/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hci_bb/bm" type="xml">
<files mask="hci_black_box_bm.xml"/>
</external>
</example>
<example id="frdmkw38_hci_black_box_freertos" name="hci_black_box_freertos" brief="The BLE hci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooh Low Energy HCI Black Box which can communicate over a serial interface.To use the pplication Test Tool 12 or any other application which supports the HCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hci_bb/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/hci_bb/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hci_bb/freertos" type="xml">
<files mask="hci_black_box_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_health_thermometer_bm" name="health_thermometer_bm" brief="The BLE health thermometer application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Health Thermometer Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/health_t/bm" path="boards/frdmkw38/wireless_examples/bluetooth/health_t/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/health_t/bm" type="xml">
<files mask="health_thermometer_bm.xml"/>
</external>
</example>
<example id="frdmkw38_health_thermometer_freertos" name="health_thermometer_freertos" brief="The BLE health thermometer application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Health Thermometer Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/health_t/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/health_t/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/health_t/freertos" type="xml">
<files mask="health_thermometer_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_heart_rate_sensor_bm" name="heart_rate_sensor_bm" brief="The BLE heart rate sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Heart Rate Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hrs/bm" path="boards/frdmkw38/wireless_examples/bluetooth/hrs/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hrs/bm" type="xml">
<files mask="heart_rate_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_heart_rate_sensor_freertos" name="heart_rate_sensor_freertos" brief="The BLE heart rate sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Heart Rate Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hrs/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/hrs/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hrs/freertos" type="xml">
<files mask="heart_rate_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_hello_world" name="hello_world" brief="The Hello World demo application provides a sanity check for the new SDK build environments and board bring up. The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers. The purpose of this demo is toshow how to use the UART, and to provide a simple project for debugging and further development." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/hello_world">
<external path="boards/frdmkw38/demo_apps/hello_world" type="xml">
<files mask="hello_world.xml"/>
</external>
</example>
<example id="frdmkw38_hid_device_bm" name="hid_device_bm" brief="The BLE hid device application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based HID Service.To test the service the any mobile device which supports HID devices over BLE can be used." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hid_device/bm" path="boards/frdmkw38/wireless_examples/bluetooth/hid_device/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hid_device/bm" type="xml">
<files mask="hid_device_bm.xml"/>
</external>
</example>
<example id="frdmkw38_hid_device_freertos" name="hid_device_freertos" brief="The BLE hid device application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based HID Service.To test the service the any mobile device which supports HID devices over BLE can be used." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hid_device/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/hid_device/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hid_device/freertos" type="xml">
<files mask="hid_device_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_hid_host_bm" name="hid_host_bm" brief="The BLE hid host application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based HID Profile.This demo requires a serial port terminal application through a serial interface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hid_host/bm" path="boards/frdmkw38/wireless_examples/bluetooth/hid_host/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hid_host/bm" type="xml">
<files mask="hid_host_bm.xml"/>
</external>
</example>
<example id="frdmkw38_hid_host_freertos" name="hid_host_freertos" brief="The BLE hid host application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based HID Profile.This demo requires a serial port terminal application through a serial interface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/hid_host/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/hid_host/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/hid_host/freertos" type="xml">
<files mask="hid_host_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_hs_beacon_bm" name="hs_beacon_bm" brief="The hs beacon test application is a simple demonstration program based on the MCUXpresso SDK.It used to demo beacon feature." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/hs_beacon/bm" path="boards/frdmkw38/wireless_examples/genfsk/hs_beacon/bm">
<external path="boards/frdmkw38/wireless_examples/genfsk/hs_beacon/bm" type="xml">
<files mask="hs_beacon_bm.xml"/>
</external>
</example>
<example id="frdmkw38_hs_beacon_freertos" name="hs_beacon_freertos" brief="The hs beacon test application is a simple demonstration program based on the MCUXpresso SDK.It used to demo beacon feature." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/hs_beacon/freertos" path="boards/frdmkw38/wireless_examples/genfsk/hs_beacon/freertos">
<external path="boards/frdmkw38/wireless_examples/genfsk/hs_beacon/freertos" type="xml">
<files mask="hs_beacon_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_i2c_interrupt" name="i2c_interrupt" brief="The i2c_functional_interrupt example shows how to use I2C functional driver to build a interrupt based application:In this example , one i2c instance used as I2C master and another i2c instance used as I2C slave .1. I2C master send data to I2C slave in interrupt . (I2C Slave using interrupt to receive the data)2. I2C master read data from I2C slave in interrupt . (I2C Slave using interrupt to send the data)3. The example assumes that the connection is OK between master and slave, so there's NO error handling code." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkw38/driver_examples/i2c/interrupt">
<external path="boards/frdmkw38/driver_examples/i2c/interrupt" type="xml">
<files mask="i2c_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_i2c_read_accel_value_transfer" name="i2c_read_accel_value_transfer" brief="The i2c_read_accel_value example shows how to use I2C driver to communicate with an i2c device: 1. How to use the i2c driver to read a i2c device who_am_I register. 2. How to use the i2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/i2c" path="boards/frdmkw38/driver_examples/i2c/read_accel_value_transfer">
<external path="boards/frdmkw38/driver_examples/i2c/read_accel_value_transfer" type="xml">
<files mask="i2c_read_accel_value_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_led_demo_freedom_0000" name="led_demo_freedom_0000" brief="The led_demo_freedom_0000 is a led blinky application load at the beginning of the target flash memory on the Freedom platform. The led demo project is an example demo firmware applications used to demonstrate how the MCU bootloader can load and launch user applications." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples/demo_apps" path="boards/frdmkw38/bootloader_examples/demo_apps/led_demo_freedom_0000">
<external path="boards/frdmkw38/bootloader_examples/demo_apps/led_demo_freedom_0000" type="xml">
<files mask="led_demo_freedom_0000.xml"/>
</external>
</example>
<example id="frdmkw38_led_demo_freedom_a000" name="led_demo_freedom_a000" brief="The led_demo_freedom_a000 is a led blinky application load at offset 0xa000 of the target flash memory on the Freedom platform. The led demo project is an example demo firmware applications used to demonstrate how the MCU bootloader can load and launch user applications." toolchain="mcuxpresso" compiler="compiler_gcc" category="bootloader_examples/demo_apps" path="boards/frdmkw38/bootloader_examples/demo_apps/led_demo_freedom_a000">
<external path="boards/frdmkw38/bootloader_examples/demo_apps/led_demo_freedom_a000" type="xml">
<files mask="led_demo_freedom_a000.xml"/>
</external>
</example>
<example id="frdmkw38_lin_master" name="lin_master" brief="The lin_master demo application demonstrates how to use LIN bus signal transfer from master node.This demo application is expected to work with another LIN instance implemented as slave node on the other board. Master node repeatedly initializes transfer by generating frame header, master and slave then exchange response as signal represented by the character array. This demo uses auto-baudrate feature." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lin" path="boards/frdmkw38/driver_examples/lin/master">
<external path="boards/frdmkw38/driver_examples/lin/master" type="xml">
<files mask="lin_master.xml"/>
</external>
</example>
<example id="frdmkw38_lin_slave" name="lin_slave" brief="The lin_master demo application demonstrates how to use LIN bus signal transfer from slave node.This demo application is expected to work with another LIN instance implemented as master node on the other board. Slave is waiting for master to initialize the communication then exchange a response as signal represented by the character array. This demo uses auto-baudrate feature." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lin" path="boards/frdmkw38/driver_examples/lin/slave">
<external path="boards/frdmkw38/driver_examples/lin/slave" type="xml">
<files mask="lin_slave.xml"/>
</external>
</example>
<example id="frdmkw38_lin_stack_master" name="lin_stack_master" brief="The lin_stack_master demo is used to demonstrate how to use the lin stack as master node." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/lin_stack/master">
<external path="boards/frdmkw38/demo_apps/lin_stack/master" type="xml">
<files mask="lin_stack_master.xml"/>
</external>
</example>
<example id="frdmkw38_lin_stack_slave" name="lin_stack_slave" brief="The lin_stack_slave demo is used to demonstrate how to use the lin stack as slave node." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/lin_stack/slave">
<external path="boards/frdmkw38/demo_apps/lin_stack/slave" type="xml">
<files mask="lin_stack_slave.xml"/>
</external>
</example>
<example id="frdmkw38_location_and_navigation_client_bm" name="location_and_navigation_client_bm" brief="The BLE location and navigation client application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Location and Navigation Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/lnc/bm" path="boards/frdmkw38/wireless_examples/bluetooth/lnc/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/lnc/bm" type="xml">
<files mask="location_and_navigation_client_bm.xml"/>
</external>
</example>
<example id="frdmkw38_location_and_navigation_client_freertos" name="location_and_navigation_client_freertos" brief="The BLE location and navigation client application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Location and Navigation Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/lnc/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/lnc/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/lnc/freertos" type="xml">
<files mask="location_and_navigation_client_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_location_and_navigation_server_bm" name="location_and_navigation_server_bm" brief="The BLE location and navigation server application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Location and Navigation Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/lns/bm" path="boards/frdmkw38/wireless_examples/bluetooth/lns/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/lns/bm" type="xml">
<files mask="location_and_navigation_server_bm.xml"/>
</external>
</example>
<example id="frdmkw38_location_and_navigation_server_freertos" name="location_and_navigation_server_freertos" brief="The BLE location and navigation server application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Location and Navigation Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/lns/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/lns/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/lns/freertos" type="xml">
<files mask="location_and_navigation_server_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_lp_bm" name="lp_bm" brief="The lowpower slave reference design application provides a reference design application on a slave device optimized for lowpower. This application is based on the temperature sensor example and has all Bluetooth services that the temperature sensor offers." toolchain="mcuxpresso" compiler="compiler_gcc" category="reference_design/bluetooth/lp/bm" path="boards/frdmkw38/reference_design/bluetooth/lp/bm">
<external path="boards/frdmkw38/reference_design/bluetooth/lp/bm" type="xml">
<files mask="lp_bm.xml"/>
</external>
</example>
<example id="frdmkw38_lp_freertos" name="lp_freertos" brief="The lowpower slave reference design application provides a reference design application on a slave device optimized for lowpower. This application is based on the temperature sensor example and has all Bluetooth services that the temperature sensor offers." toolchain="mcuxpresso" compiler="compiler_gcc" category="reference_design/bluetooth/lp/freertos" path="boards/frdmkw38/reference_design/bluetooth/lp/freertos">
<external path="boards/frdmkw38/reference_design/bluetooth/lp/freertos" type="xml">
<files mask="lp_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_lp_master_bm" name="lp_master_bm" brief="The lowpower master reference design application provides a reference design application on a Master device (central) optimized for lowpower. This application is based on the temperature collector example and has all Bluetooth services that the temperature collector offers." toolchain="mcuxpresso" compiler="compiler_gcc" category="reference_design/bluetooth/lp_master/bm" path="boards/frdmkw38/reference_design/bluetooth/lp_master/bm">
<external path="boards/frdmkw38/reference_design/bluetooth/lp_master/bm" type="xml">
<files mask="lp_master_bm.xml"/>
</external>
</example>
<example id="frdmkw38_lp_master_freertos" name="lp_master_freertos" brief="The lowpower master reference design application provides a reference design application on a Master device (central) optimized for lowpower. This application is based on the temperature collector example and has all Bluetooth services that the temperature collector offers." toolchain="mcuxpresso" compiler="compiler_gcc" category="reference_design/bluetooth/lp_master/freertos" path="boards/frdmkw38/reference_design/bluetooth/lp_master/freertos">
<external path="boards/frdmkw38/reference_design/bluetooth/lp_master/freertos" type="xml">
<files mask="lp_master_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_lptmr" name="lptmr" brief="The LPTMR project is a simple demonstration program of the SDK LPTMR driver. It sets up the LPTMRhardware block to trigger a periodic interrupt after every 1 second. When the LPTMR interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkw38/driver_examples/lptmr">
<external path="boards/frdmkw38/driver_examples/lptmr" type="xml">
<files mask="lptmr.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_edma_rb_transfer" name="lpuart_edma_rb_transfer" brief="The lpuart_edma Ring Buffer Example project is to demonstrate usage of the KSDK lpuart driver." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/edma_rb_transfer">
<external path="boards/frdmkw38/driver_examples/lpuart/edma_rb_transfer" type="xml">
<files mask="lpuart_edma_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_edma_transfer" name="lpuart_edma_transfer" brief="The lpuart_edma Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/edma_transfer">
<external path="boards/frdmkw38/driver_examples/lpuart/edma_transfer" type="xml">
<files mask="lpuart_edma_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_interrupt" name="lpuart_interrupt" brief="The lpuart_functioncal_interrupt example shows how to use lpuart driver functionalAPI to receive data with interrupt method:In this example, one lpuart instance connect to PC, the board willsend back all characters that PC send to the board." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/interrupt">
<external path="boards/frdmkw38/driver_examples/lpuart/interrupt" type="xml">
<files mask="lpuart_interrupt.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_interrupt_rb_transfer" name="lpuart_interrupt_rb_transfer" brief="The lpuart_interrupt_ring_buffer Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/interrupt_rb_transfer">
<external path="boards/frdmkw38/driver_examples/lpuart/interrupt_rb_transfer" type="xml">
<files mask="lpuart_interrupt_rb_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_interrupt_transfer" name="lpuart_interrupt_transfer" brief="The lpuart_interrupt Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/interrupt_transfer">
<external path="boards/frdmkw38/driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="lpuart_interrupt_transfer.xml"/>
</external>
</example>
<example id="frdmkw38_lpuart_polling" name="lpuart_polling" brief="The lpuart_polling Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console instantly." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/lpuart" path="boards/frdmkw38/driver_examples/lpuart/polling">
<external path="boards/frdmkw38/driver_examples/lpuart/polling" type="xml">
<files mask="lpuart_polling.xml"/>
</external>
</example>
<example id="frdmkw38_ltc_aes" name="ltc_aes" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption sampledata using AES-CBC, AES-CCM, and XCBC-MAC algorithm." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ltc" path="boards/frdmkw38/driver_examples/ltc/aes">
<external path="boards/frdmkw38/driver_examples/ltc/aes" type="xml">
<files mask="ltc_aes.xml"/>
</external>
</example>
<example id="frdmkw38_ltc_aes_edma" name="ltc_aes_edma" brief="This project is a demonstration program that uses the KSDK software for encryption/decryption sample data using EDMA forAES-CBC algorithm." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/ltc" path="boards/frdmkw38/driver_examples/ltc/aes_edma">
<external path="boards/frdmkw38/driver_examples/ltc/aes_edma" type="xml">
<files mask="ltc_aes_edma.xml"/>
</external>
</example>
<example id="frdmkw38_mcg_fee_blpe" name="mcg_fee_blpe" brief="The fee_bple example shows how to use MCG driver to change from FEE mode to BLPE mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to Fee mode from default reset mode Change from FEE -> FBE -> BLPE Change back BLPE -> FBE -> FEE Get System clock in FEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mcg" path="boards/frdmkw38/driver_examples/mcg/fee_blpe">
<external path="boards/frdmkw38/driver_examples/mcg/fee_blpe" type="xml">
<files mask="mcg_fee_blpe.xml"/>
</external>
</example>
<example id="frdmkw38_mcg_fee_blpi" name="mcg_fee_blpi" brief="The fee_bpli example shows how to use MCG driver to change from FEE mode to BLPI mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to FEE mode from default reset mode Change from FEE -> FBI -> BLPI Change back BLPI -> FBI -> FEE Get System clock in FEE mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mcg" path="boards/frdmkw38/driver_examples/mcg/fee_blpi">
<external path="boards/frdmkw38/driver_examples/mcg/fee_blpi" type="xml">
<files mask="mcg_fee_blpi.xml"/>
</external>
</example>
<example id="frdmkw38_mcg_fei_blpi" name="mcg_fei_blpi" brief="The fei_bpli example shows how to use MCG driver to change from FEI mode to BLPI mode: 1. How to use the mode functions for MCG mode switch. 2. How to use the frequency functions to get current MCG frequency. 3. Work flow Boot to FEI mode from default reset mode Change mode FEI -> FBI -> BLPI Change back BLPE -> FBI -> FEI Get System clock in FEI mode to blink LEDIn this example, because the debug console's clock frequency may change,so the example running information is not output from debug console. Here theLED blinks to show that the example finished successfully." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/mcg" path="boards/frdmkw38/driver_examples/mcg/fei_blpi">
<external path="boards/frdmkw38/driver_examples/mcg/fei_blpi" type="xml">
<files mask="mcg_fei_blpi.xml"/>
</external>
</example>
<example id="frdmkw38_otap_client_att_bm" name="otap_client_att_bm" brief="The BLE otap client att application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otac_att/bm" path="boards/frdmkw38/wireless_examples/bluetooth/otac_att/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otac_att/bm" type="xml">
<files mask="otap_client_att_bm.xml"/>
</external>
</example>
<example id="frdmkw38_otap_client_att_freertos" name="otap_client_att_freertos" brief="The BLE otap client att application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otac_att/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/otac_att/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otac_att/freertos" type="xml">
<files mask="otap_client_att_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_otap_client_l2cap_credit_bm" name="otap_client_l2cap_credit_bm" brief="The BLE otap client l2cap credit application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otac_l2cap/bm" path="boards/frdmkw38/wireless_examples/bluetooth/otac_l2cap/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otac_l2cap/bm" type="xml">
<files mask="otap_client_l2cap_credit_bm.xml"/>
</external>
</example>
<example id="frdmkw38_otap_client_l2cap_credit_freertos" name="otap_client_l2cap_credit_freertos" brief="The BLE otap client l2cap credit application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otac_l2cap/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/otac_l2cap/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otac_l2cap/freertos" type="xml">
<files mask="otap_client_l2cap_credit_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_otap_server_bm" name="otap_server_bm" brief="The BLE otap server application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Profile.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otas/bm" path="boards/frdmkw38/wireless_examples/bluetooth/otas/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otas/bm" type="xml">
<files mask="otap_server_bm.xml"/>
</external>
</example>
<example id="frdmkw38_otap_server_freertos" name="otap_server_freertos" brief="The BLE otap server application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based OTAP Profile.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/otas/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/otas/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/otas/freertos" type="xml">
<files mask="otap_server_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_pflash" name="pflash" brief="The pflash example shows how to use flash driver to operate program flash:" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/flash" path="boards/frdmkw38/driver_examples/flash/pflash">
<external path="boards/frdmkw38/driver_examples/flash/pflash" type="xml">
<files mask="pflash.xml"/>
</external>
</example>
<example id="frdmkw38_pit" name="pit" brief="The PIT project is a simple demonstration program of the SDK PIT driver. It sets up the PIThardware block to trigger a periodic interrupt after every 1 second. When the PIT interrupt is triggereda message a printed on the UART terminal and an LED is toggled on the board." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkw38/driver_examples/pit">
<external path="boards/frdmkw38/driver_examples/pit" type="xml">
<files mask="pit.xml"/>
</external>
</example>
<example id="frdmkw38_power_manager" name="power_manager" brief="The Power manager demo application demonstrates the use of power modes in the KSDK. The demo use the notification mechanismand prints the power mode menu through the debug console, where the user can set the MCU to a specific power mode. The usercan also set the wakeup source by following the debug console prompts. The purpose of this demo is to demonstrate theimplementation of a power mode manager. The callback can be registered to the framework. If a power mode transition happens,the callback will be called and user can do something. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/power_manager">
<external path="boards/frdmkw38/demo_apps/power_manager" type="xml">
<files mask="power_manager.xml"/>
</external>
</example>
<example id="frdmkw38_power_mode_switch" name="power_mode_switch" brief="The Power mode switch demo application demonstrates the use of power modes in the KSDK. The demo prints the power mode menuthrough the debug console, where the user can set the MCU to a specific power mode. The user can also set the wakeupsource by following the debug console prompts. The purpose of this demo is to show how to switch between different power modes, and how to configure a wakeup source and wakeup the MCU from low power modes. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware. - Debug pins(e.g SWD_DIO) would consume addtional power, had better to disable related pins or disconnect them. " toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/power_mode_switch">
<external path="boards/frdmkw38/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch.xml"/>
</external>
</example>
<example id="frdmkw38_proximity_reporter_bm" name="proximity_reporter_bm" brief="The BLE proximity reporter application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Proximity Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/proxi_rep/bm" path="boards/frdmkw38/wireless_examples/bluetooth/proxi_rep/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/proxi_rep/bm" type="xml">
<files mask="proximity_reporter_bm.xml"/>
</external>
</example>
<example id="frdmkw38_proximity_reporter_freertos" name="proximity_reporter_freertos" brief="The BLE proximity reporter application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Proximity Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/proxi_rep/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/proxi_rep/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/proxi_rep/freertos" type="xml">
<files mask="proximity_reporter_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_pulse_oximeter_sensor_bm" name="pulse_oximeter_sensor_bm" brief="The BLE pulse oximeter sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Pulse Oximeter Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/pulse_o2_s/bm" path="boards/frdmkw38/wireless_examples/bluetooth/pulse_o2_s/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/pulse_o2_s/bm" type="xml">
<files mask="pulse_oximeter_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_pulse_oximeter_sensor_freertos" name="pulse_oximeter_sensor_freertos" brief="The BLE pulse oximeter sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Pulse Oximeter Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/pulse_o2_s/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/pulse_o2_s/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/pulse_o2_s/freertos" type="xml">
<files mask="pulse_oximeter_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_rtc" name="rtc" brief="The RTC project is a simple demonstration program of the SDK RTC driver. It sets up the RTChardware block to trigger an alarm after a user specified time period. The test will set the currentdate and time to a predefined value. The alarm will be set with reference to this predefined dateand time." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples" path="boards/frdmkw38/driver_examples/rtc">
<external path="boards/frdmkw38/driver_examples/rtc" type="xml">
<files mask="rtc.xml"/>
</external>
</example>
<example id="frdmkw38_rtc_func" name="rtc_func" brief="The RTC demo application demonstrates the important features of the RTC Module by using the RTC Peripheral Driver.The RTC demo supports the following features:- Calendar + Get the current date time with Year, Month, Day, Hour, Minute, and Second. + Set the current date time with Year, Month, Day, Hour, Minute, and Second.- Alarm + Set the alarm based on the current time. + Application prints a notification when the alarm expires.- Seconds interrupt + Use second interrupt function to display a digital time blink every second." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/rtc_func">
<external path="boards/frdmkw38/demo_apps/rtc_func" type="xml">
<files mask="rtc_func.xml"/>
</external>
</example>
<example id="frdmkw38_running_speed_cadence_sensor_bm" name="running_speed_cadence_sensor_bm" brief="The BLE running speed cadence sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Running Speed and Cadence Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/run_scs/bm" path="boards/frdmkw38/wireless_examples/bluetooth/run_scs/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/run_scs/bm" type="xml">
<files mask="running_speed_cadence_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_running_speed_cadence_sensor_freertos" name="running_speed_cadence_sensor_freertos" brief="The BLE running speed cadence sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Running Speed and Cadence Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/run_scs/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/run_scs/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/run_scs/freertos" type="xml">
<files mask="running_speed_cadence_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_shell" name="shell" brief="The Shell Demo application demonstrates to control Leds by commands." toolchain="mcuxpresso" compiler="compiler_gcc" category="demo_apps" path="boards/frdmkw38/demo_apps/shell">
<external path="boards/frdmkw38/demo_apps/shell" type="xml">
<files mask="shell.xml"/>
</external>
</example>
<example id="frdmkw38_temperature_collector_bm" name="temperature_collector_bm" brief="The BLE temperature collector application is a simple demonstration program based on the MCUXpresso SDK.This application implements a custom GATT based Temperature Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/temp_coll/bm" path="boards/frdmkw38/wireless_examples/bluetooth/temp_coll/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/temp_coll/bm" type="xml">
<files mask="temperature_collector_bm.xml"/>
</external>
</example>
<example id="frdmkw38_temperature_collector_freertos" name="temperature_collector_freertos" brief="The BLE temperature collector application is a simple demonstration program based on the MCUXpresso SDK.This application implements a custom GATT based Temperature Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/temp_coll/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/temp_coll/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/temp_coll/freertos" type="xml">
<files mask="temperature_collector_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_temperature_sensor_bm" name="temperature_sensor_bm" brief="The BLE temperature sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/temp_sens/bm" path="boards/frdmkw38/wireless_examples/bluetooth/temp_sens/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/temp_sens/bm" type="xml">
<files mask="temperature_sensor_bm.xml"/>
</external>
</example>
<example id="frdmkw38_temperature_sensor_freertos" name="temperature_sensor_freertos" brief="The BLE temperature sensor application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based Temperature Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/temp_sens/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/temp_sens/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/temp_sens/freertos" type="xml">
<files mask="temperature_sensor_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_combine_pwm" name="tpm_combine_pwm" brief="The TPM project is a demonstration program of generating a combined PWM signal by the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The example also show's the complementary mode of operationand deadtime insertion.On boards that have 2 LEDs connected to the TPM pins, the user will seea change in LED brightness if user enter different values.And if the board do not support LEDs to show, the outputs can be observed by oscilloscope." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/combine_pwm">
<external path="boards/frdmkw38/driver_examples/tpm/combine_pwm" type="xml">
<files mask="tpm_combine_pwm.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_dual_edge_capture" name="tpm_dual_edge_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's dual-edge capture feature.This feature is available only on certain SoC's.The example sets up a TPM channel-pair for dual-edge capture. Once the input signal is received,this example will print the capture values and period of the input signal on the terminal window." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/dual_edge_capture">
<external path="boards/frdmkw38/driver_examples/tpm/dual_edge_capture" type="xml">
<files mask="tpm_dual_edge_capture.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_input_capture" name="tpm_input_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's input capture feature.The example sets up a TPM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/input_capture">
<external path="boards/frdmkw38/driver_examples/tpm/input_capture" type="xml">
<files mask="tpm_input_capture.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_output_compare" name="tpm_output_compare" brief="The TPM project is a demonstration program of the SDK TPM driver's output compare feature.It sets up one TPM channel to toggle the output when a match occurs with the channel value. The usershould probe the TPM output with a oscilloscope to see the signal toggling." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/output_compare">
<external path="boards/frdmkw38/driver_examples/tpm/output_compare" type="xml">
<files mask="tpm_output_compare.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_pwm_twochannel" name="tpm_pwm_twochannel" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The PWM dutycycle on both channelsis manually updated. On boards that have an LED connected to the TPM pins, the user will seea change in LED brightness if user enter different values." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/pwm_twochannel">
<external path="boards/frdmkw38/driver_examples/tpm/pwm_twochannel" type="xml">
<files mask="tpm_pwm_twochannel.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_simple_pwm" name="tpm_simple_pwm" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output a center-aligned PWM signal. The PWM dutycycle is manually updated.On boards that have an LED connected to the TPM pins, the user will see a change in LEDbrightness if user enter different values." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/simple_pwm">
<external path="boards/frdmkw38/driver_examples/tpm/simple_pwm" type="xml">
<files mask="tpm_simple_pwm.xml"/>
</external>
</example>
<example id="frdmkw38_tpm_timer" name="tpm_timer" brief="The TPM project is a simple demonstration program of the SDK TPM driver to use TPM as a timer.It sets up the TPM hardware block to trigger an interrupt every 1 millisecond.When the TPM interrupt is triggered a message a printed on the UART terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/tpm" path="boards/frdmkw38/driver_examples/tpm/timer">
<external path="boards/frdmkw38/driver_examples/tpm/timer" type="xml">
<files mask="tpm_timer.xml"/>
</external>
</example>
<example id="frdmkw38_trng_random" name="trng_random" brief="The True Random Number Generator (TRNG) is a hardware accelerator module that generates a 512-bitentropy as needed by an entropy consuming module or by other post processing functions. The TRNGExample project is a demonstration program that uses the KSDK software to generate random numbersand prints them to the terminal." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/trng" path="boards/frdmkw38/driver_examples/trng/random">
<external path="boards/frdmkw38/driver_examples/trng/random" type="xml">
<files mask="trng_random.xml"/>
</external>
</example>
<example id="frdmkw38_vref_example" name="vref_example" brief="In this example, the adc16 module is initiealized and used to measure the VREF output voltage. So, it cannot use interal VREF as the reference voltage. Then, user should configure the VREF output pin as the ADC16's sample input. When running the project, it will firstly measure the VREF output voltage within the default (factory) trim value. Then, it will measure the VREF output voltage under different trim value." toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/vref" path="boards/frdmkw38/driver_examples/vref">
<external path="boards/frdmkw38/driver_examples/vref" type="xml">
<files mask="vref_example.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_power_pru_bm" name="wireless_power_pru_bm" brief="The BLE wireless power pru application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based A4WP Wireless Power Transfer Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_pwr_pru/bm" path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_pru/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_pru/bm" type="xml">
<files mask="wireless_power_pru_bm.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_power_pru_freertos" name="wireless_power_pru_freertos" brief="The BLE wireless power pru application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based A4WP Wireless Power Transfer Service.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_pwr_pru/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_pru/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_pru/freertos" type="xml">
<files mask="wireless_power_pru_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_power_ptu_bm" name="wireless_power_ptu_bm" brief="The BLE wireless power ptu application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based A4WP Wireless Power Transfer Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_pwr_ptu/bm" path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_ptu/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_ptu/bm" type="xml">
<files mask="wireless_power_ptu_bm.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_power_ptu_freertos" name="wireless_power_ptu_freertos" brief="The BLE wireless power ptu application is a simple demonstration program based on the MCUXpresso SDK.This application implements a GATT based A4WP Wireless Power Transfer Profile.To test the service/profile the Kinetis BLE Toolbox application can be used which is available for both Android and iOS." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_pwr_ptu/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_ptu/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_pwr_ptu/freertos" type="xml">
<files mask="wireless_power_ptu_freertos.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_uart_bm" name="wireless_uart_bm" brief="The BLE wireless uart application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based Wireless UART Profile that emulates UART over BLE.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_uart/bm" path="boards/frdmkw38/wireless_examples/bluetooth/w_uart/bm">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_uart/bm" type="xml">
<files mask="wireless_uart_bm.xml"/>
</external>
</example>
<example id="frdmkw38_wireless_uart_freertos" name="wireless_uart_freertos" brief="The BLE wireless uart application is a simple demonstration program based on the MCUXpresso SDK.The application implements a custom GATT based Wireless UART Profile that emulates UART over BLE.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/w_uart/freertos" path="boards/frdmkw38/wireless_examples/bluetooth/w_uart/freertos">
<external path="boards/frdmkw38/wireless_examples/bluetooth/w_uart/freertos" type="xml">
<files mask="wireless_uart_freertos.xml"/>
</external>
</example>
</examples>
</board>
<board id="usbkw38" name="USB-KW38" href="http://www.nxp.com/frdm-kw38" version="1.0.0" package="MKW37Z512VFT4">
<description>USB-KW38: Freedom Development Platform for Kinetis KW37, KW38, and KW39 MCUs</description>
<image path="docs/images" type="image">
<files mask="USB-KW38.gif"/>
</image>
<metadataSet>
<metadata key="html">
<specific>
<content>The USB-KW38 is a development platform enabled by the Kinetis W series KW39/38/37 family built on ARM Cortex-M0+ processor with integrated 2.4 GHz transceiver supporting Bluetooth Smart/Bluetooth Low Energy (BLE) v4.2, Generic FSK.The USB-KW38 is form-factor compatible with the Arduino R3 pin layout for more expansion options.</content>
</specific>
</metadata>
</metadataSet>
<examples>
<example id="usbkw38_ble_fsci_black_box_bm" name="ble_fsci_black_box_bm" brief="The BLE ble fsci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooth Low Energy Host Black Box which can communicate using the FSCI protocol over a serial interface.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_fscibb/bm" path="boards/usbkw38/wireless_examples/bluetooth/ble_fscibb/bm">
<external path="boards/usbkw38/wireless_examples/bluetooth/ble_fscibb/bm" type="xml">
<files mask="ble_fsci_black_box_bm.xml"/>
</external>
</example>
<example id="usbkw38_ble_fsci_black_box_freertos" name="ble_fsci_black_box_freertos" brief="The BLE ble fsci black box application is a simple demonstration program based on the MCUXpresso SDK.This application implements a Bluetooth Low Energy Host Black Box which can communicate using the FSCI protocol over a serial interface.To use the pplication Test Tool 12 or any other application which supports the FSCI protocol is required." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_fscibb/freertos" path="boards/usbkw38/wireless_examples/bluetooth/ble_fscibb/freertos">
<external path="boards/usbkw38/wireless_examples/bluetooth/ble_fscibb/freertos" type="xml">
<files mask="ble_fsci_black_box_freertos.xml"/>
</external>
</example>
<example id="usbkw38_ble_shell_bm" name="ble_shell_bm" brief="The BLE ble shell application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Bluetooth Low Energy Host with a shell inteface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_shell/bm" path="boards/usbkw38/wireless_examples/bluetooth/ble_shell/bm">
<external path="boards/usbkw38/wireless_examples/bluetooth/ble_shell/bm" type="xml">
<files mask="ble_shell_bm.xml"/>
</external>
</example>
<example id="usbkw38_ble_shell_freertos" name="ble_shell_freertos" brief="The BLE ble shell application is a simple demonstration program based on the MCUXpresso SDK.The application implements a Bluetooth Low Energy Host with a shell inteface." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/bluetooth/ble_shell/freertos" path="boards/usbkw38/wireless_examples/bluetooth/ble_shell/freertos">
<external path="boards/usbkw38/wireless_examples/bluetooth/ble_shell/freertos" type="xml">
<files mask="ble_shell_freertos.xml"/>
</external>
</example>
<example id="usbkw38_connectivity_test_bm" name="connectivity_test_bm" brief="The connectivity test application is a simple demonstration program based on the MCUXpresso SDK.After power on, the board will start flashing all LEDs and will print the application logo into a serial port terminal, signalling an idle state.To start the application the [ENTER] key on the keyboard. Then follow the onscreen instructions to configure and run available tests." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/connectivity_test/bm" path="boards/usbkw38/wireless_examples/genfsk/connectivity_test/bm">
<external path="boards/usbkw38/wireless_examples/genfsk/connectivity_test/bm" type="xml">
<files mask="connectivity_test_bm.xml"/>
</external>
</example>
<example id="usbkw38_connectivity_test_freertos" name="connectivity_test_freertos" brief="The connectivity test application is a simple demonstration program based on the MCUXpresso SDK.After power on, the board will start flashing all LEDs and will print the application logo into a serial port terminal, signalling an idle state.To start the application the [ENTER] key on the keyboard. Then follow the onscreen instructions to configure and run available tests." toolchain="mcuxpresso" compiler="compiler_gcc" category="wireless_examples/genfsk/connectivity_test/freertos" path="boards/usbkw38/wireless_examples/genfsk/connectivity_test/freertos">
<external path="boards/usbkw38/wireless_examples/genfsk/connectivity_test/freertos" type="xml">
<files mask="connectivity_test_freertos.xml"/>
</external>
</example>
<example id="usbkw38_dspi_edma_b2b_transfer_master" name="dspi_edma_b2b_transfer_master" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/edma_b2b_transfer/master">
<external path="boards/usbkw38/driver_examples/dspi/edma_b2b_transfer/master" type="xml">
<files mask="dspi_edma_b2b_transfer_master.xml"/>
</external>
</example>
<example id="usbkw38_dspi_edma_b2b_transfer_slave" name="dspi_edma_b2b_transfer_slave" brief="The dspi_edma_b2b_transfer example shows how to use DSPI driver in edma way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_edma_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in edma . (DSPI Slave using edma to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/edma_b2b_transfer/slave">
<external path="boards/usbkw38/driver_examples/dspi/edma_b2b_transfer/slave" type="xml">
<files mask="dspi_edma_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="usbkw38_dspi_interrupt_b2b_master" name="dspi_interrupt_b2b_master" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_master.c' includes the DSPI master code.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/interrupt_b2b/master">
<external path="boards/usbkw38/driver_examples/dspi/interrupt_b2b/master" type="xml">
<files mask="dspi_interrupt_b2b_master.xml"/>
</external>
</example>
<example id="usbkw38_dspi_interrupt_b2b_slave" name="dspi_interrupt_b2b_slave" brief="The dspi_interrupt_b2b example shows how to use DSPI driver in interrupt way:In this example , we need two boards , one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_slave.c' includes the DSPI slave code.This example does not use the transactional API in DSPI driver. It's a demonstration that how to use the interrupt in KSDK driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/interrupt_b2b/slave">
<external path="boards/usbkw38/driver_examples/dspi/interrupt_b2b/slave" type="xml">
<files mask="dspi_interrupt_b2b_slave.xml"/>
</external>
</example>
<example id="usbkw38_dspi_interrupt_b2b_transfer_master" name="dspi_interrupt_b2b_transfer_master" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_master.c' includes the DSPI master code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/interrupt_b2b_transfer/master">
<external path="boards/usbkw38/driver_examples/dspi/interrupt_b2b_transfer/master" type="xml">
<files mask="dspi_interrupt_b2b_transfer_master.xml"/>
</external>
</example>
<example id="usbkw38_dspi_interrupt_b2b_transfer_slave" name="dspi_interrupt_b2b_transfer_slave" brief="The dspi_interrupt_b2b_transfer example shows how to use DSPI driver in interrupt way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_interrupt_b2b_transfer_slave.c' includes the DSPI slave code.This example uses the transactional API in DSPI driver.1. DSPI master send/received data to/from DSPI slave in interrupt . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/interrupt_b2b_transfer/slave">
<external path="boards/usbkw38/driver_examples/dspi/interrupt_b2b_transfer/slave" type="xml">
<files mask="dspi_interrupt_b2b_transfer_slave.xml"/>
</external>
</example>
<example id="usbkw38_dspi_polling_b2b_transfer_master" name="dspi_polling_b2b_transfer_master" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_master.c' includes the DSPI master code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/polling_b2b_transfer/master">
<external path="boards/usbkw38/driver_examples/dspi/polling_b2b_transfer/master" type="xml">
<files mask="dspi_polling_b2b_transfer_master.xml"/>
</external>
</example>
<example id="usbkw38_dspi_polling_b2b_transfer_slave" name="dspi_polling_b2b_transfer_slave" brief="The dspi_polling_b2b_transfer example shows how to use DSPI driver in polling way:In this example , we need two boards, one board used as DSPI master and another board used as DSPI slave.The file 'dspi_polling_b2b_transfer_slave.c' includes the DSPI slave code.1. DSPI master send/received data to/from DSPI slave in polling . (DSPI Slave using interrupt to receive/send the data)" toolchain="mcuxpresso" compiler="compiler_gcc" category="driver_examples/dspi" path="boards/usbkw38/driver_examples/dspi/polling_b2b_transfer/slave">
<external path="boards/usbkw38/driver_examples/dspi/polling_b2b_transfer/slave" type="xml">
<files mask="dspi_polling_b2b_transfer_slave.xml"/>
</external>
</example>