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

reg:no cortex m sw device found

Can any one say clearly about this problem,
i was trying to load the code but i am getting "no cortex m sw device found".
Iam using Jtag to load the code

  • Not sure there is a clear answer, there are a multitude of reasons why things fail.

    Device not connected properly
    Device not powered proplery
    Device enters low power state
    Device held in reset by other components on the board
    User code reconfigures GPIO pins used by debugger
    Pod expects VTarget voltage to drive buffers
    Pod needs newer firmware/drivers

  • Hello Adithya,

    Please provide more information on the device, debug adapter, board, MDK version. You did not provide much to make a good guess on.

    Did you see this entry:

    "No Cortex-M SW Device Found No Cortex-M processor-based device detected (using Serial Wire). Device is not connected, or not powered, or the debug interface is not working. Enable the SWJ switch in the ULINK USB-JTAG/SWD Adapter section of the Target Driver Setup - Debug dialog."

    On this page: http://www.keil.com/support/man/docs/ulink2/ulink2_errors.htm ?

    Also if the application code you previously flashed onto the device:
    - enters a lower power or system_off
    - modifies the port pins that are used for a debug connection
    - Goes to sleep

    ... then the device will be off when you try to connect, the connection will fail, and you get this message. If you think any of these may be the case, try changing the Connect and Reset Options in Options For Target — Debug — Settings are set as follows: The Connect: option must be set to under Reset The Reset: option must be set to HW RESET

    ... if none of that works and it is a custom board, do you have the nRESET pin of the device connected to ULINK2, so ULINK2 can control it? If not, you need to choose a different reset option in Options For Target — Debug — Settings .