DEV_TARGET_CMD_ERR on breakpoints (Rowley Crossworks)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2011-05-29 4:57 PM
I've just gotten some STM32VLDiscovery boards and am attempting to program them via Rowley Crossworks. I've got the STLink connection working and can download and run programs and view registers, etc. But if I try to set a breakpoint, when that breakpoint is hit I get the above error (DEV_TARGET_CMD_ERR) and, FWIW, both Discovery red LEDs go solid ON. Does this describe any known issue? Any hints as to what may be going wrong? I've tried multiple boards so hardware is ruled out.
BTW, the version of stlinkusbdriver.dll I'm using, from the ST website, is 4.0.1b. Any known problems with that?- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2011-05-31 8:28 PM
OK, problem solved (or at least, disappeared). I made a new project using the same source files to send to Rowley, built it and just tried it for the heck of it, and it works. Good, now I can play.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2011-08-03 2:56 PM
I had this same problem and found that deleting the not found symbols in the Watch window allows breakpoints to work. I've posted this up on Rowley's forum.
