Search Results

Hello Fabian I did a few updates and it didn't hang/freeze, so yes, I can confirm that the issue is gone/fixed. Thanks for the continuous improvements!

Thanks, that's Awesome! Yes, I think I'm aware of the limitations and the async nature. To me, it looks like RTT TRIM + retry is similar to NO_SKIP_BLOCK, if the retry happens right after the write (if there's another queue, the retry could happen later, but then, a larger RTT buffer could be used ). Best regards Matthias

Hi, thanks for looking into this. Status: I've tried this morning with the latest version and realized that Ozone does not hang forever, however, it takes 45 seconds until it becomes responsive again. So, no full hang, but it's faster to restart it in this situation I've used the LAUNCHXL-CC26X2R1 Launchpad ti.com/tool/LAUNCHXL-CC26X2R1 but would assume that others will show the behaviour as well. Here are my steps: Install Code Composer Studio for Mac from ti.com/tool/download/CCSTUDIO (Use ful…

Hi! We're using RTT to write out a binary packet log file (e.g. like .pcap). To avoid using a special outgoing packet buffer and extra memcpy calls, we first write the packet header and then the packet itself with SEGGER_RTT_Write. If the RTT buffer gets full after writing the header and the RTT mode is set to SEGGER_RTT_MODE_NO_BLOCK_SKIP, the packet can not get written and the log gets corrupted. Would it be possible to add a SEGGER_RTT_GetAvailWriteSpace(bufferIndex) or SEGGER_RTT_CanWriteByt…

Hi. I'd like to report similar behaviour in a different setup: TI Code Composer Studio (latest version) is used to compile for their LAUNCHXL-CC26x2R1 (Cortex M4 CC2562R1 controller) together with Ozone (2.70) and a J-Link Plus to flash and debug it on macOS X 10.14.6. Using e.g. their BLE Multi-Role example, I compile on CCS, wait until it's done, then switch to Ozone. Prior to switching back, debugging was stopped. When switching back, Ozone asks if it should reload the .elf file. After clicki…

Hi Nino. Thanks for getting back. I'd like to use RTT only for the main app on the CM4. The CM0 runs the closed source radio controller software (BLE/802.15.4/Thread) from STM. I did not see any changes to the RTT Control Block when it stopped. I've tried to move the RTT CB to non-shared memory, but on the first look, all SRAM is accessible by both MCUs. When I've tried to move the RTT CB, the CM0 didn't startup at all and RTT worked correct. I'll need to figure what's caused that (I did update …

Hi Nino. Thanks for the reply - I'm sorry I didn't have notifications configured and didn't see your reply in time (but fixed that just now!) I have a straight-forward/naive setup: start ozone, use project wizard to pick the stm32wb55xx (only two choices, with/without optional byte) and load the .elf for the CM4. I did not do anything about the CM0 and it has a pre-build binary from STM that implements the Wifi firmware. So, I assume I have a single session on the CM4 and the CM0 is left alone. …

Hi. The STM32WB55 consists of a Cortex M4F main core and a M0+ Wireless processor using shared memory for communications between them. Are there any considerations/known issues using RTT on this controller? When using RTT with the M4F, RTT works as expected at the beginning. After starting up the M0+ co-coprocessor, RTT stops when using it with the current Ozone version on Mac. I've configured it to block if the buffer gets full. When I pause in Ozone, I can single-step through the _WriteBlockin…

Hi! Is it possible to configure Ozone's Terminal to send each character without waiting for a newline? I have some example programs that have a little text-based UI and a single character triggers something. Quick idea: instead of entering a line in the input field of the terminal, could text input while the main terminal (not the input field) is selected trigger immediate RTT sends? By this, there wouldn't be a need for an additional preferences/context menu option. Thanks! Matthias

I've got a Toshiba BMSKTOPASM369BT551 dev kit with an TMPM369FDXBG ARM Cortex M3 MCU + a JLink Lite. Before, I've managed to compile a simple blink app and even debug it in Ozone (I also have J-Link Plus) Now, and I'm not aware of any changes to my hardware, I get the error below. What does it mean? What might be broken and or anything I can try to fix it? Thanks! Matthias Debug.Start(); J-Link: Device "TMPM369FDXBG" selected. J-Link: Found SW-DP with ID 0x2BA01477 J-Link: Scanning AP map to fin…