Skip to content

Commit 6d93840

Browse files
AniruddhaKanhereAniruddhaKanhere
committed
First working commit
1 parent 5e7ab0d commit 6d93840

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

50 files changed

+3172
-1149
lines changed

‎.gitmodules

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,6 @@
2525
[submodule "Middleware/FreeRTOS/pkcs11"]
2626
path = Middleware/FreeRTOS/pkcs11
2727
url = https://github.com/amazon-freertos/pkcs11.git
28-
[submodule "Middleware/AWS/ota"]
29-
path = Middleware/AWS/ota
30-
url = https://github.com/aws/ota-for-aws-iot-embedded-sdk
3128
[submodule "Middleware/tinycbor"]
3229
path = Middleware/tinycbor
3330
url = https://github.com/intel/tinycbor.git
@@ -49,3 +46,9 @@
4946
[submodule "Middleware/FreeRTOS/tests"]
5047
path = Middleware/FreeRTOS/tests
5148
url = https://github.com/FreeRTOS/FreeRTOS-Libraries-Integration-Tests.git
49+
[submodule "Middleware/AWS/mqtt-stream"]
50+
path = Middleware/AWS/mqtt-stream
51+
url = https://github.com/aws/aws-iot-core-mqtt-file-streams-embedded-c
52+
[submodule "Middleware/AWS/jobs"]
53+
path = Middleware/AWS/jobs
54+
url = https://github.com/aws/Jobs-for-AWS-IoT-embedded-sdk.git

‎.mcuxpressoide_packages_support/MIMXRT1062xxxxB_support/MIMXRT1060_dir_part.xml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<chips chipVendor="NXP"
3+
family="MIMXRT1060"
4+
vendorURL="http://www.nxp.com"
5+
chipURL="">
6+
<chip name="MIMXRT1062xxxxB"
7+
displayName="MIMXRT1062xxxxB"
8+
xml_file="MIMXRT1062_internal.xml"
9+
chipURL=""/>
10+
</chips>

‎.mcuxpressoide_packages_support/MIMXRT1062xxxxB_support/MIMXRT1060_list.xml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<chips chipVendor="NXP" family="MIMXRT1060">
3+
<chip name="MIMXRT1062xxxxB" flash=""/>
4+
</chips>

‎.mcuxpressoide_packages_support/MIMXRT1062xxxxB_support/MIMXRT1062_internal.xml

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<!DOCTYPE infoList
3+
SYSTEM "crt_infolist.dtd">
4+
<infoList vendor="NXP">
5+
<info name="MIMXRT1062xxxxB" chip="MIMXRT1062xxxxB">
6+
<chip>
7+
<name>MIMXRT1062xxxxB</name>
8+
<family>MIMXRT1060</family>
9+
<vendor>NXP</vendor>
10+
<memory id="Flash"
11+
type="Flash"
12+
size="0"
13+
is_ro="true"
14+
can_program="true"/>
15+
<memory id="RAM" type="RAM" size="1024"/>
16+
<memoryInstance id="SRAM_DTC"
17+
derived_from="RAM"
18+
location="0x20000000"
19+
size="0x00020000"/>
20+
<memoryInstance id="SRAM_ITC"
21+
derived_from="RAM"
22+
location="0x00000000"
23+
size="0x00020000"/>
24+
<memoryInstance id="SRAM_OC2"
25+
derived_from="RAM"
26+
location="0x20200000"
27+
size="0x00080000"/>
28+
<memoryInstance id="SRAM_OC"
29+
derived_from="RAM"
30+
location="0x20280000"
31+
size="0x00040000"/>
32+
</chip>
33+
<processor>
34+
<name gcc_name="cortex-m7">Cortex-M7</name>
35+
<family>Cortex-M</family>
36+
</processor>
37+
</info>
38+
</infoList>

‎.mcuxpressoide_packages_support/MIMXRT1062xxxxB_support/crt_directory.dtd

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
<!-- This is a directory of XML files for a specific processor or a
2+
a set. It contains "links" to other XML files based on lookup
3+
criteria. The file is organized into Boards (target boards),
4+
Chips (processor+ASIC chip definitions), and RTOSes.
5+
The containers for each are per processor family. The processor
6+
families are such as "ARM7", "Cortex-M", etc. Within are the
7+
links per specific item. -->
8+
<!ELEMENT directory (boards*,chips*,rtoses*)>
9+
<!-- 1st is Boards. These are target boards. The name match is
10+
normally from the user specifying the board by name (at
11+
install time or dynamically or via configuration). Board
12+
lookup by mapped register value is only available for a class
13+
of boards, since there is no standards. -->
14+
<!ELEMENT boards (board*)> <!ATTLIST boards
15+
chipVendor CDATA #REQUIRED>
16+
<!-- Board defines a board by name, the chip on it, and optional
17+
description. It also has the link to the XML file with
18+
the details. Note that the board XML file may be a shared
19+
file with more than one board in it, so the consumer must
20+
look for the matching board by name.
21+
If the name has a "*" or "?" in it, those are wildcards
22+
to allow multiple matches.
23+
The chip attribute is used to search for the chip file
24+
(see "chips" below). -->
25+
<!ELEMENT board (EMPTY)> <!ATTLIST board
26+
name CDATA #REQUIRED
27+
xml_file CDATA #REQUIRED
28+
chip CDATA #REQUIRED
29+
description CDATA #IMPLIED>
30+
31+
<!-- Chips define processor chips (processor+ASIC). These include
32+
peripherals, Flash programming information, memory layout,
33+
and vendor information.
34+
If the name has a "*" or "?" in it, those are wildcards
35+
to allow multiple matches. -->
36+
<!ELEMENT chips (chip*)> <!ATTLIST chips
37+
chipVendor CDATA #REQUIRED
38+
family CDATA #IMPLIED>
39+
<!-- Chip defines a chip by name, optionally the exact processor
40+
in it, and an optional description. It also has the link to
41+
the XML file with the details. Note that the chip XML file
42+
may be a shared file with more than one chip in it, so the
43+
consumer must look for the matching chip by name. Note that
44+
default is only filled in for one chip, and that is what will
45+
be selected if nothing requested.
46+
If the name has a "*" or "?" in it, those are wildcards
47+
to allow multiple matches.
48+
The proc attribute may be used to ensure support for the
49+
specific processor in the family. -->
50+
<!ELEMENT chip (EMPTY)> <!ATTLIST chip
51+
name CDATA #REQUIRED
52+
xml_file CDATA #REQUIRED
53+
proc CDATA #IMPLIED
54+
description CDATA #IMPLIED
55+
default (true|false) #IMPLIED>
56+
57+
<!-- Rtoses defines embedded operating systems (and kernels and
58+
the like). RTOS is used loosely, so that even an application
59+
may be represented this way. The rtos data model allows for
60+
both intelligent structure viewing (converting fields into
61+
meaningful data, linked list and array following) and optionally
62+
agent interactions (live debug of a running system).
63+
The RTOS list allows for finding a matching rtos by name
64+
or symbol match.
65+
If the name has a "*" or "?" in it, those are wildcards
66+
to allow multiple matches. -->
67+
<!ELEMENT rtoses (rtos*)> <!ATTLIST rtoses
68+
chipVendor CDATA #REQUIRED>
69+
<!-- Rtos defines an rtos by name, optionally the chip it is
70+
for (e.g. BSP/HAL), optionally the board it is for (e.g.
71+
BSP/HAL), optionally a symbol match (to verify in the current
72+
application), and an optional description. It also has the
73+
link to the XML file with the details. Note that the rtos
74+
XML file may be a shared file with more than one rtos in it,
75+
so the consumer must look for the matching rtos by name.
76+
If the name has a "*" or "?" in it, those are wildcards
77+
to allow multiple matches.
78+
The chip and board may have "*" or "?" for matching as well.
79+
The sym_match attribute allows matching automatically based
80+
on a symbol name in the current application (to load). -->
81+
<!ELEMENT rtos (EMPTY)> <!ATTLIST rtos
82+
name CDATA #REQUIRED
83+
xml_file CDATA #REQUIRED
84+
chip CDATA #REQUIRED
85+
board CDATA #REQUIRED
86+
sym_match CDATA #REQUIRED
87+
description CDATA #IMPLIED>
88+

0 commit comments

Comments
 (0)