Has anyone used VisualGdb?
-
I've been thinking of buying VisualGDB - Serious cross-platform support for Visual Studio[^] to do embedded/IoT/MCU stuff from within Visual Studio but the problem with these type of things is they're typically terrible to middling (Arduino IDE, Platform IO) for the free stuff, and I don't know if I want to pay to play for something that's going to be as dodgy as what I've used so far. I want a reliable dev environment, particularly for working with ESP32 and ARM Cortex-A and Cortex-M devices (maybe R too) VisualGDB looks promising but even though it's only $100 I hate when I buy in to a product and it blows up in my face, and I've had too much of that recently. It's trialware but I need to buy hardware to test it anyway because I don't want it if it only works well with ESP32 gadgets and I have no ARMs yet (soon though) I just am not up for the risk of buying it cold right now, but if anyone has had any experiences they want to share, I'd love to hear them.
Real programmers use butterflies
-
I've been thinking of buying VisualGDB - Serious cross-platform support for Visual Studio[^] to do embedded/IoT/MCU stuff from within Visual Studio but the problem with these type of things is they're typically terrible to middling (Arduino IDE, Platform IO) for the free stuff, and I don't know if I want to pay to play for something that's going to be as dodgy as what I've used so far. I want a reliable dev environment, particularly for working with ESP32 and ARM Cortex-A and Cortex-M devices (maybe R too) VisualGDB looks promising but even though it's only $100 I hate when I buy in to a product and it blows up in my face, and I've had too much of that recently. It's trialware but I need to buy hardware to test it anyway because I don't want it if it only works well with ESP32 gadgets and I have no ARMs yet (soon though) I just am not up for the risk of buying it cold right now, but if anyone has had any experiences they want to share, I'd love to hear them.
Real programmers use butterflies
It has a 30 day free trial. I've been using it for years now for cross platform Windows/Linux development, on a variety of embedded hardware (Custom and Raspberry PI). It does the job well, although the built in tools in VS are catching up for Linux. Not used it for simpler processors yet though.
-
It has a 30 day free trial. I've been using it for years now for cross platform Windows/Linux development, on a variety of embedded hardware (Custom and Raspberry PI). It does the job well, although the built in tools in VS are catching up for Linux. Not used it for simpler processors yet though.
Are you a super hero by chance and if so, what are your special abilities?
-
It has a 30 day free trial. I've been using it for years now for cross platform Windows/Linux development, on a variety of embedded hardware (Custom and Raspberry PI). It does the job well, although the built in tools in VS are catching up for Linux. Not used it for simpler processors yet though.
Yeah, trials are nice but like I said, I don't have the hardware yet to put it through its paces for everything I'd want to use it for. Before I buy in, I wanted to hear from people that had used it, so thanks. Mostly my concern is ARM stuff, particularly Cortex-M since i think microsoft is already able to target cortex-a via UWP unless i miss my guess.
Real programmers use butterflies
-
I've been thinking of buying VisualGDB - Serious cross-platform support for Visual Studio[^] to do embedded/IoT/MCU stuff from within Visual Studio but the problem with these type of things is they're typically terrible to middling (Arduino IDE, Platform IO) for the free stuff, and I don't know if I want to pay to play for something that's going to be as dodgy as what I've used so far. I want a reliable dev environment, particularly for working with ESP32 and ARM Cortex-A and Cortex-M devices (maybe R too) VisualGDB looks promising but even though it's only $100 I hate when I buy in to a product and it blows up in my face, and I've had too much of that recently. It's trialware but I need to buy hardware to test it anyway because I don't want it if it only works well with ESP32 gadgets and I have no ARMs yet (soon though) I just am not up for the risk of buying it cold right now, but if anyone has had any experiences they want to share, I'd love to hear them.
Real programmers use butterflies
I bought VisualGDB a couple of years ago for a project with a Raspberry PI, ESP32 and the CC1310 (Sub GHz Arm based RF processor). For the Pi and ESP, it worked well. Hid a lot of the gory detail of the build environment setup. Support was fast and competent when getting it going. I now don't know what bits are VS and what are VGDB so have to keep subscribing to support the, now completed, project. VGDB seems to stay out of the way when doing Microsoft stuff on the same VS. Remote debug works a treat on the PI, a few limitations with the ESP32 but still useful. The CC1310, sadly, wasn't supported but they said you can script an environment for other processors if you have the time and inclination. I am happy enough with CCS for that part however. Overall, would, knowing what I know now, buy it again. All up, VGDB saved me a lot of time, avoiding all the intimate build and debug stuff I didn't want to get involved in. Better focus on the application. Proviso is, I was being very vanilla about the PI and ESP32 parts so no experience of non-standard usages and I am an old school, monitor and tag debugger so didn't stretch the debugging much. Hope it is a little helpful.
-
I bought VisualGDB a couple of years ago for a project with a Raspberry PI, ESP32 and the CC1310 (Sub GHz Arm based RF processor). For the Pi and ESP, it worked well. Hid a lot of the gory detail of the build environment setup. Support was fast and competent when getting it going. I now don't know what bits are VS and what are VGDB so have to keep subscribing to support the, now completed, project. VGDB seems to stay out of the way when doing Microsoft stuff on the same VS. Remote debug works a treat on the PI, a few limitations with the ESP32 but still useful. The CC1310, sadly, wasn't supported but they said you can script an environment for other processors if you have the time and inclination. I am happy enough with CCS for that part however. Overall, would, knowing what I know now, buy it again. All up, VGDB saved me a lot of time, avoiding all the intimate build and debug stuff I didn't want to get involved in. Better focus on the application. Proviso is, I was being very vanilla about the PI and ESP32 parts so no experience of non-standard usages and I am an old school, monitor and tag debugger so didn't stretch the debugging much. Hope it is a little helpful.
Thank you so much!
Real programmers use butterflies
-
I've been thinking of buying VisualGDB - Serious cross-platform support for Visual Studio[^] to do embedded/IoT/MCU stuff from within Visual Studio but the problem with these type of things is they're typically terrible to middling (Arduino IDE, Platform IO) for the free stuff, and I don't know if I want to pay to play for something that's going to be as dodgy as what I've used so far. I want a reliable dev environment, particularly for working with ESP32 and ARM Cortex-A and Cortex-M devices (maybe R too) VisualGDB looks promising but even though it's only $100 I hate when I buy in to a product and it blows up in my face, and I've had too much of that recently. It's trialware but I need to buy hardware to test it anyway because I don't want it if it only works well with ESP32 gadgets and I have no ARMs yet (soon though) I just am not up for the risk of buying it cold right now, but if anyone has had any experiences they want to share, I'd love to hear them.
Real programmers use butterflies
Maybe this is something down the road .NET nanoFramework taps C# for embedded systems | InfoWorld[^]