Search Results

Hello, We found some reset timing related issue (about NRST pin toggling) when programming RT1051 with Flasher Portable PLUS: - "Project settings -> Production": checked "Erase", "Program" and "Verify - Also checked "Start application -> via reset pin" and "Disconnect afterwards" - Press PROG to program the part So I tried to customize the reset pin toggling sequence with "Project settings -> MCU -> Exit steps" to put in: - "delay" command - "Reset" command with "Type 2" (i.e. toggle reset pin f…

Hello,I received a newsletter about V3 beta with: - SystemView V3 comes with a redesigned GUI, which provides more flexibility and new windows. - SystemView V3 improves the performance and resource use... I followed the link but I don't see any linux release. Will there be a linux (debian) version anytime soon? Alfred

@hrb You could be my hero because I have experienced something similar but I couldn't share my elf file. See my thread here [Ozone] Host memory usage jumped since V2.54.

Sorry I should have a bit more clear in my last reply. I left the Ozone beta running for more than 15 minutes and I called it stalled. About CPU usage, it shows 25% because it is only hoarding one of the CPU core (my XPS has a quad core Intel CPU). One more data point is I have the FreeRTOS plug in enabled, i.e. "Project.SetOSPlugin("freeRTOSPlugin");" in the .jdebug file.

I have just gave v2.55 beta a try. I see Ozone stalled and hoard 100% of one of the CPU cores while consume 2.6GB of ram. Here is the link for the screenshot.

Sorry I won't be able to share the ELF. FYI our target is a Cortex-M7 running ~1MByte of (mostly) C++ code with FreeRTOS, compiled with the arm-none-eabi toochain. Am I really the only one noticing this memory usage jump?

I have seen a steady increase of host memory usage with Ozone and it becomes unusable with the latest V2.54b. My environment is Ubuntu 16.04.3 LTS 64-bit running on Dell XPS 13 with 8GB of ram. This is the memory usage as reported by Ubuntu's System Monitor (with same ELF loaded and the same Ozone configurations): - V2.52d 3GB - V2.54 3.5GB - V2.54a 4GB - V2.54b 4.3GB

This also happens on my Ubuntu 16.04.3 LTS (64-bit) setup with Ozone v2.46.

Quote from rols: “Quote from dweber: “ Is there someone who got SystemView running on FreeRTOS 9.0.0 yet? ” Yes - see my post above yours, I did it the day FreeRTOS 9.0.0 came out and it was not that hard. So go back to the V8 diffs and look at them again and have another go.” To those who are still looking for a quick solution, FYI there is a more recent post with working patch on 9.0.0.

Quote from maximevince: “I have attached a .patch file with the required changes for the GCC/ARM_CM0 and GCC/ARM_CM4F port for FreeRTOS 9.0.0. forum.segger.com/index.php/Att…dccd0f32038198fd9f6ef9f80 BR, Maxime” I manually applied the patch and I can confirm it worked. My setup is Cortex-M7 with FreeRTOS 9.0.0. Segger should just take this patch and include it in the bundle. Thanks for the providing patch! :thumbsup: