How to start helping out?

T

ThomasPDye

New member
I really like the work that pjrc are doing with teensy...

Is there any way I could get involved in testing and development? It seems like there is a lot a of load on Paul at the moment.

I have a working knowledge of c and c++, Makefiles etc. I also have a good knowledge of electronic hardware.

I am a graduate student in Electrical Engineering and I am currently at a loose end for a few months.

I have spent the past 2 days exploring some of the internals of the teensyduino library at https://github.com/PaulStoffregen/cores mostly this was with an interest in evaluating how much work would be needed to start doing lock-free audio dsp on teensy 3.2 or 4.0 upwards.

Please let me know if there's any way I could be of use to the teensy project.

Best Wishes,

Tom
 
Hi and Welcome,

I don't speak for PJRC as I am just another customer. But for me, the best way I have been able to make a few contributions. Is by finding things that interest me and try to help fix existing code and/or write some new code to add additional functionality.

And then if appropriate either create my own github project for it and/or if existing core code or libraries, issuing Pull Requests to the owner of the project.
 
Hi Kurt!

Thanks for the advice. I will make a start digging around the audio library then. See how it does things, since that is the application I had in mind.

Best Wishes,

Tom
 
I'm just a customer, too :) Yes, fixing bugs and to contribute code@ Github is a good thing. Sometime it can takes a long time until it gets merged, so be patient (I'm not... (have many PRs unmerged) ), sometimes it gets merged within seconds..

Audio is lock free?
 
A long term goal is to make everything compatible with multithreading (reentrancy etc), so far nothing was done in this regard, and I think these things would be very helpful.
Same for preparatory work for dual cores for the next planned Teensy.
 
ThomasPDye said:
Hi Kurt!

Thanks for the advice. I will make a start digging around the audio library then. See how it does things, since that is the application I had in mind.

Best Wishes,

Tom
Click to expand...

One thing you could do once you get setup with git up is go through all of the audio examples and use #ifdef where the SPI pins are defined so that it is correct if you use the example on either a Teensy 3.x or Teensy 4.x chip. Whether you want to also switch the SD card from pin 10 to 'BUILTIN_SDCARD' for the Teensy 3.5, 3.6 and 4.1 is up to you. Then issue a pull request so that hopefully Paul will see them and incorporate the fixed example in the next teensydunio.
 
If you want to look at the (OK, one...) bleeding edge of the Audio library, I've taken a stab at making it re-configurable at run time, rather than largely fixed at compile time. See https://forum.pjrc.com/threads/66840-Roadmap-quot-Dynamic-Updates-quot-any-effort-going-on and code at https://github.com/h4yn0nnym0u5e/cores and https://github.com/h4yn0nnym0u5e/Audio. This capability is on @PaulStoffregen's roadmap, though obviously he's had way too much on his plate since the map was drawn! There's also an extended editor GUI: not by me, but the author @manicksan's been very responsive in making changes to support more complex configurations which would suit a re-configurable engine. https://forum.pjrc.com/threads/65740-Audio-System-Design-Tool-update

Cheers

Jonathan
 
You must log in or register to reply here.
Back
Top