Search Results

Hi Matthias, thanks for the answer. I'll use the proposed options. Can be closed. Best, Michael

Setup: J-Scope 7.59a beta, J-Link Edu V9, STM32L431, Linux I have a loop generating new data every 1ms. I checked this timing with a scope and pin toggle. Within this loop a block of RTT without timestamps is sent, works fine so far. J-Scope shows this data but the time between two data points is shown and logged as 100µs. I noticed that there is a parameter "SamplingPeriod" in the .jscope config file, default is 100. I changed it to 1000 (1ms), but this had no effect. Does anyone has a solution…

Meanwhile, the updated versions of JScope work for me ok'ish, sometimes I get a "Speicherzugriffsfehler" and it crashes, project saving still does not work for RTT projects. Anyway, the inital bug why this thread was started is solved and it can be closed. Thanks again!

Thanks, I tried both V7.54b and V7.55b beta. With same target firmware, J-Scope now displays data and I can scale the graphs etc. Although the original bug is resolved, J-Scope still crashes when loading a .jscope config file created with the same version. config file is attached (added .txt only for upload since forum does not allow .jscope extension) Error log in terminal: Source Code (8 lines) The "Pause" button sometimes does not pause the recording, did not figure out the logic behind. If i…

Hi, thanks for your reply, sorry for my delay. I really appreciate that J-Scope is being re-born I realized that I was still using some v6.xx RTT headers and sources on the target. I updated to the recent version, but this did not help, i.e. J-Scope does not show data, but RTTLogger works, as before. Unfortunately, due to NDA I can't provide the .elf. But this is my init for RTT in main on target, RTT headers and sources are unchanged: Source Code (5 lines) Then, in a periodic interrupt data is …

Really happy to get new J-Scope versions, thanks for that! Sadly, it does not work for me; does anybody has/had the same problem and a solution? OS: Win10 (tried on three different PCs), Fedora34 (both 64 Bit) J-Link hardware: J-Link Edu 9.3, latest firmware J-Link software tried (same results): 7.54, 7.55a (beta) (64 Bit and 32 Bit, as normal user and as admin) Target: STM32F103C8 using RTT, both with and without rtt_time information at beginning of RTT buffer What works: - connecting target to…

6.60c solves this, thanks for the fast fix! Already subscribed to update messages, thanks.

Host OS Linux Fedora 30, 64Bit J-Link EDU V9, fw 13.12.2019 When upgrading from J-Link software version 6.56d to any of J-Link software versions 6.60, 6.60a, 6.60b, 6.61a the "Terms of use" screen keeps reappearing each time I start jlink. The activation of the tick box "Do not show this message again for today" does not prevent the message from reappearing (it worked on 6.56d). Does anybody else observes the same behaviour? It's perfectly fine to acknowledge this once a day, but extremely annoy…

[SOLVED] ST-Link Reflash Utility for ST-LINK V3E ?

Ok, thanks, can be closed.

Hi Segger team, I just want to add +1 vote to make mass erase/unlocking upon detection of a secured chip NOT automatic for all OS versions (especially Linux)! Under the assumption that jlink is a cautious and safe tool I bricked a device. Couldn't find a hint to the automatic unlocking in the J-Link User Guide. Please change this behaviour, as already discussed in this forum. In case I missed something, here's the log. Host is Linux, CLI 'jlink', no prompt or user interaction was possible after …

Thanks for the info and the feature request!

Thanks, looking forward to the Linux version.

Hi, J-Scope is a great tool and I'd like to use it on Linux. What ways are known to work? I tried these: - With a Win guest in a virtualbox, J-Scope works fine, but the J-Link is attached to the virtualbox and I can't run a JLinkGDBServer on Linux in parallel. - J-Scope can be installed in wine, but neither the J-Link is reachable via USB (out of wine) nor can I connect via TCP/IP (localhost:2331) to a running JLinkGDBServer (under Linux, on localhost). I guess, "TCP/IP" is only for J-Link probe…

Hi, thanks for your reply. I retested and attached the files: Setup: Win7Prof in Virtualbox on Fedora host, J-Link Edu, no issues with J-Scope or debugging Steps done: 1) Created new project in J-Scope 6.11j. 2) Started sampling, Y resolution and offset was adjusted automatically. 3) Set Y resolution and Y offset, both for every channel, in the GUI, saved config to Test_01.jscope. (renamed later to Test_01.jscope.txt for upload) 4) Closed J-Scope. 5) Started J-Scope and loaded Test_01.jscope. Th…

Yes, I tested 5.10d and 6.11j. YOffset="..." and YResolution="..." are stored and initially restored on opening an exisiting project, as you wrote. But the problem is that the channels get autoscaled and Y-shifted again when I start sampling and my manual settings are not respected any more. I manually set the parameter IsAutoConfig="0" for all channels in the config file, but this does not help. Maybe the question has to be rephrased: Is it possible to turn off autoscaling?

Hi, in J-Scope I'm missing the feature that the manually set layout of the traces is saved in the config file, too. At start, Y Resolution and Offset is scaled automatically according to the data, which generally helps, but I'd like to store my manual settings for the Y Res. and Offset, too. E.g. if something crashes I have to manually restore the settings every time. Is there a way to make this easier? Thanks!

Ok, thanks for the info.

Is there a way to use an external logic signal to halt the CPU without instrumentation on the target CPU? Is there a trigger event input or similar function on J-Link debug probes? The idea is to break program execution on an oscilloscope scope trigger event with minimal delay without involving the host PC. Target hardware is STM32F10x with J-Link Edu.