Posted: January 21st, 2015

Systems Engineering Technologies mini project

Systems Engineering Technologies mini project

Project description
1. Objective
The object of this lab is to learn through examples USB Demo from WOLF topic.
2. Project Task
You need design a program that read the text file from USB mass storage onto LCD with moving speed via the potentiometer also available on the board.
3. USB Introduction
USB was developed (in the mid-1990s) by Compaq, Intel, Microsoft, and NEC, joined later by Hewlett-Packard, Lucent and Philips. The USB was developed as a new means to

connect a large number of devices to the PC, and eventually to replace the legacy ports (serial ports, parallel ports, keyboard and mouse connections, joystick ports,

midi ports, etc.). The USB is based on a tiered star topology in which there is a single host controller and up to 127 slave devices. The host controller is connected

to a hub, integrated within the PC, which allows a number of attachment points (referred to as ports). This is illustrated in the figure below.
USB is a four-wire bus (requires a shielded cable containing 4 wires) that supports communication between a host and one or more (up to 127) peripherals. The host

controller allocates the USB bandwidth to attached devices through a token-based protocol. The bus supports hot plugging and dynamic configuration of the devices. All

transactions are initiated by the host controller.
The host schedules transactions in 1 ms frames. Each frame contains a Start-Of-Frame (SOF) marker and transactions that transfer data to or from device endpoints. Each

device can have a maximum of 16 logical or 32 physical endpoints. There are four types of transfers defined for the endpoints.
? Control transfers are used to configure the device.
? Interrupt transfers are used for periodic data transfer.
? Bulk transfers are used when the rate of transfer is not critical.
? Isochronous transfers have guaranteed delivery time but no error correction.
MCBSTR9 has a USB 2.0 interface that can be configured as:
??
Host
Device
OTG: USB On-The-Go
4. Example USB
The USB demo example is a demo program for the MCBSTR91x board. It demonstrates an USB Memory based on USB Mass Storage Class.
LEDs are used to display the following:
– P7.0: LED_RD is on when USB Device is performing Read access – P7.1: LED_WR is on when USB Device is performing Write access – P7.2: LED_CFG is on when USB Device is

configured
– P7.3: LED_SUSP is on when USB Device is suspended
The USB Memory is automatically recognized by the host PC running Windows which will load a generic Mass Storage driver.
This is not an easy project example. However, take some time to read the source code and try to get a birds-eye-view understanding of it. Start with memory.c and

backtrack the function calls. Only with a thorough understanding of the USB theory this source code would be easier to digest.
5. Report Writing
Well-conceived designs and well-written documents can help establish engineers as valuable resources in their workplaces.
A design report is written by and for technical personnel, and it must contain enough technical information to allow a fellow engineer to independently recreate the

design. It is one of the essential deliverables for any design project, almost equal in importance to the design itself.
A report serves several needs: it provides fellow engineers a convenient means to understand, evaluate and/or reuse work; it allows marketing/business personnel to

extract project details that they may need; it allows engineers to recall their work months or years later; and it provides a means for engineers to disseminate their

work.
A typical design report includes a description of the design objectives, technical descriptions of all major design blocks, a statement of the final success and/or

utility of the design, a list of all hardware and software tools required to complete the design, locations of all source files, and references to external sources

(like data sheets, specifications, or other design reports) where pertinent information can be found. A design report should present relevant design information in a

clear and concise manner, without any narrative discussions or stories about how the design. STR91x data sheet provides good examples of concise design information.
This guide provides guidelines that can be helpful in preparing a suitable report for most design projects, but it cannot address all possible design environments.

Different reports will require different amounts of detail, and perhaps even different content and organization altogether. Some reports may be a few pages long, and

some may require dozens of pages. Every report must be tailored to the design at hand, but in general, these guidelines can serve as a starting point for most

situations.
The following section provides an outline of a design report. In general, the major headings should be included in your report. A table of contents is generally not

required unless the report is longer than 15 to 20 pages, and a list of figures is not required at all.
6. Report Outline:
Title Page (with your group member picture and contribution of each group member)
Introduction
? Abstract
? Objectives
? Features?in?Brief
? Project Summary
? Tools Required
? Design Status
Background
? Reference Material Design
? Features and Specifications
? Design Overview
? Detailed Design Description
Discussion
? Problems Encountered
? Engineering Resources Used
? Marketability
? Community Feedback
References

Portfolio Task 2 – min-projects
Students are required to carry out project plan in the week 6 and work as pair towards design. Formal written report must be submitted along with code.
To do these students should:
•  Made plan on the software and hardware ?
•  Analyse the software interface and how to communicate with hardware ?
•  Demonstrate their work during workshop session ?If necessary, students may also use the internet for their research. However design using

sources entirely from the internet is not acceptable for this assignment and their work will be marked down accordingly. Student should demonstrate the design process.

?
6cc002 Modern Computer Science Marking Criteria for the part two of portfolio work (2) See the detailed work sheet with indicative marking comments.
Submission of work
The completed work for assignments must be handed in on or before the due date. Students must keep a copy or backup of any assessed work that you submit. Failure to do

so may result in students having to repeat that piece of work.
Electronic submission:
This is normally done via WOLF. Any special instructions will be available on the upload tag or within the assessment brief.
Penalties for late submission of coursework
Standard University arrangements apply. ANY late submission will result in the grade 0 NS being allocated to the coursework.
Procedure for requesting extensions / mitigating circumstances
This is done via eVision. Further information can be found at http://www.wolvesunion.org/advice/academic/
Retrieval of Failure
Where a student fails a module (less than 40% for undergraduate modules, less than 50% for postgraduate modules) they have the right to attempt the failed assessment

(s) once, at the next resit opportunity (normally July resit period). If a student fails assessment for a second time they have a right to repeat the module.
NOTE: Students who do not take their resit at the next available RESIT opportunity will be required to repeat the module.
Return of assignments
Assignments will be normally returned within three working weeks.
If students have any questions regarding their feedback they normally have two working weeks from the date when receive their returned assessment and/or written

feedback or receive their exam results to contact and discuss the matter with the lecturers.
Cheating
Cheating is any attempt to gain unfair advantage by dishonest means and includes plagiarism and collusion. Cheating is a serious offence. You are advised to check the

nature of each assessment. You must work individually unless it is a group assessment.
Plagiarism is defined as incorporating a significant amount of un-attributed direct quotation from, or un- attributed substantial paraphrasing of, the work of another.
Collusion occurs when two or more students collaborate to produce a piece of work to be submitted (in whole or part) for assessment and the work is presented as the

work of one student alone.
1. Objective
The object of this lab is to learn through examples USB Demo from WOLF topic.
2. Project Task
You need design a program that read the text file from USB mass storage onto LCD with moving speed via the potentiometer also available on the board.
3. USB Introduction
USB was developed (in the mid-1990s) by Compaq, Intel, Microsoft, and NEC, joined later by Hewlett-Packard, Lucent and Philips. The USB was developed as a new means to

connect a large number of devices to the PC, and eventually to replace the “legacy” ports (serial ports, parallel ports, keyboard and mouse connections, joystick

ports, midi ports, etc.). The USB is based on a “tiered star topology” in which there is a single host controller and up to 127 “slave” devices. The host controller is

connected to a hub, integrated within the PC, which allows a number of attachment points (referred to as ports). This is illustrated in the figure below.
USB is a four-wire bus (requires a shielded cable containing 4 wires) that supports communication between a host and one or more (up to 127) peripherals. The host

controller allocates the USB bandwidth to attached devices through a token-based protocol. The bus supports hot plugging and dynamic configuration of the devices. All

transactions are initiated by the host controller.
The host schedules transactions in 1 ms frames. Each frame contains a Start-Of-Frame (SOF) marker and transactions that transfer data to or from device endpoints. Each

device can have a maximum of 16 logical or 32 physical endpoints. There are four types of transfers defined for the endpoints.
•  Control transfers are used to configure the device. ?
•  Interrupt transfers are used for periodic data transfer. ?
•  Bulk transfers are used when the rate of transfer is not critical. ?
•  Isochronous transfers have guaranteed delivery time but no error correction. ?MCBSTR9 has a USB 2.0 interface that can be configured as: ?

Host?Device?OTG: USB On-The-Go
4. Example USB
The USB demo example is a demo program for the MCBSTR91x board. It demonstrates an USB Memory based on USB Mass Storage Class.?LEDs are used to display the following:
– P7.0: LED_RD is on when USB Device is performing Read access – P7.1: LED_WR is on when USB Device is performing Write access – P7.2: LED_CFG is on when USB Device is

configured?- P7.3: LED_SUSP is on when USB Device is suspended
The USB Memory is automatically recognized by the host PC running Windows which will load a generic Mass Storage driver.
This is not an easy project example. However, take some time to read the source code and try to get a birds-eye-view understanding of it. Start with memory.c and

backtrack the function calls. Only with a thorough understanding of the USB theory this source code would be easier to digest.
5. Report Writing
Well-conceived designs and well-written documents can help establish engineers as valuable resources in their workplaces.
A design report is written by and for technical personnel, and it must contain enough technical information to allow a fellow engineer to independently recreate the

design. It is one of the essential deliverables for any design project, almost equal in importance to the design itself.
A report serves several needs: it provides fellow engineers a convenient means to understand, evaluate and/or reuse work; it allows marketing/business personnel to

extract project details that they may need; it allows engineers to recall their work months or years later; and it provides a means for engineers to disseminate their

work.
A typical design report includes a description of the design objectives, technical descriptions of all major design blocks, a statement of the final success and/or

utility of the design, a list of all hardware and software tools required to complete the design, locations of all source files, and references to external sources

(like data sheets, specifications, or other design reports) where pertinent information can be found. A design report should present relevant design information in a

clear and concise manner, without any narrative discussions or stories about how the design. STR91x data sheet provides good examples of concise design information.
This guide provides guidelines that can be helpful in preparing a suitable report for most design projects, but it cannot address all possible design environments.

Different reports will require different amounts of detail, and perhaps even different content and organization altogether. Some reports may be a few pages long, and

some may require dozens of pages. Every report must be tailored to the design at hand, but in general, these guidelines can serve as a starting point for most

situations.
The following section provides an outline of a design report. In general, the major headings should be included in your report. A table of contents is generally not

required unless the report is longer than 15 to 20 pages, and a list of figures is not required at all.
6. Report Outline:
Title Page (with your group member picture and contribution of each group member)
Introduction
•  Abstract ?
•  Objectives ?
•  Features-in-Brief ?
•  Project Summary ?
•  Tools Required ?
•  Design Status ?Background ?
• Reference Material Design
•  Features and Specifications ?
•  Design Overview ?
•  Detailed Design Description ?Discussion
•  Problems Encountered ?
•  Engineering Resources Used ?
• Marketability?• Community Feedback
References
Mini_Project Marking Sheet
I. Technical ( 40%)

Does the project display efficient system design of functional hardware peripherals??Was the functionality of the system design effectively and creatively demonstrated

in the system?
Was the software complex, original and fully functional??Is the hardware efficiently used as possible to build the project?     Comments:
II. Coding (30%)

Is the core, underlying idea understandable, creative, feasible, path-breaking, etc?     Comments:
III. Written Report (20%)

Is the written report thorough, clear, compelling, logical, elegant, and professional?     Comments:
IV. Report Presentation (10%)

Is the report thorough, well structured, clear, compelling, logical, informative, and professionally delivered?     Comments:
Overall Grade:

References
Tomsho, G. (2009). MCTS Guide to Configuring Microsoft Windows Server 2008 Active Directory (Exam #70-640). New York, NY: Cengage Learning.

PLACE THIS ORDER OR A SIMILAR ORDER WITH US TODAY AND GET AN AMAZING DISCOUNT 🙂