Adding a test action to an existing peripheral is very straightforward providing the following steps are adhered to:

1. Write the action in the appropriate peripherals validation/system/soruce/actions/ directory, using the standard framwork function header and returning an avSYS_eTestResponse.
2. Create a header file for the action in the same directory.
3. If it is required to run the action on its own, ensure that default.c is modified appropriately (see FAQ "Debugging a single test").  If default.c isn't modified then the test will be run automatically as part of its 'test level' group.
4. Re-build the test code - the -clean switch shouldn't be necessary unless the pmap file or peripherals_list have been modified.

Back to FAQs index