Problem with breakpoints and TMS320F28069

Cedric D

Other Parts Discussed in Thread: TMS320F28335, TMS320F28069, MOTORWARE, CONTROLSUITE

Hi,

I used a TMS320F28335 with a XDS100v1 without any problems. But now I was passed on a TMS320F28069MISO with a XDS100v2 and if it is recognized, in debugger mode it doesn't stop at breakpoints, but why???????????

More precisely, I put my TMS320F28069 on a XDS100v1 but I just used the JTAG of docking station as alimentation and I used the ISOLATED JTAG on my card to communicate through the computer, could the problem be this ? But I have no choices... I give you the link to my control card, I can command GPIO and co but it really doesn't stop at any breakpoints...Thank you to help me...

CARD : http://www.ti.com/tool/tmdscncd28069miso

over 12 years ago

0 ChrisClearman over 12 years ago

TI__Guru** 119680 points

hello,

I use this same 69MISO card almost daily, and am able to set breakpoints in the source code.

Do note that the card you have has special software functionality that resides in execute only ROM, and if you are trying to set a breakpoint for that code I don't think that would be possible.

Are you using the MotorWare example projects?

0 Cedric D over 12 years ago in reply to ChrisClearman

Intellectual 660 points

Hello,

Sorry for the late I was in holidays. Thank you for your answer. I am not using the MotorWare example projects but I have downloaded it because of your post in order to see if I can find something interesting. I don't really understand your answer. Everything in my soft is run from RAM, but what do you mean in your post ? Have I to run everything from FLASH in order to have breakpoints working correctly ? Or what have I to change in my .cmd ? Have you got an example of something in which breakpoints can work? Because I spend really a lot of time in finding solutions to get the programming environment correct with this card...:'(...? Maybe there is a solution to use this card in a classic way, because I am not interested on the InstaSpins and software in it, the buyer has done a mistake when he has choosen this MISO card, the MISO part is not important for me maybe it can be avoided ?In any case, I give you my .cmd if you have an idea of what I can change for my breakpoints working...Thank you

Fullscreen 0652.28069_RAM_lnk.txt Download

/*
// TI File $Revision: /main/3 $
// Checkin $Date: March 3, 2011   13:45:43 $
//###########################################################################
//
// FILE:    28069_RAM_lnk.cmd
//
// TITLE:   Linker Command File For F28069 examples that run out of RAM
//
//          This ONLY includes all SARAM blocks on the F28069 device.
//          This does not include flash or OTP.
//
//          Keep in mind that L0,L1,L2,L3 and L4 are protected by the code
//          security module.
//
//          What this means is in most cases you will want to move to
//          another memory map file which has more memory defined.
//
//###########################################################################
// $TI Release: $ 
// $Release Date: $ 
//###########################################################################
*/

/* ======================================================
// For Code Composer Studio V2.2 and later
// ---------------------------------------
// In addition to this memory linker command file,
// add the header linker command file directly to the project.
// The header linker command file is required to link the
// peripheral structures to the proper locations within
// the memory map.
//
// The header linker files are found in <base>\F2806x_headers\cmd
//
// For BIOS applications add:      F2806x_Headers_BIOS.cmd
// For nonBIOS applications add:   F2806x_Headers_nonBIOS.cmd
========================================================= */

/* ======================================================
// For Code Composer Studio prior to V2.2
// --------------------------------------
// 1) Use one of the following -l statements to include the
// header linker command file in the project. The header linker
// file is required to link the peripheral structures to the proper
// locations within the memory map                                    */

/* Uncomment this line to include file only for non-BIOS applications */
/* -l F2806x_Headers_nonBIOS.cmd */

/* Uncomment this line to include file only for BIOS applications */
/* -l F2806x_Headers_BIOS.cmd */

/* 2) In your project add the path to <base>\F2806x_headers\cmd to the
   library search path under project->build options, linker tab,
   library search path (-i).
/*========================================================= */

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

   Notes:
         Memory blocks on F28069 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.

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

MEMORY
{
PAGE 0 :
   /* BEGIN is used for the "boot to SARAM" bootloader mode   */

   BEGIN       : origin = 0x000000, length = 0x000002
   RAMM0       : origin = 0x000050, length = 0x0003B0
   RAML0_L3    : origin = 0x008000, length = 0x002000	 /* RAML0-3 combined for size of .text */
   														 /* in Example_F2806xSWPrioritezedInterrupts */


 //
   RAML4L5L6       : origin = 0x00A000, length = 0x006000     /* on-chip RAM block L4 */

   RAML7L8       : origin = 0x010000, length = 0x004000     /* on-chip RAM block L7 */

   //

   RESET       : origin = 0x3FFFC0, length = 0x000002
   FPUTABLES   : origin = 0x3FD860, length = 0x0006A0	 /* FPU Tables in Boot ROM */
   IQTABLES    : origin = 0x3FDF00, length = 0x000B50    /* IQ Math Tables in Boot ROM */
   IQTABLES2   : origin = 0x3FEA50, length = 0x00008C    /* IQ Math Tables in Boot ROM */
   IQTABLES3   : origin = 0x3FEADC, length = 0x0000AA	 /* IQ Math Tables in Boot ROM */

   BOOTROM    : origin = 0x3FF3B0, length = 0x000C10


PAGE 1 :

   BOOT_RSVD   : origin = 0x000002, length = 0x00004E     /* Part of M0, BOOT rom will use this for stack */
   RAMM1       : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
   //RAML4L5L6       : origin = 0x00A000, length = 0x006000     /* on-chip RAM block L4 */
   //RAML5       : origin = 0x00C000, length = 0x002000     /* on-chip RAM block L5 */
   //RAML6       : origin = 0x00E000, length = 0x002000     /* on-chip RAM block L6 */
   //RAML7L8       : origin = 0x010000, length = 0x004000     /* on-chip RAM block L7 */
   //RAML8       : origin = 0x012000, length = 0x002000     /* on-chip RAM block L8 */
   USB_RAM     : origin = 0x040000, length = 0x000800     /* USB RAM		  */
}


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            : > RAML0_L3,   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
   .stack           : > RAML0_L3,      PAGE = 0

   /*.ebss            : > RAML4L5L6,      PAGE = 1
   .econst          : > RAML4L5L6,      PAGE = 1
   .esysmem         : > RAML4L5L6,      PAGE = 1

   IQmath           : > RAML0_L3,   PAGE = 0
   IQmathTables     : > IQTABLES,   PAGE = 0
   
   // Allocate FPU math areas:
   FPUmathTables    : > FPUTABLES,  PAGE = 0,
   
   DMARAML5	        : > RAML4L5L6,      PAGE = 1
   DMARAML6	        : > RAML4L5L6,      PAGE = 1
   DMARAML7	        : > RAML7L8,      PAGE = 1
   DMARAML8	        : > RAML7L8,      PAGE = 1*/




   .ebss            : > RAML4L5L6,      PAGE = 0
   .econst          : > RAML4L5L6,      PAGE = 0
   .esysmem         : > RAML4L5L6,      PAGE = 0

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

   // Allocate FPU math areas:
   FPUmathTables    : > FPUTABLES,  PAGE = 0, TYPE = NOLOAD

   DMARAML5	        : > RAML4L5L6,      PAGE = 0
   DMARAML6	        : > RAML4L5L6,      PAGE = 0
   DMARAML7	        : > RAML7L8,      PAGE = 0
   DMARAML8	        : > RAML7L8,      PAGE = 0

  /* 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)

   }
   */

}

/*
//===========================================================================
// End of file.
//===========================================================================
*/

0 Cedric D over 12 years ago in reply to Cedric D

Intellectual 660 points

I have passed everything from RAM to FLASH and nothing has changed. So I am blocked and I have no ideas how to set good breakpoints...

0 ChrisClearman over 12 years ago in reply to Cedric D

TI__Guru** 119680 points

Cedric,

The controlCARD you linked to is a special one to run MotorWare projects. If you are trying to run controlSUITE sample code you might rung into some problems as the card you have doesn't have the same ROM contents as a standard F28069 device - things like math tables and IQMath are no longer in the expected location. And if you are trying to use breakpoints in a MotorWare project it will only work in code that exists in RAM (you can't breakpoint the code in ROM).

I'm not sure what steps you are taking, but when I use breakpoints I right click --> Breakpoint on the line of code. When I run the code, IF the code gets to that location it will halt.

0 Cedric D over 12 years ago in reply to ChrisClearman

Intellectual 660 points

Hi,

I really thank you for your answer. I thought that the DSP basis keeps the same because of the reference and I had some hope to do something whit this card but you 've killed me ^^ For the breakpoint , as usually, I just double-click or right clik + CCS breakpoint which is the only choice actually. So I think I will discuss with my team in order to change the 28069MISO by a 28069 classic. In fact he have found it on the TI web site and the problem is that the only 28069 available on the TI website in the control card format (without dock) is the MISO and the mistake was born here. So it seems better for me to change my card. However I really thank you for your precious answer which had permitted to me to understand this error and don't spend more time on it. Thank you and have a good day.

Regards,

Cédric

C2000™︎ microcontrollers

C2000 microcontrollers forum

Problem with breakpoints and TMS320F28069