http://forums.leaflabs.com/topic.php?id=105 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:20:28 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=105#post-5323 Fri, 17 Jun 2011 13:38:22 +0000 khushu11 5323@http://forums.leaflabs.com/ <p>Thank you Mbolivar! I'll go deeper inside and keep posting my problems!! :-) </p> http://forums.leaflabs.com/topic.php?id=105#post-5305 Fri, 17 Jun 2011 11:37:13 +0000 mbolivar 5305@http://forums.leaflabs.com/ <p>besides the official libmaple docs, the file notes/portable.txt in the libmaple repo (which i linked to in the other thread you're asking this sort of question on) is a quick rundown on things you need to do.</p> <p>specifically regarding the clock, you can start here with the PCLK1 and PCLK2 (although this version didn't get pushed until after 0.0.11, so you'll need to use the top of the tree):</p> <p><a href="https://github.com/leaflabs/libmaple/blob/master/libmaple/stm32.h" rel="nofollow">https://github.com/leaflabs/libmaple/blob/master/libmaple/stm32.h</a></p> <p>however, the rest of the code doesn't really respect that yet, so you'll run into some other problems as you go along. e.g., libmaple/delay.h will need to change, and there's some HardwareSPI code to adjust.</p> <p>also see the CYCLES_PER_MICROSECOND board-specific value e.g. in wirish/boards/maple.h.</p> <p>any patches that help libmaple work on more chips/board configurations are very welcome. we really want to see it in widespread use; more users means more bug reports, patches, and feedback, which translates to a stronger library overall. and of course, if you give your code back to us, we'll be able to maintain it as libmaple evolves, which is a win for you.</p> <p>you may want to check out anton's discovery libmaple fork on github as a starting point:</p> <p><a href="https://github.com/anton19286/libmaple" rel="nofollow">https://github.com/anton19286/libmaple</a></p> <p>p.s., anton, if you're still on the forums, you should send us some pull requests ;).</p> <p>here are some tips on preparing patches for maximum likelihood of getting pulled in:</p> <p><a href="http://leaflabs.com/docs/libmaple/contributing.html" rel="nofollow">http://leaflabs.com/docs/libmaple/contributing.html</a> </p> http://forums.leaflabs.com/topic.php?id=105#post-5282 Thu, 16 Jun 2011 18:54:45 +0000 khushu11 5282@http://forums.leaflabs.com/ <p>Hello Bnewbold,</p> <p>While Adding a new board, I was wondering where to change the clock settings as I have an external 12Mhz clock on my stm32f103RE board. </p> <p>And also what other things and settings do I have to change to make it work for my board.</p> <p>Any directions would be great help.<br /> Thank you </p> http://forums.leaflabs.com/topic.php?id=105#post-599 Thu, 22 Jul 2010 11:01:20 +0000 bnewbold 599@http://forums.leaflabs.com/ <p>It would work roughly the same way as adding boards to the Arduino IDE: you edit the ./hardware/leaflabs/boards.txt file (or add a new ./hardware/gbulmer/ directory) with the parameters set appropriately. Then you copy any changes to libmaple into a cores/maple-custom directory. I haven't tried all this since modifying the IDE from 0018, but if you run into trouble we'll try to fix it for you.</p> <p>Currently making the changes to libmaple wouldn't be too much of a hassle if you're willing to fork; I think everything you would need is in ./wirish/wirish_digital.c. But perry is working on refactoring things to be compatible with the maple mini and maple native. After that it may be easier </p> <p>You also might want to look in to the alternate function remapping feature of the STM32 which in some cases allows hardware pins to be swapped around in software; see the stm32 reference manual. </p> http://forums.leaflabs.com/topic.php?id=105#post-597 Wed, 21 Jul 2010 17:52:58 +0000 gbulmer 597@http://forums.leaflabs.com/ <p>I am thinking of adjusting the circuit schematic and board layout slightly because I'd like to change a few of the committed pins. I.e. exchange some pins on EXT for committed pins.</p> <p>So I think it may be as simple as a few constants which need changing in a header or two.</p> <p>Can you point me at some notes, or documentation on a reasonable way to go about creating a new type of board, with a minimal set of changes to headers, so that I can use the Maple IDE?</p> <p>Ideally, the user would just select a different board, and everything would 'just work' (TM).</p> <p>TIA - GB </p>