KR100624723B1 - Mobile communication terminal managing hardware version and its operating method - Google Patents

Abstract

The present invention relates to a mobile communication terminal having a hardware version control function and a method of operating the same, the first step of inserting a code for hardware version management in the bootload code, and the memory through the code inserted into the bootload code And a third step of setting a hardware version in a specific data area of the third step of connecting the mobile communication terminal to an external device and reading the bootload code to determine a hardware version. Even if a device is not provided, the program code for checking the hardware version can be inserted into the boot loader code without additional process and cost, or the hardware version can be checked using the device ID. The hardware version can be checked for protection and integrity. Hardware version control is facilitated through.

Mobile terminal, boot loader, hardware version, device

Description

Mobile communication terminal managing hardware version and its operating method

1 is a block diagram showing the configuration of a mobile communication terminal with a hardware version control function according to the present invention;

2 is a flowchart illustrating a hardware version checking method of a mobile communication terminal according to the present invention;

3 is a flowchart illustrating a hardware version setting method of a mobile communication terminal according to the present invention.

<Explanation of symbols on main parts of the drawings>

10: control unit 11: data processing unit

12: input and output control unit 20: memory

21: bootloader 22; Bootload code

23: execution code portion 24: data portion

30: communication module 40: I / O interface

The present invention relates to a mobile communication terminal having a hardware version control function and a method for operating the same, and in particular, a hardware version control function for checking a hardware version using a device ID (ID) or a bootload code inside the mobile communication terminal. The present invention relates to a mobile communication terminal provided and a method of operating the same.

In order to indicate a hardware version, a mobile communication terminal according to the related art indicates a hardware version according to each resistance value by using a resistor when designing the hardware of the mobile communication terminal, or GPIO (General Purpose Input / Output Pin, GPIO). Through reading the hardware version of the mobile communication terminal is configured to enable the hardware version check.

In addition, the mobile communication terminal uses a method of displaying a version by inserting a hardware version into the hidden memory.

However, there is a problem in that a method of indicating a hardware version by using a resistance of a mobile communication terminal according to the present invention has to be designed to indicate a hardware version in a hardware design when manufacturing the mobile communication terminal.

In addition, there is a problem in that the version can be checked through the GPIO of the mobile communication terminal and cannot be used when there is no room for the GPIO.

In addition, in the case of using the hidden memory, since the ROM copy of the hidden memory is not possible, a program must be written accordingly, which causes a problem of adding a process.

On the other hand, in the case of a mobile communication terminal that is not provided with any device to manage the hardware version as described above there is a problem that can not perform the software upgrade suitable for the hardware version can not check the hardware version when upgrading the software.

The present invention has been made to solve the above-mentioned problems of the prior art, even if a separate hardware version management device is provided, using the ID (ID) combination or bootload code of each device to check the hardware version of the mobile communication terminal And a mobile communication terminal equipped with a hardware version control function to enable management and a method of operating the same.

In order to solve the above problems, a mobile communication terminal having a hardware version control function according to the present invention includes a memory for storing a boot loader and a bootload code, a communication module or an input / output interface connected to an external device and transmitting and receiving data; And a controller configured to execute the boot loader from the memory to collect device information by a bootload code, and to transmit the device information and hardware version information to the external device through the communication module or an input / output interface. It is a 1st characteristic.

In addition, the operating method of a mobile communication terminal equipped with a hardware version control function according to the present invention comprises the first step of inserting the code for hardware version management in the bootload code, and the code of the memory through the code inserted into the bootload code And a second step of setting a hardware version in a specific data area, and a third step of connecting the mobile communication terminal with an external device to read the bootload code to check a hardware version.

In addition, the operating method of a mobile communication terminal equipped with a hardware version management function according to the present invention comprises the first step of loading and resident a program in the RAM of the memory, and each device ID (ID) used through the RAM resident program A second step of loading the data; and a third step of comparing the ID of the device with the hardware version stored in the bootload or the hardware version of the image to be downloaded; and whether the data is suitable for the actual hardware version according to the comparison result. A third feature is that comprises a fourth step of determining the.

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings. 1 is a block diagram showing the configuration of a mobile communication terminal equipped with a hardware version control function according to the present invention.

The mobile communication terminal according to the present invention includes a memory 20 storing a boot loader 21 and a bootload code 22, and a communication module 30 for transmitting and receiving data through a connection with an external device by wireless or wired. Or an input / output interface 40 and a control unit 10 for executing the boot loader 21 to manage hardware version information.

The memory 20 includes the boot loader 21 for loading an operating system (OS), a root file system, an application program, and the like stored in a RAM memory when the system is powered on. .

In this case, the boot loader 21 reads the root file system and an application program into a RAM memory so that the mobile communication terminal is driven to perform a specific operation.

In addition, the memory 20 includes a separate program for a software management service, and the memory 20 includes a bootload code 22.

The bootload code 22 is a part which is initially executed when power is supplied to the mobile terminal, performs hardware initialization of the mobile communication terminal, and copies the file to the execution code unit 23 if there is a downloaded file. To be run.

In this case, the executable code unit 23 is an area in which executable codes of all software modules used in the mobile terminal except for the bootload code 22 are stored, and the bootload code 22 and the The remaining flash memory area except for the executable code part 23 is stored / stored in the data part 24.

The controller 10 executes the boot loader 21 from the memory 20 to collect device information by the bootload code 22, and the device information and hardware version. And an input / output control unit 12 for transmitting information to the external device through the communication module 30 or the input / output interface 40.

When the hardware version is required by the external device through the input / output interface 40 or the communication module 30, the data processing unit 11 inserts the following program code into the bootload code 22 to separate it. The hardware version management of the mobile communication terminal is performed even if a device for hardware version management of the mobile communication terminal is not provided.

#pragma DATA_SECTION (__ hard_info, ".boot");

Const type_hard_info __ hard_info [N] =

{

{

CAMERA_VENDOR_ID,

CAMERA_MODEL_ID

},

{

MEMORY_VENDOR_ID,

MEMORY_MODEL_ID

},

:

:

};

typedef struct hard_info_entry

{

const char vendor [20];

const char model [20];

} type_hard_info;

extern const type_hard_info __hard_info [];

MEMORY

{

BOOT_FLASH: org = 0x00000000 len = 0x00010000

MCP_SRAM: org = 0x0C5D0000 len = 0x00030000

}

SECTIONS

{

    .intvecs: {}> BOOT_FLASH

    .boot: {}> BOOT_FLASH

    .text: {}> BOOT_FLASH

    .cinit: {}> BOOT_FLASH

    .const: {}> BOOT_FLASH

    .data: {}> MCP_SRAM

    .bss: {}> MCP_SRAM

    .sysmem: {}> MCP_SRAM

    .stack: {}> MCP_SRAM

}

In the program code, MEMORY and SECTION are linker scripts of an embedded system to control the memory layout of an output file and to map an input file.

The program code includes a variable for inserting a version of each hardware and a code for defining a structure thereof as described above, and is for inserting a hardware version into a specific data region using a compilation option.

In addition, the program code declares a variable in the .boot region described in SECTION, and at this time, .boot must be specified in the SECTION section of the linker script.

The .boot area of the program code is set in the area called boot flash (BOOT_FLASH) together with the .intvecs and since the .intvecs always starts at 0, the .boot is created after the .intvecs to know the size of the intvecs. It is possible to check the starting address of the .boot.

At this time, the start address indicates the location of the variable declared in the .boot, and when the address is read from the outside, data stored in the previously defined variable can be read, and when the hardware version is inserted into the variable, the same method as described above is performed. This enables hardware versioning.

That is, the data processor 11 inserts the program code into the bootload code 22 to include the program code in the boot code, thereby providing a mechanism of a linker script of an embedded system. By using the above, the hardware version is stored at a specific address as a pragma and managed.

Here, the data processing unit 11 executes the program code, reads the data stored in the variable, checks the hardware version, or collects the device information and combines the device information to check the hardware version. .

The input / output control unit 12 transmits the device information and the hardware version collected by the data processing unit 11 to the external device through the communication module 30 or the input / output interface 40 so that no hardware is required from the outside. Allows you to check the version.

The hardware version checking method using the boot load of the mobile communication terminal is as follows. 2 is a flowchart illustrating a hardware version checking method of the mobile communication terminal according to the present invention, and FIG. 3 is a flowchart illustrating a hardware version setting method of the mobile communication terminal according to the present invention.

As shown in FIG. 2, the program code is used as the bootload code to declare a variable in the boot region (S1), and the hardware version is inserted at a specific address of the bootload. (S2)

The bootload image can be copied into ROM (S3), and the hardware version can be protected according to the protection setting method described later, and the hardware version can be used as a hidden memory so that the hardware version can be checked and managed. . (S4)

Meanwhile, the hardware version checking method using the device ID of the mobile communication terminal is as follows.

The mobile communication terminal is configured to include a plurality of devices for performing each function, each device has a unique ID (ID) is set.

In this case, each device has a different ID setting method according to the manufacturer, so that the method of checking the ID of the device may be different according to each device specification. Specifies how to check).

Each device configured to be included in the mobile communication terminal has a device ID (ID) stored at a specific address. As described above, a device ID is read and a device ID is read through the data value. (ID) can be checked.

In addition, the device may check the device ID when each of the set specific commands is input.

For example, in the case of a memory of the mobile communication terminal, when a specific command is determined in order for the memory, a unique device ID can be checked accordingly.

In addition, in the case of the camera provided in the mobile communication terminal, it is possible to check the index, ID (ID) through the I2C (Inter-Integrated Circuit Bus). At this time, the I2C performs a small network role that connects a device and an electronic system by carrying information between a plurality of devices through two lines for data and clock.

Here, the hardware version of the mobile communication terminal can protect the stored hardware version and device information by using a protection algorithm provided by each memory manufacturer.

The hardware version and device ID (ID) protection method can preserve data by preventing data such as hardware version stored in a specific area by using a specific command according to each manufacturer.

A hardware version setting method of the mobile communication terminal will be described below with reference to FIG. 3.

The bootload provides a function for re-downloading without a specific device when the image to download in the flash memory of the mobile communication terminal does not exist or is not operated due to an error. At this time, the bootload is required to copy the bootload image to the ROM writer to the ROM during the manufacturing process or fusing to the equipment such as Joint Test Action Group (JRAG).

As illustrated in FIG. 3, when downloading the bootload image of the mobile communication terminal or attempting to perform another function, a program resides in RAM.

The RAM resident program controls a device according to each function through a program. At this time, the RAM resident program has a code for reading the ID of the device so that the device can read the device ID. (S12)

In this case, the hardware version may be checked through a combination of device IDs read by the RAM resident program.

The bootload image to be downloaded is downloaded using the RAM resident program, and the hardware version included in the bootload image is checked. (S13)

As described above, the device ID identified by the RAM resident program is compared with a hardware version stored in a bootload image. (S14)

In addition, the hardware version of the image to be downloaded is compared with the hardware ID of the device ID or the bootload image.

That is, when a hardware version is downloaded at a specific address of the image to be downloaded and does not match the actual hardware version, it is determined whether the download image and the actual hardware version do not match.

In addition, the bootload itself may be compared with the device ID (ID) actually read by the RAM resident program to determine whether it is properly set for the hardware version.

Accordingly, in addition to checking the hardware version, the hardware version of the device ID or the download image may be compared to verify the download integrity.

Through the integrity verification as described above, the suitability of the hardware version is verified, and when the integrity is verified, image download is performed. (S15, S16)

On the other hand, when reading the hardware version from the outside, the RAM resident program is placed in RAM as above, and the hardware version can be checked through the device ID (ID) read by the RAM resident program.

In addition, since the character data can be stored in a variable declared in the bootload, in the case of a device having difficulty in checking the device ID, the device version is stored together with the hardware version through combination with other device IDs. Management becomes possible.

As described above, the mobile communication terminal equipped with a hardware version control function according to the present invention and an operation method thereof have been described with reference to the illustrated drawings, but the present invention is not limited by the embodiments and drawings disclosed herein. It can be applied to the extent that the idea is protected.

Mobile communication terminal with a hardware version control function and the operation method according to the present invention configured as described above, even if a device for separate hardware version management is not provided without checking the hardware version in the boot loader code without additional process and cost It is possible to check the hardware version by inserting the program code for the device ID (ID) or use the hardware version management through the protection and integrity check on the hardware version is effective.

Claims (6)

A memory for storing a boot loader and bootload code; A communication module or an input / output interface connected to an external device to transmit and receive data; And a controller configured to execute the boot loader from the memory to collect device information by a bootload code, and to transmit the device information and hardware version information to the external device through the communication module or an input / output interface. Mobile communication terminal with a hardware version management function, characterized in that. Inserting code for hardware version management into the bootload code; A second step of setting a hardware version in a specific data area of a memory through code inserted into the bootload code; And a third step of identifying a hardware version by reading the bootload code by connecting the mobile communication terminal with an external device. The method of claim 2, The hardware version management method of the mobile communication terminal is a method of operating a mobile communication terminal equipped with a hardware version management function, characterized in that for loading the hardware version by checking the stored address or start address for the declared variable. The method of claim 2, In the hardware version management method of the mobile communication terminal, the hardware version is characterized by managing the hardware version through a combination with other device IDs by storing data on devices that are difficult to load IDs together in the declared variables. Method of operation of a mobile communication terminal equipped with a management function. The method according to claim 3 or 4, The hardware version management method of the mobile communication terminal is a method of operating a mobile communication terminal equipped with a hardware version control function, characterized in that the hardware version is protected using the protect command data can be used as a hidden memory. A first step of loading and resident a program into a RAM of a memory; Loading each device ID used through the RAM resident program; A third step of comparing an ID of the device with a hardware version stored in a bootload or a hardware version of an image to be downloaded; And a fourth step of determining whether or not the data is suitable for the actual hardware version according to the comparison result.

Images