Search Results

Hi Neculai, I assume the compiler is removing the variables? In that case try volatile. Does that work? Best regards, Nino

Hello Motron, Thank you for your inquiry. Currently we do not provide a plugin for uc/os. Quote from motron: “If not, is this something that Segger would be interested in doing? ” We could do it as contract work. In that case NREs would apply. Would that be of interest for you? Alternatively you can create the plugin yourself using Ozones plugin interface. For more information see Ozone manual chapters 6.3 and 7.10. For reference you can use one of the provided examples for e.g. embOS. Best rega…

Hi, quick update. The Ozone version with the fix has been released V3.20a: segger.com/downloads/jlink/#Ozone Could you give it a try? Best regards, Nino

Hello, Thank you for your inquiry. We are aware of this issue and it is just a display bug. So if you select the right device name everything should still be setup up correctly. This will be fixed in the next Ozone version. Best regards, Nino

Hello Soman, Thank you for your inquiry. This is already supported. Example projects can be found here: wiki.segger.com/STM32H7#Tracing_on_STM32H7_series Best regards, Nino

Hello Bob, Thank you for your inquiry. The Code and Data rows indicate how much memory does the source from this particular file use in data and code sections. The +/- values are always referenced to the last successful build you have done. I assume here that you switch between Debug and Release build where the release build is naturally smaller due to optimization and missing debug information. That is why the LockMsg.c uses less memory when build without debug info and optimization on. Keep in…

Hello Andrew, Thank you for your inquiry. Generally when moving from one target device to another we recommend setting a project up from scratch to avoid "forgetting" something when moving from one target to another. Anyhow the approach you chose should be working. In project settings you can pick if you want to set certain settings for private or public configurations. I assume your new public configuration also inherits its settings from the private Common configuration. So make sure this opti…

Hello Remco, Yes that would be the correct approach. You have to specify a section so the fill value takes effect. Great to hear that you are up and running again. This thread will be marked as solved now. Best regards, Nino

Hello, Thank you for your inquiry. We received your inquiry in parallel via our support system and will answer you there. This thread will be closed now to avoid lost information. Best regards, Nino

Hello, Thank you for your inquiry. This happens with tray icons if software under Windows is not terminated properly. If you quit JLinkGDBServerCL correctly the tray icon will also unload correctly. To remove "dead" icons simply mouse over them. Best regards, Nino

Hello Shrey, Thank you for clarifying. It appears not the file was the cause but under certain circumstances ES was not creating certain debug symbols that are needed for this feature to work as expected. This has been fixed in V4.52c as you correctly found out. We will consider this thread as solved now. Best regards, Nino

Hello, Plans yes, but due to low demand and the availability of an ETB/ETF in such setups which is supported by J-Link it is only on the wish list without a fixed timeschedule. Best regards, Nino

Hello, Thank you for your inquiry. Markers can't be displayed in the RunTime tab. But a new markers window is planned for future SystemView versions where such information will be displayed for the set markers. But we can't name a fixed timeschedule at the moment. Best regards, Nino

Hello, Thank you for your inquiry. Did you follow the following instructions when instrumenting your NoOS application? wiki.segger.com/Use_SystemView_without_RTOS Best regards, Nino

Hello, Thank you for your inquiry. The awareness scripts shipped with Embedded Studio in the /samples folder have not changed since the 4.42 (since the files are shipped with ES) and also Embedded Studios behaviour has not changed ever since. Could you clarify where you sourced the file from before? Best regards, Nino

Hello, Thank you for your inquiry. The error message is due to an incorrect device name.The correct one is MIMXRT685S_M33. This was changed from the beta to the release version on request of NXP which was unfortunately not updated in our Wiki example. We have updated the Wiki accordingly. Could you give the example project another try? Best regards, Nino

Hello, Thank you for your inquiry. The ETR is not supported by J-Link. Best regards, Nino

Hello Li, Thank you for your inquiry. Yes the A53 architecture is supported on J-Link EDU V10 or later: segger.com/products/debug-prob…nk/models/model-overview/ However as the generic connect to A53 platforms rarely works you most likely need to do target specific initialization steps. You can do so using our JLinkScript interface. For more information see the J-Link user manual. We see that you are using a TRACE32 probe in your setup so we are not exactly sure how a J-Link EDU fits into that se…

Hello, Thank you for your inquiry. The PRU is not supported by J-Link natively. A list of supported devices can be found here: segger.com/downloads/supported-devices.php For the AM335x series only the Cortex-A8 core is supported. Best regards, Nino

Hello Remco, Thank you for your inquiry. The reason why one file is filled and one not is that hex files have 0xFF as default fill value. For the elf file this can be specified in project option Default Fill Pattern or you can use the fill attribute in the linker script. Best regards, Nino