<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/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/"><channel><title>Debugging USB on MCBSTM32E</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/38805/debugging-usb-on-mcbstm32e</link><description> 
I am trying to use the JTAG ulink debugger to catch issues in
communication in our USB driver on a MCBSTM32E board. The board is
powered off the USB and if I run my code without the JTAG attached I
can tell by my USB tester app that I have communication</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Debugging USB on MCBSTM32E</title><link>https://community.arm.com/thread/115728?ContentTypeID=1</link><pubDate>Fri, 07 May 2010 10:35:43 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:097f83e5-8414-4d1a-9d59-b0fe88fcdf40</guid><dc:creator>doubt that my ISP Al Bradford</dc:creator><description>&lt;p&gt;&lt;p&gt;
Mark one for the good guys!&lt;br /&gt;
I have never attempted to determine the cause and effect. High
current or timing, I don&amp;#39;t know. I just use the hub and continue with
my main problem of debugging my &amp;quot;perfect&amp;quot; code. I get a lot of
debugging practice!&lt;br /&gt;
Bradford&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Debugging USB on MCBSTM32E</title><link>https://community.arm.com/thread/102162?ContentTypeID=1</link><pubDate>Fri, 07 May 2010 10:15:16 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a94154d2-846c-45fb-aecc-592b1c6436bb</guid><dc:creator>Andrew Jones</dc:creator><description>&lt;p&gt;&lt;p&gt;
I got a powered USB hub and that has solved my problem, thank
you!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Debugging USB on MCBSTM32E</title><link>https://community.arm.com/thread/90405?ContentTypeID=1</link><pubDate>Thu, 06 May 2010 19:46:37 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:11f93eee-3dd7-4cf5-ad70-d9580318d988</guid><dc:creator>John Linq</dc:creator><description>&lt;p&gt;&lt;p&gt;
There are others more able to answer your post but let me provide
a link to you.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&lt;br /&gt;
&lt;a href="http://www.beyondlogic.org/usbnutshell/usb6.htm"&gt;www.beyondlogic.org/.../usb6.htm&lt;/a&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;These timeout periods are quite acceptable for even the slowest
of devices, but can be a restriction during debugging. 50mS doesn&amp;#39;t
provide for many debugging characters to be sent at 9600bps on an
asynchronous serial port or for a In Circuit Debugger/Emulator to
single step or to break execution to examine the internal Registers.
As a result, USB requires some different debugging methods to that of
other microcontroller projects.&lt;/i&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Debugging USB on MCBSTM32E</title><link>https://community.arm.com/thread/58146?ContentTypeID=1</link><pubDate>Thu, 06 May 2010 13:54:52 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:52627cee-e8dc-463d-a6b1-71f2b26172b1</guid><dc:creator>doubt that my ISP Al Bradford</dc:creator><description>&lt;p&gt;&lt;p&gt;
Andrew;&lt;br /&gt;
There are others more able to answer you post but let me ramble about
what I have frequently observed.&lt;br /&gt;
Running just about any USB target powered with the USB host and
debugging with the uLink has caused me a great number of problems.
Almost always, I have resolved this by inserting a self powered USB
hub between the host and the target.&lt;br /&gt;
Bradford&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>