anton
Member
Hello all.
How do you think, is it worth to add Discovery support in official leaflabs repository?
Marty talked about this, but I'm not so familiar with git to make the correct pull request.
becker, is it possible to write program for Discovery which will be communicate with host computer using SWD interface?
mbolivar
LeafLabs
Hi Anton,
We'd be happy to add Discovery support into libmaple. More users means a more robust library, as far as we're concerned, and we're very glad that you've found libmaple useful enough to take the trouble to port it.
If you want to make it easy on us to get your work merged in, the steps to follow are: (1) start with the current LeafLabs libmaple master branch, then (2) commit your changes on top of it into a separate "Discovery support" branch, (3) push that branch to your GitHub libmaple repo, and (4) send us a pull request.
I imagine you've probably got a 'leaflabs' remote in your local libmaple clone that points to the LeafLabs libmaple repo on GitHub. If so, then you can follow this recipe:
First, make sure you're up to date with our master branch:
$ git fetch leaflabs
Next, create a branch called "discovery-support" where you'll put your changes, starting from the current LeafLabs master:
$ git checkout -b discovery-support leaflabs/master
At this point, your current branch should be discovery-support. You can now add your commits however you like, possibly using rebase or cherry-pick.
Please sign your commits with a developer certificate of origin. I believe you're already familiar with this from your last pull request, but just in case, this just means adding the line "Signed-off-by: Your Full Name <your-email@example.com>" at the end of your commit messages. (We've started doing this for non-LeafLabs staff commits into the libmaple core. It's important to do so because it leaves a "paper trail" which helps us ensure that libmaple stays open source).
Once you're done, push your work into your libmaple fork on GitHub:
$ git push origin discovery-support
At that point, you can send us a pull request and we can get things merged in.
mbolivar
LeafLabs
about rebasing: first, do
$ git rebase -i leaflabs/master
in order to rebase the current commits starting just after our master branch, and up to your current commit.
as you noticed, that will open an editor with the commits one per line, with like this:
pick 2dfsdf3g Some commit message
pick 03249gfa Another commit message
...
where the random strings are the hashes for that commit
to change the commit message for a commit, just change the "pick" on its line to "r" (for "reword"), save, and exit your editor. git will then pop up an editor window for each commit message you need to reword, in order, starting from the oldest. edit each one as desired and close the relevant editor window. when it's all done, you can use
$ git log
to make sure the commit messages are what you want.
anton
Member
Discovery can send data via USB. Speed from 5 bit/s.
https://github.com/anton19286/libmaple/blob/discovery/swd_serial_example.cpp
https://github.com/anton19286/libmaple/blob/discovery/readSWD.exe
With Linux and modified Becker's code it is possible to speed up by several orders.
anton
Member
New version based on Becker's stlink-download works slightly faster.
https://github.com/anton19286/libmaple/blob/discovery/SerialSWD.c
https://github.com/anton19286/libmaple/blob/discovery/swd_serial.cpp
I tested under windows, but linux version should also work.
I'm going on vacation. Can somebody with with better programming skills add receiving data and buffering, possibly interrupt-drived?
Is it possible to set interrupt on change of data in memory?
anton
Member
New Discovery board, 32 MHz, low power, breadbordable, with LCD and funny slider.
http://www.st.com/internet/evalboard/product/250990.jsp
Somebody tried it?
becker
Member
I have one, and updated my stlink-download utility to support the STLink V2 interface.
I now have two versions of the utility. One works with V1 (as on the STM32VLDiscovery) and requires no additional libraries, but the SCSI-generic interface means it won't work with Apple. The second version works with V2 ('L' and 'F4' Discovery) boards, using the libusb-1.0 library. In exchange for dealing with the extra library, it works with Apple and (untested) Windows.
anton
Member
Can somebody test https://github.com/anton19286/libmaple/tree/family-discovery with Blink.cpp on the real STM32L Discovery board?
ardweebno
Member
I downloaded your git repository and compiled. Everything went swimmingly until make tried to link the final executable and the linker died with "unknown linker option: -march=arm7-m"
The weird part is that I have no problem compiling ChibiOS and STM32 Discovery examples with the same build environment. For what it is worth, I am using the Summon toolchain.
You must log in to post.
