• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 82 subscribers
  • Views 626 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.

CCS/F28M35H52C: Concerto C28x core gets disconnected when M3 is reseted

Dionisio Ramirez Prieto
Intellectual 780 points
Part Number: F28M35H52C

Tool/software: Code Composer Studio

Once I have loaded the code into the M3 and C28 cores, when I reset the M3, the C28 core suddenly gets disconnected from the PC. Also it is impossible re-connecting the C28 core until I disconnect the M3.

I checked it with CCS7, CCS8, CCS9 and several Concerto boards in the same computer (computer that I've been using for the last 18 months (windows10 and USB-C)).

This is the message that shows up when I reset and restart the M3 core:

C28xx_0: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00005)
C28xx_0: Unable to determine target status after 20 attempts
C28xx_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

And when I try to re-connect the C28:

C28xx_0: Error: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.1.0.00005)
C28xx_0: Unable to determine target status after 20 attempts
C28xx_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_0: GEL: Error while executing OnTargetConnect(): Could not read 0x00000883@Data: target is not connected
     at (*((unsigned int *) 0x0883)==0x0005) [f28m35h52c1_c28.gel:73]
     at OnTargetConnect()

Thank you

Dionisio

  • 0
    Intellectual 780 points
    Today I've checked that the Version: 7.0.0.00043 works fine.
    Nevertheless, checking 2 computers with the 2 Concerto boards and fresh installation do not work properly with CCSv7.4, CCSv8 and CCSv9, neither in Mac or PC.

    Dionisio
  • 0 in reply to Dionisio Ramirez Prieto
    TI__Guru 71785 points
    Dionisio,
    Thanks for reaching out to the E2E forum.

    In the F28M35 the M3 core is the "master" and any reset to that device will put the C28x core in reset as well.

    One of the first steps in the M3 Boot ROM is to bring the C28x out of reset. The GEL file that should be included with a F28M35 based ccxml target config will also do this in the "Device_Config()" in the "Scripts" menu item

    In terms of debugging, you would need to dis-connect the C28x before resetting the M3 to avoid this error.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Intellectual 780 points

    Hi Matthew

    Thank you for you answer.

    I've been using the F28M35x for the last 7 years almost every day.

    Usually I connect both cores and afterwards I load the code in both cores. Then I reset+restart+resume the M3 and then the C28 (in debug mode).

    I never had this problem before. Once I've loaded the code in both cores I can not run them because when I try to run the M3 it disconnects the C28 and it is not possible to connect it again until I disconnect the M3.

    In consequence, I'm sure that there is a bug in CCS, because otherwise, it makes no sense.

    By the way, in "Script", I have no files.

    Thank you

    Dionisio

  • 0 in reply to Dionisio Ramirez Prieto
    TI__Guru 71785 points
    Dionisio,
    My apologies, I mis-understood the comment about the stable system prior to this happening. Another collegue advised that this behaivor shouldn't happen either on M3 reset.

    I'm going to move this to the CCS driver forum, as I suspect there is something in play with the tools side of the equation.

    Best,
    Matthew
  • 0 in reply to Dionisio Ramirez Prieto
    TI__Guru**** 420650 points

    Hello Dionisio,

    Dionisio Ramirez Prieto said:
    Today I've checked that the Version: 7.0.0.00043 works fine.

    What is the TI Emulator Pack version for this CCS version (Help -> About CCS -> Installation Details)?

    For all the other CCS versions that do not work, did you install any CCS updates recently? Are all their TI Emulators version 8.1.0.00005?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 780 points

    Code Composer Studio  Version: 7.0.0.00043:   TI Emulators    6.0.504.1    com.ti.emulation.pack.win32.feature.group    Texas Instruments WORKS

    Code Composer Studio  Version: 8.3.0.00009:    TI Emulators    8.1.0.00005    com.ti.emulation.pack.win32.feature.group    Texas Instruments DOES NOT WORK


    Code Composer Studio  Version: 9.0.0.00018:   TI Emulators    8.1.0.00005    com.ti.emulation.pack.win64.feature.group    Texas Instruments DOES NOT WORK

    Yes, I have updated CCS 8.3 recently. The CCS v9 is a fresh installation to check this problem.

    Dionisio

  • 0 in reply to Dionisio Ramirez Prieto
    TI__Guru**** 420650 points
    Thank you. This looks like a regression with TI Emulators 8.1.0.00005.

    My CCSv8.3.0.00009 installation has the an older version of the TI Emulators pack (8.0.903.6) and I can't reproduce the issue on that. But I see it on CCSv9, which comes with 8.1.0.00005

    I will see if this is a known issue. If not, i will file a bug. In any case I will get back to you with an update.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 780 points
    The problem is the same in the Mac OSx version:
    Code Composer Studio Version: 8.3.0.00009 OS: Mac OS X, v.10.14.3, x86_64 / cocoa
    TI Emulators 8.1.0.00005 com.ti.emulation.pack.osx.feature.group Texas Instruments DOES NOT WORK

    Dionisio
  • 0 in reply to Ki
    TI__Guru**** 420650 points
    I filed a bug for this. Tracking ID: DBGTRC-4842

    Thanks
    ki