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.

TMS320F28388D: C2000

Part Number: TMS320F28388D
Other Parts Discussed in Thread: TMDSCNCD28388D

Trouble Reading Register PC:
(Error -1156 @ 0x0)
Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
(Emulation package 9.2.0.00002)

When I power on the board, I plug in the emulator first, and then power on. Use CCS10.0 to download the program to RAM, it can be downloaded normally. But when you choose to download to FLASH, an error will be reported, as shown above.

The power chip used by my circuit board is: TPS62420DRCR

The output of this chip has two channels. The current can reach 1000ma (1.2V) and one can reach 600ma (3.3V).

For the chip, there will be a certain amount of pressure on the load (I want to ask if this is the reason for the above error.) (Error -1156 @ 0x0)


I considered this situation, so I removed a lot of components on the board (LED light, DC-DC module), touched the power chip for a while, and found that the temperature was normal. When soldering the small LED lights and DC-DC modules that were removed before, the power chip will be very hot.

After removing the LED light and DC-DC module, power on the board and download the program to FLASH, the above error will still occur. (Error -1156 @ 0x0)
Download to RAM, it can still be downloaded normally.

Here to ask

thank!

vince

  • Hi Vince,

    Can you scope the Vout of TPS62420DRCR when you try to program your code into the Flash? I have a feeling that slew rate on supply is slow hence not able to support instantaneous current spike when you try to program the Flash.

    Best Regards,

    Nirav

  • hi,Nirav Ginwala 

    This power chip is dual-channel output. I tested the voltage range of 3.3V and 1.2V respectively, and the results are as follows:

    Let me talk about my understanding. In CCS10.0, start the program download to FLASH. One of the 3.3V voltages of TPS62420DRCR fluctuates: from 3.331V to 3.330V, the other voltage of 1.2V also changes in the same way.
    Then, during the download process, an error will be reported:

    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)

    Download again, it will report PRSC errors

    thanks

    vince

  • HI,Nirav Ginwala

    You mentioned that the flash memory cannot be programmed to support instantaneous current spikes. What causes it in general?

    What I think is that there may be two reasons:

    1. The output current of the two channels of the power chip is relatively small.
    2. The input voltage of the power chip is 5.5V and the current is 2A. Is it possible that the current provided by the input voltage cannot meet the power consumption requirements of the entire circuit board?

    thanks

    vince

  • Vince,

    Yes, your understanding looks correct!

    The moment flash is turned on there will be instantaneous current spikes if your supply isn't able to source the current, you need to change then you might have these problems.

    Regards,

    Manoj

  • HI,Manoj Santha Mohan 

    I plan here to try to replace the power chip with two output channels, the maximum current is 800ma respectively. (The model is TPS62410DRCR)
    Do you think my idea is feasible?

    THANKS

    VINCE

  • Hello, is there a problem with my BOOT choose circuit?

    1. When I close the switch, download the program to RAM, and it can be downloaded normally, but once I click to run, an error will be reported:

    Trouble Halting Target CPU:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)

    Download the program to FLASH, report an error:

    Error connecting to the target:
    (Error -6001) Internal Error: PRSC module detected an unknown failure.
    (Emulation package 9.2.0.00002)

    2. When I turn on the switch, I download the program to RAM, the download is unsuccessful, and an error is reported:

    Error connecting to the target:
    (Error -6001) Internal Error: PRSC module detected an unknown failure.
    (Emulation package 9.2.0.00002)

    Download the program to FLASH, report an error:

    Error connecting to the target:
    (Error -6001) Internal Error: PRSC module detected an unknown failure.
    (Emulation package 9.2.0.00002)

    How can we solve this dilemma?

    thanks

    vince

  • Vince,

    What the difference between closing the switch and turn-on switch? For me, it looks the same. I don't think your boot mode pins circuitry is contributing to the problem.

    Have you tried programming your RAM code (or) flash code in anyother reliable board setup? For example, TI control cards / TI evaluation board?

    Can you share your PCB schematics specifically related to VDDIO / VDD power supply? Also, how close are you bypass capacitors placed near to the device? If the bypass capacitors aren't close enough, it may not be able to source sudden  inrush current requirements.

    Regards,

    Manoj

  • hi,Manoj Santha Mohan

    Hello, the same project (led_ex1_blinky.c) was tested and run on TMDSCNCD28388D, and everything is normal.
    If you let go of the circuit boards you design, two problems often arise:

    1、Error connecting to the target:
    (Error -6001) Internal Error: PRSC module detected an unknown failure.
    (Emulation package 9.2.0.00002

    2、Trouble Halting Target CPU:
    (Error -1156 @ 0x0)
    Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
    (Emulation package 9.2.0.00002)

    Can you share your PCB schematics specifically related to VDDIO / VDD power supply? Also, how close are you bypass capacitors placed near to the device? If the bypass capacitors ar

    The PCB diagram is as follows, the bypass capacitor is placed under the 28388D (28388D is on the TOP layer, and the bypass capacitor is on the bottom layer)

    thanks

    vince

  • Vince,

    I'd like to try and reduce the CPU clock to see if we can get the LED blinky code to run in a stable manner.  This will help us nail down if we have a current supply issue(and then we can debug why that it happening some more).

    Inside the device.h file in the blinky project you'll see this at line 214  I've modified the IMULT by 1/2, so we will run the device at 100MHz vs 200MHz.

    Please try and re-compile with this change and let's see if things are more stable.  If that doesn't work, you can try IMULT of 8, etc.

    Please confirm that your input clock is 25MHz(same as controlCARD), since we are looking at this section of code.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    #define DEVICE_OSCSRC_FREQ 25000000U
    //
    // Define to pass to SysCtl_setClock(). Will configure the clock as follows:
    // PLLSYSCLK = 25MHz (XTAL_OSC) * 16 (IMULT) / (2 (REFDIV) * 2 (ODIV) * 1(SYSDIV))
    //
    #define DEVICE_SETCLOCK_CFG (SYSCTL_OSCSRC_XTAL | SYSCTL_IMULT(16) | \
    SYSCTL_REFDIV(2) | SYSCTL_ODIV(2) | \
    SYSCTL_SYSDIV(1) | SYSCTL_PLL_ENABLE | \
    SYSCTL_DCC_BASE_1)
    //
    // 100MHz SYSCLK frequency based on the above DEVICE_SETCLOCK_CFG. Update the
    // code below if a different clock configuration is used!
    //
    #define DEVICE_SYSCLK_FREQ ((DEVICE_OSCSRC_FREQ * 16) / (2 * 2 * 1))
    //
    // 25MHz LSPCLK frequency based on the above DEVICE_SYSCLK_FREQ and a default
    // low speed peripheral clock divider of 4. Update the code below if a
    // different LSPCLK divider is used!
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Best,
    Matthew

  • thanks,trying  it

  • HI,MatthewPate

    I am honored to have your help.

    First of all, the design of my hardware circuit and the selection of materials are based on the design of TMDSCNCD28388D.

    The above figure is the sum value of the active crystal oscillator.

    The following two figures are the value of the original program and the modified value.

    1. After changing to 16, start to download the program to the RAM of the circuit board, it can be downloaded normally, but after clicking Run, the following error appears:

    However, in this case, I power off the circuit board and re-powered it on, then burned the program into FLASH, and successfully burned into it.

    Burning again, it won't work. The error result is as follows:

    2. Next, I changed 16 to 8 as follows:

    At this point, successfully download the program to RAM, click Run, and start to report an error:

    Then, power off the circuit board, power on again, program the program to FLASH, and report an error:

    Not sure, do I understand what you mean! According to my understanding, the above test has been done.

    thanks

    vince

  • Vince,

    Thanks for doing this; I'm not familiar with the PRSC error from the XDS200 I'm not sure what a router error would be.

    I'm going to suggest that after you run the code, I'm going to suggest we single step the code until we hit the C instruction that causes the emulation break and then note that and reply back to this post with that info.

    Let's stick with 100MHz for now just to give some margin to the CPU clock.  Doing the above will let us narrow down the root cause, the emulator errors could be many different things at this point.

    Best,

    Matthew

  • HI,MatthewPate

    thanks,i will run and debug step by step。

    If the reason is found, the situation will be reported back here.

    thanks

    vince