This website uses cookies so that we can provide you with the best user experience. To read more about the cookies we use and to change your settings see our Cookies Policy.
When an active External Watchdog / System Basis Chip (SBC) or Internal CPU Watchdog is not serviced properly, i t can cause problems such as: Unintended reset during Flash programming or Mass Erase operation Error 258:Failed to initialize debug session BlueBox loses control over the CPU af...
Watchdog periodically resets your system which can cause problems such as u nintended reset during flash programming or mass erase operation, failed debug session, etc.; however it can detect failures, e.g., if your system has hung or it is no longer executing the correct sequence of code....
Possible causes and solutions CPU reset caused by either External Watchdog circuitry or internal CPU watchdog Disable all reset sources during debugging to resolve the issue. More information is available in Active Watchdog issues . F1H, F1Kx: UMI Error R_FCL_ERR_FLMD0 FLMD0-Pin not at hig...
The error means that the debugger failed to connect to the target CPU. This can be for different reasons. When troubleshooting the initial debug connection to the target CPU, it is recommended to use the CPU Reset instead of Download. Possible causes and solutions BlueBox is not properly c...
When Aurix devices are in the debug mode, W atchdog is by default enabled, but the Watchdog Timer is unconditionally suspended (stopped), which means that the Watchdog never resets the chip. To use the Watchdog during debugging, you have to disable the Watchdog Timer suspended logic (or en...
Possible causes: Faulty hardware: Target, Debug Adapter, or Active Probe CPU is always in reset or the debugger cannot reset the CPU Bad contact if the CPU is in a socket External watchdog resets the chip periodically DAP Wide mode is selected in Hardware |CPU Options |SoC , however, only ...
When troubleshooting the initial debug connection to the target CPU, it is recommended to use the CPU Reset debug command instead of the Download debug command. Possible solutions 1. Properly connected BlueBox and Debug Adapter Check if BlueBox is properly connected to the target debug con...
Possible solutions Disable internal watchdog The Internal Watchdog must be disabled because the Watchdog is not stopped when the application is stopped (microcontroller is in the debug mode). In such case, the Watchdog could reset the microcontroller while the application is stopped and th...