<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>how to fix stall pid on usb generic out report</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42260/how-to-fix-stall-pid-on-usb-generic-out-report</link><description>Hello Nordic Expert, 
 I am facing a stall pid issue with nRF52840 Dongle using nRF5_SDK_15.2.0_9412b96. The chip build code is QIAA C0 . I started with usbd_hid_generic example and added an out endpoint. I then added the BLE part similar to the ble_app_blinky_c</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 21 Jan 2019 18:37:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42260/how-to-fix-stall-pid-on-usb-generic-out-report" /><item><title>RE: how to fix stall pid on usb generic out report</title><link>https://devzone.nordicsemi.com/thread/166967?ContentTypeID=1</link><pubDate>Mon, 21 Jan 2019 18:37:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:248ded9c-0eb0-4117-8981-c3c2caec6164</guid><dc:creator>HSh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thanks for letting me know. The ongoing discussion on the other thread has not helped me yet. I will try to find a way to share a simple version of my code for your further help.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to fix stall pid on usb generic out report</title><link>https://devzone.nordicsemi.com/thread/165792?ContentTypeID=1</link><pubDate>Tue, 15 Jan 2019 14:58:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4945a2b9-c97b-4c3f-8217-0fa4227d18b8</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In the other thread, the conclusion seems to be an &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/40364/problems-with-out-reports-on-usb-hid/165727#165727"&gt;issue with the user application&lt;/a&gt; and not the USB stack.&lt;/p&gt;
&lt;p&gt;Could you upload your project, or a simplified version of it, that reproduces the issue ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to fix stall pid on usb generic out report</title><link>https://devzone.nordicsemi.com/thread/165527?ContentTypeID=1</link><pubDate>Mon, 14 Jan 2019 15:01:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ae328b7-cdde-4c4f-9367-2e08ad3bb027</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;As you already mentioned, this is most likely the same issue as in the &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/40364/problems-with-out-reports-on-usb-hid"&gt;other thread&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We are currently looking into issue, and I will post an answer here with the fix when it&amp;rsquo;s ready.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to fix stall pid on usb generic out report</title><link>https://devzone.nordicsemi.com/thread/164594?ContentTypeID=1</link><pubDate>Tue, 08 Jan 2019 22:38:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0906a6bf-82fd-49bd-93ef-64cd5e8bbf5a</guid><dc:creator>HSh</dc:creator><description>&lt;p&gt;&lt;span&gt;Some&amp;nbsp;&lt;/span&gt;&lt;span&gt;m&lt;/span&gt;&lt;span&gt;ore information that may help: In&amp;nbsp;&lt;/span&gt;&lt;span&gt;endpoint_out_event_handler&amp;nbsp;&lt;/span&gt;&lt;span&gt;@&amp;nbsp;&lt;/span&gt;&lt;span&gt;app_usbd.hid.c, I&amp;nbsp;&lt;/span&gt;&lt;span&gt;first get&amp;nbsp;&lt;/span&gt;&lt;span&gt;p_event-&amp;gt;drv_evt.data.eptransfer.status =&amp;nbsp;&lt;/span&gt;&lt;span&gt;NRF_USBD_EP_WAITING, then&amp;nbsp;&lt;/span&gt;&lt;span&gt;p_event-&amp;gt;drv_evt.data.eptransfer.status&amp;nbsp;=&amp;nbsp;NRF_USBD_EP_OK, and then stall pid status. There should be something wrong with the memory allocation of out report.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>