OpenCores

OpenCores

部分翻译

Target Debug slow

First

Prev

2/2

no use

no use

RE: Target Debug slow by julius on Aug 29, 2010			julius Posts: 336 Joined: Jul 1, 2008 Last seen: May 22, 2012
[q]I should point out that removing the sleep(1) has 1 glaring drawback. 100% CPU use of one of the cores on your processor. [/q] Yes that needs to be fixed up. Perhaps 1 second non-blocking polling of the RSP socket when the target is running (to check for the interrupt, CTRL+C, packet) and then blocking polling on the RSP socket when stopped. I should point out that removing the sleep(1) has 1 glaring drawback. 100% CPU use of one of the cores on your processor. Yes that needs to be fixed up. Perhaps 1 second non-blocking polling of the RSP socket when the target is running (to check for the interrupt, CTRL+C, packet) and then blocking polling on the RSP socket when stopped.

RE: Target Debug slow by jeremybennett on Aug 29, 2010			jeremybennett Posts: 718 Joined: May 29, 2008 Last seen: May 22, 2012
<p> Can't you make it event driven if that is the behaviour you want? </p> <p> Jeremy </p> Can't you make it event driven if that is the behaviour you want? Jeremy

First

Prev

2/2

no use

no use

© copyright 1999-2012 OpenCores.org, equivalent to ORSoC AB, all rights reserved. OpenCores®, registered trademark.