BananaPI-W2 Ubuntu 18.04 New Image Release 2018-09-17

(Justin) #21

I’m using windows 7 but I just remembered that there is another computer in the house with a newer os so I’ll try that cpu now

(Justin) #22

I tried on another computer with windows 7 and it did the exact same thing as my laptop


Is it possible to run this image from SATA SSD?


Hmm are you sure USB button register being pressed while you power on the board?

My exact setup was no SD card inserted, sw4 on 0, USB button pressed. Plugged usb-c cable while still having USB button on w2 pressed. Released button moments after LEDs were all lit up.

You can plug uart at the same time as trying this guide - you will know if it boots as usual (no USB button registered) or you have few short lines (less than 10 characters each - USB button active)

(kaka) #25
bpi-iot-ros-ai login: root
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd: 31: /usr/lib/ubuntu-release-upgrader/release-upgrade-motd: cannot create /var/lib/ubuntu-release-upgrader/release-upgrade-available: Read-only file system
mktemp: failed to create file via template '/var/lib/update-notifier/tmp.XXXXXXXXXX': Read-only file system
run-parts: /etc/update-motd.d/95-hwe-eol exited with return code 1
/usr/lib/update-notifier/update-motd-fsck-at-reboot: 33: /usr/lib/update-notifier/update-motd-fsck-at-reboot: cannot create /var/lib/update-notifier/fsck-at-reboot: Read-only file system

some time hapen this.

(Justin) #26

Wow…now that I followed your directions it is loading the drivers lol

(Justin) #27

My computer was loading the drivers but said “this device cannot start code 10”

(Justin) #28

After loading the spi rom tool my board is bricked. It’s not even registering on my computer now

(Ed) #29

Hi Kamil_S, I followed your instructions, having no SD card, setting sw4 to 0 and keeping the USB button pressed while I connect usb-c to my Windows 10 PC. The red and green LEDs light up and I release the USB button. I run the Kylin usb tool, rtumdfsample.exe, but Device 01 shows a gold gear on a black background, like all the other device icons. I run Device Manager and see “Unknown device” listed under “Other devices”. The details tab shows a value of USB\VID_0BDA&PID_1195\5&2CC31E78&0&1, and no driver. When I go to the Driver tab and attempt to update the driver from C:\Users\Ed\Downloads\bananapi\Kylin_usb_tool_ver.0008.1005811\usb_driver, where I downloaded the software, it reports “Windows was unable to install your Unknown Device”. Then I realized that the driver in the usb_driver folder was still zipped. I unzipped it and tried the update again. This time, it found the Realtek driver and installed for Realtek generic USB Device; however, Device Manager was now listiing it as an unknown USB device and it was still not recognized when I re-ran rtumdfsample.exe. I had to disconnect the w2 from the usb, hold down the USB button and reconnect it to the PC. Now Device Manager shows it as Realtek generic USB class and rtumdfsample.exe shows the Android icon for Device 01.

I’ll now continue with the instructions and see if I can successfully load Ubuntu 18.04, and report back with the results.


Might be I needed power down and plug back as well. Anyway - that was exactly my steps there. Flash SPI rom as in guide. Prepare SD card (flash image via etcher or any image to SD card you find out there) Power down board, plug SD in, switch sw4 to 1 and boot (via USB c or power barrel). It should boot just fine with HDMI working.

(Justin) #31

Ever since I flashed his spi rom tool the board isn’t recognized on my laptop at all unless I do the usb button and when I do that I can flash the spi again but I can’t see what it’s doing via serial any other time

(Ed) #32

Yes, it is now successfully booting Ubuntu 18.04 and displaying via the HDMI port. However, I have no internet connection. When I plug the ethernet cable into the GbE LAN port, only the yellow light on the left flashes. I’ll double-check the cable, but it was working fine with a different device.


At the moment there is only eth0 visible by the system. Issue ifconfig in terminal to see if you have valid IP or ‘ethtool eth0’ to see if it actually detected phisical link. Possibly try another Ethernet port on your w2 (maybe you are plugging in to eth1 that is not working at the moment)

(Justin) #34

Your spirom update has done nothing but brick my 100$ board