Building on PIO with v5.0.0 needs over 30s

[sstaub]

I'm using the core with PIO and VSCode using a MacBookPro 16 M4 with macOS 15.6.1
After update to v5.0 the building after following lines in Terminal takes over 30s, this behavior is new with 5.0
The compiling itself work normal, the building is the problem.

Building /Users/sstaub/Dateien/Development/Raspberry Pico/eOS4/.pio/build/pico/firmware.lst
Building /Users/sstaub/Dateien/Development/Raspberry Pico/eOS4/.pio/build/pico/firmware.debug.lst 

that is my ini file

[env:pico]
platform = https://github.com/maxgerhardt/platform-raspberrypi.git
framework = arduino
board_build.core = earlephilhower
board_build.filesystem_size = 0.5m
#board = rpipico
board = wiznet_5500_evb_pico2
platform_packages =
   framework-arduinopico@https://github.com/earlephilhower/arduino-pico.git#master
build_flags = -Wall

[earlephilhower]

Not sure there's anything that we can do about something nebulous like that.

5.0 didn't really change anything non-FreeRTOS (and for FreeRTOS apps, it's still building the same files but in a different folder). 4.7 moved LWIP to source to avoid needing to rebuild and store libpico 6 times, which is about 50 plain C files but they're not too large or complex. 5.0 actually removes ~4K of generated code in the non-freeRTOS case compared to 4.7.1 due to the #define __FREERTOS change vs weak functions.

As a data point, on my not-so-new AMD 5600X under Ubuntu a build of an empty sketch from clean startup (no cached .as) takes ~5 seconds under the IDE. What is your compile time for an empty setup/loop sketch under your Mac and P.IO?

[earlephilhower]

Also, if you can get times for each stage of processing (i.e. scanning libraries, compiling, linking) that might help pinpoint things. I would imagine the PIO build logs can include timestamps, somehow...

[earlephilhower]

I also just verified the CI platform.IO builds are running in about the same time pre 4.7 as post 5.0. Looks like about a 20 second difference overall, but that's actually 20 seconds add'l while building 7 sketches, so only ~3 add'l seconds/sketch.

Also looked at the ARM Mac CI times pre-4.7 and post-5.0 and they're basically identical. They are, however, running arduino-build and not platform.io.

[sstaub]

Sorry I found no timestamp, so I describing it manually, compiling a simple blink sketch:

All the stuff before works as expected

..........
Compiling .pio/build/pico/FrameworkArduino/wiring_shift.cpp.o
Archiving .pio/build/pico/libFrameworkArduino.a
Indexing .pio/build/pico/libFrameworkArduino.a
Linking .pio/build/pico/firmware.elf
Building /Users/sstaub/Dateien/Development/Raspberry Pico/arduino-blink/.pio/build/pico/firmware.lst
Building /Users/sstaub/Dateien/Development/Raspberry Pico/arduino-blink/.pio/build/pico/firmware.debug.lst

Here the problem start, it need about 40s before building is finished

Generating UF2 image
picotool uf2 convert -t elf ".pio/build/pico/firmware.elf" ".pio/build/pico/firmware.uf2"
Retrieving maximum program size .pio/build/pico/firmware.elf
Flash size: 4.00MB
Sketch size: 3.50MB
Filesystem size: 0.50MB
PSRAM size: 0.00MB
Maximium Sketch size: 3665920 EEPROM start: 0x103ff000 Filesystem start: 0x1037f000 Filesystem end: 0x103ff000
Checking size .pio/build/pico/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [          ]   1.8% (used 9492 bytes from 524288 bytes)
Flash: [          ]   1.6% (used 58844 bytes from 3665920 bytes)
Building .pio/build/pico/firmware.bin
Building .pio/build/pico/firmware.bin.signed
=================================================== [SUCCESS] Took 45.36 seconds ===================================================
 *  Terminal will be reused by tasks, press any key to close it. 

It seems there is a problem with
Building /Users/sstaub/Dateien/Development/Raspberry Pico/arduino-blink/.pio/build/pico/firmware.debug.lst
Compiling with the Arduino IDE works fine it happens only with VSCode.

[sstaub]

I looked into my other MBP13 M1, where the dependencies were not updated and compiling works as expected.
The only difference are the following two lines while compiling which are new after update to v5.0

Building /Users/sstaub/Dateien/Development/Raspberry Pico/eOS4/.pio/build/pico/firmware.lst
Building /Users/sstaub/Dateien/Development/Raspberry Pico/eOS4/.pio/build/pico/firmware.debug.lst 

[earlephilhower]

I think you need to actually get full logs with timestamps. Line by line compile commands/etc. with when they were executed, to get anywhere.

You can check the platform-build diffs for 5.0 vs 4.7.1, there's basically nothing other than a new #define if you set the FREERTOS flag or BT (which you're obviously not using on the W5500). No add'l build targets are added in the code so something in P.IO or the system's config files somewhere seem to be adding something (what exactly are those files?).

earle@amd:~/Arduino/hardware/pico/rp2040$ git diff 4.7.1 -- tools/platformio-build.py
diff --git a/tools/platformio-build.py b/tools/platformio-build.py
index 440cb0a05..a7525585c 100755
--- a/tools/platformio-build.py
+++ b/tools/platformio-build.py
@@ -89,12 +89,21 @@ if "PIO_FRAMEWORK_ARDUINO_ENABLE_BLUETOOTH" in flatten_cppdefines:
     env.Append(
         CPPDEFINES=[
             ("ENABLE_CLASSIC", 1),
-            ("ENABLE_BLE", 1)
+            ("ENABLE_BLE", 1),
+            ("CYW43_ENABLE_BLUETOOTH", 1)
         ]
     )
 else:
     libpicow = File(os.path.join(FRAMEWORK_DIR, "lib", chip, "liblwip.a"))
 
+if "PIO_FRAMEWORK_ARDUINO_ENABLE_FREERTOS" in flatten_cppdefines:
+    env.Append(
+        CPPDEFINES=[
+            ("__FREERTOS", 1)
+        ]
+    )
+
+
 env.Append(
     ASFLAGS=env.get("CCFLAGS", [])[:],
 )

If you can't get an actual verbose build log w/timestamps then maybe you re-run on your suspect machine the 4.7.1:

   framework-arduinopico@https://github.com/earlephilhower/arduino-pico.git#4.7.1

Actually, getting verbose build logs w/timestamps for both would probably be needed.

[earlephilhower]

One other thing, maybe P.IO is flubbing the depends because FreeRTOS is now a part of the core (but #ifdef'd out in normal mode. You could try something like they describe in https://docs.platformio.org/en/latest/librarymanager/ldf.html

[env:myenv]
lib_ldf_mode = chain+

The chain+ looks to evaluate C defines so should block parsing any FreeRTOS files. However, FreeRTOS sources are only ~10 plain .C files, so I can't see how they'd have any material impact, either.

[sstaub]

lib_ldf_mode = chain+ doesn't change the problem. I made also an issue on maxgerhardt/platform-raspberrypi#109

[sstaub]

Ok, this was a problem of @maxgerhardt platform build.

[maxgerhardt]

I'm still very much interested in how the commands

<compiler triple>-objdump -d firmware.elf > firmware.lst
<compiler triple>-objdump -d -S firmware.elf > firmware.debug.lst

can take 40 seconds with an average Arduino-Pico firmware. I have felt no slowdown when I built some test firmwares on Windows. Is the disassembler this slow? Is the redirection into a file with shell commands the problem? So many questions.

[earlephilhower]

Under Ubuntu22.04 Linux I just ran it and it was < 1 second with WiFi and FreeRTOS tasks (I'm porting AsyncTCP):

earle@amd:~$ time ~/Arduino/hardware/pico/rp2040/system/arm-none-eabi/bin/arm-none-eabi-objdump -d  /tmp/arduino_build_34345/AsyncTCPClient.ino.elf > out.lst

real	0m0.149s
user	0m0.129s
sys	0m0.011s
earle@amd:~$ wc -l  out.lst 
68664 out.lst

[sstaub]

@maxgerhardt maybe this macOS specific. 40s with an M4Pro 14-core is ugly.