after do this
git clone https://github.com/GUVWAF/Meshtastic-device.git
cd Meshtastic-device
git checkout LoRa-e5
Can you open the FOLDER and see if compile in your machine ?
after do this
git clone https://github.com/GUVWAF/Meshtastic-device.git
cd Meshtastic-device
git checkout LoRa-e5
Can you open the FOLDER and see if compile in your machine ?
Meshtastic-device>pio run
Error: Invalid environment name 'heltec-v2.0'. The name can contain alphanumeric, underscore, and hyphen characters (a-z, 0-9, -, _)
yes, this one of problems…
Even after fixing the environment names, the WIO E5 environment (which is seemingly the point of that branch judging by the name) is uncompilable – it directly references the master
branch of https://github.com/stm32duino/Arduino_Core_STM32/
, so no wonder, the core has evolved since then and the original version / commit wasn’t fixed in place.
But is there a reason you can’t use the master branch of the repo with the WIO E5 envionrment?
the problem is this a modification of the MASTER, wich use the LITTLEFS lib, that is not working specifically on STM32WL55 (WIO E5) on master
All Meshtastic parameter are stored in FS
Then the GUVWAF created this repository that use static parameters…not the LITTLEFS, to test the Meshtastic…
He said that compiles…but need to use older Platformio Core
He said
“You’re using version 3.2.0 of PlatformIO, but the firmware I linked was build using version <3.0.0.”
" You need to downgrade the PlatformIO core to version 6.1.6 or lower. Probably usingpip uninstall platformio
and thenpip install platformio==6.1.6
."
Can you see that ? when have time!
The firmware is buildable with the latest PlatformIO core 6.1.8a1. I just massaged the platformio.ini to use the older STM32 core version, the defines and a library dependency finder mode and it compiles the wio-e5 environment fine.
That’s confirmed by CI too.
Linking .pio/build/wio-e5/firmware.elf
Checking size .pio/build/wio-e5/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [==== ] 35.4% (used 23188 bytes from 65536 bytes)
Flash: [====== ] 62.6% (used 164132 bytes from 262144 bytes)
Building .pio/build/wio-e5/firmware.bin
======================== [SUCCESS] Took 108.54 seconds ========================
@maxgerhardt
Thank you so much!!
Archiving .pio\build\wio-e5\libFrameworkArduino.a
Indexing .pio\build\wio-e5\libFrameworkArduino.a
Linking .pio\build\wio-e5\firmware.elf
Checking size .pio\build\wio-e5\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [====== ] 60.9% (used 39880 bytes from 65536 bytes)
Flash: [======== ] 83.5% (used 218764 bytes from 262144 bytes)
Building .pio\build\wio-e5\firmware.bin
=================================================================== [SUCCESS] Took 152.79 seconds ===================================================================
Environment Status Duration
------------- -------- ------------
wio-e5 SUCCESS 00:02:32.795
==================================================================== 1 succeeded in 00:02:32.795 ==================================================================== * Terminal will be reused by tasks, press any key to close it.
Is this the meshtastic source
the same modified version of GUVWAF to not use FS, right ?
Only modified absolutely minimally what’s shown here, nothing to do with FS: Comparing GUVWAF:LoRa-e5...maxgerhardt:LoRa-e5 · GUVWAF/Meshtastic-device · GitHub
Also there was a commit on the original https://github.com/GUVWAF/Meshtastic-device/tree/LoRa-e5 making it compilable again.
Yes, i see! Thanks again