Program successfully flashes but isn't running on the Microcontroller

[complexmuhm]

I have built and flashed the example blue pill blink program on my stm32f103c8t6 and the LED won't blink. I have made sure that the microcontroller isn't dead by manually compiling, linking and flashing my own program through gnu arm. And it works. I can not get the modm blink example to work. I have tried this with a fake blue pill too. Same result: it successfully gets flashed but the code is not running.

I am using the STLINK V2 USB Programmer through SWD.v

[salkinium]

Does it start working if you power cycle the blue pill board without the SWD debugger attached?

[complexmuhm]

No nothing.

[rleh]

Sound to me like a BOOT0/BOOT1 pin problem:

(from STM32F103 Reference Manual RM0008)

[rleh]

OpenOCD writes your program to the main flash memory, so you have to connect the BOOT0 pin to GND (logic 0).

[complexmuhm]

I have already accounted for this. I am currently in Boot mode "Main Flash memory".

[complexmuhm]

As I said: If I compile my code only using CMSIS library with gnu arm embedded toolchain and flash it, it works. But using modm and "scons program" the compiled blink program suddenly won't work.

[rleh]

modm's blue-pill blink example toggles gpio pin PC13, are you toggling the same pin in your other program?
There might be "Blue-Pill" boards with the LED connected to another pin...

Do you have any other dev board (which is supported by modm) available to test another blink example?

[salkinium]

I can think of two more things:

1. Board::initialize() enables the external crystal to use for clock. It may be broken, you can test this by commenting out the line in the modm example.
2. What toolchain are you using? Are you using the toolchain from ARM, or the compiler from your distribution?

[salkinium]

Oh, and you can scons debug and single step through the code to find what actually happens. In GDB you can type restart to reset to the reset handler, then si, ni to single step around.

[complexmuhm]

thanks for the suggestion. I tried to manually step through it and also removing the Board::initialize(). Here is a screenshot:

While stepping and waiting after Led::set and Led::reset I couldn't see the LED blink. The program is being run, according to the debugging. I am not sure if it is addressing wrong addresses... (*as in addressing the wrong gpio addresses)

[complexmuhm]

And it also looks like, that the program gets stuck in modm::delay_us

[complexmuhm]

2. What toolchain are you using? Are you using the [toolchain from ARM](https://developer.arm.com/Tools%20and%20Software/GNU%20Toolchain), or the compiler from your distribution?

I am using the ARM GNU Toolchain, I have setup a basic project using the minimal example folder and have modified the linker script, the startup asm file and some linker flags. Here is the console output for compiling and flashing:

[complexmuhm]

Okay update: instead of using the blue pill example folder I have created my own folder and setup the project myself. It seems that it is working now.

[salkinium]

Hm, that's interesting and weird. But glad it's now working for you. If you find out why that happens (perhaps a path issue?), let us know.
I also cannot reproduce this behavior with the three blue pills that I have lying around.

[complexmuhm]

Definitely weird. I have no clue why this is happening. This is perhaps the only difference between those two projects the project.xml (left the one not working, right the one working):

[rleh]

I also just checked the example on one of my Blue-Pill boards and it worked perfectly.