구차니의 잡동사니 모음

CMSIS Drivers No CMSIS-Driver in Device Family Pack.

CMSIS-RTOS Blinky     EK-TM4C1294XL

CMSIS-RTOS Blinky     DK-TM4C129x 

Description

CMSIS provides additional debug functions to enlarge the Debug Access. Data can be transmitted via a certain global buffer variable towards the target system.

The Cortex-M3 / Cortex-M4 / Cortex-M7 incorporates the Instrumented Trace Macrocell (ITM) that provides together with the Serial Viewer Output (SVO) trace capabilities for the microcontroller system. The ITM has 32 communication channels; two ITM communication channels are used by CMSIS to output the following information:

ITM Channel 0: implements the ITM_SendChar function which can be used for printf-style output via the debug interface.

ITM Channel 31: is reserved for the RTOS kernel and can be used for kernel awareness debugging. 

• Advanced emulation controller provides high performance
• Supports Embedded Trace Buffer (ETB) on selected TI devices
• Operates off PC/laptop USB port, no internal adapter required
• 14-pin JTAG header 

Device Support

Please check your datasheet for details. The Embedded Trace buffer is available and has been used on the below example devices:

• ARM926: DM644x, DM646x, DM33x, DM35x, DM36x, OMAP-L13x, AM17x, AM18x.
• ARM11: OMAP2420, OMAP2430
• Cortex-A: all AM devices (AM335x, AM35xx, AM37xx, AM38xx), DM37xx, DM81xx, OMAP34xx, OMAP35xx, OMAP44x.
• Selected C6000 devices: TNETV3020, TCI648x, TCI66xx, C66xx
• DSP+ARM: C6A816x (single shared ETB)
• Devices with NO ETB support: Cortex-M, Cortex-R, C645x, C642x, DM64x, DM643x, C64x, C62x, C67x, C55x, C54x, C28x, C24x. 

– Full-featured debug solution

• Serial Wire JTAG Debug Port (SWJ-DP)

• Flash Patch and Breakpoint (FPB) unit for implementing breakpoints

• Data Watchpoint and Trigger (DWT) unit for implementing watchpoints, trigger resources,

and system profiling

• Instrumentation Trace Macrocell (ITM) for support of printf style debugging

• Trace Port Interface Unit (TPIU) for bridging to a Trace Port Analyzer

C2000 Real-time Control MCUs are C28x-based 32-bit microcontrollers with a high-performance core and application-tuned peripherals designed for real-time control applications. 

Installation Instructions for CCStudio v4.x and the Spectrum Digital XDS510/XDS560v2 JTAG Emulator

Emulators XDS560v2, XDS510USB, XDS510USB-GALVANIC, XDS510USB-PLUS, C2000 XDS510LC, XDS510PP+, SPI515, SPI525

Processors ARM7, ARM9, ARM11, F2400, F2800, C54x, C55x, C62x, C64x, C64x+, C67x, Cortex

Starter Kits DSK5416, DSK5510, DSK6713, DSK6416, DSK6455, DSKTCI6482, eZdsp2400,eZdsp2800 

**** Build of configuration Debug for project test ****

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all 

'Building file: ../hello.c'

'Invoking: C2000 Compiler'

"C:/ti/ccsv5/tools/compiler/c2000_6.2.0/bin/cl2000" -v28 -ml -mt --include_path="C:/ti/ccsv5/tools/compiler/c2000_6.2.0/include" -g --diag_warning=225 --display_error_number --diag_wrap=off --preproc_with_compile --preproc_dependency="hello.pp"  "../hello.c"

'Finished building: ../hello.c'

' '

'Building target: test.out'

'Invoking: C2000 Linker'

"C:/ti/ccsv5/tools/compiler/c2000_6.2.0/bin/cl2000" -v28 -ml -mt -g --diag_warning=225 --display_error_number --diag_wrap=off -z -m"test.map" --stack_size=0x300 --warn_sections -i"C:/ti/ccsv5/tools/compiler/c2000_6.2.0/lib" -i"C:/ti/ccsv5/tools/compiler/c2000_6.2.0/include" --reread_libs --display_error_number --diag_wrap=off --xml_link_info="test_linkInfo.xml" --rom_model -o "test.out"  "./hello.obj" "../2808_RAM_lnk.cmd" -l"rts2800_ml.lib" 

<Linking>

warning #10247-D: creating output section ".cio" without a SECTIONS specification

warning #10247-D: creating output section ".sysmem" without a SECTIONS specification

warning #10210-D: creating ".sysmem" section with default size of 0x400; use the -heap option to change the default size

"../2808_RAM_lnk.cmd", line 111: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".text" size 0x189c page 0.  Available memory ranges:

   PRAMH0       size: 0x1000       unused: 0x1000       max hole: 0x1000    

error #10010: errors encountered during linking; "test.out" not built

>> Compilation failure

gmake: *** [test.out] Error 1

gmake: Target `all' not remade because of errors.

**** Build Finished ****

SECTIONS

{

   /* Setup for "boot to SARAM" mode: 

      The codestart section (found in DSP28_CodeStartBranch.asm)

      re-directs execution to the start of user code.  */

   codestart        : > BEGIN,     PAGE = 0

   ramfuncs         : > RAMM0      PAGE = 0  

   .text            : > PRAMH0,    PAGE = 0

   .cinit           : > RAMM0,     PAGE = 0

   .pinit           : > RAMM0,     PAGE = 0

   .switch          : > RAMM0,     PAGE = 0

   .reset           : > RESET,     PAGE = 0, TYPE = DSECT /* not used, */

   .stack           : > RAMM1,     PAGE = 1

   .ebss            : > DRAMH0,    PAGE = 1

   .econst          : > DRAMH0,    PAGE = 1      

   .esysmem         : > RAMM1,     PAGE = 1

   IQmath           : >  PRAMH0,   PAGE = 0

   IQmathTables     : >  BOOTROM, type = NOLOAD, PAGE = 0

} 

 This is because the "printf" command used in the "hello world" project takes a large amount of memory which is not available on the 2812 devices. The 281x linker command file, 2812_RAM_lnk.cmd, by default does not define enough memory for code (.text) to support the "printf" command.

For getting started on the 2812, users should instead start with the CCSv4 peripheral examples in the 2812 C/C++ Header Files and Peripheral Examples software package. A good "first project" to get started with is the "cpu timer" project following the same instructions on this wiki page as were used for 2833x devices.

//#include <stdio.h>

/*

 * hello.c

 */

int main(void) {

// printf("Hello World!\n");

return 0;

}

 Spectrum Digital Configuration and Diagnostic Utility

Supports:

Printer Port: XDS510PP, XDS510PP+, SPI515, eZdsp

ISA Bus:      SPI510, XDS510

PCI Bus:      SPI525

USB Bus:      XDS510-USB

** Using emulation application from directory c:\ccstudio_v3.3\drivers

** Checking for a valid emulator/eZdsp

  $$ You are connected to:

  $$ EmuProductName=XDS510USB

  $$ EmuPortAddr=0x510

  $$ EmuPortMode=USB

  $$ ProductId=510

  $$ ProductVersion=84

** Checking emulator/eZdsp scan connection

** Emulator Test **

 $$ EmuProductName=XDS510USB

 $$ EmuPortAddr=0x510

 $$ EmuPortMode=USB

 $$ ProductId=510

 $$ ProductVersion=84

 ** Emulator Scan Test

  >> Check power to your emulator/eZdsp

  >> Then check your port mode/address

Applies to Windows installations CCSv4 and higher:

---------------------------------------------------

xds510usb and xd510usb_win64 files have been removed and replaced with signed

windows drivers and placed in:

Program Files\SpectrumDigital\Emulation\Drivers for 32-bit Windows and

Program Files (x86)\SpectrumDigital\Emulation\Drivers for 64-bit Windows

During the CCS installation process windows system level drivers are quietly 

pre-installed.  On Vista, the system level drivers install may not succeed as 

security checks may block the install.  When you plug in a USB HW device if 

Vista does not automatically find the USB drivers then the install did not 

succeed and you have two options:

1) When the install Wizard cannot find the drivers simply have the Wizard 

search the directories listed above with the search subdirectory check box 

checked.

2) Manually pre-install the drivers before plugging in the USB HW.  

To do this use Explorer and go to the appropriate driver directory listed 

above and the appropriate subdirectory, i386 for 32-bit Windows or amd64 for 

64-bit Windows and run DPInst.exe.  If you are not sure if drivers were

pre-installed during the CCS install you can safely run DPInst.exe again.