diff --git a/configs/launchxl-cc1310/README.txt b/configs/launchxl-cc1310/README.txt index 2f06a3c116..7d1b0bef86 100644 --- a/configs/launchxl-cc1310/README.txt +++ b/configs/launchxl-cc1310/README.txt @@ -10,6 +10,7 @@ Contents o Status o Serial Console o LEDs and Buttons + o Using J-Link Status ====== @@ -32,7 +33,23 @@ LEDs and Buttons LEDs ---- - Buttons ------- +Using J-Link +============ + + Reference https://wiki.segger.com/CC1310_LaunchPad (for CC1310) + + When shipped, the TI CC1310 LaunchPad evaluation board is configured to be + used with the on-board debug probe. In order to use it with J-Link, the + on-board debug probe needs to be isolated to make sure that it does not + drive the debug signals. This can be done by removing some jumpers next + to the XDS110 Out / CC1310 In connector [RXD, TXD, RST, TMS, TCK, TDO, TDI, + WDO]. After isolating the on-board probe, the CC130F128 device can be + debugged using J-Link. Please note, that the J-Link needs to be connected + to the board using the CC1310 using the micro JTAG connector marked "In". + + The RXD/TXD can then be used for a Serial console using the appropriate + TTL adapter (TTL to RS-232 or TTL to USB serial). + diff --git a/configs/launchxl-cc1312r1/README.txt b/configs/launchxl-cc1312r1/README.txt index b514766d00..f59055602d 100644 --- a/configs/launchxl-cc1312r1/README.txt +++ b/configs/launchxl-cc1312r1/README.txt @@ -11,6 +11,7 @@ Contents o LEDs and Buttons o Version 1 or 2? o Running from SRAM + o Using J-Link Status ====== @@ -19,6 +20,15 @@ Status of this board support is simply to assist in the CC13xx architecture development. Serious board development will occur later. Board support is missing LED and button support. + 2019-02-10: Figured out how to connect J-Link and began debug. First + failure is in tiva_configgpio() while trying to configure the console + UART pins. The failure is a hardfault apparently generated by: + + 109 regval = getreg32(TIVA_GPIO_DOE); + + The GPIO base address and DOE register offset seem to be okay. Must + be some issue with powering up the GPIO? The TI code calls Power_init() + which has not yet be brought into NuttX. Could this be the issue? Serial Console ============== @@ -32,10 +42,48 @@ LEDs and Buttons LEDs ---- + The LaunchXL-cc1312R1 and two LEDs controlled by software: DIO7_GLED (CR1) + and DIO6_RLED (CR2). A high output value illuminates an LED. + + DIO7_GLED CR1 High output illuminuates + DIO6_RLED CR2 High output illuminuates + + If CONFIG_ARCH_LEDS is not defined, then the user can control the LEDs in + any way. The definitions provided in the board.h header file can be used + to access individual LEDs. + + These LEDs are not used by the board port unless CONFIG_ARCH_LEDS is + defined. In that case, the usage by the board port is defined in + include/board.h and src/cc1312_autoleds.c. The LEDs are used to encode + OS-related events as follows: + + SYMBOL Meaning LED state + GLED RLED + ------------------ ------------------------ ------ ------ + LED_STARTED NuttX has been started OFF OFF + LED_HEAPALLOCATE Heap has been allocated OFF ON + LED_IRQSENABLED Interrupts enabled OFF ON + LED_STACKCREATED Idle stack created ON OFF + LED_INIRQ In an interrupt N/C GLOW + LED_SIGNAL In a signal handler N/C GLOW + LED_ASSERTION An assertion failed N/C GLOW + LED_PANIC The system has crashed OFF Blinking + LED_IDLE MCU is is sleep mode Not used + + Thus iF GLED is statically on, NuttX has successfully booted and is, + apparently, running normally. A soft glow of the RLED means that the + board is taking interrupts. If GLED is off and GLED is flashing at + approximately 2Hz, then a fatal error has been detected and the system + has halted. Buttons ------- + The LaunchXL-CC1312R1 has two push-puttons: + + DIO13_BTN1 SW1 Low input sensed when depressed + DIO14_BTN2 SW2 Low input sensed when depressed + Version 1 or 2? =============== @@ -62,3 +110,24 @@ Running from SRAM file in the scripts/ sub-directory. Based on those configuration settings, either scripts/flash.ld or sram.ld will be selected as the linker script file to be used. + +Using J-Link +============ + + Reference https://wiki.segger.com/CC1310_LaunchPad (for CC1310) + + When shipped, the TI CC1312R1 LaunchPad evaluation board is configured to be + used with the on-board debug probe. In order to use it with J-Link, the + on-board debug probe needs to be isolated to make sure that it does not + drive the debug signals. This can be done by removing some jumpers next + to the XDS110 Out / CC1310 In connector [RXD, TXD, RST, TMS, TCK, TDO, TDI, + WDO]. After isolating the on-board probe, the CC1312R1 device can be + debugged using J-Link. Please note, that the J-Link needs to be connected + to the board using the CC1312R1 using the micro JTAG connector marked + "Target In". + + NOTE: When connecting the J-Link, the interface must be set to JTAG, not + SWD as you might expect. + + The RXD/TXD can then be used for a Serial console using the appropriate + TTL adapter (TTL to RS-232 or TTL to USB serial).