F28027 USB Stick Lab1_3

Transcription

1 F28027 USB Stick Lab1_3 Blink LED LD2 (GPIO34) CPU Timer 0 Interrupt Service FLASH based standalone version 1. Project Dependencies The project expects the following support files: Support files of controlsuite installed in: C:\TI\controlSUITE\device_support\f2802x\v127 Code Generation Tools Version 5.2.7: CodeComposerStudio Version 4.1.3: DSP 2802x October 2010 Frank Bormann Revision 5.2 Texas Instruments Inc.

2 Project Objective 2. Project Objective Blink LD2 (GPIO34) at the F28027 USB stick. Time base generated by CPU Timer 0 at 50 milliseconds. Full PIE hardware interrupt system, active CPU-Timer0 ISR (PIE 1.7). Watchdog Timer active. empty main while(1) -loop. FLASH based standalone version, code starts directly after RESET 3. Hardware Setup No special setup required. Connect the F28027 USB stick to your computer. The LED LD1 (green) of the F28027 USB stick should be on. 4. Start Code Composer Studio V4 Start Code Composer Studio V4: When CCS loads, a dialog box will prompt you for the location of a workspace folder. Use the default location for the workspace and click OK. This folder contains all CCS custom settings, which includes project settings and views when CCS is closed so that the same projects and settings will be available when CCS is opened again. The workspace is saved automatically when CCS is closed. Note: The first time CCS opens a Welcome to Code Composer Studio v4 page appears. Close the page by clicking on the CCS icon in the upper right or by clicking the X on the Welcome tab. You should now have an empty workbench. The term workbench refers to the desktop development environment. The workbench will open in the C/C++ Perspective view. Notice the C/C++ icon in the upper right-hand corner. A perspective defines the initial layout views of the workbench windows, toolbars, and menus which are appropriate for a specific type of task (i.e. code development or debugging). The C/C++ Perspective is used to create or build C/C++ projects. A Debug Perspective view will automatically be enabled when the debug session is started. Page - 2 DSP Lab1_3

3 Project Modification 5. Project Modification We will use the project Lab1 as starting point. If not still open in CCSV4, open this project again Create a new code file Open file Lab1_2.c and save it as Lab1_3.c. Right click at file Lab1_2.c and select Exclude File(s) from Build : 5.2. Link Files to Project In the project window, right click at Lab1 and select Link Files to Project : In this exercise we will install a FLASH based version of Lab1_2.c. This requires a connection of all code sections to non-volatile memory. Instead of changing the existing linker command file 28027_RAM_lnk.cmd we will link a different linker command file F28027.cmd to the project. Link: C:\TI\controlSUITE\device_support\f2802x\v127\DSP2802x_common\cmd\F28027.cmd Exclude the file 28027_RAM_lnk.cmd from build: DSP Lab1_3 Page - 3

4 Code Modification 6. Code Modification 6.1. Modify file Lab1_3.c At the beginning of the file add a new external function prototype for InitFlash() from file DSP2802x_sysCtrl.c. This function is used to reduce the FLASH access wait states to minimum and to enable the FLASH code pre-fetch pipeline. Also add 3 external symbol references to symbols, which are defined in the new linker command file F28027.cmd : extern void InitFlash(void); extern Uint16 RamfuncsLoadStart; extern Uint16 RamfuncsLoadEnd; extern Uint16 RamfuncsRunStart; At the beginning of function main(), add two new pointer variables to copy a code section from FLASH to RAM. The function InitFlash() cannot be executed from FLASH, because this function changes the access speed. Therefore, we have to copy this function from FLASH to RAM, before we can actually cal it. Add: unsigned long * psourceaddr; unsigned long * pdestaddr; Now, just after the call of function InitSysCtrl(), add a for-loop to copy the FLASH section into RAM. Also add the loop counter variable i at the beginning of main() : psourceaddr = (unsigned long *)&RamfuncsLoadStart; pdestaddr = (unsigned long *)&RamfuncsRunStart; for(i=0; i<(1+&ramfuncsloadend - &RamfuncsLoadStart)/2; i++) *pdestaddr++ = *psourceaddr++; After this copy loop, call function InitFlash() after the previous for - loop: InitFlash(); Finally, change the frequency for CPU Timer 0 to 50 milliseconds. Change the existing function call: ConfigCpuTimer(&CpuTimer0, 60, 50000); 6.2. Rebuild Project Project Rebuild Active Project (Alt + Shift + P) Look for any error messages or warnings and make changes, if necessary. Target Debug Active Project Note: Since the project now includes also FLASH based sections, the start of a new Debug session will not only load RAM based sections but also re-program all FLASH based sections, which are used by the project. This step can take a few seconds. If you like, you can Page - 4 DSP Lab1_3

5 Code Modification follow the activities by expanding the Detail button in the Progress Information window (see next page): After a successful programming of the device, the Debug perspective should come up and the blue arrow in window Lab1_3.c should point to the beginning of main(). Now perform a Run (F8)! The LED should blink with a period of approximately 50 milliseconds. Stop the execution. To verify that the code is actually executed from FLASH after a RESET, do: Target Reset Reset CPU Scripts EMU Boot Mode Select EMU_BOOT_FLASH Target Run (F8) The LED should blink again with a period of 50 milliseconds Standalone Test Stop the debug execution ( Target Terminate All) Close Code Composer Studio Disconnect the F28027 USB stick from your computer Reconnect the F28027 USB stick back to your computer The LED blink program should start immediately; it is now executed from FLASH. DSP Lab1_3 Page - 5

6 Solution for Lab1_3.c 7. Solution for Lab1_3.c #include "DSP2802x_Device.h" extern void InitSysCtrl(void); extern void InitPieCtrl(void); extern void InitPieVectTable(void); extern void InitCpuTimers(void); extern void ConfigCpuTimer(struct CPUTIMER_VARS *,float,float); extern void InitFlash(void); extern Uint16 RamfuncsLoadStart; extern Uint16 RamfuncsLoadEnd; extern Uint16 RamfuncsRunStart; interrupt void cpu_timer0_isr(void); void main(void) { unsigned long i; unsigned long * psourceaddr; unsigned long * pdestaddr; InitSysCtrl(); // Basic Core Initialization psourceaddr = (unsigned long *)&RamfuncsLoadStart; pdestaddr = (unsigned long *)&RamfuncsRunStart; for(i=0; i<(1+&ramfuncsloadend - &RamfuncsLoadStart)/2; i++) *pdestaddr++ = *psourceaddr++; InitFlash(); InitPieCtrl(); // Basic PIE initialization InitPieVectTable(); // Setup vector table EALLOW; // Open access to seruce registers SysCtrlRegs.WDCR = 0x00AF; // Re - enable Watchdog GpioCtrlRegs.GPBDIR.bit.GPIO34 = 1; // output for LED LD2 PieVectTable.TINT0 = &cpu_timer0_isr; // replace timer 0 entry EDIS; InitCpuTimers(); ConfigCpuTimer(&CpuTimer0, 60, 50000); PieCtrlRegs.PIEIER1.bit.INTx7 = 1; //enable CPU_Timer 0 ISR IER = 1; // enable core line INT1 EINT; // enable global interrupt INTM ERTM; // Enable global real time DBGM CpuTimer0Regs.TCR.bit.TSS = 0; // start T0 while(1) { EALLOW; SysCtrlRegs.WDKEY = 0x55; // 1st WD service instr EDIS; } } interrupt void cpu_timer0_isr(void) { GpioDataRegs.GPBTOGGLE.bit.GPIO34 = 1; // toggle LED PieCtrlRegs.PIEACK.all = 1; // ack PIE-group 1 EALLOW; SysCtrlRegs.WDKEY = 0xAA; // 2nd WD service instr EDIS; } Page - 6 DSP Lab1_3