Sorry for the double posting, I thought it did not work.

With IOIOLibCore-5.05.jar and IOIOLibPC-5.05.jar and firmware IOIO0506

After boot:

[I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0505

[D/IOIOConnectionRegistry] Successfully added bootstrap class: 
ioio.lib.pc.SerialPortIOIOConnectionBootstrap

[D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0

[D/IOIOImpl] Waiting for IOIO connection

[V/IOIOImpl] Waiting for underlying connection

[V/IOIOImpl] Waiting for handshake


After disconnect and reconnect from USB:

[I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0505

[D/IOIOConnectionRegistry] Successfully added bootstrap class: 
ioio.lib.pc.SerialPortIOIOConnectionBootstrap

[D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0

[D/IOIOImpl] Waiting for IOIO connection

[V/IOIOImpl] Waiting for underlying connection

[V/IOIOImpl] Waiting for handshake

[I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
Bootloader ID: IOIO0400 Firmware ID: IOIO0506

[V/IOIOImpl] Querying for required interface ID

[V/IOIOImpl] Required interface ID is supported

[I/IOIOImpl] IOIO connection established

INFO: IOIO-Looper created


Am Mittwoch, 20. Juli 2016 21:04:08 UTC+2 schrieb Ytai:
>
> 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" <
> [email protected] <javascript:>> wrote:
>
>> Hi,
>>
>> I have a problem with a IOIO PC application on Debian ARM systems.
>> Same problem on Banana pro with Debian 8, Raspberry PI with Debian 8 and 
>> Cubietruck with Debian 7.
>> When the IOIO is connected to the USB-Port while the system boots, the 
>> application does not connect to the IOIO.
>> When I connect the IOIO to the USB port after the system has booted, it 
>> works without any problems.
>> On a mac book with El Capitan it also works as expected.
>>
>> udev rules are installed and in all cases I get the /dev/IOIO0 device and 
>> also the /dev/ttyACM0 device.
>>
>> *With aplication version IOIO0500:*
>> [I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0507
>> [D/IOIOConnectionRegistry] Successfully added bootstrap class: 
>> ioio.lib.pc.SerialPortIOIOConnectionBootstrap
>> [D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0
>> [D/IOIOImpl] Waiting for IOIO connection
>> [V/IOIOImpl] Waiting for underlying connection
>> [V/IOIOImpl] Waiting for handshake
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0500
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0500
>> [V/IOIOImpl] Querying for required interface ID
>> -> here it stops
>>
>> When I start it once again it works.
>> [I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0507
>> [D/IOIOConnectionRegistry] Successfully added bootstrap class: 
>> ioio.lib.pc.SerialPortIOIOConnectionBootstrap
>> [D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0
>> [D/IOIOImpl] Waiting for IOIO connection
>> [V/IOIOImpl] Waiting for underlying connection
>> [V/IOIOImpl] Waiting for handshake
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0500
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0500
>> [V/IOIOImpl] Querying for required interface ID
>> [V/IOIOImpl] Required interface ID is supported
>> [I/IOIOImpl] IOIO connection established
>>
>>
>> *With aplication version IOIO0506:*
>> [I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0507
>> [D/IOIOConnectionRegistry] Successfully added bootstrap class: 
>> ioio.lib.pc.SerialPortIOIOConnectionBootstrap
>> [D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0
>> [D/IOIOImpl] Waiting for IOIO connection
>> [V/IOIOImpl] Waiting for underlying connection
>> -> here it stops
>>
>> Starting it once again does also not work with IOIO0506
>>
>> After disconnecting the IOIO from USB and reconnecting it, it works:
>> [I/IOIOBaseApplicationHelper] Using IOIOLib version: IOIO0507
>> [D/IOIOConnectionRegistry] Successfully added bootstrap class: 
>> ioio.lib.pc.SerialPortIOIOConnectionBootstrap
>> [D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/IOIO0
>> [D/IOIOImpl] Waiting for IOIO connection
>> [V/IOIOImpl] Waiting for underlying connection
>> [V/IOIOImpl] Waiting for handshake
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0506
>> [I/IncomingState] IOIO Connection established. Hardware ID: SPRK0020 
>> Bootloader ID: IOIO0400 Firmware ID: IOIO0506
>> [V/IOIOImpl] Querying for required interface ID
>> [V/IOIOImpl] Required interface ID is supported
>> [I/IOIOImpl] IOIO connection established
>>
>> The way how I start it is a class derived from IOIOConsoleApp with run, 
>> createIOIOLooper, ...
>>
>> Hardware version: SPRK0020
>> Bootloader version: IOIO0400
>>
>> Libraries in my aplication are: IOIOLibCore-5.07.jar and 
>> IOIOLibPC-5.07.jar
>>
>> I am now fighting since days to find a way to get it running 
>> automatically after the system boots (/etc/init.d/...)
>>
>> Thanks in advance
>>
>> -- 
>> 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 https://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 https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to