Search Results

Hi Alex, sorry, i had a brain block. When you mentioned a bootloader i only thought of a custom one, not of a builtin ROM-Bootloader. Of course you were right. In the knowledge base article you linked the "secret" is mentioned at the very bottom. For reference, if anybody will stumble about this in the future, i will repeat the important sentence here: Simply leave the functions AfterTargetDownload() and AfterTargetReset() empty (but not commented out!). This did the trick for me. Why the Ozone …

Hi Alex Thanks for the reply. No, there is no bootloader involved. As i wrote at the beginning of my first post, i stripped the problem down to the Blinky example delivered with SES. If the Ozone project is not set-up correctly, then how do i get a correct set-up? SES does not seem to produce a correct Ozone setup, as mentioned. Doing the set-up with the Ozone project wizard also does not produce a correct setup. As mentioned, there is currently no user specific code involved, it is all just the…

Short Story (Steps to reproduce): - Open blinky example for RP2040-Pico in Segger-Embedded-Studio. - Build the project - Click "Debug/Debug With Ozone (Alt F5)" - When Ozone opens, start debug session - Get a Hardfault at 0x00000000 (screenshot is attached) This is all done using standard Raspberry Pi Pico Dev-Board, no custom hardware is used yet. Long Story (Background): After many years of development with STM32 micros (using Eclipse and Ozone/J-Link as my toolchain), I need to start a projec…

Hello Nino, did you found the culprit? I just gave Ozone V3.24 a try and the .deb package installs just fine now on Kubuntu. So this seems to be solved. Thanks a lot! Best regards, Martin

Hello Nino, thanks for the confirmation. Let's hope, you will be able to find a simple fix.

Hello Nino, thanks for the quick response. The tarball works out of the box! I didn't do extensive tests, but Ozone does flashing, debugging, single stepping, etc. just fine. So I think we have a winner and I am up running, thanks for the help. Can I give you any other usefull information to investigate the issue? I thought that all ubuntu flavours are very much the same under the hood. Sadly the qApt Package Installer doesn't show which dependency causes the problem. Best regards, Martin

Hi All, in the past I often needed to use a Linux Laptop for Ozone/J-Link, mostly with Linux Mint. Ozone and J-Link always installed without problems. Due to other circumstances I now had to install a current Kubuntu (21.04) on a new Laptop. With this install a have problems installing Ozone. J-Link installed fine, but when I try to install Ozone from Ozone_Linux_V322e_x86_64.deb I get the following error message (also shown in the screenshot). Error: Cannot satisfy dependencies Does anyone has …

Ah yes, that works! Thanks a lot and best regards, Martin

Hi Nino, the problrm with the crash is solved meanwhile. But it is still not possible to connect to an existing session with the newest software. Can you recommend a version which is known is working? Best regards, Martin

Hello Nino, thanks for the confirmation. It's always good to know that the fault is not on my side Best regards, Martin

Hi All, as mentioned in the subject, I am experiencing problems with the latest version of RTT Viewer. When a debug session with Ozone V2.56t is open, then starting RTT Viewer V6.34b with the option "Existing Session" leads to an immediately exit of th RTT Viewer application after clicking connect. But when Ozone is not active and RTT Viewer is not using the option "Existing Session" (but "USB") then RTT Viewer does work. I think, that this is because of the update to V6.34, but i am not 100% su…

Hi Nino, thanks for the info. The enable feature would be great! Best regards, Martin

Hi Nino, thanks for the explanation. But to be honest, I don't get the reasoning. How could a user be confused by showing the colors, if they are specified? Best regards, Martin

AArgh, found it! I normally use the TAB 'All Terminals' in RTT-Viewer. Here the color does not change, but in the TAB 'Terminal 0' the color does change. Is this intentionally disabled for the TAB 'All Terminals'? Best regards, Martin

Hi All, i can't get the escape sequences in RTT-Viewer to work. I copied the following example from the manual into the source coe: SEGGER_RTT_WriteString(0, RTT_CTRL_RESET"Red: " \ RTT_CTRL_TEXT_BRIGHT_RED"This text is red. " \ RTT_CTRL_TEXT_BLACK"" \ RTT_CTRL_BG_BRIGHT_RED"This background is red. " \ RTT_CTRL_RESET"Normal text again." ); The text is shown in RTT-Viewer, but not in red but in standard white on black. It seems the escape sequences are just ignored. Am I anything doing wrong? Reg…

Hi Niklas, I found the issue. The J-LInk was connected via a "J-Link USB Isolator". After removing the isolator the update went fine. It seems, that the J-Link update process does not like the isolator. Is this a known limitation, that the isolator may not be connected during a firmware update? Best regards, Martin

Hi Niklas, I will try, but this will have to wait until tomorrow. I have an important presentation today, where I need the J-LInk working, so no time for experiments. Will be report back tomorrow. Best regards, Martin

Hi Niklas, no problem, speaking about the same things is important. The Log Window (which is shown during the update process) shows exactly the same as in my screenshot, when using the J-Link Commander. The J-Link commander window shows this: Source Code (9 lines) Best regards, Martin

Maybe the correct term is release date? I mean the info in columns "Host Firmware" and "Emulator Firmware": forum.segger.com/index.php/Attachment/1816/ Best regards, Martin

Hi Niklas, not sure what you mean, the string you showed can be seen in the screen shot. Current firmware is: 2017 Jul 10 15:44 New firmware is: 2017 Jul 24 17:06 Or do I miss something. Best regards, Martin