• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 54 subscribers
  • Views 2200 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.

Missing F2837x_Headers_nonBIOS_cpu1.cmd

Hank Barta
Intellectual 970 points
Other Parts Discussed in Thread: CONTROLSUITE

Environment: Linux, Ubuntu 16.04

CCS: 6.2.0.00050

C2800 Compiler Tools 16.6.0

controlSUITE: ?? Path is unique to  /opt/ti/controlSUITE/device_support/F2837xD/v190

I am following directions in F2837xD-FRM-EX-UG.pdf starting on P14 to create a new project. (The PDF identifies itself as "This is version 190 of this document, last updated on Mon Feb 1 16:52:26 CST 2016.")

I have performed all steps as described through step 5. It requires "F2837x_Headers_nonBIOS_cpu1.cmd" Which is not found under /opt/ti  on the Linux install. I do find it in the following locations on my Windows install:

$ find c:/ti -name F2837x_Headers_nonBIOS_cpu1.cmd -exec md5sum {} \;
5e3e6d795268f99f52791e0fa508f345 *c:/ti/controlSUITE/device_support/F2837xD/v100/F2837xD_headers/cmd/F2837x_Headers_nonBIOS_cpu1.cmd
a3029fc846cf8ec3b374453a4164f43a *c:/ti/controlSUITE/libs/utilities/boot_rom/F2837x_rev0/rev0_rom_sources/F2837x_headers/cmd/F2837x_Headers_nonBIOS_cpu1.cmd
a3029fc846cf8ec3b374453a4164f43a *c:/ti/controlSUITE/libs/utilities/boot_rom/F2837x_revb/revb_rom_sources/F2837x_headers/cmd/F2837x_Headers_nonBIOS_cpu1.cmd

On Linux the directory does libs not exist under /opt/ti/controlSUITE/

hbarta@itws007:~$ ls /opt/ti/controlSUITE/libs
ls: cannot access /opt/ti/controlSUITE/libs: No such file or directory
hbarta@itws007:~$ ls /opt/ti/controlSUITE/
device_support
hbarta@itws007:~$

I copied the more recent version over from Windows and placed in the project directory and added to 'library file or command file as input'

I completed the remaining steps through step 8 without further exceptions. When I build I get a crapload of errors that seem to be related to the missing file.

How can I resolve these?

Thanks!

(Errors below.)

<Linking>
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 7: error #10263: BEGIN memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 8: error #10263: RAMM0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 8: error #10264: RAMM0 memory range overlaps existing memory range RAMM0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 9: error #10263: RAMD0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 9: error #10264: RAMD0 memory range overlaps existing memory range RAMD0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 10: error #10263: RAMLS0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 10: error #10264: RAMLS0 memory range overlaps existing memory range RAMLS0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 11: error #10263: RAMLS1 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 11: error #10264: RAMLS1 memory range overlaps existing memory range RAMLS1
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 12: error #10263: RAMLS2 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 12: error #10264: RAMLS2 memory range overlaps existing memory range RAMLS2
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 13: error #10263: RAMLS3 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 13: error #10264: RAMLS3 memory range overlaps existing memory range RAMLS3
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 14: error #10263: RAMLS4 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 14: error #10264: RAMLS4 memory range overlaps existing memory range RAMLS4
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 15: error #10263: RESET memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 15: error #10264: RESET memory range overlaps existing memory range RESET
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 19: error #10263: BOOT_RSVD memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 19: error #10264: BOOT_RSVD memory range overlaps existing memory range BOOT_RSVD
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 20: error #10263: RAMM1 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 20: error #10264: RAMM1 memory range overlaps existing memory range RAMM1
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 21: error #10263: RAMD1 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 21: error #10264: RAMD1 memory range overlaps existing memory range RAMD1
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 24: error #10263: RAMLS5 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 24: error #10264: RAMLS5 memory range overlaps existing memory range RAMLS5
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 26: error #10263: RAMGS0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 26: error #10264: RAMGS0 memory range overlaps existing memory range RAMGS0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 27: error #10263: RAMGS1 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 27: error #10264: RAMGS1 memory range overlaps existing memory range RAMGS1
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 28: error #10263: RAMGS2 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 28: error #10264: RAMGS2 memory range overlaps existing memory range RAMGS2
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 29: error #10263: RAMGS3 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 29: error #10264: RAMGS3 memory range overlaps existing memory range RAMGS3
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 30: error #10263: RAMGS4 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 30: error #10264: RAMGS4 memory range overlaps existing memory range RAMGS4
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 31: error #10263: RAMGS5 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 31: error #10264: RAMGS5 memory range overlaps existing memory range RAMGS5
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 32: error #10263: RAMGS6 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 32: error #10264: RAMGS6 memory range overlaps existing memory range RAMGS6
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 33: error #10263: RAMGS7 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 33: error #10264: RAMGS7 memory range overlaps existing memory range RAMGS7
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 34: error #10263: RAMGS8 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 34: error #10264: RAMGS8 memory range overlaps existing memory range RAMGS8
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 35: error #10263: RAMGS9 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 35: error #10264: RAMGS9 memory range overlaps existing memory range RAMGS9
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 36: error #10263: RAMGS10 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 36: error #10264: RAMGS10 memory range overlaps existing memory range RAMGS10
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 37: error #10263: RAMGS11 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 37: error #10264: RAMGS11 memory range overlaps existing memory range RAMGS11
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 38: error #10263: RAMGS12 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 38: error #10264: RAMGS12 memory range overlaps existing memory range RAMGS12
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 39: error #10263: RAMGS13 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 39: error #10264: RAMGS13 memory range overlaps existing memory range RAMGS13
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 43: error #10263: CPU2TOCPU1RAM memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 43: error #10264: CPU2TOCPU1RAM memory range overlaps existing memory range CPU2TOCPU1RAM
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 44: error #10263: CPU1TOCPU2RAM memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 44: error #10264: CPU1TOCPU2RAM memory range overlaps existing memory range CPU1TOCPU2RAM
"../2837x_FLASH_lnk_cpu1.cmd", line 87: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 88: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 89: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 90: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 91: warning #10190-D: absolute symbol "_RamfuncsRunSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 92: warning #10190-D: absolute symbol "_RamfuncsRunEnd" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 87: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 88: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 89: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 90: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 91: warning #10190-D: absolute symbol "_RamfuncsRunSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 92: warning #10190-D: absolute symbol "_RamfuncsRunEnd" being redefined

 undefined               first referenced     
  symbol                     in file          
 ---------               ----------------     
 _AnalogSubsysRegs       ./F2837xD_SysCtrl.obj
 _ClkCfgRegs             ./F2837xD_SysCtrl.obj
 _CpuSysRegs             ./F2837xD_SysCtrl.obj
 _DcsmZ1Regs             ./F2837xD_SysCtrl.obj
 _DcsmZ2Regs             ./F2837xD_SysCtrl.obj
 _DevCfgRegs             ./F2837xD_Gpio.obj   
 _FlashPumpSemaphoreRegs ./F2837xD_SysCtrl.obj
 _GpioCtrlRegs           ./F2837xD_Gpio.obj   
 _GpioDataRegs           ./F2837xD_Gpio.obj   
 _InputXbarRegs          ./F2837xD_Gpio.obj   
 _WdRegs                 ./F2837xD_SysCtrl.obj

error #10234-D: unresolved symbols remain

"../2837x_FLASH_lnk_cpu1.cmd", line 87: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
>> Compilation failure
makefile:145: recipe for target 'cmocka_dsp_demo_nolib.out' failed
"../2837x_FLASH_lnk_cpu1.cmd", line 88: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 89: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 90: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 91: warning #10190-D: absolute symbol "_RamfuncsRunSize" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 92: warning #10190-D: absolute symbol "_RamfuncsRunEnd" being redefined
"../2837x_FLASH_lnk_cpu1.cmd", line 87: warning #10272-D: section relative symbols from different output sections cannot be mixed; "_RamfuncsLoadStart" is in section "ramfuncs", "DOT operator" is in section ".TI.ramfunc"
"../2837x_FLASH_lnk_cpu1.cmd", line 89: warning #10272-D: section relative symbols from different output sections cannot be mixed; "_RamfuncsLoadEnd" is in section "ramfuncs", "DOT operator" is in section ".TI.ramfunc"
"../2837x_FLASH_lnk_cpu1.cmd", line 90: warning #10272-D: section relative symbols from different output sections cannot be mixed; "_RamfuncsRunStart" is in section "ramfuncs", "DOT operator" is in section ".TI.ramfunc"
"../2837x_FLASH_lnk_cpu1.cmd", line 92: warning #10272-D: section relative symbols from different output sections cannot be mixed; "_RamfuncsRunEnd" is in section "ramfuncs", "DOT operator" is in section ".TI.ramfunc"
warning #10063-D: entry-point symbol other than "_c_int00" specified:  "code_start"
error #10010: errors encountered during linking; "cmocka_dsp_demo_nolib.out" not built
gmake: *** [cmocka_dsp_demo_nolib.out] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

  • 0
    Intellectual 970 points

    Edit/update

    I see that 2837x_FLASH_lnk_cpu1.cmd is being included in the project.  I think I have fixed that by going to Properties -> Build -> Advanced Options -> Runtime Environment and selecting "Link using RAM Autoinitiailzation model"

    Now the errors start with

    <Linking>
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 7: error #10263: BEGIN memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 8: error #10263: RAMM0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 8: error #10264: RAMM0 memory range overlaps existing memory range RAMM0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 9: error #10263: RAMD0 memory range has already been specified

"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 9: error #10264: RAMD0 memory range overlaps existing memory range RAMD0
>> Compilation failure
makefile:146: recipe for target 'cmocka_dsp_demo_nolib.out' failed
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 10: error #10263: RAMLS0 memory range has already been specified
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 10: error #10264: RAMLS0 memory range overlaps existing memory range RAMLS0
"/opt/ti/ccsv6/ccs_base/c2000/include/2837x_RAM_lnk_cpu1.cmd", line 11: error #10263: RAMLS1 memory range has already been specified
.
.
.

    As an aside, it would be very cool if CCS had a wizard that would create a starting point rather than the user having to follow pages of instructions.

    thanks,

    hank

  • 0 in reply to Hank Barta
    Intellectual 970 points
    Edit: the original post should state Ubuntu 14.04. We have not upgraded. Yet. ;)
  • 0
    TI__Guru**** 173310 points

    Hank Barta said:

    controlSUITE: ?? Path is unique to  /opt/ti/controlSUITE/device_support/F2837xD/v190

    I am following directions in F2837xD-FRM-EX-UG.pdf starting on P14 to create a new project. (The PDF identifies itself as "This is version 190 of this document, last updated on Mon Feb 1 16:52:26 CST 2016.")

    There are a couple of things going on there. First I think that you may have selected a specific device when creating the new project instead of "Generic C28xx Device" as mentioned in the document. Selecting a specific device automatically adds a linker command file to the project which is one of the issues you are hitting.

    Another issue is that the document mentions incorrect file names in step 5. It asks you to add 2837x_RAM_lnk_cpu1.cmd and F2837x_Headers_nonBIOS_cpu1.cmd.
    These were the filenames in v100 rev of the device support files, however they have since changed to include the D in the device name. Hence if you change the names
    of these two files under Linker->File Search Path as in the screenshot below, then it should build without errors.

    So essentially the steps in the document should work except for changing the file names in step 5, as long as you choose the device as ""Generic C28xx Device" when creating the project.

    Let me know if this works.

    I will also notify the C2000 team that the document needs to be updated to reflect this.

  • 0 in reply to AartiG
    Intellectual 970 points

    Hi AartiG,

    Thank you for the prompt reply. I am in the throes of a workstation upgrade and am unable to test your suggestions at the moment.

    The 'create project' dialog has changed significantly. It would be wise for the document to mewntion to select the generic option because it seems pretty natural to select the specific processor. Once I have selected the specific processor, is there an alternate way to proceed to get this working or do I need to discard my work and start again?

    I have another question that is peripherally related to this issue and that is RAM vs. ROM code. I'd like to keep the code in RAM to facilitate quicker downloads for testing. At some point I will likely outgrow RAM and will need to move the code to flash (on chip.) Is there a documentation entry or Wiki entry that outlines the process to do that? It seems like there are several places in the Properties dialog that reference this but I'm not sure I have found them all and I'm also concerned that there are other things I need to change (like editing the linker command file.)

    And another question... At one point when I had a simple buildable example I found that both CPU1 and CPU2 were programmed every time I started the debugger even though the program was for CPU1 only. Is there a way to disable download for CPU2 so that only CPU1 is updated?

    thanks,

    hank

  • 0 in reply to Hank Barta
    TI__Guru**** 173310 points

    Hank Barta said:
    The 'create project' dialog has changed significantly. It would be wise for the document to mewntion to select the generic option because it seems pretty natural to select the specific processor.

    I will pass on this feedback.

    Hank Barta said:
    Once I have selected the specific processor, is there an alternate way to proceed to get this working or do I need to discard my work and start again?

    If you select a specific processor a linker command file will automatically get added to the project. As long as you delete that file from the project and proceed with following the steps in the document (with of course the modifications I mentioned above) you should be fine.

    Hank Barta said:
    At some point I will likely outgrow RAM and will need to move the code to flash (on chip.) Is there a documentation entry or Wiki entry that outlines the process to do that?

    The example projects in ControlSuite for F2837xD contain both a RAM and Flash build configuration. When you import the project into CCS, it defaults to the RAM configuration but you can switch to Flash by right-clicking on the project, going to Build Configurations->Set Active, and select the Flash config. The Flash configuration uses a linker command file that places code in Flash while the RAM configuration uses a linker command file that places code in RAM. You can use these examples as a reference or starting point for your project.

    Hank Barta said:
    At one point when I had a simple buildable example I found that both CPU1 and CPU2 were programmed every time I started the debugger even though the program was for CPU1 only. Is there a way to disable download for CPU2 so that only CPU1 is updated?

    Please post this question to the C2000 forums as the experts there would be able to provide a better answer for this. 

  • 0 in reply to AartiG
    Intellectual 970 points
    Hi AartG,
    Again, thank you for your help.

    >>The example projects in ControlSuite for F2837xD contain both a RAM and Flash build configuration ...

    I think I did not explain the point of my question regarding this. I would like to know what I need to change to support RAM and Flash build configurations in *my* project (which was created using Project -> New CCS Project.) I prefer to understand the process rather than start with an existing project and hope that works as my project grows. At some point I think I will need to segregate code that runs from RAM from code that runs from flash as I believe that code runs faster from RAM.

    I think I have a fully functional PC again and will shortly be proceeding with the rest of your suggestions.

    thanks,
    hank
  • 0 in reply to Hank Barta
    TI__Guru**** 173310 points

    Hank Barta said:
    I prefer to understand the process rather than start with an existing project and hope that works as my project grows.

    This application note is a great reference for designing applications to run from flash, in general. Although it does not have examples tailored specifically to F28377D, the concepts should apply to all F28x devices. 

    If you need further guidance on this as you go through the project development I would suggest asking in the C2000 forums.

  • 0 in reply to Hank Barta
    Intellectual 970 points
    Hi AartG,
    I am able to build the project and debug on Windows using the XDS200 (Spectrum Digital) JTAG debugger. Thank you for your help so far.

    I have not been successful getting the XDS200 working on Linux. Can you suggest the best forum for asking questions about that? (Previous posts seem to use this forum, I will start another thread.)
  • 0 in reply to Hank Barta
    TI__Guru**** 173310 points
    Glad to hear that you are able to build and debug successfully. I will go ahead and close this thread since the issue for which this thread was started is resolved.
  • 0 in reply to AartiG
    Prodigy 100 points
    I am happy to see this topic I think I have same problem when it #10263 error but generic C28xxx not have.
    I got example ( blinky or pwm from control suite)
    1) I can download to ram with example load for the first time ( that still C28xxx). But when I specific 28377D. # error 10263 abour ram appear , how can I solve that) when build
    2) example when I load my program ok ( load example pwm from control suite for the first time) then I config to flash but after Download to DSP when I hit Run. the DSP look Freeze ( I check Its stop after eallow ( and moe to estop0 ) DO I need another coode ( example init flash(), IP_boot CPU2 ???? ). Because I use 28377D but I just want to use 1 CPU . I designed 28377D board by our Lab so I worry about boot pin ??? is it important
    3) do you have some small project by your own , Flash program, and have interrupt working ok and download to flash ok
    Please show me

    thank u so much
  • 0 in reply to Duc Pham
    Prodigy 20 points
    Hi,Duc Pham
    I have the same problem ,have you solved this problem?