Why don’t you try downloading the Galileo image from the official website https://www-ssl.intel.com/content/www/us/en/do-it-yourself/downloads-and-documentation.html#galileosoftware ? Also regarding robopeak I found a link you might find helpful, take a look at https://communities.intel.com/thread/57652 .
I tried the SD card image from the official website https://www-ssl.intel.com/content/www/us/en/do-it-yourself/downloads-and-documentation.html#galileosoftware ?
The robopeak monitor also shows "Waiting for signal".
And in robopeak image, I can list rp_usbdisplay in lsmod
root@RoboPeak-Gallieo:~# lsmod | grep rp
rp_usbdisplay 18839 3
fb_sys_fops 12546 1 rp_usbdisplay
syscopyarea 12442 1 rp_usbdisplay
sysfillrect 12582 1 rp_usbdisplay
sysimgblt 12554 1 rp_usbdisplay
Is there any software way to check if galileo board detect the robopeak display well or not?
I’ve found some useful information on this link robopeak/rpusbdisp · GitHub . It seems like the problem you have is related to step 4: verify the driver. Take a look at it and let me know if this helps.
I tried Verify the driver steps
Module Size Used by rp_usbdisplay 18839 2 fb_sys_fops 12546 1 rp_usbdisplay syscopyarea 12442 1 rp_usbdisplay sysfillrect 12582 1 rp_usbdisplay sysimgblt 12554 1 rp_usbdisplay
My dmesg log shows
[ 95.400191] input: RoboPeakUSBDisplayTS as /devices/virtual/input/input2
[ 95.529923] usbcore: registered new interface driver rp-usbdisp
for the log like
[ 1814.173232] rp-usbdisp 4-1:1.0: RP USB Display found (#1), Firmware Version: X.XX, S/N: XXXXXXXXXXX, I don't find it in demsg when the display has been pluged in.
cat /dev/urandom > /dev/fb0
cat: write error: No space left on device
It seems like the display can't be detected. I have tried many usb cables when connecting the display. (microusb from usb host in Galieo to Usb hub to micro usb on robopeak display)
It seems like you don’t have enough space on your board. Try running the command df to see how much of your device’s space is being used. Do you have the standard SD card linux image or have you made any modifications to your image? If you have not made any modifications I’d recommend you to download the new R2 and try again to see if the error was caused by shortage of space. If you have already modified your image and would’t like to erase all your work by changing image you can try this command rm -rf /var/log/journal/* to remove the logs in your device and free up some space.
My image was downloaded from http://www.robopeak.com/docs/doku.php?id=product-rpusbdisp-downloads
Galileo Debian + Yocto SD Card
I don't modify anything and my SD card is 8G
root@RoboPeak-Gallieo:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 3.0G 2.5G 346M 88% /
none 113M 4.0K 113M 1% /dev
/dev/mmcblk0p1 7.5G 6.1G 1.5G 81% /media/realroot
/dev/loop0 3.0G 2.5G 346M 88% /
tmpfs 23M 676K 23M 3% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 46M 148K 46M 1% /run/shm
For downloading the new R2 image, could you share me the url of the image?
Sorry, the R2 image is for the Edison I got confused; anyway, from the df output it seems you are using much of the board’s space. When you connect the display to the board through USB do you see the robopeak logo? Have you tried maybe using another USB cable? Galileo sometimes gives issues with USB 3.0, try using USB 2.0. If the logo doesn’t appear then maybe it’s a driver issue. Have you tried to update the board’s firmware through the IDE? Also, how many fps are you using? Try first with the default that is 16.
When I connect the display to the board through USB, I can see the robopeak logo and then go to waiting for signal.
I tried 3 different USB cables, none of them can work.
And I already update the board’s firmware through the IDE. I also tried USB 2.0 hub, while it still can't work.
For fps , how to track it? I don't modify anything to the image and just try the default set up.
actually I have no specific information to share. I had just connected a display with USB cable to USB host port. A display's SW is 1.0.5. And I used Linux provided by Robopeak.
I may recommend you to check that display is detected as USB device. I mean that USB connection is present. Because it may be that one of USB signals is not connected.
To do this you may use a command lsusb in the terminal window or system("lsusb > /dev/ttyGS0"); in a sketch.