CMSIS-DAP( Debugging in Kell)
Page last updated
19 Jun 2013, by
Dwayne Dilbeck.
1 reply
1 comment on CMSIS-DAP( Debugging in Kell):
The firmware upgrade was simple. Just like programming the unit you drop the firmware on the storage device. Except where you would hit reset with a program, for firmware you need a full power cycle. After the usb cable is plugged back into the system, I now have 3 devices instead of 2 from the mbed.
The Kiel uVision4 install had no issues. Very straight forward.
Exporting the code from the web site was straight forward as well. The project opened and compiled in uVision4. uVision did flag a warning on one statement in my code, that the online compiler saw no issue with.
Issue: The download button in Kiel directly programs the lpc chip. You will not see a new bin file on the mbed drive. But in return no manual reset is required.
Right clicking on code in Kiel to set break points is intuitive. Starting a debug session is also straight forward. Becasue Kiel is an evaluation version a pop up is displayed telling you about the 32kb limit.
One item to note is a debug session will stop in at the first line of code in main and wait for the run command to execute until it hits a break point.
Please log in to post comments.
The firmware upgrade was simple. Just like programming the unit you drop the firmware on the storage device. Except where you would hit reset with a program, for firmware you need a full power cycle. After the usb cable is plugged back into the system, I now have 3 devices instead of 2 from the mbed.
The Kiel uVision4 install had no issues. Very straight forward.
Exporting the code from the web site was straight forward as well. The project opened and compiled in uVision4. uVision did flag a warning on one statement in my code, that the online compiler saw no issue with.
Issue: The download button in Kiel directly programs the lpc chip. You will not see a new bin file on the mbed drive. But in return no manual reset is required.
Right clicking on code in Kiel to set break points is intuitive. Starting a debug session is also straight forward. Becasue Kiel is an evaluation version a pop up is displayed telling you about the 32kb limit.
One item to note is a debug session will stop in at the first line of code in main and wait for the run command to execute until it hits a break point.