Search Results
Search results 1-7 of 7.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi Nino, Quote from SEGGER - Nino: “This is exactly why Ozone was developed. So you only need to use the IDE for building. ” It would still be two programs to handle, an ide and ozone. Currently they are only using one. Quote from SEGGER - Nino: “This won't work. Quote from current SWOViewer section in J-Link manual: "Should you have a target connection already open e.g. a debug session in your IDE we recommend defining the parameters device name, CPU clock frequency and SWO clock frequency via …
-
Hi, we don't want to use two different programs for developing. Some developers can not even deal with one ide. Back to the problem: I tested it with the non CL versions of GDB Server and SWO Viewer. I launch the GDBServer with options Source Code (1 line) Then connected the SWOViewer and selected the device etc at the config window. I just found out that it seems to be a Race condition... The problem persisted with about 2 out of 10 attempts. Best regards, Kevin
-
Hi again, I installed the new version V6.40. The changes say: - JLinkSWOViewer: When SWOViewer waslaunched with CL options and another connection to the target device wasalready active e.g. debug session in IDE, SWOViewer would crash. Fixed. - JLinkSWOViewerCL: When SWOViewer waslaunched with CL options and another connection to the target device wasalready active e.g. debug session in IDE, SWOViewer would crash. Fixed. But the problem still exists. forum.segger.com/index.php/Att…540bb748b8c51ed…
-
Thanks a lot! I'm looking forward to the new version! Best regards, Kevin
-
Hello Nino, it's exactly the same error with the non CL version. Thanks a lot for investigating this further! If it would work again, that would be a big advantage! Regards Kevin
-
Hello Nino, that's exactly what I do and then there is this Internal Error and nothing works anymore. Regards Kevin
-
Dear Segger Support I updated my pretty old JLink Windows software to the new version V6.34h. Now I discovered a problem with opening the SWOViewer while connected to the target via GDB Server. Internal Error "NET_WriteRead(): USB communication not locked" forum.segger.com/index.php/Att…540bb748b8c51edb287f1d119 What am I doing wrong? Do you have any solution for that? Regards Kevin