I was also worried about the power supply but ruled it out when I continued to have problems when just using USB alone. I wasn't sure about the amperage, but felt it was fine since I wasn't experiencing a voltage drop when connecting the IOIO.
Anyway... I cannibalized a quality power supply that delivers 2.4amps at 7.5volts. That did do the trick! I was immediately able to connect to my Android tablet through both the USB OTG and through a bluetooth dongle. The test app happily blinks the yellow light and there is enough current to charge the tablet - nirvana! I also wiped the IOIO and it has remained connected to my Windows PC as I type this message. So possibly it was a timing issue creating those USB problems I was experiencing. And yes, those problems were occurring while the IOIO was connected only through a standard USB with no power supply. It's so nice to have confidence in a device when one starts to create one's own problems as play begins. It looks like I am finally ready to start playing. Thanks for your help! On Saturday, April 26, 2014 7:11:12 PM UTC-4, Ytai wrote: > > The problems with the Android smell very much like power supply issues. > What is the voltage / current rating on the supply? > I've never seen problems like you're describing with your PC. Is the IOIO > connected to anything other than the PC (power supply, peripherals, etc) or > is it only PC - USB cable - IOIO? > If this is indeed just the IOIO I have no idea what can cause that and it > is the first time I hear of that problem. I don't think it is anything > related to the v5 firmware - the USB stack has not changed. Maybe try a > configuration wipe, in case this is something related to a miscalibrated > oscillator. > > > On Sat, Apr 26, 2014 at 10:12 AM, Gordon Martin > <[email protected]<javascript:> > > wrote: > >> Some success: >> >> Soldering done. I was able to update the firmware. IOIODude now reports: >> >> Hardware version: SPRK0020 >> Bootloader version: IOIO0400 >> Application version: IOIO0500 >> >> But behaviour on my Android devices remains unchanged. I've disabled USB >> debugging. The trim is clockwise. I now see no charging indicators when >> in host mode. I've never seen an accessory dialog. Bluetooth dongles >> still don't light up. >> >> But now I'm getting some strange behaviour on my Windows PC. Before the >> update it wasn't a problem having the IOIO attached for long periods of >> time. Since going to firmware 5, I have a new behaviour. After a few >> minutes windows starts suggesting that I can speed up USB by plugging into >> a 2.0 port, etc. I start getting regular chimes as if USB devices are >> being connected and disconnected. At this point my Logitech keyboard and >> mouse that use a unified 2.4Ghz USB dongle stop working. To get the chimes >> to stop and my keyboard to work, I just have to unplug the IOIO board. (The >> IOIO board is just connected via a standard USB cable.) >> >> I'm at a loss as to where to go now. I haven't found documentation that >> covers this. >> >> :-( >> >> >> On Saturday, April 26, 2014 10:35:20 AM UTC-4, Gordon Martin wrote: >>> >>> Thanks for such a thorough reply! Things are starting to look up. >>> >>> But first to answer your questions... The trimmer is/was fully >>> clockwise. My tablet never got a charging indicator. My phone did get a >>> charging indicator, but it was weird - it would sort of flash the charging >>> indicator on and off. Perhaps that's an indication that the wall wart >>> can't deliver enough current (there were no labels on the wart indicating >>> capabilities, but it isn't petite (an old battery charger)). >>> >>> The PC did recognize the device and I was able to install the drivers >>> and query the IOIO with IOIODude. The results: >>> >>> Hardware version: SPRK0020 >>> Bootloader version: IOIO0400 >>> Application version: IOIO0330 >>> >>> So I guess it is working as expected. I just need to up my game. >>> >>> I'm off to solder on the headers so I can safely short the boot pin and >>> flash this firmware... >>> >>> >>> Thanks again for your help. >>> >>> >>> >>> >>> On Friday, April 25, 2014 7:47:14 PM UTC-4, Ytai wrote: >>>> >>>> Most chances are that your board is OK. >>>> >>>> The best thing to do first is to connect the IOIO to a PC and make sure >>>> it enumerates correctly. Then run ioiodude --port=... versions to check >>>> which firmware versions you have on the board and verify that the board >>>> works in general. If it doesn't, put the IOIO into bootloader mode and >>>> repeat the test. >>>> >>>> Once you have it working with the PC and we verify that you have the >>>> correct firmware on it, we can move on to fixing Android and Bluetooth. >>>> >>>> A few random comments on what the problem may be: >>>> >>>> - ADB mode does not work on late versions of Android. You should >>>> turn USB debugging off when using the IOIO over USB as a host. >>>> - Don't use "H" mode. "A" should be fine. >>>> - Make sure the trimmer on the IOIO is fully clockwise. >>>> - Please mention whether you're getting charging indication on the >>>> Android and/or the Accessory dialog when connecting the IOIO as a USB >>>> host. >>>> >>>> >>>> >>>> On Fri, Apr 25, 2014 at 1:55 PM, Gordon Martin <[email protected]>wrote: >>>> >>>>> I'm very frustrated at not having a responsive IOIO board. I >>>>> received my IOIO-OTG from Seeed Studio last week and just wanted to test >>>>> it. >>>>> >>>>> I'm hoping this forum can help... >>>>> >>>>> I'm just trying to connect the IOIO to my Android device and use a >>>>> test app from the Play store to blink the yellow LED. >>>>> >>>>> I've tried many configurations: >>>>> >>>>> 1) Connected JST port to 12.5v power brick; connected to Android via >>>>> red OTG cable and micro USB. >>>>> 2) Connected JST port to 12.5v power brick; connected to Bluetooth >>>>> dongle via red OTG cable. >>>>> 3) Connected to Android host via a different OTG cable then micro into >>>>> the IOIO. >>>>> >>>>> I have an Android 4.2 tablet and Samsung 4.1 phone - both support >>>>> OTG. I have various bluetooth dongles - two of which match dongles I've >>>>> seen used in IOIO videos. I've enabled USB debug mode on my Android >>>>> devices. The IOIO switch is set to A but I've tried H. I've read as >>>>> much >>>>> documentation as I can find. >>>>> >>>>> In all cases I get the bright red power LED but no other activity. >>>>> The bluetooth dongles never light up. My Android devices never connect >>>>> to >>>>> the device or see a Bluetooth device. When I measure the power pins on >>>>> the >>>>> IOIO I can verify that they provide the requisite 3.3 and 5 volts so I >>>>> expect the voltage regulator is functioning properly. >>>>> >>>>> What am I missing here? At this point I'm only left with thinking >>>>> that I've got a bad board, but that seems highly unlikely. >>>>> >>>>> Any help would be greatly appreciated. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "ioio-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at http://groups.google.com/group/ioio-users. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "ioio-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/ioio-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
