I’ve been spending the last weeks building vector math libraries & dsp libraries for some stm32 projects I’m working on and it occurs to me the code is largely reusable on the aleph directly. Was hoping for a little guidance on how to get setup for testing & profiling the code, along with some ideas on what needs to happen in the libraries. I figure the starting point would be rolling some vector math functions that utilize the bf-intrinsics. I’m not sure if bf has parallel processing, but even on stm32 without it, there’s some subtle performance boosts from the memory access standpoint. Beyond that I’d like to start rebuilding the dsp libraries for block processing as there’s likely many more gains to be had there.
So my questions:
Is using the block-processing versions as simple as loading the .ldr like a normal module? I’ve got the ‘rawsc’ module compiling but no aleph handy rn.
Is there any kind of instructions for how to use the bfin_sim to test code in the box? Further to clarify, is the sim audio based, or just visual / debug-ready (sorry for the ignorance here).
Along these same lines, are there recommendations for how to do profiling of the code to make sure the block processing are outperforming their iterative versions? I know the code can be disassembled (a link on how to would be great!) but is there some other kind of automated profiler?
Those are the big ones, and from there I guess it’s just a matter of any guidance / caveats / work already done somewhere and unnecessary to revisit…