BSP test-report template: Difference between revisions

From DDCIDeos
Jump to navigationJump to search
← Older edit
Pzick@ddci.com (talk | contribs)
426 edits
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 7: Line 7:
# From Deos-Bundles:
# From Deos-Bundles:
#* deos-maintainer-tools <version>
#* deos-maintainer-tools <version>
# Jupiter Baseline installed test components:
# <distribution> Baseline installed test components:
#* <platform>-1.3.0
#* <platform>-<major>.<minor>.<debug>
#* <platform>-dev-kit-1.3.0
#* <platform>-dev-kit-<major>.<minor>.<debug>
#* bsp-examples-1.4.0
#* bsp-examples-<major>.<minor>.<debug>
#* deos653p1-runtime 5.8.1
#* deos653p1-runtime-<major>.<minor>.<debug>
# There are no regression tests for these components, so ad hoc testing was used. Testing performed on <targetName_on_target_Farm>:
# There are no regression tests for these components, so ad hoc testing was used. Testing performed on <targetName_on_target_Farm>:
## In OpenArbor, created the platform project in accordance with BSP User Guide (confirm addresses in U-Boot match the UG).
## In OpenArbor, created the platform project in accordance with BSP User Guide (confirm addresses in U-Boot match the UG).
Line 25: Line 25:
##* BSP: psio-print
##* BSP: psio-print
##* BSP: ext-clock-sync
##* BSP: ext-clock-sync
##* pcie-scanner  
##* pcie-scanner (if supported).
##* Deos653: demo653_workspace
##* Deos653: demo653_workspace
##* <Any other examples relevant to this release/bsp>
##* <Any other examples relevant to this release/bsp>
## Following the Hello-world example in the OpenArbor UG, tested:
## Following the Hello-world example in the OpenArbor UG, tested:
##* Video Steam
##* Video Stream
##* Update Target Load
##* Update Target Load
##* Mode changes  
##* Mode changes  
##* Status monitor  
##* Status monitor  
##* GDB  
##* GDB  
##* MLD  
##* MLD (No longer supported on Kismet and up)
## Ran the timemap-analytics and observed the results to be satisfactory:
## Ran the timemap-analytics and observed the results to be satisfactory:
##* Source found at: https://deos.ddci.com/scm/Deos/products/desk/python-tools/branches/mainline/code/timemap-analytics.py
##* Source found at: https://deos.ddci.com/scm/Deos/products/desk/python-tools/branches/mainline/code/timemap-analytics.py
##* Results at ./tm-results.htm
##* Switches used following the file name to show tick and window timemap analytics >> "--tick --window"
##* Results at ./timemap-results.htm
## Ran the timemap-analytics for ext-clock-sync and observed the results to be satisfactory:
##* Source found at: https://deos.ddci.com/scm/Deos/products/desk/python-tools/branches/mainline/code/timemap-analytics.py
##* Switches used following the file name to show time shifts and user events >> "--ext-clock"
##* Results at ./ext-clock-results.htm
## Built the dev-kit and compared the output against the content in the desk.
## Built the dev-kit and compared the output against the content in the desk.


Line 44: Line 49:
* One warning is reported in dev-kit as follows, which is expected:
* One warning is reported in dev-kit as follows, which is expected:
** arm-eabi-ld: warning: section `.bss' type changed to PROGBITS
** arm-eabi-ld: warning: section `.bss' type changed to PROGBITS
[[Category:BSP]]

Latest revision as of 17:43, 28 January 2025

The following is a sample for a BSP that does not have any formal tests. Edit this page and copy the contents (excluding this paragraph) into a test-report.txt file. Anything that is not supported on the BSP would be deleted. Replace everything in <brackets>.

<platform>-<major>.<minor>.<debug> <Tester First and Last Name>, <yyyy-mm-dd>


What was done:

  1. From Deos-Bundles:
    • deos-maintainer-tools <version>
  2. <distribution> Baseline installed test components:
    • <platform>-<major>.<minor>.<debug>
    • <platform>-dev-kit-<major>.<minor>.<debug>
    • bsp-examples-<major>.<minor>.<debug>
    • deos653p1-runtime-<major>.<minor>.<debug>
  3. There are no regression tests for these components, so ad hoc testing was used. Testing performed on <targetName_on_target_Farm>:
    1. In OpenArbor, created the platform project in accordance with BSP User Guide (confirm addresses in U-Boot match the UG).
    2. Updated boot image onto tftp server with latest downloaded from the installer
      • Tested release boot named deosBoot-rel-<yyyy>-<mm>-<dd>.bin
      • Tested debug boot named deosBootdbg-rel-<yyyy>-<mm>-<dd>.bin.
    3. Build a Deos Bootable Image according to the user guide (both methods) and updated the image and symbolic links used in tftp server to ensure both built and booted. Image is named:
      • composite-rel-<yyyy>-<mm>-<dd>.darc
    4. Tested both release and debug pals by ftp putting the other variant.
      • Captured tick count start and end over 5 minutes and confirm appropriate delta
    5. The following examples were integrated and put to the tftp server for testing:
      • BSP: pal-extension
      • BSP: psio-print
      • BSP: ext-clock-sync
      • pcie-scanner (if supported).
      • Deos653: demo653_workspace
      • <Any other examples relevant to this release/bsp>
    6. Following the Hello-world example in the OpenArbor UG, tested:
      • Video Stream
      • Update Target Load
      • Mode changes
      • Status monitor
      • GDB
      • MLD (No longer supported on Kismet and up)
    7. Ran the timemap-analytics and observed the results to be satisfactory:
    8. Ran the timemap-analytics for ext-clock-sync and observed the results to be satisfactory:
    9. Built the dev-kit and compared the output against the content in the desk.

Results:

  • All tests ran and passed as expected.
  • One warning is reported in dev-kit as follows, which is expected:
    • arm-eabi-ld: warning: section `.bss' type changed to PROGBITS
Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=BSP_test-report_template&oldid=68863"