Search Results

Hi Nino Ok, how should I submit the files? Is there a way without attaching it to this thread/forum? EDIT: I've created a ticket: Inquiry#60127403

With Ozone v3.10 (on Ubuntu 18.04) I have similar display issues like described in [SOLVED] Ozone: Corrupted code profile window see also attached screenshot. thx

Thanks Nino, that works!

I have the following situation: - a dedicated region in the linker script for configuration. Source Code (8 lines) - declared and initialized const variable in this region C Source Code (2 lines) - a function deleting and reprogramming the config region at runtime when stepping through the code, the memory view doesn't change when the device performs an erase on the associated flash sector, but it changes if I also delete another sector which doesn't contain such variables. For me it seems Ozone…

well it's not only because of the look and feel but also because AFAIK qt4 is not supported anymore by the qt company [1]. it's not good practice to distribute outdated and unsupported software... [1] blog.qt.io/blog/2014/11/27/qt-…xtended-for-another-year/

Quote from akohlsmith: “I use msys2 and arm-gcc to build my source code because the same build environment works on Windows, OSX and Linux. I'm using CFLAGS of -Og -g to build the firmware, and the same Makefile on Linux and OSX produces .elf binaries which Ozone can work with just fine. However when I build the source in Windows and load the .elf with Ozone, it cannot find any source files. All of the *functions* show up, but double-clicking on a function only jumps to the disassembly of the fu…

Sorry for chiming in butQuote from SEGGER - Nino: “Quote: “If I can invoke a program from the command line, there should be a --help option which gives me a full list, defaults, etc.. These options should not be easter eggs that your users must hunt for.” We disagree, all information can be found in our documentation. Adding a --help function will double the workload when updating the documentation for a feature that is rarely used.” here I heavily disagree! On the command line it's more than co…

when can we expect a qt5 version of your tools? qt4 is going away in most linux distros and with it also support for a qt4 theme which match the overall look and feel...

from the 64bit deb packagesSource Code (1 line) but libXRender1 does not exists (at least on ubuntu) and should be named libxrender1 thx ps: please stop bundling outdated qt libs...

for some (strange!) reasons, the ozone deb packages include a copy of some (outdated) qt libraries at version 4.8.6. until these libs get omitted in the packaging process and the dependency get fixed to depend on system libs, you have to remove them manually after installing the deb... Source Code (1 line)

Hi Niklas Thanks for your answer. Regards

ok, in the meantime the situation changed slightly: 1. now after I power up the target (reset line not connected), using JLinkExe I cannot connect to the target. 2. once I reset the target with the reset line, it connects. 3. now I can disconnect the reset line and everything seems to work. I can program and debug the target. Why is this initial reset necessary?

Hi I'm using NXP MKL02Z32. As I need all IOs, I also want to use the !RESET line a io. I have different pcb's with and without RESET line to the JLink. Using one without RESET I'm able to flash the application but debugging doesn't seem to work. On a different one, with RESET line, debugging works but after I disabled the RESET pin in the config flash, nothing works anymore (fashing nor debugging). Now my questions: 1. Is the MKL02 fully supported (flashing AND debugging) by the JLink without RE…