This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uVision 5.24.2.86 drops out when trying to debug.

It seems to go through the motions, downloading etc and when it is due to reconfigure itself, it disappears.

This is a new installation on a new laptop (previous computer worked ok).

Tried un-installing and re-installing uVision and Si8051F_uVision.exe driver.

Suggestions?

Parents
  • This is not uVision's fault. It's the debug driver you're using, it signals a lost connection to the device under test. Without a connection to the target, uVision exits debug mode and that's what you're seeing.

    What debug driver are you using? Did you check for updates? What debug adapter are you using? If it is a self-made one, it may be worth thinking about getting one from the device's manufacturer. What board are you trying to debug, is it a manufacturer provided evaluation board or is it a custom board? If it is a custom one, did you check an official eval board? And how do you power your target? Did you check that you've a clean and stable supply? Did you check the DUT's reset pin and it external circuitry for being correct? Did you check the debug adapters cables?

    BTW: Firmware can cause such observations as well. Better do not enter low-power modes during debug. This too may cause lost connections.

Reply
  • This is not uVision's fault. It's the debug driver you're using, it signals a lost connection to the device under test. Without a connection to the target, uVision exits debug mode and that's what you're seeing.

    What debug driver are you using? Did you check for updates? What debug adapter are you using? If it is a self-made one, it may be worth thinking about getting one from the device's manufacturer. What board are you trying to debug, is it a manufacturer provided evaluation board or is it a custom board? If it is a custom one, did you check an official eval board? And how do you power your target? Did you check that you've a clean and stable supply? Did you check the DUT's reset pin and it external circuitry for being correct? Did you check the debug adapters cables?

    BTW: Firmware can cause such observations as well. Better do not enter low-power modes during debug. This too may cause lost connections.

Children