Week 5

Title of Activity
-Circuit Diagram.
-PCB Design


Objective
-To do PCB design on the PCB board using any software that related such as PCB Design or Eagle.
-To create the circuit diagram on the PCB board.

Content/Procedure
-This is the circuit diagram for this project and this circuit will be used on the PCB board.

Circuit Diagram for Talking Voltmeter

-The design  for the PCB board.

PCB design

Result/Analysis
 -When doing the design there is a bit difficulty on doing it. This is because the software is not a very familiar and this the first time I design the PCB on the PCB board.
 -It take a lot of time just to design it. If anything missing from the circuit you need to start over again and design it from the beginning.

Conclusions
 As a conclusions, to design the PCB one must know to read the circuit and make sure nothing is missing. If not, you need to start design it over again. Also has some knowledge on using the software how to design the PCB and this is something that essential for student in technical studies. 

Week 4

Title of Activity
-Debugging a project.


Objective
-To gives an introduction to how to debug a project. The guidelines assume that you have already created and built a project as described in Getting started: New project.

Content/Procedure
-Prior to starting debugging, a proper debugger must have been selected. As mentioned the AVR Simulator will be used for this example.
-The currently selected device and debugger is displayed in the Device and Debugger tool bar. If no debugger is selected, the Current Tool button will say No Tool as shown here.

-To select a debugger, simply click on the Current Tool button. This opens the debugger selection and configuration in the project properties. The debugger selection and configuration can also be opened via the project Properties menu item found at the bottom of the Project menu. You can also open the project properties by right-clicking on the project node in the Solution Explorer window.

-Select a debugger.

1. Open the project propeties dialog from the Project menu.
2. In the Tool section of the propeties, select the AVR Simulator .
3. Click OK

-There are several ways to start a debug session.
-The Alt+F5 key combination or the Start Debugging and Break menu item builds the project and launches the debugging session. On encountering the main() function the execution is suspended . The same is achieved using the F10 key or the Step Over menu item. The project is not built if it is up to date.
-The F5 key or Continue menu entry builds the project and upon a succesful build launches the debugging session using the selected debugger. This shortcut does not suspend execution until a user breakpoint is hit.









-The Start Without Debugging menu item loads the application into the target device but does not start a debugging session. This command is used as an alternative to the stand-alone Programming Dialog described in later sections. Note that Start Without Debugging uses the projects debug configuration and not the settings specified in the stand-alone Programming Dialog.

-Start debugging.

1. In the Debug menu, select Start Debugging and Break.
2. AVR Studio will compile the project, upload the application to the program memory of the AVR Simulator and run to the start of the main() function. AVR Studio displays the text "Debugging" in the title line, indicating that a debugging session is active.

-AVR Studio allows you to control the execution of the target through a large number of commands. These commands are available on the Debug menu or through keyboard shortcuts.

-Resume and suspend execution.

1. In the Debug menu, select Continue. The AVR Simulator will resume execution, indicated by the text "Running" in the title line of AVR Studio.
2. In the Debug menu, select Break All. AVR Studio suspends execution. The yellow arrow marks the code line that will be executed when execution is resumed the next time. 

-Breakpoints provides another means of controlling program execution. Once a breakpoint in your code is "hit" by the debugger, execution is suspended.
-A breakpoint can be placed in the source code by clicking in the gutter area next to the source line where you want program execution to be suspended. Alternatively by selecting Toggle Breakpoint in the Debug menu, or simply by pressing F9.
-A red circle will appear in the gutter area.

-Place a breakpoint and run.

1. Position the text marker on a line in the application and press F9.
2. Press F5 to resume execution. AVR Studio will execute code until the breakpoint is hit and then suspend execution.

-AVR Studio allows you to observe the current state of the debugged Device through a number of debugger windows. Examples of debugger windows are the memory views, the watch view and the IO view.
-The debugger windows can be accessed on the Debug -> Windows menu or by using specific keyboard shortcuts. Most of the windows will only contain useful information when execution is stopped.

-Open the memory view

1. Make sure execution is halted (the title bar of AVR Studio should say "Debugging")
2. Navigate to Debug -> Windows -> Memory and select Memory 1. AVR Studio will open the memory window.
3. Select "data INTERNAL_SRAM" in the pull-down menu labeled "Memory" over the memory content. This displays the internal SRAM of the selected device.

-To end the debugging session and go back to code editing, select Shift + F5 or select Stop Debugging from the Debug menu.

Result/Analysis
 -This is the step how to debug the program in Atmel Atmega644.
 -Also it more friendly user and easy to understand.

Conclusions
 As a conclusions, the introduction to debugging code projects in AVR Studio. All aspects of debugging are described more in detail in the Debugging section in the AVR Studio

Week 3

Title of Activity
-How to program Atmel Atmega using AVR Studio 5.


Objective
-To program the Atmel Atmega microcontroller using AVR Studio 5.


Content/Procedure
-There is several type of Atmel and for this project the microcontroller will use is Atmel Atmega644.
-To program it, AVR Studio 5 software will be use.
-Start page

AVR Studio 5 start page

-Creating new project.
-On the Start Page discussed in getting started with AVR Studio 5, click the New Project option.

New Project

 -The wizard project appear.

New Project Wizard

-About project types.

Types of project

-How to create a project.

1. In the New Project dialog box, select Installed Templates. This lists the available project types.
2. For this example, create an AVRGCC C Executable Project.
3. In the Name box, type a name for the new project.
4. In the Location box, select a save location.
5. AVR Studio will suggest a name in the Solution name box. You can override this name if wanted.
6. Leave the Create directory for solution checkbox checked.
7. Click OK.

-Choosing a Target Device
-When a new project is created, the Device Selection dialog is displayed and you will be prompted to select the project target device.

Device Selection

 -The device selection dialog lists all supported devices for the current project type. To narrow down the selection of devices, select the device family in the Device Family field, or use the Search for Device field to view a filtered list of devices matching your search string.

-Select a device.

1. In the Device Selection dialog, select Atmel Atmega644
2. Click OK

-Writing and compiling code.

Compiling Code

-Example type of code.

Example Code

-To compile the project, press F7 key or select Build Solution from the Build menu.
Result/Analysis
 -AVR Studio automatically opens the newly created C file in the source editor. If the file is closed at any time, double click on [Project_name].c - in this case AVRGCC1.c - to open it in the editor.
At this time the C file contains only an include statement for I/O manipulation and a simple main() function.
 -AVR Studio now builds the application. All output from the compiler is listed in the output window.

Conclusions
 As a conclusions, the introduction to creating code projects in AVR Studio. All aspects of projects are described more in detail in AVR Studio projects.

Week 2

Title of Activity
-Find the hardware and equipment for FYP progress.


Objective
-Check and get the related tools for the FYP project.

Content/Procedure

-For the equipment and tools, it can be getting it in the hardware shop. With enough tools, the project progress will be started in this week.

-There are also to try to look at the several hardware shop, for getting some raw material that supposed to be used in this project.
Result/Analysis
 -For the project progress, at the end of this week the equipment and tools have been buy and all the raw materials related to this project also have classified.

Conclusions
 As a conclusions, the project progress, the problems in the ordered component will be overcome with some other planning. What the important thing in this project  are the student should plan the project progress and try to complete it before the due date and make sure that project progress completed during Engineering Day.