Add rp2040.getProfileMemoryUsage()

Author: earlephilhower

cores/rp2040/RP2040Support.h

@@ -489,6 +489,11 @@ class RP2040 {
         __profileFile = f;
         _writeProfile(__writeProfileCB);
     }
+
+    size_t getProfileMemoryUsage() {
+        extern int __profileMemSize;
+        return (size_t) __profileMemSize;
+    }
 #endif
 
 

cores/rp2040/gprof_gmon.c

@@ -322,6 +322,8 @@ static int	s_scale;
 
 static void moncontrol(int mode);
 
+int __profileMemSize = 0;
+
 void __no_inline_not_in_flash_func(monstartup)(size_t lowpc, size_t highpc) {
     register size_t o;
     char *cp;
@@ -343,16 +345,16 @@ void __no_inline_not_in_flash_func(monstartup)(size_t lowpc, size_t highpc) {
         p->tolimit = MAXARCS;
     }
     p->tossize = p->tolimit * sizeof(struct tostruct);
-
+    __profileMemSize = p->kcountsize + p->fromssize + p->tossize;
 #ifdef RP2350_PSRAM_CS
-    cp = pmalloc(p->kcountsize + p->fromssize + p->tossize);
+    cp = pmalloc(__profileMemSize);
     if (cp == (char *)0) {
         ERR("monstartup: out of memory\n");
         already_setup = 0;
         return;
     }
 #else
-    cp = malloc(p->kcountsize + p->fromssize + p->tossize);
+    cp = malloc(__profileMemSize);
     if (cp == (char *)0) {
         ERR("monstartup: out of memory\n");
         return;

docs/profiling.rst

@@ -11,7 +11,9 @@ per second.  When an application is complete, the recorded date can be dumped to
 s histogram of PCs and tally of function caller/callees can take a significant amount of RAM, from 100KB
 to 10000KB depending on the size of the application.  As such, while the RP2040 **may** be able to
 profile small applications, this is only really recommended on the RP2350 with external PSRAM.  The
-profiler will automatically use PSRAM when available.
+profiler will automatically use PSRAM when available.  Call ``rp2040.getProfileMemoryUsage()`` to get the
+memory allocated at runtime.
+
 
 Profiling also adds processing overhead in terms of the periodic sampling and the function preambles.
 In most cases there is no reason to enable (and many reasons to disable) profiling when an application