Ytai, I have setup an ioio firmware VMware Linux based development environment with the latest MPLAB IDE and the latest toolchain, build app_layer_v1, created the ioioapp, loaded it into ioio otg using ioiodude and tested it. My android application works fine. If people are interrested I can make the VMware environment available for the public. Can you pinpoint where I can setup the scanrate op the analog inputs? Thanks.
On Friday, April 24, 2015 at 6:49:41 AM UTC+2, Ytai wrote: > > Frankly, I'm not going to spend too much time supporting firmware > developers, under the assumptions that: > > 1. Their number is a very small fraction of the number of users. > 2. Most of them probably know what they're doing enough to be able to > install 2 applications (toolchain + IDE) and download the source code from > GitHub. Once you've gotten this far, there's sufficient information on the > ioio-dev forum on how to build and I would be happy to answer questions if > there still are any. > > I haven't yet gotten around to enabling software control of the rate > unfortunately. I agree that this would be a very useful feature to have. > > On Thu, Apr 23, 2015 at 1:27 PM, charlieh <[email protected] > <javascript:>> wrote: > >> I started to setup the firmware development environment to be able to >> reduce the analog sampling rate in the firmware. This is going to take to >> much time and, reading different posts, many problems can be encountered. >> Is it possible that a Virtual Linux IOIO development environment (for for >> example VMWare) is prepared that contains all the tooling to do firmware >> development for the IOIO, including the latest IOIO firmware sources? This >> will help new IOIO firmware developers a lot. >> About the analog scan rate, I read at several places that there are plans >> to be able to set the analog sampling rate? How concreet are these plans? >> Thanks. >> >> Op maandag 13 april 2015 04:41:36 UTC+2 schreef Ytai: >>> >>> Some Bluetooth dongles are less likely than others to exhibit such >>> problems. Try different ones. It is also fairly simple to reduce the analog >>> sampling rate in firmware. >>> On Apr 11, 2015 11:01 AM, "charlieh" <[email protected]> wrote: >>> >>>> The IOIO works fine with my old tablet with Android 3.2. I bought a >>>> small cheap phone to have a more compact setup. It is the Wiko GOA with >>>> stock android. The tablet doesn't drain power from the IOIO while the >>>> phone >>>> does. The IOIO is powered by an 1800mAh rechargeble batery. Because it >>>> works with another phone I suppose that the cause is this cheap phone. So >>>> I >>>> stick with my old table. Thanks for the support. >>>> I also tried bluetooth. HelloIOIO works fine. But when my application >>>> calls openAnalogInput() the phone disconnect. Without openAnalogInput() my >>>> application works fine (unfortunately I need analog input). >>>> I use the IOIO for timelapse photograps. The IOIO controlls the camera >>>> motion, the exposure interval, exposure duration and compensation. >>>> >>>> On Saturday, April 11, 2015 at 7:15:31 PM UTC+2, Ytai wrote: >>>>> >>>>> What phone is this? Is this its stock OS or some unofficial upgrade? >>>>> It appears that there might be something wrong at the USB layer, were >>>>> bytes >>>>> are either being read multiple times or the IOIO loses connection. >>>>> There's >>>>> also a small chance that this is power related. What power supply are you >>>>> using? >>>>> On Apr 11, 2015 4:44 AM, "charlieh" <[email protected]> wrote: >>>>> >>>>>> See attachements. >>>>>> >>>>>> On Friday, April 10, 2015 at 12:09:58 AM UTC+2, Ytai wrote: >>>>>>> >>>>>>> Seems like some data is getting corrupt coming from the IOIO to the >>>>>>> Android. In IOIOProtocol there are commented out lines that log every >>>>>>> byte >>>>>>> coming in and going out. Can you enable them and repeat? >>>>>>> >>>>>>> On Thu, Apr 9, 2015 at 12:17 PM, charlieh <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hello Ytai, on another phone it works. For my phone I have two logs >>>>>>>> attached. One when the phone cannot connect to the IOIO and one when >>>>>>>> it >>>>>>>> succeeds. It seems that the AccessoryConnectionBootstrap is not called >>>>>>>> at >>>>>>>> all. Any idea? Thanks. >>>>>>>> >>>>>>>> On Saturday, April 4, 2015 at 8:33:07 PM UTC+2, Ytai wrote: >>>>>>>>> >>>>>>>>> That is strange. Haven't seen it happen on the device I used for >>>>>>>>> testing (moto X mostly). Do you have another phone to test with? >>>>>>>>> Otherwise, >>>>>>>>> can you dig into what's actually happening, e.g. whether the app ever >>>>>>>>> gets >>>>>>>>> notified by the Android OS that anything had happened? >>>>>>>>> >>>>>>>>> On Fri, Apr 3, 2015 at 12:23 AM, charlieh <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> That did help a lot. I do not need to start the phone with USB >>>>>>>>>> debugging enable. But it is not 100%. I have to unplug and replug >>>>>>>>>> the IOIO >>>>>>>>>> several times before communication is established (each time the >>>>>>>>>> accessory >>>>>>>>>> dialog appears). Once connection is made, it will always connect, >>>>>>>>>> after >>>>>>>>>> switching the phone on or off or reconnecting the IOIO. But as soon >>>>>>>>>> as the >>>>>>>>>> IOIO is unpowered then I have do again several tries. It looks like >>>>>>>>>> that >>>>>>>>>> the IOIO firmware has difficulties in getting into OpenAccessory >>>>>>>>>> mode. IOIO >>>>>>>>>> Hardware: SPRK0020, IOIO Bootloader: IOIO0400, IOIO >>>>>>>>>> Firmware:IOIO0500. >>>>>>>>>> >>>>>>>>>> On Thursday, April 2, 2015 at 10:48:13 AM UTC+2, Ytai wrote: >>>>>>>>>>> >>>>>>>>>>> I've recently made some changes to IOIOLib which have made >>>>>>>>>>> OpenAccesory more reliably. In fact, all the people who have >>>>>>>>>>> reported >>>>>>>>>>> problems before and have tried it have reported that it seems to >>>>>>>>>>> have >>>>>>>>>>> solved the issue. >>>>>>>>>>> I haven't gotten around to making a software release including >>>>>>>>>>> this fix. I'll try to do that soon. In the meantime, it would be >>>>>>>>>>> great if >>>>>>>>>>> you can just grab the latest version from the master branch on >>>>>>>>>>> GitHub and >>>>>>>>>>> see if things get better. >>>>>>>>>>> >>>>>>>>>>> On Wed, Apr 1, 2015 at 11:38 PM, charlieh <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Dear Ytai, thanks for the response. >>>>>>>>>>>> When my phone has USB debugging *disabled*, I connect the IOIO >>>>>>>>>>>> and switch it on then the accessory dialog appears, I select >>>>>>>>>>>> HelloIOIO, >>>>>>>>>>>> HelloIOIO appears but doesn't connect, yellow led cannot be >>>>>>>>>>>> switched on/off. >>>>>>>>>>>> When my phobe has USB debugging *enabled*, I connect the IOIO >>>>>>>>>>>> and switch it on then the accessory dialog doesn't appear. I >>>>>>>>>>>> switch USB >>>>>>>>>>>> debugging off, accessory dialog appears, I select HelloIOIO, >>>>>>>>>>>> HelloIOIO >>>>>>>>>>>> appears and connects, yellow led can be switched on/off. As long >>>>>>>>>>>> as the >>>>>>>>>>>> IOIO is not switched off, disconnecting the cable and reconnecting >>>>>>>>>>>> the >>>>>>>>>>>> cable shows the accessory dialog again and HelloIOIO can connect >>>>>>>>>>>> to the >>>>>>>>>>>> IOIO. Hope this helps. >>>>>>>>>>>> >>>>>>>>>>>> On Wednesday, April 1, 2015 at 11:27:57 PM UTC+2, Ytai wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Doesn't work how? Are you getting the accessory dialog or not >>>>>>>>>>>>> even that? >>>>>>>>>>>>> On Apr 1, 2015 2:26 PM, "charlieh" <[email protected]> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I have the latest firmware, latest HelloIOIO application and >>>>>>>>>>>>>> Android 4.4.2. To get HelloIOIO starting communication I have to >>>>>>>>>>>>>> connect >>>>>>>>>>>>>> the IOIO OTG with the USB cable, switch it on, enable USB >>>>>>>>>>>>>> debugging and >>>>>>>>>>>>>> disable USB debugging while the OTG is kept connected and >>>>>>>>>>>>>> switched on. Just >>>>>>>>>>>>>> connecting the IOIO OTG and switch it on while USB debugging is >>>>>>>>>>>>>> switched >>>>>>>>>>>>>> off doesn't work. Any idea? Thanks. >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> 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]. >>>>>>>>>>>> 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]. >>>>>>>>>> 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]. >>>>>>>> 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]. >>>>>> 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]. >>>> 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.
