Search Results

Hello, I have to modify my question: Actually the problem of losing log messages in RTTViewer does not only occur in the case of a reset Also in cases where bursts of log statements are printed, lines get skipped/lost in the RTTViewer output. Please advice which settings regarding RTTViewer I should tweak in order to not loose any log statements. Thanks and best regards

Hello Alex, thanks for your quick reply! You mean just adding some kind of delay before issuing an self-reset? Or is there a way to detect in sw whether J-Link is done with emptying the ring buffer? During development we often trigger a reset manually vi a hw button on the test jig. What could be done in this use case to avoid skipped lines in the RTTViewer output? Best regards Paul

Hello everybody, in our development project we have the problem, that whenever we restart our MCU using reset, some lines of the RTT logging are skipped in the RTTViewer. Corresponding RTT log output looks e.g. like this: Source Code (8 lines)The current size of our RTT ring buffer is 2Kb and we think this should be enough and we actually do not want to increase it. Presumably, in case of reset of the MCU the RTTViewer does not restart reading out (and therefore empty) the ring buffer quickly en…

Hello Nino, sure, I'll attach .jdebug and J-Link log file to this post. I tried the export of the external flash memory via J-Link + savebin as you described, still the test.bin (see .jdebug) does not match the savebin export. Best regards Paul

Hello Nino, unfortunately Ozone does not use for download the .bin I specify in .jdebug file. Here is what I do: - Using Ozone v3.10d together with JLink V6.62a - Ozone project file (<myApp>.jdebug) contains path to .elf file ( File.Open("<path>/<myApp>.elf") in function OnProjectLoad(){...}) as well as the path to the .bin file ( Target.LoadMemory("<path>/<myApp>.bin", BaseAdress). - The bin file is basically the same as the bin part within the .elf file, but I changed a few bytes at the beginn…

Hello Nino, thanks a lot for your reply, that sounds good and I will try it. Just to be clear here: You mean in the TargetDownload() routine in the .jdbug file, I shall refer a unencrypted .elf file as well, not the .bin file, correct? Addition: It seems, that when I point to a .bin file in .jdbug (TargetDownload("<path>/.bin", <adress>), Ozone ignores the bin and downloads the content of the .elf file which is denoted in the Ozone project file with File.Open ("<path-to-elf-file>") in function O…

Hi there, we need to flash an encrypted application to the qspi attached NOR flash of our microcontroller and debug it with Ozone. At runtime, the application will be decrypted transparently in the background on-the-fly by a peripheral of the MCU. For the writing of the unencrypted application we use SEGGERs Open Flashloader and it this works, but doing the encryption in Open Flashloader while writing to the NOR flash does not work at all. Our new plan now is to encrypt the application before gi…

Hi there, I modified the OpenFlashLoader so that he encrypts the given application binary and writes it to the QSPI attached flash memory. When I run the OpenFlashLoader using JFlash via "Programm & Verify" it works out fine, the application is flashed and verified successfully, although the overall operation is quite slow. The problem though is, when the same OpenFlashLoader is used by any other tool then JFlash, e.g. the Ozone debugger, the flashing process fails in a quite early stage, saying…