Search Results

Search results 1-17 of 17.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • The “Close All” entry of Context-Menu which comes up when you do an ”long-left-click” on the big X on the upper right corner (where you are closing opened files) of theSource-Code-Dock seems to do what you are searching for. Best Regards

  • I think Segger will only support their own JTAG-Interface. But the older sibling of SES supports CMSIS-DAP. Regards

  • Hello Nino, Tanks for the feedback. Unfortunately, there are still problems. When switching the ‘Wide Character Size’ Option to 16-bit. CLANG is creating an error while GCC is working. Do you have also a solution for this? Best Regards

  • Hello Segger Team, I’m getting some errors when using STL with the CLANG compiler, gcc is working fine. I’ve attached an example to demonstrate this errors. You can remove the first error by setting the compiler option -fno-signed-char but I think the project behavior should be same without setting extra options for each compiler. Could you take a look at this compiler errors? Best Regards

  • Sorry for the late response I was out of the office. Sadly, I don’t have any code or binary’s left from this scenario. Right now a colleague had a similar problem with a different controller (KV11). He had flashed a binary which was compiled for a different derivate (K02 I think). Ending up with a controller which had the same behavior as mine bevor. When I had brickt my board I was also switching between different Kinetis-controllers. Maybe I had done the same mistake. I had done this mistake a…

  • Hello Niklas, the FRDM-K22F board has a red LED which signals the state of the reset line. And it is flickering while the jlink is trying to connect. In addition you can hold the reset line manually high with pushing the SW1 Bumper. I have done so (with the OpenSDA Interface and in a second try with an external JLink) with the same negative result. -->The Reset line seems to work, but it doesn’t lead to any success. You are right; the controller seems to be in a state where the J-Link can’t acce…

  • Hey Niklas, now I’m getting the same error than in ozone. Regards Markus

  • Hello Niklas, Are you sure with the device-string? I’m getting an error with it (see the picture attached) Regards Markus

  • Hello Niklas, My second Board is also not working anymore. Same behavior, it stopped working after a debug session. The software to debug crashed at some point, and ended up with a board which does to respond to the debugger anymore. I had a similar behavior some time ago with TI Stellaris controller. TI had provided a tool to get the controller working again; with normal JTAG-Adapters you couldn’t gat any access. Regards Markus

  • Hello Niklas, I’m using Ozone in Version 2.42. I’m not sure which JLINK driver Version is used, as I have installed several versions in parallel. I have uninstalled all Versions except the newest available (6.16f). But I have still the same error. What I have to mention, the debug connection has worked once, and after this, I’m not able to start the debugger again. Maybe I have brickted my Board by debugging it. I’m not familiar with the J-Link Commmander, but it looks like it is also not workin…

  • Hello, I have a problem with my FRDM-K22F Evaluation board. When I’m trying to debug with Ozone I get always this Messages J-Link: Executing InitTarget() J-Link: Connect Under Reset J-Link: Connect Under Reset J-Link: Executing InitTarget() J-Link: Connect Under Reset J-Link: Connect Under Reset J-Link: InitTarget(): PCode returned with error code -1 This interface is not supported by the connected emulator. Selection will be ignored by the DLL. Connection failed It doesn’t matter if I’m using t…

  • Hello Niklas, Thanks for the scripts. With this extension it is working with my board. It is setting the alternative Pin configuration for the trace pins, but still keeps the original one:…d7088c4d9e4d5c11d36f66f86 I already tried to deactivate the old pins by extending your code: Source Code (18 lines) Which is not working, also resetting it in the Register-View of Ozone is not working, as the debugger is activating the original configuration immediately. Regards …

  • Hello Niklas, I took a closer look to the Registers of the K80 Board. It looks like the debugger initialized the GPIO-pins incorrect. It initializes the Pins PTA6 – PTA9 as trace Pins, but on this board PTA12 – PTA16 is used for trace. I didn’t found a way to configure the pins in ozone, so I tried to configure it in my program. Sadly that didn’t work. Any Idea how to configure the pins? Regards Markus

  • Hello Niklas, Looks like, but my controller-IC is soldered and not in a socket:…ystem-module:TWR-K80F150M Regards Markus

  • Hello Niklas, the silicon on the K60-Board is really rather old. But, I could organize a TWR-K80 Board and tried the trace. On this board it is not working at all, regardless if the clock is set or not. “Normal” debugging is working. PK80 FN256VDC15 0N03P CTVDCDA Also a buggy silicon or Board? Regards Markus

  • Hello, Thanks for the fast Reply. The Label of the MCU is: PK60N512VMD100 0M33Z CTDZM1047B But this is not the final Hardware we want to use. I just wanted to get the trace running and see how it works. The final hardware will be a K66-based, but our hardware-development is still not finished. That’s why I’ve started with this board. Regards Markus

  • Hello Segger Team, I would like to trace my program. For this I’m using Ozone with a j-Trace Debugger (SW Version 610b) and a TWR-K60 Eval Board. While connecting to the Board I get a License Missing Error Message: “The connected J-Link does not have a valid license for the use of Ozone – The J-Link Debugger. J-Link PLUS, UTRA+ and PRO models come with a build in license for Ozone – The J-Link Debugger. …” Is the License not included in a j-Trace? You write on the Ozone-Product Page: “Ozone can …