Programing BlinkLED_MSP432P401R.out into. MSP-EXP432P401R-LaunchPad Firmware Programmer I closed CCS and tried the DSLite batch file BlinkLED_MSP432P401R.bat again. This time (and from then on) the following came up in the Console: I closed, Unplugged, replugged, reopened CCS again, and clicked debug. The Console said:ĬORTEX_M4_0: Flash Programmer: Writing 23864 bytes to flash memory 0x00000000
CORTEX START FAILED PLEASE TRY AGAIN CODE
I imported the Project into Code Composer Studio Version: 6.4 and clicked Debug. (And, the other examples can also be programmed with their respective batch files.) NOTE: I got the batch files and DSLite from \DSLite\DebugServer\bin\DSLite.exe -c %targetconfig% -f %firmware% It programs the MSP432 Launchpad just fine.īesides the REM's, the batch file is as MSP-EXP432P401R-LaunchPad Firmware Programmer
MSP-EXP432P401R_Software_Examples_windows\Firmware\Binary\BlinkLED_MSP432P401R When my MSP432 Launchpad was new, I was able to run: Then DSLite worked again! (But trying CCS again, killed the Launchpad again, so I repeated the JTAG fix). I re-enabled the JTAG with the procedure beginning on pg 22 in SLAU575B.pdf. I get the same error "Error connecting to the target: (Error -1063 0x0)" with my MSP432 Launchpad, but I will add this detail:ĭSLite.exe IS able to program the MSP432 LaunchPad.ĭSLite.exe was able to program the LaunchPad before I tried to use CCS.Īfter CCS "killed" the LaunchPad, DSLite could NOT program it either. I do NOT have a solution, but perhaps some helpful information. (Emulation package 6.0.14.5)ĭoes this provide any clues as to what may be going on?
CORTEX START FAILED PLEASE TRY AGAIN UPDATE
Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.14.5)Īlso, if I power sycle the board again and re-start CCS, then I get the same original error:ĬORTEX_M4_0: Error connecting to the target: (Error -1063 0x0) Device ID is not recognized or is not supported by driver.
If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. Reset the device, and retry the operation. (Emulation package 6.0.14.5)ĬORTEX_M4_0: JTAG Communication Error: (Error -1170 0x0) Unable to access the DAP.
If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. OK, so a more detailed explanation of what I'm seeing after performing a factory reset, power cycling the board, and attempting to load the blinkLED example is here:ĬORTEX_M4_0: GEL Output: Memory Map Initialization CompleteĬORTEX_M4_0: GEL Output: Halting Watchdog TimerĬORTEX_M4_0: Flash Programmer: Erasing main memoryĬORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000ĬORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1ĬORTEX_M4_0: Error occurred during flash operation: Target failed to read 0圎004300CĬORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480CĬORTEX_M4_0: Failed CPU Reset: (Error -2063 0x0) Unable to reset device.
0 kommentar(er)
