Software Testing for a Fixed Metal Case System

Question

I am writing a C ++ project for an embedded system without OS support; almost no library support. Very bare metal. Consequently, the fair amount of my code is closely related (for example, software trigger interrupts and the layer directly above them). A.

Part of what I'm doing is related to reconfiguring the serial port, which leads to a simultaneous change at the end of the PC (end of the interface) and the microprocessor (end of action). Until now, I understand myself well in the super-cautious development of the incremental type (separately). However, I would like to be more confident that my code works in an engineering sense.

What methodologies / framework would you recommend for this kind of situation?

Edit:

I am using AMD186 ES on an ACore86 board made by Tern, Inc. Compiler: Paradigm, free version (comes with board). Unfortunately, I have no way to change what I'm working on.

Answer 1

The lack of infrastructure in bare metal environments is quite complicated. I would recommend you focus on debugging tools. Even with great care and excellent methodology, you will need the ability to debug things.

gdbagent. , . gdb gdbagent . , , gdbagent , , . , .

, , JTAG. gdbagent , gdbagent . , . JTAG , . Corelis , Abatron.

Answer 2

, , .

. : http://www.hitex.us/products.html?con_186.html~content

Answer 3

, - , . JTAG . uart ( ) .

Answer 4

-, , - .

, .

-.

SRAM unit test.

, .

-, USB.

, , .

Answer 5

, , , ++ , "" C . - #defined -, " ". clunkier, , , .