• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 855 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430F449 processor reset failed: could not find device (or device not supported)

Alex Birman
Prodigy 20 points

Other Parts Discussed in Thread: MSP430F449

Hi,

I'm trying to debug TI MSP430F449 with Rowley CrossStudio 2.0.9 through TI USB JTAG MSP-FET430UIF. I've successfully connected to the device, but when I try to download to it or resetting it or anything else, I get the error "processor reset failed: could not find device (or device not supported)".

I got this project (including all its configurations) from CrossStudion 1.0.3 and the project definitely worked, including fully functional debugging.

Please help.

Thanks.

  • 0
    TI__Intellectual 935 points

    Hello Alex,
    I think it makes more sence if you adress this at Rowleys forum.
    http://rowley.zendesk.com/home

    Regards,
    Thomas Mitnacht

  • 0 in reply to Thomas Mitnacht
    Prodigy 20 points

    I'm trying both sides. I've posted the question there, but since I've seen in Google that this problem appears with various IDEs, I think it might be related either to the MCU/board itself, or the JTAG.

  • 0 in reply to Alex Birman
    Guru 227245 points

    The error message 'reset failed' is misleading. The software does not know whether the reset failed or not. It only knows that the device is not responding as it should after a reset. But this may have different reason than a failed reset.

    It is, of course, possible that the JTAG pins are connected wrong. Then after a reset, the connection cannot be established as expected. But it may as well be that the device is immediately after the reset entering a state where it does not respond to the JTAG anymore.
    One example is the voltage supervisor. If the application programs the voltage supervisor of some MSP devices wrongly, then the supervisor will hold the device in reset state until its (unreachable) conditions are met or the device makes a pwer cycle. Unfortunately, after power-on, the debugger/programmer won't take control over the device immediately (as it does not control the power-on). So the device will execute the faulty code and again the device does nto respond anymore. In some cases, temporarily applying a  higer supply voltage (if this doesn't destroy the circuit) or applying VCC to the external voltage sense pin will 'release' the processor from the voltage supervisors grip and JTAG can grab it and erase/replace the faulty program.

    Another possible cause for this kind of error is when a program crashes immediately after start 8e.g. by programming a reset vector that points into vacant memory space or SFR space, causing an immediate reset again and again. This cannot be solved by applying different voltages, of course.

    Another approach that worked in thsi case too was a lock circuit for the reset line. It did hold reset low after power-on, until it detected a reset pulse from the programmer. So the device was kept from executing any code before the (re)programming started. Implemented as a patch cable between programmer and target.

**Attention** This is a public forum