<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div> </div>
<div>"A debugging IDE not (based on) Eclipse"<br/>
<br/>
I've heard some people are using Code::Blocks, I'm not sure there are any readily made support packages for embedded work, though.<br/>
But it's native C++, not Java based, so the little naps that Eclipse may have every now and then because of that, aren't there in C::B.<br/>
<br/>
It's not just step-through debugging at a few key's press and some mouse hovering over variables that's nice about debugging with an IDE.<br/>
Also memory watches that highlight when regions of interest changed, changing display/numerical format or how a data pointer is interpreted wich a few clicks.<br/>
And RTOS aware debugging if you have multiple threads - which can easily be called for on a beast like stm32F7, depending on the natuer of the project.<br/>
I mean, probably you could run Quake on that "micro controller" with one of the boards that has 8MB RAM or so, if somebody bothered to make an optimized port of the inner rendering loop (which is famous for being incomprehensively optimized for the Pentium60) :D<br/>
And if you have plugins for a tree view of peripheral registers and named register bits and stuff, it can save a lot of time (and reduce human error factor)<br/>
Usable overviews of where program & RAM memory bytes are going is also nice vs. hacking some script that shows some ASCII barf of that...<br/>
Did I mention performance profiling with usable result browsers linked with source code...<br/>
(I think TrueStudio comes with that ready-to-use)<br/>
<br/>
All that stuff is about as much fun to do as a daily routine solely on the command line as writing SUBLEQ assembly programs as a daily routine...<br/>
<br/>
You can tame Eclipse and shape it a lot (perhaps? ;)) to your liking, though.<br/>
I know it's messy, but once it's set up and running...<br/>
I wouldn't want to miss *language aware* project-wide code editing features (e.g. rename, extract function, etc), anyone doing that with mere text search & replace tools needs buttocks paddling.<br/>
<br/>
- Steve</div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag, 29. Juni 2018 um 02:05 Uhr<br/>
<b>Von:</b> "Chris McDowell" <declareupdate@gmail.com><br/>
<b>An:</b> music.maker@gte.net<br/>
<b>Cc:</b> synth-diy@synth-diy.org<br/>
<b>Betreff:</b> Re: [sdiy] STM32 (or other) audio DSP learning recommendations</div>
<div>I actually use openstm32 for work (and synths, duh) and it's generally a breeze. They have an all-in-one installer for OSX. pretty great<br/>
<br/>
<br/>
Chris<br/>
<br/>
> On Jun 28, 2018, at 6:55 PM, Scott Gravenhorst <music.maker@gte.net> wrote:<br/>
><br/>
><br/>
> John Speth <john.speth@andrews-cooper.com> wrote:<br/>
>>> Eclipse ... is ... the ... nightmare.<br/>
>><br/>
>> Is there a free debugger UI that is NOT Eclipse.<br/>
><br/>
> That is a good question.<br/>
><br/>
> I'll admit that I just use the LEDs and VCP.<br/>
><br/>
> -- ScottG<br/>
> ________________________________________________________________________<br/>
> -- Scott Gravenhorst<br/>
> -- <a href="http://scott.joviansynth.com/" target="_blank">http://scott.joviansynth.com/</a><br/>
> -- When the going gets tough, the tough use the command line.<br/>
> -- Matt 21:22<br/>
><br/>
> _______________________________________________<br/>
> Synth-diy mailing list<br/>
> Synth-diy@synth-diy.org<br/>
> <a href="http://synth-diy.org/mailman/listinfo/synth-diy" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a><br/>
<br/>
<br/>
_______________________________________________<br/>
Synth-diy mailing list<br/>
Synth-diy@synth-diy.org<br/>
<a href="http://synth-diy.org/mailman/listinfo/synth-diy" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a></div>
</div>
</div>
</div></div></body></html>