Search Results

I upgraded to 2.34 and it crashes no more! my next problem will be lots of dropped packets but this is likely because the target interface speed changes from what I defined in the command line of the gdb server.

sorry to bring this up again, but would it be possible to call the needed functions on the target manually after a reset that SystemViewer can keep recording? thank you very much!

okay, the signature of the std lib _write_r function is: C Source Code (1 line) vs. the signature of the SEGGER_RTT_Syscalls_GCC.c C Source Code (1 line) boils down to this difference: size_t is an unsigned type, int is signed. I'm a bit curious why I face this problem and can't find anyone else with this problem. we are using newlib.

Hi, this is unlikely a problem of RTT, but some of you might have an idea whats wrong here? ../../libs/middleware/segger_rtt/Syscalls/SEGGER_RTT_Syscalls_GCC.c:104:5: error: conflicting types for '_write_r' int _write_r(struct _reent *r, int file, const void *ptr, int len) { ^ In file included from ../../libs/middleware/segger_rtt/Syscalls/SEGGER_RTT_Syscalls_GCC.c:46:0: /usr/local/arm-none-eabi/include/reent.h:159:17: note: previous declaration of '_write_r' was here extern _ssize_t _write_r _P…

Hi, I read that emUSB now supports CDC-ECM protocol. How would you describe the Advantage of CDC-ECM over RNDIS? I have the reception, since RNDIS does not require drivers in Windows, it might be a good cross-platform option. thank you very much! best regards

you seem to have made some progress very nice! happy to receive your beta, too! Erich already wrote a blog post about it mcuoneclipse.com/2016/05/18/fr…th-segger-gdb-in-eclipse/

how is the current state here? did you add this feature to the J-Link tools?

what are the changes in 2.34 that could improve the stability under high load situations?

Hi SystemView users, have you seen this: toem.de/index.php/projects/imp…ystem-viewer-with-impulse ? might be worth a look! they are actively seeking partners for joint integration, interfaces and collaborated development.

it was just a suggestion from my side. I don't think it's implemented yet.

fifo-style display might be a solution? discard older events to enable an endless live view.

Quote from SEGGER - Alex: “Hi, Quote: “ what about the target sources for SystemViewer? ” What's the question here? What are you asking for here? Sorry but this question is anything but clear.... As you can see on our website, the target sources for SystemView can be downloaded from our website: segger.com/downloads/free_tools#SystemView - Alex” this was an addition to the discussion about collaborating with the community through putting source code in a puplic reposiotry. as I have to admit, th…

thanks for the response. I clearly understand this concern. what about the target sources for SystemViewer?

Quote from SEGGER - Niklas: “Hi Martin,can you write an E-Mail to segger.com/support/technical-support/ regarding this problem, in order to make sure that you will get help as fast as possible?This forum is mainly for customers who are out of the E-mail support time (Or never had one, like J-Link EDU / J-Link lite users).Best regards,Niklas” sorry for the OT but...why do you think so? this forum is of great use of everyone using your tools. it eases the run on your support channels to remain the…

is this topic of interest for further development? would be nice to follow the SystemView without restarting the session each time I reset my debug session.

aargh... the reflection in the IDE was wrong. the RTT_LOCK symbol is defined! ...and it gets called! So my problem is not solved

Hi Johannes, thanks for your attention. you are right; SEGGER_RTT_LOCK is not defined during the build... need to look into it. regards

just a quick note: one has to be really careful on what memory address is specified for the "testcspeed" command in JLink Commander. for Freescale (NXP) devices there are different SRAM regions which are accessible differently for data and instructions. I was confused because I got a reading of half the frequency I was expecting. turns out, I was running the test in a suboptimal SRAM region (SRAM_U). The information in which memory region the speed test should be run is available in JLinkSWO Vie…

Hi Niklas, thank you very much for your explanation! I appreciate it very much! I have edited a previous post of mine. best regards Peter

I'm using a STM32F429 device. J-Link Commander says 180 MHz. This covers with my intention. But I face some strange effects with my application and want to be sure about the Freq. I'm on linux. there is no binary called "JLinkCommander". But "JLinkExe" seems to understand the same commands. How would I connect to a target via script mode? I want to have the core frequency printed on stdout. edit: hope this helps if someone wants to do the same: Source Code (4 lines) Source Code (40 lines) with s…