-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate templates for XMOS Devices #15
Comments
The code that Vult generates is still processor independent. I made a test some time ago with one of the old XMOS processors I had and it works correctly. What I have in mind is that, when compiling the Vult runtime it would be nice selecting the optimized version of the functions for each processor. |
Sounds rad! I heard good things about XMOS from the module designer that runs Noise Engineering. He has some pretty cool modules. Any specific chips/dev boards I should get to evaluate? |
@MacroMachines A good starting point and cost-effective solution to start with is the XMOS startKit + XA-SK-AUDIO. The audio slice gives you MIDI I/O, 2 x Audio In, 2 x Audio Out and S/PDIF. The startKit also includes the USB Debugger on board for programming and debugging the board. |
I have been considering going the stm32f4 route for my next projects, I'm On Monday, June 6, 2016, Datanoise notifications@github.com wrote:
Nicholas C. Raftis III
|
As mentioned before, the currently generated code compiles correctly in XMOS devices but it does not uses any of the custom XMOS instructions. I'm moving this to the next milestone since I still don't have any XMOS audio board. |
I have not used an XMOS device in a long time. Last time I tried to get one there were some export restrictions. I think I wont be doing any work on them in the short future. Still, the generated code should compile fine. |
The XMOS multicore microcontrollers are great for DSP. It's really easy to develop multicore DSP applications for it and it would really profit from VULT support.
The text was updated successfully, but these errors were encountered: