-
Notifications
You must be signed in to change notification settings - Fork 24
/
MEK-MIMX8QX_manifest_v3_8.xml
5848 lines (5848 loc) · 364 KB
/
MEK-MIMX8QX_manifest_v3_8.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_MEK-MIMX8QX" name="MEK-MIMX8QX" brief="This is SDK version 2.9.0 manifest file. It describes the content of the MEK-MIMX8QX and additional settings for tools that support SDK version 2.9.0" format_version="3.8" api_version="2.0.0" configuration="5cc1c7de7f129072c6c29165bffffca6" xsi:schemaLocation="http://nxp.com/ksdk/2.0/ksdk_manifest_v3.0.xsd http://nxp.com/mcuxpresso/sdk/sdk_manifest_v3.8.xsd">
<!--Timestamp (UTC): 2021-01-16 00:21:13.652234-->
<!--This manifest is generated based on sdk repo commit: 3073e476325c80265f0c6d9a806af8fd0bfd767b-->
<defines>
<define name="CPU_$|package|" value=""/>
<define name="CPU_$|package|_$|core|" value=""/>
</defines>
<externalDefinitions>
<definition extID="com.crt.advproject.config.exe.debug"/>
<definition extID="com.crt.advproject.config.exe.release"/>
<definition extID="QSPI_FLASH_MIMX8QX6xxxFZ"/>
</externalDefinitions>
<ksdk id="MCUXpresso290" name="MCUXpresso290" version="2.9.0" revision="435 2021-01-15"/>
<compilers>
<compiler id="compiler_gcc" name="gcc" type="gcc"/>
<compiler id="compiler_iar" name="iar" type="iar"/>
</compilers>
<toolchainSettings/>
<toolchains>
<toolchain id="armgcc" name="GCC_ARM_Embedded" version="9.3.1" full_name="GCC ARM Embedded" compiler="compiler_gcc" type="armgcc" vendor="GCC ARM Embedded" vendor_url="http://launchpad.net/gcc-arm-embedded"/>
<toolchain id="iar" name="IAR_Embedded_Workbench_for_ARM" version="8.50.9" full_name="IAR Embedded Workbench for ARM" compiler="compiler_iar" type="iar" vendor="IAR Systems" vendor_url="http://www.iar.com"/>
</toolchains>
<boards>
<board id="mekmimx8qx" name="MEK-MIMX8QX" href="https://www.nxp.com/pip/MCIMX8QXP-CPU" version="1.0.0" package="MIMX8QX6AVLFZ">
<description>i.MX 8QuadXPlus Multisensory Enablement Kit (MEK)</description>
<image path="boards/mekmimx8qx" type="image">
<files mask="mekmimx8qx.png"/>
</image>
<examples>
<example id="mekmimx8qx_canfd_interrupt_transfer" name="canfd_interrupt_transfer" brief="The canfd_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/canfd" path="boards/mekmimx8qx/driver_examples/canfd/interrupt_transfer">
<external path="boards/mekmimx8qx/driver_examples/canfd/interrupt_transfer" type="xml">
<files mask="canfd_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_canfd_loopback" name="canfd_loopback" brief="The canfd_loopback_functional example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrouth internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/canfd" path="boards/mekmimx8qx/driver_examples/canfd/loopback">
<external path="boards/mekmimx8qx/driver_examples/canfd/loopback" type="xml">
<files mask="canfd_loopback_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_canfd_loopback_transfer" name="canfd_loopback_transfer" brief="The canfd_loopback example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrough internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/canfd" path="boards/mekmimx8qx/driver_examples/canfd/loopback_transfer">
<external path="boards/mekmimx8qx/driver_examples/canfd/loopback_transfer" type="xml">
<files mask="canfd_loopback_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_enet_txrx_transfer" name="cmsis_enet_txrx_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 method please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html. The cmsis_enet_transfer example shows how to use CMSIS ENET driver: In this example, the ENET transmits 20 number broadcast frames and will print the received frame. " toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/enet" path="boards/mekmimx8qx/cmsis_driver_examples/enet/txrx_transfer">
<external path="boards/mekmimx8qx/cmsis_driver_examples/enet/txrx_transfer" type="xml">
<files mask="cmsis_enet_txrx_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_lpi2c_edma_b2b_transfer_master" name="cmsis_lpi2c_edma_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_edma_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with EDMA:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpi2c" path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/edma_b2b_transfer/master">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/edma_b2b_transfer/master" type="xml">
<files mask="cmsis_lpi2c_edma_b2b_transfer_master_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_lpi2c_edma_b2b_transfer_slave" name="cmsis_lpi2c_edma_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_i2c_edma_b2b_transfer_master example shows how to use i2c driver as master to do board to board transfer with EDMA:In this example, one i2c instance as master and another i2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpi2c" path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/edma_b2b_transfer/slave">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/edma_b2b_transfer/slave" type="xml">
<files mask="cmsis_lpi2c_edma_b2b_transfer_slave_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_lpi2c_int_b2b_transfer_master" name="cmsis_lpi2c_int_b2b_transfer_master" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The lpi2c_int_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one lpi2c instance as master and another lpi2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpi2c" path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/int_b2b_transfer/master">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/int_b2b_transfer/master" type="xml">
<files mask="cmsis_lpi2c_int_b2b_transfer_master_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_lpi2c_int_b2b_transfer_slave" name="cmsis_lpi2c_int_b2b_transfer_slave" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The lpi2c_int_b2b_transfer_master example shows how to use CMSIS i2c driver as master to do board to board transfer with interrupt:In this example, one lpi2c instance as master and another lpi2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpi2c" path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/int_b2b_transfer/slave">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpi2c/int_b2b_transfer/slave" type="xml">
<files mask="cmsis_lpi2c_int_b2b_transfer_slave_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpuart" path="boards/mekmimx8qx/cmsis_driver_examples/lpuart/edma_transfer">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpuart/edma_transfer" type="xml">
<files mask="cmsis_lpuart_edma_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_cmsis_lpuart_interrupt_transfer" name="cmsis_lpuart_interrupt_transfer" brief="CMSIS-Driver defines generic peripheral driver interfaces for middleware making it reusable across a wide range of supported microcontroller devices. The API connects microcontroller peripherals with middleware that implements for example communication stacks, file systems, or graphic user interfaces. More information and usage methord please refer to http://www.keil.com/pack/doc/cmsis/Driver/html/index.html.The cmsis_uart_interrupt_transfer example shows how to use uart cmsis driver in interrupt way:In this example, one uart instance connect to PC through uart, the board willsend back all characters that PC send to the board.Note: The example echo every 8 characters, so input 8 characters every time." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="cmsis_driver_examples/lpuart" path="boards/mekmimx8qx/cmsis_driver_examples/lpuart/interrupt_transfer">
<external path="boards/mekmimx8qx/cmsis_driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="cmsis_lpuart_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dma3_memory_to_memory" name="dma3_memory_to_memory" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It executes one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/edma" path="boards/mekmimx8qx/driver_examples/edma/memory_to_memory">
<external path="boards/mekmimx8qx/driver_examples/edma/memory_to_memory" type="xml">
<files mask="dma3_memory_to_memory_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dma3_scatter_gather" name="dma3_scatter_gather" brief="The EDMA memory to memory example is a simple demonstration program that uses the SDK software.It excuates one shot transfer from source buffer to destination buffer using the SDK EDMA drivers.The purpose of this example is to show how to use the EDMA and to provide a simple example fordebugging and further development." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/edma" path="boards/mekmimx8qx/driver_examples/edma/scatter_gather">
<external path="boards/mekmimx8qx/driver_examples/edma/scatter_gather" type="xml">
<files mask="dma3_scatter_gather_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dpu_blitblend" name="dpu_blitblend" brief="In this project, the safety stream and content stream are both displayed.safety stream on the left part, content stream on the right part.The blit engine generates the frame buffers, the blend modes are differentfor safety stream and content stream.For each stream, there are 5 rectangles, 4 of them are fixed (red, green, blue,and white) and 1 of them is floating (yellow). When the floating rectangleoverlay occurs, the blend modes are different for safety stream and contentstream. For the left part, the overlay color is fixed rectangle adds floatingrectangle. For the right part, the overlay color is fixed rectangle subtractsthe floating rectangle.In this project, the blit engine shadow register feature is used. Newconfiguration is written to the registers during the previous process isstill on-going. The pipline sequence completed interrupt is used to make sureall pending process finished when necessary." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/dpu" path="boards/mekmimx8qx/driver_examples/dpu/blitblend">
<external path="boards/mekmimx8qx/driver_examples/dpu/blitblend" type="xml">
<files mask="dpu_blitblend_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dpu_character" name="dpu_character" brief="The DPU Character example shows how to use the DPU driver to show characters. In this example, the fetch decode is used to fetch frame buffer to show. Two frame buffers are used, CPU fills the inactive frame buffer DPU shows the active frame buffer. When the example runs, you can see character changing in the middle of the screen." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/dpu" path="boards/mekmimx8qx/driver_examples/dpu/character">
<external path="boards/mekmimx8qx/driver_examples/dpu/character" type="xml">
<files mask="dpu_character_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dpu_fetch_decode" name="dpu_fetch_decode" brief="The DPU Fetch Decode example shows how to use the DPU driver to enable fetch decoderunit and the scaler. The fetch decoder output frame size is smaller than desiredoutput, so the scaler units are used for the frame size convert.In this example, the screen is divided to two parts, one for content stream, andthe other for safty stream.If this example runs success, rectangles will move in the screen." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/dpu" path="boards/mekmimx8qx/driver_examples/dpu/fetch_decode">
<external path="boards/mekmimx8qx/driver_examples/dpu/fetch_decode" type="xml">
<files mask="dpu_fetch_decode_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_dpu_rop" name="dpu_rop" brief="This example shows how to use the ROP unit in blit engine. In this project,there are three input frame buffers to the blit engine. The blit enginegenerates two frames using different ROP configurations, so the output framesare different.For landscape display panel:Output frame 0 +------------------+------------------+------------------+ | | | | | Red | Yellow | Green | | | | | | | | | | +--------------------------------------+ | | | | | | | | | Magenta | White | Cyan | | | | | | | | | | | | | | +--------|---------+------------------+------------------+ | | | | | Black | | Black | | | Blue | | | | | | +--------+--------------------------------------+--------+Output frame 1 +------------------+------------------+------------------+ | | | | | Cyan | Blue | Magenta | | | | | | | | | | +--------------------------------------+ | | | | | | | | | Green | Black | Red | | | | | | | | | | | | | | +--------|---------+------------------+------------------+ | | | | | White | | White | | | Yellow | | | | | | +--------+--------------------------------------+--------+For portrait display panel:Output frame 0 +------------------+------------------+------------------+ | | | | | Red | Yellow | Green | | | | | | | | | | | | | | | | | | | | | | +--------------------------------------+ | | | | | | | | | Magenta | White | Cyan | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--------|---------+------------------+------------------+ | | | | | Black | | Black | | | Blue | | | | | | | | | | | | | | | | | | +--------+--------------------------------------+--------+Output frame 1 +------------------+------------------+------------------+ | | | | | Cyan | Blue | Magenta | | | | | | | | | | | | | | | | | | | | | | +--------------------------------------+ | | | | | | | | | Green | Black | Red | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--------|---------+------------------+------------------+ | | | | | White | | White | | | Yellow | | | | | | | | | | | | | | | | | | +--------+--------------------------------------+--------+The two frames are shown one by one. Because the switch intervalis controlled by an software loop delay, so the interval might be differentfor debug target and release target.In this project, a new blit engine process is started only when the previousframe finished." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/dpu" path="boards/mekmimx8qx/driver_examples/dpu/rop">
<external path="boards/mekmimx8qx/driver_examples/dpu/rop" type="xml">
<files mask="dpu_rop_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_enet_txrx_multiring_transfer" name="enet_txrx_multiring_transfer" brief="The enet_txrx_multiring_transfer example shows the way to use ENET driver to receive and transmit avb frame in the avb feature supported multi-ring platforms. this example is only supported in multi-ring platform.1. This example shows how to initialize the ENET MAC.2. How to use ENET MAC to transmit frames in avb supported multiple-ring platforms.The example transmits 30 number frames. For simple demo, we create frames with some special definition.1. Build transmission frames with broadcast mac address.2. Build different frames for each ring: 10 normal ethernet frame, 10 similar IEC 61883-6 type frames,10 similar IEC 61883-8 type frames and the two IEC 1722 avb frames are set with different vlan priority . Notice, To simply show how to use three different rings in rx/tx on one board. This example set PHY local loop and you will see there will be PHY init auto-negotiation fail and this is normal. because phy can not finishauto-negotiation when phy is in loop back mode. However, the auto-negotiation fail has no impact on this loop back example, so just forget about the failure auto-negotiation." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/enet" path="boards/mekmimx8qx/driver_examples/enet/txrx_multiring_transfer">
<external path="boards/mekmimx8qx/driver_examples/enet/txrx_multiring_transfer" type="xml">
<files mask="enet_txrx_multiring_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_enet_txrx_ptp1588_transfer" name="enet_txrx_ptp1588_transfer" brief="The enet_rxtx_ptp1588 example shows the way to use ENET driver to receive and transmit frame in the 1588 feature required cases.1. This example shows how to initialize the ENET MAC.2. How to use ENET MAC to receive and transmit frame.3. How to add to the multicast group to receive PTP 1588 message.4. How to get the time stamp of the PTP 1588 timer.4. How to use Get the ENET transmit and receive frame time stamp.The example transmits 20 number PTP event frame, shows the timestamp of the transmitted frame.The length, source MAC address and destination MAC address of the received frame will be print. The time stamp of the received timestamp will be print when the PTP message frame is received. Note, The RMII mode is used for default setting to initialize the ENET interface between MAC and the external PHY. you can change it to MII mode as you wish. Please make sure the MII Mode setting in the MAC is synchronize to the settingin TWR-SERIAL board for the external PHY." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/enet" path="boards/mekmimx8qx/driver_examples/enet/txrx_ptp1588_transfer">
<external path="boards/mekmimx8qx/driver_examples/enet/txrx_ptp1588_transfer" type="xml">
<files mask="enet_txrx_ptp1588_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_enet_txrx_transfer" name="enet_txrx_transfer" brief="The enet_rxtx example shows the simplest way to use ENET driver for simple frame receive and transmit.1. This example shows how to initialize the ENET MAC.2. How to use ENET MAC to receive and transmit frame.The example transmits 20 number broadcast frame, print the frame length, source MAC addressand destination MAC address when receive frame.Note, The RMII mode is used for default setting to initialize the ENET interface between MAC and the external PHY. youcan change it to MII mode as you wish. Please make sure the MII Mode setting in the MAC is synchronize to the settingin TWR-SERIAL board for the external PHY." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/enet" path="boards/mekmimx8qx/driver_examples/enet/txrx_transfer">
<external path="boards/mekmimx8qx/driver_examples/enet/txrx_transfer" type="xml">
<files mask="enet_txrx_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_esai_edma_transfer" name="esai_edma_transfer" brief="The esai_edma_transfer example shows how to use esai driver with edma:In this example, one esai instance playbacks the audio data recorded by the same esai instance using edma." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/esai" path="boards/mekmimx8qx/driver_examples/esai/edma_transfer">
<external path="boards/mekmimx8qx/driver_examples/esai/edma_transfer" type="xml">
<files mask="esai_edma_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_esai_interrupt_transfer" name="esai_interrupt_transfer" brief="The esai_interrupt_transfer example shows how to use esai driver with interrupt:In this example, one esai instance playbacks the audio data recorded by the same esai instance using interrupt." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/esai" path="boards/mekmimx8qx/driver_examples/esai/interrupt_transfer">
<external path="boards/mekmimx8qx/driver_examples/esai/interrupt_transfer" type="xml">
<files mask="esai_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/flexcan" path="boards/mekmimx8qx/driver_examples/flexcan/interrupt_transfer">
<external path="boards/mekmimx8qx/driver_examples/flexcan/interrupt_transfer" type="xml">
<files mask="flexcan_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_flexcan_loopback" name="flexcan_loopback" brief="The flexcan_loopback_functional example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrouth internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/flexcan" path="boards/mekmimx8qx/driver_examples/flexcan/loopback">
<external path="boards/mekmimx8qx/driver_examples/flexcan/loopback" type="xml">
<files mask="flexcan_loopback_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/flexcan" path="boards/mekmimx8qx/driver_examples/flexcan/loopback_edma_transfer">
<external path="boards/mekmimx8qx/driver_examples/flexcan/loopback_edma_transfer" type="xml">
<files mask="flexcan_loopback_edma_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_flexcan_loopback_transfer" name="flexcan_loopback_transfer" brief="The flexcan_loopback example shows how to use the loopback test mode to debug your CAN Bus design:To demonstrates this example, only one board is needed. The example will config one FlexCAN MessageBuffer to Rx Message Buffer and the other FlexCAN Message Buffer to Tx Message Buffer with same ID.After that, the example will send a CAN Message from the Tx Message Buffer to the Rx Message Bufferthrough internal loopback interconnect and print out the Message payload to terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/flexcan" path="boards/mekmimx8qx/driver_examples/flexcan/loopback_transfer">
<external path="boards/mekmimx8qx/driver_examples/flexcan/loopback_transfer" type="xml">
<files mask="flexcan_loopback_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_flexspi_octal_polling_transfer" name="flexspi_octal_polling_transfer" brief="The flexspi_octal_polling_transfer example shows how to use flexspi driver with polling:In this example, flexspi will send data and operate the external octal flash connected with FLEXSPI. Some simple flash command willbe executed, such as Write Enable, Erase sector, Program page.Example will first erase the sector and program a page into the flash, at last check if the data in flash is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/flexspi" path="boards/mekmimx8qx/driver_examples/flexspi/octal/polling_transfer">
<external path="boards/mekmimx8qx/driver_examples/flexspi/octal/polling_transfer" type="xml">
<files mask="flexspi_octal_polling_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_event" name="freertos_event" brief="This document explains the freertos_event example. It shows how task waits for an event (defined setof bits in event group). This event can be set by any other process or interrupt in the system.The example application creates three tasks. Two write tasks write_task_1 and write_task_2continuously setting event bit 0 and bit 1.Read_task is waiting for any event bit and printing actual state on console. Event bits areautomatically cleared after read task is entered.Three possible states can occurre:Both bits are set.zBit B0 is set.Bit B1 is set." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_event">
<external path="boards/mekmimx8qx/rtos_examples/freertos_event" type="xml">
<files mask="freertos_event_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_generic" name="freertos_generic" brief="This document explains the freertos_generic example. It is based on code FreeRTOS documentation fromhttp://www.freertos.org/Hardware-independent-RTOS-example.html. It shows combination of severaltasks with queue, software timer, tick hook and semaphore.The example application creates three tasks. The prvQueueSendTask periodically sending data toxQueue queue. The prvQueueReceiveTask is waiting for incoming message and counting number ofreceived messages. Task prvEventSemaphoreTask is waiting for xEventSemaphore semaphore given fromvApplicationTickHook. Tick hook give semaphore every 500 ms.Other hook types used for RTOS and resource statistics are also demonstrated in example:* vApplicationIdleHook* vApplicationStackOverflowHook* vApplicationMallocFailedHook" toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_generic">
<external path="boards/mekmimx8qx/rtos_examples/freertos_generic" type="xml">
<files mask="freertos_generic_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_hello" name="freertos_hello" brief="The Hello World project is a simple demonstration program that uses the SDK UART drivere incombination with FreeRTOS. The purpose of this demo is to show how to use the debug console and toprovide a simple project for debugging and further development.The example application creates one task called hello_task. This task print "Hello world." messagevia debug console utility and suspend itself." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_hello">
<external path="boards/mekmimx8qx/rtos_examples/freertos_hello" type="xml">
<files mask="freertos_hello_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_lpuart">
<external path="boards/mekmimx8qx/rtos_examples/freertos_lpuart" type="xml">
<files mask="freertos_lpuart_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_mutex" name="freertos_mutex" brief="This document explains the freertos_mutex example. It shows how mutex manage access to commonresource (terminal output).The example application creates two identical instances of write_task. Each task will lock the mutexbefore printing and unlock it after printing to ensure that the outputs from tasks are not mixedtogether.The test_task accept output message during creation as function parameter. Output message have twoparts. If xMutex is unlocked, the write_task_1 acquire xMutex and print first part of message. Thenrescheduling is performed. In this moment scheduler check if some other task could run, but secondtask write_task+_2 is blocked because xMutex is already locked by first write task. The firstwrite_task_1 continue from last point by printing of second message part. Finaly the xMutex isunlocked and second instance of write_task_2 is executed." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_mutex">
<external path="boards/mekmimx8qx/rtos_examples/freertos_mutex" type="xml">
<files mask="freertos_mutex_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_queue" name="freertos_queue" brief="This document explains the freertos_queue example. This example introduce simple logging mechanismbased on message passing.Example could be devided in two parts. First part is logger. It contain three tasks:log_add().....Add new message into the log. Call xQueueSend function to pass new message into message queue.log_init()....Initialize logger (create logging task and message queue log_queue).log_task()....Task responsible for printing of log output.Second part is application of this simple logging mechanism. Each of two tasks write_task_1 andwrite_task_2 print 5 messages into log." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_queue">
<external path="boards/mekmimx8qx/rtos_examples/freertos_queue" type="xml">
<files mask="freertos_queue_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_sem" name="freertos_sem" brief="This document explains the freertos_sem example, what to expect when running it and a briefintroduction to the API. The freertos_sem example code shows how semaphores works. Two differenttasks are synchronized in bilateral rendezvous model.The example uses four tasks. One producer_task and three consumer_tasks. The producer_task starts bycreating of two semaphores (xSemaphore_producer and xSemaphore_consumer). These semaphores controlaccess to virtual item. The synchronization is based on bilateral rendezvous pattern. Both ofconsumer and producer must be prepared to enable transaction." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_sem">
<external path="boards/mekmimx8qx/rtos_examples/freertos_sem" type="xml">
<files mask="freertos_sem_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_swtimer" name="freertos_swtimer" brief="This document explains the freertos_swtimer example. It shows usage of software timer and itscallback.The example application creates one software timer SwTimer. The timer's callback SwTimerCallback isperiodically executed and text "Tick." is printed to terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_swtimer">
<external path="boards/mekmimx8qx/rtos_examples/freertos_swtimer" type="xml">
<files mask="freertos_swtimer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_freertos_tickless" name="freertos_tickless" brief="This document explains the freertos_tickless example. It shows the CPU enter at sleep mode and then it is waked up by expired time delay that using GPT module." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="rtos_examples" path="boards/mekmimx8qx/rtos_examples/freertos_tickless">
<external path="boards/mekmimx8qx/rtos_examples/freertos_tickless" type="xml">
<files mask="freertos_tickless_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_combine_pwm" name="ftm_combine_pwm" brief="The FTM project is a demonstration program of generating a combined PWM signal by the SDK FTM driver. It sets up the FTMhardware block to output PWM signals on two TPM channels. The example also shows the complementary mode of operationand deadtime insertion.On boards that have 2 LEDs connected to the FTM pins, the user will see a change in LED brightness.And if the board do not support LEDs to show, the outputs can be observed by oscilloscope." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/combine_pwm">
<external path="boards/mekmimx8qx/driver_examples/ftm/combine_pwm" type="xml">
<files mask="ftm_combine_pwm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_dual_edge_capture" name="ftm_dual_edge_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's dual-edge capture feature.This feature is available only on certain SoC's.The example sets up a FTM channel-pair for dual-edge capture. Once the input signal is received,this example will print the capture values and period of the input signal on the terminal window." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/dual_edge_capture">
<external path="boards/mekmimx8qx/driver_examples/ftm/dual_edge_capture" type="xml">
<files mask="ftm_dual_edge_capture_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_input_capture" name="ftm_input_capture" brief="The FTM project is a demonstration program of the SDK FTM driver's input capture feature.The example sets up a FTM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/input_capture">
<external path="boards/mekmimx8qx/driver_examples/ftm/input_capture" type="xml">
<files mask="ftm_input_capture_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_output_compare" name="ftm_output_compare" brief="The FTM project is a demonstration program of the SDK FTM driver's output compare feature.It sets up one FTM channel to toggle the output when a match occurs with the channel value. The usershould probe the FTM output with a oscilloscope to see the signal toggling." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/output_compare">
<external path="boards/mekmimx8qx/driver_examples/ftm/output_compare" type="xml">
<files mask="ftm_output_compare_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_pwm_twochannel" name="ftm_pwm_twochannel" brief="The FTM pwm two channel Example project is a demonstration program that uses the KSDK software to generate a square pulse PWM on 2 channel to control the LED brightness.- FTM generates a PWM with the increasing and decreasing duty cycle.- LED brightness is increasing and then dimming. This is a continuous process." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/pwm_twochannel">
<external path="boards/mekmimx8qx/driver_examples/ftm/pwm_twochannel" type="xml">
<files mask="ftm_pwm_twochannel_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_simple_pwm" name="ftm_simple_pwm" brief="The FTM project is a simple demonstration program of the SDK FTM driver. It sets up the FTMhardware block to output a center-aligned PWM signal. The PWM dutycycle is periodically updated.On boards that have an LED connected to the FTM pins, the user will see a change in LED brightness." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/simple_pwm">
<external path="boards/mekmimx8qx/driver_examples/ftm/simple_pwm" type="xml">
<files mask="ftm_simple_pwm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_ftm_timer" name="ftm_timer" brief="The FTM project is a simple demonstration program of the SDK FTM driver to use FTM as a timer.It sets up the FTM hardware block to trigger an interrupt every 1 millisecond.When the FTM interrupt is triggered a message a printed on the UART terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/ftm" path="boards/mekmimx8qx/driver_examples/ftm/timer">
<external path="boards/mekmimx8qx/driver_examples/ftm/timer" type="xml">
<files mask="ftm_timer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_gpt_capture" name="gpt_capture" brief="The gpt_capture project is a simple demonstration program of the SDK GPT driver's input capture feature.The example sets up a GPT channel for rise-edge capture. Once the input signal is received,this example will print the capture value." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/gpt" path="boards/mekmimx8qx/driver_examples/gpt/capture">
<external path="boards/mekmimx8qx/driver_examples/gpt/capture" type="xml">
<files mask="gpt_capture_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_gpt_timer" name="gpt_timer" brief="The gpt_timer project is a simple demonstration program of the SDK GPT driver. It sets up the GPThardware block to trigger a periodic interrupt after every 1 second. When the GPT interrupt is triggereda message a printed on the UART terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/gpt" path="boards/mekmimx8qx/driver_examples/gpt/timer">
<external path="boards/mekmimx8qx/driver_examples/gpt/timer" type="xml">
<files mask="gpt_timer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_hello_world" name="hello_world" brief="The HelloWorld demo prints the "Hello World" string to the terminal using the SDK UART drivers and repeat what user input. The purpose of this demo is to show how to use the UART, and to provide a simple project for debugging and further development." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="demo_apps" path="boards/mekmimx8qx/demo_apps/hello_world">
<external path="boards/mekmimx8qx/demo_apps/hello_world" type="xml">
<files mask="hello_world_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_igpio_led_output" name="igpio_led_output" brief="The GPIO Example project is a demonstration program that uses the KSDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example take turns to shine the LED." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/gpio" path="boards/mekmimx8qx/driver_examples/gpio/led_output">
<external path="boards/mekmimx8qx/driver_examples/gpio/led_output" type="xml">
<files mask="igpio_led_output_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_intmux" name="intmux" brief="This example shows how to use INTMUX to route the internel interrupt to the system.In this example, one of the INTMUX input source(such as LPIT, TPM) is used to generate internel interrupt.The internel interrupt is outputted to system through INTMUX. Then the interrupt is handled by IRQSTEER, whichlocated outside of the CM4 subsystem." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples" path="boards/mekmimx8qx/driver_examples/intmux">
<external path="boards/mekmimx8qx/driver_examples/intmux" type="xml">
<files mask="intmux_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_isi_ci_pi_yuv422" name="isi_ci_pi_yuv422" brief="This example shows how to use ISI to receive camera frame through CI_PI.In this example, the camera input frame is YUV422 format and ISI output frameis RGB656 format. The output frame is shown in the screen.NOTE:This example must run continously to get the right result, breaking during debugwill results to display tearing. Because the ISI driver maintains IP state throughISR, if the core is halted, then driver state does not match the IP state. Whenexiting debug, the core might be halted for a short while, so the tearing mayhappen when exiting debug.If the camera and LCD panel resolutions are not the same, then only part of thecamera frame will be shown." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/isi/ci_pi/yuv422" path="boards/mekmimx8qx/driver_examples/isi/ci_pi/yuv422">
<external path="boards/mekmimx8qx/driver_examples/isi/ci_pi/yuv422" type="xml">
<files mask="isi_ci_pi_yuv422_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_isi_mipi_csi2_rgb565" name="isi_mipi_csi2_rgb565" brief="This example shows how to use ISI to receive camera frame through MIPI CSI2.In this example, the camera input frame and ISI output frame are both RGB656format. The output frame is shown in the screen.NOTE:This example must run continously to get the right result, breaking during debugwill results to display tearing. Because the ISI driver maintains IP state throughISR, if the core is halted, then driver state does not match the IP state. Whenexiting debug, the core might be halted for a short while, so the tearing mayhappen when exiting debug.If the camera and LCD panel resolutions are not the same, then only part of thecamera frame will be shown." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/isi/mipi_csi2/rgb565" path="boards/mekmimx8qx/driver_examples/isi/mipi_csi2/rgb565">
<external path="boards/mekmimx8qx/driver_examples/isi/mipi_csi2/rgb565" type="xml">
<files mask="isi_mipi_csi2_rgb565_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_isi_mipi_csi2_yuv422" name="isi_mipi_csi2_yuv422" brief="This example shows how to use ISI to receive camera frame through MIPI CSI2.In this example, the camera input frame is YUV422 format and ISI output frameis RGB656 format. The output frame is shown in the screen.NOTE:This example must run continously to get the right result, breaking during debugwill results to display tearing. Because the ISI driver maintains IP state throughISR, if the core is halted, then driver state does not match the IP state. Whenexiting debug, the core might be halted for a short while, so the tearing mayhappen when exiting debug.If the camera and LCD panel resolutions are not the same, then only part of thecamera frame will be shown." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/isi/mipi_csi2/yuv422" path="boards/mekmimx8qx/driver_examples/isi/mipi_csi2/yuv422">
<external path="boards/mekmimx8qx/driver_examples/isi/mipi_csi2/yuv422" type="xml">
<files mask="isi_mipi_csi2_yuv422_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpadc_interrupt" name="lpadc_interrupt" brief="The lpadc_interrupt example shows how to use interrupt with LPADC driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the LPADC'ssample input. When running the project, typing any key into debug console would trigger the conversion. ADC watermark interrupt would be asserted once the number of datawords stored in the ADC Result FIFO is greater than watermark value.In ADC ISR, the watermark flag would be cleared by reading the conversion result value. Also, result information wouldbe printed when the execution return to the main function." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpadc" path="boards/mekmimx8qx/driver_examples/lpadc/interrupt">
<external path="boards/mekmimx8qx/driver_examples/lpadc/interrupt" type="xml">
<files mask="lpadc_interrupt_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpadc_polling" name="lpadc_polling" brief="The lpadc_single_polling example shows the simplest way to use LPADC driver.In this example, user should indicate a channel to provide a voltage signal (can be controlled by user) as the LPADC'ssample input. When running the project, typing any key into debug console would trigger the conversion. The execution would check the FIFO valid 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." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpadc" path="boards/mekmimx8qx/driver_examples/lpadc/polling">
<external path="boards/mekmimx8qx/driver_examples/lpadc/polling" type="xml">
<files mask="lpadc_polling_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_edma_b2b_transfer_master" name="lpi2c_edma_b2b_transfer_master" brief="The lpi2c_edma_b2b_transfer_master example shows how to use lpi2c driver as master to do board to board transfer with EDMA:In this example, one lpi2c instance as master and another lpi2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/edma_b2b_transfer/master">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/edma_b2b_transfer/master" type="xml">
<files mask="lpi2c_edma_b2b_transfer_master_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_edma_b2b_transfer_slave" name="lpi2c_edma_b2b_transfer_slave" brief="The lpi2c_edma_b2b_transfer_slave example shows how to use lpi2c driver as slave to do board to board transfer with a EDMA master:In this example, one lpi2c instance as slave and another lpi2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/edma_b2b_transfer/slave">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/edma_b2b_transfer/slave" type="xml">
<files mask="lpi2c_edma_b2b_transfer_slave_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_interrupt_b2b_transfer_master" name="lpi2c_interrupt_b2b_transfer_master" brief="The lpi2c_interrupt_b2b_transfer_master example shows how to use lpi2c driver as master to do board to board transfer with interrupt:In this example, one lpi2c instance as master and another lpi2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/interrupt_b2b_transfer/master">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/interrupt_b2b_transfer/master" type="xml">
<files mask="lpi2c_interrupt_b2b_transfer_master_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_interrupt_b2b_transfer_slave" name="lpi2c_interrupt_b2b_transfer_slave" brief="The lpi2c_interrupt_b2b_transfer_slave example shows how to use lpi2c driver as slave to do board to board transfer with interrupt:In this example, one lpi2c instance as slave and another lpi2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/interrupt_b2b_transfer/slave">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/interrupt_b2b_transfer/slave" type="xml">
<files mask="lpi2c_interrupt_b2b_transfer_slave_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_polling_b2b_master" name="lpi2c_polling_b2b_master" brief="The lpi2c_polling_b2b_master example shows how to use lpi2c driver as master to do board to board transfer using polling method:In this example, one lpi2c instance as master and another lpi2c instance on the other board as slave. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/polling_b2b/master">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/polling_b2b/master" type="xml">
<files mask="lpi2c_polling_b2b_master_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_polling_b2b_slave" name="lpi2c_polling_b2b_slave" brief="The lpi2c_polling_b2b_slave example shows how to use lpi2c driver as slave to do board to board transfer with a polling master:In this example, one lpi2c instance as slave and another lpi2c instance on the other board as master. Master sends a piece of data to slave, and receive a piece of data from slave. This example checks if the data received from slave is correct." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/polling_b2b/slave">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/polling_b2b/slave" type="xml">
<files mask="lpi2c_polling_b2b_slave_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpi2c_read_accel_value_transfer" name="lpi2c_read_accel_value_transfer" brief="The lpi2c_read_accel_value example shows how to use LPI2C driver to communicate with an lpi2c device: 1. How to use the lpi2c driver to read a lpi2c device who_am_I register. 2. How to use the lpi2c driver to write/read the device registers.In this example, the values of three-axis accelerometer print to the serial terminal on PC throughthe virtual serial port on board." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpi2c" path="boards/mekmimx8qx/driver_examples/lpi2c/read_accel_value_transfer">
<external path="boards/mekmimx8qx/driver_examples/lpi2c/read_accel_value_transfer" type="xml">
<files mask="lpi2c_read_accel_value_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpit_single_channel" name="lpit_single_channel" brief="The LPIT single channel project is a simple example of the SDK LPIT driver. It sets up the LPIThardware block to trigger a periodic interrupt after every 1 second. When the LPIT interrupt is triggereda message a printed on the serial terminal and an LED is toggled on the board." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpit" path="boards/mekmimx8qx/driver_examples/lpit/single_channel">
<external path="boards/mekmimx8qx/driver_examples/lpit/single_channel" type="xml">
<files mask="lpit_single_channel_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpuart" path="boards/mekmimx8qx/driver_examples/lpuart/edma_transfer">
<external path="boards/mekmimx8qx/driver_examples/lpuart/edma_transfer" type="xml">
<files mask="lpuart_edma_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpuart_interrupt" name="lpuart_interrupt" brief="The lpuart_functioncal_interrupt example shows how to use lpuart driver functionalAPI to receive data with interrupt method:In this example, one lpuart instance connect to PC, the board willsend back all characters that PC send to the board." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpuart" path="boards/mekmimx8qx/driver_examples/lpuart/interrupt">
<external path="boards/mekmimx8qx/driver_examples/lpuart/interrupt" type="xml">
<files mask="lpuart_interrupt_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpuart_interrupt_rb_transfer" name="lpuart_interrupt_rb_transfer" brief="The lpuart_interrupt_ring_buffer Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpuart" path="boards/mekmimx8qx/driver_examples/lpuart/interrupt_rb_transfer">
<external path="boards/mekmimx8qx/driver_examples/lpuart/interrupt_rb_transfer" type="xml">
<files mask="lpuart_interrupt_rb_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpuart_interrupt_transfer" name="lpuart_interrupt_transfer" brief="The lpuart_interrupt Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console in a group of 8 characters." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpuart" path="boards/mekmimx8qx/driver_examples/lpuart/interrupt_transfer">
<external path="boards/mekmimx8qx/driver_examples/lpuart/interrupt_transfer" type="xml">
<files mask="lpuart_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lpuart_polling" name="lpuart_polling" brief="The lpuart_polling Example project is to demonstrate usage of the KSDK lpuart driver.In the example, you can send characters to the console back and they will be printed out onto console instantly." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/lpuart" path="boards/mekmimx8qx/driver_examples/lpuart/polling">
<external path="boards/mekmimx8qx/driver_examples/lpuart/polling" type="xml">
<files mask="lpuart_polling_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_dhcp_bm" name="lwip_dhcp_bm" brief="The lwip_dhcp demo application demonstrates a DHCP demo on the lwIP TCP/IP stack.The application acts as a DHCP client and prints the status as it is progressing.Once the interface is being bound to an IP address obtained from DHCP server, address information is printed." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_dhcp/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_dhcp/bm" type="xml">
<files mask="lwip_dhcp_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_dhcp_freertos" name="lwip_dhcp_freertos" brief="The lwip_dhcp demo application demonstrates a DHCP demo on the lwIP TCP/IP stack.The application acts as a DHCP client and prints the status as it is progressing.Once the interface is being bound to an IP address obtained from DHCP server, address information is printed." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_dhcp/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_dhcp/freertos" type="xml">
<files mask="lwip_dhcp_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_httpsrv_bm" name="lwip_httpsrv_bm" brief="The lwip_httpsrv demo application demonstrates an HTTPServer on the lwIP TCP/IP stack with bare metal SDK or FreeRTOS.The user uses an Internet browser to send a request for connection. The board acts as an HTTP server and sends a Webpage back to the PC." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_httpsrv/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_httpsrv/bm" type="xml">
<files mask="lwip_httpsrv_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_httpsrv_freertos" name="lwip_httpsrv_freertos" brief="The lwip_httpsrv demo application demonstrates an HTTPServer on the lwIP TCP/IP stack with bare metal SDK or FreeRTOS.The user uses an Internet browser to send a request for connection. The board acts as an HTTP server and sends a Webpage back to the PC." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_httpsrv/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_httpsrv/freertos" type="xml">
<files mask="lwip_httpsrv_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_iperf_bm" name="lwip_iperf_bm" brief="This is the IPerf server example to check your bandwidth using the network performance measurement IPerf application on a PC as a client.It is currently a minimal implementation providing an IPv4 TCP server only.Instead of the command line IPerf application, for more convenience, it is recommended to use the JPerf2 graphical tool, which can be downloaded here: https://sourceforge.net/projects/iperf/files/jperf/jperf%202.0.0/jperf-2.0.0.zip/download" toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_iperf/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_iperf/bm" type="xml">
<files mask="lwip_iperf_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_mqtt_freertos" name="lwip_mqtt_freertos" brief="The lwip_mqtt demo application demonstrates MQTT client connecting to MQTT broker via unsecured socket. The application obtains IP and DNS addresses from DHCP and resolves broker's hostname if needed. Then it connects to the broker and subscribes to the "lwip_topic/#" and "lwip_other/#" topics. Further it publishes five messages to the "lwip_topic/100" which are also received back as the board is subscribed to the "lwip_topic/#". Meanwhile it continues to receive messages published to the subscribed topics from other clients." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_mqtt/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_mqtt/freertos" type="xml">
<files mask="lwip_mqtt_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_ping_bm" name="lwip_ping_bm" brief="The lwip_ping demo application demonstrates a Ping Demo on the lwIP TCP/IP stack, which uses the ICMP protocol. Theapplication periodically sends the ICMP echo request to a PC, and processes the PC reply. Type "ping $board_address"in the PC command window to send an ICMP echo request to the board. The lwIP stack sends the ICMP echo reply back to thePC." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_ping/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_ping/bm" type="xml">
<files mask="lwip_ping_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_ping_freertos" name="lwip_ping_freertos" brief="The lwip_ping demo application demonstrates a Ping Demo on the lwIP TCP/IP stack which using the ICMP protocol. Theapplication periodically sends the ICMP echo request to a PC and processes the PC reply. Type the "ping $board_address"in the PC command window to send an ICMP echo request to the board. The lwIP stack sends the ICMP echo reply back to thePC." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_ping/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_ping/freertos" type="xml">
<files mask="lwip_ping_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_tcpecho_bm" name="lwip_tcpecho_bm" brief="The lwip_tcpecho demo application demonstrates a TCP echo demo on the lwIP TCP/IP stack with bare metal KSDK orFreeRTOS. The demo uses the TCP protocol and acts as an echo server. The application sends back the received TCPpackets from the PC, which can be used to test whether a TCP connection is available." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_tcpecho/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_tcpecho/bm" type="xml">
<files mask="lwip_tcpecho_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_tcpecho_freertos" name="lwip_tcpecho_freertos" brief="The lwip_tcpecho demo application demonstrates a TCP echo demo on the lwIP TCP/IP stack with bare metal KSDK orFreeRTOS. The demo uses the TCP protocol and acts as an echo server. The application sends back the received TCPpackets from the PC, which can be used to test whether a TCP connection is available." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_tcpecho/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_tcpecho/freertos" type="xml">
<files mask="lwip_tcpecho_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_udpecho_bm" name="lwip_udpecho_bm" brief="The lwip_udpecho demo application demonstrates a UDP echo demo on the lwIP TCP/IP stack with bare metal KSDK orFreeRTOS, which uses the UDP protocol and acts as an echo server. The application sends back the received UDP packetsfrom the PC, which can be used to test whether a UDP connection is available." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_udpecho/bm">
<external path="boards/mekmimx8qx/lwip_examples/lwip_udpecho/bm" type="xml">
<files mask="lwip_udpecho_bm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_lwip_udpecho_freertos" name="lwip_udpecho_freertos" brief="The lwip_udpecho demo application demonstrates a UDP echo demo on the lwIP TCP/IP stack with bare metal KSDK orFreeRTOS, which uses the UDP protocol and acts as an echo server. The application sends back the received UDP packetsfrom the PC, which can be used to test whether a UDP connection is available." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="lwip_examples" path="boards/mekmimx8qx/lwip_examples/lwip_udpecho/freertos">
<external path="boards/mekmimx8qx/lwip_examples/lwip_udpecho/freertos" type="xml">
<files mask="lwip_udpecho_freertos_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_mmcau" name="mmcau" brief="Memory-Mapped Cryptographic Acceleration Unit (MMCAU)This project is a demonstration program that uses the KSDK software for encryption/decryption sampledata using AES-CBC, DES3-CBC and Hash algorithms MD5, SHA1 and SHA256." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="mmcau_examples" path="boards/mekmimx8qx/mmcau_examples/mmcau_api">
<external path="boards/mekmimx8qx/mmcau_examples/mmcau_api" type="xml">
<files mask="mmcau_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_power_mode_switch" name="power_mode_switch" brief="The Power mode switch demo application demonstrates the use of power modes in the KSDK. The demo prints the power mode menuthrough the debug console, where the user can set the MCU to a specific power mode. The user can also set the wakeupsource by following the debug console prompts. The purpose of this demo is to show how to switch between different power modes, and how to configure a wakeup source and wakeup the MCU from low power modes. Tips: This demo is to show how the various power mode can switch to each other. However, in actual low power use case, to save energy and reduce the consumption even more, many things can be done including: - Disable the clock for unnecessary module during low power mode. That means, programmer can disable the clocks before entering the low power mode and re-enable them after exiting the low power mode when necessary. - Disable the function for unnecessary part of a module when other part would keep working in low power mode. At the most time, more powerful function means more power consumption. For example, disable the digital function for the unnecessary pin mux, and so on. - Set the proper pin state (direction and logic level) according to the actual application hardware. Otherwise, the pin cirrent would be activied unexpectedly waste some energy. - Other low power consideration based on the actual application hardware. - Debug pins(e.g SWD_DIO) would consume addtional power, had better to disable related pins or disconnect them. " toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="demo_apps" path="boards/mekmimx8qx/demo_apps/power_mode_switch">
<external path="boards/mekmimx8qx/demo_apps/power_mode_switch" type="xml">
<files mask="power_mode_switch_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_rgpio_led_output" name="rgpio_led_output" brief="The RGPIO Example project is a demonstration program that uses the SDK software to manipulate the general-purposeoutputs.The example is supported by the set, clear, and toggle write-only registers for each port output data register. The example take turns to shine the LED." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/rgpio" path="boards/mekmimx8qx/driver_examples/rgpio/led_output">
<external path="boards/mekmimx8qx/driver_examples/rgpio/led_output" type="xml">
<files mask="rgpio_led_output_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_rpmsg_lite_pingpong_rtos_linux_remote" name="rpmsg_lite_pingpong_rtos_linux_remote" brief="The Multicore RPMsg-Lite pingpong RTOS project is a simple demonstration program that uses theMCUXpresso SDK software and the RPMsg-Lite library and shows how to implement the inter-corecommunicaton between cores of the multicore system. The primary core releases the secondary corefrom the reset and then the inter-core communication is established. Once the RPMsg is initializedand endpoints are created the message exchange starts, incrementing a virtual counter that is partof the message payload. The message pingpong finishes when the counter reaches the value of 100.Then the RPMsg-Lite is deinitialized and the procedure of the data exchange is repeated again.Shared memory usageThis multicore example uses the shared memory for data exchange. The shared memory region isdefined and the size can be adjustable in the linker file. The shared memory region start addressand the size have to be defined in linker file for each core equally. The shared memory startaddress is then exported from the linker to the application." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="multicore_examples" path="boards/mekmimx8qx/multicore_examples/rpmsg_lite_pingpong_rtos/linux_remote">
<external path="boards/mekmimx8qx/multicore_examples/rpmsg_lite_pingpong_rtos/linux_remote" type="xml">
<files mask="rpmsg_lite_pingpong_rtos_linux_remote_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_rpmsg_lite_str_echo_rtos_imxcm4" name="rpmsg_lite_str_echo_rtos_imxcm4" brief="The Multicore RPMsg-Lite string echo project is a simple demonstration program that uses theMCUXpresso SDK software and the RPMsg-Lite library and shows how to implement the inter-corecommunicaton between cores of the multicore system.It works with Linux RPMsg master peer to transfer string content back and forth. The name servicehandshake is performed first to create the communication channels. Next, Linux OS waits for userinput to the RPMsg virtual tty. Anything which is received is sent to M4. M4 displays what isreceived, and echoes back the same message as an acknowledgement. The tty reader on the Linux sidecan get the message, and start another transaction. The demo demonstrates RPMsg’s ability to sendarbitrary content back and forth. Note: The maximum message length supported by RPMsg is now 496bytes. String longer than 496 will be divided by virtual tty into several messages.Shared memory usageThis multicore example uses the shared memory for data exchange. The shared memory region isdefined and the size can be adjustable in the linker file. The shared memory region start addressand the size have to be defined in linker file for each core equally. The shared memory startaddress is then exported from the linker to the application." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="multicore_examples" path="boards/mekmimx8qx/multicore_examples/rpmsg_lite_str_echo_rtos">
<external path="boards/mekmimx8qx/multicore_examples/rpmsg_lite_str_echo_rtos" type="xml">
<files mask="rpmsg_lite_str_echo_rtos_imxcm4_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_sai_edma_transfer" name="sai_edma_transfer" brief="The sai_edma_transfer example shows how to use sai driver with EDMA:In this example, one sai instance playbacks the audio data stored in flash/SRAM using EDMA channel." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/sai" path="boards/mekmimx8qx/driver_examples/sai/edma_transfer">
<external path="boards/mekmimx8qx/driver_examples/sai/edma_transfer" type="xml">
<files mask="sai_edma_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_sai_interrupt" name="sai_interrupt" brief="The sai_interrupt example shows how to use sai functional API to implement interrupt playback:In this example, one sai instance playbacks the audio data stored in flash/SRAM using interrupt." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/sai" path="boards/mekmimx8qx/driver_examples/sai/interrupt">
<external path="boards/mekmimx8qx/driver_examples/sai/interrupt" type="xml">
<files mask="sai_interrupt_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_sai_interrupt_transfer" name="sai_interrupt_transfer" brief="The sai_interrupt_transfer example shows how to use sai driver with interrupt:In this example, one sai instance playbacks the audio data stored in flash/SRAM using interrupt." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/sai" path="boards/mekmimx8qx/driver_examples/sai/interrupt_transfer">
<external path="boards/mekmimx8qx/driver_examples/sai/interrupt_transfer" type="xml">
<files mask="sai_interrupt_transfer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_sema42_uboot" name="sema42_uboot" brief="The sema42 uboot example shows how to use SEMA42 driver to lock and unlock a sema gate.This example should work together with uboot. This example runs on Cortex-M core,the uboot runs on the Cortex-A core." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/sema42" path="boards/mekmimx8qx/driver_examples/sema42/uboot">
<external path="boards/mekmimx8qx/driver_examples/sema42/uboot" type="xml">
<files mask="sema42_uboot_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_srtm_demo" name="srtm_demo" brief="TBD" toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="demo_apps" path="boards/mekmimx8qx/demo_apps/srtm_demo">
<external path="boards/mekmimx8qx/demo_apps/srtm_demo" type="xml">
<files mask="srtm_demo_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_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="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/dual_edge_capture">
<external path="boards/mekmimx8qx/driver_examples/tpm/dual_edge_capture" type="xml">
<files mask="tpm_dual_edge_capture_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tpm_input_capture" name="tpm_input_capture" brief="The TPM project is a demonstration program of the SDK TPM driver's input capture feature.The example sets up a TPM channel for dual-edge capture. Once the input signal is received,this example will print the capture value." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/input_capture">
<external path="boards/mekmimx8qx/driver_examples/tpm/input_capture" type="xml">
<files mask="tpm_input_capture_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tpm_output_compare" name="tpm_output_compare" brief="The TPM project is a demonstration program of the SDK TPM driver's output compare feature.It sets up one TPM channel to toggle the output when a match occurs with the channel value. The usershould probe the TPM output with a oscilloscope to see the signal toggling." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/output_compare">
<external path="boards/mekmimx8qx/driver_examples/tpm/output_compare" type="xml">
<files mask="tpm_output_compare_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tpm_pwm_twochannel" name="tpm_pwm_twochannel" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output PWM signals on two TPM channels. The PWM dutycycle on both channelsis manually updated. On boards that have an LED connected to the TPM pins, the user will seea change in LED brightness if user enter different values." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/pwm_twochannel">
<external path="boards/mekmimx8qx/driver_examples/tpm/pwm_twochannel" type="xml">
<files mask="tpm_pwm_twochannel_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tpm_simple_pwm" name="tpm_simple_pwm" brief="The TPM project is a simple demonstration program of the SDK TPM driver. It sets up the TPMhardware block to output a center-aligned PWM signal. The PWM dutycycle is manually updated.On boards that have an LED connected to the TPM pins, the user will see a change in LEDbrightness if user enter different values." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/simple_pwm">
<external path="boards/mekmimx8qx/driver_examples/tpm/simple_pwm" type="xml">
<files mask="tpm_simple_pwm_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tpm_timer" name="tpm_timer" brief="The TPM project is a simple demonstration program of the SDK TPM driver to use TPM as a timer.It sets up the TPM hardware block to trigger an interrupt every 1 millisecond.When the TPM interrupt is triggered a message a printed on the UART terminal." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples/tpm" path="boards/mekmimx8qx/driver_examples/tpm/timer">
<external path="boards/mekmimx8qx/driver_examples/tpm/timer" type="xml">
<files mask="tpm_timer_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_tstmr" name="tstmr" brief="The tstmr example shows the usage of TSTMR driver in application. The TSTMR module is a free running incrementing counter that starts running after system reset de-assertion and can be read at any time by the software for determining the software ticks.The TSTMR runs off the 1 MHz clock and resets on every system reset.In this example, it would output a time stamp information when the application is ready. And then, delay for 1 second with TSTMR_DelayUs() function. Before and after the delay, it would output the two time stamps information again." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples" path="boards/mekmimx8qx/driver_examples/tstmr">
<external path="boards/mekmimx8qx/driver_examples/tstmr" type="xml">
<files mask="tstmr_v3_8.xml"/>
</external>
</example>
<example id="mekmimx8qx_wdog32" name="wdog32" brief="The WDOG32 Example project is to demonstrate usage of the KSDK wdog32 driver.In this example, fast testing is first implemented to test the wdog32.After this, refreshing the watchdog in None-window mode and window mode is executed.Note wdog32 is disabled in SystemInit function which means wdog32 is disabledafter chip emerges from reset." toolchain="armgcc iar" compiler="compiler_gcc compiler_iar" category="driver_examples" path="boards/mekmimx8qx/driver_examples/wdog32">
<external path="boards/mekmimx8qx/driver_examples/wdog32" type="xml">
<files mask="wdog32_v3_8.xml"/>
</external>
</example>
</examples>
</board>
</boards>
<devices>
<device id="MIMX8QX6xxxFZ" name="MIMX8QX6" version="1.0.0" full_name="MIMX8QX6xxxFZ" family="MIMX8QXx" platform="i.MX">
<description>i.MX 8X Family – Arm Cortex-A35, 3D Graphics, 4K Video, DSP, Error Correcting Code on DDR</description>
<metadataSet>
<metadata key="vendor" value="NXP"/>
</metadataSet>
<core id="cm4_MIMX8QX6xxxFZ" name="cm4" fpu="true" type="cm4"/>
<memory>
<memoryBlock id="SRAM_UPPER_MIMX8QX6xxxFZ" name="SRAM_UPPER" addr="20000000" size="00020000" type="RAM" access="RW"/>
<memoryBlock id="SRAM_LOWER_MIMX8QX6xxxFZ" name="SRAM_LOWER" addr="1ffe0000" size="00020000" type="RAM" access="RW"/>
</memory>
<total_memory flash_size_kb="0" ram_size_kb="256"/>
<package id="MIMX8QX6AVLFZ" name="MIMX8QX6AVLFZ"/>
<evaluation_boards>
<evaluation_board name="mekmimx8qx"/>
</evaluation_boards>
<debug_configurations>
<debug_configuration id_refs="com.crt.advproject.config.exe.debug com.crt.advproject.config.exe.release">
<params>
<params id="internal.attach.slave.release.MIMX8QX6xxxFZ" name="internal.attach.slave" value="true"/>
<params id="internal.multi.swd.release.MIMX8QX6xxxFZ" name="internal.multi.swd" value="true"/>
<params id="internal.wiretype.release.MIMX8QX6xxxFZ" name="internal.wiretype" value="SWD"/>
<params id="internal.has_swo.release.MIMX8QX6xxxFZ" name="internal.has_swo" value="false"/>
</params>
<drivers>
<driver id_refs="QSPI_FLASH_MIMX8QX6xxxFZ">
<driverBinary path="devices/MIMX8QX6/mcuxpresso" type="binary">
<files mask="flash_driver_placeholder.cfx"/>
</driverBinary>
</driver>
</drivers>
</debug_configuration>
</debug_configurations>
<linkerSettings nature="c_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="mtb_supported" value="false"/>
</linkerSettings>
<linkerSettings nature="cpp_nature">
<linker property="start_symbol" value="ResetISR"/>
<linker property="text_align" value="4"/>
<linker property="data_align" value="4"/>
<linker property="bss_align" value="4"/>
<linker property="mtb_supported" value="false"/>
</linkerSettings>
</device>
</devices>
<components>
<component id="project_template.mekmimx8qx.MIMX8QX6" name="mekmimx8qx" brief="Board_project_template mekmimx8qx" version="1.0.0" full_name="Board_project_template mekmimx8qx" devices="MIMX8QX6xxxFZ" device_cores="cm4_MIMX8QX6xxxFZ" category="Board Support/SDK Project Template" user_visible="true" type="project_template" package_base_path="boards/mekmimx8qx/project_template" project_base_path="board">
<dependencies>
<all>
<component_dependency value="platform.drivers.common.MIMX8QX6"/>
<component_dependency value="device.MIMX8QX6_CMSIS.MIMX8QX6"/>
<component_dependency value="device.MIMX8QX6_startup.MIMX8QX6"/>
<component_dependency value="platform.drivers.lpuart.MIMX8QX6"/>
<component_dependency value="platform.drivers.igpio.MIMX8QX6"/>
<component_dependency value="component.lpuart_adapter.MIMX8QX6"/>
<component_dependency value="component.lists.MIMX8QX6"/>
<any_of>
<all>
<component_dependency value="platform.utilities.assert.MIMX8QX6"/>
<component_dependency value="utility.debug_console.MIMX8QX6"/>
<component_dependency value="component.serial_manager.MIMX8QX6"/>
</all>
<all>
<component_dependency value="platform.utilities.assert_lite.MIMX8QX6"/>
<component_dependency value="utility.debug_console_lite.MIMX8QX6"/>
</all>
</any_of>
</all>
</dependencies>
<source relative_path="./" type="c_include">
<files mask="board.h"/>
<files mask="clock_config.h"/>
<files mask="pin_mux.h"/>
<files mask="peripherals.h"/>
</source>
<source relative_path="./" type="src">
<files mask="board.c"/>
<files mask="clock_config.c"/>
<files mask="pin_mux.c"/>
<files mask="peripherals.c"/>
</source>
<include_paths>
<include_path relative_path="./" type="c_include"/>
<include_path relative_path="./" type="c_include"/>
</include_paths>
</component>
<component id="platform.CMSIS.MIMX8QX6" name="CMSIS" brief="Cmsis" version="5.6.0" full_name="Cmsis" devices="MIMX8QX6xxxFZ" user_visible="true" type="CMSIS" package_base_path="CMSIS" project_base_path="./">
<dependencies>
<all>
<component_dependency value="platform.Include_common.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.Common_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver"/>
<component_dependency value="platform.CMSIS_Driver_Include.CAN_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_MAC_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.Ethernet_PHY_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.Flash_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.I2C_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.MCI_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.NAND_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.SAI_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.SPI_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.USART_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_Device_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.USB_Host_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.WiFi_CMSISInclude.MIMX8QX6"/>
<component_dependency value="platform.Include_dsp.MIMX8QX6"/>
<component_dependency value="platform.CMSIS_Driver_Include.GPIO_CMSISInclude.MIMX8QX6"/>
</all>
</dependencies>
<source relative_path="./" project_relative_path="CMSIS" type="doc">
<files mask="LICENSE.txt"/>
</source>
<source relative_path="Include" type="c_include">
<files mask="core_cm23.h"/>
<files mask="cmsis_armcc.h"/>
<files mask="tz_context.h"/>
<files mask="core_cm3.h"/>
<files mask="mpu_armv8.h"/>
<files mask="core_cm4.h"/>
<files mask="core_cm0.h"/>
<files mask="cmsis_armclang.h"/>
<files mask="core_cm7.h"/>
<files mask="arm_math.h"/>
<files mask="cmsis_iccarm.h"/>
<files mask="core_cm1.h"/>
<files mask="core_dsp.h"/>
<files mask="cmsis_compiler.h"/>
<files mask="core_cm0plus.h"/>
<files mask="core_sc000.h"/>
<files mask="core_armv81mml.h"/>
<files mask="core_cm35p.h"/>
<files mask="cmsis_armclang_ltm.h"/>
<files mask="cmsis_gcc.h"/>
<files mask="mpu_armv7.h"/>
<files mask="core_armv8mml.h"/>
<files mask="core_cm33.h"/>
<files mask="cmsis_version.h"/>
<files mask="core_armv8mbl.h"/>
<files mask="core_sc300.h"/>
<files mask="arm_const_structs.h"/>
<files mask="arm_common_tables.h"/>
</source>
<include_paths>
<include_path relative_path="Include" type="c_include"/>
</include_paths>
</component>
<component id="platform.CMSIS_DSP_Lib.MIMX8QX6" name="CMSIS_DSP_Lib" brief="Cmsis_dsp_lib" version="1.7.0" full_name="Cmsis_dsp_lib" devices="MIMX8QX6xxxFZ" user_visible="false" type="CMSIS" package_base_path="CMSIS/DSP" project_base_path="DSP">
<source relative_path="Examples/ARM/arm_class_marks_example" type="src">
<files mask="arm_class_marks_example_f32.c"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example" type="configuration">
<files mask="arm_class_marks_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example" type="project">
<files mask="arm_class_marks_example.uvoptx"/>
<files mask="arm_class_marks_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_class_marks_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example" type="src">
<files mask="arm_convolution_example_f32.c"/>
<files mask="math_helper.c"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example" type="configuration">
<files mask="arm_convolution_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example" type="project">
<files mask="arm_convolution_example.uvoptx"/>
<files mask="arm_convolution_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_convolution_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example" type="src">
<files mask="arm_dotproduct_example_f32.c"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example" type="configuration">
<files mask="arm_dotproduct_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example" type="project">
<files mask="arm_dotproduct_example.uvoptx"/>
<files mask="arm_dotproduct_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_dotproduct_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example" type="src">
<files mask="arm_fft_bin_data.c"/>
<files mask="arm_fft_bin_example_f32.c"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example" type="configuration">
<files mask="arm_fft_bin_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example" type="project">
<files mask="arm_fft_bin_example.uvoptx"/>
<files mask="arm_fft_bin_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_fft_bin_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example" type="src">
<files mask="arm_fir_data.c"/>
<files mask="arm_fir_example_f32.c"/>
<files mask="math_helper.c"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example" type="configuration">
<files mask="arm_fir_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example" type="project">
<files mask="arm_fir_example.uvoptx"/>
<files mask="arm_fir_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_fir_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example" type="src">
<files mask="arm_graphic_equalizer_example_q31.c"/>
<files mask="arm_graphic_equalizer_data.c"/>
<files mask="math_helper.c"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example" type="configuration">
<files mask="arm_graphic_equalizer_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example" type="project">
<files mask="arm_graphic_equalizer_example.uvoptx"/>
<files mask="arm_graphic_equalizer_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_graphic_equalizer_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example" type="src">
<files mask="math_helper.c"/>
<files mask="arm_linear_interp_example_f32.c"/>
<files mask="arm_linear_interp_data.c"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example" type="configuration">
<files mask="arm_linear_interp_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example" type="project">
<files mask="arm_linear_interp_example.uvoptx"/>
<files mask="arm_linear_interp_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_linear_interp_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example" type="src">
<files mask="arm_matrix_example_f32.c"/>
<files mask="math_helper.c"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example" type="configuration">
<files mask="arm_matrix_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example" type="project">
<files mask="arm_matrix_example.uvoptx"/>
<files mask="arm_matrix_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM0" type="src">
<files mask="system_ARMCM0.c"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM0" type="asm_include">
<files mask="startup_ARMCM0.s"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM3" type="src">
<files mask="system_ARMCM3.c"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM3" type="asm_include">
<files mask="startup_ARMCM3.s"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM4_FP" type="src">
<files mask="system_ARMCM4.c"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM4_FP" type="asm_include">
<files mask="startup_ARMCM4.s"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM7_SP" type="src">
<files mask="system_ARMCM7.c"/>
</source>
<source relative_path="Examples/ARM/arm_matrix_example/RTE/Device/ARMCM7_SP" type="asm_include">
<files mask="startup_ARMCM7.s"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example" type="src">
<files mask="math_helper.c"/>
<files mask="arm_signal_converge_example_f32.c"/>
<files mask="arm_signal_converge_data.c"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example" type="c_include">
<files mask="math_helper.h"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example" type="configuration">
<files mask="arm_signal_converge_example.ini"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example" type="doc">
<files mask="Abstract.txt"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example" type="project">
<files mask="arm_signal_converge_example.uvoptx"/>
<files mask="arm_signal_converge_example.uvprojx"/>
</source>
<source relative_path="Examples/ARM/arm_signal_converge_example/RTE/Device/ARMCM0" type="src">