[SOLVED] [J-Trace] What is the maximum timeline instruction buffer? This conversation happened in 2020. SEGGER team stated that currently instruction buffer is 64 Mb no matter what is set by the user, and this will be fixed in the near future. Now it is almost three years old, but the limitation is still present. I still see no more than 800 ms of trace in Ozone. Is there any ETA on fixing that?
This issue becomes ever more severe as you switch from USB connection to TCP connection. JFlash and Ozone now cannot work simultaneously (at least with J-Trace native ethernet port), so each reflash puts significantly more burden on you: disconnect Ozone, connect JFlash, erase chip, disconnect JFlash, connect Ozone back. Also, with TCP it now fails in a totally deterministic way. Every Ozone flashing attempt now fails with timeout or corrupts flash data.
After switching from STM32F4 to STM32G4 chip I started to encounter weird UsageFault exceptions related to corrupted flash memory. This happens when code is reloaded, apparently Ozone fails to correctly reprogram the chip. Erasing chip with JFlash and restarting debug session (so code will be uploaded again) fixes the issue for some time. JFlash also confirms that flashed code does not match actual binary. This issue didn't occur on F4 devices. I would be happy to provide more data to investigat…