Search Results

Hello, thank you for bringing this to our attention. Would it be possible for you to share an .elf file that can be used as a reproducer to demonstrate these issues? Best regards, Matthias

Hello, yes, this should work. You can find more information about J-Scope in the wiki. wiki.segger.com/UM08028_J-Scope Best regards, Matthias

Hello, this function is currently not available, because of some faulty behavior. It will be readded with a future release of J-Scope. Best regards, Matthias

Hello, J-Scope has been included in the J-Link Software and Documentation pack which you can download at: segger.com/downloads/jlink/ You can find the executable at the default installation path: C:\Program Files (x86)\SEGGER\JLink Best regards, Matthias

Hello Michael, when RTT without timestamps is used, a block of samples without any timestamps arrives for J-Scope at the same time. Therefore there is no real way for J-Scope to know the real time difference between any two samples. Because of this, J-Scope just assumes a time difference of 100 us. If you want to have timestamps that reflect the real situation, we recommend using HSS or better RTT with timestamps. Best regards, Matthias

Hello, a similar sounding issue was just fixed and will be released with the next version of the J-Link software package scheduled for some time next week. Once released, could you give it a try and tell me if it solves the issue? Best regards, Matthias

Hello, that would be very helpful, thank you. Best regards, Matthias

What I meant is the .out file of course.

Hello, such an issue is not known to us. Would it be possible for you to provide the .elf file for us to investigate the issue? Best regards, Matthias

Hello, this would be V6.11m. Best regards Matthias

Hello Franz, the current version of J-Scope is a rework that was released a few months ago and is still being improved upon. The option to configure RTT search ranges is currently not implemented, but is on the list of features to add to J-Scope. I will let you know when it is done and in which release this will be included. Best regards, Matthias

Hello, sorry for the delayed response, there were a lot of interrupts. I tried to reproduce the issue, but am not sure that I have a complete picture of the setup you are using. Would it be possible for you to provide the following? - The elf file - The code for the RTT initialization and usage - A detailed step-by-step reproduction guide - A short screen recording demonstrating the issue Parallel usage can be a complex issue for which we would need as much information as possible. Best regards,…

Hello, thank you for the feedback. We are not aware of such an issue. I will try to reproduce it and get back to you with my results. Best regards Matthias

Quote from hdgb: “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: ” Hello, thank you for the feedback. I was sometimes able to reproduce the crash issue, but it does not seem to be consistent. I will have a look into fixing this issue. Regarding the Pause button: The current behaviour of the pause b…

Hello, your RTT usage looks good. There was indeed an issue with the displaying of RTT data that matches your description. This issue was resolved with V7.54b of the J-Link software package. Thank you for bringing this to our attention. Best regards, Matthias

Hello, The recent version of J-Scope was a major rework that still has some bugs to iron out, so thanks for your detailed feedback Regarding the main issue: Is it possible for you to provide the .elf file and .jscope project file? I´ve had a quick look with a generic RTT setup and this works as expected. The pause button and saving issues are reproduceable and will be addressed as soon as possible. I was not able to reproduce the behaviour that you mentioned where the variables are not selectabl…

Hello, issues 2 & 3 should be fixed now and will be included in the next release of the J-Link software package. Could you send us the ELF file and Project file for issue 1? Best regards, Matthias

Hello, we have tested the flash loader elf file from the "Output\Release\Exe" directory that you sent us. The elf file did not contain the SEGGER_OPEN_Read function. At a guess, it looks like it may have been optimized away when compiling. We have prepared a project for you so that we can be certain, that we are testing with the same conditions. download.segger.com/Matthias/STM32F207VC_Test.7z This contains a StartTest.bat which starts J-Flash and executes a readback of the selected sectors. Thi…

Hello, we have investigated this issue and were not able to reproduce it. With the project you sent us, SEGGER_Open_Read() is not called when using the flash loader ELF file with J-Flash. We were able to successfully use our template project as flash loader. Could you try out the attached template project and let us know the results? Best regards Matthias

Hello, the issue should be fixed now with J-Link V6.88b which was released last friday (2020-11-27). Best regards Matthias