Search Results

Search results 1-9 of 9.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Ok, I have implemented this and it appears to work - the 'module' information appears to be written along with Sync and System Info events as described in section 6.2.5 ("SEGGER_SYSVIEW_SYNC_PERIOD_SHIFT").

  • Custom events

    rene.becker - - SEGGER SystemView related

    Post

    Hi Michael, Have a look at section 10.2 (Integrating SEGGER SystemView into a middleware module) - that should be what you're after Regards, Rene

  • I did some further work on this ..... The Host Application Behaviour is still the same, i.e. when I perform a 'Read Recorded Data' the application still only appears to load 5 events. However, if I save the data from the target buffer into a binary file as described here: segger.com/products/developmen…t-mortem-mode/#tab-3559-6 and subsequently load this file into the Host application I do see sensible activity. Any idea why Read Recorded Data might not work?

  • Hi, I am thinking of creating some custom events in order to squeeze more events in the SystemView buffer on my target device. I am reading through the section 'Integrating SEGGER SystemView into a middleware module' and skimming through some of the source code, and by the looks of it the target has to send some special packets to the host to register any custom module with the host SystemView application. Since in Post Mortem mode the target buffer is continuously overwritten those packets will…

  • Thanks, Johannes. makes sense. Have just tried standard Eclipse with Gnu ARM Eclipse plugin again, this time specifying the exact part number. Unfortunately still not working. I am using TIs code composer at the moment which is ok, but it does not appear to support the remote debugging feature. No problem during development, but when deploying remote debugging would be a really good feature to have ... Regards, Rene

  • Hi, I have SystemView working ok. in 'normal mode', but would now like to switch to post mortem mode. When I do this (following instructions on segger.com/products/developmen…t-mortem-mode/#tab-3559-5), then run the target, stop the target after a while and read the data from target (Target->Read Recorded Data) it only loads 5 events (Start, System Info, 2x System Description Entries and Target Time). When inspecting the buffer it appears to be filled as expected. What could be going wrong?

  • Ok, it's working. By default the 'Configuration' Dialog that pops up when pressing the green arrow button shows Cortex-M3. If I go and expand the drop down list I find the actual device (LM3S2D93) in the list, and after selecting that SystemView connects just fine. I didn't look there before because I thought Cortex-M3 was auto-detected correctly (and the device indeed is based on a Cortex M3 ... I am also having trouble with some other aspects, e.g. I cannot use plain Eclipse with GNU Arm Eclip…

  • Hello, I believe that with SystemViewer I should be able to connect to a running target at any time, but at the moment I am not able to do so unless I have an active debug session going. When a debug session is runnig SystemView appears to work as it should, if not I always get an error message "Failed to start recording. RTT Control Block not found". The device I am working with is a TI Stellaris LM3S2D93, I am using Code Composer Studio V6.2. I am using the gcc toolchain, not TI's toolchain. A…

  • Hi, I am having trouble with using the SWO Viewer since upgrading my J-Link SW from version 4.74b to 4.78g. The first thing I noticed is that with the new version my debug session is 'lost'. When I start a debug session with certain breakpoints set these are never hit if I start to monitor terminal output with JLinkSWOViewer.exe/JLinkSWOViewerCL.exe. It looks as if starting the SWO viewer resets the processor again. The second thing I noticed is that the output of the commandline variant is no g…