In-vehicle operating system, debugging system and method, electronic device and storage medium

The embedded BEOS operating system with a three-layer architecture addresses the limitations of bare metal programming in in-vehicle systems, enhancing maintainability, extensibility, and portability, and facilitating secure and efficient software development and debugging.

JP2024541174APending Publication Date: 2024-11-08BYD CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024516355
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-12-30
Filing Date
2022-12-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Conventional in-vehicle operating systems rely on bare metal programming of one-chip microcontrollers, leading to low maintainability, extensibility, and portability, with increasing intellectual property costs and software usage costs.

Method used

Implementing a uniquely developed embedded BEOS operating system with a three-layer architecture (hardware, software, and application layers) and a BEOS debugging system to enhance real-time performance, stability, and security.

Benefits of technology

The BEOS system provides superior code maintainability, program extensibility, and project portability, ensuring high system stability and execution efficiency, while enabling effective development, authentication, and maintenance of in-vehicle software.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024541174000001_ABST
    Figure 2024541174000001_ABST
Patent Text Reader

Abstract

The present invention provides an in-vehicle operating system, a debugging system and method, an electronic device, and a storage medium. The in-vehicle operating system includes a hardware layer, a software layer, and an application layer, the hardware layer includes at least one controller hardware each including a processor, the software layer includes a BEOS operating system and a BEOS driver, the BEOS operating system manages and controls the hardware and software resources of the computer system, the BEOS driver completes data transmission between the hardware layer and the software layer, and the application layer includes a plurality of application programs each providing an in-vehicle related application. By utilizing the independently developed embedded BEOS operating system, the in-vehicle operating system according to the present disclosure has higher real-time performance and stability, and is therefore safer. In addition, a corresponding BEOS debugging system is arranged in the in-vehicle operating system, which can better perform development, certification, debugging, maintenance, etc. of in-vehicle software.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This disclosure claims priority to a Chinese patent application with application number 202111663812.0, entitled "In-vehicle operating system, debugging system and method, electronic device and storage medium," filed on December 30, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to the field of in-vehicle technology, and in particular to an in-vehicle operating system, a debugging system and method, an electronic device, and a storage medium. [Background technology]

[0003] The framework design of traditional automotive operating systems is rough and single. For example, many automotive software applications use a single-chip microcomputer as a controller. Using the bare metal programming method of a single-chip microcomputer can reduce costs, but this development mode has major drawbacks. First, the code is not easily maintainable; second, the program is not easily scalable; and finally, the project is not easily portable. In addition, the world is increasingly attaching importance to intellectual property, and one day in the future, the software currently used for free may no longer be free, which indirectly increases the cost of use and increases the costs of automotive companies. Summary of the Invention

[0004] The in-vehicle operating system, debugging system and method, electronic device, and storage medium utilize an independently developed embedded BEOS operating system, which allows the in-vehicle operating system according to the embodiments of the present disclosure to have higher real-time performance, stability, and safety. In addition, the in-vehicle operating system is provided with a corresponding BEOS debugging system, which allows the in-vehicle software to be better developed, certified, debugged, maintained, etc., in the independently developed in-vehicle operating system.

[0005] In a first aspect, the present disclosure provides an in-vehicle operating system including a hardware layer, a software layer, and an application layer arranged in bottom-to-top order, the hardware layer including at least one controller hardware, each controller hardware including a processor; The software layer includes a BEOS operating system and a BEOS driver, the BEOS operating system manages and controls the hardware and software resources of the computer system, and the BEOS driver completes data transmission between the hardware layer and the software layer; The application layer is connected to the BEOS operating system via an operating system interface and includes a number of application programs, each of which provides an in-vehicle related application.

[0006] The in-vehicle operating system of the embodiment of the present disclosure utilizes the independently developed embedded BEOS operating system, thereby making the in-vehicle operating system of the embodiment of the present disclosure more real-time capable, more stable, and more secure.

[0007] In a second aspect, the BEOS debugging system of the present disclosure runs on a PC terminal to develop, certify, debug and maintain an in-vehicle operating system.

[0008] In the BEOS debug system of an embodiment of the present disclosure, a corresponding BEOS debug system is arranged in the in-vehicle operating system, so that the in-vehicle software can be better developed, certified, debugged, maintained, etc. in the independently developed in-vehicle operating system.

[0009] In a third aspect, a BEOS debugging method according to the present disclosure includes: The BEOS debug system sends a debug command to the in-vehicle operating system; The in-vehicle operating system debugs the target to be debugged based on the debug command; the target to be debugged is executed according to the debug command, and the execution result is fed back to the BEOS debug system; The BEOS debug system determines performance of the target to be debugged based on the execution result of the target to be debugged.

[0010] According to the BEOS debugging method of the embodiment of the present disclosure, a developer can print and view the program logic, the window program state, etc., through the BEOS debugging system, and perform corresponding adjustment tests.

[0011] In a fourth aspect, an electronic device according to the present disclosure includes a processor and a memory, wherein at least one instruction, at least one program, code set or instruction set is stored in the memory, and the instruction, program, code set or instruction set is loaded and executed by the processor to realize steps in a BEOS debugging method according to each embodiment of the present disclosure and steps in a task synchronization, communication and driver method in an in-vehicle operating system.

[0012] In a fifth aspect, a computer-readable storage medium according to the present disclosure stores one or more programs that, when executed by one or more processors, implement steps in the BEOS debugging method according to each embodiment of the present disclosure and steps in the task synchronization, communication and driver method in an in-vehicle operating system. [Brief description of the drawings]

[0013] Additional aspects and advantages of the present disclosure will become more apparent upon reading the detailed description of the non-limiting embodiments thereof, which are given with reference to the following drawings, in which:

[0014] [Figure 1] FIG. 2 is an architecture diagram of a combined in-vehicle operating system and BEOS debug system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a specific architecture diagram of a combination of the BEOS operating system and corresponding BEOS drivers according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 is a configuration diagram of a data perpetuation management module according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a task block diagram of an in-vehicle operating system according to an embodiment of the present disclosure. [Diagram 5] FIG. 2 is a task synchronization diagram of an in-vehicle operating system according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a task communication diagram of a first embodiment of an in-vehicle operating system according to an embodiment of the present disclosure. [Figure 7] FIG. 11 is a task communication diagram of a second embodiment of an in-vehicle operating system according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a BEOS driver diagram of an in-vehicle operating system according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is an exemplary diagram of a CAN driver according to an embodiment of the present disclosure. [Figure 10] FIG. 2 is a debug tool diagram of a BEOS debug system for debugging an in-vehicle operating system according to an embodiment of the present disclosure. [Figure 11] FIG. 1 is a configuration block diagram of an electronic device according to an embodiment of the present disclosure. [Figure 12] FIG. 2 is a configuration block diagram of a server according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The present disclosure will be described in detail below with reference to the drawings and examples. It should be understood that the specific examples described herein are merely for the purpose of illustrating the related invention, and are not intended to limit the invention. For the sake of convenience, the drawings only show parts related to the invention.

[0016] In addition, the embodiments and features of the embodiments of the present disclosure can be combined with each other as long as they are not inconsistent. Hereinafter, the present disclosure will be described in detail with reference to the drawings.

[0017] A conventional in-vehicle operating system includes a user space and a kernel space, the user space includes an application program module, a whitelist management module, a configuration management module, and an audit log generation module, and the kernel space includes a system call layer, an autonomous access control module, a mandatory access control module, a reliability measurement module, an application program load module, and a policy cache management module. The whitelist management module is connected to the application program module and the configuration management module, and the reliability measurement module can perform reliability measurement on the application program file so as to make the kernel space determine whether the application program can continue to be loaded. The conventional in-vehicle operating system only includes two parts, the user space and the kernel space, and the framework design of the in-vehicle system is rough and single, and there is no debugging system related to the development of the in-vehicle, and it has not been applied to the actual vehicle. The bare metal programming method of the one-chip microcomputer has many disadvantages such as poor code maintainability, poor program scalability, and poor project portability.

[0018] FIG. 1 is an exemplary configuration diagram of an in-vehicle operating system according to an embodiment of the present disclosure.

[0019] As shown in Fig. 1, in this embodiment, the in-vehicle operating system according to the present disclosure includes a hardware layer, a software layer, and an application layer, which are arranged from bottom to top. The hardware layer includes at least one controller hardware, each of which includes a processor; The software layer includes a BEOS operating system and a BEOS driver, the BEOS operating system manages and controls the hardware and software resources of the computer system, and the BEOS driver completes data transmission between the hardware layer and the software layer; The application layer is connected to the BEOS operating system via an operating system interface and includes a number of application programs, each of which provides an in-vehicle related application.

[0020] Specifically, the hardware layer provides hardware related to the vehicle and includes at least one controller hardware, each of which includes one processor, for example, a one-chip microcomputer. A plurality of application programs and a BEOS (Be Operating System) operating system are communicatively connected to each other via a portable operating system interface (POSIX). The POSIX (Portable Operating System Interface) standard defines an interface standard that an operating system should provide to an application program, and is a collective term for a series of API (Application Programming Interface) standards defined by the IEEE (Institute of Electrical and Electronics Engineers) for software that runs on various UNIX (Uniplexed Information and Computering System, UNIX operating system) (UNIX is a registered trademark).In response to the deficiencies of the bare metal programming method of the one-chip microcomputer in the conventional in-vehicle system, the in-vehicle operating system of this embodiment utilizes a combination method of the independently developed embedded BEOS operating system and the one-chip microcomputer, the BEOS operating system runs on hardware such as multiple one-chip microcomputers, the one-chip microcomputer develops the in-vehicle software, the BEOS operating system is a computer program that manages and controls the hardware and software resources of the computer system, and is also the kernel and baselight of the computer system, the BEOS operating system can handle basic transactions such as memory management and allocation, prioritization of system resource supply and demand, control of input / output devices, network operation, and file system management, and can provide an operating interface for users to interact with the system. The BEOS operating system has excellent code maintainability, program extensibility, and project portability, and is also low cost.

[0021] In addition, the BEOS operating system of the embodiment of the present disclosure can realize full graphics, has high system stability and execution efficiency, can support 64-bit file systems and multi-processors, and integrates powerful multimedia software. BEOS allows multiple audio, video, image, and network-based application software to operate simultaneously, memory and processors are always kept in the most stable running state, and the quality of multimedia does not change. BEOS also has complete network functions and comprehensive network software.

[0022] 2 is a static block diagram of an in-vehicle operating system. As shown in FIG. 2, in the embodiment of the present disclosure, the BEOS operating system includes a task layer, an intermediate protocol stack layer, and an OS Kernel (Operating System Kernel) layer, which are arranged from top to bottom.

[0023] Specifically, as shown in FIG. 2, the task layer includes a work task module and a system monitoring task module, and the work task module includes at least one main task unit, each of which is communicatively connected to at least one sub-task unit.

[0024] The intermediate protocol stack layer includes at least one of a file system module, a TCP / IP protocol module, a Bluetooth protocol stack module (Bluetooth is a registered trademark), a signal management module, a network management module, a CAN service module, and a data persistence management module.

[0025] The OS kernel layer includes at least one of a task management module, a task communication module, a memory management module, a memory run-time library module, a timer management module, a synchronization management module, and an interrupt management module.

[0026] Specifically, the intermediate protocol stack layer provides various services for the in-vehicle operating system, and each module provides a file system, a TCP / IP (Transmission Control Protocol / Internet Protocol) protocol, a Bluetooth protocol stack (Bluetooth is a registered trademark), signal management, network management, a CAN (Controller Area Network) service, and data persistence management, etc. accordingly. A file system is a method and data structure for an operating system to clarify files on a magnetic disk or partition, that is, a method of organizing files on a magnetic disk. A file system refers to a type of magnetic disk or partition that stores files, or a file system, and a software mechanism in an operating system that is responsible for managing and storing file information is called a file management system, or abbreviated as a file system. TCP / IP refers to a protocol cluster that can realize information transmission between multiple different networks, and consists of an IP protocol in the network layer and a TCP protocol in the transmission layer. The Bluetooth protocol specification (Bluetooth is a registered trademark) aims to make applications that comply with the specification work together. The CAN service management is responsible for realizing network management services and coordinating the switching between awake and sleep states of the CAN network.

[0027] The network management module consists of four modules: ComM (Communication Manager), general-purpose network manager interface, bus-related network manager, and bus-related state manager. In the development process of automotive electronic ECUs (Electronic Control Units), the network management module reduces power consumption, and various communication buses select whether to sleep or operate normally according to their functions in specific situations. By distinguishing different communication bus structures, communication between specific ECUs for specific functions is realized, and ECUs that do not need to participate in the function can go into sleep, thereby reducing energy loss. The network management module coordinates the sleep and awake of the entire vehicle, etc.

[0028] During the development process of domain controller applications and services, each service and application needs to store data persistently. Data persistence management simplifies the programming of data storage by services and applications and provides a unified data storage API for services and applications. As shown in Figure 3, data persistence management includes the following functions: 1) API interface: Realizes API interfaces of KEY-VALUE type and file type, including write interface and read interface. 2) Data verification and master / slave backup: System development design engineers write a configuration file (XML format) to the master / slave backup path through the configuration tool, and the data persistence storage management is responsible for adding the data to be written by the application or service to the verification code (KEY-VALUE type data) and storing them in the master / slave backup area in a lump. 3) Data verification and restoration: When an application or service reads KEY-VALUE data through the read interface, the data persistence storage management reads the data and the corresponding verification code together, verifies the data, and if the verification fails, the data in the backup area needs to be read and restored after verification, and if the data in the backup area also fails to be verified, returns an error code to the caller. 4) Application Data Separation: Each service and application data is stored separately, and one application and service is stored in one KEY-VALUE type file according to the application name and service name.

[0029] Each module in the OS kernel layer provides task management, inter-task communication mechanism, memory management and runtime library, timer management, synchronization management, and interrupt management, etc. Task management is mainly responsible for creating / deleting and scheduling user tasks. Inter-task communication is responsible for synchronization between tasks and data transmission between tasks, for example, multiple subtasks may send different messages to a message queue of one subtask, and one subtask may send different messages to a message queue of different subtasks. Memory management is responsible for allocating, collecting, and managing built-in memory. Timer management is responsible for users to execute user-defined functional functions within a given time, and timer services provide software timers for application programs and basic software. Synchronization management means that in one task, there may be auxiliary relationships between several subtasks. That is, one subtask needs to wait until another subtask completes a certain event before continuing, which involves synchronization issues between subtasks, as shown in Figure 5. The interrupt management is mainly responsible for setting the user interrupt function, and can immediately execute the interrupt function set by the user after an interrupt occurs in the hardware, or can accurately handle abnormalities in the hardware after they occur. The system monitoring task unit in the task layer monitors the computer system in real time.

[0030] In one embodiment, the main task unit provides resource centralization management and sub-task unit management; The centralized resource management includes at least one of a timer, a message queue, a semaphore, a wait list, and application and release of a hardware resource; The subtask unit management includes at least one of subtask creation, subtask deletion, subtask state control, and subtask state monitoring.

[0031] FIG. 4 is a task block diagram of the in-vehicle operating system.

[0032] As shown in Figure 4, each project work in the in-vehicle operating system disclosed herein is defined as one main task and several subtasks, the main task functions are resource centralized management and subtask management, the main task can determine the order and mutually exclusive relationship of the creation / deletion of subtasks according to the needs of the project, and the resource centralized management includes application and release of related resources such as timers, message queues, semaphores, wait lists, hardware, etc. The subtask management mainly includes subtask creation / deletion, subtask state control, and subtask state monitoring and inspection.

[0033] FIG. 5 is a task synchronization diagram of an in-vehicle operating system.

[0034] As shown in Figure 5, in one task, there may be a subsidiary relationship between some subtasks, i.e., one subtask needs to wait for another subtask to complete a certain event before continuing, which involves the synchronization problem between subtasks.

[0035] For example, an information station includes two subtasks, one of which is a module command sending subtask such as 3G / 4G / 5G, and the other is a data receiving subtask. After sending a command to the device (referring to the timer, task manager, memory management, etc. in the OS kernel of the BEOS operating system), the sending subtask needs to wait for the serial port data receiving subtask to return the command execution result status before continuing execution.

[0036] Specifically, the task synchronization method of the in-vehicle operating system disclosed herein includes the following steps.

[0037] In S101, one synchronization event is defined.

[0038] In S102, after the command transmission subtask transmits a command, the command transmission subtask waits for the serial port data reception subtask to complete the event by using WaitEvent (event name).

[0039] In S103, after the serial port data reception subtask receives and analyzes the serial port data, the event is completed and then a task waiting for the event is started by Wakeup (event name).

[0040] In S104, the two subtasks are continuously executed.

[0041] FIG. 6 is a task communication diagram of the first embodiment of the in-vehicle operating system.

[0042] As shown in FIG. 6, when a subtask has data that needs to be sent to the next subtask, it can be sent through a message queue, for example, multiple subtasks can send different message queues to the message queue of a subtask, which specifically includes the following substeps:

[0043] In S201, the main task creates a message queue to be used by the subtask using CreateMQ().

[0044] In S202, each of the subtasks of the messages to be sent provides SendMsg() via the underlying OS kernel to send the message data to the message queue.

[0045] In S203, the subtask of the message to be received receives the message data from the message queue by ReceiveMsg( ).

[0046] Also, for example, Fig. 7 is a task communication diagram of the second embodiment of the in-vehicle operating system. As shown in Fig. 7, one subtask sends different message queues to message queues of different subtasks, and specifically includes the following substeps S301 to S303.

[0047] In S301, the main task creates multiple message queues to be used by the subtasks using CreateMQ().

[0048] In S302, each subtask of a message to be sent provides SendMsg() via the underlying OS kernel to send message data to multiple message queues.

[0049] In S303, the subtasks of the multiple messages to be received receive message data from the corresponding message queues by ReceiveMsg( ).

[0050] In order to ensure the accuracy of message data and make the best use of resources, the subtask designed by the in-vehicle operating system disclosed herein processes messages as follows: periodically inquire whether a message has arrived in the message queue; if there is a message in the message queue, retrieve the message from the message queue, process the message according to the protocol defined by each application, and then continue to process the message; if there is no message in the message queue, the subtask sleeps and waits, and when a message arrives in another task, it will be awakened and process the message.

[0051] In one embodiment, the BEOS drivers include at least one of a serial port driver, a CAN driver, a SPI driver, a Flash driver, an I2C driver, and an RTC driver.

[0052] Specifically, referring to the static block diagram of the in-vehicle operating system shown in FIG. 2, the BEOS driver in FIG. 1 corresponds to the device driver interface in FIG. 2, and the BEOS driver includes a serial port driver, a CAN driver, an SPI (Serial Peripheral interface, serial peripheral interface) driver, a Flash (Flash EEPROM, flash memory) driver, an I2C (Inter-Integrated Circuit, I2C bus) driver, and an RTC (Real_Time Clock, real-time clock) driver. FIG. 8 is a driver diagram of the in-vehicle operating system. As shown in FIG. 8, each driver in the BEOS driver includes the following four parts: 1) Driver interface: A task realizes data exchange with hardware through the driver interface, and different hardware does not change the driver interface. 2) Intermediate logic layer: a) Logic control is to process the content related to the protocol / specification, such as CAN classification processing, data verification, b) Synchronization control is to perform synchronization control when multiple tasks access the hardware at the same time, and c) Buffer management is to perform buffer management for the data generated by the device to prevent data overflow. 3) Hardware Interface: The driver realizes operations on the hardware through the hardware interface, and the hardware interface is related to the platform. 4) Driver and other assemblies: For example, timers, synchronization, communication, etc.

[0053] Taking the CAN driver as an example, CAN is the abbreviation for Controller Area Network, which was developed by the German company BOSCH, which is famous for its research, development and production of automotive electronic products. It eventually became an international standard (ISO 11898) and is one of the most widely applied field buses in the world. Figure 9 is an example diagram of a CAN driver in an in-vehicle operating system. As shown in Figure 9, the CAN driver is a shared device, and is designed to allow multiple tasks to read and write CAN simultaneously. The prerequisite is that InitCan() is called at the initialization of the platform to initialize the CAN hardware, register the CAN interrupt service program, and create a data transmission timer.

[0054] Through the CAN driver interface, execute OpenCan(Can Id) to open, WriteCan(CanHandle, Type, Data, Len) to write, ReadCan(CanHandle, Data, Len) to read, CloseCan(CanHandle), and SetCan(CanHandle, Type, Data) to set and adjust the buffer size, cancel CAN data transmission, etc., and execute GetCan(CanHandle, Type, Data) and ResetCan(CanHandle).

[0055] The read and write logic control performs reads ReadCan and writes WriteCan.

[0056] The hardware interface executes the _WriteCan and Can interrupt service programs.

[0057] For example, in the data transmission between the application task and the CAN driver interface, the WriteCan in the CAN driver interface is first classified by logic control into three events, three event periods + once every two seconds, one period per second, one trigger, etc., and then transmitted to the CAN hardware through timer management, write protection, and write register, and then transmitted to the CAN interrupt service program, and entered into the CAN buffer through data application, search / insertion in the CAN buffer management, and finally executed ReadCan.

[0058] The in-vehicle operating system in the prior art is merely an interface between the user and the in-vehicle hardware, and is also an interface between the in-vehicle hardware and the upper layer software, while the in-vehicle operating system according to the present disclosure includes three layers, namely, a hardware layer, a software layer, and an application layer, and the design of the three layers makes it easier to maintain and develop in-vehicle application software, and the three layers each play their own role, so that the in-vehicle operating system has higher real-time performance, higher stability, and higher safety. The in-vehicle operating system according to the present disclosure is introduced in more detail about the implementation method and specific implementation process, and has been actually applied to automobiles.

[0059] As shown in FIG. 1, a BEOS debugging system according to another embodiment of the present disclosure runs on a PC terminal and develops, certifies, debugs, and maintains an in-vehicle operating system.

[0060] Specifically, the in-vehicle operating system according to the embodiment of the present disclosure includes a corresponding BEOS debug system, and when developing in-vehicle software in the in-vehicle operating system, the BEOS debug system can more effectively perform development, certification, debugging, maintenance, etc., so that the in-vehicle software can be better developed and debugged in the independently developed in-vehicle operating system. The in-vehicle operating system according to the embodiment of the present disclosure may be directly applied to automobiles, or may be opened up to third parties such as individuals, departments, manufacturers, etc., to develop in-vehicle-related software in the in-vehicle operating system.

[0061] FIG. 10 is a tool diagram of the BEOS debugging system for debugging the in-vehicle operating system.

[0062] As shown in Figure 10, the BEOS debugging system runs on a personal computer (PC) terminal and is divided into four functional modules, specifically including a communication protocol processing module, a source code processing module, a debug element analysis module, and a user operation interface module.

[0063] The communication protocol processing module provides communication data processing for the BEOS debug system running on the PC terminal and the BEOS operating system running on the one-chip microcomputer. The source code processing module provides functions such as source code data structure analysis, source code display, and source code location. Source code data structure analysis is for analyzing the data structure of the code. Source code display is for displaying the source code of programmed code. Source code location is for directly locating to the definition points of functions, variables, structures, parameters, etc. required for search.

[0064] The debug element analysis module provides variable display functions necessary for debugging, such as register display, global variable display, local variable display, stack information display, and function call order display, allowing developers to grasp the program execution status, hardware driver status, and software execution status in real time, and to make timely adjustments and corrections when errors occur.

[0065] The user operation interface module (GUI, Graphical User Interface) provides a user operation interface, which is an intermediary for interaction and communication between a user and the hardware and software. Through the user operation interface, a user sends instructions to the software to perform a specific function, and the software executes the instructions through the hardware and other software, and returns the execution result to the user in the form of characters or graphics.

[0066] The source code compilation function of the in-vehicle operating system of the present disclosure consists of three parts: source code compilation, compilation information window, and error definition.

[0067] The software programming of the in-vehicle operating system disclosed herein can call a programming tool to program source code, and can also generate an official release version based on the source code to perform programming upgrades, etc.

[0068] The debugging of the in-vehicle operating system of the present disclosure includes four parts: registers, local variables, global variables, and task states, so as to allow program developers to easily develop in-vehicle applications.

[0069] The scope of application of the in-vehicle operating system according to the present disclosure is not limited to the development of automobile applications, and the in-vehicle operating system may also be applied to the development of related application software for future autonomous driving, drone development, airplanes, ships, etc.

[0070] As a further aspect, a BEOS debugging method according to an embodiment of the present disclosure includes: The BEOS debug system sends a debug command to the in-vehicle operating system; The in-vehicle operating system debugs the target to be debugged according to the debug command; a step of executing the target to be debugged based on the debug command and feeding back the execution result to the BEOS debug system; The BEOS debug system includes a step of determining performance of the target to be debugged based on the execution result of the target to be debugged.

[0071] For example, after the controller is installed in the vehicle, the controller does not run according to the designed mode, such as the window step is incorrect, and the window is originally designed to be fully raised, but as a result it is only raised halfway. The developer can print and view the program logic, window program status, etc. through the BEOS debug system, and make corresponding adjustments and tests.

[0072] Based on the above embodiment, Fig. 11 is a configuration block diagram of an electronic device according to an embodiment of the present disclosure. As shown in Fig. 11, the electronic device 401 includes a processor 4011 and a memory 4012, and the processor 4011 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 4011 may be implemented using at least one hardware form of a digital signal processing (DSP), a field programmable gate array (FPGA), or a programmable logic array (PLA).

[0073] The processor 4011 may include a main processor and a coprocessor, where the main processor is a processor that processes data in an awake state and is also called a Central Processing Unit (CPU), and the coprocessor is a low-power processor that processes data in a standby state.

[0074] The processor 4011 may also include a graphics processing unit (GPU), which performs rendering and drawing for content that needs to be displayed on a display screen. In some embodiments, the processor 4011 may further include an artificial intelligence (AI) processor, which processes computational operations related to machine learning.

[0075] The memory 4012 may include one or more computer readable storage media, which may be non-transitory. The memory 4012 may further include high speed random access memory and non-volatile memory, such as one or more magnetic disk storage electronics, flash memory storage electronics. In some embodiments, the non-transitory computer readable storage media in the memory 4012 stores at least one instruction that is executed by the processor 4011 to implement a document display method according to a method embodiment of the present disclosure.

[0076] In some embodiments, the electronic device 401 may further include a peripheral electronics interface 4013 and at least one peripheral electronic device. The processor 4011, the memory 4012, and the peripheral electronics interface 4013 may be connected via a bus or signal lines. Each peripheral electronic device may be connected to the peripheral electronics interface 4013 via a bus, signal lines, or a circuit board.

[0077] Specifically, the peripheral electronics include, but are not limited to, a radio frequency circuit 4014, a touch panel display 4015, and a power source 4016. The peripheral electronics interface 4013 may connect at least one peripheral electronics for input / output (I / O) to the processor 4011 and the memory 4012. In some embodiments, the processor 4011, the memory 4012, and the peripheral electronics interface 4013 are integrated on the same chip or circuit board, and in some other embodiments, any one or two of the processor 4011, the memory 4012, and the peripheral electronics interface 4013 may be implemented on a single chip or circuit board, and the embodiments of the present disclosure are not limited thereto.

[0078] The radio frequency circuit 4014 transmits and receives radio frequency (RF) signals, also called electromagnetic signals. The radio frequency circuit 4014 communicates with communication networks and other communication electronic devices via electromagnetic signals. The radio frequency circuit 4014 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. Optionally, the radio frequency circuit 4014 includes an antenna system, an RF transceiver, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, user identity module cards, and the like. The radio frequency circuit 4014 can communicate with other electronic devices through at least one wireless communication protocol, including, but not limited to, metropolitan area networks, each generation mobile communication network (2G, 3G, 4G, and 5G), wireless local area networks, and / or Wireless Fidelity (WiFi) networks. In some embodiments, the radio frequency circuit 4014 may further include circuitry related to Near Field Communication (NFC).

[0079] The touch panel display 4015 displays a user interface (UI). The UI may include graphics, text, icons, videos, and any combination thereof. If the touch panel display 4015 is a touch panel display, the touch panel display 4015 is further capable of collecting touch signals on or above the surface of the touch panel display 4015. The touch signals may be input as control signals to the processor 4011 for processing. In this case, the touch panel display 4015 may provide virtual buttons and / or a virtual keyboard, also called soft buttons and / or a soft keyboard. In some embodiments, the touch panel display 4015 may be one and is mounted on the front panel of the electronic device 401, in other embodiments, the touch panel display 4015 may be at least two and is mounted on different surfaces of the electronic device 401 or arranged in a folding design, and in further embodiments, the touch panel display 4015 may be a flexible display and is mounted on a curved or folded surface of the electronic device 401. Additionally, the touch panel display 4015 may be implemented as a non-rectangular, irregularly shaped, i.e., irregular screen. The touch panel display 4015 may be fabricated from materials such as Liquid Crystal Display (LCD), Organic Light-Emitting Diode (OLED), and the like.

[0080] As one skilled in the art will appreciate, the structure shown in FIG. 11 is not intended to limit electronic device 401, which may include more or fewer components than shown, may combine several components, and may be arranged using different assemblies.

[0081] In this embodiment, the electronic device 401 further includes one or more programs stored in the memory 4012 and executed by the one or more processors 4011, the one or more programs including instructions for performing task synchronization, communication and driver methods, and BEOS debugging methods in an in-vehicle operating system executed by the electronic device according to an embodiment of the present disclosure.

[0082] Based on the above embodiment, FIG. 12 is a configuration block diagram of a server according to an embodiment of the present disclosure. As shown in FIG. 12, the server 402 may have relatively large differences due to different arrangements or performances, and may include one or more central processing units (CPUs) 4021 (e.g., one or more processors), a memory 4022, and one or more storage media 4025 (e.g., one or more mass storage electronic devices) that store application programs 4023 or data 4024. Here, the memory 4022 and the storage medium 4025 may be temporary storage devices or permanent storage devices. The program stored in the storage medium 4025 may include one or more modules (not shown), each of which may include a series of instruction operations for a computer system. The central processing unit 4021 may be configured to communicate with the storage medium 4025 and execute the series of instruction operations in the storage medium 4025 on the server 402.

[0083] The server 402 may include one or more power sources 4026, one or more wired or wireless network interfaces 4027, one or more input / output interfaces 4028, and / or one or more operating systems 4029, such as BEOS, Windows Server 2003, or the like. TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM It may further include the following.

[0084] In another aspect, a computer-readable storage medium according to an embodiment of the present disclosure stores program code for executing any of the embodiments of the task synchronization, communication and driver method in an in-vehicle operating system and the BEOS debugging method of each of the above-mentioned embodiments.

[0085] In a further aspect, a computer program product including instructions according to an embodiment of the present disclosure, when executed on a computer, causes the computer to perform any of the embodiments of the task synchronization, communication and driver method in an in-vehicle operating system and the BEOS debugging method of each of the preceding embodiments.

[0086] For the sake of convenience and conciseness, so that those skilled in the art can clearly understand, the specific operating processes of the above-mentioned systems, devices, and modules may refer to the corresponding processes in the above-mentioned method embodiments, and the description thereof will be omitted here.

[0087] It should be understood that in some embodiments of the present disclosure, the disclosed system, device, and method may be realized in other ways. For example, the device embodiments described above are merely illustrative, and the division of modules is merely a logical division of functions, and there may be other division methods when actually realized, for example, multiple modules or components may be combined or integrated into another system, and some features may be ignored or not implemented. In addition, the mutual coupling, direct coupling, or communication connection shown or discussed may be realized by some interfaces, and the indirect coupling or communication connection of devices or modules may be electrical, mechanical, or other forms. Modules described as separate members may or may not be physically separated, and members displayed as modules may or may not be physical units, i.e., they may be located in the same place or distributed in multiple network units. Some or all of the modules may be selected according to actual needs to achieve the effects of the technical means of the present embodiment.

[0088] In addition, each functional module in each embodiment of the present disclosure may be integrated into one processing unit, each module may exist physically alone, or two or more units may be integrated into one module. The integrated units may be realized in the form of hardware or in the form of a software functional unit. The integrated units may be realized in the form of a software functional unit and stored in one computer-readable storage medium when sold or used as an independent product.

[0089] Based on such understanding, the part of the technical means of the present disclosure that contributes to the prior art, or all or a part of the technical means may be realized in the form of a software product, and the computer software product is stored in a storage medium and includes some instructions for causing one computer electronic device (which may be a personal computer, a server, or a network electronic device, etc.) to execute all or a part of the steps of the information reporting method in each embodiment of the present disclosure. The aforementioned storage medium includes various media capable of storing program codes, such as a USB memory, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0090] It should be noted that the above examples are merely for explaining the technical means of the present disclosure and are not intended to limit the same. Although the present disclosure has been described in detail with reference to the above examples, a person skilled in the art may still modify the technical means described in each of the above examples or equivalently replace part of the technical features thereof, and such modifications or replacements of the corresponding technical means do not deviate from the spirit and scope of the technical means of each of the embodiments of the present disclosure.

Claims

1. The system includes a hardware layer, a software layer, and an application layer, which are arranged in order from bottom to top, and the hardware layer includes at least one controller hardware, each of which includes one processor; The software layer includes a BEOS operating system and a BEOS driver, the BEOS operating system manages and controls the hardware and software resources of the computer system, and the BEOS driver completes data transmission between the hardware layer and the software layer; The application layer is connected to the BEOS operating system via an operating system interface and includes a plurality of application programs each of which provides an application related to an in-vehicle device.

2. The BEOS operating system includes a task layer, an intermediate protocol stack layer, and an OS kernel layer, which are arranged in order from top to bottom; 2. The in-vehicle operating system of claim 1, wherein the BEOS drivers include at least one of a serial port driver, a CAN driver, an SPI driver, a Flash driver, an I2C driver, and an RTC driver.

3. The in-vehicle operating system of claim 2 , wherein the intermediate protocol stack layer includes at least one of a network management module, a CAN service module, and a data persistence management module.

4. 4. The in-vehicle operating system according to claim 2 or 3, wherein the intermediate protocol stack layer further includes at least one of a file system module, a TCP / IP protocol module, a Bluetooth protocol stack module (Bluetooth is a registered trademark), and a signal management module.

5. The in-vehicle operating system according to any one of claims 2 to 4, characterized in that the OS kernel layer includes at least one of a task management module, a task communication module, a memory management module, a memory runtime library module, a timer management module, a synchronization management module, and an interrupt management module.

6. The in-vehicle operating system according to any one of claims 2 to 5, characterized in that the task layer includes an operation task module and a system monitoring task module, and the operation task module includes at least one main task unit, each of which is communicatively connected to at least one sub-task unit.

7. The main task unit provides resource centralized management and subtask unit management, and the resource centralized management includes at least one of a timer, a message queue, a semaphore, a wait list, and application and release of a hardware resource; The in-vehicle operating system of claim 6 , wherein the subtask unit management includes at least one of subtask creation, subtask deletion, subtask state control, and subtask state monitoring.

8. The task communication method in the work task module includes: A step in which the main task creates a message queue to be used by the subtask using CreateMQ(); Each of at least one subtask of a message to be sent sends message data to the message queue by SendMsg(); 8. The in-vehicle operating system according to claim 6, further comprising a step of: receiving message data from the message queue by at least one subtask of a message to be received using ReceiveMsg( ).

9. A BEOS debugging system, which is executed on a PC terminal and develops, certifies, debugs and maintains an in-vehicle operating system according to any one of claims 1 to 8.

10. The system includes a communication protocol processing module, a source code processing module, a debug element analysis module, and a user operation interface module; The communication protocol processing module provides communication data processing between the BEOS debugging system and the BEOS operating system; The source code processing module provides functions of source code data structure analysis, source code display, and source code location; The Debug Element Analysis module provides a variable display function required for debugging.

10. The BEOS debugging system of claim 9, wherein the user operation interface module provides a user operation interface.

11. the BEOS debug system sending a debug command to the in-vehicle operating system; The in-vehicle operating system debugs the target to be debugged based on the debug command; the target to be debugged is executed according to the debug command, and the execution result is fed back to the BEOS debug system; the BEOS debugging system determining performance of the target to be debugged based on an execution result of the target to be debugged.

12. 12. An electronic device comprising: a processor; and a memory, wherein the memory stores at least one instruction, at least one program, code set, or instruction set, and wherein the instruction, program, code set, or instruction set is loaded and executed by the processor to realize the steps of the task communication method recited in claim 8 and the steps of the BEOS debugging method recited in claim 11.

13. A computer-readable storage medium having stored thereon one or more programs that, when executed by one or more processors, implement the steps of the task communication method recited in claim 8 and the steps of the BEOS debugging method recited in claim 11.

Citation Information

Patent Citations

  • Vehicle-mounted software development platform

    CN113821247A

  • Vehicle control program and program generation method, program generator, and automobile controller

    JP2009080566A

  • Highly flexible metadata synthesis

    JP2014526727A