Skip to content

Conversation

kfoltman
Copy link
Contributor

This is just a stupid bug while refactoring the mass erase code into the generic flash operation code - it's not supposed to initiate mass erase before every flash operation :)

@kfoltman kfoltman changed the title stm32: do not do mass erase on *every* flash operation :) stm32: speed the whole thing up - from 50s to 4s for my current project Jun 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants