Feed for discussion QFC General in project QNX Foundation Classes.

post113848: USB fucntion driver

2015-05-22T10:24:12Z

Hi ,

I am trying to write simple usb function driver with bulk end points on ti J6 platform,we are able to attache the descriptor to the device controller and enumartion succeed till get configuration descriptor but setconfuguration fails.

Do we have to do some thing from the application side (class driver side using libusbdci.so )to make it work?

Please le me know if there is some sample usb function class driver or some documentions regarding function drivers.

post99803: RE: QNX CAR performance details - Required

2013-03-12T09:39:57Z

FYI, QNX Car is not an Operating System, it is a development environment.

For other informations, please contact your local sales representative.

Regards,

Seyfettin Sunger

-----Original Message-----

From: Naveen Sudevan [mailto:community-noreply@qnx.com]

Sent: Tuesday, March 12, 2013 8:10 AM

To: general-qfc

Subject: QNX CAR performance details - Required

Hi

I am looking for "QNX CAR" Operating System details. Can you provide

me the bellow given details for selecting this OS.

1. OS Footprint ________

2. MMU support ________

3. Minimum clock required ________

4. Latency ________

5. Priority Level ________

6. Scheduler,Task switching time ________

7. Boot time ________

8. RAM Req (during execution - only for OS) ________

9. OS Modularity ________

11. Support Boot Loader ________

12. OS cost / licensing ________

13. Royalty cost

14. Tools cost (compiler/debugger/emulator/performance analyzer)

15. Widely used / emerging? ________

16. Forum / tech support availability ________

Naveen Sudevan

_______________________________________________

QFC General

http://community.qnx.com/sf/go/post99797

To cancel your subscription to this discussion, please e-mail

general-qfc-unsubscribe@community.qnx.com

post99797: QNX CAR performance details - Required

2013-03-12T06:10:25Z

Hi

I am looking for "QNX CAR" Operating System details. Can you provide me the bellow given details for selecting this OS.

1. OS Footprint ________

2. MMU support ________

3. Minimum clock required ________

4. Latency ________

5. Priority Level ________

6. Scheduler,Task switching time ________

7. Boot time ________

8. RAM Req (during execution - only for OS) ________

9. OS Modularity ________

11. Support Boot Loader ________

12. OS cost / licensing ________

13. Royalty cost

14. Tools cost (compiler/debugger/emulator/performance analyzer)

15. Widely used / emerging? ________

16. Forum / tech support availability ________

Naveen Sudevan

post52209: Re: Composite USB Device Driver: Can't Select Audio Interface And Auido I/O Error

2010-04-21T09:52:59Z

Hi Liu

I'm trying to understand how to write a class driver for and AudioStreming interface... I see that you managed some good data from the logitech USB camera. Can I ask you some sample code for setting up the USB audio class under QNX?

thanks in advance!

Davide

post32197: Composite USB Device Driver: Can't Select Audio Interface And Auido I/O Error

2009-06-22T12:27:01Z

Hi,everybody

   I have a composite usb device:

   1)A hid out to usb device, a video in to host with bulk transport mode , and an audio device in to host.

   2)There is only a configure for this Miscellaneous Device Class

   3)For the audio device's auido stream interface descriptor, there are two alternate setting . No. 0 with not endpoint ,and No.1 with an ISOCHRONOUS endpoint.

   I wrote insertion function to all the three device, but there is some question.

   1)In auido device insertion fucntion, if I run  the function of usbd_select_configure , then the function of usbd_select_interface will be ok;

    But , if I not run the usbd_select_configure, the the function of usbd_select_interface will failed and the return code will be EBUSY(16).It means that the audio device is in busy.

   For there is only one configure for devices and I think usbd_select_configure is not necessary.But why I should run this funciton.

  2)If I run the usbd_select_configure and usbd_select_interface ,so insertion process will be OK.Then when I open the auido device and receive data from, I can't get normal data : the status of URB is USBD_STATUS_CMP_ERR;the return value of  usbd_urb_status() is EIO(5).

   In my hand , I have an logitech web camera.The usb descriptor of logitech's audio in device is almost same as my audio in device.The only different thing the max packet size.I used my program to recevie audio data from logitech web camera , it looks ok.

  3)Audio device can't work with video and hid device.If I remove the auido device insertion function , the video and hid device will works ok;If I don't remove the audio device insertion function ,the receive function of video device and the send function of hid device will be locked.

   I followed the qnx refrence about usb ddk , I check my source code

and not sure how to fix those question.

   What can I do to find the reason and fix it.Thanks every much.

Best Regard

Liu Liming

post4100: Re: Poco

2008-01-07T19:01:02Z

> I didn't know about C++ 09 . I looked it up and but couldn't find anything

> related to thinks like FTP, mail, web, path, file handling etc.

It doesn't have anything like that (those are more like applet classes than language bindings to OS constructs).

C++ 09 has all the stuff that QFC might *overlap* with Poco (like thread classes etc.).

My plan is that the QFC stuff that will be replaced by C++ 09 will disappear in a QFC 2.0 revision when C++ 09 comes out, but that the interface to QFC specific classes will not change.

> I tried to play with BOOST but the thinks makes executable size incredibly big

> , which is why I really like Poco ( and it supports QNX6)

Boost is a playground, and many of the ideas from that will turn up in C++ 09, but should be much smaller (as embedded is a major emphasis of C++ 09).

>

post4096: Re: Poco

2008-01-07T18:25:47Z

> Mario,

>

> Rather than use "yet another general purpose class library", I am waiting for

> the new C++ standard (09) which will address all of the things that you have

> mentioned as overlap.  Until then QFC includes some of the classes that aren't

>  standardized, but are necessary for QFC (such as the thread class).

>

> Rennie

I  didn't know about C++ 09 .   I looked it up and but couldn't find anything related to thinks like FTP, mail, web, path, file handling etc.

I tried to play with BOOST but the thinks makes executable size incredibly big, which is why I really like Poco ( and it supports QNX6)

post4024: Re: Varia

2008-01-03T02:44:03Z

Mario,

I certainly welcome any enhancements to the documentation.

post4023: Re: Poco

2008-01-03T02:42:24Z

Mario,

Rather than use "yet another general purpose class library", I am waiting for the new C++ standard (09) which will address all of the things that you have mentioned as overlap. Until then QFC includes some of the classes that aren't standardized, but are necessary for QFC (such as the thread class).

Rennie

post2597: Poco

2007-11-13T15:07:13Z

Hello Rennie,

Have you ever consider building QFC on top of Poco. Poco is much more well rounded, and it`s portable between various platform. It has support for TCP/IP ( http, ftp, mail), xml, database, path handling, fancy logging and most POSIX primitive.

Of course it would be difficult to make the QNX specific stuff like resmgr and messaging portable, but that`s beside the point.

I think a resmgr would be more powerful if it would be build on top of say Poco::Util::Application.

Of course nothing prevents anyone from using QFC and Poco at the same time but there is so much redundencies ;-)

post2321: Varia

2007-10-26T18:02:42Z

Here is a run down of my first experience with QFC:

For some reason I have been unable to install any of the plug-in ( subversion, doxygen ) on my Eclipse setup (4.0.1).

Eclox ( Doxygen ) says " QNX Momentics QNX SDK (4.0.1.200709071150-7Z-589wAHwDupz02XvsAdeu5) requires feature "org.eclipse.cdt (3.0.1)", or compatible."

Subversion plug in shows:  Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information.

  ----- Current configuration problems -----

    QNX Momentics QNX SDK (4.0.1.200709071150-7Z-589wAHwDupz02XvsAdeu5) requires feature "org.eclipse.cdt (3.0.1)", or compatible.

  ----- Configuration problems after the operation -----

    QNX Momentics QNX SDK (4.0.1.200709071150-7Z-589wAHwDupz02XvsAdeu5) requires feature "org.eclipse.cdt (3.0.1)", or compatible.

    JDT Ignore Extensions (Optional) (1.0.4) requires plug-in "org.eclipse.jdt.core".

    Subversive Integration for the Mylyn Project (Optional) (1.0.9) requires feature "org.eclipse.mylyn.context_feature".

    Subversive Integration for the CSC Project Set Project (Optional) (1.0.5) requires feature "com.csc.dip.projectset.feature".

I manually check it out, ( on self hosted 6.3.2 ).  I have doxygen but not the dot modules , which made the generated documentation (html) unreadable.

I haven't try to use it so far, definitely interesting and Rennie, a big thanks.

I have been starting to play with the Poco library which is IMHO a very nicely designed C++ library.  I can't put my finger on it or make any positive suggestion but I do find that there is a lack of organisation in the QFC mainly when compare with Poco.  Or maybe it's just the way the resulting documentation is layed out, that does give a sense of "clarity".

I'll keep playing with it and try to come up with more constructive comment if applicable ;-)