This FAQ only applies to the verification of the new peripheral within the platform.

1. Ensure RTL correctly wired up and Interrupt source assigned

2. Write any test actions in: <peripheral>/validation/system/source/actions
Test actions must follow the structure and format as described in FAQ "PXP - PXP310 - Verification - Adding test actions".

3. Create a CheckState function in same directory
Ensure that a CheckState function is created for this peripheral.  It must follow the same structure as a test action (see FAQ "PXP - PXP310 - Verification - What is a CheckState function?"). If this is another instance of an already existing peripheral then a CheckState function should already exist.

4. Write any necessary drivers in: <peripheral>/validation/system/source/drivers
Drivers do not have to follow the same structure as test actions but should, as a minimum, include an initialisaion function.

5. Ensure new entry in peripherals_list, including: “I <interrupt controller>,<source>”
Peripherals_list must be updated to point to the new peripheral or new instance of an existing peripheral. See FAQ "PXP - PXP310 - Verification - What is peripherals_list?".

6. Make appropriate additions to default.c
The new test actions need only be declared in default.c if you expect to run them in isolation.  If you expect to run the tests automatically via the framework then you do not need to make any changes to default.c.

7. Add line to source_files.txt to ensure test code is found if using command files
If command files are being used then ensure a line pointing to the directory containing the new test actions is added to source_files.txt.

8. Rebuild code using –clean switch to force a rebuild of peripherals_list
-clean will need to be used as there will most likely be a new pmap file or, at the very least, changes to peripherals_list.

New test actions will be automatically included in action sheet and run by framework

Back to FAQs index