Design Through Curriculum on Embedded Systems Team:Aisha Grieme, Jeff Melvin, Dane Seaberg Advisors: Dr. Tyagi and Jason Boyd Client: Dept. of Electrical and Computer Engineering

REQUIREMENTS Problem Statement Concept Diagram and Sketch Requirements Deliverables

Problem Statement Students end each year with a wealth of new knowledge without having had the opportunity to use concepts from multiple courses in a single project

Concept Description Design a system for use in a design course to link curriculum concepts from junior Computer Engineering courses Multiple tracks in Computer Engineering program Focus to be applied on embedded systems Topics will be enforced through a team embedded systems project System will require teams to apply curriculum concepts from courses

Concept Diagram

Conceptual Sketch Design Through the Curriculum Course CprE 381 Computer Organization CprE 308 Task Management Memory Management ComS 309 Software Design Process Version Control ComS 311 Algorithm Design

Operating Environment Embedded system laboratory

User Interface Description AVR Studio 4 & JTAG Push Buttons LCD Terminal Microsoft Windows

Functional Requirements One-half semester Must have clear documentation Must focus on an adequate sample of curriculum course concepts

Nonfunctional Requirements Platform must be easy to use Must be adaptable for new curriculum or curriculum concepts

Market Survey Performed by Sophomore Design Through Curriculum on Embedded Systems Students showed preference for a “build your own robot” embedded systems project

Deliverables Course outline Demonstrable design project System documentation

PROJECT PLAN Work distribution Recourses and Costs Schedule Risks

Resource and Cost Estimate Time ResourceCourse Resources The department has all the hardware, and the software is open source JTAG Programmer - $300 iRobot Create - $130 Cerebot II - $40 Peripheral Hardware

Risks and Mitigation Plan Time ◦ Risk: The student may not be able to complete the project within the allotted time ◦ Mitigation: Create a timeline for the students to follow and have checkpoints for the students to meet Lack of Background ◦ Risk: Students may lack the background to be able to follow the curriculum ◦ Mitigation: Define a specific skill set and course background to take the class.

DESIGN DETAILS Course Plan Course Hardware Considerations

COURSETOPICIMPLEMENTATION Cpr E 381Computer Organization Students will need to manage the configuration of the system, and what components are turned on Cpr E 308 Task and Memory Management Limited memory, multi tasking system Cpr E 308File Systems Project implements a file system on the operating system Cpr E 308SchedulingTasks require Scheduling Cpr E 308I/O Program on robot must handle incoming data as well as output to computer and other robot Cpr E 288 Embedded System Programming Basic Requirement, the project is on embedded platform Com S 311Algorithm Design Students will need to create an algorithm for the robots to complete the task in a timely manor ComS 309Software Design Process Students will develop a process plan and schedule ComS 309Version Control Students will use subversion to control code changes

Course Plan Week 1: ◦ Get robot, software, and project requirements ◦ Develop process model and project schedule Week 2: ◦ Learn about the system and begin programming ◦ Set up subversion for the team Week 3: ◦ OS should be loaded ◦ Robots should be communicating ◦ Develop algorithms in embedded systems

Course Plan Week 4: ◦ Algorithm design should be finished ◦ Learn about timing in embedded systems Week 5: ◦ Finish algorithm implementation Week 6: ◦ Testing will begin Week 7: ◦ Student will demo their robots

Hardware Considerations BOARD MICRO CONTROLLER OPERATING SYSTEM FILE SYSTEM THREADSTASKS REAL TIME PRIORITY SHIFT MUTEXES OPEN SOURCE cRIOSpartan-3 FPGAVxWorks*****No VEX Robotics: PIC PICmicroSalvoOS?Yes ??No Bug Labs: Bugbase ARM Cortex A-8Poky LinuxYes? ?? Arduino: Mega Atmega1280DuniOSNo Yes Digilent Inc: Cerebot II Atmega128FemtoOSYesNoYes * Access to this functionality was not available, but may have been granted upon request

NI cRIO Used by previous project OS functionality not available Possibility of getting some functionality Interfaces with labVIEW

Vex PIC V0.5 Interfaces with RobotC IDE Documentation shows support for needed functionality Proprietary Non-Vex add-ons

Bug Labs BUGbase Runs Linux, has full support of needed functionality Interfaces with Eclipse Limited emulator functionality Recently Released

Arduino Mega Plenty of memory Available OS has limited functionality IDE for board primitive No components ◦ Which will work ◦ Drivers

Cerebot II and iRobot Create Familiarity ◦ Board ◦ IDE OS choices limited ◦ Femto OS Drivers for components written

IMPLEMENTATION Course Demo Testing Lessons Learned Conclusion

Build and Demo Synchronized “dancing” and playing music Shell interface Bluetooth communication with computer

Testing System Tests ◦ Femto OS API ◦ Open Interface ◦ Dual Robot Communication Course Testing ◦ Lab with target student demographic ◦ Survey and questionnaire

Lessons Learned Need to define research requirements well Importance of adhering to decisions Consequences of an incomplete design Value of seeking expertise in areas of unfamiliarity

Future Work Research and test a more feature rich OS ◦ May require additional hardware research Student and TA instructions Course Testing

Questions?