Tool/software: Code Composer Studio
Hello
I want to store a limited number of sampled data of the incoming SDFM signal in DSP and then export them into a file (for example excel file). What is the simplest way? The method should be fast enough to store the data in a rate of fs=50kHz.
Regards
I don't think copying those lines is necessary or a good way to proceed. It's possible you may need to read through the basics of linker command files in chapter 8 of the Assembly Language Tools Guide:
However, the attached is an extract from the draft DCL v4.0 user's guide which steps you through how to add data logging capability to your code. I recommend you simply follow these steps. Feel free to post back if there's anything which isn't clear.
Regards,
Richard
Hello Richard
I have read the "DCL V4.9 User's Guide" and also important part of spru513 relating to the MEMORY and SECTIONS.
I have followed the instruction of "DCL V4.9 User's Guide".
I imported a simple project to CCS :
C:\ti\c2000\C2000Ware_DigitalPower_SDK_1_01_00_00\c2000ware\device_support\f2837xd\examples\cpu1\blinky\cpu01
then I have added "2837xD_RAM_lnk_cpu1.cmd" file from below path to my project:
C:\ti\c2000\C2000Ware_DigitalPower_SDK_1_01_00_00\c2000ware\device_support\f2837xd\common\cmd
I aimed to add following code to this file:
"
MEMORY
{
…
RAML5 : origin = 0x00C000, length = 0x002000
…
}
SECTIONS
{
…
mySectionName : > RAML5, PAGE = 1 align(2)
…
}"
But before that, while I built the project, some errors occurred during linking. (I have attached a screenshot of the CCS which shows the errors)
It is worth noting that I didn't change the "2837xD_RAM_lnk_cpu1.cmd" file and just added it to blinky project! (this is one step before testing the FDLOG!)
Some screenshots of properties of my project are attached too.
I don't know why this errors occur!
Could you please guide me?
I have also attached modified blinky code i which I have added the instruction related to the FDLOG.
regards
//###########################################################################
//
// FILE: blinky_cpu01.c
//
// TITLE: LED Blink Example for F2837xD.
//
//! \addtogroup cpu01_example_list
//! <h1> Blinky </h1>
//!
//! This example blinks LED X
//!
//! \note If using a Launchpad, use the Launchpad build configurations.
//!
//
//###########################################################################
// $TI Release: F2837xD Support Library v3.04.00.00 $
// $Release Date: Sun Mar 25 13:26:04 CDT 2018 $
// $Copyright:
// Copyright (C) 2013-2018 Texas Instruments Incorporated - http://www.ti.com/
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions
// are met:
//
// Redistributions of source code must retain the above copyright
// notice, this list of conditions and the following disclaimer.
//
// Redistributions in binary form must reproduce the above copyright
// notice, this list of conditions and the following disclaimer in the
// documentation and/or other materials provided with the
// distribution.
//
// Neither the name of Texas Instruments Incorporated nor the names of
// its contributors may be used to endorse or promote products derived
// from this software without specific prior written permission.
//
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
// $
//###########################################################################
//
// Included Files
//
#include "F28x_Project.h"
#include "DCL_fdlog.h"
#pragma DATA_SECTION(myBuffer, "test")
float32_t myBuffer[100];
FDLOG pLog = FDLOG_DEFAULTS;
//
// Defines
//
#define BLINKY_LED_GPIO 31
void main(void)
{
//
// Step 1. Initialize System Control:
// PLL, WatchDog, enable Peripheral Clocks
// This example function is found in the F2837xD_SysCtrl.c file.
//
InitSysCtrl();
//
// Step 2. Initialize GPIO:
// This example function is found in the F2837xD_Gpio.c file and
// illustrates how to set the GPIO to it's default state.
//
InitGpio();
GPIO_SetupPinMux(BLINKY_LED_GPIO, GPIO_MUX_CPU1, 0);
GPIO_SetupPinOptions(BLINKY_LED_GPIO, GPIO_OUTPUT, GPIO_PUSHPULL);
//
// Step 3. Clear all interrupts and initialize PIE vector table:
// Disable CPU interrupts
//
DINT;
//
// Initialize the PIE control registers to their default state.
// The default state is all PIE interrupts disabled and flags
// are cleared.
// This function is found in the F2837xD_PieCtrl.c file.
//
InitPieCtrl();
//
// Disable CPU interrupts and clear all CPU interrupt flags:
//
IER = 0x0000;
IFR = 0x0000;
//
// Initialize the PIE vector table with pointers to the shell Interrupt
// Service Routines (ISR).
// This will populate the entire table, even if the interrupt
// is not used in this example. This is useful for debug purposes.
// The shell ISR routines are found in F2837xD_DefaultIsr.c.
// This function is found in F2837xD_PieVect.c.
//
InitPieVectTable();
DCL_initLog(&pLog, myBuffer, 100);
//
// Enable global Interrupts and higher priority real-time debug events:
//
EINT; // Enable Global interrupt INTM
ERTM; // Enable Global realtime interrupt DBGM
//
// Step 6. IDLE loop. Just sit and loop forever (optional):
//
for(;;)
{
//
// Turn on LED
//
DCL_writeLog(&pLog, 1);
GPIO_WritePin(BLINKY_LED_GPIO, 0);
//
// Delay for a bit.
//
DELAY_US(1000*500);
//
// Turn off LED
//
GPIO_WritePin(BLINKY_LED_GPIO, 1);
//
// Delay for a bit.
//
DELAY_US(1000*500);
}
}
//
// End of file
//
Richard
I know that I should remove "Linker command file:" field.
But each time I remove it (select none), and click on "OK", in the next time I open the properties it appears again !!!
you can see it in the attached pictures.
