A modular design method for a control unit based on a new generation of low-voltage, high-performance IoT switches

Abstract

This invention proposes a modular design method for a control unit based on a new generation of low-voltage, high-performance IoT switches. Based on a real-time operating system (RTOS), a hot-swap management module is set in the middleware layer to monitor and manage module insertion and removal events. The hot-swap management module includes: a monitoring submodule for real-time monitoring of module insertion and removal events; a driver management submodule for loading and unloading module drivers to ensure correct initialization upon insertion and resource release upon removal; and a communication submodule for providing communication interfaces with the operating system and application layer to ensure real-time transmission of insertion and removal events and status. By monitoring module insertion and removal events and loading and unloading module drivers, it achieves hot-swap functionality for modules and supports peripherals such as HPLC, Bluetooth, networking modules, and screens, improving system reliability and flexibility. It compensates for the lack of hot-swap functionality for peripherals in embedded systems and is suitable for embedded applications.

Description

Technical Field

[0001] This invention relates to the field of embedded system technology, and in particular to a modular design of a control unit based on a new generation of low-voltage, high-performance IoT switches. Background Technology

[0002] With the development of embedded systems, modular design plays an important role in improving system flexibility and maintenance convenience. However, traditional embedded systems typically require a system restart when plugging or unplugging modules, which not only affects system availability but may also lead to data loss and system instability.

[0003] In existing technologies, some systems achieve hot-swapping of modules through a combination of hardware and software. However, these systems are usually designed for specific hardware platforms and lack versatility. Furthermore, existing systems often lack effective exception handling mechanisms during module insertion and removal, which can easily lead to system crashes or data corruption.

[0004] For example, existing technologies such as CN200910190432-A CPCI hot-swappable system and CN202310924387-Hot-swappable method, PCIE device and management controller show that hot-swapping is a mature solution in PC and Linux systems, but there is no reliable solution for embedded systems. Summary of the Invention

[0005] Currently, embedded systems based on the RT-Thread operating system are widely used in various industrial and consumer devices. Therefore, developing a system that supports hot-swappable modules is of great significance. This invention addresses the shortcomings and deficiencies of existing technologies by proposing a modular design method for a control unit based on a new generation of low-voltage, high-performance IoT switches. The main purpose is to enable safe insertion and removal of modules without restarting the system, ensuring system stability and reliability. By monitoring module insertion and removal events and loading and unloading module drivers, hot-swappable modules are implemented. This method also supports peripherals such as HPLC, Bluetooth, 485, 4G networking modules, and screens, improving system reliability and flexibility, compensating for the lack of hot-swappable peripherals in embedded systems, and making it suitable for high-performance embedded applications.

[0006] The present invention specifically adopts the following technical solution:

[0007] A modular design method for control units based on a new generation of low-voltage, high-performance IoT switches:

[0008] Based on a real-time operating system (RTOS), a hot-swap management module is set up in the middleware layer to monitor and manage module insertion and removal events.

[0009] The hot-swap management module includes:

[0010] Monitoring submodule: Used for real-time monitoring of module insertion and removal events;

[0011] Driver management submodule: Used to load and unload module drivers to ensure that the module can be correctly initialized when inserted and to release resources when removed;

[0012] Communication submodule: Provides communication interfaces with the operating system and application layer to ensure real-time transmission of plug-in / plug-out events and status.

[0013] Furthermore, when a new module is detected being inserted, the monitoring submodule sends an insertion event notification, and the driver management submodule loads the corresponding driver and initializes the module;

[0014] When a module is detected to be unplugged, the monitoring submodule sends a unplugging event notification, and the driver management submodule uninstalls the driver and releases resources.

[0015] Furthermore, if any abnormal situation occurs during module insertion or removal, a rollback operation will be performed to ensure stable system operation.

[0016] Furthermore, log information is recorded during each hot-plug operation, including at least the plug-in / plug-out time, module type, plug-in / plug-out status, success or failure, and error code.

[0017] Furthermore, for cases where peripheral hardware supports hot-swapping but the embedded system does not, implementing hot-swapping functionality includes the following steps:

[0018] Enable peripheral SDIO;

[0019] Enable the DFS virtual file system;

[0020] Enable the FATFS file system and register the registered devices to the DFS virtual file system in the form of ELM FATFS.

[0021] Then, the application layer calls dfs_mount to mount the peripheral hardware.

[0022] Furthermore, for cases where peripheral hardware supports hot-swapping, but the embedded system does not:

[0023] Obtain the plug-in / plug-out status of peripheral hardware through external interrupts or timer polling:

[0024] When peripheral hardware is plugged in:

[0025] After reading the configuration parameter values ​​when the hot-plug driver is loaded and verifying their correctness, the system pre-requests the resources and memory space required by the peripheral hardware during hot-plugging; through the monitoring submodule, the peripheral hardware's semaphore is seized and an insertion event notification is sent, the peripheral hardware driver is loaded and the file system is initialized, and the information is written to the log system;

[0026] When peripheral hardware is unplugged: the pin signal is detected, the peripheral hardware signal is released, the monitoring submodule sends a unplug event notification, the peripheral hardware thread is closed, the driver is uninstalled, and the information is written to the log system.

[0027] Furthermore, for peripheral hardware that does not support hot-swapping:

[0028] Determine the plugging / unplugging status of the device based on its own communication characteristics or protocols;

[0029] By maintaining a thread for peripheral hardware detection, this thread periodically sends AT commands to the corresponding peripheral hardware. When the peripheral hardware does not respond, it is determined that the module has been unplugged or is damaged. At this time, the monitoring submodule sends a module unplug event, closes the corresponding running thread, uninstalls the driver, and writes the information to the log system. When the module responds again, it is determined that the module has been reconnected or replaced. At this time, the monitoring submodule sends a module insert event, creates the running thread corresponding to the peripheral hardware, reloads the module driver, and writes the information to the log system.

[0030] Furthermore, it supports full hot-swapping and high-reliability hot-swapping;

[0031] Full hot-plugging is achieved by using the level of peripheral hardware pins as a switch. When peripheral hardware is inserted or removed, before the peripheral hardware starts or stops working, the switch first changes state to generate a system enumeration signal to notify the operating system that a device module is about to be inserted or removed. The operating system then performs bus enumeration to install or uninstall the device driver.

[0032] The high-reliability hot-swap is based on full hot-swap, and by monitoring the normal operation of each device module in real time, it isolates abnormal device modules and activates alternative backup device modules.

[0033] Furthermore, a control unit based on a new generation of low-voltage, high-performance IoT switches adopts the above modular design method, including a hardware layer, an operating system layer, a middleware layer, and an application layer; wherein, the hardware layer adopts a multi-core chip including a RISC-V core; the operating system adopts the RT-Thread operating system; and the application layer interacts with the hot-swap management module through an API interface.

[0034] Furthermore, hot-swapping enables module management for components including the HPLC module, Bluetooth module, 485 communication module, mobile communication module, and screen peripherals.

[0035] This invention and its preferred embodiment realize the hot-swappable function of modules by monitoring module insertion and removal events, loading and unloading module drivers, and supporting peripherals such as HPLC, Bluetooth, 485, 4G networking modules and screens, thereby improving the reliability and flexibility of the system, making up for the lack of hot-swappable peripherals in embedded systems, and are suitable for high-performance embedded applications, especially for the control unit of a new generation of low-voltage high-performance IoT switches. Attached Figure Description

[0036] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments:

[0037] Figure 1 This is a schematic diagram of the system architecture of an embodiment of the present invention.

[0038] Figure 2 This is a schematic diagram of the hot-swap management module according to an embodiment of the present invention.

[0039] Figure 3 This is a schematic diagram of the module insertion process in an embodiment of the present invention.

[0040] Figure 4 This is a schematic diagram of the module unplugging process in an embodiment of the present invention.

[0041] Figure 5 This is a schematic diagram of the exception handling process in an embodiment of the present invention.

[0042] Figure 6 This is a diagram illustrating the error log recording structure of an embodiment of the present invention.

[0043] Figure 7 This is a schematic diagram of the entire process of the hot-swap management module in an embodiment of the present invention. Detailed Implementation

[0044] In the following, specific embodiments of this application will be described in detail with reference to the accompanying drawings. Based on these detailed descriptions, those skilled in the art will be able to clearly understand and implement this application. Without departing from the principles of this application, features from various embodiments can be combined to obtain new implementations, or certain features from some embodiments can be substituted to obtain other preferred implementations.

[0045] To make the features and advantages of this patent more apparent and understandable, specific embodiments are provided below, along with accompanying drawings, for detailed explanation:

[0046] like Figure 1As shown, the control unit system for a low-voltage, high-performance IoT switch based on hot-swappable technology and modular design, provided in an embodiment of the present invention, includes: a hardware layer, an operating system layer, a middleware layer, and an application layer. The hardware layer includes a multi-core chip, preferably a multi-core chip with a RISC-V core; the operating system layer is the RT-Thread operating system; the middleware layer includes a hot-swappable management module; and the application layer is a user application program.

[0047] The system architecture is as follows:

[0048] Hardware layer: Multi-core chip with high clock speed, suitable for high-performance applications.

[0049] Operating system layer: RT-Thread operating system, which provides real-time, multi-task scheduling, device driver and other functions.

[0050] Middleware layer: Hot-swap management module, responsible for monitoring and managing module insertion and removal events.

[0051] Application layer: User applications interact with the hot-plug management module through API interfaces.

[0052] like Figure 2 As shown, the hot-swap management module includes a monitoring submodule, a driver management submodule, and a communication submodule. The monitoring submodule is used to monitor module insertion and removal events in real time and notify other parts of the system in a timely manner; the driver management submodule is responsible for loading and unloading module drivers to ensure that the module can be correctly initialized when inserted and release resources when removed; the communication submodule provides communication interfaces with the operating system and application layer to ensure the real-time transmission of insertion and removal events and statuses.

[0053] like Figure 3 As shown, when a new module is detected, the monitoring submodule sends an insertion event notification, and the driver management submodule loads the corresponding driver and initializes the module.

[0054] like Figure 4 As shown, when a module is detected to be unplugged, the monitoring submodule sends a unplug event notification, and the driver management submodule uninstalls the driver and releases resources.

[0055] like Figure 5 As shown, if an abnormal situation occurs during module insertion or removal, the system will automatically perform a rollback operation to ensure stable system operation.

[0056] like Figure 6 As shown, an error logging module is also provided, which records detailed log information during each hot-plug operation, including plug-in / plug-out time, module type, plug-in / plug-out status, success or failure, error code, etc.

[0057] Log storage and retrieval: The log recording module stores log information in non-volatile memory and supports querying and analysis through API interface.

[0058] The system designed above can at least support hot-swappable functions for HPLC (carrier communication) modules, Bluetooth modules, 485 communication modules, 4G networking modules, and screen peripherals.

[0059] in:

[0060] a) HPLC (Power Line Carrier Communication) module: Used for power line carrier communication, supporting hot-swapping without interrupting power line communication.

[0061] b) Bluetooth module: used for short-range wireless communication, supporting hot-swapping without interrupting existing Bluetooth connections.

[0062] c) RS-485 communication module: used for RS-485 bus communication in industrial control, supporting hot-swapping without interrupting RS-485 bus communication.

[0063] d) 4G networking module: used for cellular network communication, supporting hot-swapping without interrupting the 4G network connection.

[0064] e) Screen peripherals: used for display output, supporting hot-swapping without interrupting display output.

[0065] The specific hot-swap management function is designed as follows:

[0066] a) HPLC (Carrier Communication) module:

[0067] i. In RT-Thread, the driver for the HPLC module is designed to be dynamically loaded and unloaded.

[0068] ii. When the HPLC module is inserted, the monitoring submodule detects the insertion event and notifies the drive management submodule.

[0069] iii. The driver management submodule calls the dynamic driver loading interface provided by RT-Thread to load the HPLC module driver into the system and initialize the communication parameters.

[0070] iv. When unplugged, the driver management submodule calls the dynamic driver unloading interface to unload the HPLC module driver and release resources.

[0071] b) Bluetooth module:

[0072] i. The Bluetooth module driver in RT-Thread is also designed to be dynamically loaded and unloaded.

[0073] ii. Insertion events are detected by the monitoring submodule and notified to the driver management submodule, which loads the Bluetooth module driver and initializes the Bluetooth stack.

[0074] iii. When a disconnection event occurs, the driver management submodule uninstalls the Bluetooth driver and ensures that the current Bluetooth connection is properly disconnected to prevent data loss.

[0075] c) 485 communication module:

[0076] The i.485 module driver can be dynamically loaded and unloaded in RT-Thread.

[0077] ii. Upon insertion, the monitoring submodule notifies the driver management submodule, which loads the 485 driver and configures the bus parameters.

[0078] iii. When unplugged, the driver management submodule unloads the 485 driver and releases related resources to ensure stable bus communication.

[0079] d) 4G network module:

[0080] The i.4G module driver supports dynamic loading and unloading.

[0081] ii. Upon insertion, the monitoring submodule notifies the driver management submodule to load the 4G driver and initialize the network connection.

[0082] iii. When unplugged, the driver management submodule uninstalls the 4G driver to ensure a safe disconnection of the network connection.

[0083] e) Screen peripherals:

[0084] i. Screen peripheral drivers support dynamic loading and unloading.

[0085] ii. During insertion, the monitoring submodule notifies the driver management submodule to load the screen driver and initialize the display parameters.

[0086] iii. When the screen is unplugged, the driver management submodule unloads the screen driver and releases the display buffer resources.

[0087] In many systems, such as Linux, hot-swapping is widely supported for certain peripherals, but not yet in embedded systems, especially real-time operating systems (RTOS). Below are some common hot-swapping peripherals, as well as device types supported in Linux but not fully supported in RTOS:

[0088] like Figure 7 As shown, for different modules, this embodiment of the hot-swap management module provides the following two preferred embodiments of hot-swap methods:

[0089] Category 1: Peripheral hardware that supports hot-swapping but is not supported by the embedded system, such as SD cards, USB devices, PCIe devices, SATA devices, network devices, etc. Taking SD cards as an example, using an SD card in an RTOS requires the following steps:

[0090] 1. Enable peripheral SDIO,

[0091] 2. Enable DFS virtual file system

[0092] 3. Enable the FATFS file system and register the registered sd0 block device to the DFS virtual file system in the form of ELM FATFS.

[0093] 4. At this point, call dfs_mount at the application layer to mount sd0, and you can then use the SD card and file system.

[0094] Considering that removing the card midway through system operation could lead to system malfunctions and other problems.

[0095] Because the SD card hardware has a pin_check pin (high level when inserted, low level when removed), the SD card driver code can be modified to add a signal check to the SD card's pin_check pin to obtain the SD card's insertion and removal status.

[0096] When the SD card is inserted:

[0097] The system reads the user's configuration parameter values ​​when the hot-swap driver is loaded, verifies the correctness of these parameters, pre-requests resources and memory space required by the functional board device during hot-swapping from the system, monitors the module, preempts the SD card's semaphore, sends an insertion event notification, loads the SD card driver and initializes the file system, and writes the information to the log system. When the SD card is removed, the system detects pin signals, releases the SD card's semaphore, sends a removal event notification, closes the SD card thread, unloads the SD card driver, and writes the information to the log system.

[0098] Category 2: Communication modules whose peripheral hardware does not support hot-swapping, such as 4G modules and carrier modules.

[0099] The device's own communication characteristics or protocols can be used to determine if the device has been plugged in or unplugged. For example, for UART devices (4G modules, carrier modules, etc.), their presence can be determined by detecting whether the device responds to communication.

[0100] By maintaining a thread for monitoring the communication module, this thread periodically sends AT commands to the communication module (4G module). When the module does not respond, it is determined that the module has been unplugged or is damaged. At this time, the monitoring submodule sends a module unplug event, closes the running thread of the 4G module, uninstalls the 4G module driver, and writes the information to the log system. When the module responds again, it is determined that the module has been reconnected or replaced. At this time, the monitoring submodule sends a module insert event, creates the running thread of the 4G module, reloads the 4G module driver, and writes the information to the log system.

[0101] Based on the above design, the embodiments of the present invention can achieve support for full hot-swapping and high-reliability hot-swapping.

[0102] Full hot-plugging is based on basic hot-plugging, adding a virtual microswitch (e.g., using the level of a pin as a switch) to the device insertion / removal mechanism. When a device is inserted or removed, before the device starts or stops working, the microswitch first changes its state and generates a system enumeration (#ENUM) signal. This signal notifies the operating system that a device is about to be inserted or removed, and the operating system then performs actions such as bus enumeration, installing or uninstalling the device driver.

[0103] High-reliability hot-swappable is built upon full hot-swappable technology. It can monitor whether a device is functioning properly, and the system can automatically isolate a faulty device, start a replacement device, and then continue operating.

[0104] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0105] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0106] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0107] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0108] The above description is a preferred embodiment of the present invention. It should be noted that, for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

[0109] This patent is not limited to the above-described preferred embodiment. Anyone can derive other modular design methods for control units based on a new generation of low-voltage high-performance IoT switches under the guidance of this patent. All equivalent changes and modifications made within the scope of this patent application shall be covered by this patent.

Claims

1. A modular design method for a control unit based on a new generation of low-voltage, high-performance IoT switches, characterized in that: Based on a real-time operating system (RTOS), a hot-swap management module is set up in the middleware layer to monitor and manage module insertion and removal events. The hot-swap management module includes: Monitoring submodule: Used for real-time monitoring of module insertion and removal events; Driver management submodule: Used to load and unload module drivers to ensure that the module can be correctly initialized when inserted and to release resources when removed; Communication submodule: Used to provide communication interfaces with the operating system and application layer to ensure real-time transmission of plug-in / plug-out events and status; Supports full hot-swapping; Full hot-plugging is achieved by using the voltage level of peripheral hardware pins as a switch. When a peripheral hardware is inserted or removed, before the peripheral hardware starts or stops working, the switch first changes state to generate a system enumeration signal to notify the operating system that a device module is about to be inserted or removed. The operating system then performs bus enumeration to install or uninstall the device driver.

2. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: When a new module is detected, the monitoring submodule sends an insertion event notification, and the driver management submodule loads the corresponding driver and initializes the module. When a module is detected to be unplugged, the monitoring submodule sends a unplugging event notification, and the driver management submodule uninstalls the driver and releases resources.

3. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 2, characterized in that: If any abnormal situation occurs during module insertion or removal, a rollback operation will be performed to ensure stable system operation.

4. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: During each hot-plug operation, log information is recorded, including at least the plug-in / plug-out time, module type, plug-in / plug-out status, success or failure, and error code.

5. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: For peripheral hardware that supports hot-swapping, but the embedded system does not, implementing hot-swapping functionality includes the following steps: Enable peripheral SDIO; Enable the DFS virtual file system; Enable the FATFS file system and register the registered devices to the DFS virtual file system in the form of ELM FATFS. Then, the application layer calls dfs_mount to mount the peripheral hardware.

6. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: For peripheral hardware that supports hot-swapping, but the embedded system does not: Obtain the plug-in / plug-out status of peripheral hardware through external interrupts or timer polling: When peripheral hardware is plugged in: After reading the configuration parameter values ​​when the hot-plug driver is loaded and verifying their correctness, the system pre-requests the resources and memory space required by the peripheral hardware during hot-plugging; through the monitoring submodule, the peripheral hardware's semaphore is seized and an insertion event notification is sent, the peripheral hardware driver is loaded and the file system is initialized, and the information is written to the log system; When peripheral hardware is unplugged: the pin signal is detected, the peripheral hardware signal is released, the monitoring submodule sends a unplug event notification, the peripheral hardware thread is closed, the driver is uninstalled, and the information is written to the log system.

7. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: For peripheral hardware that does not support hot-swapping: Determine the plugging / unplugging status of the device based on its own communication characteristics or protocols; By maintaining a thread for peripheral hardware detection, this thread periodically sends AT commands to the corresponding peripheral hardware. When the peripheral hardware does not respond, it is determined that the module has been unplugged or is damaged. At this time, the monitoring submodule sends a module unplug event, closes the corresponding running thread, uninstalls the driver, and writes the information to the log system. When the module responds again, it is determined that the module has been reconnected or replaced. At this time, the monitoring submodule sends a module insert event, creates the running thread corresponding to the peripheral hardware, reloads the module driver, and writes the information to the log system.

8. The modular design method for a control unit based on a new generation of low-voltage high-performance IoT switches according to claim 1, characterized in that: It also supports high-reliability hot-swapping, which is based on full hot-swapping and involves real-time monitoring of whether each device module is operating normally to isolate abnormal device modules and activate alternative backup device modules.

9. A control unit based on a new generation of low-voltage, high-performance IoT switches, characterized in that, The modular design method according to any one of claims 1-8 includes a hardware layer, an operating system layer, a middleware layer, and an application layer; wherein the hardware layer adopts a multi-core chip including a RISC-V core; the operating system adopts the RT-Thread operating system; and the application layer interacts with the hot-plug management module through an API interface.

10. The control unit based on a new generation of low-voltage high-performance IoT switch according to claim 9, characterized in that: Hot-swappable modules are used to manage the following components: HPLC module, Bluetooth module, 485 communication module, mobile communication module, and screen peripherals.

Images