Data interaction methods, devices, equipment, and media between FSI and SOC
By sharing a memory region between the FSI and the SOC for data interaction, the problems of hardware redundancy, functional safety limitations, and high cost in cross-functional safety island and SOC module communication of XCP technology are solved. This achieves efficient and secure XCP communication, meets functional safety requirements, and improves system compatibility and reliability.
Patent Information
- Application Number
- CN202510553776.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-29
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2045-04-29
AI Technical Summary
Existing XCP technology suffers from hardware redundancy, functional safety limitations, insufficient real-time performance, and high costs when communicating with SOC modules across functional safety islands. In particular, the data acquisition rate is limited in high-bandwidth, low-latency scenarios, and the diversified communication methods increase system complexity and security risks.
By sharing a memory region between the FSI and the SOC, and using the preset shared memory region for data interaction, external access to the FSI hardware link is avoided, achieving efficient XCP communication with cross-hardware compatibility and scalability. The shared memory mechanism is used for data interaction to meet functional safety requirements, and security is improved through encryption schemes.
It achieves functional safety requirements without adding new hardware communication interfaces, improves the real-time performance and reliability of XCP communication, reduces costs, enhances system compatibility and security, and adapts to the challenges of diversified communication methods.
Smart Images

Figure CN120614144B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle communication technology, and in particular to a data interaction method, apparatus, device and medium between FSI (Functional Safety Island) and SOC (System on Chip). Background Technology
[0002] XCP (Universal Measurement and Calibration Protocol) is a core protocol in the automotive electronics field, developed by ASAM (Association for Standardization of Automation and Measuring Systems). It is primarily used for parameter calibration and real-time data acquisition of ECUs (Electronic Control Units). This protocol supports dynamic monitoring and parameter adjustment of ECUs during development, testing, and mass production, and is one of the key technologies for software-defined vehicles. XCP includes two core functions: calibration and measurement. It serves as the crucial link between "software algorithms" and "hardware control" in automotive electronics development, significantly improving the development efficiency and flexibility of ECUs through standardized measurement and calibration mechanisms. With the development of automotive electrification and intelligence, the importance of XCP in high-bandwidth, low-latency scenarios (such as Ethernet domain controllers and functional safety systems) is becoming increasingly prominent.
[0003] However, most existing XCP functions rely on CAN or CANFD buses, which affects the DAQ data acquisition rate. Furthermore, the diverse communication methods used by different controllers require the host computer to have multiple interface adaptation capabilities, increasing hardware costs and security risks, and reducing system reliability and maintainability, all of which urgently need to be addressed. Summary of the Invention
[0004] This application provides a data interaction method, apparatus, device, and medium between FSI and SOC to solve the problems of hardware redundancy, functional safety limitations, insufficient real-time performance, and high cost in existing XCP technology when communicating with SOC modules across functional safety islands. It achieves efficient XCP communication between FSI and SOC modules through a shared memory mechanism, avoids external access to FSI hardware links, meets functional safety requirements, improves cross-hardware compatibility and scalability, and has high security and reliability.
[0005] The first aspect of this application provides a data interaction method between an FSI and a SOC, including the following steps:
[0006] Determine whether the current XCP_Link module has received a request message sent by the host computer;
[0007] If the current XCP_Link module receives the request message, then the type of the request message is determined;
[0008] Based on a preset shared memory region, data interaction between FSI and SOC is performed according to the type of the request message.
[0009] According to one embodiment of this application, when the type of the request message is an observation message, the step of performing data interaction between FSI and SOC based on a preset shared memory region and according to the type of the request message includes:
[0010] The observation message is parsed to obtain the observation data;
[0011] Determine whether the observed data is FSI data;
[0012] If the observed data is the FSI data, then access the preset shared memory area and read the first observed value corresponding to the FSI data;
[0013] The first observed value is written into the first reply message, and the first reply message is sent to the host computer.
[0014] According to one embodiment of this application, after determining whether the observed data is FSI data, the method further includes:
[0015] If the observed data is not the FSI data, then based on the observed data, the module to be accessed in the SOC is determined;
[0016] Obtain the second observation value from the module to be accessed, write the second observation value into the second reply message, and send the second reply message to the host computer.
[0017] According to one embodiment of this application, when the type of the request message is a labeling message, the step of performing data interaction between FSI and SOC based on a preset shared memory region and according to the type of the request message includes:
[0018] The calibration message is parsed to obtain calibration data, which includes a first calibration value.
[0019] Determine whether the calibration data is FSI data;
[0020] If the calibration data is the FSI data, then the first calibration value is written into the preset shared memory area, and the first address corresponding to the first calibration value is read in reverse to obtain the first reverse read value. The first reverse read value is written into the third reply message, and the third reply message is sent to the host computer.
[0021] According to one embodiment of this application, after determining whether the calibration data is FSI data, the method further includes:
[0022] If the calibration data is not the FSI data, then the calibration value is updated, and the second address corresponding to the updated calibration value is read in reverse to obtain the second reverse read value. The second reverse read value is written into the fourth reply message, and the fourth reply message is sent to the host computer.
[0023] According to one embodiment of this application, the current XCP_Link module is integrated on the SOC side.
[0024] According to the data interaction method between FSI and SOC in this application embodiment, when the current XCP_Link module receives a request message sent by the host computer, the type of the request message is determined; based on a preset shared memory area, data interaction between FSI and SOC is performed according to the type of the request message. This solves the problems of hardware redundancy, functional safety limitations, insufficient real-time performance, and high cost in existing XCP technologies when communicating across functional safety islands and SOC modules. It achieves efficient XCP communication between FSI and SOC modules through a shared memory mechanism, avoiding external access to the FSI hardware link, meeting functional safety requirements, improving cross-hardware compatibility and scalability, and possessing high security and reliability.
[0025] A second aspect of this application provides a data interaction device between an FSI and a SOC, comprising:
[0026] The judgment module is used to determine whether the current XCP_Link module has received a request message sent by the host computer;
[0027] The determination module is used to determine the type of the request message if the current XCP_Link module receives the request message;
[0028] The data interaction module is used to perform data interaction between FSI and SOC based on a preset shared memory area and according to the type of the request message.
[0029] According to one embodiment of this application, when the type of the request message is an observation message, the data interaction module is configured to:
[0030] The observation message is parsed to obtain the observation data;
[0031] Determine whether the observed data is FSI data;
[0032] If the observed data is the FSI data, then access the preset shared memory area and read the first observed value corresponding to the FSI data;
[0033] The first observed value is written into the first reply message, and the first reply message is sent to the host computer.
[0034] According to one embodiment of this application, after determining whether the observed data is FSI data, the data interaction module is further configured to:
[0035] If the observed data is not the FSI data, then based on the observed data, the module to be accessed in the SOC is determined;
[0036] Obtain the second observation value from the module to be accessed, write the second observation value into the second reply message, and send the second reply message to the host computer.
[0037] According to one embodiment of this application, when the type of the request message is a calibration message, the data interaction module is configured to:
[0038] The calibration message is parsed to obtain calibration data, which includes a first calibration value.
[0039] Determine whether the calibration data is FSI data;
[0040] If the calibration data is the FSI data, then the first calibration value is written into the preset shared memory area, and the first address corresponding to the first calibration value is read in reverse to obtain the first reverse read value. The first reverse read value is written into the third reply message, and the third reply message is sent to the host computer.
[0041] According to one embodiment of this application, after determining whether the calibration data is FSI data, the data interaction module is further configured to:
[0042] If the calibration data is not the FSI data, then the calibration value is updated, and the second address corresponding to the updated calibration value is read in reverse to obtain the second reverse read value. The second reverse read value is written into the fourth reply message, and the fourth reply message is sent to the host computer.
[0043] According to one embodiment of this application, the current XCP_Link module is integrated on the SOC side.
[0044] According to the data interaction device between FSI and SOC in this application embodiment, when the current XCP_Link module receives a request message sent by the host computer, it determines the type of the request message; based on a preset shared memory area, it performs data interaction between FSI and SOC according to the type of the request message. This solves the problems of hardware redundancy, functional safety limitations, insufficient real-time performance, and high cost in existing XCP technologies when communicating across functional safety islands and SOC modules. It achieves efficient XCP communication between FSI and SOC modules through a shared memory mechanism, avoiding external access to the FSI hardware link, meeting functional safety requirements, improving cross-hardware compatibility and scalability, and possessing high security and reliability.
[0045] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the data interaction method between FSI and SOC as described in the above embodiments.
[0046] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the data interaction method between FSI and SOC as described in the above embodiments.
[0047] The beneficial effects of this application are:
[0048] (1) Traditional XCP solutions, whether using CANFD, Ethernet, or SPI (Serial Peripheral Interface), all rely on hardware interfaces. For controllers with certain functional safety requirements, or controllers without external communication requirements, implementing XCP functionality requires adding corresponding hardware communication interfaces, resulting in wasted resources, increased costs, and security risks. This application achieves XCP functionality without adding additional hardware communication interfaces by sharing a memory area between the FSI and the SOC.
[0049] (2) In traditional XCP solutions, each individual controller needs to integrate a separate XCP protocol stack, and the XCP host computer needs to connect to multiple nodes during use. This application provides a cross-hardware XCP solution that can implement XCP functionality with a single node.
[0050] (3) Current XCP data transmission cannot meet the increasingly stringent security requirements. This application is scalable and can meet higher security requirements through the scheme of encrypting Ethernet packets.
[0051] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0052] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:
[0053] Figure 1 This is a schematic diagram of the structure of a data interaction system between FSI and SOC according to an embodiment of this application;
[0054] Figure 2 This is a flowchart illustrating a data interaction method between an FSI and a SOC according to an embodiment of this application.
[0055] Figure 3 This is a flowchart of the XCP diagnostic initialization process according to an embodiment of this application;
[0056] Figure 4 This is a flowchart illustrating the processing of XCP observation messages and the completion of XCP observation actions according to one embodiment of this application;
[0057] Figure 5 This is a flowchart illustrating the processing of XCP calibration messages and the completion of XCP calibration actions according to one embodiment of this application;
[0058] Figure 6 This is a block diagram of a data interaction device between FSI and SOC according to an embodiment of this application;
[0059] Figure 7 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation
[0060] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.
[0061] Those skilled in the art will understand that the development of XCP has gone through three main stages:
[0062] The CCP (CAN Calibration Protocol) era (1995-2003): In the early days of vehicle electronic systems, communication between various systems was mainly conducted through the CAN (Controller Area Network) bus. The CCP protocol, based on the CAN bus, only supported 1Mbps bandwidth and was limited by the 64-byte payload of the CAN frame, failing to meet the high-speed data acquisition requirements of ADAS (Advanced Driving Assistance Systems). For example, in engine bench testing, the CCP's polling mode required frequent interactions, resulting in parameter update delays as high as milliseconds.
[0063] XCP 1.0-1.3 phase (2003-2015): With the increasing functionality and complexity of vehicles, XCP simultaneously extended its protocol to support more communication protocols. Through an abstract transport layer, XCP could operate on buses such as CAN, Ethernet, and FlexRay. For example, XCP on Ethernet supported UDP / TCP protocols, increasing bandwidth to 1Gbps. It also introduced block caching and DAQ (Data Acquisition List), improving efficiency by more than 10 times compared to CCP. For example, Vector CANape achieved second-level flash writing of 1MB of Flash data through block caching.
[0064] XCP 1.5 and Industry Practices (2016-Present): To further meet real-time requirements, XCP on Ethernet achieves microsecond-level latency through timestamp synchronization and event triggering mechanisms, satisfying the real-time requirements of autonomous driving sensor fusion. For example, the Mobileye EyeQ5 platform utilizes XCP on Ethernet to achieve nanosecond-level synchronization of LiDAR point cloud data.
[0065] Current development trends indicate that the software-defined vehicle technology roadmap makes XCP (X-Chip Collaboration) increasingly important in all stages of development, testing, and mass production. However, it still faces challenges in areas such as high real-time performance, security, and cross-domain collaboration. Furthermore, to implement XCP functionality, controllers often need to reserve external transmission links, such as Ethernet, CAN, and SPI.
[0066] Despite the continuous evolution of XCP technology, it still faces the following shortcomings in practical applications:
[0067] (1) Real-time performance and bandwidth bottlenecks: Currently, most XCP functions still rely on CAN or CAN FD buses. Taking CAN FD as an example, the maximum speed of CAN FD is 2Mbps, and bandwidth needs to be reserved for other protocols such as diagnostics, resulting in limited DAQ data acquisition rate. For example, ADAS domain controllers need to simultaneously acquire data from cameras (100Mbps), radar (50Mbps), and IMU (10Mbps), and the bandwidth utilization of CAN FD is close to saturation. The non-deterministic arbitration mechanism of the CAN bus may cause data transmission delay jitter, affecting the accuracy of real-time control.
[0068] (2) Challenges of Centralized Architecture: Different controllers employ diverse communication methods (such as CAN, Ethernet, FlexRay, etc.) based on their own characteristics and application scenarios, requiring the host computer to have multi-interface adaptation capabilities, which increases system complexity and cost. Taking traditional body controllers as an example, CAN bus is often used to meet their real-time and stability requirements; while ADAS domain controllers, due to the need to process a large amount of sensor data, have extremely high bandwidth requirements and therefore tend to use Ethernet communication. This diversified communication method requires the host computer to have corresponding interface adaptation capabilities to realize XCP calibration and data acquisition for different controllers.
[0069] (3) Cost issues: Even if multiple controllers use the same communication method, such as CAN bus, in practical applications, each controller is usually assigned an independent interface to connect to the host computer. Although this configuration ensures the independence of communication between each controller and the host computer, it leads to a large occupation of host computer interface resources, which not only increases hardware costs, but also makes system wiring more complicated and reduces the reliability and maintainability of the system.
[0070] (4) Functional safety requirements: For some controllers, such as FSI (Functional Safety Island), there are no other CAN or ETH (Ethernet) communication requirements besides XCP. Or, in order to meet functional safety requirements, communication interfaces are usually not allowed to be exposed. Adding corresponding hardware links only to meet the XCP function will not only waste resources, but also introduce more security risks.
[0071] (5) Cross-hardware multi-controller requirements: For centralized architecture, multiple controllers need to implement XCP function at the same time. Traditional single-point communication methods cannot meet the requirements of cross-hardware synchronous recording.
[0072] The following description, with reference to the accompanying drawings, describes a data interaction method, apparatus, device, and medium between FSI and SOC according to embodiments of this application.
[0073] Before introducing the data interaction method between FSI and SOC in the embodiments of this application, we will first introduce the data interaction system between FSI and SOC involved in the data interaction method between FSI and SOC in the embodiments of this application.
[0074] As those skilled in the art will understand, an FSI is essentially an automotive-grade embedded MCU (Microcontroller Unit) with high safety requirements, such as ASIL D (Automotive Safety Integrity Level). The FSI is primarily used for real-time monitoring and detection of system operation, identifying hardware and software faults, and isolating faulty components to prevent them from affecting the entire system. For isolated FSIs, to meet on-chip functional safety requirements, hardware isolation is emphasized, requiring no external communication interfaces.
[0075] Furthermore, such as Figure 1 As shown, the data interaction system between the FSI and the SOC establishes a functional shared memory between the FSI and the SOC. This shared memory, belonging to the FSI's functional safety island, is used for data interaction between internal CPU complexes (such as Cortex-R52) within the FSI, as well as communication with external security MCUs. The FSI has full read and write permissions and can directly modify memory values. Simultaneously, the SOC can read or write data under FSI authorization via dedicated channels (such as SPI interface or DMA engine).
[0076] Figure 1 The host computer in this application can be CANOE host computer software, ASW refers to application software, and ETH refers to Ethernet. In this embodiment, an XCP_Link module is also integrated on the SOC side. The XCP_Link module can also realize the observation and calibration functions of each module on the SOC side, and realize the XCP solution across SOC-FIS hardware.
[0077] Specifically, the host computer sends observation or calibration diagnostic request messages via Ethernet protocol. The XCP_Link module, acting as the slave device, receives these request messages. If the request message is an XCP observation message and contains FSI data, it accesses the shared memory area, reads the value at the corresponding location, writes it into a reply message, and sends it back to the host computer. If the request message contains data from other SOC modules, it accesses the corresponding module and completes the observation function. For calibration messages, if the request message contains FSI data, it writes the calibration value into the shared memory area and writes the reversed value into a reply message, sending it to the host computer. If the request message contains data from other SOC modules, it accesses the corresponding module and completes the calibration.
[0078] Therefore, the data interaction system between FSI and SOC proposed in this application does not require a separate external CAN or ETH link for FSI. By relying on SOC to interact with the host computer, costs are reduced, and external access to the FSI hardware link is avoided, thus meeting functional safety requirements. When both SOC and FSI have XCP requirements, the distinction is only made at the software layer of the XCP_Link module. Only one device and one channel can simultaneously perform XCP observation or calibration operations on FSI and SOC, improving cross-hardware compatibility and scalability. Furthermore, the XCP function can be enabled or disabled through the SOC-side configuration file.
[0079] The following section details the data interaction method between FSI and SOC applied to the aforementioned data interaction system between FSI and SOC.
[0080] Specifically, Figure 2 This is a flowchart illustrating a data interaction method between FSI and SOC provided in an embodiment of this application.
[0081] like Figure 2 As shown, the data interaction method between FSI and SOC includes the following steps:
[0082] In step S201, it is determined whether the current XCP_Link module has received a request message sent by the host computer.
[0083] XCP_Link is an XCP program integrated on the SOC side. Currently, the XCP_Link module is integrated on the SOC side. This module can process XCP diagnostic commands from the host computer and can also detect whether the FSI is working properly through heartbeat messages, enabling XCP diagnostics. In this embodiment, the XCP_Link module interacts with the host computer via Ethernet protocol and uses TCP / IP (Transmission Control Protocol / Internet Protocol) protocol to ensure reliable data transmission.
[0084] Specifically, in this embodiment of the application, it is possible to determine whether a request message sent by the host computer has been received by continuously monitoring the network interface (such as the Ethernet interface) of the current XCP_Link module.
[0085] It should be noted that, in this embodiment of the application, before determining whether the current XCP_Link module has received a request message sent by the host computer, the XCP diagnostic initialization work also needs to be completed.
[0086] Specifically, the FSI program stores observations in a shared memory region, which the XCP_Link module has read and write permissions for. Upon receiving an observation command, the XCP_Link module looks up the corresponding observation value in the shared memory region using an index table, and then sends that value back to the host computer, completing one observation. During program execution, FSI simultaneously updates the observation values in the shared memory region.
[0087] The following is combined Figure 3 This section describes the process of initializing XCP diagnostics.
[0088] Specifically, such as Figure 3 As shown, the XCP_Link module first starts up after the system is powered on. After starting up, the XCP_Link module checks the working status of the Functional Safety Island (FSI) to ensure its normal operation.
[0089] Once the FSI is confirmed to be working properly, the XCP_Link module will enter a waiting state, ready to receive connection requests from a host computer. The host computer typically refers to an external control device, such as a computer or dedicated testing equipment. Once the host computer successfully connects, the XCP_Link module will receive observation commands from it. If the FSI fails to work properly, the process ends.
[0090] In step S202, if the current XCP_Link module receives a request message, the type of the request message is determined.
[0091] In step S203, based on the preset shared memory region, data interaction between FSI and SOC is performed according to the type of request message.
[0092] Furthermore, in some embodiments, when the type of the request message is an observation message, based on a preset shared memory area, data interaction between FSI and SOC is performed according to the type of the request message, including: parsing the observation message to obtain observation data; determining whether the observation data is FSI data; if the observation data is FSI data, accessing the preset shared memory area and reading the first observation value corresponding to the FSI data; writing the first observation value into a first reply message, and sending the first reply message to the host computer.
[0093] Among them, the preset shared memory region functional safety island (FSI) and the memory space used for data interaction between the system-on-a-chip (SOC) are used.
[0094] Specifically, for the FSI program, observations need to be stored in a shared memory area, and the data needs to be updated based on program execution. For the XCP_Link module, after receiving an observation request from the host computer, it parses the received observation message, extracts key information from the message, such as the data identifier of the observation, the data type, and the requested data length, and obtains the observation data.
[0095] Furthermore, the XCP_Link module determines whether the requested observation data in the observation message belongs to FSI data. If the observation data is FSI data, the XCP_Link module accesses a preset shared memory region and, based on a memory index table, uses the index information parsed from the observation message to locate the specific data location. This index corresponds to a specific address or data structure within the preset shared memory region. Once the correct memory location is located, the XCP_Link module reads the first observation value corresponding to the FSI data. After reading the first observation value, the XCP_Link module writes the first observation value into the first response message and sends the first response message containing the first observation value to the host computer, thus completing one observation operation.
[0096] Furthermore, in some embodiments, after determining whether the observed data is FSI data, the method further includes: if the observed data is not FSI data, determining the module to be accessed in the SOC based on the observed data; obtaining the second observed value in the module to be accessed, writing the second observed value into the second response message, and sending the second response message to the host computer.
[0097] Specifically, if the observed data is not FSI data, it indicates that the observed data belongs to other modules in the SOC. The XCP_Link module needs to determine which module in the SOC contains the required data based on the information in the observation message. Each module in the SOC has a specific function and dataset; for example, one module might handle sensor data, while another might handle actuator status. Once the module to be accessed is determined, the XCP_Link module will access it according to its interface and protocol, read data through a specific communication interface or memory-mapped area, obtain the second observed value, encapsulate this second observed value in a second response message, and send the second response message to the host computer to ensure that the host computer can receive the required observation data.
[0098] To facilitate a clearer and more intuitive understanding by those skilled in the art of processing XCP observation messages and completing XCP observation actions in the embodiments of this application, the following is a detailed explanation. Figure 4 Please provide a detailed explanation.
[0099] Specifically, such as Figure 4As shown, the process of processing XCP observation messages and completing XCP observation actions includes the following steps:
[0100] First, the XCP_Link module parses the received observation message and determines whether the observation belongs to FSI data. If the observation belongs to FSI data, it locates and accesses the data in shared memory according to the index table. After completing the access, the processing result is sent to the host computer in the form of a reply message.
[0101] If the observation is not part of the FSI data, the required observation values are obtained from within the SOC. After obtaining the values, the processing results are sent to the host computer in the form of a reply message.
[0102] In addition, while parsing the observation messages, the FSI program updates the data in the shared memory to ensure that the data in the shared memory is up-to-date so that accurate information can be obtained when accessing the shared memory region.
[0103] Furthermore, in some embodiments, when the type of the request message is a calibration message, based on a preset shared memory area, data interaction between FSI and SOC is performed according to the type of the request message, including: parsing the calibration message to obtain calibration data, the calibration data including a first calibration value; determining whether the calibration data is FSI data; if the calibration data is FSI data, then writing the first calibration value into the preset shared memory area, and reading back the first address corresponding to the first calibration value to obtain a first reverse read value, writing the first reverse read value into a third reply message, and sending the third reply message to the host computer.
[0104] Specifically, for FSI programs, the calibration values need to be stored in a shared memory area, and the program reads the calibration data from the shared memory during runtime. The host computer sends an XCP calibration request message to the XCP_Link module on the SOC side via Ethernet / TCP protocol. After receiving the calibration request from the host computer, the XCP_Link module parses the calibration request message, extracts the calibration instruction type, calibration value identifier (such as variable name or memory address index), and first calibration value (the target value to be written), and obtains the calibration data.
[0105] Furthermore, the XCP_Link module queries a predefined memory index table based on the calibration identifier to determine whether the calibration data is FSI data. If it is FSI data, it writes the calibration value to the preset shared memory region of FSI through a dedicated channel (such as SPI or DMA engine), locates the specific address in the shared memory (such as 0x8000_1000) according to the index table, and writes the first calibration value (such as 25.5) to that address.
[0106] After the writing is completed, the XCP_Link module reads the value just written from the same address (0x8000_1000) to obtain the first reverse read value, fills the third reply message with the first reverse read value, and sends the third reply message to the host computer via the Ethernet protocol to complete one calibration function.
[0107] Furthermore, in some embodiments, after determining whether the calibration data is FSI data, the method further includes: if the calibration data is not FSI data, updating the calibration value, and performing a reverse read on the second address corresponding to the updated calibration value to obtain a second reverse read value, writing the second reverse read value into a fourth reply message, and sending the fourth reply message to the host computer.
[0108] The second address refers to the physical address of the calibrated value in the SOC memory.
[0109] Specifically, if the calibration data is not FSI data, meaning it is data from an internal SOC module, the XCP_Link module queries the SOC's internal calibration variable mapping table based on the calibration identifier to determine the physical address of the calibration data in the SOC memory (e.g., 0x4000_2000), which is the second address. The first calibration value in the message is written to the second address in the SOC memory, and the newly written value is read from the second address (0x4000_2000) to obtain the second reverse read value. This second reverse read value is then filled into the fourth reply message and sent to the host computer via Ethernet, completing the calibration function.
[0110] To facilitate a clearer and more intuitive understanding by those skilled in the art of processing XCP calibration messages and completing XCP calibration actions in the embodiments of this application, the following is a detailed explanation. Figure 5 Please provide a detailed explanation.
[0111] Specifically, such as Figure 5 As shown, the process of processing the XCP calibration message and completing the XCP calibration action includes the following steps:
[0112] First, the XCP_Link module parses the received calibration message. If the calibration data belongs to FSI data, it writes the data to the corresponding location in shared memory according to the index table. After the write operation is completed, it reads the data just written from shared memory to verify the correctness of the write operation. If the verification is successful, the processing result is sent to the host computer in the form of a reply message.
[0113] If the calibration value is not part of the FSI data, the corresponding calibration value is updated within the SOC. After the update is complete, the processing result is sent to the host computer as a reply message.
[0114] In addition, while parsing the calibration message, the FSI program reads data from the shared memory to ensure that it can obtain the latest data status before writing new data.
[0115] Therefore, the data interaction method between FSI and SOC proposed in this application, by relying on a shared memory area between FSI and SOC, can implement XCP functionality without adding additional hardware communication interfaces. With the continuous development of intelligent connected vehicle technology, new communication protocols and devices will continue to emerge, leading to higher demands for information security. Encrypting XCP data using TLS or similar methods can improve XCP security. The cross-hardware XCP solution between FSI and SOC proposed in this application has advantages such as low cost, cross-hardware compatibility and scalability, and high security and reliability, while avoiding the adaptation difficulties caused by the diversification of communication methods.
[0116] Furthermore, with the development of software-defined vehicles, XCP is being used more extensively in the automotive field. Cross-hardware XCP solutions that do not rely on additional hardware interfaces will further accelerate the market application and promotion of intelligent connected vehicles, and drive the automotive industry towards intelligence and connectivity.
[0117] According to the data interaction method between FSI and SOC in this application embodiment, when the current XCP_Link module receives a request message sent by the host computer, the type of the request message is determined; based on a preset shared memory area, data interaction between FSI and SOC is performed according to the type of the request message. This solves the problems of hardware redundancy, functional safety limitations, insufficient real-time performance, and high cost in existing XCP technologies when communicating across functional safety islands and SOC modules. It achieves efficient XCP communication between FSI and SOC modules through a shared memory mechanism, avoiding external access to the FSI hardware link, meeting functional safety requirements, improving cross-hardware compatibility and scalability, and possessing high security and reliability.
[0118] Next, the data interaction device between FSI and SOC according to the embodiments of this application is described with reference to the accompanying drawings.
[0119] Figure 6 This is a block diagram of the data interaction device between FSI and SOC according to an embodiment of this application.
[0120] like Figure 6 As shown, the data interaction device 10 between FSI and SOC includes: a judgment module 100, a determination module 200, and a data interaction module 300.
[0121] The system includes a judgment module 100, which is used to determine whether the current XCP_Link module has received a request message sent by the host computer; a determination module 200, which is used to determine the type of the request message if the current XCP_Link module has received a request message; and a data interaction module 300, which is used to perform data interaction between FSI and SOC based on a preset shared memory area and the type of the request message.
[0122] Furthermore, in some embodiments, when the type of the request message is an observation message, the data interaction module 300 is used to: parse the observation message to obtain observation data; determine whether the observation data is FSI data; if the observation data is FSI data, access a preset shared memory area and read the first observation value corresponding to the FSI data; write the first observation value into a first reply message, and send the first reply message to the host computer.
[0123] Furthermore, in some embodiments, after determining whether the observed data is FSI data, the data interaction module 300 is further configured to: if the observed data is not FSI data, determine the module to be accessed in the SOC based on the observed data; obtain the second observed value in the module to be accessed, write the second observed value into the second reply message, and send the second reply message to the host computer.
[0124] Furthermore, in some embodiments, when the type of the request message is a calibration message, the data interaction module 300 is used to: parse the calibration message to obtain calibration data, the calibration data including a first calibration value; determine whether the calibration data is FSI data; if the calibration data is FSI data, write the first calibration value into a preset shared memory area, and read the first address corresponding to the first calibration value to obtain a first reverse read value, write the first reverse read value into a third reply message, and send the third reply message to the host computer.
[0125] Furthermore, in some embodiments, after determining whether the calibration data is FSI data, the data interaction module 300 is further configured to: if the calibration data is not FSI data, update the calibration value, and perform reverse reading on the second address corresponding to the updated calibration value to obtain a second reverse reading value, write the second reverse reading value into a fourth reply message, and send the fourth reply message to the host computer.
[0126] Furthermore, in some embodiments, the current XCP_Link module is integrated on the SOC side.
[0127] It should be noted that the foregoing explanation of the data interaction method embodiment between FSI and SOC also applies to the data interaction device between FSI and SOC in this embodiment, and will not be repeated here.
[0128] According to the data interaction device between FSI and SOC in this application embodiment, when the current XCP_Link module receives a request message sent by the host computer, it determines the type of the request message; based on a preset shared memory area, it performs data interaction between FSI and SOC according to the type of the request message. This solves the problems of hardware redundancy, functional safety limitations, insufficient real-time performance, and high cost in existing XCP technologies when communicating across functional safety islands and SOC modules. It achieves efficient XCP communication between FSI and SOC modules through a shared memory mechanism, avoiding external access to the FSI hardware link, meeting functional safety requirements, improving cross-hardware compatibility and scalability, and possessing high security and reliability.
[0129] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:
[0130] The memory 701, the processor 702, and the computer program stored on the memory 701 and executable on the processor 702.
[0131] When the processor 702 executes the program, it implements the data interaction method between FSI and SOC provided in the above embodiments.
[0132] Furthermore, electronic devices also include:
[0133] Communication interface 703 is used for communication between memory 701 and processor 702.
[0134] The memory 701 is used to store computer programs that can run on the processor 702.
[0135] The memory 701 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.
[0136] If the memory 701, processor 702, and communication interface 703 are implemented independently, then the communication interface 703, memory 701, and processor 702 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 7The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0137] Optionally, in a specific implementation, if the memory 701, processor 702, and communication interface 703 are integrated on a single chip, then the memory 701, processor 702, and communication interface 703 can communicate with each other through an internal interface.
[0138] The processor 702 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.
[0139] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described data interaction method between FSI and SOC.
[0140] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0141] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0142] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.
Claims
1. A data interaction method between FSI and SOC, characterized in that, Includes the following steps: Determine whether the current XCP_Link module has received a request message sent by the host computer; If the current XCP_Link module receives the request message, then the type of the request message is determined; Based on a preset shared memory region, data interaction between FSI and SOC is performed according to the type of the request message; The current XCP_Link module is integrated on the SOC side; When the type of the request message is an observation message, the step of performing data interaction between FSI and SOC based on the type of the request message and a preset shared memory area includes: parsing the observation message to obtain observation data; determining whether the observation data is FSI data; if the observation data is FSI data, accessing the preset shared memory area and reading the first observation value corresponding to the FSI data; writing the first observation value into a first reply message, and sending the first reply message to the host computer. When the type of the request message is a calibration message, the step of performing data interaction between FSI and SOC based on the type of the request message according to the preset shared memory area includes: parsing the calibration message to obtain calibration data, the calibration data including a first calibration value; determining whether the calibration data is FSI data; if the calibration data is FSI data, then writing the first calibration value into the preset shared memory area, and reading back the first address corresponding to the first calibration value to obtain a first read-back value, writing the first read-back value into a third reply message, and sending the third reply message to the host computer.
2. The method of claim 1, wherein, After determining whether the observed data is FSI data, the process further includes: If the observed data is not the FSI data, then based on the observed data, the module to be accessed in the SOC is determined; Obtain the second observation value from the module to be accessed, write the second observation value into the second reply message, and send the second reply message to the host computer.
3. The method of claim 1, wherein, After determining whether the calibrated data is FSI data, the process also includes: If the calibration data is not the FSI data, then the calibration value is updated, and the second address corresponding to the updated calibration value is read in reverse to obtain the second reverse read value. The second reverse read value is written into the fourth reply message, and the fourth reply message is sent to the host computer.
4. A data interaction device of FSI and SOC, characterized in that, include: The judgment module is used to determine whether the current XCP_Link module has received a request message sent by the host computer; The determination module is used to determine the type of the request message if the current XCP_Link module receives the request message; The data interaction module is used to perform data interaction between FSI and SOC based on a preset shared memory area and according to the type of the request message; The current XCP_Link module is integrated on the SOC side; When the type of the request message is an observation message, the data interaction module is configured to: parse the observation message to obtain observation data; determine whether the observation data is FSI data; if the observation data is FSI data, access the preset shared memory area and read the first observation value corresponding to the FSI data; write the first observation value into a first reply message, and send the first reply message to the host computer; When the type of the request message is a calibration message, the data interaction module is configured to: parse the calibration message to obtain calibration data, the calibration data including a first calibration value; determine whether the calibration data is FSI data; if the calibration data is FSI data, write the first calibration value into the preset shared memory area, and read the first address corresponding to the first calibration value to obtain a first reverse read value, write the first reverse read value into a third reply message, and send the third reply message to the host computer.
5. An electronic device, comprising: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the data interaction method between FSI and SOC as described in any one of claims 1-3.
6. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by a processor to implement the data interaction method between FSI and SOC as described in any one of claims 1-3.
Citation Information
Patent Citations
System on chip and vehicle comprising same
CN117951075A
Multi-system control method and device, electronic equipment and storage medium
CN118672825A
