Experimental report (experiment three)

Beijing Institute of Electronic Technology (BESTI)

Real Inspection report

Course: Cryptographic system Design Basic class: 1352 classes, 1353 classes

Name: Liu Hao, Wang Yuexu No.: 20135318, 20135232

Score: Instructor: Lou Jia Peng Experimental Date: 2015.11.24

Experiment level: Preview degree: Experiment time: 15:30-18:00

Instrument Group: Compulsory/Elective: Experiment Number: 3

Experiment Name: Experiment Three: transplantation of real-time system

Experimental purposes and requirements:    1. master uc/osii (uCLinux ) porting process                                         

2 . Mastering C, compilation of mixed programming

Experimental instrument:

Name	Model	Number
PC Machine	Lenovo	1
Embedded experimental Platform	Up-tech S2410	1

Experiment contents, steps and experience:

First, the contents of the experiment:

This experiment is based on ARM development platform transplant Uc/osii or uclinux. Master uc/osii (UCLinux ...) and Master C, the mixed programming of the Assembly.

Second, the experimental steps:

(i) Basic development environment

1. Connect the experimental box power, use serial line, line, network cable, connect the experiment box and the host

2. Install ads

Install file in 00-ads1.2 directory, crack method 00-ads1.2\crack Directory

3. Installing the Giveio Drive

installation files in the 01-giveio directory

(1) Copy the entire Giveio directory to the C:\WINDOWS, and copy the Giveio.sys file under the directory to c:/windows/system32/drivers.

(2) In the Control Panel, select Add Hardware > Next > select-yes i have connected this hardware > Next > Check-Add New Hardware Device > Next > Check Install I manually select hardware from List > Next > select-Show All devices > Select-Install from disk-browse, specify drive as C:\WINDOWS\GIVEIO\giveio.inf file, click OK, install driver

4. Installing the JTAG Driver

Install the files in the 02-uarmjtag2.0 directory, the steps are as follows:

(1) Add driver

UarmJtag2.0 after installation, please connect the up-netarm3000 a simple emulator (C Jtag) to a PC, and then add hardware, the steps are as follows (for example, Windows XP): Start a Control Panel add hardware one step at a time I've connected this hardware one step after one select the Add a new hardware device one step at a time select Install I manually choose the hardware from the list one step by one select one Show all devices one choice (process longer) one from disk installation One browse, specify drive to c \ Program Files\uarmjtag\driver\lptjtag file, click OK, then click Next to install the driver.

(2) Simulation debugging

Click "Initialize Configuration", in the popup dialog box, "Processor type", select the appropriate ARM7 or arms (the default is ARM7, click OK; in Axd, execute menu options I Configure target to set the Axd, choose ADP as Remote debugging, Click the Configure button to further set the specific parameters; Click the Select button to choose a remote connection for ARM Ethernet driver, click the Configure button to enter the simple parallel port emulator IP address, input 127.0.0.1 can be simulated debugging.

5. Configure HyperTerminal: Baud rate is 115200, data bit 8, no parity, stop bit 1, no data flow control.

6. Test that the basic installation is correct, refer to document "03-Test document. doc", test procedure under 04-test directory;

(1) First run the ADS1.2 integrated development environment, click the File->open option, select the project file we use the/ucos V6.0/EXP11 drawing in the CD API function as an example to select EXP11.MCP and click Open.

(2) Select the files that need to be compiled, click on 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.

(3) Click Make to compile the link, compile the result after compiling, show no error, 4 warnings and 15 other information.

(4) Be sure to open Uarmjtag Click Initialize Configuration selection ARM9 Click OK before the debugger runs. Minimize to the pallet and ensure our platform stops in the Vivi state.

(5) Click the Debug button to simulate debugging, popup debugging interface; When the status is not available, click Options->configure Target, Pop-up dialog, click Configure, change the main two places name: Select Arm Ethernet Driver,configuration: Configure as: 127.0.0.1, click OK, then select ADP to click OK.

If you have finished loading the text without any display, then you need to turn it off and run the debug once.

Then click Debug again this time is the normal loading state. After the load is complete, click the Run button, and then the normal state will stop at the main function, which is the system automatically.

Then continue clicking the Run button to run the drawing experiment. On the LCD screen we will be drawing a good figure. Please pause and exit the program before closing.

Third, the problems encountered and solutions

1. Problem One: The test uses make to compile the link, and the result shows 9 errors.

WORKAROUND: The result of the error is that after selecting EXP11.MCP, the Exp11_data folder will appear when you compile the link with make, so you need to delete the original folder first. However, we follow the instructions to ensure that the code is in English path, and delete the code folder in the Exp11_data folder and still prompt an error. After careful examination found that we deleted the folder is on the computer desktop, but the experiment opened in the USB stick. After we delete the Exp11_data folder in the code folder in the USB drive, the compilation succeeds.

2. Problem two: The simulation after debugging the load has been shown as error:

Workaround: The problem is that when installing the JTAG driver, running Uarmjtag2.0.exe does not have the driver installed, just unzip the driver. After we reinstall it after reinstalling, follow the detailed installation steps to guide the installation after this load is successful.

Iv. Experience of Experiment

This experiment uses the ADS1.2 integrated development environment to run and draw a waveform diagram with the hardware. During the steps to install the software and run the software there are some small problems, in fact, there is no real understanding of the experimental principles and carefully read the reference guide caused by. Our team through this experiment, in the hands of the practice of combining theory and hardware, knowledge has a deeper learning and understanding. and learn from mistakes and pay attention to them later.

Experimental report (experiment three)