Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

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

  • Hi, we received your request in parallel via our support system. To make sure that no data is lost between the different channels this thread will be closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. Please note that this is not a support forum. If you are in active support period we recommend to use our official support channel. I also noticed that you have a support case already open regarding this. Please do not open the same inquiries via multiple contact channels as this can lead to lost/wrong information between channels which in result leads to more work on our end which is not beneficial for your inquiry. We will close this thread now to avoid dupli…

  • Hello, I feel that there is a misunderstanding here. Ozone already has that feature (ignore all the command line stuff and scripts). You can already save in your Ozone .jdebug file which J-Link to use based on the serial number. It is simply that for some reason you can't get that to work. Correct? Could you try the following? 1. Open your Ozone project in Ozone. 2. Go to Tools->J-Link Settings, this should yield picture A below. 3. Select the three dots for the host interface settings (red circ…

  • Hello, Quote from awneil: “but it doesn't do that. ” Ok that is odd. Works flawlessly for me for years. Could you provide a short clip on how you try to do this? Quote from awneil: “It's a workaround. I still think it would be nicer to have it in the per-user setup file ” It is more than a workaround. It provides a simple solution to exactly the setup prerequisites that you described. Where is the difference to have a Ozone launch script e.g. in Python where you call in one line Ozone with the C…

  • Hello, Thank you for your inquiry. Yes that would be one correct approach. You can of course also use a JLinkScript and SetupTarget(). Ozone generally offers all needed target manipulation actions like read, write, reset etc. See the Ozone manual for more information. For completeness. Exec.Command is only meant to be used for J-Link Command strings: wiki.segger.com/J-Link_Command_Strings Best regards, Nino

  • Hello, Thank you for your inquiry. The prompt should only appear if more that 1 J-Link are detected to be connected to the host PC. Is this a common occurrence with you and your colleagues? Quote from awneil: “but the serial number is not added to the .jdebug project file, and there's nothing in the .jdebug.user either. ” Yes, because you need to select the J-Link you want. Right now it defaults to USB which will open the prompt if more than 1 are connected or chose the single J-Link. Press the …

  • Hello, Thank you for your inquiry. The error message indicates that the elf file you are loading does not conform the elf file standard: en.wikipedia.org/wiki/Executab…nkable_Format#File_header As you can see they call a section in the header "magic number". From the screenshot you provided it seems that you set your JLinkScript as the elf file (your actual target application). We can see that in the console log with File.Open() Ozone tries to load the JLinkScript file as an elf file and obvious…

  • Hello Bogdan, Thank you for your inquiry. We have the following option for that: Options -> Environment -> User Interface -> Show Large Icons in Toolbar Does that work for you? Best regards, Nino

  • Hello, Thank you for your feedback. I will pass this on to our team. But we can't promise if such change will be implemented or not. Best regards, Nino

  • Hello, yes that is normal. The instruction trace window will only show the last ~64 MB of raw trace data received. Depending on your target device that is typically somewhere between 50-100 million instructions. Default options in Ozone is to display 10M instructions. You can increase that value in the trace settings options. What is unlimited is the code coverage and code profile which is done in the live analysis. Currently if you want to dump all instruction trace data you need to do the trac…

  • There is no data trace support available in our tools or software. You can of course extract the ETB data manually and write your own analyzer but this is outside of our support scope. For this the trace data can be dumped into a trace file: wiki.segger.com/J-Link_Command_Strings#TraceFile But for data trace you would have to overwrite our default trace init of the Arm Coresight componetns (ETM, TPIU, etc.) with a JlinkScript: wiki.segger.com/J-Link_script_files Please understand that we can't p…

  • Hello Prashanth, data trace via the trace pins is not supported by either J-Trace Pro nor Ozone. Currently there are no plans to add support for this for the existing trace probes. Best regards, Nino

  • Hello, Quote from prashanth.prakash: “So how can we enable data tracing on Ozone then? ” It is not supported. Data tracing is only supported by a hand full of Cortex-A and -R devices and would require a 16 bit trace interface to avoid overflows. As our customers typically do not want to waste so many pins for just debugging we do not provide a trace probe for such interface and feature. Quote from prashanth.prakash: “Is 5 pin trace only used for instruction and cycle accurate traces? ” Correct. …

  • Hello, Thank you for sharing your setup. Great to hear that the Pico SDK is now working with your ES Setup as expected. To keep this information available for other users as well we will now close and archive this thread. Happy debugging! Best regards, Nino

  • Hello Prashanth, Thank you for your inquiry. Please note that the data trace that you refer here to is independent from the 5 pin trace that you use for instruction tracing. Instead it uses the debug interface and HSS. segger.com/products/debug-prob…#data-acquisition-via-hss Just for awareness. How do you detect the 500 Hz sampling frequency? From the screenshots it is not apparent. If you refer to unexpected timeline values, make sure that under trace settings the correct CPU clock speed is set…

  • Hi Sid, Thank you for your inquiry. The generic approach that would work for any SystemView instrumentation is to encapsulate all SystemView calls with e.g. #if DEBUG or similar. In the case of FreeRTOS it is sufficient to make the include of the SEGGER_SYSVIEW_FreeRTOS.h conditional in the FreeRTOSConfig.h file though. Best regards, Nino

  • Hi, I see that you contacted our support in parallel. So you were indeed using the J-Link SDK. As the issue has been resolved this thread will be closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. Which SDK/DLL are you referring to exactly? Do you mean the J-Link SDK? Please understand that public mention of any DLL functions is a license violation. If you have issues with the J-Link SDK please get in contact with our support team as explained in my signature. If you mean something else, could you elaborate what exactly are you trying to do? Right now I do not see how this relates to our IDE Embedded Studio, which this subforum is for. Best regards, Nino

  • Hello Peter, Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino

  • Hello, You can call CMAKE and other tools via command line in ES projects options under "User Build Step". However please understand that we can't provide support on how to as the Pico SDK is not our product. So we recommend to consult the Pico SDK documentation and/or Raspberry support. Best regards, Nino