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 Kevin, Thank you for your inquiry. The issue is that J-Link can only assume default memories to always be accessible. Memory reads on address ranges that are not available can cause damage on some target devices which is why we will only search ranges that we know are existing. But you can tell J-Link to search a specific range or set it to the RTT control block directly. How is described in the J-Link user manual in the RTT FAQ section or in the SystemView user manual. Best regards, Nino

  • Hello, Thank you for your inquiry. We do not recommend routing the trace signals to the 2.54 mm header. Trace signals are not specified by Arm for that type of header and most probes expect there to be ground. Some third party probes might break down if other signals are routed there so we can't recommend this approach. Here is the official pin out: segger.com/products/debug-prob…gy/interface-description/ For tracing we recommend using only the 1.27mm 19 pin header. To keep that compatible to th…

  • Hello, According to the manual this device has no ETB. Only pin trace via ETM seems to be supported. It will most likely not work out-of-the-box as the trace pins need to be initialized first e.g. using a JLinkScript file. How to do it is described here: wiki.segger.com/How_to_configu…t_files_to_enable_tracing We will add the M2351 to our trace wishlist and create an example project which will then be added to our tested devices site: segger.com/products/debug-prob…echnology/tested-devices/ I ex…

  • Hello, Thank you for the feedback. Glad to hear that everything is working as expected now. We try to improved Ozone wherever we can which is why we always recommend using our latest software if possible. Best regards, Nino

  • Hello, Thank you for your inquiry. Currently there is no option to export debug terminal output from ES to a file other than copy pasting it to a text file. We will add this to our feature wish list so it might be added to a future version of Embedded Studio. Best regards, NIno

  • Hello, The emSession file will be update once a solution/project is closed or Embedded Studio is closed. Best regards, Nino

  • Hello, Thank you for your inquiry. The Always Rebuild option does not have advanced conditional options. If it is set to yes it will always rebuild just as the name of the option indicates. We will add your proposal to our feature wish list and see if this could be added in future so the Always Rebuild option would get additional config options. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you elaborate what exactly you are trying to do? We do not provide any Keil tools as Keil is a different company. If you are looking to do some pre or post compile/build steps you can do so in Embedded Studio project settings where you can e.g. call external CL applications which will then be executed at the hook points that you have set in your project. Best regards, Nino

  • Hello, Thank you for your inquiry. The LPC55S69 unfortunately does not implement any ETB, so only ETM tracing via pins can be used. Quote from rabbitlennon: “I suppose there at least should be an ETM module available, because the ETM module is advertised in the product manual. ” It is available, however it is possible that the ROM table in incomplete or incorrect so J-Link can't detect the module. But you can set the base address manually via JLinkScript. See J-Link user manual for more informat…

  • Hello Denis, Great to hear that you are up and running again. As you correctly found out there is a big difference between selecting the generic k81 device name and the one allow setting the security bits. I assume that by using the latter some of the Flash lock bits have been set which lead to the follow up issues you have experienced. Make sure to use the enable security device selection only if you want to lock your target device indefinitely e.g. after production. We do not recommend using t…

  • Hello, Thank you for your inquiry. Long load times in Ozone usually result from complex nested symbol information in the elf file which can sometimes appear "suddenly" even if the code change was small, the compiler output hower has changed significantly. But of course we try to improve Ozone here gradually so even more complex and nested elf files can still be interpreted quickly as you are used to. Which Ozone version are you currently using? Could you try the latest one and see if the behavio…

  • Hello, Thank you for your inquiry. We received your inquiry via our support system as well. To make sure no data gets lost this thread will be closed now. Information for others who end up here: The issue seems to have been related to the host PC. It got resolved as follows: Resolved by entering netsh http add iplisten 0.0.0.0 Best regards, Nino

  • Hello, Thank you for providing the elf file. There seems to be a misconception on how the Elf.GetBaseAddr(); command works. We have addressed this in the next revision of the manual so it is more clear. Esentially GetBaseAddr will simply return the lowest address of your elf image. This can be the beginning of a vector table but can also be some kind of bootloader or other data. To get the value of the Reset_Handler PC you can use ELF.GetEntryPointPC instead. I hope this is more clear now. Best …

  • Hello, Thank you for your inquiry. To make sure we understand you correctly here, you are essentially looking for a way to inherit include paths that are set in e.g. a library project also to the executable project in the same solution. Is that correct so far? If yes then you can do this via solution settings instead of project settings. That way all projects within the solution will inherit the options set on solution level. Is this what you are looking for? Best regards, Nino

  • Hello, Thank you for your inquiry. To make sure we understand you correctly here, is everything working now? Best regards, Nino

  • Hello, Thank you for your inquiry. Everytime you close Embedded Studio for the last open project an .emSession file will be created which saves all current window positions etc. If you load the corresponding .emProject file next time in SES the settings from the .emSession file will be applied. Is that what you were looking for? Best regards, Nino

  • Hello Owain, There have been no changes to SES yet in this regard. If you use the Registers.xml from the CPU support package in SES as explained in the linked thread everything should be working as expected. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. What exactly does the error message say? Which version of Embedded Studio are you using? From the log we can not see any issues. Could you provide an example project for reproduction purposes? Best regards, Nino

  • Hello, You are welcome. We will consider this thread as solved now. Best regards, Nino

  • Hello, Thank you for providing the init script. The chunking of writes you see in GDB Server is done by the GDB client you are using. GDB Server will simply execute whatever the GDB Client sends him. Please understand that we have no influence over this so it would need to be fixed from GDB Client perspective. For reference you can try downloading your image with J-Link Commander instead using the loadfile command. This will download the image in larger chunks so the bottleneck is on the target …