Method for programming a bus-compatible electronic motor vehicle controller

• US 5,444,643 A
• Filed: 09/08/1993
• Issued: 08/22/1995
• Est. Priority Date: 09/08/1992
• Status: Expired due to Fees

• Current Assignee: Daimler Chrysler Company LLC (Stellantis NV)
• Original Assignee: Mercedes-Benz AG (Mercedes-Benz Group AG)
• Inventors: Muller, Karlheinz, Thurner, Thomas, Haussler, Bernd
• Primary Examiner(s): Voeltz, Emanuel T.
• Assistant Examiner(s): Assouad, Patrick J.
• Application Number:
  US08/117,838
• Time in Patent Office: 713 Days
• Field of Search: 364/579, 364/242.94, 364/238.3, 364/238.6, 364/239, 364/239.6, 364/239.7, 364/239.8, 364/239.9, 364/240, 364/240.1, 364/240.5, 364/240.8 , 364/242.2, 364/242.4, 364/242.6, 364/242.92, 364/242.95, 364/242.96, 395/200, 395/275, 395/700, 395/250, 395/550, 340/825.5
• US Class Current: 702/122
• CPC Class Codes: B60R 16/0315 using multiplexing techniques multiplexing for transmission of signals G08C15/00; multiplexing for electrical communication in general H04J
• CPC Class Codes: H04L 12/40 Bus networks
• CPC Class Codes: H04L 12/4135 using bit-wise arbitration
• CPC Class Codes: H04L 12/5692 Selection among different networks
• CPC Class Codes: H04L 2012/40215 Controller Area Network CAN
• CPC Class Codes: H04L 2012/40273 the transportation system being a vehicle
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 49/9057 Arrangements for supporting packet reassembly or resequencing
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC

Abstract

A method for programming a bus-compatible electronic motor vehicle controller that is equipped with at least one microcomputer to implement its control function and with ROM and RAM in order to accommodate and handle applications software required for the control function, and is also equipped with at least one bus protocol chip, the ROM being programmed such that the applications software communicates with a bus via the bus protocol chip and via a specific instruction and communications interface forming a first interface of the bus protocol chip. The method includes providing a second interface, which is independent of the bus protocol chip, and defining the second interface as a further, universal instruction and communications interface. The first and second interfaces are coupled with a driver module that is independent of the applications software and adapted to the bus protocol chip and has the properties of an adapter. The applications software are matched and aligned exclusively to the second interface with respect to the bus communication and the applications software is produced independently of the bus protocol chip. The applications software and the driver module are linked to one another by a link process. Program code is obtained as a result of the link process. The program code is stored such that the program code is resident in the ROM.

Claims

1. Method for programming a bus-compatible electronic motor vehicle controller that is equipped with at least one microcomputer to implement its control function and with ROM and RAM in order to accommodate and handle applications software required for the control function, and is also equipped with at least one bus protocol chip, and the ROM being programmed such that the applications software communicates with a bus via the at least one bus protocol chip and via a specific instruction and communications interface forming a first interface of said at least one bus protocol chip, comprising:

providing a second interface, which is independent of the at least one bus protocol chip, and defining the second interface as a standard instruction and communications interface;

coupling said first and second interfaces with a driver module that is independent of the applications software and adapted to the at least one bus protocol chip and has the properties of an adapter;

matching and aligning the applications software exclusively to the second interface with respect to the bus communication and producing the applications software independently of the at least one bus protocol chip;

linking the applications software and the driver module to one another by a link process;

obtaining program code as a result of the link process; and

storing the program code such that the program code is resident in said ROM;

wherein the driver module performs at least the following functions after linking to the applications software;

initializing at least one of bus protocol chip communications paths and the at least one bus protocol chip before start of a communication;

retrieving transmission data from at least one RAM address, loading the transmission data into a transmission register of the at least one bus protocol chip and causing the transmission data to be read out onto the bus; and

retrieving received data from a reception register of the at least one bus protocol chip and loading the received data into at least one predetermined memory location in the RAM of the microcomputer.

2. Method according to claim 1, wherein the driver module performs at least the following further functions after linking to the applications software;

constructing and administrating a waiting queue for transmission communications objects;

sending the transmission communication objects from the waiting queue in a priority basis; and

cancelling transmission jobs in an individual, selective manner before the transmission jobs are sent.

3. Method according to claim 1, further comprising providing at least one further module that is independent of the applications software and independent of the at least one bus protocol chip, and linking the at least one further module, together with at least one of the applications software and the driver module by a link process, in order to obtain the program code which can be stored in the ROM of the controller.

4. Method according to claim 1, wherein the driver module performs at least the following further function after linking to the applications software:

positioning received data from a reception register of the at least one bus protocol chip under a processing function, and loading the received data, processed in this manner, into at least one predetermined memory location in the RAM of the microcomputer of the motor vehicle controller.

5. Method according to claim 1, wherein the driver module performs at least the following further function after linking to the applications software:

changing the at least one bus protocol chip into a power-saving standby mode.