I know this will sound like a rookie talking, but that is pretty much my 
level with BBB.  I assumed you meant to remote into the BBB when it was 
running the bSNES image and run that command.  I thought it would just be 
plug and play with an ethernet cable and putty, but I could never make that 
connection connect for some reason. 

Then I took out the uSD card and only had the miniUSB cable connected.  I 
could remote in then and run that command, but nothing was showing up other 
than the root hub with the controller plugged in.

So I just plugged both controllers into my Ubuntu PC and ran it, thinking 
that they should appear the same on any linux device.  Here's what I saw 
with everything else.  The blank lines are the controllers:

*Bus 001 Device 016: ID 058f:6465 Alcor Micro Corp. *
*Bus 003 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse*
*Bus 004 Device 004: ID 12bd:d015  *
*Bus 004 Device 003: ID 12bd:d012  *
*Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub*
*Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub*
*Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub*
*Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub*

Let me know if that is not quite what you had in mind :)  Feel free to talk 
as if I'm linux impaired. 

On Thursday, January 30, 2014 10:27:21 AM UTC-5, Andrew Henderson wrote:
>
> Glad that you found the Android image useful!  If you have the chance, can 
> you plug in each of those gamepads that you have, run "lsusb", and send me 
> the results?  I suspect that they will report as different gamepads, even 
> though the branding is the same.  I'd eventually like to have an sqlite 
> database that has USB ID strings and button mappings in it so that 
> BeagleSNES will automatically configure your controller if it is one listed 
> in its database.  But, if your two gamepads both report exactly the same 
> and still have different button mappings, that means the database approach 
> might not work.
>
> The 3.12/3.13 kernels have much better USB support, so USB gamepads should 
> work far better (especially when hotplugging).  But, they aren't quite 
> there yet.  When they are, I'll move both the BBB and BB-xM over to those 
> kernels.
>
> Andrew
>
> On Tuesday, January 28, 2014 11:17:09 PM UTC-5, Scott Paul wrote:
>>
>> I'll keep an eye out for the update.  In the meantime, I bought a second, 
>> different controller and everything works now.  Connecting the controller 
>> has been a little spotty compared to the other one that the start and 
>> select buttons don't work on, but it works.  I cycled the power a couple 
>> times, plugged and unplugged it and it eventually worked.  Once it did work 
>> it seemed more consistently connected after a power cycle.  The other 
>> remote didn't have that issue.  Oh well.  It works.
>>
>> I've only tried a few games quickly, but I like it.  For anyone else 
>> ordering through Amazon...
>>
>> This is where I ordered the one that worked: 
>> http://www.amazon.com/gp/product/B0058FN036/ref=oh_details_o02_s00_i00?ie=UTF8&psc=1
>> Sold by *Hitgaming Video Games 
>> <http://www.amazon.com/gp/help/seller/at-a-glance.html?ie=UTF8&isAmazonFulfilled=1&seller=A3O4XUIPWQ2IWK>*
>>
>> This is where I ordered the one that caused me problems: 
>> http://www.amazon.com/gp/product/B0034ZOAO0/ref=oh_details_o03_s00_i00?ie=UTF8&psc=1
>> Sold by *Hitgaming Video Games 
>> <http://www.amazon.com/gp/help/seller/at-a-glance.html?ie=UTF8&isAmazonFulfilled=1&seller=A3O4XUIPWQ2IWK>*
>>
>> Good luck getting the right one :)    
>>
>> Anyways, thanks Andrew.  I also got the Android 4.2.2 running on the BBB. 
>>  Good work on that too!  That also worked after I tried imaging the disk 
>> from the Ubuntu machine.
>>
>>
>> On Sunday, January 26, 2014 4:02:54 PM UTC-5, Andrew Henderson wrote:
>>>
>>> Yes.  The front-end GUI does not look at that configuration file for 
>>> button mapping.  That is the configuration file for the SNES9X emulator. 
>>>  Part of my work for v0.5 is to pull button mappings from that file.  v0.5 
>>> should give you the following:
>>>
>>> - An additional VFAT partition that houses the config files, ROMs, and 
>>> images.  This way, you can pop the microSD card into your non-Linux PC and 
>>> add ROMs, edit files, etc.
>>> - XML for the games.cfg.  This is using the Expat XML parsing library. 
>>>  This will eliminate most of the common problems, I hope, like the config 
>>> file having to be just-so or DOS end-of-line characters messing things up, 
>>> etc.
>>> - Key mapping from the SNES9X emulator's config file so that you can do 
>>> a custom key mappings.
>>>
>>> I am a PhD student, and I've been working on a papers over the past few 
>>> months, so I haven't been working on BeagleSNES development as much as I 
>>> would like.  I'm still working on it, though, and I'll be getting a release 
>>> out as soon as I can.  Trust me, I don't want to answer mail after mail for 
>>> support when I can release a new version that addresses these issues 
>>> directly!
>>>
>>> Andrew
>>>  
>>>
>>> On Sunday, January 26, 2014 3:13:18 PM UTC-5, Scott Paul wrote:
>>>>
>>>> Hi Andrew.  Is there a short explanation for why I can't quickly edit 
>>>> the "*snes9x.conf.BBB*" file and change the lines 
>>>>
>>>>
>>>> *J00:B8 = Joypad1 SelectJ00:B9 = Joypad1 Start*
>>>>
>>>> to something like 
>>>>
>>>>
>>>> *J00:B6 = Joypad1 SelectJ00:B7 = Joypad1 Start*
>>>>
>>>> to effectively test different button mappings? I tried editing them and 
>>>> popping the card back in the BBB but it doesn't seem to do anything.  Does 
>>>> modifying that conf file require a rebuild to take effect?  
>>>>
>>>> When do you hope to release the v0.5?
>>>>
>>>>
>>>> On Friday, January 3, 2014 9:22:19 AM UTC-5, Andrew Henderson wrote:
>>>>>
>>>>> Hey Scott.  I have been away for the holidays and won't be back to my 
>>>>> office with my equipment until the start of next week.  You have 
>>>>> everything 
>>>>> set up correctly, it seems.  The games.cfg looks OK, in any case.  The 
>>>>> problem is that the button numbers for the start and select are hardcoded 
>>>>> in the front-end GUI.  I have a better button mapping scheme on my dev 
>>>>> list 
>>>>> for v0.5 of BeagleSNES, but I can't work on it and get another release 
>>>>> out 
>>>>> until I am able to get back to my equipment.  The short answer is that 
>>>>> you 
>>>>> will require a code change and recompile to get it working for your 
>>>>> particular controller.
>>>>>
>>>>> I have a big laundry list of things that I have been working on that I 
>>>>> want to get out for v0.5, and a few of the items have been delaying me in 
>>>>> getting the release out.  I may just have to bite the bullet and expedite 
>>>>> the more urgent items because a large number of people have received new 
>>>>> BBBs for the holidays and have been filling my inbox with all sorts of 
>>>>> issues regarding gamepads and button mappings.
>>>>>
>>>>> Good work on getting everything working as well as you have so far.  I 
>>>>> should write a book on how to develop the BBB into a standalone appliance 
>>>>> based on all of the feedback and reports that I have received from 
>>>>> everyone 
>>>>> over the last six months...
>>>>>
>>>>> Andrew
>>>>>
>>>>>
>>>>> On Wednesday, January 1, 2014 6:23:41 PM UTC-5, Scott Paul wrote:
>>>>>>
>>>>>> So close...
>>>>>>
>>>>>> I had an old PC sitting around collecting dust so I formatted that to 
>>>>>> Ubuntu 12.04.  I re-did everything from that machine.  Before I started, 
>>>>>> when I plugged in the SD card that I had setup from the Win7 machine 
>>>>>> into 
>>>>>> the Ubuntu machine it seemed to mount the two partitions fine ... but it 
>>>>>> also gave me a pop-up error message about not wanting to mount the drive 
>>>>>> for some reason ... even though I could see both parts.  Anyways, it did 
>>>>>> this each time I mounted the card.  After I reformatted the card with 
>>>>>> the 
>>>>>> beaglesnes image that message has no longer come up.  I have mounted the 
>>>>>> card several more times too.  
>>>>>>
>>>>>> At first it did not work.  Then I took it out of its Adafruit 
>>>>>> case<http://www.adafruit.com/products/1555?gclid=CNGJv-2J3rsCFVLxOgodcRsAeA>and
>>>>>>  tried.  Then it would boot up, give me music, and let me scroll through 
>>>>>> the placeholder's in the default config.  I am certain I tried this 
>>>>>> before 
>>>>>> but it did not matter.  I quickly realized that the molding on the cable 
>>>>>> needed to be cut down.  If I had read adafruit's page closer, I might 
>>>>>> have 
>>>>>> caught that note.  Not happy about that, but it worked.  I think that I 
>>>>>> had 
>>>>>> both a cable problem and a Windows problem, but maybe it was only a 
>>>>>> cable/case problem and I didn't do something else write the time I tried 
>>>>>> that with the Win7 SD card setup.
>>>>>>
>>>>>> I have been at it for a while today, but the problem now is that it 
>>>>>> will not select the games I've added in the menu.  I have tested the 
>>>>>> controller on the Ubuntu machine and can see the start and select 
>>>>>> buttons 
>>>>>> do register.  I have been doing everything in the Ubuntu machine.  The 
>>>>>> pictures are showing up, the text descriptions are updated.  At first I 
>>>>>> had 
>>>>>> 5 games listed so I tried adding 5 more.  Each time the menu list 
>>>>>> updated 
>>>>>> as expected, but pressing start or select doesn't do anything.  The roms 
>>>>>> are all in the rootfs/home/ubuntu/beaglesnes/rom folder.  They are all 
>>>>>> .smc.  I even removed spaces and tried shortening the .smc file names.
>>>>>>
>>>>>> I'm only using one controller.  I can't really think of much else to 
>>>>>> try right now.  Again, I welcome any support.  I attached my games.cfg 
>>>>>> file 
>>>>>> if that helps
>>>>>>
>>>>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to