Other Parts Discussed in Thread: TMDSCNCD28388D
Purchased TI’s 28388D main chip.
With reference to the schematic design of TMDSCNCD28388D, I designed a circuit board by myself.
From June to December this year, the board can be used normally.
However, recently, when I programmed the board, I kept getting errors. The errors are as follows:
The following two are detailed burning exception log records:
C28xx_CPU1: GEL Output: Memory Map Initialization Complete C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... C28xx_CPU1: GEL Output: ... DCSM Initialization Done ... C28xx_CPU1: GEL Output: CPU2 is out of reset and configured to wait boot. (If you connected previously, may have to resume CPU2 to reach wait boot loop.) C28xx_CPU1: GEL Output: CM is out of reset and configured to wait boot. (If you connected previously, may have to resume CM to reach wait boot loop.) 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. User code execution from SR could commence after both flash banks are programmed. C28xx_CPU1: Only CPU1 on-chip Flash Plugin can configure clock for CPU1, CPU2 and CM Flash operations. Plugin automatically configures PLL when CPU1 Flash operations are invoked. However, if users want to do only CPU2 or CM Flash operations without doing a prior CPU1 operation in the current session, they should click on 'Configure Clock' button in CPU1's on-chip Flash Plugin before invoking CPU2 and CM Flash operations. When this button is used, Flash Plugin will configure the clock for CPU1/CPU2 at 190MHz and CM at 95MHz using INTOSC2 as the clock source. Plugin will leave PLL config like this and user application should configure the PLL as required by application. C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... C28xx_CPU1: GEL Output: ... DCSM Initialization Done ... C28xx_CPU1: GEL Output: CPU2 is out of reset and configured to wait boot. (If you connected previously, may have to resume CPU2 to reach wait boot loop.) C28xx_CPU1: GEL Output: CM is out of reset and configured to wait boot. (If you connected previously, may have to resume CM to reach wait boot loop.) C28xx_CPU1: Failed CPU Reset: (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 9.5.0.00143) C28xx_CPU1: Error: (Error -1135 @ 0x3FD2AE) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.5.0.00143) 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 C28xx_CPU1: GEL: Error while executing OnReset(-1): Could not write 0x0005FB00@Data: target is not connected at *((int*) 0x5FB00)=0 [f28388d_cpu1.gel:27] at OnReset(-(1)) C28xx_CPU1: Error occurred during flash operation: CPU Reset error. Error code -1 C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FB00@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x00007029@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read register ST1: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write register ST1: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x00007029@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D22E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x00007062@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005FB00@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F824@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F820@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F980@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000000@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error setting the GSxMSEL register for Flash operations C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000000@Data: target is not connected C28xx_CPU1: Flash Programmer: Error during initialization (missing algorihtm). Operation Cancelled. C28xx_CPU1: File Loader: Memory write failed: Unknown error C28xx_CPU1: GEL: File: F:\workspace_v10\led_ex1_blinky\CPU1_FLASH\led_ex1_blinky.out: Load failed. C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000000@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error setting the GSxMSEL register for Flash operations C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00000000@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error setting the GSxMSEL register for Flash operations C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled. C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug. C28xx_CPU1: Error occurred during flash operation: Could not read 0x00070223@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: GEL Output: Memory Map Initialization Complete C28xx_CPU1: Failed CPU Reset: (Error -6311) PRSC module failed to write to a register. (Emulation package 9.5.0.00143) 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 9.5.0.00143) C28xx_CPU1: Error: (Error -1135 @ 0xD057) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.5.0.00143) 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 C28xx_CPU1: GEL: Error while executing OnReset(-1): Could not write 0x0005FB00@Data: target is not connected at *((int*) 0x5FB00)=0 [f28388d_cpu1.gel:27] at OnReset(-(1)) C28xx_CPU1: GEL: Error while executing OnTargetConnect(): Reset failed: retcode=-1 at GEL_Reset() [f28388d_cpu1.gel:117] at OnTargetConnect()
After a problem occurs, check the schematic diagram and PCB of the board, and measure the resistance, capacitance and inductance of the power supply module and JTAG module, and use the oscilloscope to measure the stability of the 25M crystal oscillator.
No problem, the boot mode is also dialed to the condition that GPIO84 and GPIO72 are both pulled high (after the power is off, the program starts from the flash).
Generally speaking, when the circuit board is only downloading programs (using JTAG port, emulator xds200), errors are prone to often occur. Sometimes, occasionally, the program can be downloaded, and the program can run normally after the power is turned off and on again. From the working state of the circuit board, everything is normal.
The main chip and JTAG schematic diagram connection diagram, crystal diagram, power module:
I'm here to ask if there is anything else that might go wrong. Hope to get some guidance.
grateful!
