Problem building STM32 blinky example

[brucebiotech]

Hi,

I am new to AtomVM and am trying to build and run the stm32 nucleo144 example. I am using erlang otp v 28, the atomvm main branch and a Nucleo stm32l4r5zi board.

After building and flashing the stm32 atomvm, I flash the example AtomVM/build/examples/erlang/stm32/blink_nucleo144.avm. This loads and I get three flashing LEDs.

I then copied the erlang code from the above example to atomvm_examples/erlang/blinky example and built blinky.avm using rebar3 (the pins in the stock example are wrong for my board and I suspect the main branch has changed the return value from atomvm:platform()).

With this build setup I get a blinky.avm but loading this does not blink any LEDs. I have tried using atomvmlib.avm or atomvmlib-stm32.avm with pack-beam but neither work. Other than that I have no more ideas on what to try next

Any pointers on what I am missing would be appreciated.

[pguyot]

Hello,

Would you mind pasting the modified blinky.erl you used? The example uses {b, 0} on STM32, but on your board, LEDs are {b, 7}, {b, 14} and {c, 7}.

Also, atomvm:platform() stil returns stm32 on stm32 platform, this didn't change.

[brucebiotech]

I did start with the original blinky example only modifying the pin() to be {b, 7} but this did not work.

I then simply copied the contents of blink_nucleo144.erl into the blinky example directory and built using rebar.

In each case I generated a blinky.avm file that is much bigger than the nucleo144 example, arount 118kbytes compared to 3kbytes.

I have setup my build environment, mainly from from source, on a new pc so its a pretry vanilla setup.

[brucebiotech]

I have narrowed the problem to the --prune option in packbeam.

If I build the blinky example using packbeam without --prune it works, 3 leds blinking. But the .avm file is quite big.

If I do the same but include the --prune option it does not work, no LEDs blinking.

[pguyot]

Thank you so much for this. I confirmed yesterday the problem, being able to reproduce it.

[brucebiotech]

It will be good to get this fixed. It spoilt an otherwise very smooth build process for me as a newcommer to the atomvm.

Separately my next problem is my nucleo is an MB1312A which uses the stm32l4's LPUART1 for the st-link VCOM which is not currently a build option. So my next task is adding this to get my atomvm console working.