[sdiy] STM32 (or other) audio DSP learning recommendations

Thu Jul 5 16:03:16 CEST 2018

Well, perhaps you'll beat me to publishing an open source project, but 
I've been using STM32F7 + SAI + I2S codec for a few years in proprietary 
products. The Synthtech E352 and E370 are both based on the F7 + I2S DAC 
and there were a few R&D projects with true codecs and SDRAM memory that 
I did prior to those that never saw the light of day.

Working on an H7 design right now. ;)

Eric

On 07/05/2018 06:52 AM, Martin Klang wrote:
> 
> Looks like I'll beat Eric to it! Check out his most excellent project 
> page here:
> 
> http://ebrombaugh.studionebula.com/synth/stm32f4_codec/index.html
> 
> 
> 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).
> 
> 
> 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):
> 
> https://github.com/pingdynasty/OpenWare/
> 
> The code is in heavy development though and I don't recommend it for 
> readability, correctness, or intelligibility.
> 
> 
> Martin
> 
> 
> On 04/07/18 01:02, ulfur hansson wrote:
>> 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.
>>
>> we have a WM8731 DAC on board, but alas setting up the code properly 
>> for use with the STM seems a little tricky.
>>
>> 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 ;)
>>
>> any help/direction towards further resources would be immensely 
>> helpful and well appreciated!!
>>
>> all the best,
>> -úlfur
>>
>> Sent from outer space
>>
>> On Jun 29, 2018, at 8:00 AM, Steve <sleepy_dog at gmx.de 
>> <mailto:sleepy_dog at gmx.de>> wrote:
>>
>>> "A debugging IDE not (based on) Eclipse"
>>>
>>> I've heard some people are using Code::Blocks, I'm not sure there are 
>>> any readily made support packages for embedded work, though.
>>> 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.
>>>
>>> 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.
>>> 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.
>>> 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.
>>> 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
>>> 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)
>>> Usable overviews of where program & RAM memory bytes are going is 
>>> also nice vs. hacking some script that shows some ASCII barf of that...
>>> Did I mention performance profiling with usable result browsers 
>>> linked with source code...
>>> (I think TrueStudio comes with that ready-to-use)
>>>
>>> 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...
>>>
>>> You can tame Eclipse and shape it a lot (perhaps? ;)) to your liking, 
>>> though.
>>> I know it's messy, but once it's set up and running...
>>> 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.
>>>
>>> - Steve
>>> *Gesendet:* Freitag, 29. Juni 2018 um 02:05 Uhr
>>> *Von:* "Chris McDowell" <declareupdate at gmail.com 
>>> <mailto:declareupdate at gmail.com>>
>>> *An:* music.maker at gte.net <mailto:music.maker at gte.net>
>>> *Cc:* synth-diy at synth-diy.org <mailto:synth-diy at synth-diy.org>
>>> *Betreff:* Re: [sdiy] STM32 (or other) audio DSP learning recommendations
>>> 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
>>>
>>>
>>> Chris
>>>
>>> > On Jun 28, 2018, at 6:55 PM, Scott Gravenhorst <music.maker at gte.net 
>>> <mailto:music.maker at gte.net>> wrote:
>>> >
>>> >
>>> > John Speth <john.speth at andrews-cooper.com 
>>> <mailto:john.speth at andrews-cooper.com>> wrote:
>>> >>> Eclipse ... is ... the ... nightmare.
>>> >>
>>> >> Is there a free debugger UI that is NOT Eclipse.
>>> >
>>> > That is a good question.
>>> >
>>> > I'll admit that I just use the LEDs and VCP.
>>> >
>>> > -- ScottG
>>> > 
>>> ________________________________________________________________________
>>> > -- Scott Gravenhorst
>>> > -- http://scott.joviansynth.com/
>>> > -- When the going gets tough, the tough use the command line.
>>> > -- Matt 21:22
>>> >
>>> > _______________________________________________
>>> > Synth-diy mailing list
>>> > Synth-diy at synth-diy.org <mailto:Synth-diy at synth-diy.org>
>>> > http://synth-diy.org/mailman/listinfo/synth-diy
>>>
>>>
>>> _______________________________________________
>>> Synth-diy mailing list
>>> Synth-diy at synth-diy.org <mailto:Synth-diy at synth-diy.org>
>>> http://synth-diy.org/mailman/listinfo/synth-diy
>>> _______________________________________________
>>> Synth-diy mailing list
>>> Synth-diy at synth-diy.org <mailto:Synth-diy at synth-diy.org>
>>> http://synth-diy.org/mailman/listinfo/synth-diy
>>
>>
>> _______________________________________________
>> Synth-diy mailing list
>> Synth-diy at synth-diy.org
>> http://synth-diy.org/mailman/listinfo/synth-diy
> 
> 
> 
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy
> 