This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
civilinfrastructureplatform:ciptestingreferencetestcases [2018/06/07 15:09] rajmarshall [Prerequisites:] make it board independent |
civilinfrastructureplatform:ciptestingreferencetestcases [2018/06/11 10:38] rajmarshall [Procedure:] correct formatting |
||
---|---|---|---|
Line 284: | Line 284: | ||
* An IWG20M that is powered up, connected to the LAN with an ethernet cable and connected to the host machine with a USB cable. | * An IWG20M that is powered up, connected to the LAN with an ethernet cable and connected to the host machine with a USB cable. | ||
* A locally built CIP kernel and initramfs. | * A locally built CIP kernel and initramfs. | ||
- | * A Remote Power on Switcher - we have tested with... // - need connection info in the board page// | + | * A Remote Power on Switcher - see [[renesasboard|Renesas IWG20M]] for these details. |
==== Procedure: ==== | ==== Procedure: ==== | ||
Line 382: | Line 382: | ||
* A working CIP Board-at-Desk Single-Developer (B@D) Virtual Machine | * A working CIP Board-at-Desk Single-Developer (B@D) Virtual Machine | ||
* A Beaglebone Black or a Renesas IWG20M board that is powered up, connected to the LAN with an ethernet cable and connected to the host machine with an FTDI cable. | * A Beaglebone Black or a Renesas IWG20M board that is powered up, connected to the LAN with an ethernet cable and connected to the host machine with an FTDI cable. | ||
- | * A built kernel for the appropriate board (see Test #3) | + | * A built kernel for the appropriate board (see Test #3 or #5 depending upon your board) |
* The board has a current successful health check (it is marked as online in LAVA) | * The board has a current successful health check (it is marked as online in LAVA) | ||
Line 394: | Line 394: | ||
In the LAVA web interface, click on API->Authentication Tokens and then on the 'new' button, | In the LAVA web interface, click on API->Authentication Tokens and then on the 'new' button, | ||
give it a description and then click the 'View Token Hash' button and copy the displayed hash value. | give it a description and then click the 'View Token Hash' button and copy the displayed hash value. | ||
- | Then ''lava-tool auth-add http://lavauser@localhost:8080/RPC2 | + | Then: |
+ | '' vagrant@guest:~/git-repos/linux-cip$ **lava-tool auth-add http://lavauser@localhost:8080/RPC2** '' | ||
Paste token for http://lavauser@localhost:8080/RPC2/: **paste token - which will not be echoed** | Paste token for http://lavauser@localhost:8080/RPC2/: **paste token - which will not be echoed** |