Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 23 subscribers
  • Views 1133 views
  • Users 0 members are here
Related

Riotboard USB driver for Windows (Eclipse)

Former Member

I have been following the tutorial here to get up and started with Eclipse and the Riotboard - however, one critical problem is that Windows 7 cannot find a device driver for RIOT-MXSOLO. It finds the portable storage driver, but not the driver required for debugging in Eclipse (i.e., it appears with an exclamation mark under "Other Devices" in device manager. It appears fine under "Portable Devices", and works fine as a removable drive). Any help would be greatly appreciated!

  • 0

    Hi Kenji,

     

    • What do you have your DIP switches set to?
    • Have you tried searching Windows Update for a driver?
    • Can you open device manager, open up the 'RIOT-MXSOLO' you have listed, go to the 'details' tab, from the dropdown select 'Hardware Ids' and then provide the details?

    (It should start with PCI\VEN_).

     

    This will help to identify what scenario you're in and whether or not it identifies as the same board I have here; I could then possibly help to provide a driver or point to where it is or try to replicate the problem.

     

    Thanks.

  • 0 in reply to cstanton

    Hi Christropher,

     

    I found the solution overnight - simple, but not straightforward if you aren't already up with Android development! I had to manually install the google ADT driver, found in the android SDK (adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver). It is essential that this is put into the tutorial. Thanks for the prompt reply to my question though!

     

    One other question you may be able to help with - how do I go about accessing the expansion port (GPIO) from within Android?

     

    Thanks again.

  • 0 in reply to Former Member

    Dear Kenji,

     

    I don't know. I suspect that you'll have to read data from a sys device. Working out which one is a journey of discovery that you'll have to take because I don't have any documentation that'll point me in the right direction.

     

    Once I've re-acquired a debug cable I'll be able to have a look around on the RIoTboard myself. I imagine that you've already googled around for an answer?

     

    This seems to be an area that's lacking in information; a pointer would be this Google Group post I've found with some reflection on how this is handled with the BeagleBone Black but this question on StackOverflow goes into better detail..

     

    Hopefully the version of Android on the RIoTboard has been compiled to expose the GPIO.