![]() 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? 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 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |