{"id":1181,"date":"2024-11-25T11:42:29","date_gmt":"2024-11-25T10:42:29","guid":{"rendered":"https:\/\/itb-solutions.de\/?page_id=1181"},"modified":"2025-05-27T08:06:24","modified_gmt":"2025-05-27T06:06:24","slug":"hilmux","status":"publish","type":"page","link":"https:\/\/itb-solutions.de\/en\/produkte\/hilmux\/","title":{"rendered":"HILmux"},"content":{"rendered":"

Testautomation and Quality assurance<\/p>\n\n\n\n

\n
\n

<\/p>\n\n\n\n

Product describtion<\/h3>\n\n\n\n

In CI test system very often the device under test will be set to a known state by flashing a base software using a debugger before starting the test. Normally the runtime of the test itself is much larger than flashing the base software itself. For running for example smoke tests in an CI environment multiple DUT instances are available and can be used for tests in parallel. The HILmux can be used to connect one debugger instance to multiple DUT instances in such use case.<\/p>\n\n\n\n


HILmux select and establish the connection from one or more Debugger instances to multiple embedded DUT instances and\/ or to different SOC per DUT instance
Measurement of the reference voltage of the different connected DUTs\/ SOCs to get their power status
Use the HILmux to repair a DUT within the testfarm which has been \u201eupdate bricked\u201c after running a failed test. Just select the Debugger connection to the \u201ebricked\u201c DUT using the HILmux to perform a developer flash.
Controllable over USB<\/p>\n\n\n\n

Features<\/h4>\n\n\n\n

For development and measurement purposes \u201especial tools\u201c are available to readout and\/ or change memory regions within the DUT. Those tools use the same debugg interface like a \u201eclassic debugger\u201c. If these \u201especial tools\u201c are part of your automated tests HILmux gives you the flexibility to connect the \u201especial tool\u201c or the \u201eclassic debugger\u201c to the DUT.
Very often an integration test combining many different embedded control units connected to each other is executed in many test cycles to prove the needed stability within this interconnected setup. Here it can happen that you run in the rarely situation that one of the devices within the interconnection hangs. HILmux can is this case remotely setup a debugger connection within the complex testsetup to the DUT within the integration test setup to debug the problem remotely at the affected embedded control unit.<\/p>\n\n\n\n

On-demand <\/h4>\n\n\n\n