Problem building STM32 blinky example
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- erlang
- Domain
- embedded-iot
Research direction
Start by comparing the stock AtomVM/build/examples/erlang/stm32/blink_nucleo144.avm with the atomvm_examples/erlang/blinky project built using rebar3, including how the example is packaged with atomvmlib.avm or atomvmlib-stm32.avm. Check the board pins and the reported change to atomvm:platform(); the issue does not identify a specific failure or test. Done means the custom blinky.avm runs on the Nucleo STM32L4R5ZI and blinks the intended LEDs.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Erlang
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomvm/AtomVM
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
lwIP sockets: a failed listen or connect leaves the socket lock held, a later close hangs foreverOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 3 days
Similar issues
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
[Bug]: RFENCE rejects the architecturally defined full-range size when start_addr is nonzeroPossibly taken @hongwei-2026 claimed this today. OpenC-bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rustsbi/rustsbi#484 · 1 comment ·
Maintainers usually reply within 1 day
-
Fan percentage in Auto mode shows the night-mode speed cap (`nmdv`) while the fan is idle (`fnst: OFF`)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cmgrayb/hass-dyson#552 ·
Maintainers usually reply within 1 day
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2664 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
seven-lynx/HoundMind#108 ·
Maintainers usually reply within 1 day