Open avaldebe opened 5 years ago
I have the same problem. In fact the maple core seems to be completely broken, nothing compiled using it will work on the STM32F103C8T6. It will just lock up and do nothing.
By contrast, using the maple core (rogerclarkmelbourne repository) in the Arduino IDE works flawlessly with the same examples I tried, so the problem seems to be with Platform.io or our config (my ini looks the same as above).
I suspect this was a mistake on our part. I was able to reproduce this just now with the below platformio.ini
and code. I then changed the board type to genericSTM32F103C8
(which also allows for board_build.core = maple
to be removed), and it's working fine.
Since the rogerclarkmelbourne/Arduino_STM32 (maple core) doesn't actually mention the blue pill in the boards.txt (and does have Generic STM32F103C series
), but the stm32duino/Arduino_Core_STM32 does... I think we've been specifying the wrong board. This also makes sense given the default cores used. 🤦♂ 🤐
[env:STM32]
platform = ststm32
board = bluepill_f103c8
board_build.core = maple
framework = arduino
upload_protocol = stlink
debug_tool = stlink
#include <Arduino.h>
void setup()
{
pinMode(PC13 ,OUTPUT);
}
void loop()
{
digitalWrite(PC13 ,HIGH);
delay(500);
digitalWrite(PC13 ,LOW);
delay(500);
}
What I am finding is that if I have only:
[env:STM32] platform = ststm32 board = genericSTM32F103C8 framework = arduino
This builds by default with the maple core...
and if I specify anything other than maple for board type it will default to the stm32duino/Arduino_Core_STM32 as shown below.
[env:STM32] platform = ststm32 board = genericSTM32F103C8 framework = arduino board_build.core = bla
and if I specify anything other than maple for board type
To be expected... since the test is only checking if maple is specified, else use the stm32duino core
However, the essence of this issue seems to be based on having used the wrong board definition, hence my comments above.
That makes sense... just wanted to clarify that for the generic board definition that maple core appears to be the default.
Is there any fix for this yet? I can't use Maple on bluepill at all, it compiles and upload but does nothing
Does it work with the platform.ini and code sample from my earlier comment?
https://github.com/platformio/platform-ststm32/issues/231#issuecomment-599163921
On Wed, 16 Sep 2020, 1:30 am matias-levy, notifications@github.com wrote:
Is there any fix for this yet? I can't use Maple on bluepill at all, it compiles and upload but does nothing
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/platformio/platform-ststm32/issues/231#issuecomment-692794150, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ66KJPFCS5RLAFTODXMK3SF6CBNANCNFSM4HCP6F2A .
Does it work with the platform.ini and code sample from my earlier comment? #231 (comment) … On Wed, 16 Sep 2020, 1:30 am matias-levy, @.***> wrote: Is there any fix for this yet? I can't use Maple on bluepill at all, it compiles and upload but does nothing — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#231 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ66KJPFCS5RLAFTODXMK3SF6CBNANCNFSM4HCP6F2A .
No, I am out of ideas. This works on the Arduino IDE
The blink example will work fine for the default stm32duino core, but it does nothing for the maple code.
Here is my config:
EDIT: After updating the ST STM32 platform to 5.3.0, I do no longer need to define
LED_BUILTIN
on the default core. The maple core will not compile without it, so I guess that #216 only addressed the default core.