Forum Replies Created
-
AuthorPosts
-
Ken MacfarlaneParticipant
Yes, that’s exactly what happens. However, there is no Raw Terminal tab in the project props.
I tried creating the same but on an F407VG (my target, not an ST eval board), but there, the F4 doesn’t even appear in device manager. I was careful to make a USB_FS example. I’m pretty sure that the USB is a FS slave.
Ken MacfarlaneParticipantDon’t think this works properly yet – the Select a USB Device lists 2 identical debuggers – same Programmer type, Windows device name, Vendor ID, Device ID & Interface (ST-Likn v2.1, St Microelectronics ST.., 0483, 374B & 00 in my case). Although I can pick one, regardless of which one I pick, the OpenOCD test exits with code 1.
Ken MacfarlaneParticipantOh, and VS has to be restarted after you update OpenOCD, or you get a bogus message about the memory at the stack location not being writeable!
Ken MacfarlaneParticipantFound it – under Install Support for Additional debug methods (on the Debug Method Tab), it allows you to update any of the debuggers installed. Note that when you test the OpenOCD settings, it says e.g
Open On-Chip Debugger 0.9.0 (2016-05-03), but doesn’t actually give the revision (it must have been r8 here, because now the dates changed to 2016-05-10 & r9)
Ken MacfarlaneParticipantSorry, but I can’t see how to update openOCD . Is this something that I can do from within VS? Also, I don’t know how to tell what version I’m using – it’s dated May 6th, 2016. I’ve poked about under the “Show help on configuring OpenOCD” link on the Debug Settings tab under Project Properties for example.
Ken MacfarlaneParticipantHi,
I’m not sure if this is the same problem as I don’t know how to tell if its the CppEngineHost – the whole VisualStudio app hangs on startup every 2nd day or so. I can get round it by creating each new project in its own solution, in a new directory. The others around me who are more knowledgeable about VS than I am, reckon that the problem is the number of files that VS has to parse on startup due to having ~10 projects in my stmF7 solution, & that it could be fixed by deleting all of VS’s temporary files e.g. the .pdb’s & .vcxproj’s, but I haven’t tried this yet as I’m not convinced I’ve got all the files I need under Git yet!
Ken MacfarlaneParticipantUnder the Makefile settings, the default Linker Script path has spaces in it, so you have to make a local copy & then the warning stops (that breakpoints aren’t going to work properly).
-
AuthorPosts