Blink V3

46 views
Skip to first unread message

Al B

unread,
May 10, 2013, 4:14:40 PM5/10/13
to ioio-...@googlegroups.com
I downloaded the latest Blink V3 and using IOIO Manager I made "Blink-IOIO0003" active by starring it. Then, I turned the IOIO OTG off & on and connected it to the Android device. However, the yellow LED did not light nor started blinking. Did I miss any step?

Ytai Ben-Tsvi

unread,
May 10, 2013, 4:35:30 PM5/10/13
to ioio-...@googlegroups.com
IOIO-OTG (or more precisely, the v4 bootloader which the IOIO-OTG uses by default) doesn't work with IOIO Manager. See IOIODude.


On Fri, May 10, 2013 at 1:14 PM, Al B <cagi...@gmail.com> wrote:
I downloaded the latest Blink V3 and using IOIO Manager I made "Blink-IOIO0003" active by starring it. Then, I turned the IOIO OTG off & on and connected it to the Android device. However, the yellow LED did not light nor started blinking. Did I miss any step?

--
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 ioio-users+...@googlegroups.com.
To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ioio-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Al B

unread,
May 10, 2013, 4:52:04 PM5/10/13
to ioio-...@googlegroups.com
Hum?  I'm now a little bit confused since once you told me that I could use an IOIO-OTG as a programmer to update a IOIO v1 firmware via the IOIO Manager so did I misunderstand you?

Does IOIO Manager only works with the former IOIO v1?  I thought the only constraint was the Android OS version "Android version 4.1 (Jelly Bean) broke the compatibility with the IOIO bootloader. This means you will not be able to use IOIO Manager for application firmware upgrades".

Ytai Ben-Tsvi

unread,
May 10, 2013, 7:45:47 PM5/10/13
to ioio-...@googlegroups.com
It is indeed a bit confusing. Let me clear up the mess:

IOIOManager serves two unrelated purposes:
  1. Upgrade the application firmware on IOIO's which run the V3.x bootloader (which is normally not the IOIO-OTG). This feature will not work on Android v4.1 or greater.
  2. Use any IOIO running app firmware V2.x or greater as a programmer for another IOIO (any version), thus being able to upgrade the other IOIO's firmware. Since IOIOManager is not currently built against IOIOLibAccessory, you have to use ADB or Bluetooth (between the Android and your "programmer" IOIO) for doing that. ADB mode doesn't work on Android 4.2.2 or greater. If BT is not an option, you can rebuild IOIOManager with IOIOLibAccessory baked into it, which I'll probably do myself at some point.


On Fri, May 10, 2013 at 1:52 PM, Al B <cagi...@gmail.com> wrote:
Hum?  I'm now a little bit confused since once you told me that I could use an IOIO-OTG as a programmer to update a IOIO v1 firmware via the IOIO Manager so did I misunderstand you?

Does IOIO Manager only works with the former IOIO v1?  I thought the only constraint was the Android OS version "Android version 4.1 (Jelly Bean) broke the compatibility with the IOIO bootloader. This means you will not be able to use IOIO Manager for application firmware upgrades".
Reply all
Reply to author
Forward
0 new messages