Pixhawk 2 Intel Edison Setup of FlytOS


#1

I’m tying to get the FlytOS installed onto my Intel Edison connected to my Pixhawk 2
I got a Serial Connection to my Edison uname -r shows 3.10.98-poky-edison+
lsusb shows
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But there isn’t a device called sda*

After I’ve installed 3.10.17-yocto-standard-r2
now lsusb shows nothing
and also no device called sda
Connected via USB OTG Cable an USB Stick
Alternativ connected a External Powered USB Hub via USB OTG Cable
Connected a USB Stick, USB HDD to that nothing…

Please Suggest an option to install FlytOS


#2

Hi,

I hope you have Jubilinux pre-installed in your device. Moreover, please attach a pic of your setup. I am stating the obvious, but I hope you have powered up edison via its dedicated power supply, and not via its USB port.


#3

I have Jubilinux installed. Powered the Pixhawk by external power source.
the output of dmesg is:

[ 8.965350] intel_scu_watchdog_evo: watchdog_stop [ 9.338016] EXT4-fs (mmcblk0p5): warning: mounting unchecked fs, running e2fsck is recommended [ 9.339054] EXT4-fs (mmcblk0p5): mounted filesystem without journal. Opts: (null) [ 109.838409] pmic_ccsm pmic_ccsm: USB ID Removed. Notifying OTG driver [ 109.898179] dwc3-host dwc3-host.2: remove, state 4 [ 109.898232] usb usb2: USB disconnect, device number 1 [ 109.902916] xHCI xhci_drop_endpoint called for root hub [ 109.902941] xHCI xhci_check_bandwidth called for root hub [ 109.904157] dwc3-host dwc3-host.2: USB bus 2 deregistered [ 109.907373] dwc3-host dwc3-host.2: remove, state 4 [ 109.907422] usb usb1: USB disconnect, device number 1 [ 109.908000] xHCI xhci_drop_endpoint called for root hub [ 109.908020] xHCI xhci_check_bandwidth called for root hub [ 109.915328] dwc3-host dwc3-host.2: USB bus 1 deregistered [ 113.774063] pmic_ccsm pmic_ccsm: USB ID Detected. Notifying OTG driver [ 114.639504] dwc3-host dwc3-host.2: xHCI Host Controller [ 114.639995] dwc3-host dwc3-host.2: new USB bus registered, assigned bus number 1 [ 114.640248] dwc3-host dwc3-host.2: irq 34, io mem 0xf9100000 [ 114.640388] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 114.640411] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.640431] usb usb1: Product: xHCI Host Controller [ 114.640450] usb usb1: Manufacturer: Linux 3.10.98-poky-edison dwc-xhci [ 114.640469] usb usb1: SerialNumber: dwc3-host.2 [ 114.642095] xHCI xhci_add_endpoint called for root hub [ 114.642117] xHCI xhci_check_bandwidth called for root hub [ 114.643666] hub 1-0:1.0: USB hub found [ 114.643719] hub 1-0:1.0: 1 port detected [ 114.644707] dwc3-host dwc3-host.2: xHCI Host Controller [ 114.661477] dwc3-host dwc3-host.2: new USB bus registered, assigned bus number 2 [ 114.661665] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 114.661690] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.661710] usb usb2: Product: xHCI Host Controller [ 114.661729] usb usb2: Manufacturer: Linux 3.10.98-poky-edison dwc-xhci [ 114.661748] usb usb2: SerialNumber: dwc3-host.2 [ 114.667184] xHCI xhci_add_endpoint called for root hub [ 114.667208] xHCI xhci_check_bandwidth called for root hub [ 114.667500] hub 2-0:1.0: USB hub found [ 114.667548] hub 2-0:1.0: 1 port detected [ 176.068735] perf samples too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

lsusb shows:
root@jubilinux:/home/edison# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Could somebody please tell me if the pixhawk 2 could work with USB OTG?

Thank you in advance
Tim Schmitz


#4

Yes, it should.

Do you still not see any sda device in ls /dev ?


#5

Hi guys,
I’m having the same problem as well. Flashed the Edison with Jubilinux and tried mounting the USB stick using an OTG cable but it doesn’t seem to show up in /dev. I know the OTG cable works because when its plugged in, the error -99 goes away via the lsusb command. However, no SDA under /dev. I’ve tried this via the USB power on the Pixhawk Cube as well as though the drone battery itself but no luck either way.


#6

Could it be possible that instead of showing up as /dev/sda, it is being represented by some other device id. Do you see /dev/usb? or /dev/disk? kindly check them and post.


#7

Maybe the answer is that the OGT connection is broken at intel Edison


#8

Here is the contents of /dev. There isn USB drive even though the OTG and USB stick are inserted.

char loop-control ram11 tty16 tty45 ttyPTI1
console mapper ram12 tty17 tty46 uhid
cpu mcelog ram13 tty18 tty47 uinput
cpu_dma_latency mem ram14 tty19 tty48 urandom
disk mid_ipc ram15 tty2 tty49 usbmon0
fd mmcblk0 ram2 tty20 tty5 usbmon1
full mmcblk0boot0 ram3 tty21 tty50 usbmon2
fuse mmcblk0boot1 ram4 tty22 tty51 vcs
i2c-1 mmcblk0p1 ram5 tty23 tty52 vcs1
i2c-2 mmcblk0p10 ram6 tty24 tty53 vcs2
i2c-3 mmcblk0p2 ram7 tty25 tty54 vcs3
i2c-4 mmcblk0p3 ram8 tty26 tty55 vcs4
i2c-5 mmcblk0p4 ram9 tty27 tty56 vcs5
i2c-6 mmcblk0p5 random tty28 tty57 vcs6
i2c-7 mmcblk0p6 rfkill tty29 tty58 vcsa
iio:device0 mmcblk0p7 rtc tty3 tty59 vcsa1
iio:device1 mmcblk0p8 rtc0 tty30 tty6 vcsa2
initctl mmcblk0p9 shm tty31 tty60 vcsa3
input mmcblk0rpmb snd tty32 tty61 vcsa4
intel_sst_ctrl mqueue spidev5.1 tty33 tty62 vcsa5
kmem net stderr tty34 tty63 vcsa6
kmsg network_latency stdin tty35 tty7 vga_arbiter
kvm network_throughput stdout tty36 tty8 vhost-net
log null tty tty37 tty9 watchdog
loop0 nvram tty0 tty38 ttyGS0 zero
loop1 port tty1 tty39 ttymcu0
loop2 pti tty10 tty4 ttymcu1
loop3 ptmx tty11 tty40 ttymcu2
loop4 pts tty12 tty41 ttyMFD0
root@jubilinux:~#


#9

Thanks @7IM, for your insight. This could well be the reason why it is not working on newer Intel Edison boards. Meanwhile, let me search how to flash edison via any other approach.


#10

Hi there,

You can send the image over the network! First install openbsd-netcat (don’t remember the exact package name for Ubunut/Debian but it is in the repos. Use apt search to find it), after that you can pipe the image to a network connection like this:

On the Edison

nc -l 1337 | dd of=/dev/mmcblk0 bs=128K oflag=direct

On your main computer where the extracted image is located:

pv imagename.img | nc $IP_OF_EDISON 1337

That’s it! pv will give you a nice status update about how much data has already been send and also the current speed at which the data is transfered. If you don’t need this you can use cat. In our case it took around 30-45 Minutes to complete the transmission via WiFi!

Cheers,
Matthias


#11

Thanks @xvzf for your solution. I would definitely try this out.


#12

Thanks xvzf. I will try this too.


#13

@bg3009 and @7IM,

We recently updated our edison image and improved our documentation which would surely remove the problems faced by you. I would request you to try it again.