I have tried using SystemView in a FreeRTOS application:

Processor: Cortex-M3 (in LPCXpresso LPC1769 board)
IDE: MCUXpresso IDE v11.2.1 [Build 4149] [2020-10-07]

OS: FreeRTOS kernel v10.4.3
SystemView: v3.20

I have followed the steps detailed in the user guide, namely:

• I have copied the following files into the project (keeping the recommended directory structure):
  
  • /Config/Global.h
    
  • /Config/SEGGER_RTT_Conf.h
    
  • /Config/SEGGER_SYSVIEW_Conf.h
    
  • /Config/SEGGER_SYSVIEW_Config_FreeRTOS.c
    
  • /Sample/FreeRTOSV10/SEGGER_SYSVIEW_FreeRTOS.c
    
  • /Sample/FreeRTOSV10/SEGGER_SYSVIEW_FreeRTOS.h
    
  • /SEGGER/SEGGER_RTT.c
    
  • /SEGGER/SEGGER_RTT.h
    
  • /SEGGER/SEGGER_SYSVIEW_ConfDefaults.h
    
  • /SEGGER/SEGGER_SYSVIEW_Int.h
    
  • /SEGGER/SEGGER_SYSVIEW.c
    
  • /SEGGER/SEGGER_SYSVIEW.h
    
  • /SEGGER/SEGGER.h
    
• I have included in the path the three folders.
  
• In FreeRTOSConfig.h I define INCLUDE_xTaskGetIdleTaskHandle and INCLUDE_pxTaskGetStackStart as 1.
  
• At the end of FreeRTOSConfig.h (after all the defines) I #include "SEGGER_SYSVIEW_FreeRTOS.h".
  
• I have added a call to SEGGER_SYSVIEW_Conf() in the main function (after target initialization and before any FreeRTOS API function call).
  
• I have not been able to apply the patch file to the FreeRTOS kernel sources because they do not match.
  

When I try to compile the project it gives me the following error: macro "traceTASK_NOTIFY_FROM_ISR" passed 1 arguments, but takes just 0. It gives me the same error with the following macros:

• traceTASK_NOTIFY_FROM_ISR
  
• traceTASK_NOTIFY_GIVE_FROM_ISR
  
• traceTASK_NOTIFY_TAKE
  
• traceTASK_NOTIFY_WAIT
  
• traceTASK_NOTIFY
  

I can see, in effect, that the macro traceTASK_NOTIFY_FROM_ISR, for example, is defined as follows in the SEGGER_SYSVIEW_FreeRTOS.h file.:
#define traceTASK_NOTIFY_FROM_ISR() SEGGER_SYSVIEW_RecordU32x5(apiID_OFFSET + apiID_XTASKGENERICNOTIFYFROMISR, SEGGER_SYSVIEW_ShrinkId((U32)pxTCB), ulValue, eAction, (U32)pulPreviousNotificationValue, (U32)pxHigherPriorityTaskWoken)

However, in the tasks.c file it is called as traceTASK_NOTIFY_FROM_ISR( uxIndexToNotify ). That is, they are defined without parameters, but they are called with a parameter.

But no one else seems to have that problem. I miss something ...


Did I forget to configure something?


Thank you.

So that was the little detail that I forgot ... I had understood it right backwards when reading the other threads: I believed that as of FreeRTOS v10.0.0 the patch was no longer necessary.


Well, I have tried again to create a FreeRTOS SystemView application, this time with version 10.0.0, thinking that it would not have compilation problems, but I was wrong. I have followed the steps above and also applied the patch without problems. When compiling the project I received errors such as "undefined reference to 'SEGGER_RTT_ASM_WriteSkipNoLock' " that were fixed by adding the SEGGER_RTT_ASM_ARMv7M.S file. But then I got the error "fatal error: SEGGER_RTT_Conf.h: No such file or directory" which I have not been able to fix.


The SEGGER_RTT_Conf.h file is in the 'Config' directory, as recommended in the SystemView user guide, directory added to the path. Why am I getting that error?


Thanks for your time, Nino. Maybe I better open another thread?
Asier

Hello Nino,

Thanks for your time. Obviously, I understand that you cannot provide support for third party software. I also understand that the level of forum users is usually very diverse (from beginners to experts in the world of embedded software), which makes support even more difficult (for example, you cannot know if the user knows, indeed, to add a file to path).

But I think that sometimes you hide behind third-party software: if I post the question to the MCUXpresso forum, they will tell me that they cannot offer support for FreeRTOS or SystemView, as they are third-party software. Ditto on the FreeRTOS forum. Etc.

If I posted the question to the SystemView forum it is because it is new to my project. I've been working with MCUXpresso for years (since it was LPCXpresso) and months browsing with FreeRTOS. I'm not going to say that I have no problems with them, but so far I get the projects to compile - another thing is that they do what they should do

Now I try to add the SystemView functionality to them and that is when it stops compiling. So I think it is a SystemView problem. As specified in my previous post, the 'Config' directory was included in the path. If I look in the project properties, the 'Config' directory appears in the 'Include paths (-I)' and, in addition, it is recognizing other header files from the same directory.

I bought the J-Link to be able to debug FreeRTOS projects in MCUXpresso (because you tell me I can do it). I get the product and follow the instructions you give (because I also understand that some users ask without even reading the user manual). But following the instructions that you give (I think, that is why I detailed the steps taken so much, because another option is that I had not followed the instructions well) I cannot reach the objective. And when I ask for help, you hide behind third-party software.

Without further ado, Nino, I simply wanted you to understand how users feel sometimes. I have bought a product from you, I have followed your instructions, but I have not obtained any results.

As for the problem in the previous post, I have done a little test and post it in case it could help someone. Instead of creating the directory tree recommended in the SystemView User Guide I have created the following scheme: within the 'systenview' directory I have only created two directories, one named 'src' where I have copied the source files and the other named 'inc' where I have copied the header files and the assembler file 'SEGGER_RTT_ASM_ARMv7M.S '. Obviously, I have included the file 'inc' to the path.

Maybe it is not ideal, because the configuration files and those that are not are mixed, but it works. At least it compiles (I haven't had time to test it). I don't know why that happens (that is, I don't know what the problem is), but what I said: with the structure recommended in the user guide (structure that I detail in the first post) the project does not compile me, and with this new structure yes. The two projects are identical except for the 'systemview' directory structure (and the path, of course).

Thank you very much,

Asier

Hi warlord,

Thanks for your answer. Keeping the directory structure recommended in the SystemView user guide (detailed in the first post of this thread) and replacing the SEGGER_RTT_Conf.h file as recommended, I get the error:
I hope it helps. Thank you very much for your attention,
Asier

Hi warlord,

Done: I replace the content of the file with the original (copying and pasting the content, without replacing the file) and I get the original result (error in 16~18 lines):

Hi warlord,

Great! Every day you learn something ... and with help much more.

First: I thought the error came from SEGGER_RTT.h: 60: 10, but no, I realize that a line before marks the error that you point out to me, SEGGER_RTT_ASM_ARMv7M.S: 18:

Second: I had no idea that assembler files had their own path.

Third: now I understand why the src and inc directory structure worked. The inc directory was in the path of the assembler files.

I have included the Config directory in the path of the assembly files and... voilá! Compile perfectly.

In the end, it was my mistake and it was, indeed, the path, as Nino pointed out. But I would like to emphasize that with a little help, the less experienced can also learn and enjoy these devices. Think, if not, in what position I was: I had bought a J-Link to debug FreeRTOS projects and it was of no use to me.

Although it is not true, it has not been a little help, it has been A LOT of help. Thank you very, very much for your time, patience and dedication, warlord. With help like the one you have offered me, you can learn a lot. Thank you very much, really.

Asier