Forum Replies Created
-
Posts
-
I guess it’s just a difference in semantics, then. I thought “from scratch” meant that there was an “Empty Project” template like VisualGDB offers for other ARM devices that I’ve used. Or, better yet, something like the Pico Project Generator that lets you select what features you want (e.g. I2C and SPI), and generates the necessary CMakeLists.txt with a bare-bones main.c file.
However, that’s just a nice-to-have. I can just choose an example that’s closest to what I want, then replace the code. Also, the Pico Project Generator works well with VisualGDB’s “Import an existing project” option, so I’m good to go.
No problems to report – the Pico support looks ready for release to me.
Thanks,
Dan.
Hi,
Yes, your suggestion of using OpenOCD with the WinUSB driver fixed the problem. It works really well — I’ve used the debugger with a few different small projects and haven’t run into any problems.
This is off-topic, I know, but I’m wondering about a statement in your tutorial:
“The Raspberry Pi Pico Project wizard allows creating new projects from scratch…”
I didn’t see any way to do that, so I’ve been using the Pico Project Generator to create projects, then open them in VisualGDB using the “Import an existing project” option.
I’m wondering if I missed something: is there a way to create a new Pico project using only VisualGDB? If not, that’s OK: using the Pico Project Generator approach is fine with me.
Thanks,
Dan.
Hi,
Thanks to you both for the information.
I’ll try updating the J-Link driver and moving more of my code to RAM to see if that improves things. If not, it’s good to know that it’s not just something wrong with my setup.
Fred, I was originally using the GDB Stub and ran into problems there with breakpoints and single-stepping. I thought that might be caused by me having moved all of my code into Flash, so I switched to OpenOCD to free up more RAM. It’s good to know that GDB Stub isn’t 100% reliable either. As you say, I can live with the limitations now that I know they exist.
Thanks,
Dan
Teensy is actually not a great match for VisualGDB. While you might be able to use VisualGDB to build the code, debugging it is pretty much impossible because the Teensy doesn’t expose SWD or JTAG pins. A hardware hack is possible – see http://mcuoneclipse.com/2014/08/09/hacking-the-teensy-v3-1-for-swd-debugging/ – but not for the faint of heart. I doubt
If you really want to use the Teensy, you’re better off doing development using another development board with a similar Kinetix processor then deploy it to the Teensy (perhaps with Teensy’s Arduino IDE) when everything has been tested and debugged.
Dan.
