KR100296035B1 - Method for setting and changing internet protocol address and ethernet address for embedded system - Google Patents

Abstract

end. The technical field to which the invention described in the claims belongs

It is a technique for setting the IP and Ethernet address of the embedded system.

I. The technical problem to be solved by the invention

The built-in system accommodates existing methods and provides an addressing method common to all devices.

All. Summary of Solution of the Invention

The present invention is a method for setting and changing the IP and Ethernet address of the embedded system, and when the power of the built-in system is turned on by checking whether data according to the IP or Ethernet address is received from the operator according to the IP or Ethernet address A shell mode performing step of storing data in a non-volatile memory when data is received, A get IP performing step of reading an IP stored in the non-volatile memory after the shell mode is performed and applying it to a variable, and the reading after performing the get IP. In the step of checking whether the on-variable has a value and if there is no value applied to the variable, the server performs an RLP request for receiving IP data from the server and an application for creating a communication channel between the target board and the host after performing the RLP. This is an Xtrace execution step that provides a debugging channel for execution. It is characterized by loosening.

la. Important uses of the invention

It is used in all embedded systems that use VTRX.

Description

How to set and change IP and Ethernet address of the built-in system {METHOD FOR SETTING AND CHANGING INTERNET PROTOCOL ADDRESS AND ETHERNET ADDRESS FOR EMBEDDED SYSTEM}

The present invention relates to a method of setting and changing a unique IP address and an ethernet address in an embedded system, in particular, OS of VTRX. To configure and change the IP address and the Ethernet address in an embedded system that uses.

In general, each board of the embedded system sends and receives data in a specific network, and each board needs to be assigned an address. These addresses are divided into IP addresses and Ethernet addresses. When using Internet communication, the IP address must be stored in each board's memory, and when using Ethernet communication, the Ethernet address must be stored. Therefore, when transmitting and receiving data between boards, data is transmitted to the address of the corresponding board according to the data transmission and reception method. However, since these boards are used for each board embedded in each system, they have a unique number. Therefore, in the embedded system using VTRX as a real time operating system, the following three methods are used to allocate IP addresses differently for each board.

The first method is to hard code the board to be embedded in the system. The second method is to set the value in the IP address variable, which is an environment variable of the VTRX, and the third method is Reverse. Address Resolution Protocol (hereinafter referred to as RARP) There is a method of assigning an IP address using a server.

First, we describe how to hardcode a board that will be mounted on a particular system. Hardcoding defines the following environment variables in the configuration file that generates the source code.

boot.env.variable: ip_addr

Each environment variable must also have a name and a value. This is shown as an example.

boot.env.ip_addr.envname: IP_ADDR

boot.env.ip_addr.value: 165.213.227.212

Then, after Xconfig is executed, the value of IP_ADDR is defined as 165.213.227.212, and the boot program sets this value in a global variable called boot_bridge_ip_addr. Assuming that the configuration file containing these contents is the bootconfig.def file, execute Xconfig as follows.

xconfig bootconf.def m147def microtes.def

This creates and compiles a bootconf.c file having the following data structure and is stored in the boot up code as shown in Table 1 below.

char * boot_environ_rom {} = {'IP_ADDR = 165.213.227.212',… };

However, this method of hardcoding the device has a problem that it is difficult to apply when the product is mass-produced because the boot up memory must be different in order to set different IP addresses for each board. In addition, there was a problem that can not be used when the network structure or domain (Domain) is changed.

Next, the IP_ADDR environment variable can be set using the setenv command on the boot shell when the device is booted up. As such, a method of setting the IP address to 165.213.227.212 is shown in Table 2 below.

boot> setnv IP ADDR 165.213.227.212

Then, the IP_ADDR value is set in boot_bgidge_ip_addr and stored in RAM, which is volatile memory. Therefore, with the second method, every time the device's board is powered off, the data stored in volatile memory is erased each time. Therefore, when the power is turned on again, the operator had to set the IP address every time.

Finally, we explain how to use RARP. In case of using RARP, RARP server should be provided. The board then broadcasts its Ethernet address via the LAN port. In general, since the ethernet address of the board is hardcoded, the ethernet address is set by using a dip (DIP) switch in an embedded system. Therefore, it is assumed that the Ethernet address has already been set. When the RARP server responds, it sends the IP address to the board where the boot program is running. Accordingly, the boot program of the board sets the IP address. The above method has a problem in that an IP address can be assigned to a corresponding board only when a RARP server exists on a network.

Accordingly, an object of the present invention is to provide a method for easily setting and changing an IP address and an Ethernet address on a board of an embedded system.

Another object of the present invention, in setting the IP address and the Ethernet address on the board of the embedded system, accommodates all the conventional methods, facilitates the user and the interface when setting and changing the IP address, power on / off It provides a method of setting and connecting an IP address and an Ethernet address that are not affected.

1 is a block diagram of a transmission system implemented by an embedded system scheme;

Figure 2 is a block diagram of a main part according to the present invention in the board of the transmission system,

3 is a control flowchart performed on a board of an embedded system according to a preferred embodiment of the present invention;

4 is a control flowchart of a shell subroutine in accordance with a preferred embodiment of the present invention;

5 is a control flowchart of a get IP subroutine according to a preferred embodiment of the present invention;

6 is a control flowchart of an RLP subroutine in accordance with a preferred embodiment of the present invention.

The present invention for achieving the above object is a method for setting and changing the IP and Ethernet address of the embedded system, by checking whether the data according to the IP or Ethernet address is received from the operator when the power is turned on the embedded system A shell mode performing step of storing data in accordance with an IP or Ethernet address in a nonvolatile memory, and a step of executing a get IP after reading the IP stored in the nonvolatile memory and applying the variable to a variable after performing the shell mode; After performing the get IP, checking whether the read-out variable has a value, and if there is no value applied to the variable, performing RLP requesting and receiving IP data from a server, and after performing RLP, between the target board and the host. Provide a debugging channel to perform an application that creates a communication channel. Is characterized by consisting of the step of performing the trace.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a transmission system implemented in an embedded system scheme. Hereinafter, a block configuration of a transmission system to which the present invention is applied will be described with reference to FIG. 1.

The first receiver 10 receives data through a line connected to the transmission system on the left side and outputs the data to the branch combiner 30, and the first transmitter 20 transmits data received from the branch combiner 30 on the left side. It transmits to the transmission system on the left through the line connected to the transmission system. The controller 60 controls the overall operation of the transmission system, and in particular, performs the control with reference to each IP of the corresponding equipment. The data processor 70 detects data received from a transmission system connected to the left or right side, monitors the line, and processes data according to network management. The branch combiner 30 separates data to be transmitted to the sub system and data to be transmitted to another transmission system under the control of the controller 60 and outputs the data to the first transmitter 20 or the second transmitter 40. Or output data to the subsystem. The second transmitter 40 is connected to the right transmission system through a line connected to the right side, and outputs data received from the branch coupling unit 30 to the right transmission system. The second receiver 50 converts the data received from the line connected to the transmission system on the right into an electrical signal and outputs the electrical signal to the branch coupling unit 30.

Figure 2 is a block diagram of the main part of the board of the transmission system according to the present invention. Hereinafter, a block configuration and its operation required for setting an IP address will be described in detail with reference to FIG. 2.

The operator connects to a specific board of the transmission system using the operator computer. At this time, the connection between the operator computer and a specific board of the transmission system is connected by using a local area network (LAN), and the board connected to the operator computer has a LAN connection 12 for connecting via a LAN. In the following description, an example in which the first receiver 10 of FIG. 1 is connected to an operator computer will be described. The first receiver 10 includes a LAN connection 12 for transmitting and receiving data to and from an operator computer, and includes a processor 11 for controlling the operation of the first receiver 10. In addition, a memory unit 13 for storing data necessary for the operation of the processor 11, temporarily storing data generated during operation, and NVRAM 14 for storing an IP address according to the present invention. The processor 11 is connected to another device of the first receiver 10.

3 is a control flowchart performed on a board of an embedded system according to a preferred embodiment of the present invention. Hereinafter, a control process performed on a board of an embedded system according to the present invention will be described in detail with reference to FIGS. 1 to 3.

When each board of the transmission system is powered on, the board proceeds to step 100 to perform a shell mode. The operation of the subroutine according to the shell mode will be described with reference to FIG. 4. 4 is a control flowchart of a shell subroutine according to a preferred embodiment of the present invention. Hereinafter, the operation of the subroutine in shell mode will be described with reference to FIG. 4.

In the shell mode, the processor 11 sets the internal timer to a predetermined time. Then, it is checked whether data is received through the LAN connection unit 12. If the test result data is received, the process proceeds to step 116. If the data is not received, the process proceeds to step 114 to check whether a timeout signal is received. When the timeout signal is received from the internal timer, the processor 11 ends the shell mode and proceeds to a get IP step (200) of FIG. 3.

In this case, when the operator inputs an IP address, for example, '165.213.227.212' in the operator computer by inputting a Set IP command, the input IP address is transferred to the processor 11 through the LAN connection unit 12. Is entered. The processor then proceeds to step 116 to examine the received data. In operation 118, the processor 11 checks whether the set IP data is set. When the set IP data is received, the processor 11 proceeds to step 120 to store data about the IP in the NVRAM 14 and proceeds to step 128.

In contrast, if the received data is not set IP data, the processor 11 proceeds to step 122 and checks whether set-eder data has been received. If the set result data is received, the process proceeds to step 124, and if no set ether data is received, the process proceeds to step 126. Here, the set-ether data refers to a case in which the operator inputs data instructing the operator to use the data through the energynet by using the operator's computer. For example, the operator setsset '0: 0: f0: ff: 1: This is the case when 2 'is input. If the test result set data is received, the process proceeds to step 124 where the data is stored in the NVRAM 14 and the shell mode is terminated. However, if it is not the data according to the test result, the process proceeds to step 126 to check whether the data according to the termination is received. When the data according to the end of the test result is received, the shell mode is terminated and the process proceeds to Get IP of step 200 of FIG. 3. However, if it is not the end data, the data input in step 112 is recognized as incorrectly input data and the process proceeds to step 128. The processor 11 checks whether data is received in step 128. When the test result data is received, the process proceeds to step 115, and when no data is received, the process proceeds to step 114. Through such a process, the IP data is received, the Ether data is received, or the time-out is used to use the data previously stored in the NVRAM 14.

After the execution of the shell mode through the process as shown in FIG. 4, the processor 11 proceeds to the get IP step of step 200. Next, the steps of the Get IP will be described with reference to FIG. 5. 5 is a control flowchart of a get IP subroutine according to a preferred embodiment of the present invention. Hereinafter, the subroutine of Get IP will be described in detail with reference to FIGS. 2 and 5.

The processor 11 proceeds to step 210, and reads data stored in the shell mode or previously stored IP or Ether data from the NVRAM 14. The processor 11 sets the read data in a variable. That is, the IP data is read and used when the IP data exists, and when the IP data is not stored in the NVRAM 14 and only the Ether data is stored, the Ether data is read and used. Since the NVRAM 14 is a non-volatile memory, data is not deleted when the power is turned on or off, so that the data once stored is not erased until the operator deletes it again. Therefore, the user can input and use IP or Ether data with one input. After setting the data read to the variable through the above process, the get IP subroutine is terminated, and the RRP of step 300 is performed.

The ALPH subroutine will now be described with reference to FIG. 6. 6 is a control flowchart of an AL subroutine according to a preferred embodiment of the present invention.

The processor 11 checks whether the IP set in the variable exists in step 310. In this case, there is no IP, that is, there is no IP previously stored in the NVRAM 14 or there is no IP previously input from an operator, and thus the IP cannot be set to a variable. In this case, the processor 11 proceeds to step 312, otherwise the processor terminates the RLP subroutine.

When the processor 11 proceeds to step 312, the processor 11 generates and transmits a signal for requesting IP data to a server of the transmission system. In step 314, it is checked whether IP data is received from the server. If the IP data is received, the process proceeds to step 316 to store the IP data in the NVRAM 14, and then proceeds to step 318 to apply to the variable. And the RLP subroutine ends. As such, when the RLP subroutine ends, the processor proceeds back to the xtrace mode in step 400 of FIG. 3. Here, the X-trace is a step of making a communication channel with a target board and a development host in SPECTRA, which is a development environment of the VRTX RTOS, and provides a debugging channel so that an application can be performed. That is, through this process, IP and Ethernet addresses can be freely set or changed according to the environment.

As described above, rather than fixing one specific IP or Ethernet address, there is an advantage in that the system can be freely set and changed according to the environment in which the system is installed or the input of the operator. It also has the advantage of not having to enter an IP address every time.

Claims (3)

In the method of setting and changing the IP and Ethernet address of the built-in system, A shell mode performing step of checking whether data according to an IP or Ethernet address is received from an operator when the embedded system is powered on and storing the data according to the IP or Ethernet address in a nonvolatile memory; Performing a get IP after reading the IP stored in the nonvolatile memory after the shell mode is executed; A step of performing an ALP requesting and receiving IP data from a server if there is no value applied to the variable by checking whether the read-out variable has a value after performing the get IP; Method of setting and changing the IP and Ethernet address of the embedded system, characterized in that the step of performing the X trace to provide a debugging channel to perform the application to make a communication channel between the target board and the host after performing the RLP. The method of claim 1, wherein the shell mode execution step, Setting a timer according to a shell mode execution time to a predetermined time; Checking whether the set IP or set-eder data is received before timeout of the timer; If the set IP or set-adder data is received as a result of the test, storing the data in the nonvolatile memory and ending the shell mode; And exiting the shell mode when a timeout signal is received before the set IP or set ether data is received. According to claim 1 or 2, wherein the step of performing ALLP, Checking whether there is no IP and Ether data stored in the nonvolatile memory; Terminating the RLP execution routine when there are IP and Ether data stored in the nonvolatile memory; Requesting IP data to a server connected to the system if there is no IP and Ether data as a result of the inspection; Receiving the IP data from the server and storing the IP data in the nonvolatile memory; And applying the data stored in the non-volatile memory to the variable IP and Ethernet address of the embedded system.