Details for testcase: Install VisionFive



BugReport a bug against the content of this testcase
ID1754
TitleInstall VisionFive
LinkNo link provided
Part of testsuitesVisionFive

RevisionWritten on the 2022-07-27 18:47 by brian-murray
Text

The scope of this test is to ensure that riscv64+visionfive image boots from SD card on StarFive VisionFive board

Flash downloaded image onto SD card
You can use Gnome Disks app to restore img.xz onto the SD card
Alternatively you can use xz -d to decompress, and then dd to copy the image to the SD card
Connect networking, serial console to the board
Ethernet cable for networking
FTDI adapter for serial console (pinout available here: https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive...)
Connect to the serial console
sudo screen /dev/ttyUSB1 115200
Power on the board
You should see U-BOOT menu
It should then boot GRUB after a delay
You should see GRUB menu
It should then boot the default kernel after a delay
After a while cloud-init will run
Then one will be able to login
Login and change password
Login using ubuntu for both username and password
Reenter ubuntu password again
Set new password
Confirm the new password
Perform WiFi testing
Make sure the WiFi device is enabled:
$ sudo apt install network-manager
$ nmcli radio wifi
enabled
List AP:
$ nmcli dev wifi list
Perform generic testing
Check that apt update works
Run any command that is not installed, check that command-not-found recommends things to install
e.g. hello
Install a package and check that it works, e.g. hello
Perform snap testing
Install a snap and check that it works, e.g. hello
Perform HDMI testing
Plug an HDMI cable and make sure a prompt asking for login appears on the screen
Perform USB test
Plug a keyboard in and enter the login/password
Perform Bluetooth testing
Add the RISC-V PPA:
$ sudo add-apt-repository ppa:ubuntu-risc-v-team/release
$ sudo apt update
Install the required packages:
$ sudo apt install linux-firmware-starfive brcm-patchram-plus-starfive
The installation may fail because the Bluetooth is flaky but the service installed by the brcm-patchram-plus-starfive package takes care of retrying
Check the brcm-patchram-plus-starfive.service status:
$ sudo systemctl status brcm-patchram-plus-starfive.service
Loaded: loaded (/lib/systemd/system/brcm-patchram-plus-starfive.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-06-22 13:42:33 UTC; 32min ago
...
Additionally, you can check that the Bluetooth controller appears:
$ bluetoothctl
Agent registered
[CHG] Controller 70:4A:0E:95:C7:1B Pairable: yes
Note that the bluetooth requires GPIO toggling so if that works, we consider GPIO to work too.
Reboot
The board should reboot normally
Poweroff
Console messages should reach poweroff target
There should be final kernel dmsg powering off
Manually turn power-off from the board

If all actions produce the expected results listed, please submit a 'passed' result.
If an action fails, or produces an unexpected result, please submit a 'failed' result and file a bug. Please be sure to include the bug number when you submit your result.

RevisionWritten on the 2022-07-27 18:43 by brian-murray