• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1152 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS 5 and TMS320-P28016 Development Board

Daryl Lee
Intellectual 270 points

Other Parts Discussed in Thread: TMS320F28016

I have recently upgraded from CCS 3.3 to CCS 5 and prefer not to regress.  I just received an XDS100-V2 JTAG emulatror and a TMS320-P28016 development board from Olimex, whose "quick start" instructions are for CCS 3.3.  I tried to "translate" them to CCS 5 and ran into a couple of issues, after successfully importing the "Blinking_LED" project from its CCS 3.3 format, I run into these two issues, beyond which I can't proceed.

1.  When I plug the USB cable into the XDS100-V2, I don't get that warm little "thunk" sound indicating the device has been recognized and is usable.

2.  When I try to create a new target configuration in CCS 5, I cannot find TMS320-P28016 on the list; is it "close enough" to use TMS320-F28016?

Is there any guidance available for me?

 

  • 0
    TI__Guru**** 480811 points

    Hello,

    Daryl Lee said:
    1.  When I plug the USB cable into the XDS100-V2, I don't get that warm little "thunk" sound indicating the device has been recognized and is usable.

    I'd start with the below resource on XDS100;

    http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting

    Daryl Lee said:
    2.  When I try to create a new target configuration in CCS 5, I cannot find TMS320-P28016 on the list; is it "close enough" to use TMS320-F28016?

    I'd try using "TMS320F28016"

    Thanks

    ki

     

  • 0 in reply to Ki
    Intellectual 270 points

    Thanks.  It seems my USB problem was due to the USB Hub that apparently chose this moment to die.  I bypassed it and now all that seems well.

    I did select the TMS320F28016 and that moved me along.  It turns out the symbolization on the BOARD uses a P, but the chip is clearly an F.

    Now I'm getting memory mapping errors at link time.  In the linker.cmd file I have the following map (imported from the sample code received from Olimex):

    MEMORY
    {
     PAGE 0 :
       /* For this example, L0 is split between PAGE 0 and PAGE 1 */
       /* BEGIN is used for the "boot to SARAM" bootloader mode   */
     
       BEGIN      : origin = 0x000000, length = 0x000002            
       RAMM0      : origin = 0x000002, length = 0x0003FE
       PRAML0     : origin = 0x008000, length = 0x000800   
       RESET      : origin = 0x3FFFC0, length = 0x000002
       BOOTROM    : origin = 0x3FF000, length = 0x000FC0              

            
    PAGE 1 :

       /* For this example, L0 is split between PAGE 0 and PAGE 1 */

       BOOT_RSVD   : origin = 0x000400, length = 0x000080     /* Part of M1, BOOT rom will use this for stack */
       RAMM1       : origin = 0x000480, length = 0x000380     /* on-chip RAM block M1 */
       DRAML0   : origin = 0x008800, length = 0x000800  
    }

    Every memory line reports "run placement fails for object".  So I think I need to finally make myself learn how memory allocation really works.

  • 0 in reply to Daryl Lee
    Intellectual 270 points

    Well, that was a red herring.  It seems I was using the wrong example project.  I now have a different problem that I will try to chase down on my own for a little bit.  Thanks for your help!