Rack-based BlueBox supports Continuous Integration of embedded software

June 29, 2021 // By Nick Flaherty
Rack-based BlueBox supports Continuous Integration of embedded software
Installing the BlueBox iC5000/iC5700 CI in test racks enables continuous integration of embedded software with hardware debugging as a natural part of test automation

iSystem in Germany has launched a rack-based version of its BlueBox hardware for remote debugging and continuous integration (CI) of embedded software.

The iC5000/iC5700 CI adds hardware debugging into Continuous Integration (CI) infrastructures. Test racks with multiple hardware setups, each consisting of the embedded target hardware and the iC5000/iC5700 CI give globally distributed development and test teams shared access to hardware debugging capabilities within the CI setup.

Continuous Integration is a software development practice which allows developers to regularly submit their newly generated code to a code repository. A CI Software Tool starts an automated build and test process and provides developers with a timely feedback on the functionality of their code, adding to the team’s learning curve and increasing code quality.

However, to test as close as possible to the real hardware, tests often must be performed on the target hardware itself to safeguard the end products’ function as well as accurate timing behavior of the application.

Providing the CI capability requires a combination of BlueBox hardware, software and consulting services on how to setup the hardware and software of a CI infrastructure, unburdening the individual developer from complex hardware setups on the desk.

The iC5000/iC5700 CI was designed to be implemented in a CI rack setup and can be combined with iSystem’s winIDEA and testIDEA tools so the interfaces and automation capabilities can act as a target test framework. These stimulate functions, read values from a running target in a non-intrusive way, do fault injection and more.

Using trace technology, the hardware debugger supports complex test scenarios that cannot be implemented with conventional software testing tools. Tracing can be used to test the performance of the embedded software and handle timing analysis and code profiling.


Related articles

Other articles on eeNews Europe

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.