Author Topic: Did I break my stm32f103?  (Read 1385 times)

0 Members and 1 Guest are viewing this topic.

Offline mrburnzieTopic starter

  • Regular Contributor
  • *
  • Posts: 136
  • Country: cs
Did I break my stm32f103?
« on: February 24, 2017, 09:33:33 pm »
Hello!

I'm new to the stm32 world and I've chosen the stm32f103 blue pill... at first everything was working I was using uart programming setting the BOOT0 to 1 and BOOT1 to 0 and using stm32flash (on linux) to flash the code and everything worked...
But suddenly the writing was really, really slow and going up to 56% and stopping... I think it's because I've somehow erased the bootloader? I admit I was changing the jumpers a bit...

Any suggestions on fixing?

Thanks!
« Last Edit: February 24, 2017, 09:40:46 pm by mrburnzie »
"Talk is cheap, show me the code"

Anyone need of freelance software/hardware developer, hit me up!
 

Offline mrburnzieTopic starter

  • Regular Contributor
  • *
  • Posts: 136
  • Country: cs
Re: Did I break my stm32f103?
« Reply #1 on: February 24, 2017, 09:56:21 pm »
The problem was that I wasn't flashing .bin I was flashing .elf files... my apologies  |O |O :popcorn: :popcorn: :-+
"Talk is cheap, show me the code"

Anyone need of freelance software/hardware developer, hit me up!
 

Offline AndyC_772

  • Super Contributor
  • ***
  • Posts: 4228
  • Country: gb
  • Professional design engineer
    • Cawte Engineering | Reliable Electronics
Re: Did I break my stm32f103?
« Reply #2 on: February 25, 2017, 09:34:24 am »
For what it's worth, I don't think it's physically possible to erase the bootloader. The worst you can do is set the top level of read protection in the option bytes, which is an irreversible operation that disables the debug interface completely. Do that and the chip is scrap.


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf