<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>LeafLabs Garden &#187; Topic: Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?</title>
		<link>http://forums.leaflabs.com/topic.php?id=103</link>
		<description>A place to share, learn, and grow...</description>
		<language>en-US</language>
		<pubDate>Fri, 22 Jan 2016 00:14:44 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://forums.leaflabs.com/search.php</link>
		</textInput>
		<atom:link href="http://forums.leaflabs.com/rss.php?topic=103" rel="self" type="application/rss+xml" />

		<item>
			<title>gbulmer on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-935</link>
			<pubDate>Wed, 01 Sep 2010 13:57:10 +0000</pubDate>
			<dc:creator>gbulmer</dc:creator>
			<guid isPermaLink="false">935@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Poslathian, just to clarify for folks.&#60;br /&#62;
Members of the STM32F101, STM32F103, STM32F105 and STM32F107 family, which come in LQFP100 and LQFP144 packages have analogue reference Vref+ and Vref-. (I haven't looked at the STM32W or STM32L to have noticed).&#60;/p&#62;
&#60;p&#62;Also, STM32F103's in a TFBGA64 (same number of pins as the Maple's LQFP64) has an analogue Vref+, but no Vref-. The TFBGA64 version loses PC3. I have no idea why they did that; it's weird to me.&#60;/p&#62;
&#60;p&#62;One key thing about adding the d14 to the Maple header is the Arduino analog pin 0 is aleady aliased to digital pin number 14 in the Arduino libraries. This might make sharing some libraries slightly more complex.&#60;/p&#62;
&#60;p&#62;It's done now - ship it :-)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>poslathian on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-932</link>
			<pubDate>Wed, 01 Sep 2010 13:10:43 +0000</pubDate>
			<dc:creator>poslathian</dc:creator>
			<guid isPermaLink="false">932@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;the issue with d14 is that the rbt6 doesnt have an aref pin. While the analog supply, vdda, is separate, its nominally 3.3v, and that feature just doesnt exist on that chip. We figured we might as well not waste a perfectly good gpio, I suppose we could have left the trace unconnected. Incidentally, some of the larger stm32's do have an aref, including, I believer, the Maple Native.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>leaflabsandy on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-929</link>
			<pubDate>Wed, 01 Sep 2010 10:50:55 +0000</pubDate>
			<dc:creator>leaflabsandy</dc:creator>
			<guid isPermaLink="false">929@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Quote: &#34;As a medium time Arduino user, and someone who has built hardware based on Arduino, I have NEVER used D0 in a sketch/program.&#34;&#60;/p&#62;
&#60;p&#62;Reply: I don't either - what I tried to convey that the Pin # is a digital bit and&#60;br /&#62;
if ref. to D0-D13.(sorry about using D14 - the Maple has this) unless used as an analog.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gbulmer on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-927</link>
			<pubDate>Wed, 01 Sep 2010 10:03:45 +0000</pubDate>
			<dc:creator>gbulmer</dc:creator>
			<guid isPermaLink="false">927@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;As a medium time Arduino user, and someone who has built hardware based on Arduino, I have &#60;em&#62;NEVER&#60;/em&#62; used D0 in a sketch/program.&#60;/p&#62;
&#60;p&#62;It doesn't compile in the Arduino IDE. The error is, e.g.&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;error: 'D0' was not declared in this scope
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;I can't remember ever seeing any sketches that used that notation, though I haven't read all the examples. To use it, it would have to be #defined as declared somewhere, and I think I'd have noticed that.&#60;br /&#62;
mbed does it that way. Maybe you're thinking of that?&#60;/p&#62;
&#60;p&#62;Which pin '0' refers to is usually pretty clear from context, e.g. it's used in a 'digital' or 'analog' I/O library call.&#60;/p&#62;
&#60;p&#62;The silkscreen on my Arduino Diecimilia numbers the digital pins from 0 to 13.&#60;br /&#62;
There is no digital 14 (I was surprised when Maple added it, as that is incompatible with Arduino).&#60;br /&#62;
The other two pins on the two 8 pin digital I/O headers is GND and AREF.&#60;br /&#62;
In the Arduino library and headers, analogue pin 0 is aliased as digital pin 14, upto analogue pin 5, which is aliased as digital pin 19.&#60;/p&#62;
&#60;p&#62;HTH
&#60;/p&#62;</description>
		</item>
		<item>
			<title>x893 on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-910</link>
			<pubDate>Mon, 30 Aug 2010 20:20:00 +0000</pubDate>
			<dc:creator>x893</dc:creator>
			<guid isPermaLink="false">910@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Where i can find change log (for example r5 with rev3) ?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>okie on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-908</link>
			<pubDate>Mon, 30 Aug 2010 18:58:45 +0000</pubDate>
			<dc:creator>okie</dc:creator>
			<guid isPermaLink="false">908@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Maple r5 design files have been pushed:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://github.com/leaflabs/hardware&#34; rel=&#34;nofollow&#34;&#62;http://github.com/leaflabs/hardware&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>leaflabsandy on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=5#post-906</link>
			<pubDate>Mon, 30 Aug 2010 17:25:44 +0000</pubDate>
			<dc:creator>leaflabsandy</dc:creator>
			<guid isPermaLink="false">906@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Being a hardcore Arduino user and the Maple is an Arduino compatible in form and&#60;br /&#62;
commands/functions.&#60;/p&#62;
&#60;p&#62;D represents digital - so when an Arduino user programs a sketch he knows that pin #&#60;br /&#62;
&#34;0&#34; (not microcontroller pin #) is the same as &#34;D0&#34; in his program code.&#60;br /&#62;
The silkscreen on the Arduino is 0-14 for digital and 0-6 for analog.&#60;br /&#62;
Note: The analog is a subset of the digital I/O.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>poslathian on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-905</link>
			<pubDate>Mon, 30 Aug 2010 17:19:18 +0000</pubDate>
			<dc:creator>poslathian</dc:creator>
			<guid isPermaLink="false">905@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;to use llandy's forum conventions:&#60;/p&#62;
&#60;p&#62;Quote: Put yourself into a hardware developer's shoes. It is extremely expensive&#60;br /&#62;
to design multiple shields for Maple rev3, Maple rev5 and maybe Maple rev6!&#60;/p&#62;
&#60;p&#62;Reply: &#34;- the header location issue, as had been pointed out, has to be locked down so that people can build off of it with confidence. That is now the case. &#34; - However minor improvements like silk changes, adjustments to the power supply/selection/regulator circuit, non-functional component changes (cap values, rvalues etc), are all fair game in my opnion, and we will continue to improve these minor aspects to the best of our ability.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gbulmer on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-904</link>
			<pubDate>Mon, 30 Aug 2010 17:07:13 +0000</pubDate>
			<dc:creator>gbulmer</dc:creator>
			<guid isPermaLink="false">904@http://forums.leaflabs.com/</guid>
			<description>&#60;blockquote&#62;&#60;p&#62;Sorry all, the BUT did not make it out to a header...we all agreed it was more important to have a GND pin on the header...as in, every header gets a ground.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;I agree with that philosophy too. It would have been good to have the buttons on headers, but I've had a similar problem; too many useful signals, and not enough pins :-)&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;I cant speak for the RTC stuff since I havnt looked in to it that much. For now I'll say....hmmmm...interesting.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;Yes, it would have been nice to have the RTC crystal oscillator pins tracked together to a common place, but I agree ...&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;... - the header location issue, as had been pointed out, has to be locked down so that people can build off of it with confidence. That is now the case.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;It's done now - ship it.&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;The confusion about the pc9/d38 issue i think is a conventions problem. I kept saying &#34;pin 38&#34; but what i meant was d38. d38 is not a pin on Maple, it is a pin on the stm32, it is the reference number in the wirish library. So from now on, when referencing software-accessible pins we should say &#34;d#&#34; as in &#34;d1,d2,d3&#34; etc. And if you mean the physical pin, you mean pin 1, pin 2...etc.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;I think there is still some ambiguity.&#60;br /&#62;
The d# is a high-level Maple library view of the STM32F, created in the Maple headers/library.&#60;br /&#62;
Using the d# for software accessible pins is simple and clear.&#60;/p&#62;
&#60;p&#62;I was using &#34;P$4&#34; to mean the pin number on the STM32F103R 64-pin LQFP package, which corresponds with the Eagle CAD.&#60;br /&#62;
As an example d36 = P$38.&#60;br /&#62;
Then, if I've understood, d38 = P$40.&#60;/p&#62;
&#60;p&#62;Physical pins (on headers) are unambiguous as they use the Maple library names, but just don't go as high, so ditching the 'd' is okay.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>leaflabsandy on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-903</link>
			<pubDate>Mon, 30 Aug 2010 16:45:35 +0000</pubDate>
			<dc:creator>leaflabsandy</dc:creator>
			<guid isPermaLink="false">903@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Quote: &#34;Probably in mid october well be doing this all over again for Rev6!&#34;&#60;/p&#62;
&#60;p&#62;Reply: Put yourself into a hardware developer's shoes. It is extremely expensive&#60;br /&#62;
to design multiple shields for Maple rev3, Maple rev5 and maybe Maple rev6!&#60;/p&#62;
&#60;p&#62;I sure hope, if a user buys a Maple rev3 and two years from now he needs the&#60;br /&#62;
&#34;same&#34; Maple rev3 instead of the latest and greatest updated, newer, version that&#60;br /&#62;
he is able to purchase the same one! Please don't say &#34;we no longer make that version!&#34;&#60;/p&#62;
&#60;p&#62;In printed circuit board design attention to details is very important. Being on grid, stacking design, current limiting, component availability / second sourcing are just a few of the many items that a PCB designer needs to be aware of to create a stable design.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>okie on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-898</link>
			<pubDate>Mon, 30 Aug 2010 13:36:40 +0000</pubDate>
			<dc:creator>okie</dc:creator>
			<guid isPermaLink="false">898@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;it goes:&#60;br /&#62;
reset,Vcc/3.3,Vdda/3.3,GND,GND,Vin
&#60;/p&#62;</description>
		</item>
		<item>
			<title>leaflabsandy on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-896</link>
			<pubDate>Mon, 30 Aug 2010 13:34:12 +0000</pubDate>
			<dc:creator>leaflabsandy</dc:creator>
			<guid isPermaLink="false">896@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Quote: &#34;Additionally, the second VCC pin on the bottom left header has been replaced with VDDA, the analog voltage.&#34;&#60;/p&#62;
&#60;p&#62;Reply: From the reset pin on the six pin header ... reset,Vcc/3.3,Vcc/3.3,GND,GND,Vin.&#60;br /&#62;
What position, on this header, did you place the VDDA from the reset?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>poslathian on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-893</link>
			<pubDate>Mon, 30 Aug 2010 12:09:36 +0000</pubDate>
			<dc:creator>poslathian</dc:creator>
			<guid isPermaLink="false">893@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;will link to the schematics once we push to git. I think theyre already in the svn (which is officially deprecated by the way). Sorry all, the BUT did not make it out to a header...we all agreed it was more important to have a GND pin on the header...as in, every header gets a ground. &#60;/p&#62;
&#60;p&#62;I cant speak for the RTC stuff since I havnt looked in to it that much. For now I'll say....hmmmm...interesting. &#60;/p&#62;
&#60;p&#62;Thats it for Rev5 though, there were a lot of subtle changes we wanted to make but didnt for timing reasons (there will be an inventory gap at this point. Maybe some distributors still have some stock...) Probably in mid october well be doing this all over again for Rev6!&#60;/p&#62;
&#60;p&#62;BUT - the header location issue, as had been pointed out, has to be locked down so that people can build off of it with confidence. That is now the case. The 21/22 pins that were moved off the header are conveniently positioned on the 1/10&#34; grid. Also a great many thoughtful silk changes were pushed. &#60;/p&#62;
&#60;p&#62;The confusion about the pc9/d38 issue i think is a conventions problem. I kept saying &#34;pin 38&#34; but what i meant was d38. d38 is not a pin on Maple, it is a pin on the stm32, it is the reference number in the wirish library. So from now on, when referencing software-accessible pins we should say &#34;d#&#34; as in &#34;d1,d2,d3&#34; etc. And if you mean the physical pin, you mean pin 1, pin 2...etc. Incidentally, the only discrepancy between these two is d38. There is no pin 38. &#60;/p&#62;
&#60;p&#62;Of course, libmaple is completely agnostic of this 1-38 numbering scheme, which is invented inside of wiring. The real pin numbers are the PXX (as in PC9, PB8, ...). This gets a little messy around the JTAG pins, which happen to be GPIO's also. And the numbers, internally, go up to 42 or something...but that port isnt really intended to be used for anything but jtag. And its intentionally not documented that those pins can be GPIO. For the record, the JTAG port since on the 1/20&#34; grid...
&#60;/p&#62;</description>
		</item>
		<item>
			<title>gbulmer on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-892</link>
			<pubDate>Mon, 30 Aug 2010 11:57:03 +0000</pubDate>
			<dc:creator>gbulmer</dc:creator>
			<guid isPermaLink="false">892@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;Okie&#60;/p&#62;
&#60;blockquote&#62;&#60;p&#62;These are the last changes we'll be able to make on Maple r5. I could not find a clear, easy enough way to route BOOT0 or PC9 to a 0.1&#34; spaced header location.
&#60;/p&#62;&#60;/blockquote&#62;
&#60;p&#62;IMHO, it would have been better to take both RTC oscillator pins (22 and 23, i.e. P$3, PC14/OSC32_IN, and P$4, PC15/OSC32_OUT) off the EXT header, rather than pins 21 and 22 (P$2, PC13/TAMPER-RTC and P$3, PC14/OSC32_IN). That is the way I have gone.&#60;/p&#62;
&#60;p&#62;But, to me, getting back to 0.1&#34; grid is more important. So I am happier with the changes than without.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>leaflabsandy on "Source/Vendor/Part # of Maple &#34;External&#34; 18 pin 10.5 mm female stacking header?"</title>
			<link>http://forums.leaflabs.com/topic.php?id=103&amp;page=4#post-887</link>
			<pubDate>Mon, 30 Aug 2010 06:54:16 +0000</pubDate>
			<dc:creator>leaflabsandy</dc:creator>
			<guid isPermaLink="false">887@http://forums.leaflabs.com/</guid>
			<description>&#60;p&#62;As for the current limit resistors the &#34;BUT&#34; needs it because a user could change the&#60;br /&#62;
I/O direction from input to output (LOW) and zap the tac and I/O. The reset is always&#60;br /&#62;
an input but stacking shields you might need some current protection - be very careful&#60;br /&#62;
on the mods for this pin.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
