Search Results

Hi Fabian, thanks I will try that. Kind regards Andreas

Hello, is there a possibility to configure Ozone "never" to download the selected ELF file? I currently try to debugging a production device and want to avoid the downloading of the firmware accidentally. I just need to select "Attach to Running Target". But I know, there will be the time when I will just click "Download & Reset Target" accidentally. Kind regards Andreas

Hi Nino, thanks. I tried the new Version. Everything works fine. SWO is active after connection to target. Kind regards Andreas

Hi Nino, very nice. Thanks for support! Kind regards Andreas

Hi, I use STM32F469 as device. In the old versions of ozone (2.59) this has not been an Issue. The SWO was always active after connecting to the Target. Also nothing changed in initialization. Kind regards Andreas

Hello Nino, when I start Ozone, I normally load one of my pre-configured "jdebug" files. SWO is activated in these files. But when start Debugging, it connects to the Target and breaks at "main". Then I see that SWO cannot start. I've selected anything as "auto" and I use SWO only for printf now. Kind regards Andreas

Hello Nino, I noticed another problem: The activation of SWO fails at startup. I need to configure it manually. This is the Output I get: >> Disabled output of control characters >> SWO active >> failed to activate SWO data capture: SWO trace cannot be started: invalid core frequency >> SWO inactive Is it possible to activate SWO when breaking at main() ? Kind regards Andreas

Hello Nino, thanks for the very fast fix! I can verify that this problem is fixed. Tooltips are readable now. I noticed another problem: The activation of SWO fails at startup. I need to configure it manually. This is the Output I get: >> Disabled output of control characters >> SWO active >> failed to activate SWO data capture: SWO trace cannot be started: invalid core frequency >> SWO inactive Is it possible to activate SWO when breaking at main() ? Kind regards Andreas

Hi, ok thanks. Kind regards Andreas

Hi, I use the newest Ozone from today. If I move the mouse over my code I usually get a Tooltip with a black font. Now its a white font over a bright background, which is not visible anymore. I use Ubuntu Mate 16.04 LTS. I got several updates today. Do I need to install any package to get a black font? This sounds like a similar issue with GTK <-> KDE. Kind regards Andreas

Hello Nino, thanks for your help! I checked that and noticed that I mixed up RAM address with Flash addresses which start with 0x08XXXXXX. Of course RAM starts at 0x20000000. So no Zero at the beginning... Bad mistake! Kind regards Andreas

Hello Nino, thanks for your help. I've attached a Log File. As mentioned, I use a STM32F469 Dicovery Board with JLink Reflash FW. So I hope this is no limitation. Kind regards Andreas

Hi, I have setup a little Demo Project for our STM32F469 Disco Board. I use the JLink Firmware on the ST-Link Module on the Board. I use Keil as Debug IDE (Target Build runs over Make & GCC)... When I stop my target I want to read some Parts of the SRAM with the debugger. But that does not work. I don't get any content. When I do this with our actual Project I can read SRAM on Break. For our Project we use an JLink Pro connected over SWD. If I try to read a SRAM Region with the JLink Commander o…

Hi Nino, thanks. That feature would be very helpful to get some additional information out of my target. Kind regards Andreas

Hi Nino, thanks for reply. Will it support VCOM in future over a FW update or depends it on HW Version? Kind regards Andreas

Hello, I'm using a JTrace with the newest firmware and attached to a USB3.0 Hub. The JLink Configurator says I cannot use VCOM functionality with JTrace. The manual only relates on JLinks but says nothing about JTrace explicitly. Can I activated VCOM to get printfs from my Target over ITM? That would be very useful for me. Kind regards Andreas

Hello Niklas, thanks for your help. Problem solved. I set the BOOT0 Pint to 3.3V and the controller booted into Bootloader Mode. Then I was able to attach to it with the debugger and erase the flash. I adjusted the RCC Values for my custom board. Now Firmware is running. Kind regards Andreas

Hi, I use a STM32F469IG and ported the Eval Firmware to the new PCB with 2 CPUs. Firmware runs only a RealTimeOS (Sciopta) and some Modules. I deactivated IOs (unfortunattely not all). The main thing I forgot was the RCC Config. So CPU should run on 560MHz. HSE = 25MHz PLL_M = 8 PLL_N = 360 PLL_P = 2 -> 560MHz The Discovery Board runs with 8MHZ HSE which ends in 180MHz SystemClock. Now I cannot connect to it anymore. The JTAG Scan shows the ARM CoreSight JTAG Debug Port and the Boundary Scan Por…