• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 441 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.

TMS320F28379D: Error

Ray Vincent Aranzaso
Mastermind 18180 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE, LAUNCHXL-F28379D

Hi,

Good Day. I have a customer who is working with TMS320F28379D. Please see below the query of the customer to your response. Thank you very much.

I explain the problem we have. I was looking for a similar post on the forum and I found one possible explanation. However, I would like to confirm. 
I soldered manually the microcontroller TMS320F28379DPTPT and I can load and debug the project for the CPU1 but I cannot load de project of the CPU2. 
It cannot be a firmware problem because it works in another PCB with this microcontroller.
 
The error that appears is:
C28xx_CPU2: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006) C28xx_CPU2: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006) C28xx_CPU2: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006) C28xx_CPU2: Unable to determine target status after 20 attempts C28xx_CPU2: 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
 
Is this the microcontroller damaged? Even if the CPU1 works perfectly? There are some supply pins only dedicated for the CPU2?
 
Best Regards,
Ray Vincent
  • 0
    TI__Guru 50611 points

    Ray,

    What is the boot mode? Is there any code running on CPU2? 

    Can the customer put the device in 'Wait Boot' mode, then launch the target configuration file manually. Then connect CPU1 and CPU2. Do they see same failure?

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    TI__Mastermind 18180 points

    Hi Santosh,

    Good Day. Please see below the response of our customer to you reply. Thank you very much.

    There is no code on CPU2 since it is the first time after soldering the uC and I never got to load a program on the CPU2. The boot is by J-Tag for your information both resistors are on the pull-up. 
    I cannot connect de CPU2 since I cannot load any program on CPU2.
    I spouse the CPU2 after load CPU1 is in wait mode because any OTP code is load.
    Best Regards,
    Ray Vincent
  • 0 in reply to Ray Vincent Aranzaso
    TI__Guru 50611 points

    Ray,

    Can you ask customer to run C2000Ware blinky LED example? Just to make they have correct target configuration file, and correct setup.  Please ask him to put in 'Wait Boot' mode. The example is located at:

    C:/ti/c2000/C2000Ware_4_01_00_00/driverlib/f2837xd/examples/dual/led

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    TI__Mastermind 18180 points

    Hi Santosh,

    Good Day. Please see below the response of our customer to your reply. Thank you very much.

    I load de blink-led example but I can only load the CPU1 project as I expected. I do not fully understand what means to leave CPU2 in WAIT BOOT mode, I guess that it is in wait boot mode since it is de first time and I only load CPU1 because if I try to load both at once the error of the no-load CPU2 project occur. 
    The target configuration is okay because I can load CPU1 with no problem and the target configuration test passes with success. I guess de some part of the flash memory corresponding to the CPU2 of the micro is damaged and there is no option to solve it. Do you think the same thing?
    Best Regards,
    Ray Vincent
  • 0 in reply to Ray Vincent Aranzaso
    TI__Guru 50611 points

    Ray,

    Let's follow following steps:

    • Open the target configuration view  : CCS menu View -> Target Configuration
    • Expand the project folder, and right click the target configuration, and launch it
    • connect CPU1 and CPU2

    Are they able to connect both cores?

  • 0 in reply to Santosh Jha
    TI__Mastermind 18180 points

    Hi Santosh,

    Good Day. Please see below the latest response of our customer to your suggestion. Thank you very much.

    I tested blink-led example and it worked!  I cannot understand why this example works and my own projects don't if other PCBs with this microcontroller work. Could you help me please?

    Best Regards,
    Ray Vincent
  • 0 in reply to Ray Vincent Aranzaso
    TI__Guru 50611 points

    Ray,

    Please ask the customer to compare/review the linker command file. They can reuse the target configuration file from the example.

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    TI__Mastermind 18180 points

    Hi Santosh,

    Good Day. Please see below the response of our customer to your suggestion. Thank you very much.

    I get how to reproduce the error by modifying the blinky led example. I switched the program to load not in RAM as it is by default but in FLASH and the same error as when I try to load my project happens. I didn't modify the FLASH cmd, I only switch in the project configuration.

    I realize that the CPU2 can load the program on RAM but it is not possible to load on FLASH. I did the test with blinked led example changing the cmd and also with my own project. Both give me same error.

    Best Regards,
    Ray Vincent
  • 0 in reply to Ray Vincent Aranzaso
    TI__Guru 50611 points

    Ray,

    I just tested on Launchxl-F28379D. If the customer is using the flash configuration, he will need to use Flash configuration for CPU1 and CPU2. If he wants to use standalone mode, then for CPU1, select FLASH_STAND_ALONE build, load and write to flash.

    Again, my recommendation will be to first check the functionality with Blinky_LED from C2000Ware SDK. If it works, then compare/review your project setting. If customer has a project which shows the problem, I can review it.

    Thanks & Regards,

    Santosh