Keil Logo

Debugging with ULINK2

Follow the steps below to start debugging using the µVision Debugger and the ULINK2 USB-JTAG Adapter.

  1. Connect the ULINK2 to the Cortex Debug connector of the MCB1000 Board.
    MCB1000 Board Connected to ULINK2
  2. Power up the MCB1000 Board.
  3. Configure the Debugger in the Project — Options for Target — Debug dialog.

    Options for Target Button Use the Options for Target toolbar button and click the Debug tab to display the Debug dialog.

    Use: ULINK Cortex DebuggerSelect the Use: radio button and then ULINK Cortex Debugger in the drop-down list to choose the ULINK2 USB-JTAG Adapter as the debugging tool.

    Use: ULINK ARM DebuggerCheck the Load Application at Startup and the Run to main() options to load your application and execute code up to the beginning of your main() function when the debugger starts.

  4. Click the Settings button to open the ARM Target Driver Setup dialog.

    This dialog displays the IDCODE of the ARM device on the MCB1000 Board.

    Options for Target - Debug - Settings - JTAG Device Display

    Download OptionsSelect the Verify Code Download option under Download Options to compare the loaded application program with the Flash ROM content. You may disable this option to speed up the debugger start.

    SWD SelectionMake sure the Port: selector is set to SW. The MCB1xxx boards does not support a JTAG interface.

  5. Click OK to save any changes you have made, then start the Debugger.

    Start/Stop Debug Button Use the Start/Stop Debug Session toolbar button or the menu Debug — Start/Stop Debug Session to start debugging the program.


  • Debugging stops working properly if the code puts the device into a power saving mode. Therefore, do not enable either of the power saving modes while testing and debugging software.
  • Further details can be found in the µVision User's Guide, topic Debugging, and in the MDK-ARM Primer, chapter Debug Applications.
  • ITM and DWT trace debugging are not available with the MCB11U10, MCB1114 or MCB11C14 boards because their MCUs do not provide the Serial Wire Output(SWO) signal needed for these options. As a result, the Logic Analyzer and OS Event Viewer features of the debugger are also not available because they require the SWO signal.
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.