Ubuntu not seeing poplar board on fastboot


#1

I am having issues getting my linux (Ubuntu) to see the poplar board. I have the board on fastboot 0 and when i run fastboot devices or adb devices nothing is listed.

I am following the directions on:


#2

When you run “fastboot 0” on U-Boot prompt, do you see USB device detected on PC side, something like below on dmesg output?

usb 2-1.4: new high-speed USB device number 7 using ehci-pci
usb 2-1.4: New USB device found, idVendor=18d1, idProduct=d00d
usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.4: Product: USB download gadget
usb 2-1.4: Manufacturer: HiSilicon
usb 2-1.4: SerialNumber: 0123456789POPLAR


#3

How do i check for this message?
Should it appear automatic on the terminal?


#4

Run command ‘dmesg’ on Ubuntu terminal.


#5

I haven’t got the new poplar board (the old one I have doesn’t support fastboot) but I can’t see anything in the docs explaining how to hook up the USB cabling and IIRC the fastboot connection was going to be a little odd for this board.

What is cables have you got connecting your board to your PC?


#6

There is a Type-A-Male to Type-A-Male USB cable shipped with HopeRun Poplar board. Connecting USB2 port of Poplar to host PC using the cable should get you Fastboot.


#7

I do not get that message
I post the whole list here with screenshots.



#8

I am using a micro-USB cable (board) to Type-A-Male USB cable (host). Is that incorrect?


#9

Yes. The micro-USB is simply a serial port with a USB interface. It cannot be used for fastboot or adb.

Note also that if you have the original poplar board (made by Tocoding) it cannot support fastboot at all. You can recognise an original poplar board because it has two (host mode only) USB sockets on the “front” next to the IR receiver.

If you have a new poplar board (made by Hoperun) this double USB socket will have been replaced by a single type A socket (that is OTG capable). This requires a special type A to type A cable to operate in OTG mode.


#10

I have the Tocoding board. How would you recommend loading android onto the board?


#11

Tocoding board fades out from the official support, but you can follow the documents below to try old Android build.


#12

The instruction still has me using the flashing process to get the android build on the board, is there an alternative method to load the android onto the board (if flashing is not enabled).


#13

The documents I gave you will instruct you flash Android images onto eMMC using USB disk, and it doesn’t request fastboot support.


#14

I’m sorry I’m a little confused, this is the same document i initially followed. Are you saying after i get to step 4. Build of ( Compiling userspace ), I should flash andriod image onto eMMC. Is there instructions for doing that? and when i make my image i get a folder with multiple files not one ios file


#15

More specifically: