> Hi Todd,
> 
> I'm not very familiar with USB but I don't think io-pkt should crash. Do 
> you happen to have a core file from when io-pkt crashes? It sounds like 
> you did some analysis on it because you say USB is not fully 
> initialized? Or, by "die", do you mean something else?

io-pkt exits via SIGKILL if I just do a waitfor /dev/io-usb/io-usb (instead of sleep), as suggested. The waitfor did 
work under QNX6.3.2. sloginfo does not provide any clues as to why it exited, except that I see a bunch of io-usb stuff 
following where io-pkt tries to launch. io-pkt was running OK today and actually did crash with SIGSEGV while I was at 
lunch (nothing really running on the board).

Process 4102 (io-pkt-v4) terminated SIGSEGV code=1 fltno=11 ip=01088cd4

> 
> You could try maybe "waitfor /dev/io-usb/io-usb" as described here:
> http://www.qnx.com/developers/docs/6.4.1/neutrino/user_guide/hardware.html#USB
>  
> scroll down to "Ethernet adapters".
> 
> Cheers!
> /P
> 
> Todd Peterson wrote:
> > In 6.3.2, I start the USB driver:
> >
> > io-usb -vvv -dohci ioport=0x31020000,irq=59,verbose=5
> >
> > and then waitfor /dev/io-usb/io-usb
> >
> > and then start io-net
> >
> > In 6.4.1, if I follow the same steps, except use io-pkt,  io-pkt dies, 
> because the USB is not fully initialized. If I do a sleep 2, and then start io
> -pkt, it works fine. But, I hate using a sleep, instead of waiting for some 
> evidence that the USB is up. 
> >
> > Any suggestions?
> >
> > working .bsh snippet:
> >
> > io-usb -vvv -dohci ioport=0x31020000,irq=59,verbose=5
> > sleep 2
> > io-pkt-v4 -d asix -p tcpip
> >
> >
> >
> >
> > _______________________________________________
> >
> > io-net migration
> > http://community.qnx.com/sf/go/post37047
> >
> >