In Milestone 3, we demonstrate our ability to tackle complex engineering problems by applying fundamental principles of electronics and computing to our senior design project. We showcase our design, implementation, and testing process, highlighting the technical challenges we’ve solved along the way. Additionally, we emphasize our teamwork, detailing how we’ve effectively distributed tasks, coordinated efforts, and kept each team member fully engaged through regular discussions and assessments.
3.1 Implementation
Current Progress:
To send audio data from the microcontroller (bottom right) to the microprocessor (top right), we need a router (bottom left) to give them both IP addresses so that they can communicate over TCP/IP. We used a simple travel router for this purpose and made the microprocessor the TCP server and the microprocessor the TCP client. Next, we need to set up the Real-Time Streaming Protocol (RTSP), the communication protocol we'll be using to stream audio data between the client and server.
Setbacks:
This is our first time using products from Renesas, which required us to get familiar with an IDE called E^2 Studio. All programming has occurred within this IDE.
Momentum has been hard to establish due to the Renesas products we are using requiring a high-skill floor to navigate and make changes to base libraries/systems. We've configured and grown familiar with two important internal systems, those being ThreadX and NetX. ThreadX is a real-time operating system that takes care of the scheduling for the multiple tasks that each microcontroller/microprocessor is running. NetX is a thread-safe network protocol stack built on top of ThreadX that enables communication such as TCP/IP.
Due to a recent change in the component being used as a Bluetooth module, we are slightly behind in our design schedule for the implementation of audio intake. We'll continue to emphasize board intercommunications because this event unfortunately also set back audio processing and output.
3.2 Design and Test
Here is an early proof of communication. As stated earlier, the microprocessor acted as the TCP server that sent a message to the client as soon as the connection was established over their respective communication ports. As is seen in the photo, we were able to confirm that the message did get received by the microcontroller.
3.3 Teaming and Leadership
Vincent Renda
Set up TCP connection for microcontroller and microprocessor.
Assisting with RTSP communication.
Nicholas DeRobertis
Working on Inter-IC Sound (I2S) connection between microprocessor and digital-to-analog converters.
Chris Kniss
Working on I2S connection between microprocessor and digital-to-analog converters.
Arminder Singh
Working on RTSP communication between microprocessor and microcontroller.
Erik Bobinski
Set up a bootloader for the microprocessor.
Helped get TCP code working for the microprocessor.
Andrew Lee
Setting up Bluetooth module and connection to microcontroller.