TM4C129X: Add custom system control header file (incomplete)

TODO

@@ -895,7 +895,21 @@ o Network (net/, drivers/net)
                CONFIG_NET_NOINTS).  This is really a very bad use of CPU
                resources;  All of the network stack processing should be more
                to a work queue (and, all use of CONFIG_NET_NOINTS=n should
-               be eliminated).
+               be eliminated).  This applies to almost all Ethernet drivers:
+
+               ARCHITECTURE   CONFIG_NET_NOINTS
+               C5471          NO
+               STM32          NO
+               TIVA           NO
+               eZ80           NO
+               LPC17xx        YES << Only this one supports CONFIG_NET_NOINTS
+               DMxxx NIC      NO
+               PIC32          NO
+               RGMP           NO
+               SAM3/4         NO
+               SAMA5D         NO
+               SIM            NO << Doesn't have interrupts anyway
+
   Status:      Open
   Priority:    Pretty high if you want a well behaved system.
 

arch/arm/src/tiva/chip/tiva_syscontrol.h

@@ -49,6 +49,8 @@
 #  include "chip/lm3s_syscontrol.h"
 #elif defined(CONFIG_ARCH_CHIP_LM4F)
 #  include "chip/lm4f_syscontrol.h"
+#elif defined(CONFIG_ARCH_CHIP_TM4C129XNC)
+#  include "chip/tm4c129x_syscontrol.h"
 #elif defined(CONFIG_ARCH_CHIP_TM4C)
 #  include "chip/tm4c_syscontrol.h"
 #elif defined(CONFIG_ARCH_CHIP_CC3200)

arch/arm/src/tiva/tiva_syscontrol.h

@@ -85,7 +85,7 @@ void tiva_clockconfig(uint32_t newrcc, uint32_t newrcc2);
  * Name: up_clockconfig
  *
  * Description:
- *   Called early in the bootsequence (before .data and .bss are available)
+ *   Called early in the boot sequence (before .data and .bss are available)
  *   in order to configure initial clocking.
  *
  ****************************************************************************/

configs/dk-tm4c129x/README.txt

@@ -25,13 +25,8 @@ README.txt
       memories, parallel peripherals, and other system functions. 
     - In-Circuit Debug Interface (ICDI)
 
-On-Board GPIO Usage
-===================
-
-  [To be provided]
-
-Using OpenOCD and GDB with an FT2232 JTAG emulator
-==================================================
+Using OpenOCD and GDB with ICDI
+===============================
 
   Building OpenOCD under Cygwin:
 
@@ -377,8 +372,25 @@ Buttons and LEDs
 Serial Console
 ==============
 
-  [To be provided]
+  By default, all configurations use UART0 which connects to the USB VCOM
+  on the DEBUG port on the TM4C123 ICDI interface:
 
+    UART0 RX - PA.0
+    UART0 TX - PA.1
+
+  However, if you use an external RS232 driver, then other options are
+  available.  If your serial terminal loses connection with the USB serial
+  port each time you power cycle the board, the VCOM option can be very
+  painful.
+
+  UART0 TTL level signals are also available at J3 (also at J1):
+
+    DEBUG_TX - J3, pin 13.  Labelled PA1
+    DEBUG_RX - J3, pin 15.  Labelled PA0
+
+  Remove the jumper between pins 13-14 and 15-16 to disconnect UART0 from
+  the TM4C123 ICDI chip; Connect your external RS-232 driver at pins 13
+  and 16.  5v, 3.3v, AND GND are arvailable nearby at J10.
 
 DK-TM4129X Configuration Options
 ================================