Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CCS/TMS320F28379D: Not a power supply issue: low-power mode when initializing PLL and peripheral clocks

$
0
0

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

Hello, 

I am experiencing the exact similar situation as the one described on this closed thread :

however, I have tested this with Agilent bench power supplies, LDOs and other sources and I keep running into the same issue. What could be the problem?

CCS/TMS320F28379D: Issue with low-power mode when initializing PLL and peripheral clocks

http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/744697?CCS-TMS320F28379D-Issue-with-low-power-mode-when-initializing-PLL-and-peripheral-clocks#pi320995filter=all&pi320995scroll=false 


  • I am also using a custom board:   TMS320F28379D - PTP package
  • A 10MHz crystal with 18pF
  • I've verified JTAG connectivity (XDS 100v2 emulator)

 

Error Message:

C28xx_CPU1: Error: (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 7.0.100.0)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: 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

When trying to initialize the PLL for 200MHz using the C2000Ware function InitSysPll() in F2837xD_SysCtrl.c with call: InitSysPll(XTAL_OSC,IMULT_20,FMULT_0,PLLCLK_BY_2); the debugger crashes with the following error:

C28xx_CPU1: Error: (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 7.0.100.0)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: 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

I can step through the program, which crashes at ClkCfgRegs.SYSCLKDIVSEL.bit.PLSYSCLKDIV = divsel; at the end of the PLL routine with the following errors:

C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: 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_CPU1: Can't Single Step Target Program: (Error -1156 @ 0x81B1) 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 7.0.100.0)
C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0x81B1) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
C28xx_CPU1: Error: (Error -1135 @ 0x81B1) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: 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



Viewing all articles
Browse latest Browse all 262198

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>