Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Olimex STM32 H103 board #33

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Olimex STM32 H103 board #33

wants to merge 2 commits into from

Conversation

torfbolt
Copy link
Contributor

Made the changes to JTAG upload a little more generic. At the moment, the Makefile is using the OpenOCD config file for the olimex_stm32_h103 board, as it does not differ from the configuration required by maple. To make this more clean for future versions, maybe you could send a patch to OpenOCD to add a leaflabs_maple.cfg file.
The OpenOCD wrapper scripts should not be needed any more, but please test this. The makefile works for me, but I don't have a Maple board, so I can't do any testing on this.

I also made some small changes to the makefile to make it easier to build an external project against the precompiled libmaple library by just exporting LIB_MAPLE_HOME and modifying the build-targets.mk file.

Pin layout and header files for the STM32 H103 prototype board from
Olimex featuring an STM32F103RBT6 chip. This commit contains all
necessary changes to compile with BOARD=olimex_stm32_h103.

Signed-off-by: David Kiliani <[email protected]>
Replaces the OpenOCD wrapper scripts with a direct call to
OpenOCD using the stock interface and board configuration
scripts.

Signed-off-by: David Kiliani <[email protected]>
@mbolivar
Copy link
Contributor

I've pushed 5d05638 (Add support for the Olimex STM32 H103 board.) into the LeafLabs tree; however, I don't have time to test 163f444 right now, so I won't do that just yet. I'm making changes to the way boards are configured, however, and will try to maintain your board as I go. I may ask you for advice at some point or other.

This brings me to a related question -- are you willing to maintain the board support for this? If so, can we reach you at the email you provided in your signoff with maintainer-related requests?

@torfbolt
Copy link
Contributor Author

This brings me to a related question -- are you willing to maintain the board support for this? If so, can we reach you at the email you provided in your signoff with maintainer-related requests?

Yes, that should be no problem, as I will probably continue using
libmaple on this board for quite some time.

@mbolivar
Copy link
Contributor

Great! That's good news.

@torfbolt
Copy link
Contributor Author

I think this pull request can be closed. All the relevant stuff is in master (I'm using it right now) and the remaining patch is obsolete since I use the patched maple bootloader from my branch
https://github.com/torfbolt/maple-bootloader/tree/olimex_stm32_h103
to upload programs via DFU.

Do you plan on unifying the bootloader code with some BOARD variable, or will it just be separate branches? Should I submit a pull request for my bootloader branch?

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