Search Results

Search results 1-20 of 28.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Thanks! I'm using an intel MacBook, and also an intel iMac.

  • I'm using macOS Big Sur (11.2.3). And it happens also on my macbook, same OS. I tried adding a stub symbol for main() but it still crashes. Also that error might just show up for you because the default Ozone settings are to break at the symbol "main". In this project we break at Reset_Handler, but that shouldn't matter (shouldn't cause Ozone to freeze). Also, if I set up the Ozone project with a J-link log file (using the New Project Wizard), and then open the .elf file, all that's in the log f…

  • That's odd you see a compressed video, the video is crisp when I play it on youtube, and youtube says the resolution is quite high (2160p60). Perhaps you need to manually select the resolution (click on the gear icon on the youtube video, and select a better resolution)? The issue is that when using Go To address, the cursor will only stay there when the debug session is halted (when the "power" icon in the toolbar is green), or if the program is running (power icon is red with a "pause" icon ne…

  • Another v3.22 bug report: Here is an example of an elf file that causes v3.22 to hang, and eventually crash. dropbox.com/s/jj11xzusd4iz56q/main.elf?dl=0 To reproduce: 1. Start Ozone, any version from v3.22 to v3.22e. 2. Open a project, or start a new one, it doesn't matter. Doesn't matter if a J-Link or J-Trace is attached or not. 3. Select "File > Open" 4. Choose this elf file. 5. The cursor will turn to a spinning beach-ball and Ozone will hang for a very long time (forever?) The .elf file is …

  • When Ozone v3.22e is attached to a running program, and the program is paused, the Go To... menu item in the Disassembly window will not work properly. The address you enter in the dialog box will be shown momentarily but then the Disassembly window will jump back to the PC (current instruction). When I say "paused" I mean that you are able to step through code. This doesn't happen if the program is running and not paused with the debugger attached, or if it's stopped (not running). In those cas…

  • I'd also like to add, that it's not just the Disassembly window, I've also found the Watched Data, Local Data, and seemingly most (all?) the windows causes a crash when moved from one docked pane to another docked position. The window often temporarily turns into a floating window while you drag it (this is normal), but then it crashes once it stops being a floating window. To reproduce is easy: -Launch Ozone v3.22e -Close the "open project" dialog box, or open a project, it doesn't matter. -Dra…

  • Any news about this? v3.22e changelog says nothing about fixes for menu display, or slow menu response. Are there plans to fix it? The slow menu response at least would be great. We can live with cutoff text in the menus I suppose. thanks Dan

  • Hi, more bugs in Ozone v3.2x... On macOS Big Sur, Ozone v3.22e. First, get a fresh install of Ozone v3.22e: -Delete `~/Library/Preferences/com.segger.Ozone.plist` file if it exists -Install with the .pkg installer --Or copy files from downloaded .dmg file to /Applications folder (it doesn't matter) Now, launch Ozone: -Open Ozone v3.22e -The New Project Wizard will open automatically (or click it "Create New Project", or open an existing project, or use an empty project; it doesn't matter) -For p…

  • Hi Nino, Unfortunately the issue remains the same with Ozone v3.22e. Both issues: #1) Context menus are very slow to respond to mouse movements #2) Menu item text is cut-off whenever an menu item does not have an icon With regards to this issue, I notice no difference at all between v3.22b and v3.22e. I also tried changing the Application Font to see if that would fix it (thank you for fixing that!). However it doesn't seem to change anything. Attached are more screen shots from v3.22e. The slow…

  • Thank you, I subscribed to the notifications and will respond when I can test the new version. thanks Dan

  • Quote from rflmota: “Just going to open a similar thread (I checked yesterday but there wasn't anything related on the forum), I'm facing the exact same issues as @danngreen. I've also tried v3.10j as @danngreen suggested, but I still face the same slow response on context menu behaviours. ” Are you also using macOS Big Sur 11.2.2?

  • Hi, a few more issues with Ozone in macOS Big Sur. I'm using an 8-core i7 iMac 2019, with 40GB RAM and I've tested this with no other applications running except Ozone. I've also have the same issue on a 8-core i9 Macbook Pro, which is also on macOS BigSur. 1) When moving the mouse over a context menu (the pop-up menu that displays when you right-click somewhere), the highlighting of the menu items (based on where the cursor is), has a very slow response to mouse motions. Please see the attached…

  • Thank you, I look forward to the next release. There's another font-related bug, I will post in a different thread so this one can be marked as SOLVED.

  • I'm using macOS Big Sur 11.2.2, which is the latest release from Apple. I tried it with a DMG install, and also with the PKG install, and both have the same bug. What version macOS are you able to verify it is working? And what installation method is working for you? I also tried it on another computer (also macOS 11.2.2, as we keep all our computers at the office up to date). I get the same results, same bug exists. Ozone v3.22a does not have this bug.

  • Hi, on MacOS, Ozone v3.22b, the font cannot be changed using the Preferences window. Attempting to change the font by clicking the "..." button will bring up the system font picker. But not matter what font is selected, Ozone will issue the same command which can be seen in the Console: Edit.Font (FONT_SRC_CODE, "Helvetica, 11pt, Regular"); This happens for any font (Source Code, Application, Execution counters, Line Numbers, etc..): Edit.Font (FONT_SRC_CODE, "Helvetica, 11pt, Regular"); Edit.Fo…

  • Are there any updates to addressing this issue? [ABANDONED] Bug: Ozone Watched Data Window ignores mouse events in right-side 480 pixels I see the thread was marked "Abandoned" and locked, but I never received a reply to my last post. I have tested in the latest Ozone v2.56w, and the problem is the same. The right side of the Watched Data window does not respond to mouse events (clicks or drags). It doesn't matter where the Watched Data window is placed or docked, and it always effects a region …

  • Hmm, no that doesn't change anything. I removed the com.segger.* files in $HOME/Library/Preferences/ and then removed /Applications/SEGGER/Ozone, exactly as described in the User Guide. I then installed version 2.56r, and have the same behavior. I tried installing on a different disk (different /Applications/ directory) just to be sure, but it still gives me the same 480pixel blackout area.

  • I am using macOS 10.13.4 on an iMac (Retina 5K, 27-inch, Late 2015). The bug has been present for many macOS versions. We tested on a Macbook Pro 2015, and the bug was not present, like you found. On the iMac, the behavior happens at all times. There does not need to even be a programmer attached. Any time the Watched Data window is visible, it does not respond to any mouse events in the right 480px of the window. If I start Ozone and select "New > Project" it still happens. The bug is not prese…

  • Thanks, version 2.56p seems to have corrected it! Dan