Add MCUDev DevEBox and WeAct MiniSTM32H7 to README#142
Open
AlyoshaVasilieva wants to merge 1 commit into
Open
Conversation
Member
|
Reopened after it was closed by an errant bors |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the MCUDev DevEBox and WeAct MiniSTM32H7 to the readme, relatively cheap development boards.
I've done the basic blinky test for both of these boards. In the case of the DevEBox, I tested the STM32H743VIT6 version.
I'd prefer to link to a documentation source for the DevEBox, rather than their Taobao store, but I cannot find any site they run other than their store. There's a MicroPython board definition repo by mcauser that documents some aspects of the board.
I didn't add it to the readme but the WeAct board has read-out protection enabled and I had to manually issue a mass erase command to be able to connect to it. STM32CubeProg's read unprotect command just disconnected the board from USB with no other effect.