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.

  • Hello, I just gave your sample snippet a try and it is working for me. Could you give the attached Ozone project a try? Simply use it from the same folder as the example project. Does this work for you? Quote from rals: “Using Break.SetCmdOnAddr() in combination with Elf.GetEntryPointPC() seemed more general than using Break.SetCommand() since line numbers can change and we would like to avoid changing the project file too often. ” I see, makes sense, thank you for clarifying. Quote from rals: “…

  • Hi, OK. We will put this on hold now and see if we can fix the other issue first. Best regards, Nino

  • Hello, Quote from Masmiseim: “Bye the way, Comments in XML-Files are not colored properly. I would expect that the angle bracket which enframe comments are also colored like the rest of the comment. ” We will add this to the improvements list. Best regards, Nino

  • Hello, Quote from miao.mingming: “I have the same question. If the SVD file can be used in Embedded Studio, more old chip projects move to the IDE will be possiable. ” This appears to be a different question. This thread is about importing a svd file to the memory map. Using a svd file to access registers you can do that with Embedded Studio. Simply set the svd file in project options under "Register Definition File". Best regards, Nino

  • Hello, What do you mean with step 2? Should step 3 not be the first one? Whenever I try to connect to the target or enter the debug session and the target is not powered on or not connected I simply get a "Could not connect error" and end up back at the ES mainscreen. Could you provide more detailed reproduction steps? What target device are you debugging? Best regards, Nino

  • Hello, Thank you for your inquiry. See here for a similar problem: SystemView hanging (blocked call) when recording events outside of RTOS tasks. Essentially FreeRTOS did not stay backwards compatible to V10.0.0 so all versions after that required additional instrumentation steps. Some versions are already covered by our community in our forum, but I do not think I have seen someone posting his V10.4.3 config yet. As mentioned in the other thread. Long term we will try to provide as many patch f…

  • Hello Jason, Thank you for your inquiry. From the problem description it sounds like the instrumentation in FreeRTOS is not correct/complete. Please note that the patch file provided with SystemView is only compatible to FreeRTOS V10.0.0. All versions after that require additional changes as Amazon/FreeRTOS chose not to stay backwards compatible to the V10 major release. Even V10.0.1 already needed additional instrumentation. You can find some of the "fixed" FreeRTOS files in this community foru…

  • Hello, Thank you for your update. Good to hear that you are up and running again. Generally we recommend to work with the Embedded Studio project defaults where possible to avoid such accidental path issues. We will consider this thread as solved now. Best regards, Nino

  • Hello, Thank you for providing the example project. Quote from Masmiseim: “Open the File fsl_flexcan.h and scroll to line 675 to find an example for the ampersand issue. ” Yes its reproducible and will be improved. Quote from Masmiseim: “Open the file main.c and select a space character, for example the one after the keyword ‘for‘. You should see the behaviour from my screenshot. ” Again reproducible. Will be improved. Quote from Masmiseim: “The detection of invalid code is not working correctly…

  • Hello Rune, I just gave the Wiki example another try and it works out of the box for me. Does the original Wiki example work for you as well? You seem to have modified it afterwards. Is there even application code at address 0x08008260 where a breakpoint could be set? Is there a particular reason you are use the address directly and not the file or symbol information from the current application? Best regards, Nino

  • Hello, We will discuss internally and see where the export GUI can be improved so it works more intuitively. Best regards, Nino

  • Hello, Can you confirm that you are seeing the same as here? Restored window size is lost under some circumstances If yes, we can reproduce it and see if Qt can be forced to play along. Best regards, Nino

  • Hello, Thank you for your inquiry. Quote from vtol-ronit: “Can someone please tell me what is the meaning of that reason value and where I can find that list to know more about that different reason value? ” This depends on the RTOS you are using and how the SystemView instrumentation is applied. See the SystemView user manual for more information. Section 6.1.1.4 Task Stop Ready should explain where the value comes from. Best regards, Nino

  • Hello, Thank you for your inquiry. We are aware of this issue and it will be fixed in the next release. It is only a display issue and has no impact on your target application. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide an example project for reproduction? What target device are you debugging exactly? Is it on an eval board or custom hardware? Best regards, Nino

  • Hello, Thank you for your inquiry. Quote from epac-tom: “I am able to see the warnings if I switch the Output window to Source Navigator, set to Tasks, and scroll through the list, expand the given source file and scroll down to find the warning - is this the only option that lists these out and can be used to navigate to the offending code? ” You can also swap between them with F4 on your keyboard. Quote from epac-tom: “How/where can I find out about the 14 infos? ” In the tasks view if you exp…

  • Hello, Thank you for your inquiry. You can simply call it as documented within the root tags of your memory map. There is one typo though in the documentation, should be /> at the end. Could you elaborate how you plan to use this and what your benefit you expect from it? It is a legacy option kept for compatibility but should not be used in new setups if possible. Best regards, Nino

  • Hello David, The whole argument is a string. So you need to put the "" around the complete argument. Best regards, Nino

  • Hello, Thank you for your inquiry. 1: Was not reproducible for me. Could you give the latest Embedded Studio a try? Do you still see this behaviour? If yes, could you post a code/comment snippet in the forum as a reproducer? 2: Is reproducible and will be improved. 3: Is not reproducible for me. Could you provide an examplefile with reproduction steps? 4: Is reproducible and will be improved. Best regards, Nino

  • Hello, OK makes sense. Will be added to the feature wishlist. Best regards, Nino