Posts by SEGGER - Johannes

Hi,

Quote

Does 'based' mean you have adopted/modified/improved that library?

Yes.
STLPort is not maintained anymore, last release is from 2008. Its standard is C++98.
We added some features and compatibility changes for later C++ standards to the library in ES.
Plan is to come up with a new C++ library with a current C++ standard, but there is no immediate schedule, yet.

The compilers in ES support up to C++14 now.

Regards
Johannes

Hi,

There are no limitations other than the general ones for Embedded Studio. That is you may not use the Embedded Studio library for commercial use without purchase of a commercial license.

Embedded Studio also includes a C++ library built for embedded systems, currently based on STLPort.

The libraries are not available with full debug info but as optimized object code only.

There are no hidden costs, such as royalties or software rental fees.
Embedded Studio licenses are perpetual. You purchase it once and can use any update released within one year for as long as you want to.
After that your you can purchase a support and update renewal to get the latest updates, or you stick with your last version and use that one for the next years.

Regards
Johannes

Hi,

The technical features of Embedded Studio are all the same for free and commercial licenses.
You download the exact same setup in both cases. There are no technical limitations with the free licenses.

The major point is: Without a paid license you may not use Embedded Studio for commercial development.

We encourage hobbyists and students to start development of embedded systems.
To start with Embedded Studio is therefore kept simple. You can directly download and install it without registration.
We do not want to spoil the educational use of Embedded Studio with some arbitrary limits, such as 30 days trial or 32k size limit. Embedded Studio can fully be used for non-commercial and educational purposes.

When you want to use Embedded Studio for commercial development, i.e. get paid or earn any money with what you develop, you need to get a commercial license.
Once the license is activated, you can use any Embedded Studio released within your support and upgrade period (typically 1 year) for as long as you want to (even after that year).
When a commercial license is found you do not get the license pop up anymore. Additionally with a paid license you may get support via e-mail instead of through this forum only.

Regards
Johannes

Hi,

SystemView has only been used with CCS in combination with embOS, therefore the default combination used the embOS locking mechanism.

Replacing it with a definition like this should work:

...
 #elif (defined (__TI_ARM_V7M3__) || defined (__TI_ARM_V7M4__))
    #ifndef   SEGGER_RTT_MAX_INTERRUPT_PRIORITY
      #define SEGGER_RTT_MAX_INTERRUPT_PRIORITY   (0x20)
    #endif
    #define SEGGER_RTT_LOCK()   {                                                                   \
                                  unsigned int LockState;                                           \
                                  LockState = _set_interrupt_priority(SEGGER_RTT_MAX_INTERRUPT_PRIORITY);


    #define SEGGER_RTT_UNLOCK()   _set_interrupt_priority(LockState);                               \
                                }
  #endif
...

Regards
Johannes

Hi,

Of course your wav file should not overwrite any other part of your system, so you would usually place it after your applicaiton code.
Since you are probably going to access it from your application, you should know where to put it.

Correct, you add it as Additional Load File[1], set the type to bin and enter the start address where to load it.

Regards
Johannes

Hi,

Regarding ID_BASE it is okay to not call SEGGER_SYSVIEW_SetRAMBase or to call it with 0 as base.

In your recording the start of the SystemInit task is not recorded.
Therefore SystemView does not know in which context the system currently executes.
We might improve this behavior to let the system record its current context on start of recording.

It might be possible that FreeRTOS does not create a task run event when the scheduler is started,
but I did not verify this.

What you can try is call SEGGER_SYSVIEW_Start() immediately after SEGGER_SYSVIEW_Conf()/SEGGER_SYSVIEW_Init().
This will start recording directly.
You can then either break after that call and connect with SystemView to catch the full recording, or you run and attach at a later point to get the start and everything from when you attached.

Regards
Johannes

Hi,

SEGGER_SYSVIEW_X_GetTimestamp() will be called in the recording function called by SEGGER_SYSVIEW_Record*().
You do not have to modify them.

If the recording shows only one cycle, make sure that the implementation of SEGGER_SYSVIEW_X_GetTimestamp() does work.
Refer to the sample configurations given for the various supported systems.

Regards
Johannes

Hi,

Thanks for the explanation.
Would it be possible to get a recording of the behavior you described?
That would allow a better analysis of what might go wrong.

If you get duplicated or invalid events this indicates that your system is not behaving correctly or that the SystemView data cannot correctly be read.

Could it be possible that you use low-power modes (call WFI) in your application?
This would also explain why you cannot connect with SystemView while the system is running.

Regards
Johannes

Hi,

Keil does not support extended assembler syntax.

Instead you can use something like this:

U32 SEGGER_SYSVIEW_X_GetInterruptId(void) {
  register U32  IPSR __asm("ipsr");
  return(IPSR);
}

Regards
Johannes

Hi,

Did you make sure that SEGGER_RTT_MAX_INTERRUPT_PRIORITY is defined according to your system configuration to mask all interrupts that produce SystemView events?

Regards
Johannes

Hi,

You are right, Cortex-M0+ devices do not have the ICSR[VECTACTIVE] bits implemented.
Instead you can read the active vector from the IPSR, best implemented in a user-provided function SEGGER_SYSVIEW_X_GetInterruptId():

/*********************************************************************
*
*       SEGGER_SYSVIEW_X_GetInterruptId()
*
* Function description
*   Return the currently active interrupt Id,
*   which ist the active vector taken from IPSR[5:0].
*
* Return value
*   The current currently active interrupt Id.
*
* Additional information
*   This function is not used by default, as the active vector can be 
*   read from ICSR instead on Cortex-M0.
*   For Cortex-M0+ devices, change SEGGER_SYSVIEW_GET_INTERRUPT_ID
*   in SEGGER_SYSVIEW_Conf.h to call this function instead.
*/
U32 SEGGER_SYSVIEW_X_GetInterruptId(void) {
  U32 Id;


  __asm volatile ("mrs %0, ipsr"
                  : "=r" (Id)
                  );
  Id &= 0x3F;


  return Id;
}

Regards
Johannes

Hi,

You are correct, it does work in post mortem mode because the middleware info is periodically written to the buffer.

Please make sure that the buffer is large enough to hold the full system and middleware information (and of course enough events for your analysis).

Regards
Johannes

Hi Marcus,

In general there should not be a problem, as with STM32F4 devices even auto detection should work.
So if the control block cannot be found there seems to be an issue with your setup.

It is correct that J-Link Commander does not give an output, neither will RTT Client if you do not do any prontf output viar RTT.

Do you run SystemView stand-alone or is there any other connection to J-Link, e.g. a debug session, open?
Did you select the device in the SystemView configuration dialog?
Does your system use any low-power mode, i.e. call WFI?

Regards
Johannes

Hi,

Yes, it is possible with this command:

var = Elf.GetExprValue("&variable");

Regards
Johannes

Hi,

To just load the second file without reset, you can use File.Load() instead of File.Open() and Debug.Download().

Best regards
Johannes

Hi,

The FreeRTOS plugin in general works, so we would need more information to analyze the problem.

Are you using the 64-bit or 32-bit version?
Which version of FreeRTOS do you use?
Would it be possible to provide your application elf file?
Do you use a standard eval board or custom hardware?
Could you provide a Ozone log file of a crashed session? (start Ozone with --logfile=<PathToLogfile>)

Best regards
Johannes

Hi,

Regarding the 0 timestamps:

This can happen when the DWT unit is not enabled.
On Cortex-M3/4 the timestamp is generated from the DWT->CYCCNT, so the cycle counter needs to be enabled and to do this the DWT needs to be enabled as well.
This is usually done by the debugger, but can also be done by the application.

if ((CoreDebug->DEMCR & CoreDebug_DEMCR_TRCENA_Msk) == 0) {
CoreDebug->DEMCR |= 1 << CoreDebug_DEMCR_TRCENA_Pos; // Enable DWT in DEMCR if not done, yet.
}
DWT->CTRL |= 1 << DWT_CTRL_CYCCNTENA_Pos; // Enable CYCCNT in DWT_CTRL.

When there has been a debug session running or you connected with J-Link before, and read the data without a reset,
then the CYCCNT might have still been enabled and the application generated real timestamps.

If you do not want to use the CYCCNT, you can of course configure SystemView for any other timestamp source, i.e. the SysTick, too.

Regards
Johannes

Hi,

Sorry for the delay in response.

Filter on specific API events from the OS or other modules can now be set with SystemView PRO.
Otherwise it is only possible to show all or no API functions at all.

The module description looks correct so far. In addition to M=<ModuleName> you can optionally add V=<VersionNumber>, other parameters are not supported.

With module name and version number it is possible to load a description file to not need to describe all functions in the module description (and save some memory).
To do this, place a file SYSVIEW_<ModuleName>_<VersionNumber>.txt or SYSVIEW_<ModuleName>.txt in /description/ of the SystemView installation directory.

With the current version of SystemView, the registered modules also show up in the System Information, so there you can check that registration worked.

Best regards
Johannes

Hi,

SystemView loads the most recent J-Link Software.
If you have a restricted account and installed the J-Link Software with administrator credentials,
it can happen, that the registry path to the J-Link software is not added to your users HKEY.

The easiest solution is to copy the J-Link DLL into the SystemView installation directory.
For more information, have a look at https://wiki.segger.com/Could_not_open_J-Link_shared_library

Best regards
Johannes

Hi,

Sorry for the late reply.

Can you check that your target application is still running after you connected SystemView or called SEGGER_SYSVIEW_Start().

This issue is most commonly caused by a crash of the target application, for example because your stack sizes are too small.

Best regards
Johannes