Process for the protection of stored program controls from overwriting

[0002] The present invention relates to a method for protecting stored-program control systems from being overwritten.

[0003] Methods for protecting stored-program control systems, which are preferably used in motor vehicles, are already known. In German Patent No. 43 44 866 a control device, in particular a motor vehicle control device, is programmed via an external programming device. In order to prevent unintentional programming, an inquiry must be made by the control device to the external programming device. The inquiry is accomplished via a means which can detect a signal to authorize programming if the external programming device is connected with its serial transmission line to the control device. After this security inquiry, programming of the control device is accomplished into a programmable nonvolatile memory of the control device, via the serial interface. This conventional method represents a purely hardware-based programming protection system. The purely hardware based protection system for the programmable memory requires the use of various electronic components in the control device, which are capable of detecting connection of the data transmission line on a hardware basis. This implies additional physical complexity for the control device.

[0004] Also, simple software security systems, which generally invoked by the programming device or tester, are conventional. With purely software-based security systems, there is always the risk that a skip in the program routine will cause authorization for programming to be granted incorrectly.

[0005] The method according to the present invention has the advantage that unintentional programming of the program memory cannot occur, since the programming routine contains additional security inquiries which check for authorization before execution of each programming segment. It is particularly advantageous if the programming routines that are stored in the control device are structured in the form of modules. As a result, unintentional deletion and writing of new data into the programmable memory is no longer possible, since the program cannot be activated even by an unintentional jump to an arbitrary position.

[0006] It is also advantageous to assemble the program routine from instruction sequences. When the instruction sequence is executed, authorization is also checked after each instruction.

[0007] It is advantageous in this context to store authorization flags in a RAM (random access memory). Advantageously, the authorization is performed not simply by storing once, but by repeatedly storing the authorization flag in the RAM in redundant fashion, and further programming can be accomplished only after checking multiple authorization flags.

[0008] A further advantageous embodiment is represented by storage of the authorization in the form of specific RAM address contents, whereby the program routine checks the contents of the addresses. It is also possible to generate the authorization as a combination of registers and data transferred from the programming device.

[0009] It is further advantageous, for authorization of the programming routine, for signals to be sent by the external programming device, which causes flags to be set in the programming routine.

[0010] This authorization can be implemented by the external programming device as a one-time transfer of the authorization signals, so that the authorizations are accessed in memory during programming.

[0011] Also advantageous, however, is a variant which queries the authorization from the programming device between the

[0012] FIG. 1 illustrates a programming operation of a method according to the present invention.

[0013] A control device which is protected by a software protection system, in a manner defined by the method according to the present invention, from overwriting its program memory can be a braking, engine, or transmission control device. Usually, a control device of this kind can be connected via a diagnostic connector to an external programming device. The control devices are installed in the motor vehicle during production, programming of the control devices being accomplished at the end of the line or in the shop. The control device contains a microprocessor on which, in an integrated or separate fashion, a nonvolatile programmable memory is provided. The nonvolatile memory is configured, in particular, as a flash EPROM. To program the nonvolatile memory, an authorization signal must be applied to the memory. The programming routine is an internal control device program which makes it possible to program the nonvolatile memory. This programming routine is stored in the ROM or RAM of the control device processor. In order to initiate programming, a signal is transmitted from the external programming device, or tester, to the control device. The control device detects the signal and the programming routine sets the authorization flag. This authorization flag is stored in RAM.

[0014] In a first exemplary embodiment, it is assumed that programming of the nonvolatile memory cannot be performed directly from the program memory of the processor in which the programming routine is stored. The programming routine must therefore first be loaded into the executable memory, i.e. from flash memory into X-RAM. For that purpose, the programming routine is broken down into at least two modules, each of which cannot by itself, initiate programming of the nonvolatile memory. After the first module has been loaded, according to the present invention the programming authorization is queried again before the next module is loaded.

[0015] In a further example, it is assumed that a specific instruction sequence must be written in order to program the memory. According to the present invention, inquiries which check whether a programming authorization exists are inserted within the programming sequence. If no such authorization exists, programming is terminated. As a result, an unintentional jump to an arbitrary point in the program cannot in any circumstances result in programming of the memory. The programming authorization is initiated by the tester and detected by the processor in the control unit. The program grants the authorization, and sets the authorization flag that is stored in RAM. It is therefore necessary to take additional actions so that this programming authorization is not unintentionally, e.g. due to an execution fault in the program, entered into RAM. This would mean that unintentional programming could be performed despite the intervening check. The following steps are used as additional measures:

[0016] 1. The programming authorization is stored in multiple redundant fashion in RAM. This prevents authorization from occurring if an authorization flag is unintentionally written to RAM on a single occasion.

[0017] 2. The programming authorization is not explicitly stored in a program module. Instead, the programming authorization is detected implicitly by way of a check of the contents of specific RAM addresses, the addresses being written from outside, for example by the tester, i.e. not at any point by the program itself.

[0018] 3. Addresses and/or contents, which are constituents of the programming sequence, are generated only by combining addresses with data transferred from the tester.

[0019] FIG. 1 depicts a programming process in an exemplary embodiment. The exemplary embodiment shows the programming operation from bytes 1 through n that are to be programmed by the tester into the nonvolatile memory. The memory is designed so that it programs a byte #i precisely when authorization byte #1, authorization byte #2, address byte #i, and the contents of byte #i are transferred to it correctly and in that sequence. To begin this operation, the tester sends to the control device the request for programming. The tester then sends PF1 through PF3 in program authorization block 8 to the control device, in which they are stored in RAM as authorization flags PF1 through PF3. Byte #i through byte #n in program block 9, which are to be programmed, are then transferred by the tester and temporarily stored in RAM. As defined by the method according to the present invention, in order to program a byte #i, first the authorization is checked. The programming routine checks whether authorization flags PF1 through PF31, 2, 3 are correct. If so, authorization byte #1 is transferred to EPROM 4. Then another inquiry 1′, 2′, 3′ for program authorization flags PF1 through PF3 is made. If the check is successful, the second authorization byte #2 is transferred 5. Then the address and contents of byte #i are transferred. This results in the programming of byte #i 7. From this point the programming routine returns back to the starting point in order to transfer the next data of byte #i+1. Each time, the authorization flag is checked first and then the authorization bytes #1 or #2 are written.