No, that is not possible with the current design.
On Fri, Jun 16, 2023 at 8:50 AM Adir Krafman wrote:
> Hi all / Ytai,
>
> I need to be able to connect the IOIO-OTG to an android device and then
> dynamically(programmatically) switch the roles of host and device between
> the android and board.
That would involve rebuilding the firmware as the pin is hardcoded in it.
On Thu, Apr 30, 2020, 09:46 Ivan Iveljic wrote:
> Hey I've got a question, how to change the ioio Bluetooth password?
>
> Thanks in advance
>
> Christian Gutierrez schrieb am Do., 30. Apr. 2020,
> 18:38:
>
>> Hello,
>>
The IOIO can work as either a device or host, depending on which side of
the USB cable is connected to it. You'd need to include the
IOIOLibAndroidDevice library in your project. It can also work as a USB
device with a PC app in a similar manner.
On Thu, Apr 30, 2020, 09:38 Christian Gutierrez
I haven't put a watchdog in the firmware. Shouldn't be hard to do for
someone who knows what they're doing. Could be triggered either by an
explicit command from the app (which will give you end-to-end) or to USB
status (which will give you zero impact on the app on the expense of less
coverage).
Do you want to send out a pull request?
On Mon, Apr 23, 2018, 14:39 JP wrote:
> Thanks!
>
> I can confirm that Mikhail's suggestions also fixed the same errors for me.
>
> /JP
>
>
> Den onsdag 16 augusti 2017 kl. 12:26:13 UTC+2 skrev Mikhail Evstafyev:
>>
>> I've just
Is this over Bluetooth? If so, try a different dongle. Some dongles seem to
not be able to keep up with the bandwidth required for analog inputs and
corrupt the data, causing the connection to drop.
On Nov 26, 2017 12:27 PM, "Tyler" wrote:
> Kannan,
>
> I don't see
>From experience, this behavior sometimes occurs as result of saturating the
BT bandwidth with some dongles. Each analog input you open generates an
additional ~1.25kB/s of data.
Your options are either:
- Try different dongles. Some experience this behavior more than others.
- Modify the
BF:EB are the last 4 digits of the address (which depends on the dongle)
and 4545 is the pin (always).
On Fri, Nov 3, 2017 at 7:24 AM, Ilan Tal wrote:
> According to the documentation pair of a phone to IOIO is given by IOIO
> (xx:yy) where these give the last 4 numbers.
> I
On Mon, Oct 23, 2017 at 12:10 AM, Ilan Tal wrote:
> Thanks Ytai,
> I couldn't see clear enough to see there are 5 pins on the micro USB,
> unlike the 4 pins on the USB.
> Maybe this explains why I don't remember ever seeing a male micro USB to
> male micro USB.
>
> Am I
The "A" side of the cable (host) has ID pin shorted to the GND net and the
B side (guest) doesn't.
On Oct 21, 2017 21:57, "Ilan Tal" wrote:
> As a sanity check, I would like to ask what is the difference if you plug
> in the cable one way or the other.
> On my computer I
See inline
On Sat, Oct 21, 2017 at 9:26 AM, Ilan Tal wrote:
> I would very much like that what you imply would be true.
> I don't know what the "direction of the cable" really means.
> There is a red cable which comes with the board which is a male microUSB
> connected to a
rd for this test.
> There are a couple of versions of the USB OTG checker programs and both
> fail on new phones, and work on old phones. Naturally they are free and
> have ads.
>
> On Fri, Oct 20, 2017 at 11:54 PM, Ytai Ben-Tsvi <yta...@gmail.com> wrote:
>
>> Can y
Can you please explain the sentence "The play store USB OTG says the the
OTG isn't compatible"?
On Oct 19, 2017 21:54, "Ilan Tal" wrote:
> Just to remove all doubt I asked my brother to try the auto mode. With the
> old phones, both of his boards work fine. With the new
I think you might be somewhat misusing the term OTG. USB OTG has to do with
the ability of a device to switch between being a host on the USB bus to
bring a device, based on which side of the cable it is connected to. Since
all phones used to be only devices, manufacturers started using the term
The latest version (as of almost two years now) of the IOIO from SparkFun
and SeeedStudio has improved protection for the regulator.
If you want to bypass the on-board regulator, just feed 5v directly into
the 5v rail from an external regulator. Your damaged regulator might be
shorting the 5v rail
You won't be able to charge the phone if you're using the IOIO in device
mode, since it is always the host that supplies power to the device and not
the other way around. When you say "OTG" I'm assuming you mean that the
phone is the host and the IOIO is the device. Otherwise, I don't see a
reason
There are a few issues here, I hope I didn't forget anything.
- Timeout: the approach I took with all blocking operations is that they
all handle Thread.interrupt() correctly. This way, you can implement your
timeout externally without having to change the IOIO library internals.
The "small MCU" option is along the line of putting something like an
Arduino between the IOIO and the sensor, which will translate the unusual
protocol of the sensor into something more standard, such as serial (UART).
That is, this middleman will constantly wait for samples from the HX711 and
as
See my previous response about your options
On Sep 19, 2017 6:51 PM, "Maximillian" wrote:
> Hi Ytai,
>
>
> Thanks for reply and sorry for the confusion.
>
> I plan to use this weight sensor with IOIO
>
>
>
I'm assuming you're using OpenAccessory? It is not unlikely that there are
problems in this area, my impression is that this feature of Android was
poorly designed and even more poorly implemented in some cases. It is also
possibly that there's a bug somewhere in the IOIO code that interacts with
The downside of your approach is that you cannot use scaling, so you'll be
bloating the bandwidth between the IOIO and the application 16x. Maybe not
a problem for the rates you're talking about. Removing the check just means
delete the block that says:
if (mode_ != PulseMode.POSITIVE && mode_ !=
Yeah, I see. Well, since you're going to be ignoring the value anyway, you
can simply remove the mode check.
On Thu, Aug 31, 2017 at 6:32 PM, Maximillian
wrote:
> Hi Ytai,
>
> Sorry I think the logic is ok.
>
> It's just we cannot use *getDurationBuffered()* along
Analog samples get pushed from the IOIO to the Android at 1kHz (one sample
every 1ms). So if you use getVoltage(), whatever sample you're getting is
only a few milliseconds old (since there's some latency too). I'm guessing
that for pH measurements this is completely insignificant. The *Sync
I don't think there's a lot of value in using the *Sync version. Otherwise
it's fine, as long as you don't mind that the sample rate varies with the
flow rate. Otherwise, create a separate thread for one or the other.
On Aug 28, 2017 18:21, "Maximillian" wrote:
>
Here's a hint:
https://groups.google.com/forum/#!msg/ioio-users/SE-I_iSCdYs/bLehlYJWDvQJ
On Wed, Aug 23, 2017 at 4:18 PM, Ytai Ben-Tsvi <yta...@gmail.com> wrote:
> What's the maximum pulse rate for your application?
>
> On Wed, Aug 23, 2017 at 3:36 PM, Maximillian <felix.c
What's the maximum pulse rate for your application?
On Wed, Aug 23, 2017 at 3:36 PM, Maximillian
wrote:
> Can you give more hint about how to count?
>
> I'm not really sure how to do it.
>
> Big thanks
>
> On Wednesday, August 23, 2017 at 11:56:20 PM UTC+7, Ytai
If I understand correctly, what you're seeing is typical to forgetting to
include the intent filters in the manifest, such as here:
https://github.com/ytai/ioio/blob/master/software/applications/HelloIOIO/src/main/AndroidManifest.xml#L8
On Fri, Aug 18, 2017 at 6:46 AM, 'Marcel Brandenburg' via
Sampling the frequency and integrating will give you an estimate of the
total. If it's not accurate enough, you'll need to count.
On Aug 22, 2017 2:51 PM, "Maximillian" wrote:
> Hi Ytai,
>
> This is my current code (trimmed for this post)
>
>
> int FLOW_METER_PIN =
It is known, but there isn't currently a plan to add it. If anyone wants to
contribute a patch, I will happily consider adopting it.
On Aug 13, 2017 8:21 PM, "Maximillian" wrote:
> Is this still a known missing feature? As this post is from 2013.. I need
> to use flow
There could possibly be intermittent shorts to ground that would explain
that. Otherwise, I'm not aware of anything more obvious that would explain
that behavior.
On Aug 19, 2017 2:18 PM, "JP" wrote:
> Hi Ytai!
>
> The IOIO V1 board I'm using for my anemometer probably
I don't think the probe actually emits negative voltage. I think the table
is an example with voltages relative to some offset that the next section
describes how to measure. Essentially, you're doing a 2-parameter
calibration.
If you're unsure, connect a voltmeter to the sensor before connecting
I don't know that there's anything that can be done about this, as it is
the phone that determines how much current to draw (up to a 500mA limit,
specified by the USB standard). Perhaps there's some protocol that I'm not
aware of to let the phone know it can draw more.
To make sure that what
IOIO Hardware Tester is not part of the official IOIO codebase. I have
never seen the source code and can not vouch for its quality or feature set.
Adding AOA support to your app should be a simple matter of adding a
dependency on the IOIOLibAndroidAccessory library via your Eclipse project
or
Just post it somewhere and send me a link.
On Jun 21, 2017 15:23, "Ante Brkic" wrote:
> Thanks a lot for the answer and suggestion!
>
> I figured out that the reason for failure was custom made usb cable which
> probably got short-wired during the stress test. So I got new
It is hard to tell exactly what was the failure mode. If you indeed
correlate the failures with physical damage, consider making sure the
electronics are well protected against shorting or cutting off during
flipping. What I often do in my hacky projects is bury electrical
connections in hot glue
What does the log say?
On May 18, 2017 1:12 PM, wrote:
> Hi,
>
> I have tried to implement the SPI master using the example HELLOIOIO
> SPI example. My application is terminating (It says ioio disconnected ) on
> toggling the button.
>
> Here is my looper code
>
>
Do the precompiled apps (e.g. HelloIOIO) work? If so, it is probably an
issue with how you're building your app (see build files of example apps).
On May 30, 2017 4:17 PM, "Oscar Prom" wrote:
> A Google Pixel (running Android 7.1) won't connect to a IOIO board when
> using
You need only the aar. See the example apps for how to specify the
dependencies correctly.
On Thu, May 25, 2017 at 6:22 PM, wrote:
> when I try to add the aar and jar library to the android studio project,
> building failed with this error.
>
> Error:Execution failed for
Did you remember to turn USB debugging off?
On Thu, May 18, 2017 at 2:02 PM, theodore peters
wrote:
> Hello,
>
> I have the IOIO-OTG and when I use it as a Device and the android as the
> Host, the examples(and my app) work well.
> When I switch the Host and Device
IOIOLibCore translates the main IOIO API (ioio.lib.api.*) into a
bidirectional serial protocol that the IOIO understands.
IOIOLibAndroid adds an implementation of the serial channel over TCP/ADB as
well as ties the IOIO application model (IOIOLooper, etc) into the Android
application framework.
I don't know specifically about this radio, but indeed SPI is possible.
Usually, unless the device has some weird timing requirements, there should
be no problem. You should be able to translate the Arduino-based library to
Java.
Alternatively, you can leave the Arduino in the loop and use the
With the latest firmware, when powering the IOIO and connecting to the
phone, are you getting a charge icon or a dialog asking for which
application to run?
Also, have you tried using the IOIO as a USB device rather than a host?
On Feb 13, 2017 4:04 PM, "Ahmed Khalil"
Both are path problems:
For the script to work you need to have the mplab bin directory in your
path.
Then you need mplab to know about your toolchain locations. This is done
from the tools menu of mplab, where you can add toolchains.
On Jan 27, 2017 05:24, "Pranay Sharma"
This smells like an electrical problem. What are the electrical specs of
the modem? How exactly are you connecting it to the IOIO?
As an aside, your loop() doesn't block (i.e. spin-loops) whenever there is
no data in the UART, which is a very bad practice (maxes out CPU, drains
battery). You
This is not an inductor but a ferrite bead.
Please build with XC16 using a clean clone. I don't want to waste time
troubleshooting a non-standard environment.
On Sat, Jan 21, 2017 at 6:03 AM, wrote:
> I'm asking this question because I'm in doubt that is this really a
>
Typically relays require significant current through their coils compared
to the amount of current you want to run through your pins. A simple
circuit with a transistor and a flyback diode per relay is recommended.
On Jan 18, 2017 10:46 PM, "Malik Atta ur rehman" <
malikattaurrehman...@gmail.com>
Your project might have gotten messed up during the experimentation. Can
you try building a fresh copy now that you have the right compiler?
On Jan 18, 2017 11:49 PM, wrote:
> Hello Ytai,
> I'm attempting to use MPLAB X v3.50 with xc16 compiler V1.30. The
> individual sub
I'm assuming your question is the one in the subject and not in the message
body. The answer is no, it is not currently supported. At some point I
considered adding WiFi dongle support and never got around to it. Should be
physically possible but new firmware will need to be written.
--
You
You can install the latest firmware version (v5.06 currently) on the IOIO
v1 and you'll get OpenAccessory support.
On Tue, Jan 3, 2017 at 5:57 AM, Ian Forbes wrote:
> Hi
>
> I have an old ioio V1 board that I connect to a Dell 5 PDA to run "XCSoar"
> software. The Dell
Why would you use an external oscillator as opposed to just an external
crystal?
On Dec 22, 2016 7:17 AM, "P.S" wrote:
> Dear Ytai and All,
> We were choosing http://www.mouser.com/ds/2/96/008-0256-0-786323.pdf to
> be used as an external oscillator.
> Any comments or
They're definitely still being manufactured and sold by SparkFun and
SeeedStudio. Might be a temporary holiday-related shortage.
On Tue, Dec 20, 2016 at 12:27 PM, Tim Archer wrote:
> Hello Ytai,
>
> Is the IOIO OTG board still being manufactured or is a new version in the
I don't know of any specific issues with Android 6. The IOIO hardware
tester app is not an official IOIO tool and has not been maintained in a
very long time so I wouldn't expect it to work.
Regardless of apps, when you disable USB debugging and connect the IOIO,
does the accessory dialog pop up?
Physically, you have everything you need to do that, but you're looking
into weeks of custom firmware development to support this use case. There
are probably easier solutions.
On Dec 13, 2016 09:00, "Ken Perry" wrote:
> I have a custome VCP device. It also supports HID.
The only way to do it in the existing app framework is to have the service
manager both connections and share one of them with the app through an API.
Alternatively, you can make changes to the application framework, allowing
the client to specify which connection types to consider when starting
No special tips. Just make sure every component you use is rated for this
range and that its critical parameters within the desired range across the
temperature range you want to support.
On Dec 7, 2016 11:55 PM, "P.S" wrote:
> Dear Ytai,
> I will be starting to make a version
First, to both of you: I wouldn't use Bluetooth for something that needs to
work flawlessly 24/7. Not sure if the problem is the standard, the Android
stack, the IOIO stack, the dongles or whatever, but from my experience,
connection is not 100% reliable. If your code is tolerant to occasional
I would try a different dongle and/or recalibrate the IOIO oscillator as
described in the wiki under calibration wipe. I've seen cases where data
losses occur silently with some dongle/phone combination, resulting in a
disconnect.
>From your logs I see no evidence of disconnects though. Would you
Yes, that should work fine, as long as you remember to use a pull down
resistor on the pin (either internal or external) to assert a valid 'low'
condition when the relay is open.
Another way to accomplish the same thing, which is probably what I would
do, is to have the relay pull to GND while
Yeah sure, all pins can handle 0..3.3V (and some up to 5V).
What you're describing sounds a bit strange, but maybe only because I don't
fully understand what you're trying to do.
On Mon, Nov 14, 2016 at 10:05 PM, David Messem
wrote:
> Hi IOIO users!
>
> Apologies if this
Yes. The achievable rates are all of:
400 / N
100 / N
for any N in 1..65536
So, for example, you can do 4M or 2M or 1.33M or 1M, etc.
On Thu, Oct 20, 2016 at 3:12 PM, Jose Rojo wrote:
> hi.. I tried UART up to 115200 bps... question.. can the IOIO OTG go
>
OK. I will try to use your bundle and see if I can figure it out. Might be
a few days.
On Mon, Oct 10, 2016 at 11:52 AM, Martin Jensen wrote:
> It's still responsive. With same program I can write the standard firmware
> right after.
> Versions output:
>
> IOIO Bootloader
After this failure, is the IOIO bootloader still responsive, i.e. if you
run ioiodude versions, what do you get?
On Mon, Oct 10, 2016 at 11:42 AM, Martin Jensen wrote:
> There you go:
>
> Writing image...
> java.io.IOException ]
> at
Yeah, you should be able to build ioiodude yourself from source. It's on
GitHub as part of the IOIO repository.
On Mon, Oct 10, 2016 at 11:21 AM, Martin Jensen wrote:
> I managed to put the standard firmware on it just fine with ioiodude103.
> I'm gonna see if I can get the
Hey, see inline.
On Wed, Oct 5, 2016 at 2:52 PM, Kevin Miller wrote:
> I'm connecting a IOIO to a hobbyist robot which also has a UART. I plan to
> use the IOIOService because there will be other sensors attached to the
> IOIO by UART and I want to be able to handle I/O in
1. The errors you're seeing are a symptom of data corruption between the
IOIO and the phone. I works suspect the dongle or the phone.
2. The timer value you're setting is limited to 16 bit, so 65535 is your
max. You can slow down the timer or use a different one, but this will have
other
Should be easy. There are numerous threads on this forum about how to do
this. The first and most significant step is to be able to build and
install the stock firmware yourself. The rest is really easy.
On Oct 2, 2016 3:27 PM, "Martin Jensen" wrote:
> Can I reprogram the IOIO
The IOIO doesn't support hubs
On Oct 2, 2016 11:31, "Martin Jensen" wrote:
> Yeah that must be it. I will look into the adapters first,however it seems
> the device is the problem. I've tried with a USB hub, but it said something
> about not having exactly two interfaces and
Can you please try a non IOIO app?
On Sep 29, 2016 16:03, "Kevin Miller" wrote:
> It is specific to Android services. I can debug activities in the same
> app, but breakpoints and Log commands inside the IOIOService are ignored.
> The app is a slight derivation of the
Are you able to debug any app using this setup? In other words, is this
problem specific to IOIO apps?
On Sep 29, 2016 12:39, "Kevin Miller" wrote:
> I did a IOIO project a year ago with the same phone and same IOIO and same
> laptop, same BT dongle for the IOIO, and I'm
https://learn.sparkfun.com/tutorials/ioio-otg-hookup-guide
On Tue, Sep 27, 2016 at 11:47 AM, Cesar Quiroz wrote:
> Hello Ytai
>
> I wanna to install the software via Linux Ubuntu. How to procedure with
> this?
> I don't found tutorial to explain this.
>
> Can you help me,
Does this happen with the precompiled apps too?
On Mon, Sep 5, 2016 at 10:56 AM, Martin Jensen wrote:
> I've got two IOIO's on bluetooth which works on my two Samsung tablets,
> Tab 2 7.0 (5.1.1) and Note 10.1 (6.0.1) but not on my Lenovo Tab 2 A7-10
> (5.0)
>
> It gives me
I've definitely seen some dongles in the past that are what's called a USB
compound device, meaning they apart as a USB hub with one or more devices
hanging off of it. Those aren't supported since hubs are not supported.
There might be similar quirks with other dongles.
On Sep 6, 2016 6:39 PM,
What you're describing sounds like an electrical issue.
You get what you pay for... Those are low quality knock-offs, which are
unlikely tested before being shipped.
Might have better luck with a board from SparkFun and SeeedStudio, which is
guaranteed to be manufactured to high standard and
This doesn't seem like a IOIO specific question, but rather a general
question about exception handling in Java.
In short, you have to either catch the exception or specify it as being
thrown out of the calling method. Why is that a problem in your case?
See IOIOSimpleApp for an example for how to
This doesn't seem like a IOIO-related question. You might have better luck
on StackOverflow.
On Mon, Aug 1, 2016 at 3:53 PM, Ilan Tal wrote:
> I've got the basic ioio connection going. I can sample 2 analogue pins.
> The next step is to try to graph the results.
> In
Does it work with the stock firmware bundles? If so, probably something
about your custom bundle being corrupted.
On Jul 30, 2016 19:02, "Tinuz77" wrote:
> Hi Ytai,
>>
>
> Great work on the IOIO. I created a custom firmware for my lasertag
> project but i get the
With the risk of stating the obvious, are the grounds of the IOIO and
Arduino connected?
I don't see any fundamental problem with the code, but maybe overlooking
something.
On Jul 30, 2016 05:16, "'Nick Jonas' via ioio-users" <
ioio-users@googlegroups.com> wrote:
> Hello!
>
> I'm trying to have
You can check the release notes page on the wiki. I find it surprising that
it had anything to do with the firmware. Are you convinced that the
difference isn't only due to a IOIOLib version difference?
On Jul 25, 2016 00:56, "oliver.hadasch via ioio-users" <
ioio-users@googlegroups.com> wrote:
Yeah, unfortunately PureJavaComm is a bit inconsistent when it comes to
handling these corner cases. One opening sequence that works on Linux
wouldn't necessarily work on Windows or OSX etc. Glad you found a solution.
On Jul 22, 2016 23:02, "oliver.hadasch via ioio-users" <
Does /dev/IOIO0 exist after boot? If so, what happens if you try to access
it with 'screen'?
On Jul 21, 2016 12:14 AM, "oliver.hadasch via ioio-users" <
ioio-users@googlegroups.com> wrote:
> Sorry for the double posting, I thought it did not work.
>
> With IOIOLibCore-5.05.jar and
Use the latest firmware version. Try downgrading the library version to the
previous one.
On Jul 20, 2016 9:51 PM, "oliver.hadasch via ioio-users" <
ioio-users@googlegroups.com> wrote:
> Hi,
>
> I have a problem with a IOIO PC application on Debian ARM systems.
> Same problem on Banana pro with
Since you're not using the provided application framework, what you need to
look at is not how the example applications work (because they *do* use
it), but rather how the framework itself works.
A good starting point is here:
Yes, you can definitely do that. This is exactly how the firmware upgrades
I'm distributing work.
Once you have a hex file, there are a bunch of utilities in the /tools
directory that help you convert it to a .ioioapp bundle file, which can
then be read by IOIODude and flashed on the IOIO over
The table titled "internal RC accuracy" in the datasheet specifies a
typical 0.15% deviation, but a worst case 1% across the temperature range.
USB's nominal requirement is 0.25%. So if you want to be 100% certain you'd
need to add a crystal to the circuit (and make a configuration flag change
in
I haven't done any work to characterize the temperature range or design for
a specific one. You'd have to do that be checking the datasheets of the
individual parts. I'm assuming that 85C should be safe for most if not all
parts. Another thing you'd need to evaluate is how stable the internal
Bit banging is not something that is typically possible with the IOIO.
Implement general purpose support is a lot of work and probably involved
implementing some kind of a small interpreter running the IOIO.
I'm not currently planning on adding 1-wire support either, as it is not a
super popular
Here's how to force an oscillator calibration:
https://github.com/ytai/ioio/wiki/IOIO-OTG-Bootloader-and-IOIODude#configuration-wipe
The blink app does not identify itself as a USB device, so it is expected
that you'll only be able to talk to your PC from the bootloader at this
point. Does it
There are various ways to do this. Once of the simpler ones is to have some
communication mechanism between the UI thread and the IOIO thread, such as
a shared variable holding the file object, or null if nothing is to be
sent. You can then use Java's wait/notify to synchronize the threads, e.g.
I don't think there's anything fundamentally problematic with Android 6.
You definitely need to have USB debugging off. If the accessory dialog
doesn't pop up, it is more likely a problem with the tablet than with the
IOIO.
You may try running the IOIO in device mode and see whether this works.
On
will allow you to set a 1ms sleep without the pulse
>> collapsing, but no guarantees on maximum width, it may come out wider than
>> 1ms.
>> On Apr 12, 2016 3:02 PM, "Vic Wintriss" <vic.wi...@jointheleague.org>
>> wrote:
>>
>> Ytai:
>>
>>
was able to move the servo motor, but only
> where it is physically connected IOIO. I ask tip suggestions on what to
> control it from the other android phone (have control over wifi).
> thanks advance
>
> 2016-06-13 22:54 GMT+02:00 Ytai Ben-Tsvi <yta...@gmail.com>:
>
Is this specific to a service or does it also happen with an activity? Does
it happen with the precompiled examples HelloIOIO and/or HelloIOIOService?
On Jun 17, 2016 9:50 AM, "Matthew Pegula" wrote:
> Following up on Nick's post (we're teammates) this issue only seems to
There's already a b4a library for IOIO. Maybe use that?
On Jun 17, 2016 6:17 AM, "István Rostás" wrote:
> Thank you for reply. I red Sparkfun and build my own ioiolibandroid.jar.
> Then I extracted the non-activity part of the HelloIOIO and IOIOService
> example app to
There are maven targets for the libraries. Please refer to the wiki and or
example apps. Can you please test the precompiled apps before proceeding to
you own built ones?
On Jun 16, 2016 15:58, "Daniel Buchanan" wrote:
> Hi Ytai,
>
> It does show up as /dev/IOIO0,
Using the IOIO as a programmer for another is a pretty esoteric feature,
specifically developed to allow users to upgrade the bootloader between
version 1and 2 some five years ago. This need became pretty obsolete as
soon as IOIOs started shipping with newer bootloaders and later with the
This is not the intended usage. Please refer to the example apps or the
beginner tutorial from SparkFun.
On Jun 15, 2016 02:51, "István Rostás" wrote:
> Hi Guys!
> I have a small looper class (from the helloioio sample), what I
> instantiate so:
> private Looper ls;
> ls =
The latest firmware assumes xc16
On Jun 15, 2016 12:31, "David" wrote:
> Thanks. Solved the issue such a silly mistake forgot to take pin 33 to
> ground as I am powering up the phone from the pcb.
>
> To compile code in mplabx I can use the xc16 compiler? Is there
Is the new board appearing as a /dev/IOIOx device? Are you using the exact
same jar with both versions? What's the deal with the undefined IOIOLib
version?
There have been some changes in the library that may have caused this
problem, but I cannot see how the firmware version is related.
On Jun
I don't know this app at all, but from a quick scan it seems like the
IOIO-related stuff takes place in:
https://github.com/akexorcist/IOIO-CameraRobot/blob/master/app/src/main/java/app/akexorcist/ioiocamerarobot/ioio/IOIOControllerActivity.java#L329
You'd need to open PwmOutput on whatever pin
You seem to be doing the right thing. I would suspect your hardware. Did
you deviate in any way from the standard circuit? Especially around the USB
and vbus area.
On Jun 11, 2016 08:08, "David" wrote:
> HI Can anyone help me. When you download the devboot
1 - 100 of 941 matches
Mail list logo