Please try to watch carefully and read the page above before asking any questions. If something still doesn't work for you, I'll be happy to help. Note that this is *potentially not the final release*, as I'm not 100% done testing. See the "Caveats" section on the page above in order to adjust your expectations. However, this release is *probably in pretty good shape*.
> Please try to watch carefully and read the page above before asking any > questions. If something still doesn't work for you, I'll be happy to help. > Note that this is *potentially not the final release*, as I'm not 100% > done testing. See the "Caveats" section on the page above in order to > adjust your expectations. However, this release is *probably in pretty > good shape*.
> -- > You received this message because you are subscribed to the Google > Groups "ioio-users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/ioio-users/-/77jkZQPCI60J. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
I agree. There currently isn't. I chose to publish a video first, as it is more accessible to many people, required less work for me, and will probably generate less questions :D But I do plan to add a written guide on that same Wiki page soon.
> I agree. There currently isn't. > I chose to publish a video first, as it is more accessible to many > people, required less work for me, and will probably generate less > questions :D > But I do plan to add a written guide on that same Wiki page soon.
> -- > You received this message because you are subscribed to the Google > Groups "ioio-users" group. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
I tried to follow your video, but I keep seeing the following error message: The attached IOIO is running a application firmware version that is not compatible with the programmer. Expecting version IOIO0200 or higher.
I am using one 3-month old IOIO board that is never upgraded as the programmer to program a new IOIO board I ordered few days ago. Any suggestion for me to proceed the firmware upgrade or any information I need to look into?
You first need to upgrade the application firmware on your "programmer IOIO". This is done by downloading the App-IOIO0300 application firmware, starring it, and power-cycling the programmer IOIO. The yellow LED should light up for a little longer than usual and then everything should work. However, as I mention on the video, some Android devices which have been messed around with by the OEM or the carrier do not handle this function (application firmware programming) well. If this is your case, try to get your hands on another Android just for this specific part. It is a one-time process (until the next time there's an app-firmware upgrade).
On Sun, Nov 6, 2011 at 2:26 PM, lucas <feng...@gmail.com> wrote: > HI Ytai,
> I tried to follow your video, but I keep seeing the following error > message: > The attached IOIO is running a application firmware version that is not > compatible with the programmer. Expecting version IOIO0200 or higher.
> I am using one 3-month old IOIO board that is never upgraded as the > programmer to program a new IOIO board I ordered few days ago. Any > suggestion for me to proceed the firmware upgrade or any information I need > to look into?
> To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
I was very excited to see the bluetooth capability demonstrated. I ordered two more IOIO boards (now I have 3) a new bluetooth dongle and decided to replicate your results. My setup is identical to yours right down to the Parrot AR Drone battery :). Following the video step-by-step everything went very smoothly. I connected the new IOIO, it recognized the board (everything green), then wrote and verified the firmware.
The problem I'm having is that the board doesn't seem to have anything on it afterward. When I reset the power and plug it the USB connection on the phone, logcat doesn't report any usb/adb connection. It appears to be dead.
When I re-wire it back up to the programmer IOIO, it recognizes the board again (everything is green again) and once again I can write and verify the firmware update without issue. I've done this several times have tried writing all 3 bootloaders but none seem to show any signs of life.
Do you have any suggestions for what I can try to bring the IOIO board back to life.
Needless to say I never got bluetooth working.
I haven't tried the 3rd IOIO board for fear of cooking it as well.
Thanks for your assistance. I think you're doing an incredible job on the hardware and supporting and building the IOIO community. Great work!
Hi James, This may be a result of using the wrong firmware version. Make sure you use the Boot-0300-App-0310 bundle. Reset the programmed board after programming. Disconnect it completely from the programmer, power it and connect it to the Android. Notice whether the charging icon and/or the debug icon on the Android turn on. Also notice what's happening with the yellow LED on the IOIO. Let me know the results and we can continue to investigate.
On Mon, Nov 7, 2011 at 10:13 PM, James <ebaja...@gmail.com> wrote: > Hi Ytai,
> I was very excited to see the bluetooth capability demonstrated. I ordered > two more IOIO boards (now I have 3) a new bluetooth dongle and decided to > replicate your results. My setup is identical to yours right down to the > Parrot AR Drone battery :). Following the video step-by-step everything > went very smoothly. I connected the new IOIO, it recognized the board > (everything green), then wrote and verified the firmware.
> The problem I'm having is that the board doesn't seem to have anything on > it afterward. When I reset the power and plug it the USB connection on the > phone, logcat doesn't report any usb/adb connection. It appears to be dead.
> When I re-wire it back up to the programmer IOIO, it recognizes the board > again (everything is green again) and once again I can write and verify the > firmware update without issue. I've done this several times have tried > writing all 3 bootloaders but none seem to show any signs of life.
> Do you have any suggestions for what I can try to bring the IOIO board > back to life.
> Needless to say I never got bluetooth working.
> I haven't tried the 3rd IOIO board for fear of cooking it as well.
> Thanks for your assistance. I think you're doing an incredible job on the > hardware and supporting and building the IOIO community. Great work!
> To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Hi Ytai,
I tried again and got it working. As it turns out, it was the power
adjustment screw on the IOIO board. It was turned too low.
When I connected the updated IOIO to my phone and slowly turned up the
adjustment, the USB/ADB lit up on the phone and I was in business.
From there I was able to plug in a bluetooth dongle and pair the IOIO
with my phone. I tried 3 different dongles and they all seemed to
pair.
I'm a bit embarrassed that I didn't think to try that before. I never
had to touch the charging adjustment on my original IOIO board.
Thanks for your help. This should be fun.
On Nov 8, 12:30 am, Ytai Ben-Tsvi <yta...@gmail.com> wrote:
> Hi James,
> This may be a result of using the wrong firmware version.
> Make sure you use the Boot-0300-App-0310 bundle.
> Reset the programmed board after programming. Disconnect it completely from
> the programmer, power it and connect it to the Android. Notice whether the
> charging icon and/or the debug icon on the Android turn on. Also notice
> what's happening with the yellow LED on the IOIO.
> Let me know the results and we can continue to investigate.
> On Mon, Nov 7, 2011 at 10:13 PM, James <ebaja...@gmail.com> wrote:
> > Hi Ytai,
> > I was very excited to see the bluetooth capability demonstrated. I ordered
> > two more IOIO boards (now I have 3) a new bluetooth dongle and decided to
> > replicate your results. My setup is identical to yours right down to the
> > Parrot AR Drone battery :). Following the video step-by-step everything
> > went very smoothly. I connected the new IOIO, it recognized the board
> > (everything green), then wrote and verified the firmware.
> > The problem I'm having is that the board doesn't seem to have anything on
> > it afterward. When I reset the power and plug it the USB connection on the
> > phone, logcat doesn't report any usb/adb connection. It appears to be dead.
> > When I re-wire it back up to the programmer IOIO, it recognizes the board
> > again (everything is green again) and once again I can write and verify the
> > firmware update without issue. I've done this several times have tried
> > writing all 3 bootloaders but none seem to show any signs of life.
> > Do you have any suggestions for what I can try to bring the IOIO board
> > back to life.
> > Needless to say I never got bluetooth working.
> > I haven't tried the 3rd IOIO board for fear of cooking it as well.
> > Thanks for your assistance. I think you're doing an incredible job on the
> > hardware and supporting and building the IOIO community. Great work!
> > To post to this group, send email to ioio-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > ioio-users+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/ioio-users?hl=en.
> Hi Ytai, > I tried again and got it working. As it turns out, it was the power > adjustment screw on the IOIO board. It was turned too low. > When I connected the updated IOIO to my phone and slowly turned up the > adjustment, the USB/ADB lit up on the phone and I was in business. > From there I was able to plug in a bluetooth dongle and pair the IOIO > with my phone. I tried 3 different dongles and they all seemed to > pair. > I'm a bit embarrassed that I didn't think to try that before. I never > had to touch the charging adjustment on my original IOIO board. > Thanks for your help. This should be fun.
> On Nov 8, 12:30 am, Ytai Ben-Tsvi <yta...@gmail.com> wrote: > > Hi James, > > This may be a result of using the wrong firmware version. > > Make sure you use the Boot-0300-App-0310 bundle. > > Reset the programmed board after programming. Disconnect it completely > from > > the programmer, power it and connect it to the Android. Notice whether > the > > charging icon and/or the debug icon on the Android turn on. Also notice > > what's happening with the yellow LED on the IOIO. > > Let me know the results and we can continue to investigate.
> > On Mon, Nov 7, 2011 at 10:13 PM, James <ebaja...@gmail.com> wrote: > > > Hi Ytai,
> > > I was very excited to see the bluetooth capability demonstrated. I > ordered > > > two more IOIO boards (now I have 3) a new bluetooth dongle and decided > to > > > replicate your results. My setup is identical to yours right down to > the > > > Parrot AR Drone battery :). Following the video step-by-step everything > > > went very smoothly. I connected the new IOIO, it recognized the board > > > (everything green), then wrote and verified the firmware.
> > > The problem I'm having is that the board doesn't seem to have anything > on > > > it afterward. When I reset the power and plug it the USB connection on > the > > > phone, logcat doesn't report any usb/adb connection. It appears to be > dead.
> > > When I re-wire it back up to the programmer IOIO, it recognizes the > board > > > again (everything is green again) and once again I can write and > verify the > > > firmware update without issue. I've done this several times have tried > > > writing all 3 bootloaders but none seem to show any signs of life.
> > > Do you have any suggestions for what I can try to bring the IOIO board > > > back to life.
> > > Needless to say I never got bluetooth working.
> > > I haven't tried the 3rd IOIO board for fear of cooking it as well.
> > > Thanks for your assistance. I think you're doing an incredible job on > the > > > hardware and supporting and building the IOIO community. Great work!
> > > To post to this group, send email to ioio-users@googlegroups.com. > > > To unsubscribe from this group, send email to > > > ioio-users+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/ioio-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Both should work (assuming, you also connection programmer 36 to target mclr too). Chances are that you have wiring / soldering problems. Is that possible?
On Wed, Nov 30, 2011 at 12:08 PM, dragorn <dr4g...@gmail.com> wrote: > In your video you connect programmer 38 to target 38, programmer 37 to > target 37.
> On my pair of first-gen sparkfun boards (chip id 128) this results in > "unknown target connected".
> To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Used the same wires and flashed in both directions (dev1 flashing dev2, re-cable, dev2 flashing dev1) with no problems on 36,35. I get "unknown target connected" for 38,37 with programmer hosted on either device, switching the RST pin of course.
Solder joints all look clean, whacked them with some flux and reheated them to be safe, and since dev1 and dev2 work reflexively it wouldn't indicate to me that they have an electrical problem - if 37/38 were bad on one device I'd expect it to fail when acting as the programmer.
These are from the very first run of sparkfun pre-order boards.
On Wed, Nov 30, 2011 at 4:02 PM, Ytai Ben-Tsvi <yta...@gmail.com> wrote: > Both should work (assuming, you also connection programmer 36 to target > mclr too). > Chances are that you have wiring / soldering problems. Is that possible?
> On Wed, Nov 30, 2011 at 12:08 PM, dragorn <dr4g...@gmail.com> wrote:
>> In your video you connect programmer 38 to target 38, programmer 37 to >> target 37.
>> On my pair of first-gen sparkfun boards (chip id 128) this results in >> "unknown target connected".
>> To post to this group, send email to ioio-users@googlegroups.com. >> To unsubscribe from this group, send email to >> ioio-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/ioio-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Strange... AFAIK, SparkFun themselves use pins 38/37 for programming. But anyway, can't argue with the fact that it solved your problem... Thanks for sharing this info, maybe there's something I'm overlooking and this will help others fix a similar problem!
On Wed, Nov 30, 2011 at 1:37 PM, mike kershaw <drag...@kismetwireless.net>wrote:
> Used the same wires and flashed in both directions (dev1 flashing dev2, > re-cable, dev2 flashing dev1) with no problems on 36,35. I get "unknown > target connected" for 38,37 with programmer hosted on either device, > switching the RST pin of course.
> Solder joints all look clean, whacked them with some flux and reheated > them to be safe, and since dev1 and dev2 work reflexively it wouldn't > indicate to me that they have an electrical problem - if 37/38 were bad on > one device I'd expect it to fail when acting as the programmer.
> These are from the very first run of sparkfun pre-order boards.
> -m
> On Wed, Nov 30, 2011 at 4:02 PM, Ytai Ben-Tsvi <yta...@gmail.com> wrote:
>> Both should work (assuming, you also connection programmer 36 to target >> mclr too). >> Chances are that you have wiring / soldering problems. Is that possible?
>> On Wed, Nov 30, 2011 at 12:08 PM, dragorn <dr4g...@gmail.com> wrote:
>>> In your video you connect programmer 38 to target 38, programmer 37 to >>> target 37.
>>> On my pair of first-gen sparkfun boards (chip id 128) this results in >>> "unknown target connected".
>>> To post to this group, send email to ioio-users@googlegroups.com. >>> To unsubscribe from this group, send email to >>> ioio-users+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/ioio-users?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "ioio-users" group. >> To post to this group, send email to ioio-users@googlegroups.com. >> To unsubscribe from this group, send email to >> ioio-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/ioio-users?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
I don't mean to sound like I haven't read the IOIO wiki because I have read just about every page. Do I absolutely need 2 IOIO boards, PIC programmer, an android device, bluetooth dongle, and a computer to acheive bluetooth functionality? Could it be done with one PIC programmer and 1 IOIO?
Sorry if that wasn't clear: You need *either* a second IOIO *or* a programmer. So it seems like you are good to go. Download the hex bundle from the Downloads page, use SPRK0015 or 16 according to your board , connect the programmer (mclr, 3.3V, GND, 38, 37) and GO.
> Sorry if that wasn't clear: > You need *either* a second IOIO *or* a programmer. So it seems like you are > good to go. > Download the hex bundle from the Downloads page, use SPRK0015 or 16 > according to your board , connect the programmer (mclr, 3.3V, GND, 38, 37) > and GO.
Yes. But if you go to sure electronics directly and not through eBay it is a little cheaper. On Dec 6, 2011 8:14 AM, "Souk Nomichith" <teaminer...@gmail.com> wrote:
> Thanks, > Now I need a PIC programmer since I don't have one yet. Will this > programmer work? It's on ebay? http://tinyurl.com/75p8ofs
> -Souk
> On Dec 5, 11:54 pm, Ytai Ben-Tsvi <yta...@gmail.com> wrote: > > Sorry if that wasn't clear: > > You need *either* a second IOIO *or* a programmer. So it seems like you > are > > good to go. > > Download the hex bundle from the Downloads page, use SPRK0015 or 16 > > according to your board , connect the programmer (mclr, 3.3V, GND, 38, > 37) > > and GO.
> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Because I have an HTC Thunderbolt, I borrowed my wife's HTC Evo 4g and successfully ran the HelloIOIO app via USB so I know her phone works. But I want to put the bluetooth firmware on the IOIO so I bought another IOIO. I successfully flashed the new bootloader app onto the 'programmer' IOIO. I know this because I first flashed the Blink app and when I flashed back to IOIO0300, the blinking stopped.
Here's where things start to go wrong. If I have my phone plugged into the IOIO via USB, I hang after selecting '>Programmer>Select'. However, if I unplug the phone, I can hit 'Select' and select the 'Boot-IOIO0300-App-IOIO0310' app and I select 'Sprk0016'. I then plug the phone back in and it just hangs on 'Waiting for target'. I'm assuming I shouldn't be unplugging my phone at any point during this process but the IOIO Manager app just hangs if I don't.
Not sure where to go from here.
- I've uninstalled and reinstalled all of the QR Code files as well as the IOIO Manager. - I've also made sure that the pot is turned all of the way up on both IOIO's. - One IOIO is powered by a 5v wall wart while the other is powered by a 9 volt battery. - 38 > 38, 37 > 37 and 36 to target mclr (reset)
"Waiting for target" is good. It means that IOIOManager was able to communicate with your programmer IOIO and is waiting for the target IOIO to be connected. Did you remember to share a common ground between the IOIOs? Also, better power them from the same supply, just in case both supplies don't get along.
On Thu, Dec 8, 2011 at 8:07 PM, emooney <eric.moo...@gmail.com> wrote: > Hey Ytai,
> Because I have an HTC Thunderbolt, I borrowed my wife's HTC Evo 4g and > successfully ran the HelloIOIO app via USB so I know her phone works. But I > want to put the bluetooth firmware on the IOIO so I bought another IOIO. I > successfully flashed the new bootloader app onto the 'programmer' IOIO. I > know this because I first flashed the Blink app and when I flashed back to > IOIO0300, the blinking stopped.
> Here's where things start to go wrong. If I have my phone plugged into the > IOIO via USB, I hang after selecting '>Programmer>Select'. However, if I > unplug the phone, I can hit 'Select' and select the > 'Boot-IOIO0300-App-IOIO0310' app and I select 'Sprk0016'. I then plug the > phone back in and it just hangs on 'Waiting for target'. I'm assuming I > shouldn't be unplugging my phone at any point during this process but the > IOIO Manager app just hangs if I don't.
> Not sure where to go from here.
> - I've uninstalled and reinstalled all of the QR Code files as well as > the IOIO Manager. > - I've also made sure that the pot is turned all of the way up on both > IOIO's. > - One IOIO is powered by a 5v wall wart while the other is powered by > a 9 volt battery. > - 38 > 38, 37 > 37 and 36 to target mclr (reset)
> To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
Thanks so much for the quick reply Ytai. I got one of the two working at least through USB. I'll do the same process tomorrow morning for the other. There's something I probably missed on that one. I can't get the bluetooth working though; I'm banking on my BT Kensington Dongle. It's pretty old ( +2 yrs) and may not be 2.0. So tomorrow, I'm going to see if I can track down one that you recommend and see if that works.
Thanks again for your time. Very much appreciated.
BTW, since you are able to program, my current recommendation is to use the release candidate firmware. It looks pretty good and I'll soon release it officially.
On Thu, Dec 8, 2011 at 9:55 PM, emooney <eric.moo...@gmail.com> wrote: > Thanks so much for the quick reply Ytai. I got one of the two working at > least through USB. I'll do the same process tomorrow morning for the other. > There's something I probably missed on that one. I can't get the bluetooth > working though; I'm banking on my BT Kensington Dongle. It's pretty old ( > +2 yrs) and may not be 2.0. So tomorrow, I'm going to see if I can track > down one that you recommend and see if that works.
> Thanks again for your time. Very much appreciated.
> To post to this group, send email to ioio-users@googlegroups.com. > To unsubscribe from this group, send email to > ioio-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/ioio-users?hl=en.
I am facing similar problem: "waiting for target". I waited for some minutes but nothing happened. My IOIO bootloader is 0100 and firmware 0300. I re-installed the IOIO manager and re-filled the library. The blink bootloader worked fine. I used Galaxy Tab 10.1 (Honeycomb) to program it (before I used Froyo 2.2 but hang).
