구차니의 잡동사니 모음

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.  

Warning: Spectrum Digital XDS510USB drivers are included with the installation of CCS v4/v5

Deprecation notices:

The 32-bit version of Code Composer Studio for Linux is discontinued in favor of a 64-bit version since CCSv6.2.0.

Windows XP support is deprecated with the release of CCSv7.0.0.

Spectrum Digital XDS510USB JTAG debuggers are not supported with 64bit CCS installations. Currently this impacts Linux and MacOS.

Stellaris (LM3S and LM4F) devices are not supported starting with CCSv7.0.0. 

Simply unzip and copy the License File for Older versions into <install dir>/ccs_base/DebugServer/license.

What is not supported

• Serial Wire Output for TPIU trace output
  

• Standard Console I/O operations (fread, fwrite, fopen, etc.) are not yet supported on the current release of CCS when using the on-board emulator

//=======================================================

//  Structural coding

//=======================================================

assign reset_n = 1'b1; 

You need change in Pin Planner:

DRAM_LDQM to DRAM_DQM[0]

DRAM_UDQM to DRAM_DQM[1]

and

DRAM_BA_0 to DRAM_BA[0]

DRAM_BA_1 to DRAM_BA[1]

And then, you can assign these pins to your Nios II as buses.

DRAM_DQM[1..0]

DRAM_BA[1..0]

You must do this because Nios II in SOPC Builder 9.1 SP2 has buses for these connections to the SDRAM  

Nios® II Boot from EPCQ or EPCS in Quartus® II 13.1

Workaround/Fix

3.      Make sure the Nios II’s Reset Vector is pointing at EPCS/EPCQ Controller. 

Nios II Processor Application Copied from EPCS Flash to RAM Using Boot Copier

The EPCS address space is not mapped into the Altera Avalon EPCS Flash Controller’s Avalon MM slaveinterface. Instead, read or write accesses are done through CSRs. Upon system reset, the EPCS device needs to be initialized before usage.

For these reasons, the EPCS controller-based boot copier is required for initializing the EPCS device and copying the Nios II application to RAM for execution.

The EPCS controller instantiates a block of boot ROM internally at its base address (offset 0x0, just before EPCS controller’s CSRs) for storing the boot copier. Nios II reset vector offset must set to EPCS controller base address, such that upon system reset the boot copier is executed first to initialize the EPCS controller and device.