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.

flash_programming_cpu02 won't download to controlCARD (TMS320F28377D)

flash_programming_cpu01 builds and loads without difficulty. When I try to debug flash_programming_cpu02 the output in the console is:

C28xx_CPU2: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code.  Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU2: Error occurred during flash operation: No core matches the pattern 'CPU1'
C28xx_CPU2: Error setting the GSxMSEL register for Flash operations
C28xx_CPU2: Error occurred during flash operation: Timed out waiting for target to halt while executing wr_pll.alg
C28xx_CPU2: Error writing the PLL values (Flash algorithm timed out). Operation cancelled.
C28xx_CPU2: Error occurred during flash operation: No core matches the pattern 'CPU1'
C28xx_CPU2: File Loader: Memory write failed: Unknown error
C28xx_CPU2: GEL: File: C:\Users\hank.barta\Documents\00-scratch\flash_programming_cpu02\CPU2_FLASH\flash_programming_cpu02.out: Load failed.
C28xx_CPU2: Error occurred during flash operation: No core matches the pattern 'CPU1'
C28xx_CPU2: Error setting the GSxMSEL register for Flash operations

I've checked all of the things I normally change if I migrate a project from CPU1 to CPU2:

 Move from CPU1 to CPU2
	Project Options - General - rename Configurations to reflect CPU2 (Not required but will reduce confusion)
	- compiler advanced options Predefined Symbols CPU1 -> CPU2
	- Linker file search paths - change <...>cpu1.cmd to <...>cpu2.cmd
	- delete CPU1_RAM directory
	- Debug - Change Device to XDS100 C28xx_CPU2
	- Debug -> Flash Settings - change Core Selection to CPU2

The second to last setting seems not to stick. If I reopen the properties I find it set to CPU1. (Note: I did not migrate the project. I just imported from Control Suite v190.)

I can't figure out why this is not working. If there is something in my checklist I have overlooked, please let me know. 

I'm using CCS 6.2.0.00050

thanks,

hank

  • Please make sure CPU1 is connected and halted when you are trying to download the code on CPU2.

    Regards,
    Vivek Singh
  • Hi Vivek,
    Can you point me to specific instructions for how to do that?

    thanks,
    hank
  • Hi Hank,

    After launching the target configuration, right click on CPU1 and then click on connect. Then same way connect to CPU2 and try to load the program.

    Regards,
    Vivek Singh
  • Hi Vivek,

    Thanks for the followup.

    Apologies for being a bit thick, but I cannot follow your instructions. I do not know what you mean by "launching the target configuration." Can you be a bit more specific?

    I poked around and found this 

    I don't see what you're talking about.

    I will reiterate that I

    • Imported the project
    • Built (clicking the hammer icon on the tool bar") with no errors
    • Tried to debug (clicking the bug icon on the tool bar) and was presented with the error.

    I've built several other projects earlier in the day that involved both cores and not had this issue. I also migrated one project (watchdog_cpu01) to CPU2 and not experienced this. 

    thank you for your help.

    best,

    hank

    (2nd attempt to post. First post still sitting there 'busy')

  • Hi Hank,

    In the project, under target you have target configuration file (with extension .ccxml). Please right click on that and then click on "Launch Selected Configuration". Once it's lunched, right click on CPU1 and click on connect and also connect CPU2. Then click on "Run" icon on top and select load and brows the .out file to load.

    Hope this helps.

    Regards,

    Vivek Singh 

  • Hi Vivek,

    Thanks for working with me on this. Yes that helps. (It would have saved me some time had you started with "Window -> Show View -> Target Configurations" because I did not equate that with "In the project" and it took some time to find that.)

    The procedure you described worked - thank you!

    How can I configure the project and/or debug configuration so that I can do that by clicking on the debug icon or at most selecting a debug configuration? That's a pretty tortuous process to perform each time I want to debug this project. All of my other CPU2 projects debug with a single mouse click.

    best,

    hank

  • Hank,

    Good that you got it working and sorry, I thought you already have the target configuration file in project view hence did not mentioned how to look for target configuration file.

    How can I configure the project and/or debug configuration so that I can do that by clicking on the debug icon or at most selecting a debug configuration? That's a pretty tortuous process to perform each time I want to debug this project. All of my other CPU2 projects debug with a single mouse click.

    It should work but there may be some issue in project configuration. Please compare the project configuration of working and non-working project.

    Regards,

    Vivek Singh

  • I think I found the solution to this. First I did manage to find a project that would download when built from flash. (A couple others displayed the same problem.) The working example was ipc_gpio_toggle_cpu02. I compared Debug settings in Properties and found for ipc_gpio_toggle_cpu02 with flash_programming_cpu02 and found on the "Auto Run and Launch Options" the Launch Options for the working program were

    and for the one with difficulty debugging

    When I applied these settings from ipc_gpio_toggle_cpu02 to flash_programming_cpu02 I was able to download it without any problems. In addition, it also seems to have resolved the problem with acquiring the flash pump () and that now runs to completion.

  • Hi Hank,

    Good to know issue is resolved and thank you for sharing your findings.

    Regards,
    Vivek Singh