Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Filesystems/Discussion/General/usblauncher creation/List of Posts
Forum Topic - usblauncher creation: (4 Items)
   
Update
Christopher Olarti(deleted)
06/12/2014 2:17 PM
post110678
usblauncher creation   
What would I do to initialize the usblauncher so i can update the necessary usb descriptors when making the i.MX6 
SabreLite a Client/Device.  I am trying to initialize the feature during the bootscript and I am unable to see the /etc/
usblauncher/ directory.

Specifications:
QNX6.6 with BSP
i.MX6 SabreLite

Thanks.
Andrew Sherk
06/12/2014 4:57 PM
post110683
RE: usblauncher creation   
To get the /etc/usblauncher directory: the files are on your host (e.g. D:\qnx660\target\qnx6\etc\usblauncher) and you'd
 need to modify the build file for the BSP so that they are included in the IFS, or otherwise mount a filesystem that 
has these files so they are available on the target.

You'll need to start pps, usblauncher with a config file with the Host_Stack and Device_Stack sections enabled (the /etc
/usblauncher/rules.lua has them commented out, remove --[[ and --]] markers to do this) then refer to

http://www.qnx.com/developers/docs/660/topic/com.qnx.doc.dev_pub.ref_guide/topic/usblauncher_stack_modes.html 

and

http://www.qnx.com/developers/docs/660/index.jsp?topic=%2Fcom.qnx.doc.dev_pub.ref_guide%2Ftopic%
2Fusblauncher_config_usb_descriptors.html

for updating the USB descriptors.

On the target

# pps
# mkdir /pps/qnx
# usblauncher -vvv -c /etc/usblauncher/rules.lua

The usblauncher command-line options are described here:
http://www.qnx.com/developers/docs/660/index.jsp?topic=%2Fcom.qnx.doc.dev_pub.ref_guide%2Ftopic%2Fusblauncher_usage.html


Cheers,
Andy

-----Original Message-----
From: Christopher Olarti [mailto:community-noreply@qnx.com] 
Sent: Thursday, June 12, 2014 2:17 PM
To: general-filesystems
Subject: usblauncher creation

What would I do to initialize the usblauncher so i can update the necessary usb descriptors when making the i.MX6 
SabreLite a Client/Device.  I am trying to initialize the feature during the bootscript and I am unable to see the /etc/
usblauncher/ directory.

Specifications:
QNX6.6 with BSP
i.MX6 SabreLite

Thanks.




_______________________________________________

General
http://community.qnx.com/sf/go/post110678
To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
Christopher Olarti(deleted)
06/12/2014 5:32 PM
post110684
Re: RE: usblauncher creation   
Thanks for the response.  However, when looking for the .build file that I should update, I came across  3 other .build 
files.  The following is the original .build file that I am using:

/prebuilt/armle-v7/boot/build/sabrelite.build

However, the following are other .build files that I found:

/src/hardware/startup/boards/imx6x/sabrelite/build.build

/src/hardware/support/appsmedia-sample/appsmedia-sample-common.build
/src/hardware/support/appsmedia-sample/appsmedia-sample-imx6.build


Also when looking in the build scripts themselves, I am not exactly sure where to include the usblauncher location from 
the Host... If the modification is in sabrelite.build, then would it be under .console.sh when setting the environment 
variables, or would it be with .bootstrap when identifying the PATHs and LD_LIBRARY_PATH.


Thanks.
Andrew Sherk
06/17/2014 3:14 PM
post110721
RE: RE: usblauncher creation   
Is your build file setup so that an inserted SD card is mountable? Maybe for starters, it'll be easier for you to copy 
over the 'usblauncher' binary and /etc/usblauncher files to the SD card and mount it after the system is booted, instead
 of modifying the IFS.

What is the location of the qnx660 install?
If for example the location (on Linux) is /opt/qnx660

then you'll find the etc files here:

/opt/qnx660/target/qnx6/etc/usblauncher

The executable binary here

/opt/qnx660/target/qnx6/armle-v7/bin/usblauncher

If your SD card is DOS, you could copy the binary to /dev/shmem, then set it executable (chmod +x usblauncher). For 
development purposes you can also mount a DOS filesystem as executable to run Neutrino binaries from it.

Help working with BSPs:
http://www.qnx.com/developers/docs/660/index.jsp?topic=%2Fcom.qnx.doc.neutrino.building%2Ftopic%2Fbsp.html

Making the IFS with 'mkifs' via the command-line:
http://www.qnx.com/developers/docs/660/index.jsp?topic=%2Fcom.qnx.doc.neutrino.utilities%2Ftopic%2Fm%2Fmkifs.html

Note: for general questions about usblauncher, feel free to post to the OS Meta forum:
http://community.qnx.com/sf/discussion/do/listTopics/projects.core_os/discussion.metawiki

For BSP-specific questions you can post to the BSP forum:
http://community.qnx.com/sf/discussion/do/listTopics/projects.bsp/discussion.bsp

Cheers,
Andy

-----Original Message-----
From: Christopher Olarti [mailto:community-noreply@qnx.com] 
Sent: Thursday, June 12, 2014 5:33 PM
To: general-filesystems
Subject: Re: RE: usblauncher creation

Thanks for the response.  However, when looking for the .build file that I should update, I came across  3 other .build 
files.  The following is the original .build file that I am using:

/prebuilt/armle-v7/boot/build/sabrelite.build

However, the following are other .build files that I found:

/src/hardware/startup/boards/imx6x/sabrelite/build.build

/src/hardware/support/appsmedia-sample/appsmedia-sample-common.build
/src/hardware/support/appsmedia-sample/appsmedia-sample-imx6.build


Also when looking in the build scripts themselves, I am not exactly sure where to include the usblauncher location from 
the Host... If the modification is in sabrelite.build, then would it be under .console.sh when setting the environment 
variables, or would it be with .bootstrap when identifying the PATHs and LD_LIBRARY_PATH.


Thanks.






_______________________________________________

General
http://community.qnx.com/sf/go/post110684
To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems