You could get rid of -Wl,--gc-sections, which might lead to a nonzero file size - it probably still won't work but you might be able to look at the .lst file and get an idea why the entrypoint isn't getting called?
Also can you compile with RELEASE=1 PICO_1V3=1 make and see if that works?
It looks like you're still using Windows as well?
If I were you I'd really just install a VM and use Ubuntu with arm-none-eabi-gcc. Trying to change to do the build under windows as well as porting to a new chip is just asking for trouble.
There are also some webpages on building for EFM32 with Makefiles too - maybe try one of them... Don't use Espruino at all at the moment but just try and get something building with GCC and a Makefile.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
You could get rid of
-Wl,--gc-sections
, which might lead to a nonzero file size - it probably still won't work but you might be able to look at the.lst
file and get an idea why the entrypoint isn't getting called?Also can you compile with
RELEASE=1 PICO_1V3=1 make
and see if that works?It looks like you're still using Windows as well?
If I were you I'd really just install a VM and use Ubuntu with arm-none-eabi-gcc. Trying to change to do the build under windows as well as porting to a new chip is just asking for trouble.
There are also some webpages on building for EFM32 with Makefiles too - maybe try one of them... Don't use Espruino at all at the moment but just try and get something building with GCC and a Makefile.