2E2430/2440 Wireless ProjectLecture 2/4-08 Per Zetterberg
2E2430/2440 Wireless ProjectLecture 2/4-08 Per Zetterberg
Agenda
Project management.
DSP programming
PC programming.
In Lab:
Hand out (literature) and equipment.
Short description of equipment.
Information from computer support.
Meet with your project assistant.
After showing Georges slides.
Show DSP cards. How to start CCS. Where to get help.
Show getting-started homepages.
Show how to use EDMA_RTDX_GPIO
Project Management
Project plan due April 1 at 15.00!
on web-page
Project plan shall contain
Background
Specification
Sketch of solution.
Description of tasks.
Allocation of people to tasks.
Time-plan.
See:
www.s3.kth.se/signal/edu/projekt/examination.shtml
Bottom up versus top-down
Top down:
Divide into subtasks.
Divide subtasks into sub-sub tasks.
Design
Implement
Bottom Up:
Learn how to compile.
Send a pulse.
Receive the pulse.
Synchronize to the pulse
…..
Recommendations
Follow bottom and top-down approaches simultaneously.
Dedicate (must)
DSP programmers.
PC programmers.
Algorithm/simulation/theory experts.
Project leader.
Let tasks run in parallel e.g. learning DSP and testing algorithm.
Weekly meetings and progress report
Weekly meetings lead by the group leader on Monday or Tuesdays.
The project assistant will also attend.
Progress reports are minutes of meeting.
Action items assigned.
Follow up against time-plan and old "action items“.
Who has done what the past week
Shall be posted on the group web-site shortly after the meeting.
www.s3.kth.se/signal/edu/projekt/examination.shtml
Progress reports due
www.s3.kth.se/signal/edu/projekt/schedule.shtml 8 April.
15 April.
22 April
29 April.
6 May
13 May
20 May
27 May
Mid-Term Evaluation
DSP assignment. Handed out 16 April.
Handed in by April 29.
Matlab prototype deadline April 29.
System working on real-data but using matlab for processing.
Defined in project specification.
Miscellaneous
Do not contact Texas Instruments directly. Send your enquires to perz@ee.kth.se.
Do not contact support@s3.kth.se directly. Send your enquires to me perz@ee.kth.se.
Awards
All groups shall do a literature search.
Tell if you need some document printed.
Lectures
Are these dates good ? DSP lecture April 2, 10.15. (CCS, EDMA, Loading of data, comparison with matlab, cache, good advices).
DSP lecture April 8. 10.15 (Code optimization). Led by Matthias Kassner from Texas Instruments.
New for this year: Grades
Will be decided shortly after the grand-final “If the prototype is successful, the final-report is well written and contains adequate analysis and all the other deliverables are in good shape then all members who have made significant contributions will receive the highest grade. If this is not the case, the achievements of the individual group members will be scrutinized. This can be done by examining the progress-reports and other documents produced and from observations done during the course of the project”
Conclusion
Get started NOW.
Do literature search.
Get started with the DSP (and PC) reading.
Sketch a solution
Write project plan.
See also project homepage:
http://www.s3.kth.se/signal/edu/projekt/
DSP Programming
Setup in the project course: PC or ”host” DSP or target (or DSK)
What is a DSP ?
A CPU which is optimized for signal processing:
Special instructions for common signal processing operations, e.g. multiply and accumulate.
Often on-chip circuits that handle input/output (IO).
Low power consumption.
Cheap (compared to processors in e.g. desktop computers).
Project Prototype DSP versus PC
Concurrently running programs at both the DSP and the PC.
DSP-card used for:
Signal processing
IO (sampling/playback)
PC used for:
Graphical User Interface (GUI)
Controlling the application, receiving results.
The DSP in the project course
Belongs to the TI C6x family of DSPs State of the art – widely used in industry You will use a Texas Instruments C6713 floating point digital signal processor.
Massively parallel architecture (VLIW) - up to eight 32 bit instructions are executed simultaneously.
Running at 225 MHz, giving 1.2 GFlops peak performance.
Development Tools
Matlab
Algorithm development.
Prototype verification.
User interface development (GUI)
Control of DSP card
Control of code profiling.
DSP: Code Composer Studio
Algorithm implementation in C/Assembler
Debugging in conjunction with Matlab implementation
Code profiling.
Code Development flow
Technical Requirements of Prototype
Real-time functionality
DSP-card: signal processing, PC: user interface
User interface through a GUI (windows style) implemented in matlab.
No unnecessary use of processor time on the PC
Well structured and adequately commented source code
For more details see
www.s3.kth.se/signal/edu/projekt/examination.shtml
Comments