3-phase sinusoidal PWM signal generation issues with TMSF28027

Hi Richard,

Thank you very much for your answer. I have controlSUITE in my computer and I've already opened the example you've mentioned; however, the target in this example is the TMS320F2803 DSP's and I'm currently using a TMS320F2802 MCU; is there an example designed for this family? Or how should I migrate from one target to the other?

Thanks again.

Regards,

Jorge

Richard,

I've seen the Devint initilisation file for the F2802x and it actually runs and doesn't present any problem to debug, however, I can't seem to visualize with the oscilloscope the generated PWM signals, as if the controller didn't do anything. I first thought it could be the motor-control driver files, since they are all for the F2803x family, but the controlSUITE does not provide the F2802x ones.

Also I read that these controlSUITE programs take into account a full kit for motor control provided by TI. The thing is that I only have the MCU and I wish to use my own inverter, but I don't know if, since the program doesn't detect the kit plugged into the MCU, that could be the reason why it seems do nothing (this happened to me while I was trying to use the InstaSPIN-FOC solution with the same microcontroller: since I didn't have any motor control kit, the MCU seemed to do nothing). Do you think one of these could be the problem?

Thank you very much for your help and advices.

Regards,

Jorge

Hi Richard,

I'm using the TMSF28027F.

The linker command file:

/*==================================================================================*/
/* User specific Linker command file for running from RAM */
/*==================================================================================*/
/* FILE: F28035_RAM_HVACI_Scalar.CMD */
/* */
/* Description: Linker command file for User custom sections targetted to run */
/* from RAM. */
/* */
/* Target: TMS320F28035 device */
/* */
/* Version: 1.00 */
/* */
/*----------------------------------------------------------------------------------*/
/* Copyright Texas Instruments © 2009 */
/*----------------------------------------------------------------------------------*/
/* Revision History: */
/*----------------------------------------------------------------------------------*/
/* Date | Description */
/*----------------------------------------------------------------------------------*/
/* 10/24/08 | Release 1.0 New release. */
/*----------------------------------------------------------------------------------*/

/* Define the memory block start/length for the DSP2803x
PAGE 0 will be used to organize program sections
PAGE 1 will be used to organize data sections

Notes:
Memory blocks on F28035 are uniform (ie same
physical memory) in both PAGE 0 and PAGE 1.
That is the same memory region should not be
defined for both PAGE 0 and PAGE 1.
Doing so will result in corruption of program
and/or data.

L0 block is mirrored - that is it
can be accessed in high memory or low memory.
For simplicity only one instance is used in this
linker file.

Contiguous SARAM memory blocks can be combined
if required to create a larger memory block.
*/

MEMORY
{
PAGE 0 :
/* Note that the memory allocation below does not create sections as necessary for
the CLA on the F2803x.
*/

BEGIN : origin = 0x000000, length = 0x000002
BOOT_RSVD : origin = 0x000002, length = 0x00004E
RAMM0 : origin = 0x000050, length = 0x0003B0

progRAM : origin = 0x008000, length = 0x001800

IQTABLES : origin = 0x3FE000, length = 0x000B50 /* IQ Math Tables in Boot ROM */
IQTABLES2 : origin = 0x3FEB50, length = 0x00008C /* IQ Math Tables in Boot ROM */
IQTABLES3 : origin = 0x3FEBDC, length = 0x0000AA /* IQ Math Tables in Boot ROM */

RESET : origin = 0x3FFFC0, length = 0x000002
BOOTROM : origin = 0x3FF27C, length = 0x000D44


PAGE 1 :

RAMM1 : origin = 0x000480, length = 0x000380

dataRAM : origin = 0x009800, length = 0x000800

CLA_CPU_MSGRAM : origin = 0x001480, length = 0x000080
CPU_CLA_MSGRAM : origin = 0x001500, length = 0x000080
}


SECTIONS
{
codestart : > BEGIN, PAGE = 0
ramfuncs : > RAMM0, PAGE = 0

.text : > progRAM, PAGE = 0

.cinit : > RAMM0, PAGE = 0
.pinit : > RAMM0, PAGE = 0
.switch : > RAMM0, PAGE = 0
.reset : > RESET, PAGE = 0, TYPE = DSECT

.stack : > RAMM1, PAGE = 1

.ebss : > dataRAM, PAGE = 1
.econst : > dataRAM, PAGE = 1

.esysmem : > RAMM1, PAGE = 1

IQmath : > progRAM, PAGE = 0
IQmathTables : > IQTABLES, PAGE = 0, TYPE = NOLOAD

Cla1ToCpuMsgRAM : > CLA_CPU_MSGRAM, PAGE = 1
CpuToCla1MsgRAM : > CPU_CLA_MSGRAM, PAGE = 1

/* Uncomment the section below if calling the IQNexp() or IQexp()
functions from the IQMath.lib library in order to utilize the
relevant IQ Math table in Boot ROM (This saves space and Boot ROM
is 1 wait-state). If this section is not uncommented, IQmathTables2
will be loaded into other memory (SARAM, Flash, etc.) and will take
up space, but 0 wait-state is possible.
*/
/*
IQmathTables2 : > IQTABLES2, PAGE = 0, TYPE = NOLOAD
{

IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)

}
*/
/* Uncomment the section below if calling the IQNasin() or IQasin()
functions from the IQMath.lib library in order to utilize the
relevant IQ Math table in Boot ROM (This saves space and Boot ROM
is 1 wait-state). If this section is not uncommented, IQmathTables2
will be loaded into other memory (SARAM, Flash, etc.) and will take
up space, but 0 wait-state is possible.
*/
/*
IQmathTables3 : > IQTABLES3, PAGE = 0, TYPE = NOLOAD
{

IQmath.lib<IQNasinTable.obj> (IQmathTablesRam)

}
*/

}


SECTIONS
{
DLOG: > dataRAM,PAGE=1
}

I tried using a linker command file specificaly for F2802x devices, but the program won't compile this way due to memory space issues, that's way I switched back to the original linker command file that came for the example.

Thank you very much for your help!

Kind regards,

Jorge

Jorge,

The issue is you're using a project built for the F28035 on a part with much less memory.  I've tried juggling the memory sections to make it fit, but the F28027 part just doesn't have enough memory to run everything from RAM.  I think the main reason is the memory allocated to data logging.  

I see two alternatives: The simplest solution is to move to an F28035 part to run this example as it stands.  Otherwise what you can do is use a flash based F28027 linker file (you'll find "F28027.cmd" in the same directory as "28027_RAM_lnk.cmd").  You'll be able to build and load the project, but you'll be limited to only two hardware breakpoints to debug any code. 

Regards,

Richard

Hi, I am trying to do the same using a launchpad, will this example run on the launchxl-F28069 launchpad?

Thanks.