US8930710B2 - Using a manifest to record presence of valid software and calibration - Google Patents

Using a manifest to record presence of valid software and calibration Download PDF

Info

Publication number
US8930710B2
US8930710B2 US13/557,060 US201213557060A US8930710B2 US 8930710 B2 US8930710 B2 US 8930710B2 US 201213557060 A US201213557060 A US 201213557060A US 8930710 B2 US8930710 B2 US 8930710B2
Authority
US
United States
Prior art keywords
software
calibration
memory
file
files
Prior art date
Legal status (The legal status 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 status listed.)
Active, expires
Application number
US13/557,060
Other languages
English (en)
Other versions
US20130111271A1 (en
Inventor
Kevin M. Baltes
James T. Kurnik
Ronald J. Gaynier
Thomas M. Forest
Ansaf I. Alrabady
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
GM Global Technology Operations LLC
Original Assignee
GM Global Technology Operations LLC
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 GM Global Technology Operations LLC filed Critical GM Global Technology Operations LLC
Priority to US13/557,060 priority Critical patent/US8930710B2/en
Assigned to GM Global Technology Operations LLC reassignment GM Global Technology Operations LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GAYNIER, RONALD J., ALRABADY, ANSAF I., BALTES, KEVIN M., FOREST, THOMAS M., KURNIK, JAMES T.
Priority to DE102012109615.5A priority patent/DE102012109615B4/de
Priority to CN201210415290.7A priority patent/CN103198270B/zh
Publication of US20130111271A1 publication Critical patent/US20130111271A1/en
Assigned to WILMINGTON TRUST COMPANY reassignment WILMINGTON TRUST COMPANY SECURITY AGREEMENT Assignors: GM Global Technology Operations LLC
Assigned to GM Global Technology Operations LLC reassignment GM Global Technology Operations LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: WILMINGTON TRUST COMPANY
Application granted granted Critical
Publication of US8930710B2 publication Critical patent/US8930710B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/26—Functional testing
    • G06F11/261—Functional testing by simulating additional hardware, e.g. fault simulation
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0426—Programming the control sequence
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0428—Safety, monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/26—Functional testing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24034—Model checker, to verify and debug control software

Definitions

  • This invention relates generally to a system and method for determining that operating software and/or calibration files are present and valid after a bootloader flashes the files into the memory of a controller before allowing the operating software to execute in the controller and, more particularly, to a system and method for determining that operating software and/or calibration files are present and valid after a bootloader flashes the files into the memory of a vehicle electronic control unit (ECU) before allowing the operating software to execute in the ECU, where the method includes creating a programming manifest at the beginning of a memory segment for both the operating software and the calibration files that identifies that all of the programmable parts in the software and calibration memory segments are valid.
  • ECU vehicle electronic control unit
  • ECUs electronice control units
  • controllers that control the operation of vehicle systems, such as the powertrain, climate control system, infotainment system, body systems, chassis systems, and others.
  • vehicle systems such as the powertrain, climate control system, infotainment system, body systems, chassis systems, and others.
  • Such controllers require special purpose-designed software in order to perform the control functions.
  • software that is not properly validated, or worse, maliciously-designed, in a vehicle controller include unintended behavior of the vehicle or its systems, loss of anti-theft features on the vehicle, potential tampering with components such as the odometer, and loss of other vehicle features and functions.
  • asymmetric key cryptography uses digital signatures for authenticating files that are programmed into controllers.
  • asymmetric key cryptography uses a pair of mathematically-related keys, known as a private key and a public key, to encrypt and decrypt a message.
  • a signer uses his private key, which is known only to himself, to encrypt a message.
  • the digital signature can later be decrypted by another party using the public key, which is paired to the signer's private key.
  • Flashing is a well known process for uploading software, calibration files and other applications into the memory of a vehicle ECU or other programmable device.
  • a bootloader is an embedded software program loaded in the memory of the ECU that provides an interface between the ECU and a programming device that is flashing the software.
  • the bootloader flashes the operating software and calibration files into the ECU memory, where the operating software provides the software that causes the various vehicle functions to operate in conjunction with each other and the calibration files are the various vehicle configuration and tuning parameters, such as binary switches, thresholds, etc., for the particular vehicle systems.
  • the bootloader typically employs asymmetric key cryptography and stores a public key that must be used to decode a digital signature transferred by the programming device before uploading to or reflashing of the ECU is allowed to prevent malicious software or calibration files from being uploaded into the ECU.
  • the bootloader can determine that the operating software and/or calibration files are present and valid by checking for the occurrence of specific digital patterns, known as a “presence pattern” within software and/or calibration file memory blocks.
  • a prefix pattern a digital pattern within software and/or calibration file memory blocks.
  • the bootloader has to “know” where the presence patterns are located, even if the patterns can be moved in fixed memory increments.
  • software and calibration re-partitioning may render the bootloader incompatible with the software and calibration files stored in the memory.
  • the presence patterns are included in the software and calibration files, the patterns exist before the integrity check is performed.
  • a system and method for verifying that operating software and/or calibration files are present and valid after a bootloader flashes the files into the memory on a vehicle ECU before allowing the operating software to execute.
  • the ECU memory defines a memory segment for each of the operating software and the calibration files.
  • a software manifest is provided in a memory slot before the operating software segment in the ECU memory.
  • a calibration manifest is provided in a memory slot before the calibration segment in the ECU memory.
  • FIG. 1 is a block diagram of a system showing the operation of digital signature verification process
  • FIG. 2 is a flow chart diagram showing a process for identifying if operating software and calibration parts are present and valid in an ECU memory to allow a bootloader to execute the operating software;
  • FIG. 3 is a representation of a memory in the ECU showing programming manifests including flags that identify that the software and calibration files are present and valid;
  • FIG. 4 is another representation of a memory in the ECU showing programming manifests including flags that identify that the software and calibration files are present and valid.
  • FIG. 1 is a block diagram 10 of a known method for using asymmetric key digital signatures for authenticating files that are programmed into controllers.
  • asymmetric key cryptography uses a pair of mathematically-related keys known as a private key and a public key to encrypt and decrypt a message.
  • a signer uses his private key, which is known only to himself, to encrypt a file or message.
  • the digital signature can later be decrypted by another party using the public key, which is paired to the signer's private key to authenticate a file or message.
  • a content file 14 is provided, where the content file 14 could be a piece of software, a calibration file, or other “soft-part” content to be used in a controller.
  • a hash calculation is performed on the content file 14 to produce a hash value 16 .
  • the hash value 16 is then encrypted with the signer's private key to produce a digital signature 18 , where the digital signature 18 is only good for that particular content file 14 .
  • the digital signature 18 and the content file 14 are then used in a verifying step 20 , which would be performed by the bootloader in the ECU in the application being discussed herein.
  • the digital signature 18 is decrypted using the signer's public key to produce a hash value 22 .
  • a hash calculation is performed on the content file 14 by the verifier to produce a calculated hash value 24 .
  • the decrypted hash value 22 is compared to the calculated hash value 24 . If the decrypted hash value 22 matches the calculated hash value 24 , then a valid determination at oval 28 is issued, and the content file 14 is used. If the decrypted hash value 22 does not match the calculated hash value 24 , then an invalid determination at oval 30 is issued, and the content file 14 is not used.
  • the present invention proposes a technique for validating that an operating software has been properly flashed into the memory of a vehicle ECU using a bootloader.
  • the technique allocates a predetermined memory space at a first software flash section in a memory segment for the software, where the software code immediately follows the memory space.
  • the memory space is defined as a software programming manifest that identifies that the operating software has properly been flashed, for example, by setting a flag in the software manifest.
  • the first memory segment is used as the software manifest because it is erased first during software reprogramming to record the software programming results.
  • the memory space for the manifest is an increment of the smallest write size permitted by the bootloader flash. The software being flashed does not overwrite this memory space.
  • the results of an integrity check such as digital signature verification described above, are recorded in the manifest.
  • the present invention also proposes a technique for validating that calibration files have been properly flashed into the memory of a vehicle ECU using a bootloader.
  • the technique allocates a predetermined memory space at a first calibration file flash section in a memory segment for the calibration files, where the calibration file code immediately follows the memory space.
  • the memory space is defined as a calibration file programming manifest that identifies that the calibration files have properly been flashed, for example, by setting a flag in the calibration file manifest.
  • the first memory segment is used as the calibration file manifest because it is erased first during calibration file reprogramming to record the calibration file results.
  • the memory space for the manifest is an increment of the smallest write size permitted by the bootloader flash.
  • the calibration files being flashed do not overwrite this memory space. After the bootloader programs each calibration file, the results of the integrity check are recorded in the manifest space.
  • the bootloader Upon an ECU reset, the bootloader will check all software and calibration flags in the software and calibration file manifests. If all of the flags are valid, then a transfer to the operating software is permitted. Otherwise, the bootloader stays in the boot mode.
  • FIG. 2 is a flow chart diagram 40 showing a process for using programming manifests to record the presence of valid software and/or calibration files when flashing the operating software and/or calibration files to the memory on a vehicle ECU by a bootloader flashing process.
  • a bootloader programming executive at box 42 controls the bootloader programming function, and this function may be entered via request by a service tool at a servicing facility.
  • the bootloader programming executive detects a request to program software or calibration and enters box 44 to perform some operation, such as uploading or flashing the operating software and/or calibration files for the particular vehicle ECU.
  • the bootloader flashes an operating software or calibration file, it first erases the appropriate memory segment(s), which sets the flag(s) in a programming manifest memory space indicating that the software or particular calibration file has not been properly flashed.
  • the bootloader determines whether a valid flash has occurred each time a separate piece of software or calibration file is flashed by determining that the flag has been properly set in the manifest.
  • the bootloader performs an integrity check and updates the programming manifest at box 48 .
  • the bootloader determines whether all of the operating software and calibration files have been properly flashed at decision diamond 50 , and if not, returns to the bootloader programming executive at the box 42 to flash the next piece of software or calibration file. If all of the software and/or calibration files are properly flashed at the decision diamond 50 , then the bootloader determines whether all of the operating software and calibration file flags in the programming manifest have been properly set and are valid at decision diamond 52 , and if so, allows execution of the operating software at box 54 .
  • the bootloader sends a negative response message to the requester, such as the programming tool, at box 56 indicating that the flashing has not properly occurred.
  • FIG. 3 is a representation of a portion of an ECU memory 60 including a flash memory segment 62 that stores operating software and calibration files that are flashed by the bootloader.
  • the bootloader stores one operating software file and four calibration files for the particular application, which is by way of a non-limiting embodiment.
  • the operating software is flashed into a memory section 64 and the calibration files are flashed into memory sections 66 .
  • a programming manifest is defined in the memory segment 62 for both the operating software and the calibration files, and that manifest is at the beginning of the memory segment for the operating software or the calibration files.
  • the software manifest is stored at memory slot 68 before the software memory section 64 and only includes a single software flag 70 because the operating software only includes a single part, namely, the operating software stored in the segment 64 .
  • the calibration manifest is located at memory slot 72 before the calibration files in the memory sections 66 , where the calibration manifest stores a calibration flag 74 for each of the separate calibration files, which would be four calibration flags in this example.
  • the manifest memory space is provided at the beginning of the memory segment for the operating software and calibration files because this space would be the first part of the memory to be erased if the operating software or the particular calibration file were reprogrammed with new files, where a new flag would need to be set in the manifest for those new files. Note since the calibration files all reside in the same memory segment, all calibration files must be programmed during any calibration flashing event and the segment is erased once before writing the first calibration file.
  • FIG. 4 is another representation of a portion of an ECU memory 80 where like elements to the ECU memory 60 are identified by the same reference numeral.
  • a calibration manifest including a calibration flag is provided immediately preceding each of the calibration files.
  • a calibration manifest is provided at memory slot 82 for a calibration file stored in memory section 84 and includes a single calibration flag
  • a calibration manifest is provided at memory slot 86 for a calibration file stored in memory section 88 and also includes a single calibration flag
  • a calibration manifest is provided in memory slot 90 for a calibration file stored in memory section 92 and also includes a single calibration flag
  • a calibration manifest is provided at memory slot 94 for a calibration file stored in memory section 96 and also includes a single calibration file.
  • the configuration of the ECU memory 80 may have benefits over the configuration of the ECU memory 60 because the calibration files may be flashed to different calibration segments that are not contiguous with each other where a calibration manifest would be provided at the beginning of the separate calibration segments that may be overwritten when the new calibration file is downloaded.
  • the knowledge of what segments in the ECU memory are flashed for one or more calibration files may determine how many flags are in the calibration manifest, where one flash segment may include a single calibration file and other flash segments may include multiple calibration files.
  • the bootloader would ensure that all of the calibration files are programmed before that flag is set by enforcing a programming sequence of the calibration files. For example, each calibration file would be given a specific sequence ID, and flashing of the calibration files would be performed in the order of those IDs. For example, a calibration file with a sequence ID of 3 would not be flashed before a calibration file with a sequence ID of 2.
  • programming of the calibration file being flashed must be successful, i.e., the signature must be valid, before the next calibration file is flashed.
  • the bootloader sets the flag to indicate successful programming for all of the calibration files in that segment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Automation & Control Theory (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
US13/557,060 2011-10-28 2012-07-24 Using a manifest to record presence of valid software and calibration Active 2033-07-12 US8930710B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US13/557,060 US8930710B2 (en) 2011-10-28 2012-07-24 Using a manifest to record presence of valid software and calibration
DE102012109615.5A DE102012109615B4 (de) 2011-10-28 2012-10-10 Verwendung eines Manifests zur Präsenzaufzeichnung von gültiger Software und Kalibrierung
CN201210415290.7A CN103198270B (zh) 2011-10-28 2012-10-26 使用清单来记录有效软件和校准文件的存在

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161552968P 2011-10-28 2011-10-28
US13/557,060 US8930710B2 (en) 2011-10-28 2012-07-24 Using a manifest to record presence of valid software and calibration

Publications (2)

Publication Number Publication Date
US20130111271A1 US20130111271A1 (en) 2013-05-02
US8930710B2 true US8930710B2 (en) 2015-01-06

Family

ID=48084482

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/557,060 Active 2033-07-12 US8930710B2 (en) 2011-10-28 2012-07-24 Using a manifest to record presence of valid software and calibration

Country Status (3)

Country Link
US (1) US8930710B2 (de)
CN (1) CN103198270B (de)
DE (1) DE102012109615B4 (de)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9928890B2 (en) 2016-08-29 2018-03-27 Apple Inc. System and method for calibrating memory using credit-based segmentation control
US10430178B2 (en) 2018-02-19 2019-10-01 GM Global Technology Operations LLC Automated delivery and installation of over the air updates in vehicles

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9600662B2 (en) * 2014-06-06 2017-03-21 T-Mobile Usa, Inc. User configurable profiles for security permissions
US9430220B2 (en) * 2014-07-22 2016-08-30 GM Global Technology Operations LLC Method, medium, and apparatus for re-programming flash memory of a computing device
CA2988947C (en) 2015-06-08 2023-10-03 Cosmetic Technologies, Llc Automated delivery system of a cosmetic sample
JP2017167916A (ja) * 2016-03-17 2017-09-21 株式会社デンソー 情報処理システム
DE102016007498A1 (de) 2016-06-18 2017-12-21 Audi Ag Manipulationssichere Bereitstellung einer Funktionalität eines Assistenzsystems eines Kraftfahrzeugs
DE102016221108A1 (de) * 2016-10-26 2018-04-26 Volkswagen Aktiengesellschaft Verfahren zum Aktualisieren einer Software eines Steuergeräts eines Fahrzeugs
CN106789672B (zh) * 2017-01-18 2020-08-04 北京经纬恒润科技有限公司 一种报文路由处理方法及装置
US11822955B2 (en) * 2020-01-17 2023-11-21 Steering Solutions Ip Holding Corporation System and method for decentralized vehicle software management

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5619698A (en) * 1995-05-05 1997-04-08 Apple Computer, Inc. Method and apparatus for patching operating systems
US6505105B2 (en) * 2001-01-05 2003-01-07 Delphi Technologies, Inc. Electronic control unit calibration
US6550052B1 (en) * 1999-11-09 2003-04-15 Daimlerchrysler Corporation Software development framework for constructing embedded vehicle controller software
US20080133823A1 (en) * 2004-09-30 2008-06-05 Martin Laichinger Method For Describing Memory Contents And For Describing The Transfer Of Memory Contents
US20110138188A1 (en) * 2009-12-04 2011-06-09 Electronics And Telecommunications Research Institute Method and system for verifying software platform of vehicle

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6571191B1 (en) 1998-10-27 2003-05-27 Cummins, Inc. Method and system for recalibration of an electronic control module
US7366589B2 (en) 2004-05-13 2008-04-29 General Motors Corporation Method and system for remote reflash
CN101031880A (zh) * 2004-09-30 2007-09-05 罗伯特·博世有限公司 用于描述存储内容和用于描述存储内容的传输的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5619698A (en) * 1995-05-05 1997-04-08 Apple Computer, Inc. Method and apparatus for patching operating systems
US6550052B1 (en) * 1999-11-09 2003-04-15 Daimlerchrysler Corporation Software development framework for constructing embedded vehicle controller software
US6505105B2 (en) * 2001-01-05 2003-01-07 Delphi Technologies, Inc. Electronic control unit calibration
US20080133823A1 (en) * 2004-09-30 2008-06-05 Martin Laichinger Method For Describing Memory Contents And For Describing The Transfer Of Memory Contents
US20110138188A1 (en) * 2009-12-04 2011-06-09 Electronics And Telecommunications Research Institute Method and system for verifying software platform of vehicle

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Jung et al. "Fault Tolerant Protocol for CAN Flash Programming", The 13th International Pacific Conference on Automotive Engineering , Aug. 22-24, 2005, 6 pages. *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9928890B2 (en) 2016-08-29 2018-03-27 Apple Inc. System and method for calibrating memory using credit-based segmentation control
US10430178B2 (en) 2018-02-19 2019-10-01 GM Global Technology Operations LLC Automated delivery and installation of over the air updates in vehicles

Also Published As

Publication number Publication date
CN103198270B (zh) 2015-11-25
CN103198270A (zh) 2013-07-10
US20130111271A1 (en) 2013-05-02
DE102012109615B4 (de) 2022-05-12
DE102012109615A1 (de) 2013-05-02

Similar Documents

Publication Publication Date Title
US8930710B2 (en) Using a manifest to record presence of valid software and calibration
US8978160B2 (en) Method for selective software rollback
US8856538B2 (en) Secured flash programming of secondary processor
US9021246B2 (en) Method to replace bootloader public key
US8881308B2 (en) Method to enable development mode of a secure electronic control unit
US8966248B2 (en) Secure software file transfer systems and methods for vehicle control modules
JP6595822B2 (ja) 情報処理装置及びその制御方法
CN105938433B (zh) 用于对机动车的控制设备进行编程的方法
US20140075517A1 (en) Authorization scheme to enable special privilege mode in a secure electronic control unit
US8856536B2 (en) Method and apparatus for secure firmware download using diagnostic link connector (DLC) and OnStar system
US8880898B2 (en) Anti-roll-back mechanism for counter
JP4733840B2 (ja) 署名方法
US10423401B2 (en) Method for updating software of a control device of a vehicle
CN111984962B (zh) 固件安全验证方法及装置
US20130111212A1 (en) Methods to provide digital signature to secure flash programming function
US20070028115A1 (en) Method for guaranteeing the integrity and authenticity of flashware for control devices
US20140058532A1 (en) Method for partial flashing of ecus
US11429364B2 (en) Software installation method
US10282549B2 (en) Modifying service operating system of baseboard management controller
CN110520861B (zh) 用于通过使用安全元件来快速认证程序的方法和装置
CN108229144B (zh) 一种应用程序的验证方法、终端设备及存储介质
US20100100966A1 (en) Method and system for blocking installation of some processes
US20200233676A1 (en) Bios management device, bios management system, bios management method, and bios management program-stored recording medium
KR101806719B1 (ko) 보안 부팅에 따른 메모리 영역 자동 설정이 가능한 전자 제어유닛 및 이를 이용한 보안 부팅 방법
KR20130015007A (ko) 비휘발성 메모리의 메모리 블록의 검증 방법

Legal Events

Date Code Title Description
AS Assignment

Owner name: GM GLOBAL TECHNOLOGY OPERATIONS LLC, MICHIGAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BALTES, KEVIN M.;KURNIK, JAMES T.;GAYNIER, RONALD J.;AND OTHERS;SIGNING DATES FROM 20120717 TO 20120722;REEL/FRAME:028831/0609

AS Assignment

Owner name: WILMINGTON TRUST COMPANY, DELAWARE

Free format text: SECURITY AGREEMENT;ASSIGNOR:GM GLOBAL TECHNOLOGY OPERATIONS LLC;REEL/FRAME:030694/0500

Effective date: 20101027

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: GM GLOBAL TECHNOLOGY OPERATIONS LLC, MICHIGAN

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:034287/0415

Effective date: 20141017

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8