SystemC: a homogenous environment to test embedded systems
Proceedings of the ninth international symposium on Hardware/software codesign
Adaptive Scenario-Based Object-Oriented Test Frameworks for Testing Embedded
COMPSAC '02 Proceedings of the 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment
A Generic Test and Maintenance Node for Embedded System Test
Proceedings of the IEEE International Test Conference on TEST: The Next 25 Years
Testing Embedded Systems by Using a C++ Script Interpreter
ATS '02 Proceedings of the 11th Asian Test Symposium
An Interaction Testing Technique between Hardware and Software in Embedded Systems
APSEC '02 Proceedings of the Ninth Asia-Pacific Software Engineering Conference
An Undergraduate Program in Embedded Systems Engineering
CSEET '05 Proceedings of the 18th Conference on Software Engineering Education & Training
ACM Transactions on Embedded Computing Systems (TECS)
FIE '98 Proceedings of the 28th Annual Frontiers in Education - Volume 03
Nexos: a next generation embedded systems laboratory
ACM SIGBED Review
Hi-index | 0.00 |
As student numbers in embedded systems lab courses increase, it becomes more and more time-consuming to verify the correctness of their homework and exam programs. Automatic verification can vastly improve the speed and quality of such tests. This paper describes a system that can carry out black-box tests to verify whether the embedded software running on a target system meets predefined requirements. To this aim, we employ a special test board using an ATmega128 microcontroller which is connected to both the target system and to a host computer. Tests can be selected and started remotely, the results are presented to the user on the host. Monitoring and control via Internet is also easily possible. A special meta-language is used to describe the correct behavior of the tested program, and this description is compiled and downloaded to the test system via a standard RS-232 interface, where the test is executed. The same interface is used to control the tests and for transfer of data and end results.