Automotive Switch Fabric Node Reprogramming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In automotive switch fabric networks, there is a challenge in reprogramming nodes while maintaining communication, especially when upgrading software or diagnosing faults, as existing methods fail to efficiently manage memory re-flashing and software updates.
Innovation Solution
A system and method using a diagnostic device and interface to download software components to nodes in the network, utilizing two memory partitions in each node – an erasable code block for standard software and a permanent boot block for standalone operation, allowing seamless reprogramming without disrupting network functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a node's memory is reprogrammed to upgrade software or diagnose faults, then the node can be updated or maintained, but communication continuity is disrupted during the re-flashing process
Solution Approach 1:
The memory is divided into two separate partitions: a first partition for storing original software and a second partition for storing updated software. This segmentation allows the system to switch between partitions without interrupting communication, as one partition can be reprogrammed while the other remains active and functional.
Solution Approach 2:
The updated software is downloaded and stored in the second memory partition before it is needed. This preliminary action allows the system to prepare the update in advance, so that when switching partitions is required, the new software is already ready and communication can resume immediately without interruption.
2Adaptability or versatility
If software components are updated in the code block, then the node functionality is improved, but the node cannot maintain standalone switching operation during updates
Solution Approach 1:
The memory is segmented into a first partition containing the complete software code block and a second partition containing only the boot block. This segmentation allows the second partition to maintain standalone switching capability while the first partition is updated, ensuring that the node can always function independently even during software updates.
Solution Approach 2:
The essential boot block functionality is copied into the second memory partition, creating a minimal but sufficient standalone version. This copy allows the node to maintain independent switching operation even when the main code block in the first partition is being updated or is incomplete.
3Quantity of substance
If the entire memory is used for software storage, then maximum software capacity is achieved, but there is no redundancy for fault tolerance during reprogramming
Solution Approach 1:
The memory is divided into two functional partitions with different purposes: the first partition for comprehensive software storage and the second partition for critical boot functionality and redundancy. This segmentation provides fault tolerance by ensuring that if the first partition fails or is being updated, the second partition contains sufficient information to maintain operation.
Solution Approach 2:
The second memory partition serves as a cushion or backup that is prepared in advance. It contains the boot block that enables standalone operation, providing a safety net that prevents complete system failure during reprogramming operations on the first partition.
Data Source
AI summary
A system and method for reprogramming nodes in an automotive switch fabric network using a diagnostic interface. The switch fabric network includes a plurality of nodes joined by communication links for the transmission of data there between. The plurality of nodes includes at least one target node. The target node includes a processor, a transceiver, and a memory. The memory includes an erasable memory portion and a protected memory portion. The processor in the target node switches from executing instructions in the erasable memory portion to executing instructions in the protected memory portion during a reprogramming period when the target node erases a current software component and stores a new software component in its erasable memory portion. The diagnostic interface is adapted to transmit the new software component to the target node.