Hi Sebastian, I had mainly tested NuttX Task Trace with spresense:nsh and maix-bit:nsh. I confirmed the feature by the latest source code by changing the following configs and found that it still works. If possible, would you share the configuration to get the error ?
diff boards/arm/cxd56xx/spresense/configs/nsh/defconfig boards/arm/cxd56xx/spresense/configs/nsh-trace/defconfig 28a29,30 > CONFIG_DRIVER_NOTE=y > CONFIG_DRIVER_NOTECTL=y 45c47,50 < CONFIG_SCHED_WAITPID=y --- > CONFIG_SCHED_INSTRUMENTATION=y > CONFIG_SCHED_INSTRUMENTATION_FILTER=y > CONFIG_SCHED_INSTRUMENTATION_IRQHANDLER=y > CONFIG_SCHED_INSTRUMENTATION_SYSCALL=y 52a58,59 > CONFIG_SYSTEM_SYSTEM=y > CONFIG_SYSTEM_TRACE=y Thanks, Yuuichi Nakamura -----Original Message----- From: Sebastian Glatz <sebastian.gl...@voliro.com> Sent: Wednesday, December 30, 2020 9:49 PM To: dev@nuttx.apache.org Subject: Nuttx Task Trace Hi all, I want to set up *NuttX Task Trace *to profile and debug performance related issues of our PX4 modification. For that I have followed this description: https://nuttx.apache.org/docs/latest/guides/tasktraceuser.html#nuttx-kernel-configuration I have edited the .config file. I tried it for both the PX4 project (running on Pixhawk 4) and a plain STM32 blink LED app (running on STM32 Blue Pill). Neither would build with those kernel configurations in place. I would get make errors like this: make[3]: Entering directory '~/nuttx/apps/system/trace' CC: trace.c <command-line>:0:6: error: expected identifier or '(' before numeric constant Has someone successfully used NuttX Task Trace? How did you proceed? Also does anyone have some comments on my error message? Best, Seb
