<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>Looks like I'll beat Eric to it! Check out his most excellent
project page here:</p>
<p><a class="moz-txt-link-freetext" href="http://ebrombaugh.studionebula.com/synth/stm32f4_codec/index.html">http://ebrombaugh.studionebula.com/synth/stm32f4_codec/index.html</a></p>
<p><br>
</p>
<p>It's for the F4 again, but the differences aren't that huge. It
uses the I2S peripheral though, not the SAI (since the STM32F407
didn't have it).</p>
<p><br>
</p>
<p>For a SAI example for the same codec you could have a look at my
new OWL / OpenWare firmware, which also uses the ST HAL (for
better or worse):</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/pingdynasty/OpenWare/">https://github.com/pingdynasty/OpenWare/</a></p>
<p>The code is in heavy development though and I don't recommend it
for readability, correctness, or intelligibility.<br>
</p>
<p><br>
</p>
<p>Martin<br>
</p>
<br>
<div class="moz-cite-prefix">On 04/07/18 01:02, ulfur hansson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7ABD0BDC-6AF9-497B-8040-4B90372078C2@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
me and my buddy just recently managed to get a custom STM32F7
board to blink an LED (!) it’s my first digital design project,
and a little blinking light has never made me this happy before.
<div><br>
</div>
<div>we have a WM8731 DAC on board, but alas setting up the code
properly for use with the STM seems a little tricky.
<div><br>
</div>
<div>does anyone have a boilerplate setup/lesrning resource for
this particular DAC? the best resource we’ve found so far
seems to be a mutable instrument design that has the same chip
but for an M4 - we would love to find more detailed info on
how to properly implement it into out code on the F7 - no need
to reinvent the wheel here i reckon ;)</div>
<div><br>
</div>
<div>any help/direction towards further resources would be
immensely helpful and well appreciated!!</div>
<div><br>
</div>
<div>all the best,</div>
<div>-úlfur<br>
<br>
<div id="AppleMailSignature">Sent from outer space</div>
<div><br>
On Jun 29, 2018, at 8:00 AM, Steve <<a
href="mailto:sleepy_dog@gmx.de" moz-do-not-send="true">sleepy_dog@gmx.de</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<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" <<a
href="mailto:declareupdate@gmail.com"
moz-do-not-send="true">declareupdate@gmail.com</a>><br>
<b>An:</b> <a href="mailto:music.maker@gte.net"
moz-do-not-send="true">music.maker@gte.net</a><br>
<b>Cc:</b> <a
href="mailto:synth-diy@synth-diy.org"
moz-do-not-send="true">synth-diy@synth-diy.org</a><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 <<a
href="mailto:music.maker@gte.net"
moz-do-not-send="true">music.maker@gte.net</a>>
wrote:<br>
><br>
><br>
> John Speth <<a
href="mailto:john.speth@andrews-cooper.com"
moz-do-not-send="true">john.speth@andrews-cooper.com</a>>
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" moz-do-not-send="true">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>
> <a href="mailto:Synth-diy@synth-diy.org"
moz-do-not-send="true">Synth-diy@synth-diy.org</a><br>
> <a
href="http://synth-diy.org/mailman/listinfo/synth-diy"
target="_blank" moz-do-not-send="true">http://synth-diy.org/mailman/listinfo/synth-diy</a><br>
<br>
<br>
_______________________________________________<br>
Synth-diy mailing list<br>
<a href="mailto:Synth-diy@synth-diy.org"
moz-do-not-send="true">Synth-diy@synth-diy.org</a><br>
<a
href="http://synth-diy.org/mailman/listinfo/synth-diy"
target="_blank" moz-do-not-send="true">http://synth-diy.org/mailman/listinfo/synth-diy</a></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Synth-diy mailing list</span><br>
<span><a href="mailto:Synth-diy@synth-diy.org"
moz-do-not-send="true">Synth-diy@synth-diy.org</a></span><br>
<span><a
href="http://synth-diy.org/mailman/listinfo/synth-diy"
moz-do-not-send="true">http://synth-diy.org/mailman/listinfo/synth-diy</a></span><br>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Synth-diy mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Synth-diy@synth-diy.org">Synth-diy@synth-diy.org</a>
<a class="moz-txt-link-freetext" href="http://synth-diy.org/mailman/listinfo/synth-diy">http://synth-diy.org/mailman/listinfo/synth-diy</a>
</pre>
</blockquote>
<br>
</body>
</html>