Dev.notes

20170805: 16.04 Ubuntu update

simplelink-sdk_1_40_01_00  (3100 msp432 headers)
JLink (Segger), V6.16j (6.16.10)
ti_emupack_setup_7.0.48.0_linux_x86_64.bin:

msp432-gcc-1.2.0.1-linux-x64-support-package-installer.run:
  3001 headers
msp432-gcc-support-files.zip:
  3001 headers

(see ~/mm/w/new for more details)


20070310: Various Updates

Installed

* ti_emupack_setup_6.0.579.0_linux_x86_64.bin
      -> /opt/ti/ti-emu
* msp432-gcc-1.1.0.1-linux-x64-support-package-installer.run
      -> /opt/ti/ti-arm-lsp
* CCS7.1.0.00014_web_linux-x64.tar.gz
      -> /opt/ti/ccs/ccsv7

New TI XDS110 standalone probe.
XDS110 (02.03.00.05) Probe with CMSIS-DAP
SerialNumber: 00000000
creates two ACM tty devices
0451:BEF3
Texas Instruments XDS110 (02.03.00.05) Probe with CMSIS-DAP


XDS110-ET on MSP-EXP432P401R Launchpad dev board (dev6a)
XDS110 (02.03.00.07) Embed with CMSIS-DAP
SerialNumber: M4321005
creates two ACM tty devices
0451:BEF3
Texas Instruments XDS110 (02.03.00.07) Embed with CMSIS-DAP

New version of XDS Emulation Software (emupack): 6.0.579.0
http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package
ti_emupack_setup_6.0.579.0_linux_x86_64.bin

Firmware versions: for XDS110 (both -ET and -SA).
* /opt/ti/ti-arm-lsp/emulation/common/uscif/xds110: 2.3.0.2
* /opt/ti/ti-emu/ccs_base/common/uscif/xds110:      2.3.0.7
* /opt/ti/ccs/ccsv7/ccs_base/common/uscif/xds110:   2.3.0.7


* XDS Target Connection Guide
  http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide

* Launching TI GDB Server: gdb_agent_console
  (see: http://processors.wiki.ti.com/index.php/XDS_GDB_Agent)

  from: msp432-gcc-1.1.0.1-linux-x64-support-package-installer.run
  -->   /opt/ti-arm-lsp

  need xds110_msp432_{jtag,swd}.dat to feed to gdb_agent_console.
  xds110_msp432_*.dat shows up in:

    /opt/ti/ti-arm-lsp/emulation/common/uscif/xds110_msp432_{jtag,swd}.dat


  launch via:

    cd /opt/ti/ti-arm-lsp/emulation/common/uscif
    LD_LIBRARY_PATH=<see below>
    gdb_agent_console -f MSP432 xds110_msp432_jtag.dat
    gdb_agent_console [-p <port>] [-f <flash>]  <board data file>

    (run just gdb_agent_console to get help)

    gdb server port   localhost:55000

  wants LD_LIBRARY_PATH to include ccs_base/emulation/drivers and
  ccs_base/emulation/analysis/bin.  we see:

  /opt/ti/ti-arm-lsp/emulation/emulation/drivers
  /opt/ti/ti-emu/ccs_base/emulation/drivers
  /opt/ti/ccs/ccsv7/ccs_base/emulation/drivers
        and
  /opt/ti/ti-emu/ccs_base/emulation/analysis/bin
  /opt/ti/ccs/ccsv7/ccs_base/emulation/analysis/bin


* Using TI GDB Server

  s/w breakpoints not supported in flash.  need to use hbreak.


Using new XDS110 Debug Probe with the Dev6a (MSP-EXP432P401R):

Connect the 20 pin debug cable to the debug port on the XDS110 (right
connector, .05 20 pin connector).  Connect the 20 pin to 10 pin ARM Cortex
.05 adapter.  It is keyed.  Notice that the 10 pin connector is marked with
a side labelled "1 2".  This side gets mated to J8 on the launch pad such
that the 1/2 on the adapter lines up with the 1/2 on the J8 connector.  The
cable will run across the launchpad on top of the msp432p401r chip on the
board.


You need Openocd to use the XDS110 with GDB.

OpenOcd: https://sourceforge.net/projects/openocd/files/openocd/0.10.0/
docs: https://sourceforge.net/projects/openocd/files/openocd/0.10.0/openocd.pdf/download

Using OpenOcd:

Connect the XDS110 as above.

You will also need an openocd.cfg file in the same place as what you are
debugging.  It needs to contain:

    source [find interface/cmsis-dap.cfg]
    source [find target/ti_msp432p4xx.cfg]

then run openocd as:

    openocd -f openocd.cfg


Still doesn't seem to work very well.  Very slow on the XDS110-ET and haven't
gotten it to work on the XDS110 standalone pod.


Other installation steps for VM:

1) update python setuptools
   pip install -U setuptools

2) install pyocd
   pip install --pre -U pyocd


===========================================================================

XDS110:
    http://processors.wiki.ti.com/index.php/XDS110

    the xds110-et is the onboard jtag pod on the msp-exp432p401r launchpad
    dev board.

    Black LP: SN 0, fw: 02.02.04.00
    Red LP: SN M4321005, fw: 02.02.05.01
    update to 02.03.00.02

XDS110 is OpenOCD ready (0.8 and above)


Firmware Updating:

Black LP: 0451/bef3 normal XDS110 (02.02.04.00) with CMSIS-DAP, sn 00000000
      dfu 1cbe/00ff Tiva Device Firmware Update
      Luminary Micro Inc. Stellaris ROM DFU Bootloader
Red LP:   0451/bef3 normal XDS110 (02.02.05.01) with CMSIS-DAP, sn M4321005
      dfu 1cbe/00ff Tiva Device Firmware Update


*** NXP LPC Link 2

LPC4370dfeT100 - main processor
lpcscript 1.8.0_723 linux



Install of msp432-gcc-1.0.0.1-linux-support-package into /opt/ti-arm has binaries
that need execute permission to run.

*** /opt/ti-arm moved to /opt/ti/ti-arm-lsp

    /opt/ti-arm/emulation/common/uscif/gdb_agent_console
    /opt/ti-arm/emulation/common/uscif/dbgjtag
    /opt/ti-arm/emulation/common/uscif/xds110/xds110reset
    /opt/ti-arm/emulation/common/uscif/xds110/xdsdfu

Install of ti_emupack_setup_6.0.407.3_linux results in binaries set to mode 777.
install into /opt/ti-emu.

*** /opt/ti-emu moved to /opt/ti/ti-emu

What version of the xds110 firmware is supplied by the various packages:
(would be nice if there was a reasonable way to identify the fw version)

ti-arm/emulation/common/uscif/xds110/xdsdfu             (has _{jtag,swd}.dat)
        Apr 28 06:31 firmware.bin       02.03.00.01
ti/ccsv6/ccs_base/common/uscif/xds110/xdsdfu (6.1.3, 6.2.0.48)
        Aug  3 14:55 firmware.bin       02.03.00.02
ti-emu/ccs_base/common/uscif/xds110/xdsdfu
        Aug  3 14:55 firmware.bin       02.03.00.02


TI GDB proxy is gdb_agent_console:

  zot (32): pwd
  /home/cire/ti/ccsv6/ccs_base/common/uscif
  zot (33): ./gdb_agent_console --help
  Usage: xds_gdb_agent [-p <port>] [-f <flash>] <board-data-file>

  Library dependencies:

zot (39): strace ./gdb_agent_console -f MSP432 /opt/ti-arm-lsp/emulation/common/uscif/xds110_msp432_jtag.dat
looks in ., ./tls, ./x86_64, ../../common/uscif/{.,tls,x86_64}, ../../common/bin/{...}
         ../../DebugServer/{bin,drivers}/{...}, ../../emulation/analysis/bin/{...}


CMSIS:
    Keil, http://www.keil.com/pack/doc/CMSIS/General/html/index.html


Flashing XDS110:  (/opt/ti/ccsv6/common/uscif/xds110/xdsdfu)
    xdsdfu -f firmware.bin -r


Segger:
    Jlink (non-clone) 1366/0101 S/N 000269400672

    Ozone (gui debugger)

    Install JLink support into CCS:
        https://www.segger.com/ti-code-composer-studio.html#ccs6


Projects and Build Handbook:
    http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS
Debug Handbook for CCS:
    http://processors.wiki.ti.com/index.php/Debug_Handbook_for_CCS
SWO Trace:
    http://processors.wiki.ti.com/index.php/SWO_Trace
SWO/CCS/Hardware Trace:
    http://www.ti.com/lit/an/slaa674a/slaa674a.pdf


Code Composer

Code Composer maybe used for advanced tracing, program flow, and energy trace.
This hasn't been evaluated yet.

It is also used to snag current data files from the CCS tree.  It is manually
installed into either your home dir or into the vagrant home.  There are
various install issues if installed as root.  It should get installed as
/home/vagrant/ti/ccsv6.