advertisement
phyCORE-i.MX35 Getting More Involved
•
Select I2C Hardware Bus support.
•
Check IMX I2C interface.
•
Save your configuration and exit the configuration tool.
•
Type:
make ARCH=arm CROSS_COMPILE=arm-1136jfs-linuxgnueabi- uImage
The kernel sources will be compiled and the new kernel will be built. This will take a few minutes. The new kernel will be written to
arch/arm/boot/uImage.
If the process of building the kernel stops with an error, check the values of both ARCH and CROSS_COMPILE.
•
Close the terminal window.
In this section you learned how to configure and compile a new kernel.
Now you can add new features to your kernel, or remove features you do not need.
Writing the Kernel into the Target’s Flash
In this passage you will find a description on how to write the newly created kernel into the phyCORE-i.MX35’s flash memory. Before the kernel can be written into the flash, the target will have to download the kernel from a TFTP server. This will be done from the command line of the boot loader.
The kernel will be copied into target’s RAM.
Then you will have to erase the part of the flash where you want to copy the kernel image to. Finally the kernel is written from the RAM to the flash.
In the default configuration you will find four partitions on the target: The first partition contains the boot loader, the second is used to store the boot
© 2009 PHYTEC Messtechnik GmbH L-724e_2
43
phyCORE-i.MX35 Quick Start Instructions loader settings, the third partition stores the Linux kernel, and the fourth contains the root file system.
The four partitions have the following address ranges:
0xa0000000 - 0xa003ffff (U-Boot)
0xa0040000 - 0xa005ffff (U-Boot Environment)
0xa0060000 - 0xa025ffff (Linux Kernel)
0xa0260000 - 0xa1ffffff (Linux Root File System)
You should never erase the U-Boot partition. If this partition is erased, you won’t be able to start your target anymore.
Refer to the chapter “Installing Linux on the phyCORE-
i.MX35”
for detailed information on how to restore your U-
Boot partition in such a case.
•
First open a new terminal window if it is not opened yet.
•
Copy the new kernel image to the /tftpboot directory and exit:
cp ~/linux-*/arch/arm/boot/uImage /tftpboot; exit
•
Open Microcom and press the RESET button on the target.
You will see the output “Hit any key to stop autoboot.”
•
Press any key to stop autoboot.
44
© 2009 PHYTEC Messtechnik GmbH L-724e_2
phyCORE-i.MX35 Getting More Involved
You can download the kernel from the TFTP server to the target’s
RAM, erase the required flash area, and write the kernel from the
RAM into the flash with just one simple command: update_kernel.
•
Type the following command to check your U-Boot settings:
edit /env/config
You will see the configuration file which holds U-Boot’s environment variables.
© 2009 PHYTEC Messtechnik GmbH L-724e_2
45
phyCORE-i.MX35 Quick Start Instructions
46
•
Make sure that the following values are set in the configuration file: eth0.ipaddr=192.168.3.11 eth0.netmask=255.255.0.0 eth0.serverip=192.168.3.10
•
Type CTRL-D to save the settings to the file.
•
If you made any changes to the U-Boot environment, type save to write these changes to the U-Boot environment partition, and then press the target’s RESET button. The phyCORE-i.MX35 reboots with the new settings applied. Again, press any key to stop autoboot.
•
Type update_kernel nor uImage to download the kernel using TFTP and write it into the target’s flash. The copy process can take up to a minute.
•
Press the RESET button on the target to restart the phyCORE-i.MX35 with the new kernel. The target will boot the newly created kernel.
•
Close Microcom when the target has successfully finished with booting the kernel and mounting the root file system.
© 2009 PHYTEC Messtechnik GmbH L-724e_2
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 5 Introduction
- 5 Rapid Development Kit Documentation
- 5 Professional Support Packages available
- 6 Overview of this Quick Start Instruction
- 7 Conventions Used In This Quick Start Manual
- 8 System Requirements
- 8 Software Development Tool Chains
- 8 Eclipse
- 9 The GNU Cross Development Tool Chain
- 11 Getting Started
- 11 Requirements of the Host Platform
- 12 Configuring the Host Platform
- 12 Installing Software packages
- 18 Set Up Network Card Configuration
- 19 Disabling the Firewall
- 20 Set Up TFTP Server
- 22 Linux-i.MX35-Kit Setup
- 23 Starting the Setup
- 31 Advanced Configuration Information
- 32 Connecting the host with the target
- 36 Copying an Example to the Target
- 37 Copying a program to the target
- 38 Using Telnet to Execute a Program on The Target
- 39 Using SSH to Execute a Program on The Target
- 42 Advanced Information
- 42 Copying a Program to the Target With the Command Line
- 42 Executing a Program on the Target
- 42 Executing a Program Directly on the Target Using SSH
- 44 Getting More Involved
- 44 Configuring and Compiling the Kernel
- 47 Writing the Kernel into the Target’s Flash
- 51 Opening an Existing Project
- 52 Copying the HelloWorld Project
- 52 Starting Eclipse and Importing the Example Project
- 57 Creating a New Project
- 67 Changing the Demo Application
- 68 Executing the Program on the Target using Microcom
- 69 Starting a Program out of Eclipse on the Target
- 77 Debugging an Example Project
- 77 Starting the GDB server on the target
- 79 Configuring and Starting the Debugger in Eclipse
- 83 Setting a Breakpoint
- 84 Stepping and Watching Variable Contents
- 86 Changing Variable Values
- 88 Using the Memory Monitor
- 91 Further Information
- 92 Summary
- 93 Installing Linux on the phyCORE-i.MX
- 93 Installing the Boot Loader
- 98 Configuring Environmental Variables
- 102 Restoring the U-Boot Default Configuration
- 102 Writing the Kernel / Root File System into Flash