Experimental three reports 20135209 Pan Heng 20135204 Shi Zhiyu

Beijing Institute of Electronic Technology (BESTI)

Real Inspection report

Course: Information Security system Design Basic class: 1352

Name: Pan Heng Shi Zhiyu

Study No.: 20135209 20135204

Score: Instructor: Lou Jia Peng Experimental Date: 2015.11.24

Experiment level: Preview degree: Experiment time: 15:30~17:30

Instrument Group: 04,09 Compulsory/elective: Compulsory experiment serial number: 03

Experiment Name: experiment three

Experimental purposes and requirements:                                                                                  &NBS P              

1. Learn The principle of driving design under Linux;

2. Master the process of driving development and debugging by using the module method.                                                     

Experimental instrument:

Name	Model	Number
Embedded experimental Platform	Up-tech s2410/p270	1
PC Machine		1

Experiment contents, steps and experience:

First, the experimental steps

1.0 Connect the Experimental box power, use serial line, line, network cable, connect the experiment box and the host

1.1 Install Ads (install files in 00-ads1.2 directory, crack method 00-ads1.2\crack directory)
1.2 Installing the Giveio driver (installation files in the 01-giveio directory)
Copy the entire Giveio directory to the C:\WINDOWS and copy the Giveio.sys file under the directory to c:/windows/system32/drivers.
In the Control Panel, choose Add Hardware > Next > select-yes i have connected this hardware > Next > Check-Add New Hardware Device > Next > Check Install I manually select from list

Hardware > Next > select-Show All devices > select-Install from disk-browse, specify drive as C:\WINDOWS\GIVEIO\giveio.inf file, click OK, install driver

1.3 Installing the JTAG driver (install files in the 02-uarmjtag2.0 directory)

1.4 Configure HyperTerminal: Baud rate is 115200, data bit 8, no parity, stop bit 1, no data flow control.
1.5 Test the basic installation is correct, refer to document "03-Test document. pdf", test program in 04-test directory

1. Run the ADS1.2 integrated development environment.

2. Click the File->open option.

3. Select the project file we use the API function of/ucos V6.0/EXP11 drawing in CD-ROM for example select EXP11.MCP and click Open.

4. Select the file you want to compile in the blank location in front of the corresponding folder to select, the header file library file is not selected, because it has been included in the source code.

5. Click Make to compile the link.

Compile results appear after compilation, and the secondary picture shows no errors, 4 warnings, and 15 additional information. If the result is not the following, the possible problem is that the code path has Chinese,

To copy the code in an English directory, there may be a problem with the Exp11_data folder in the Code folder, delete the Exp11_data folder.

6. Be sure to turn on the Uarmjtag click Initialize configuration option before running the debugger ARM9 click OK. Minimize to the pallet and ensure our platform stops in the Vivi state.

7. Click the Debug button to debug the simulation, and the debug interface is displayed.

8. If this status is not available, click Options->configure Target and Pop up the dialog box. To set it. The main changes were two places:

Name: Select Arm Ethernet driver;configuration: configured to: 127.0.0.1. Click OK, then select ADP to click OK.

The loading interface will appear after you determine. If the loading is complete without any display in the text area, then you need to close it and run the debug once.

Then continue to click on Options->configure Target and select ADP Click OK after the dialog box pops up. After determining the loading interface will appear, this time needs to be closed.

Then click Debug again this time is the normal loading state. Appears to indicate a normal load.

After loading completes as below, if the load is unsuccessful, or other problems, mostly JTAG driver installation issues, uninstall the reinstallation. Note: When installing the JTAG driver,

Running Uarmjtag2.0.exe does not install the driver, just unzip the drive.

Then we click the Run button. After the normal state he will stop in the main function, which is the system automatically. Then we continue with the Run button to run the drawing experiment.

On the LCD screen we will be drawing a good figure.

The Vivi console responds as follows:

Please pause and exit the program before closing.

Second, the experimental experience

This experiment content a lot of, give our group to impress deeply, especially the occurrence of the fault in the experiment, our self-investigation finally make the experiment to carry on and successfully complete. For us is not small progress and improvement.

In addition, through hands-on practice, the use of modular approach to drive development and commissioning of the process has been further understanding, so that we benefit.

Iii. Questions and understanding

1. Understanding of the experimental process:

(1) When installing Giveio and JTAG-class software, it is not enough to simply double-click the. exe file, but also to install the hardware driver to actually install successfully and can run.

(2) Ads must be cracked before they can be used.

(3) Vivi Console If a long time without the command input will stop, back to the first connection when the selection page appears, if not in time to choose, will go directly to the Linux console, causing a lot of inconvenience.

2. Problems encountered during the experiment and solutions:

(1) Problem: Install ads when found that it is already on the computer, but did not crack, can not be used.

FIX: In Start | Program "To find ads, find the" License installation ... "option, such as:

Then follow the method given in the document to crack.

(2) Problem: HyperTerminal Open, connected successfully into the Vivi console, but for a long time do not enter the instruction to enter the Linux console; Turn off the hardware device reconnection fails, log off the computer user log on again did not make the connection successful.

Solution: Changed a hardware device did not pick up, after restarting the computer to connect again, also learned the experience, no longer prematurely open the Vivi console.

Experimental three reports 20135209 Pan Heng 20135204 Shi Zhiyu