In our code, we use the HALT assembly instruction of the ColdFire in our ASSERT statements to stop our debugger to alert the developer of a serious error. Although ASSERT code should be removed when not debugging, sometimes it can be missed, causing our devices to inadvertently halt when an assert occurs.
If it's possible, it would be great if the firmware could detect whether a debugger is connected, and if it is not, then to branch around the HALT instruction and take alternate action.
Is anyone aware of whether this is possible? Do any of the BDM registers contain such information?