System-in-loop testing for ADAS SoCs

A system, comprising:

• a microcontroller that includes:
• multiple destination components including a memory, a control register, and a data modification module (DMM);
• and
• an interface including a table containing entries that map each virtual channel of a set of virtual channels to a particular destination component of the multiple destination components, the interface configured to:
• communicate over the set of virtual channels;
• store, using the table, a first packet received via a first virtual channel of the set of virtual channels in the memory of the multiple destination components;
• and
• receive an update packet via a second virtual channel of the set of virtual channels, in which the second virtual channel is associated with the DMM in a current version of the table;
• wherein the DMM is configured to:
• receive the update packet from the interface, and parse the update packet to determine that, in the current version of the table, a first value of the update packet maps to a destination component that is associated with a particular virtual channel of the set of virtual channels and a second value of the update packet represents a new destination component to be associated with the particular virtual channel;
• and
• cause the interface to modify the current version of the table to generate an update version of the table in which the second value is written in place of the first value to associate the particular virtual channel with the new destination component, such that the system is configured to process a subsequent packet received via the particular virtual channel associated with the first value of the update packet by storing the subsequent packet at the new destination component associated with the second value of the update packet.

A method comprising:

• storing, by an interface and using a table, a first packet received via a first virtual channel of the set of virtual channels at a first destination component of the multiple destination components, the table containing entries that map each virtual channel including the first virtual channel of a set of virtual channels to a particular destination component of the multiple destination components;
• receiving, by the interface, an update packet via a second virtual channel of the set of virtual channels, in which the second virtual channel is associated with the DMM in a current version of the table, the update packet having first and second values;
• providing, by the interface, the update packet to a data modification module (DMM) of the multiple destination components;
• parsing the update packet, by the DMM, to determine that, in the current version of the table, the first value maps to a destination component in a current version of the table that is associated with a particular virtual channel of the set of virtual channels and the second value represents a new destination component to be associated with the particular virtual channel;
• receiving, by the interface from the DMM, the second value extracted from the update packet by the DMM;
• writing the second value to the table to modify the current version of the table to generate an updated version of the table to associate the particular virtual channel with the new destination component;
• and
• in response to receiving a subsequent packet via the particular virtual channel associated with the first value of the update packet, storing the subsequent packet at the new destination component associated with the second value of the update packet.