aboutsummaryrefslogtreecommitdiff
path: root/include/libopencm3/lm3s
diff options
context:
space:
mode:
authorAlexandru Gagniuc2012-11-21 20:39:36 -0600
committerAlexandru Gagniuc2012-12-31 01:35:25 -0600
commit326c945b55d6dd1cf153c6ca8715685a968b1384 (patch)
tree3b418fbc7f7894218120b43f1cf714d05ed42fd2 /include/libopencm3/lm3s
parent70746ccd676445481511c0e8bc6b617f7b052878 (diff)
lm4f: Add lm4f support files copied from lm3s
Create lm4f code infrastructure from the lm3s infrastructure. As far as the interrupt table is concerned, don't create an irq.yaml. Just include the LM3S nvic.h. The LM3S vector table seems to be compatible with the LM4F Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Diffstat (limited to 'include/libopencm3/lm3s')
-rw-r--r--include/libopencm3/lm3s/irq.yaml5
1 files changed, 5 insertions, 0 deletions
diff --git a/include/libopencm3/lm3s/irq.yaml b/include/libopencm3/lm3s/irq.yaml
index 7d5ff3a..15abb81 100644
--- a/include/libopencm3/lm3s/irq.yaml
+++ b/include/libopencm3/lm3s/irq.yaml
@@ -1,3 +1,8 @@
+# Although this says LM3S, the interrupt table applies to the LM4F as well
+# Some interrupt vectores marked as reserved in LM3S are used in LM4F, and some
+# vectors in LM3S are marked reserved for LM4F. However, the common vectors are
+# identical, and we can safely use the same interrupt table. Reserved vectors
+# will never be triggered, so having them is perfectly safe.
includeguard: LIBOPENCM3_LM3S_NVIC_H
partname_humanreadable: LM3S series
partname_doxygen: LM3S