# \[GSoC\] Co-Processors Update #6

**URL:** <https://www.ruby-forum.com/t/gsoc-co-processors-update-6/230975>\
**Category:** GNU Radio\
**Created:** [July 15, 2014, 8:13pm UTC](https://www.ruby-forum.com/t/gsoc-co-processors-update-6/230975 "2014-07-15T20:13:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [July 15, 2014, 8:13pm UTC](https://www.ruby-forum.com/t/gsoc-co-processors-update-6/230975/1 "2014-07-15T20:13:06Z")

</div>

Hello all,

Logistical:

- GSoC students don’t forget to provide a quick update at the dev call  
July  
17th 1700 UTC
- One month left until pencils down

Progress:

- I was able to open the FFTC driver handle successfully so I can now  
send  
it data! I used a different approach that does communication with the  
FFTC  
through the DSP cores so first need to write a little test then I need  
to  
figure out the ARM\<==\>DSP communication through their resource manager  
system. It should be painless from here on out since I’m now debugging  
reasonable errors instead of crazy memory descriptor dma allocation  
errors.  
I plan to update the wiki soon and push some code this week/weekend.

- Took a thorough look at the CppUnit testing suite to better understand  
the qa done in the runtime in an effort to make hacking runtime easier.  
Will release my notes before the call on thursday.

Thanks everyone for the guidance.