Changes between Version 19 and Version 20 of cc135x

Timestamp:

08/12/2020 11:55:49 PM (4 years ago)

Author:

Cale Collins

Comment:

added note about connecting antenna, added note about rmmod ftdi_sio before programming, added section for DTR.

cc135x

@@ -33 +33 @@
  - TI Launchpad
   * These have an XDS110 JTAG Debugger on-board (implemented via the Tiva MCU chip). The XDS110 debugger exposes two USB ACM serial devices where the first one is tied directly to the CC13xx UART (pinout matching the 'serial downloader' pins specified in the TRM) and the second serial device is for JTAG programming. These boards can be programmed via the TI 'Uniflash' tool (GUI or stand-alone command-line) or the CCS IDE.
+
+** IMPORTANT **  Always have an antenna connected, without one the high power amplifier will glitch the board and cause a reset.
 
 References:
@@ -404 +406 @@
  * GW5910-C via IMX6 GPIO
 
+Before attempting to use the Gateworks Jtag programmer {{{sudo rmmod ftdi_sio}}}, without this step programming may fail.  
+
 Note that the OpenOCD package from Ubuntu lacks the necessary cc26xx flash driver so we must either build OpenOCD from source manually or use the Gateworks Ubuntu PPA:
  * Installing from Gateworks Ubuntu PPA:
@@ -611 +615 @@
   - make sure you point to the correct /dev/ttyUSB* device managed by the ftdi_sio driver
 
+== DTR
+
+Some board revisions will reqire DTR to be asserted before the board will come out of reset.  DTR is part of a UART policy dating back to the modem days where by default 'HUP' is enabled which will send a 'hangup' signal (via DTR or data-terminal-ready) when the last process closes the tty. In essence DTR# is driven high when no processes have the UART device open and driven low when any process has the UART device open. Unfortunately this is the wrong polarity to 'just work' in an obvious manner.
+
+You can manually control DTR in a number of ways:
+ * use {{{picocom}}} ([#picocom see below]) which allows you to toggle DTR via control commands
+ * use {{{stty}}} to disable HUP which will release DTR# and drive it high letting the CC1352P out of reset but not that terminal programs may put it back in reset if they control DTR.
+{{{#!bash
+# Find the tty associated with the GW16122 device in your system
+TTY=/dev/$(for i in $(ls -1d /sys/bus/usb/devices/*); do [ -r $i/interface ] && { [[ "$(cat $i/interface)" =~ "GW16122" ]] && basename $(ls -d $i/ttyUSB*); }; done)
+echo $TTY
+stty -F $TTY hup
+}}}
+ * write your own UART code that uses the TIOCMBIS and TIOSMBIS ioctl to manually control the modem signals:
+  - with a C application use an ioctl on the tty from termios.h:
+{{{#!c
+cat << EOF > dtr.c
+#include <errno.h>
+#include <fcntl.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
+#include <sys/ioctl.h>
+#include <sys/types.h>
+#include <sys/stat.h>
+
+int main(int argc, char **argv)
+{
+        int fd, line, assert;
+        const char *tty;
+
+        if (argc < 2) {
+                fprintf(stderr, "usage: %s <ttydev> <0|1>\n", argv[0]);
+                exit -1;
+        }
+
+        tty = argv[1];
+        assert = atoi(argv[2]);
+
+        /* open serial port */
+        fd = open(tty, O_RDWR | O_NOCTTY);
+        if (fd == -1) {
+                perror("open");
+                exit -errno;
+        }
+
+        /* perform IOCTL to set DTR */
+        line = TIOCM_DTR;
+        printf("%s: %s DTR#\n", tty, assert ? "assert" : "deassert");
+        if (ioctl(fd, assert ? TIOCMBIS : TIOCMBIC, &line) == -1) {
+                perror("ioctl");
+                close(fd);
+                exit (-errno);
+        }
+        close(fd);
+
+        return 0;
+}
+EOF
+}}}
+{{{#!bash
+gcc -c dtr.c -o dtr
+chmod +x dtr
+# Find the tty associated with the GW16122 device in your system
+TTY=/dev/$(for i in $(ls -1d /sys/bus/usb/devices/*); do [ -r $i/interface ] && { [[ "$(cat $i/interface)" =~ "GW16122" ]] && basename $(ls -d $i/ttyUSB*); }; done)
+echo $TTY
+# make sure a HUP will not be sent when a process does not have control over the TTY
+stty -F $TTY -hup
+# assert DTR# (drive low; hold part in reset)
+./dtr $TTY 1
+# deassert DTR# (drive high; release part from reset) 
+./dtr $TTY 0
+}}}
+  - use python-serial via a python script:
+{{{#!python
+cat << EOF > dtr
+#!/usr/bin/env python
+
+import serial
+import string
+import sys
+
+if len(sys.argv) < 3:
+    print("usage: %s <ttydev> <0|1>\n" % sys.argv[0])
+    exit(-1)
+
+dev=sys.argv[1]
+lvl=string.atoi(sys.argv[2])
+
+if lvl:
+    print("%s: assert DTR#\n" % dev)
+else:
+    print("%s: deassert DTR#\n" % dev)
+ser = serial.Serial(dev)
+ser.isOpen()
+ser.setDTR(lvl)
+ser.close()
+EOF
+}}}
+{{{#!bash
+apt install python python-serial
+chmod +x dtr
+# Find the tty associated with the GW16122 device in your system
+TTY=/dev/$(for i in $(ls -1d /sys/bus/usb/devices/*); do [ -r $i/interface ] && { [[ "$(cat $i/interface)" =~ "GW16122" ]] && basename $(ls -d $i/ttyUSB*); }; done)
+echo $TTY
+# make sure a HUP will not be sent when a process does not have control over the TTY
+stty -F $TTY -hup
+# assert DTR# (drive low; hold part in reset)
+./dtr $TTY 1
+# deassert DTR# (drive high; release part from reset) 
+./dtr $TTY 0
+}}}
+