Hi Christopher,

Could you add -vvvl to the usblauncher command-line, then run sloginfo -t and provide the output?
This turns up the verbosity setting so that we can see what usblauncher's doing at each step. The -l sends the output to
 slogger.

Until you get everything working correctly, I recommend running

echo "start_stack::device,2" >> /pps/qnx/usb_ctrl

manually, instead of in the boot script.

You can run sloginfo in the background, and observe any new output as a response to the commands you enter on the 
console:

sloginfo -wt &

then

echo "start_stack::device,2" >> /pps/qnx/usb_ctrl

What output do you see?

It's ok to leave the first io-usb running. You'll need this to use the non-OTG port.  devb-umass appears to fail with "
xpt_configure: umass SIM attach failure" since the first io-usb instance is not running now.

If you have the first io-usb instance running (started by the boot script), then let usblauncher start the io-usb-dcd 
for the other controller, you'll be able to connect a USB cable between the two ports and run 'usb' or 'devb-umass' to 
test out the client device all on one target.

-Andy


-----Original Message-----
From: Christopher Olarti [mailto:community-noreply@qnx.com] 
Sent: Thursday, June 19, 2014 1:00 PM
To: osmeta-core_os
Subject: Re: RE: RE: USB Device - usblauncher unable to update from *.lua files

Hi Andy,

Please find the attachment to be the latest actions for running usblauncher.  I included the *.build file and the log 
file.

I commented out the initialization of the USB OTG Mass at the .script portion and made the console.sh run usblauncher -h
.  I did update the *.lua files to be recognized in dev/io-usb-dcd instead of dev/otg/io-usb-dcd.  I also included in 
the console.sh the echo "start_stack::device,2" for umass after executing usblauncher.

I noticed in the log file, with "pidin arg", I did not see the device driver for a umass.





_______________________________________________

OSMeta
http://community.qnx.com/sf/go/post110765
To cancel your subscription to this discussion, please e-mail osmeta-core_os-unsubscribe@community.qnx.com

Hi Christopher, 

Ok, let's try it from another angle, since you had usblauncher started somehow.

- don't mount the ram disk to / at boot up so we can rule out a problem with where /pps/qnx/device/usb_ctrl is being 
written to
- start pps with -m /pps/qnx

then try the echo "start_stack::device,1" etc. as before.

If you're still having problems it may be best to arrange a screen share / WebEx through your QNX contact (portal) so 
that we can walk you through the steps live.

-Andy

-----Original Message-----
From: Christopher Olarti [mailto:community-noreply@qnx.com] 
Sent: Thursday, June 19, 2014 5:23 PM
To: osmeta-core_os
Subject: Re: RE: USB Device - usblauncher unable to update from *.lua files

Hi Andy,

I apparently do not have a bin/usblauncher.

# ls bin/
sh           slog2info




But in my build script, it does contain the binary:





# Redirect console messages
[type=link] /bin/sh=/proc/boot/ksh
[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem

# Programs require the runtime linker (ldqnx.so) to be at a fixed location

# Shared libraries
libc.so
libm.so.2

##############################################################
## Multimedia Publishing
##############################################################
/bin/usblauncher=usblauncher

[search=${QNX_TARGET}/etc/usblauncher]
/etc/usblauncher/rules.lua=rules.lua
/etc/usblauncher/umass.lua=umass.lua
/etc/usblauncher/usbser.lua=usbser.lua

[search=${QNX_TARGET}/armle-v7/lib/dll/pubs]
/lib/dll/pubs/pp-generic.so=pp-generic.so

#Restore search path
[search=${MKIFS_PATH}]


should i include usblauncher as a general command?



_______________________________________________

OSMeta
http://community.qnx.com/sf/go/post110774
To cancel your subscription to this discussion, please e-mail osmeta-core_os-unsubscribe@community.qnx.com

I left everything close to the original file, except I included information for slogger2.

I performed the following commands

#pps -m /pps/qnx
#usblauncher -h -vvvl -p 2 -t -s /lib/dll/pubs/ echo "start_stack::device,1" >> /pps/qnx/usb_ctrl

However I do not see the USB Serial in the PC Device Manager, like i would if i uncommented

    ##############################################################
## USB OTG port (operating in device mode)...
## The commands below will configure the i.MX6 OTG port as a Mass Storage Device
#############################################################  
    Example of CDC-ACM (serial) device #####

    #display_msg Configure USB Serial Device

    # Step 1 - Start USB device stack
    #io-usb-dcd -dusbser-mx6sabrelite-ci ioport=0x02184000,irq=75
    #waitfor /dev/io-usb-dcd/io-usb 4
    #waitfor /dev/io-usb-dcd/devu-usbser-mx6sabrelite-ci.so 4

    # Step 2 - Start USB CDC-ACM function driver and enable USB soft connect
    #devc-serusb_dcd -e -v -F -s -d iface_list=0,unit=1
    #waitfor /dev/serusb1 4 
    #ulink_ctrl -l 1