alfredoh1234-sandbox issueshttp://opensource.ieee.org/groups/alfredoh1234-sandbox/-/issues2020-01-20T17:57:03Zhttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/16windows installer download confusing2020-01-20T17:57:03ZAlfredo Herrerawindows installer download confusing*Created by: alfredoh1234*
It s not obvious how to download the Windows batch script to Windows and if it is required to have a GitHub account or not*Created by: alfredoh1234*
It s not obvious how to download the Windows batch script to Windows and if it is required to have a GitHub account or nothttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/15How to connect to Serial port on board2020-01-20T17:56:52ZAlfredo HerreraHow to connect to Serial port on board*Created by: jonahgraham*
To connect to the serial port on the target board from the VM you need to do two things:
1. Set rules in VM to give normal user permission (extracted from StackOverflow) this creates a new file.
a. `sudo n...*Created by: jonahgraham*
To connect to the serial port on the target board from the VM you need to do two things:
1. Set rules in VM to give normal user permission (extracted from StackOverflow) this creates a new file.
a. `sudo nano /etc/udev/rules.d/50-myusb.rules`
b. Add this to the file:
```
KERNEL=="ttyUSB[0-9]*",MODE="0666"
KERNEL=="ttyACM[0-9]*",MODE="0666"
```
c. Save and exit
2. Connect the USB in VirtualBox to the VM
a. Open the VM in VirtualBox - you may need to take it out of headless mode to do this
b. From Devices menu -> USB -> Check "ARM DAPLink ..."
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/13Running with older Virtualbox, other VM software and other operating systems2020-01-20T17:56:00ZAlfredo HerreraRunning with older Virtualbox, other VM software and other operating systems*Created by: jeremybennett*
# Ubuntu
## Virtualbox
I was able to get the OVA image working with Ubuntu 17.10 and VirtualBox 5.1.34. You will need the Virtualbox extension pack:
```
sudo apt install virtualbox-ext-pack
```
I don't...*Created by: jeremybennett*
# Ubuntu
## Virtualbox
I was able to get the OVA image working with Ubuntu 17.10 and VirtualBox 5.1.34. You will need the Virtualbox extension pack:
```
sudo apt install virtualbox-ext-pack
```
I don't get a usable console, but with the default NAT settings I can
connect over SSH:
```
ssh -X -A user@192.168.56.101
```
which means I can then fire up Eclipse from the command line.
## Virtual Machine Manager
VMM cannot yet handle OVA files. However the OVA image is just a tar of a file image and some settings. Untar the OVA and you get a vmdk file, which VMM can convert and use.
# Fedora
## Virtualbox
We couldn't get the OVA image to work on Fedora 27. We can get Virtualbox to run, but when it loads the OVA image, it tries to use some Oracle kernel modules which are not signed.
## Virtual Machine Manager
We used exactly the same approach as with Ubuntu, and the system fired up just fine. However it didn't have a network adapter, so unlike Ubuntu we had no external network connectivity.
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/12Zephyr requires dtc_1.4.6 or higher.2020-01-20T17:55:45ZAlfredo HerreraZephyr requires dtc_1.4.6 or higher.*Created by: jcps07*
Zephyr requires dtc_1.4.6 or higher. You could use the one from Zephyr SDK (not included in VM image) or easily update it with the following commands:
`curl -L http://mirrors.kernel.org/ubuntu/pool/main/d/device-...*Created by: jcps07*
Zephyr requires dtc_1.4.6 or higher. You could use the one from Zephyr SDK (not included in VM image) or easily update it with the following commands:
`curl -L http://mirrors.kernel.org/ubuntu/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-1_amd64.deb > device-tree-compiler_1.4.7-1_amd64.deb`
`sudo apt install ./device-tree-compiler_1.4.7-1_amd64.deb`http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/11Cannot ssh to the VM from Windows host2020-01-20T17:55:31ZAlfredo HerreraCannot ssh to the VM from Windows host*Created by: MMI*
The VM appears to create the host only interface with an IP of 192.168.56.101.
However, ssh simply hangs and there's no evidence that VirtualBox set up an interface/route/whatever on the Windows side on that network.
...*Created by: MMI*
The VM appears to create the host only interface with an IP of 192.168.56.101.
However, ssh simply hangs and there's no evidence that VirtualBox set up an interface/route/whatever on the Windows side on that network.
Windows ipconfig tells me:
`Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.156.233
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :`
**Solution**:
The problem here is that I had VirtualBox misconfigured... to fix, in the virtualbox manager GUI:
File->Host Network Manager...
Then change the properties for the VirtualBox Host-Only Ethernet Adapter to "Configure Adapter Automatically"
All good for me after thathttp://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/10https://open-isa.org/get-started/ refers to old Eclipse installation2020-01-20T17:55:13ZAlfredo Herrerahttps://open-isa.org/get-started/ refers to old Eclipse installation*Created by: jonahgraham*
The https://open-isa.org/get-started/ has installation instructions for Eclipse, but refers to an old Eclipse that is a bit harder to get working properly.
What this repo installs in the VM is a newer Eclip...*Created by: jonahgraham*
The https://open-isa.org/get-started/ has installation instructions for Eclipse, but refers to an old Eclipse that is a bit harder to get working properly.
What this repo installs in the VM is a newer Eclipse with the GNU MCU tools already bundled.
https://github.com/openhwgroup/riscv_vm/blob/407a8d444f8a05ab21df1a68bcae4a9a4aaf0900/bin/eclipse-mcu_install.sh#L40
I recommend that toolset be used by anyone not using the VM, get it here: https://github.com/gnu-mcu-eclipse/org.eclipse.epp.packages/releases/tag/v4.5.1-20190101-2018-12http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/9CMake Error with RISCV32GCC_DIR2020-01-20T17:54:51ZAlfredo HerreraCMake Error with RISCV32GCC_DIR*Created by: martinda*
What should be the value of the `RISCV32GCC_DIR` env var? (I tried installing the VM but could not, so I am following the steps from https://open-isa.org/get-started/ directly).
Commands:
```
cd rv32m1_sdk_r...*Created by: martinda*
What should be the value of the `RISCV32GCC_DIR` env var? (I tried installing the VM but could not, so I am following the steps from https://open-isa.org/get-started/ directly).
Commands:
```
cd rv32m1_sdk_riscv/boards/rv32m1_vega/demo_apps/hello_world/ri5cy/riscvgcc
./build_debug.sh
```
Result:
```
CMake Error at /home/martin/riscv/rv32m1_sdk_riscv/tools/cmake_toolchain_files/riscv32gcc.cmake:23 (MESSAGE):
***Please set RISCV32GCC_DIR in envionment variables***
Call Stack (most recent call first):
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:91 (include)
CMakeLists.txt
CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
make: *** No targets specified and no makefile found. Stop.
```
http://opensource.ieee.org/alfredoh1234-sandbox/riscv_vm/-/issues/1Host-only port preventing VM to start on Windows host2020-01-20T17:54:04ZAlfredo HerreraHost-only port preventing VM to start on Windows host*Created by: alfredoh1234*
The OVA-appliance image has two ethernet ports configured:
* **enp0s03** is a NAT port used to connect to the internet, but **NOT** the host
* **enp0s8** is a Host-only port used to communicate with ...*Created by: alfredoh1234*
The OVA-appliance image has two ethernet ports configured:
* **enp0s03** is a NAT port used to connect to the internet, but **NOT** the host
* **enp0s8** is a Host-only port used to communicate with the host to enable the X11 forwarding over ssh
* If the VM fails to launch after importing the *.ova appliance image, look at the logs by selecting:
- [Machine]->[Show Log…] from the VirtualBox menu
- or with the keyboard shortcut [Ctrl+L].
* Look for the an error message that starts with “Failed to open/create the internal network…”.