WO2015123932A1 - 一种移动终端的触摸屏固件修复方法和装置 - Google Patents

一种移动终端的触摸屏固件修复方法和装置 Download PDF

Info

Publication number
WO2015123932A1
WO2015123932A1 PCT/CN2014/078595 CN2014078595W WO2015123932A1 WO 2015123932 A1 WO2015123932 A1 WO 2015123932A1 CN 2014078595 W CN2014078595 W CN 2014078595W WO 2015123932 A1 WO2015123932 A1 WO 2015123932A1
Authority
WO
WIPO (PCT)
Prior art keywords
touch screen
firmware
driver
identification
mobile terminal
Prior art date
Application number
PCT/CN2014/078595
Other languages
English (en)
French (fr)
Inventor
刘龙芳
王文利
杨广明
Original Assignee
惠州Tcl移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 惠州Tcl移动通信有限公司 filed Critical 惠州Tcl移动通信有限公司
Publication of WO2015123932A1 publication Critical patent/WO2015123932A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1433Saving, restoring, recovering or retrying at system level during software upgrading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/654Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories

Definitions

  • the present invention relates to the field of mobile terminals, and in particular, to a touch screen firmware repair method and apparatus for a mobile terminal.
  • the input device basically uses a capacitive touch screen (CTP, Capacitive Touch). Panel), because the sensing area of the capacitive screen sensor is large and electromagnetic induction mode, the capacitive screen is extremely susceptible to external electromagnetic interference; and the low-cost touch screen has insufficient structural rigidity, and the touch screen itself is easily bent and deformed when touched; The positioning of the touch screen is not accurate. Therefore, in order to make the touch screen positioning effect better, it is necessary to frequently modify the touch software parameters of the capacitive touch screen. Each time the adjusted touch software is packaged to form a separate software package (called firmware, abbreviated as FW, Firmware).
  • firmware abbreviated as FW, Firmware
  • the firmware will be programmed to the touch screen of the capacitive screen when the boot driver is loaded (integrated Circuit, integrated circuit), if there is an accident in this process that causes the programming to fail, it will cause damage to the touch software inside the touch screen, making the device unable to respond to the user's operation, resulting in a large number of equipment repair and return, bringing the user inconvenient. And now after the user buys the mobile device, after the developer releases the new system version, many users will choose to update the system to get a better experience. When the system is first booted after updating the system, the amount of firmware update data of the touch screen is large.
  • the communication bandwidth is small, causing a long boot time, which may cause some users to unplug the battery and restart the computer, thereby causing the touch screen firmware update to be interrupted unexpectedly, and the function of the touch panel of the touch screen is damaged, and the touch screen may be invalid after booting.
  • the technical problem to be solved by the present invention is to provide a touch screen firmware repairing method and apparatus for a mobile terminal, which aims to solve the problem that the existing mobile terminal touch screen firmware update fails and the touch screen fails.
  • a touch screen firmware repair method for a mobile terminal comprising the following steps:
  • a touch screen firmware repair method for a mobile terminal comprising the following steps:
  • the step of restarting the mobile terminal before the step of restarting the touch screen firmware of the mobile terminal further includes:
  • An identification data storage area for storing the identification ID of the touch screen is disposed in the touch integrated circuit IC of the touch screen.
  • the step of reading the identification ID of the touch screen that is pre-stored, and finding the driver that matches the touch screen from the driver structure list according to the identification ID includes:
  • the step of writing firmware data corresponding to the identification ID in the touch screen to the touch screen includes:
  • the step of reading the identification ID of the touch screen stored in advance, and finding the driver matching the touch screen from the driver structure list according to the identification ID further includes:
  • An error code is returned when a driver matching the touch screen is not found from the list of driver structures.
  • the step of writing firmware data corresponding to the identification ID in the touch screen to the touch screen includes:
  • the parameter corresponding to the ID is taken out from the parameter data packet that is driven by the driver, and the parameter update program that is driven by the driver itself is entered, forcibly corresponding to The valid parameters of the current ID are written to the touch IC.
  • a touch screen firmware repairing device for a mobile terminal comprising:
  • a touch screen determining module configured to restart the mobile terminal when the touch screen firmware update of the mobile terminal fails
  • a driving matching module configured to read a pre-stored identification ID of the touch screen, and find a driver matching the touch screen from the driver structure list according to the identification ID;
  • a firmware writing module configured to write firmware data corresponding to the identification ID in the driver into the touch screen
  • a loading module for loading the driver to complete touch screen firmware repair.
  • the touch screen firmware repairing device of the mobile terminal further comprising:
  • a preset module for setting an identification data storage area for storing the identification ID of the touch screen in the touch IC of the touch screen.
  • the touch screen firmware repairing apparatus of the mobile terminal wherein the driving matching module comprises:
  • a reading unit configured to read the identification ID from the identification data storage area of the touch screen
  • the driving determining unit is configured to sequentially determine, according to the identification ID of the touch screen, whether the plurality of drivers in the driver structure list match the touch screen, and find a driver that matches the touch screen.
  • the touch screen firmware repairing apparatus of the mobile terminal wherein the firmware writing module comprises:
  • a firmware reading unit configured to read corresponding firmware data in the driver according to the identification ID
  • firmware writing unit for writing 1 KB of firmware data to the touch screen
  • firmware determining unit configured to determine whether the firmware data is written
  • a firmware verification unit for verifying whether the firmware data is complete.
  • the touch screen firmware repairing apparatus of the mobile terminal wherein the driving matching module is further configured to return an error code when a driver matching the touch screen is not found in the driver structure list.
  • the present invention also provides a mobile terminal including the touch screen firmware repairing apparatus of the mobile terminal described above.
  • the touch screen firmware repairing method and device for a mobile terminal effectively solve the problem that the existing mobile terminal touch screen firmware update fails to cause the touch screen to fail.
  • the restart is performed.
  • a mobile terminal reading an identification ID of the touch screen stored in advance, finding a driver matching the touch screen from the driver structure list according to the identification ID; and firmware data corresponding to the identification ID in the driver Writing into the touch screen; loading the driver to complete the touch screen firmware repair; enabling the touch screen to be automatically repaired when the mobile terminal is restarted, and restarting the mobile terminal as soon as the touch screen firmware is damaged, the repair mode in the driver software is started.
  • FIG. 1 is a flowchart of a preferred embodiment of a method for repairing a touch screen firmware of a mobile terminal according to the present invention
  • FIG. 2 is a structural block diagram of a preferred embodiment of a touch screen firmware repairing apparatus for a mobile terminal according to the present invention.
  • the present invention provides a method and a device for repairing a touch screen firmware of a mobile terminal.
  • the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
  • FIG. 1 is a flowchart of a preferred embodiment of a method for repairing a touch screen firmware of a mobile terminal according to the present invention. As shown in the figure, the method includes the following steps:
  • Step S100 When the touch screen firmware update of the mobile terminal fails, restarting the mobile terminal;
  • Step S200 reading an identification ID of the touch screen stored in advance, and finding a driver matching the touch screen from the driver structure list according to the identification ID;
  • Step S300 writing firmware data corresponding to the identification ID in the driver into the touch screen
  • Step S400 loading the driver to complete touch screen firmware repair.
  • step S100 when the touch screen firmware update of the mobile terminal fails, the mobile terminal is restarted.
  • MTK has established a touch screen architecture layer to manage all the drivers, in order to traverse all the touch screen drivers to achieve more Touch screen compatible for the purpose.
  • MTK is the abbreviation of Taiwan Unicom's multimedia chip provider, the full name is MediaTek.
  • the control flow of the driver architecture layer of the mobile terminal based on the MTK platform is: adding a touch screen (TP) driver to the driver structure list, and then determining whether the current node of the driver list is empty, and if it is empty, the process ends, that is, the matching fails. If it is not empty, the current driver in the list is taken, and the driver list is traversed by the pointer.
  • TP touch screen
  • the current driver matches the current TP. If yes, the current driver is loaded. If not, it continues to determine whether the current node of the driver list is empty, that is, the drivers in the driver structure list are sequentially taken out to Touch screen (TP) matching. In other words, the device driver of the touch screen is automatically added to the driver list only when it is running. If the system does not load the TP driver normally, the list will be empty, and the list pointer will be displayed after the driver match. Move, after moving to the end without data, it will be empty, so you need to check whether the currently pointed list node is empty. When the driver matches, it will run the driver obtained from the node pointed to by the current pointer of the driver list. Use this driver to adapt the device. If the adaptation fails, exit the driver and return to the architecture layer. Obtain the next driver from the next node in the driver list for adaptation.
  • TP Touch screen
  • the original parameters in the touch screen are all cleared first, and then the new parameters are written from the FW to the main control IC of the touch screen, and there are ten processes in updating the data. A few seconds, and the boot interface does not change at this time. Since there is no change in the boot interface for ten seconds, the user will think that the boot fails, and forcefully pull out the battery and power it on again. At this time, since the old parameters have been deleted, the new parameters are not written, causing the touch control panel of the touch screen to fail, and the touch screen is invalid, causing the user to return or return the product.
  • FW new firmware
  • each touch screen driver is notified to enter the repair mode by another flag, and the drive list is re-traversed from the beginning, and each touch screen driver performs parameter update of the touch screen if the matching is successful when matching.
  • step S200 the identification ID of the touch screen stored in advance is read, and the driver matching the touch screen is found from the driver structure list based on the identification ID.
  • the identification data storage area is used for storing the identification ID of the supplier's touch screen, and the data is only written together with the initial parameters when the touch screen is shipped, and is not modified afterwards.
  • the repair mode is entered, and the driver list is re-traversed from the beginning. If there is no match in the repair mode, the connection line of the touch screen is not connected and needs to be reconnected. . Whenever the firmware update of the touch screen fails due to an accident, the repair mode will enter the repair mode in the driver architecture layer to repair the touch screen. If the touch screen is normal, the match will find the current match when traversing the drive list for the first time. The driver of the touch screen, and then directly exit the loading process of the driver, does not traverse the second pass, preventing other time from being consumed during normal startup, affecting the boot speed.
  • the startup mode and communication mode of the debug mode of the touch screen matched with the driver are added, so that the touch screen feeds back the information stored in the dedicated identification data storage area to the driver in the debug mode, through this dedicated
  • the identification data stored in the identification data storage area and other information can determine whether the current driver matches the current touch screen. If it matches, it enters the firmware update phase. If it does not match, it returns to the architecture layer and reads the next driver for adaptation. Until the match is successful.
  • step S300 firmware data corresponding to the identification ID in the driver is written in the touch screen. Specifically, if the driver that matches the touch screen is found according to the identification ID, the parameter corresponding to the ID is taken out from the parameter data packet that is driven by the driver, and the parameter update program that is driven by the driver is entered. The valid parameters corresponding to the current ID are forcibly written into the touch IC, and after confirming that the writing is completed, the process returns to the normal flow, and the current drive is added as a running driver of the touch screen to the system of the mobile terminal.
  • the driver is loaded to complete the touch screen firmware repair.
  • the mobile terminal touch screen firmware is repaired by the above steps, and the touch screen can be used normally by simply loading the driver.
  • the method further includes:
  • step S200 specifically includes:
  • S220 Determine, according to the identification ID of the touch screen, whether the plurality of drivers in the driver structure list match the touch screen, and find a driver that matches the touch screen.
  • step S200 further includes:
  • step S300 specifically includes:
  • step S340 it is determined whether the firmware data is written, if it is finished, then proceeds to step S350; if not, returns to step S330;
  • step S350 Verify that the firmware data is complete. If not, return to step S320; if yes, perform step S400.
  • step S300 the corresponding firmware data in the driver is first read according to the identification ID, and then the original firmware data in the touch screen, that is, the FLASH described above is cleared. Then, the firmware data corresponding to the identification ID is sequentially written, and 1 KB is written each time until the firmware data is written. Then, it is verified whether the written firmware data is complete. If it is complete, the process proceeds to step S400, and the driver is loaded to complete the touch screen firmware repair; if not, the original firmware of the touch screen is cleared and rewritten.
  • the method for repairing the touch screen firmware of the mobile terminal obtaineds the identification ID of the touch screen pre-stored by the repair mode after confirming that the touch screen has been damaged, and then takes out the parameter corresponding to the ID from the parameter data package of the drive.
  • the repair mode in the driver software will be activated, forcibly entering the firmware update program, and rewriting the complete parameters contained in the driver to the touch IC, thereby repairing the Invalid touch screen eliminates the repair and return caused by firmware update, and improves the quality of the product; it is realized by software, which is simple to implement and low in cost, and brings great convenience to users.
  • the touch screen firmware repairing apparatus of the mobile terminal is further provided.
  • the present invention further provides a touch screen firmware repairing apparatus of the mobile terminal. As shown in FIG. 2, the apparatus includes:
  • the touch screen judging module 10 is configured to restart the mobile terminal when the touch screen firmware update of the mobile terminal fails; specifically, as described in step S100;
  • the driving matching module 20 is configured to read a pre-stored identification ID of the touch screen, and find a driver matching the touch screen from the driver structure list according to the identification ID; specifically, as described in step S200;
  • a firmware writing module 30 configured to write firmware data corresponding to the identification ID in the driver into the touch screen; specifically, as described in step S300;
  • the loading module 40 is configured to load the driver to complete the touch screen firmware repair; specifically, as described in step S400.
  • the touch screen firmware repairing apparatus of the mobile terminal further includes:
  • a preset module for setting an identification data storage area for storing the identification ID of the touch screen in the touch IC of the touch screen.
  • the driving matching module 20 includes:
  • a reading unit configured to read the identification ID from the identification data storage area of the touch screen
  • the driving determining unit is configured to sequentially determine, according to the identification ID of the touch screen, whether the plurality of drivers in the driver structure list match the touch screen, and find a driver that matches the touch screen.
  • firmware writing module 30 includes:
  • a firmware reading unit configured to read corresponding firmware data in the driver according to the identification ID
  • firmware writing unit for writing 1 KB of firmware data to the touch screen
  • firmware determining unit configured to determine whether the firmware data is written
  • a firmware verification unit for verifying whether the firmware data is complete.
  • the firmware reading unit reads the corresponding firmware data in the driver according to the identification ID, and then clears the original firmware data in the touch screen, that is, the FLASH described above, by the clearing unit.
  • the firmware data corresponding to the identification ID is written by the firmware writing unit, and each time 1 KB is written, the firmware determining unit determines whether the firmware data is written until the firmware data is written. Then, the firmware verification unit verifies whether the written firmware data is complete. If it is complete, the driver is loaded to complete the touch screen firmware repair; if not, the original firmware of the touch screen is cleared and rewritten.
  • the touch screen firmware repairing apparatus of the mobile terminal wherein the drive matching module 20 is further configured to return an error code when a driver matching the touch screen is not found in the driver structure list.
  • the mobile terminal according to the present invention is a mobile terminal having a touch screen such as a mobile phone or a tablet computer.
  • the touch screen firmware repairing apparatus of the mobile terminal provided by the embodiment of the present invention is formed in a terminal, such as a mobile terminal or a tablet computer or the like, and the touch screen firmware repairing apparatus of the mobile terminal is the same as the above embodiment.
  • the touch screen firmware repairing method of the mobile terminal belongs to the same concept, and any method provided in the embodiment of the touch screen firmware repairing method of the mobile terminal can be run on the touch screen firmware repairing device of the mobile terminal, and the specific implementation process thereof is described in detail.
  • the embodiment of the method for repairing the touch screen firmware of the mobile terminal is not described here.
  • the touch screen firmware repairing method of the mobile terminal of the embodiment of the present invention a person skilled in the art may understand all or part of the flow of the touch screen firmware repairing method of the mobile terminal that implements the embodiment of the present invention, which may be through a computer.
  • the program is controlled to control related hardware, and the computer program can be stored in a computer readable storage medium, such as in a memory of the terminal, and executed by at least one processor in the terminal, during execution.
  • the flow of an embodiment of the methods as described above is included.
  • the storage medium may be a magnetic disk, an optical disk, a read only memory (ROM), or a random access memory (RAM).
  • each functional module may be integrated into one processing chip, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated module if implemented in the form of a software functional module and sold or used as a standalone product, may also be stored in a computer readable storage medium, such as a read only memory, a magnetic disk or an optical disk, etc. .
  • the present invention provides a touch screen firmware repair method and apparatus for a mobile terminal, by restarting the mobile terminal when the touch screen firmware update of the mobile terminal fails; reading the pre-stored touch screen identification ID, according to the The identification ID finds a driver matching the touch screen from the driver structure list; writes firmware data corresponding to the identification ID in the driver to the touch screen; loads the driver to complete Touch screen firmware repair; enables the touch screen to automatically repair the firmware when restarting the mobile terminal.
  • the repair mode in the driver software is started, the firmware update program is forced to be entered, and the complete program included in the driver is included.
  • the parameters are rewritten into the touch IC, thereby repairing the touch screen that has been invalidated, eliminating the repair and return caused by the firmware update, improving the quality of the product, and bringing great convenience to the user, which is realized by software, and is simple to implement and cost. Lower.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Telephone Function (AREA)

Abstract

本发明公开了移动终端的触摸屏固件修复方法,当触摸屏固件更新失败时,重启移动终端;读取触摸屏的识别ID,根据识别ID从驱动程序结构列表中找出与触摸屏匹配的驱动程序;将驱动程序中与识别ID对应的固件数据写入触摸屏中;加载驱动程序,以完成触摸屏固件修复;本发明消除了固件更新导致的返修和退货,给用户带来了方便。

Description

一种移动终端的触摸屏固件修复方法和装置 技术领域
本发明涉及移动终端领域,尤其涉及的是一种移动终端的触摸屏固件修复方法和装置。
背景技术
现有移动终端,以手机为例,其输入设备基本上使用了电容触摸屏(CTP,Capacitive Touch Panel),由于电容屏这种传感器的感应区域很大且是电磁感应方式,使得电容屏极易受到外部电磁干扰;并且低成本的触摸屏的结构刚性不够,触摸时容易造成触摸屏本身弯曲形变;使得触摸屏的定位不准确。因此,为了让触摸屏定位效果更好,就需要频繁的给电容触摸屏的触控软件参数进行修改,每一次调校好的触控软件都会打包形成一个独立的软件包(称之为固件,简写为FW,Firmware)。所述固件会在开机驱动加载时烧写到电容屏的触控IC(integrated circuit,集成电路)中,如果在这个过程出现意外导致烧写失败,就会造成触摸屏内部触控软件的损坏,使得设备无法响应用户的操作,造成大量的设备返修和退货,给用户带来了不便。并且现在的用户买到移动设备之后,在开发商放出了新的系统版本之后,很多用户会选择更新系统以获得更好的体验,在更新系统之后初次开机时,由于触摸屏的固件更新数据量大,通信带宽小,引起开机时间长,会导致部分用户拔掉电池重新开机,从而造成触摸屏固件更新意外中断,损坏触摸屏的触控IC的功能,也会导致开机后触摸屏无效。
因此,现有技术还有待于改进和发展。
技术问题
本发明要解决的技术问题在于,提供一种移动终端的触摸屏固件修复方法和装置,旨在解决现有的移动终端触摸屏固件更新失败导致触摸屏失效的问题。
技术解决方案
一种移动终端的触摸屏固件修复方法,其中所述方法包括以下步骤:
在触摸屏的触控集成电路IC中设置一用于存放触摸屏的识别ID的识别数据存储区;
当移动终端的触摸屏固件更新失败时,重启所述移动终端;
读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;当从所述驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码;
将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
加载所述驱动程序,以完成触摸屏固件修复。
一种移动终端的触摸屏固件修复方法,其中所述方法包括以下步骤:
当移动终端的触摸屏固件更新失败时,重启所述移动终端;
读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;
将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
加载所述驱动程序,以完成触摸屏固件修复。
其中在所述当移动终端的触摸屏固件更新失败时,重启所述移动终端的步骤之前还包括:
在触摸屏的触控集成电路IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
其中所述读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序的步骤具体包括:
从所述触摸屏的识别数据存储区读取识别ID; 以及
根据所述触摸屏的识别ID依次判断所述驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与所述触摸屏匹配的驱动程序。
其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
根据所述识别ID读入所述驱动程序中对应的固件数据;
清空触摸屏中的闪存FLASH;
每次向所述触摸屏写入1KB的固件数据;
判断所述固件数据是否写完,若写完,则进入下一步骤;若否,则返回所述每次向所述触摸屏写入1KB的固件数据的步骤;以及
校验所述固件数据是否完整,若否,则返回所述清空触摸屏中的闪存FLASH的步骤;若是,则执行所述加载所述驱动程序,以完成触摸屏固件修复的步骤。
其中所述读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序的步骤还包括:
当从所述驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
根据所述识别ID找出与所述触摸屏匹配的驱动程序后,则把对应于ID的参数从驱动自带的参数数据包中取出来,进入驱动自身自带的参数更新程序,强行把对应于当前ID的有效参数写入到触控IC中。
一种移动终端的触摸屏固件修复装置,其中,包括:
触摸屏判断模块,用于当移动终端的触摸屏固件更新失败时,重启所述移动终端;
驱动匹配模块,用于读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;
固件写入模块,用于将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
加载模块,用于加载所述驱动程序,以完成触摸屏固件修复。
所述的移动终端的触摸屏固件修复装置,其中,还包括:
预先设置模块,用于在触摸屏的触控IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
所述的移动终端的触摸屏固件修复装置,其中,所述驱动匹配模块包括:
读取单元,用于从触摸屏的识别数据存储区读取识别ID;
驱动判断单元,用于根据触摸屏的识别ID依次判断驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与触摸屏匹配的驱动程序。
所述的移动终端的触摸屏固件修复装置,其中,所述固件写入模块包括:
固件读入单元,用于根据所述识别ID读入所述驱动程序中对应的固件数据;
清空单元,用于清空触摸屏中的FLASH;
固件写入单元,用于向所述触摸屏写入1KB的固件数据;
固件判断单元,用于判断所述固件数据是否写完;以及
固件校验单元,用于校验所述固件数据是否完整。
所述的移动终端的触摸屏固件修复装置,其中,所述驱动匹配模块还用于当从驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
本发明还提供一种包括上面所述的移动终端的触摸屏固件修复装置的移动终端。
有益效果
本发明所提供的一种移动终端的触摸屏固件修复方法和装置,有效地解决了现有的移动终端触摸屏固件更新失败导致触摸屏失效的问题,通过当移动终端的触摸屏固件更新失败时,重启所述移动终端;读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;加载所述驱动程序,以完成触摸屏固件修复;使得重启移动终端时能够自动修复固件损坏的触摸屏,只要触摸屏固件损坏后重启移动终端,就会启动驱动软件中的修复模式,强制进入固件更新程序,把驱动程序中包含的完整的参数重新写入到触控IC中,从而修复已经无效的触摸屏,消除了固件更新导致的返修和退货,提高产品的质量,给用户带来了大大的方便。
附图说明
图1为本发明提供的移动终端的触摸屏固件修复方法较佳实施例的流程图;
图2为本发明提供的移动终端的触摸屏固件修复装置较佳实施例的结构框图。
本发明的最佳实施方式
本发明提供一种移动终端的触摸屏固件修复方法和装置,为使本发明的目的、技术方案及优点更加清楚、明确,以下参照附图并举实施例对本发明进一步详细说明。应当理解,此处所描述的具体实施例仅仅用以解释本发明,并不用于限定本发明。
请参阅图1,图1为本发明提供的移动终端的触摸屏固件修复方法较佳实施例的流程图,如图所示,所述方法包括以下步骤:
步骤S100、当移动终端的触摸屏固件更新失败时,重启所述移动终端;
步骤S200、读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;
步骤S300、将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;
步骤S400、加载所述驱动程序,以完成触摸屏固件修复。
下面结合具体的实施例对上述步骤进行详细的描述。
在步骤S100中,当移动终端的触摸屏固件更新失败时,重启所述移动终端。
具体来说,在现有的MTK平台中,为了管理同一个项目中的多款触摸屏驱动,MTK建立了一个触摸屏的架构层去管理所有的驱动,目的是能够遍历所有的触摸屏驱动,以达到多款触摸屏兼容的目的。其中,MTK是台湾联发科技多媒体芯片提供商的简称,全称叫MediaTek。基于MTK平台的移动终端的驱动架构层的控制流程为:将触摸屏(TP)驱动添加到驱动程序结构列表中,然后判断驱动列表当前节点是否为空,若为空,则结束,也就是匹配失败;若不为空,则取出列表中当前驱动,并将驱动列表遍历指针后移。然后再判断取出的当前驱动是否匹配当前TP,若为是,则加载当前驱动,若为否,则继续判断驱动列表当前节点是否为空,即继续依次取出驱动程序结构列表中的驱动程序来与触摸屏(TP)匹配。也就是说,触摸屏的设备驱动程序只有在运行时才会自动添加到驱动列表中,如果系统没有正常加载TP驱动程序,那这个列表就会是空,而且,在进行驱动匹配时列表指针会后移,移到没有数据的尾部后也会是空的,因此需要在检查当前指向的列表节点是否为空,在进行驱动匹配时就会运行从驱动列表当前指针指向的节点中取得的驱动程序,使用此驱动去适配设备,适配失败就退出驱动返回架构层,从驱动列表的下一个节点中获取下一个驱动进行适配。
当检测到有新的固件(FW)时,会先把触摸屏里面的原先的参数全部清除,然后再把新的参数从FW中写到触摸屏的主控IC中,而在更新数据的过程有十几秒钟,而开机界面此时没有任何变化,由于开机界面十几秒钟没有任何变化用户会以为开机失败,强制拔出电池重新上电开机。此时由于旧的参数已经被删除,新的参数未写入,造成触摸屏的主控IC无法运行,触摸屏失效,引起用户返修或退货。
至于如何判断移动终端的触摸屏固件更新失败,通过上述的驱动架构层控制流程可知,当在正常加载匹配完全部驱动后仍然没有匹配成功,这说明触摸屏已经损坏了。具体来说,在驱动加载时设立一个标志,当驱动匹配成功时,就把此标志置位,架构层就通过此标志了解到加载的结果,从而决定是否继续进行下一个触摸屏驱动的匹配,当所有驱动列表中的驱动全部使用完还没有匹配成功,则触摸屏固件更新失败。
由于出问题的设备总是少数,为了所有设备的开机效率,详细的错误检查与信息核对只能在错误机器上进行,要避开正常的设备。因此,需要在驱动架构层设置一个修复模式,当在正常加载匹配完全部驱动后仍然没有匹配成功,说明触摸屏已经损坏了,然后进入修复模式,对每一款驱动都进入触控IC的调试模式进行详细信息匹配。在驱动架构层就通过另一个标志通知各个触摸屏驱动进入修复模式,并且把驱动列表从头重新遍历一遍,每一个触摸屏驱动在匹配时如果匹配成功,就进行触摸屏的参数更新。
在步骤S200中,读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序。具体来说,为了让触摸屏在更新参数中损坏的情况下仍然可以被识别,需要在触摸屏的触控IC中设定一个专用的识别数据存储区,而且这个存储区只能在触摸屏出厂时写入,其它任何时候都不容许修改。所述识别数据存储区用于存放供应商的触摸屏的识别ID,而且这部分数据只在触摸屏出厂时与初始参数一起写入,之后不再修改。
具体来说,在架构层正常遍历驱动列表没有匹配成功之后就进入修复模式,并且从头重新遍历驱动列表,如果在修复模式下还没有匹配上,那就是触摸屏的连接线没有连接好,需要重新连接。每当由于意外造成触摸屏的固件更新失败,重启之后在驱动架构层中就会进入修复模式,从而修复触摸屏,而如果触摸屏是正常的,启动时就会在第一次遍历驱动列表时找到匹配当前触摸屏的驱动程序,然后直接退出驱动的加载过程,不会进行第二遍的遍历,防止正常启动时消耗其它时间,影响开机速度。
在每一个驱动程序中,都会加上与驱动匹配的触摸屏的调试模式的开启方式和通信方式,使得触摸屏在调试模式中把保存在专用的识别数据存储区的信息反馈给驱动程序,通过这个专用的识别数据存储区存储的识别ID等信息,便可判定当前驱动是否和当前触摸屏匹配,如果匹配,就进入固件更新阶段,如果不匹配,就返回架构层,读取下一个驱动程序进行适配,直到匹配成功。
在步骤S300中,将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中。具体来说,若根据所述识别ID找出与所述触摸屏匹配的驱动程序,则把对应于ID的参数从驱动自带的参数数据包中取出来,进入驱动自身自带的参数更新程序,强行把对应于当前ID的有效参数写入到触控IC中,在确认写入完成之后,退回到正常流程,并把当前驱动作为触摸屏的运行驱动添加到移动终端的系统中。
在所述步骤S400中,加载所述驱动程序,以完成触摸屏固件修复。具体来说,通过上述步骤便将移动终端触摸屏固件修复好,只需加载所述驱动程序,便可正常使用所述触摸屏。
进一步地,在所述步骤S100之前,还包括:
S90、在触摸屏的触控IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
进一步地,所述步骤S200具体包括:
S210、从触摸屏的识别数据存储区读取识别ID;
S220、根据触摸屏的识别ID依次判断驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与触摸屏匹配的驱动程序。
进一步地,所述步骤S200还包括:
S230、当从驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
进一步地,所述步骤S300具体包括:
S310、根据所述识别ID读入所述驱动程序中对应的固件数据;
S320、清空触摸屏中的FLASH(闪存);
S330、每次向所述触摸屏写入1KB的固件数据;
S340、判断所述固件数据是否写完,若写完,则进入步骤S350;若否,则返回步骤S330;
S350、校验所述固件数据是否完整,若否,则返回步骤S320;若是,则执行所述步骤S400。
具体来说,在步骤S300中首先根据所述识别ID读入所述驱动程序中对应的固件数据,然后清空触摸屏中原有的固件数据,即上述的FLASH。再依次写入所述识别ID对应的固件数据,每次写入1KB,直到所述固件数据写入完毕。然后校验写入的固件数据是否完整,若完整,则进入步骤S400,加载所述驱动程序,以完成触摸屏固件修复;若不完整,则清空触摸屏的原有固件,重新写入。
本发明提供的移动终端的触摸屏固件修复方法,在确认触摸屏已经损坏后,通过修复模式取得预先存储的触摸屏的识别ID,然后把对应于ID的参数从驱动自带的参数数据包中取出来,进入驱动自身自带的参数更新程序,强行把对应于当前ID的有效参数写入到触控IC中,在确认写入完成之后,退回到正常流程,并把当前驱动作为触摸屏的运行驱动添加到系统中,使得只要触摸屏固件损坏的设备重新开机,驱动软件中的修复模式就会启动,强制进入固件更新程序,把驱动程序中包含的完整的参数重新写入到触控IC中,从而修复已经无效的触摸屏,消除了固件更新导致的返修和退货,提高产品的质量;其通过软件实现,实现简单,成本较低,给用户带来了大大的方便。
基于上述移动终端的触摸屏固件修复方法,本发明还提供了一种移动终端的触摸屏固件修复装置,如图2所示,所述装置包括:
触摸屏判断模块10,用于当移动终端的触摸屏固件更新失败时,重启所述移动终端;具体如步骤S100所述;
驱动匹配模块20,用于读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;具体如步骤S200所述;
固件写入模块30,用于将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;具体如步骤S300所述;
加载模块40,用于加载所述驱动程序,以完成触摸屏固件修复;具体如步骤S400所述。
进一步地,所述的移动终端的触摸屏固件修复装置,其中,还包括:
预先设置模块,用于在触摸屏的触控IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
进一步地,所述驱动匹配模块20包括:
读取单元,用于从触摸屏的识别数据存储区读取识别ID;
驱动判断单元,用于根据触摸屏的识别ID依次判断驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与触摸屏匹配的驱动程序。
进一步地,所述固件写入模块30包括:
固件读入单元,用于根据所述识别ID读入所述驱动程序中对应的固件数据;
清空单元,用于清空触摸屏中的FLASH;
固件写入单元,用于向所述触摸屏写入1KB的固件数据;
固件判断单元,用于判断所述固件数据是否写完;
固件校验单元,用于校验所述固件数据是否完整。
具体来说,所述固件读入单元根据所述识别ID读入所述驱动程序中对应的固件数据,然后通过清空单元清空触摸屏中原有的固件数据,即上述的FLASH。再通过固件写入单元写入所述识别ID对应的固件数据,每次写入1KB,通过固件判断单元判断所述固件数据是否写完,直到所述固件数据写入完毕。然后通过固件校验单元校验写入的固件数据是否完整,若完整,则加载所述驱动程序,以完成触摸屏固件修复;若不完整,则清空触摸屏的原有固件,重新写入。
进一步地,所述的移动终端的触摸屏固件修复装置,其中,所述驱动匹配模块20还用于当从驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
本发明所述的移动终端为手机或平板电脑等具有触摸屏的移动终端。
本发明实施例提供的移动终端的触摸屏固件修复装置形成于一终端,所述终端譬如为手机或平板电脑等具有触摸屏的移动终端,所述移动终端的触摸屏固件修复装置与上文实施例中的移动终端的触摸屏固件修复方法属于同一构思,在所述移动终端的触摸屏固件修复装置上可以运行所述移动终端的触摸屏固件修复方法实施例中提供的任一方法,其具体实现过程详见所述移动终端的触摸屏固件修复方法实施例,此处不再赘述。
需要说明的是,对本发明实施例的移动终端的触摸屏固件修复方法而言,本领域普通技术人员可以理解实现本发明实施例的移动终端的触摸屏固件修复方法的全部或部分流程,是可以通过计算机程序来控制相关的硬件来完成,所述计算机程序可存储于一计算机可读取存储介质中,如存储在终端的存储器中,并被该终端内的至少一个处理器执行,在执行过程中可包括如上述各方法的实施例的流程。其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(ROM)或随机存储记忆体(RAM)等。
对本发明实施例的移动终端的触摸屏固件修复装置而言,其各功能模块可以集成在一个处理芯片中,也可以是各个模块单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时,也可以存储在一个计算机可读取存储介质中,所述存储介质譬如为只读存储器,磁盘或光盘等。
综上所述,本发明提供的一种移动终端的触摸屏固件修复方法和装置,通过当移动终端的触摸屏固件更新失败时,重启所述移动终端;读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;加载所述驱动程序,以完成触摸屏固件修复;使得重启移动终端时能够自动修复固件损坏的触摸屏,只要触摸屏固件损坏后重启移动终端,就会启动驱动软件中的修复模式,强制进入固件更新程序,把驱动程序中包含的完整的参数重新写入到触控IC中,从而修复已经无效的触摸屏,消除了固件更新导致的返修和退货,提高产品的质量,给用户带来了大大的方便,其通过软件实现,实现简单,成本较低。
应当理解的是,本发明的应用不限于上述的举例,对本领域普通技术人员来说,可以根据上述说明加以改进或变换,所有这些改进和变换都应属于本发明所附权利要求的保护范围。
本发明的实施方式
工业实用性
序列表自由内容

Claims (20)

  1. 一种移动终端的触摸屏固件修复方法,其中所述方法包括以下步骤:
    在触摸屏的触控集成电路IC中设置一用于存放触摸屏的识别ID的识别数据存储区;
    当移动终端的触摸屏固件更新失败时,重启所述移动终端;
    读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;当从所述驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码;
    将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
    加载所述驱动程序,以完成触摸屏固件修复。
  2. 根据权利要求1所述的移动终端的触摸屏固件修复方法,其中所述读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序的步骤具体包括:
    从所述触摸屏的识别数据存储区读取识别ID; 以及
    根据所述触摸屏的识别ID依次判断所述驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与所述触摸屏匹配的驱动程序。
  3. 根据权利要求1所述的移动终端的触摸屏固件修复方法,其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
    根据所述识别ID读入所述驱动程序中对应的固件数据;
    清空触摸屏中的闪存FLASH;
    每次向所述触摸屏写入1KB的固件数据;
    判断所述固件数据是否写完,若写完,则进入下一步骤;若否,则返回所述每次向所述触摸屏写入1KB的固件数据的步骤;以及
    校验所述固件数据是否完整,若否,则返回所述清空触摸屏中的闪存FLASH的步骤;若是,则执行所述加载所述驱动程序,以完成触摸屏固件修复的步骤。
  4. 根据权利要求1所述的移动终端的触摸屏固件修复方法,其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
    根据所述识别ID找出与所述触摸屏匹配的驱动程序后,则把对应于ID的参数从驱动自带的参数数据包中取出来,进入驱动自身自带的参数更新程序,强行把对应于当前ID的有效参数写入到触控IC中。
  5. 根据权利要求1所述的移动终端的触摸屏固件修复方法,其中所述移动终端为手机。
  6. 根据权利要求1所述的移动终端的触摸屏固件修复方法,其中所述移动终端为平板电脑。
  7. 一种移动终端的触摸屏固件修复方法,其中所述方法包括以下步骤:
    当移动终端的触摸屏固件更新失败时,重启所述移动终端;
    读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;
    将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
    加载所述驱动程序,以完成触摸屏固件修复。
  8. 根据权利要求7所述的移动终端的触摸屏固件修复方法,其中在所述当移动终端的触摸屏固件更新失败时,重启所述移动终端的步骤之前还包括:
    在触摸屏的触控集成电路IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
  9. 根据权利要求8所述的移动终端的触摸屏固件修复方法,其中所述读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序的步骤具体包括:
    从所述触摸屏的识别数据存储区读取识别ID; 以及
    根据所述触摸屏的识别ID依次判断所述驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与所述触摸屏匹配的驱动程序。
  10. 根据权利要求7所述的移动终端的触摸屏固件修复方法,其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
    根据所述识别ID读入所述驱动程序中对应的固件数据;
    清空触摸屏中的闪存FLASH;
    每次向所述触摸屏写入1KB的固件数据;
    判断所述固件数据是否写完,若写完,则进入下一步骤;若否,则返回所述每次向所述触摸屏写入1KB的固件数据的步骤;以及
    校验所述固件数据是否完整,若否,则返回所述清空触摸屏中的闪存FLASH的步骤;若是,则执行所述加载所述驱动程序,以完成触摸屏固件修复的步骤。
  11. 根据权利要求7所述的移动终端的触摸屏固件修复方法,其中所述读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序的步骤还包括:
    当从所述驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
  12. 根据权利要求7所述的移动终端的触摸屏固件修复方法,其中所述将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中的步骤具体包括:
    根据所述识别ID找出与所述触摸屏匹配的驱动程序后,则把对应于ID的参数从驱动自带的参数数据包中取出来,进入驱动自身自带的参数更新程序,强行把对应于当前ID的有效参数写入到触控IC中。
  13. 一种移动终端的触摸屏固件修复装置,其中所述装置包括:
    触摸屏判断模块,用于当移动终端的触摸屏固件更新失败时,重启所述移动终端;
    驱动匹配模块,用于读取预先存储的触摸屏的识别ID,根据所述识别ID从驱动程序结构列表中找出与所述触摸屏匹配的驱动程序;
    固件写入模块,用于将所述驱动程序中与所述识别ID对应的固件数据写入所述触摸屏中;以及
    加载模块,用于加载所述驱动程序,以完成触摸屏固件修复。
  14. 根据权利要求13所述的移动终端的触摸屏固件修复装置,其中所述装置还包括:
    预先设置模块,用于在触摸屏的触控IC中设置一用于存放触摸屏的识别ID的识别数据存储区。
  15. 根据权利要求14所述的移动终端的触摸屏固件修复装置,其中所述驱动匹配模块包括:
    读取单元,用于从触摸屏的识别数据存储区读取识别ID;以及
    驱动判断单元,用于根据触摸屏的识别ID依次判断驱动程序结构列表中的多个驱动程序是否与触摸屏匹配,找出与触摸屏匹配的驱动程序。
  16. 根据权利要求13所述的移动终端的触摸屏固件修复装置,其中所述固件写入模块包括:
    固件读入单元,用于根据所述识别ID读入所述驱动程序中对应的固件数据;
    清空单元,用于清空触摸屏中的FLASH;
    固件写入单元,用于向所述触摸屏写入1KB的固件数据;
    固件判断单元,用于判断所述固件数据是否写完;以及
    固件校验单元,用于校验所述固件数据是否完整。
  17. 根据权利要求13所述的移动终端的触摸屏固件修复装置,其中所述驱动匹配模块还用于当从驱动程序结构列表中找不到与所述触摸屏匹配的驱动程序,则返回错误代码。
  18. 一种包括权利要求13至17任一项所述的移动终端的触摸屏固件修复装置的移动终端。
  19. 根据权利要求18所述的移动终端,其中所述移动终端为手机。
  20. 根据权利要求18所述的移动终端,其中所述移动终端为平板电脑。
PCT/CN2014/078595 2014-02-19 2014-05-28 一种移动终端的触摸屏固件修复方法和装置 WO2015123932A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410056103.X 2014-02-19
CN201410056103.XA CN103823723B (zh) 2014-02-19 2014-02-19 一种移动终端的触摸屏固件修复方法和装置

Publications (1)

Publication Number Publication Date
WO2015123932A1 true WO2015123932A1 (zh) 2015-08-27

Family

ID=50758805

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/078595 WO2015123932A1 (zh) 2014-02-19 2014-05-28 一种移动终端的触摸屏固件修复方法和装置

Country Status (2)

Country Link
CN (1) CN103823723B (zh)
WO (1) WO2015123932A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857356A (zh) * 2019-02-15 2019-06-07 青岛海信移动通信技术股份有限公司 一种屏幕显示方法、电子设备及存储介质
CN111897552A (zh) * 2020-08-13 2020-11-06 四川长虹电器股份有限公司 一种用于tcon驱动ic的写程方法
CN112905195A (zh) * 2021-03-22 2021-06-04 珠海格力电器股份有限公司 触摸屏驱动配置方法、装置、计算机设备和存储介质
CN114706602A (zh) * 2022-04-01 2022-07-05 珠海读书郎软件科技有限公司 一种基于Android的通过app更新触摸屏参数的方法
WO2022222603A1 (zh) * 2021-04-19 2022-10-27 惠州Tcl云创科技有限公司 一种触摸屏开机触摸失效的处理方法、系统及智能终端

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105204877B (zh) * 2014-06-18 2019-11-15 中兴通讯股份有限公司 一种终端固件升级方法及装置
CN104506539B (zh) * 2014-12-26 2017-12-15 珠海迈越信息技术有限公司 一种基于固件更新的服务器识别方法及装置
CN104598276B (zh) * 2015-01-13 2018-01-16 中科创达软件科技(深圳)有限公司 一种触摸屏固件在线升级方法及装置
CN106371862B (zh) * 2016-08-23 2020-07-14 Tcl移动通信科技(宁波)有限公司 一种移动终端出厂时的触摸屏设置处理方法及系统
CN107291310A (zh) * 2017-06-21 2017-10-24 珠海格力电器股份有限公司 一种触摸屏灵敏度的自适应调节方法、装置及系统
CN107728839B (zh) * 2017-09-28 2021-05-21 努比亚技术有限公司 冻屏监测解决方法、移动终端及计算机可读存储介质
CN108205446A (zh) * 2017-10-24 2018-06-26 中兴通讯股份有限公司 固件修复方法及装置
CN113127252A (zh) * 2021-05-14 2021-07-16 江苏华存电子科技有限公司 一种存储器装置中固件智能修复方法
CN115543172B (zh) * 2022-11-23 2023-03-14 天津华宁电子有限公司 一种刮板运输机集成式矿鸿人机界面显示控制方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100088498A1 (en) * 2006-08-01 2010-04-08 Research In Motion Limited System and method for managing hardware configuration parameters
CN102033770A (zh) * 2010-12-17 2011-04-27 中兴通讯股份有限公司 移动终端的触摸屏固件升级方法及装置
CN102646044A (zh) * 2012-03-06 2012-08-22 深圳市福智软件技术有限公司 一种多触摸屏加载程序的系统和方法
CN202548794U (zh) * 2012-02-14 2012-11-21 上海与德通讯技术有限公司 触摸屏设备
CN103577213A (zh) * 2012-08-09 2014-02-12 深圳市中兴移动通信有限公司 一种智能终端触摸屏固件的升级方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9519423B2 (en) * 2011-04-22 2016-12-13 Sony Corporation Information processing apparatus
CN103246535B (zh) * 2013-04-26 2016-08-03 广州德浩科视电子科技有限公司 一种拼接屏升级系统的升级方法
CN103455354B (zh) * 2013-09-06 2017-04-12 南京南自信息技术有限公司 一种防止固件升级失败的方法和设备
CN103533534B (zh) * 2013-10-15 2017-02-01 厦门亿联网络技术股份有限公司 一种dect手机的固件无线升级方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100088498A1 (en) * 2006-08-01 2010-04-08 Research In Motion Limited System and method for managing hardware configuration parameters
CN102033770A (zh) * 2010-12-17 2011-04-27 中兴通讯股份有限公司 移动终端的触摸屏固件升级方法及装置
CN202548794U (zh) * 2012-02-14 2012-11-21 上海与德通讯技术有限公司 触摸屏设备
CN102646044A (zh) * 2012-03-06 2012-08-22 深圳市福智软件技术有限公司 一种多触摸屏加载程序的系统和方法
CN103577213A (zh) * 2012-08-09 2014-02-12 深圳市中兴移动通信有限公司 一种智能终端触摸屏固件的升级方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857356A (zh) * 2019-02-15 2019-06-07 青岛海信移动通信技术股份有限公司 一种屏幕显示方法、电子设备及存储介质
CN111897552A (zh) * 2020-08-13 2020-11-06 四川长虹电器股份有限公司 一种用于tcon驱动ic的写程方法
CN112905195A (zh) * 2021-03-22 2021-06-04 珠海格力电器股份有限公司 触摸屏驱动配置方法、装置、计算机设备和存储介质
WO2022222603A1 (zh) * 2021-04-19 2022-10-27 惠州Tcl云创科技有限公司 一种触摸屏开机触摸失效的处理方法、系统及智能终端
CN114706602A (zh) * 2022-04-01 2022-07-05 珠海读书郎软件科技有限公司 一种基于Android的通过app更新触摸屏参数的方法
CN114706602B (zh) * 2022-04-01 2023-03-24 珠海读书郎软件科技有限公司 一种基于Android的通过app更新触摸屏参数的方法

Also Published As

Publication number Publication date
CN103823723B (zh) 2017-08-08
CN103823723A (zh) 2014-05-28

Similar Documents

Publication Publication Date Title
WO2015123932A1 (zh) 一种移动终端的触摸屏固件修复方法和装置
US20040225873A1 (en) Method and system for recovering program code in a computer system
WO2013103023A1 (ja) 情報処理装置、情報処理方法、およびコンピュータプログラム
CN106775610B (zh) 一种电子设备启动方法及一种电子设备
US11995427B2 (en) Method, apparatus, device, and storage medium for upgrading vehicle-mounted Tbox
WO2016206514A1 (zh) 启动处理方法及装置
US20030070102A1 (en) Password changing method and computer system, and computer readable record medium storing a program therein
CN111625295A (zh) 一种嵌入式系统启动方法、装置、设备及存储介质
CN112433769A (zh) 一种bmc启动方法、装置、计算机设备及存储介质
US7418542B2 (en) Rewritable, nonvolatile memory, electronic device, method of rewriting rewritable, nonvolatile memory, and storage medium having stored thereon rewrite program
CN113157303A (zh) 升级方法、嵌入式系统、终端及计算机存储介质
CN109375953B (zh) 一种操作系统启动方法及装置
CN116578327B (zh) 一种程序更新方法、装置及电子设备和存储介质
CN113220319A (zh) 一种数据更新方法、装置及车辆
CN106325912B (zh) 嵌入式操作系统的启动方法及装置
CN102043640A (zh) 快闪系统及其程序更新方法
JP2001331379A (ja) フラッシュメモリ更新プログラムの書き換え方法及び装置
CN107168824A (zh) 一种断电保护方法及装置
CN113190244A (zh) 无线模组升级的方法、装置、计算机设备和存储介质
JP2003216449A (ja) パッチ処理システム
CN112162772B (zh) 一种应用程序的运行控制方法、装置、单片机及存储介质
WO2022211483A1 (en) Method and apparatus for avoiding exception
CN113127044A (zh) 一种bmc升级方法、装置及相关组件
WO2019093762A1 (ko) 전자 장치 및 그 제어 방법
JP2003330724A (ja) 情報処理装置、情報処理方法、及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14883428

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14883428

Country of ref document: EP

Kind code of ref document: A1