• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1597 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

migrating from CC 4.12 to CCS 3.3

Jerry Nettleton
Intellectual 350 points

I've migrated/converted a project from 4.12 to 3.3.83.19 for an F2406A DSP project.  Now I have 2 issues:

1. When running the debugger, I can't set any breakpoints.  How can I debug things and set breakpoint using the XDS510LC USB JTAG emulator?

2. I used the "on-chip flash programming" option in the tools menu to update the DSP flash on the board.  When I cycle power w/o emulator attached, it doesn't appear to boot.  Do I need to make any changes for the appropriate entry point or run-time configuration?

 

  • 0
    TI__Guru*** 130875 points

    HI Jerry,

    is there a specific reason you are going back in versions?  Backward compatibility, especially 4 ->3 is not necessary common or straight forward.  How did you do the migration?  Are there further details you would be able to provide?

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Intellectual 350 points

    I'm not going backward.  CCS 3.3 is newer than CC 4.12 (which I discovered in another thread).

    I need to support a legacy product with an F2406A DSP.  The new .PJT project file was automatically generated from a .MAK file using CCS 3.3.  The project recompiles w/o any errors or warnings and produces a .OUT file.  When I load the .OUT file, the DSP doesn't appear to boot.  I found something about "Startup Mode" but I haven't found much documentation on it yet.

    Any ideas?

  • 0 in reply to Jerry Nettleton
    TI__Guru*** 130875 points

    Hi Jerry,

    my appologies for the misunderstanding.  I automatically thing CCS I suppose.   Let me see if I can get some more expert colleagues on the old versions to take a peak.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Guru**** 450031 points

    Hi Jerry,
    Did you check to make sure you are building with --rom_model (-cr) and not --ram_model (-c)?

    Thanks
    ki

  • 0 in reply to Ki
    Intellectual 350 points

    I didn't find the --rom_model or --ram_model options.  The linker options that I found were for "Autoinit Model":

    Run-Time Autoinitialization (-c)
    Load-Time Initialization (-cr)

    The Autoinit Model settings for this project was set to "-c" (same option in the old .MAK file).

  • 0 in reply to Jerry Nettleton
    Intellectual 350 points

    Question 2 resolved -- I connected a logic analyzer and found out that DSP started but my code had a bug which prevented it from displaying anything on the LCD.

    Question 1 -- how can I enable breakpoints using the JTAG emulator?  What is the default/recommended memory map for a F2406A DSP?  I looked at the GEL file but there's a lot of extra stuff in there so it's not entirely clear.

     

  • 0 in reply to Jerry Nettleton
    TI__Guru**** 450031 points

    Jerry Nettleton said:
    how can I enable breakpoints using the JTAG emulator? 

    Setting breakpoints in v3 should be similar to what it was with the old CC versions. You should be able to set them in the editor margins if your application is built with debug symbols and -o1 optimization and lower. You can also open the breakpoints window (Debug->Breakpoints) and set them there (via address or symbol)

    Jerry Nettleton said:
    What is the default/recommended memory map for a F2406A DSP?  I looked at the GEL file but there's a lot of extra stuff in there so it's not entirely clear.

    This question is best asked in the C2000 device forums. But the GEL file seems to do a good guy of describing the memory map. Look at lines 98-177. It gives the page, start address, length of defined memory ranges. This should give you in good details what is available memory and what it is used for (via the comments)

    Thanks

    ki