SparkFun Electronics Commentsurn:uuid:214d0e4e-f1b1-d287-ce26-ac5b4c9f82492024-03-28T05:44:27-06:00SparkFun Electronicssantaimpersonator on DEV-12774 - SparkFun BeagleBone Black Proto Capesantaimpersonatorurn:uuid:57d4775b-8dea-4936-6c4a-b53208d194e32019-06-19T10:55:08-06:00<p>Unfortunately, I can't post a screenshot of board layout from the Eagle file. However, if you want, the file is available under the <strong>Documents</strong> tab and <a href="https://www.autodesk.com/products/eagle/free-download" rel="nofollow">Eagle does have a free maker license</a> that you can use. Just open the <code>.brd</code> file.<p>Otherwise, the two double-stacks of outlined pins mirror the connections to the Beaglebone. Additionally, the pins outlined by boxes also share a connection (they should be labeled). I hope this information helps. If you have any more technical questions, please use the link in the banner above, to get started with posting a topic in our <a href="https://forum.sparkfun.com/" rel="nofollow">forums</a>. Our technical support team will do their best to assist you.</p></p>
Customer #837796 on DEV-12774 - SparkFun BeagleBone Black Proto CapeCustomer #837796urn:uuid:8b106f4b-709a-f0b4-d606-b2097b5ebe872019-06-18T13:30:02-06:00<p>The central prototyping area (rectangular grid of holes) - are those holes all isolated from each other, or are any connected together? For example, the Schmartboard cape has a diagram showing the holes are connected together in groups of five</p>
Kirk R on DEV-12774 - SparkFun BeagleBone Black Proto CapeKirk Rurn:uuid:1aa9625c-400f-57e8-402c-daf340526e702016-08-05T16:06:05-06:00<p>I believe there are a few small typos on the P9/P8 headers as they relate to the GPIOs.<p>*P9</p><p>PIN 14 -- GPIO_50 (currently marked as GPIO_40. It is port gpio1[18] => 1*32+18 = 50)</p><p>PIN 17 -- GPIO_5 (currently marked as GPIO_4)</p><p>PIN 18 -- GPIO_4 (currently marked as GPIO_5)</p><p>PIN 27-31 -- GPIO all marked in the 12x's, should be 11x's</p><p>These have been verified on the table/datasheet provided by BBB. Although, I have yet to check the software files relate as mentioned above.</p><p>If the schematics are ever revised, or future capes designed it would be great to see this rev'ed! Cheers.</p></p>
Customer #115576 on DEV-12774 - SparkFun BeagleBone Black Proto CapeCustomer #115576urn:uuid:0ea76162-6d7c-ea22-0aad-2d1796e34fab2016-03-14T10:22:51-06:00<p>I don't think the 4k7 sda, scl pull-up resistors meet the bbb system reference manual requirement for 5k6 parts.</p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:8d4350fb-74a5-bf56-ebc0-b7ff83e660be2015-01-28T17:03:49-07:00<p>Ah, I think I understand your question better, you will have a small gap between the board and the BBB connector using the stackable headers. With non stacking headers PRT-12791, the plastic holder takes up the space between the BBB and the bottom of the PCB. I hope this helps!</p>
ZenoTec on DEV-12774 - SparkFun BeagleBone Black Proto CapeZenoTecurn:uuid:dd4f73f5-5d43-1564-b439-b99770b21c762015-01-23T19:09:02-07:00<p>I have a Beaglebone Black RevC from Element14. The headers I'm using are in the stackable 2x23 header found in the "Also Purchased" column to the right. The headers on the board have the same height as the stackable headers. I also tried it on a Rev A and it seems to have the same issue. Should the proto cape be able to sit flat against the header on the Beaglebone without a header soldiered to it? Thanks for looking into this.</p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:58fc97a5-1210-948d-e24d-e501c5780bbb2015-01-23T10:46:58-07:00<p>Interesting, I have one on my desk and it looks just fine. Can you give me more info on the headers and the version of BeagleBone you are using? It's possible that BeagleBone changed connectors on us. I'll see what I can find out. Thanks for bringing this up.</p>
ZenoTec on DEV-12774 - SparkFun BeagleBone Black Proto CapeZenoTecurn:uuid:65f77afa-4ba8-0346-3536-a3a0349c0c462015-01-09T15:00:04-07:00<p>I just picked up a few of these to start doing some prototyping with. The power connector on the BBB seems to be in the way keeping it from seating all the way. It stops about 1/8" short. Is this an intended "feature" or am I missing something?</p>
jbdatko on DEV-12774 - SparkFun BeagleBone Black Proto Capejbdatkourn:uuid:34ca2996-9436-ca52-73f9-1b63d99589002014-12-11T15:58:44-07:00<p>Hey Mark,<p>Casey is spot-on, the BeagleBone reserves those four i2c addresses for cape EEPROMs and it prevents any other kernel module from instantiating at that location. I would always expect to see that result from i2c-detect with or without that proto-cape.</p><p>BTW, there is a <em>very good</em> tutorial on BBB capes <a href="http://papermint-designs.com/community/node/331" rel="nofollow">here</a> and I wrote a <a href="http://datko.net/2013/11/03/bbb_i2c/" rel="nofollow">tutorial</a> on some BBB i2c specific issues.</p></p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:45355139-a07d-342c-a7fd-852955f4cd9c2014-12-11T12:45:03-07:00<p>I believe all the address blocks are blocked out so you don't try to use a device on those. I'll see if Josh will chime in with more info.</p>
Mark A. Yoder on DEV-12774 - SparkFun BeagleBone Black Proto CapeMark A. Yoderurn:uuid:8bfc93a9-d479-185a-fccd-ee006f51bb462014-12-10T13:03:37-07:00<p>I just got a proto cape and have added stackable headers. I plug it into my BeagleBone Black, running the 2014-11-11 image of Debian and run i2cdetect I get:<pre><code>i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</code></pre><p>UU's are showing up where I expect the cape EEPROM to be. But the UU's show up even if the cape isn't attached.</p><p>What should I do?</p><p>--Mark</p></p>
Crizo on DEV-12774 - SparkFun BeagleBone Black Proto CapeCrizourn:uuid:c95b6fdd-e2be-d7bd-3e78-7441e97524dc2014-10-10T11:23:33-06:00<p>If anyone has trouble with the address bits, note that the unsoldered pads represent a 1 in the address table. Soldering them changes them to 0. It makes sense if you look at the default address of 0x57 with no pads jumpered. Normally the eeprom keeps these low, but the proto cape has pullups so they are high by default.</p>
Customer #575274 on DEV-12774 - SparkFun BeagleBone Black Proto CapeCustomer #575274urn:uuid:ecba5452-263a-9f78-d6e5-e9ca3b39b6632014-08-17T00:35:19-06:00<p>One note is that the board is about 1mm too long to fit neatly into the Adafruit BoneBox. Just in the bit with the EEPROM on it.<p>Else excellent product and easy to use.</p></p>
jbdatko on DEV-12774 - SparkFun BeagleBone Black Proto Capejbdatkourn:uuid:3102563b-f18d-c324-1a77-c2986b32e9c12014-08-13T13:25:12-06:00<p>I started making a tutorial for BBB Cape EEPROMs <a href="https://github.com/jbdatko/eeprom_tutorial/blob/master/eeprom.md" rel="nofollow">here</a>. If you can get the May 2014 Issue of <a href="http://www.linuxjournal.com/content/may-2014-issue-linux-journal-cool-projects" rel="nofollow">Linux Journal</a>, I wrote about the device tree in some more depth. I don't think I can release the text to you myself, sorry.<p>Also, the Beagle device tree system has changed a bit. They used to keep stuff in <code>/lib/firmware</code>, which is where I think you can still drop your compiled DTB. The majority of the AM335x device tree, included capes, appears to be folded into a master file, the location of which I am not sure.</p><p>As recommended below, [Derek Molloy](here: http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/ ) has some excellent tutorials.</p><p>You approach is sound though. Once you have the EEPROM matching with your DTBO, the BBB will boot and automatically pin mux your cape.</p></p>
HouseOfBeck on DEV-12774 - SparkFun BeagleBone Black Proto CapeHouseOfBeckurn:uuid:71b88729-4680-f148-eff6-1aa021bf505e2014-08-12T17:42:07-06:00<p>See "Loading custom capes" here for information on a bug when loading custom capes.<p><a href="http://elinux.org/Beagleboard:BeagleBoneBlack_Debian" rel="nofollow">Loading custom capes</a></p></p>
Customer #383681 on DEV-12774 - SparkFun BeagleBone Black Proto CapeCustomer #383681urn:uuid:9489e72f-74db-b23c-58cc-92c3a0bd4a022014-08-06T05:19:19-06:00<p>I purchased this cape. Apparently I can write a dts file and compile it so that I have better control of the headers at boot time. I'm trying to control some dc motors and was only able to find 4 gpios and 4 more pwms that are low and stay low when the beaglebone boots. I can use those for now, but I imagine that in the future this will probably change and I'd like to know how to deal with it. I'd also like to be able to choose my pin layout so that it's a little more intuitive for my students.<p>So my questions are:</p><p>Can I access and program the eeprom on the proto cape from the beaglebone black? If so, how?</p><p>How do I make the dts file?</p><p>How do I compile it?</p><p>Where do I put it?</p><p>How do I make debian use it when it boots?</p></p>
Swift on DEV-12774 - SparkFun BeagleBone Black Proto CapeSwifturn:uuid:2309e9cd-5c7e-1144-37fe-78376d323b8f2014-07-01T20:35:32-06:00<p>Found many infos here:
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/
http://papermint-designs.com/community/node/338</p>
Swift on DEV-12774 - SparkFun BeagleBone Black Proto CapeSwifturn:uuid:eacb5e24-b78f-dded-0ded-20a4e3e2bcb92014-07-01T20:32:33-06:00<p>I was frustated with this product with BBB Debian image..... but with BBB Angstrom was a breeze to make the BBB recognize the cap and use the device tree mecanism. What is wrong with BBB Debian image not working with this product?</p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:7f41d535-7004-3646-f7b4-8dac722324262014-06-09T22:13:24-06:00<p>Update: Some boards went out with CryptoCape data on the EEPROM. It won't harm anything but I am working on a quick script to erase it.</p>
Jarryd on DEV-12774 - SparkFun BeagleBone Black Proto CapeJarrydurn:uuid:e33b49a7-db62-0eba-fb06-f18f32b0c1482014-06-09T22:01:51-06:00<p>What size breadboard would fit with stackable female headers populated?</p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:dcee3f6b-ccce-f98f-b3f8-320043922f5a2014-06-07T17:26:10-06:00<p>Thanks for the heads up! I will double check our production files.</p>
jdsteele on DEV-12774 - SparkFun BeagleBone Black Proto Capejdsteeleurn:uuid:7c9c67b6-7e0c-2abc-7d7a-43702df4dde82014-06-07T17:23:16-06:00<p>The description states that the EEPROM is blank, however, at least one of these that I purchased came programmed as a "SparkFunBB-BONE-CRYPTO2014", presumably intended for SF's new CryptoCape DEV-12773.</p>
CaseyTheRobot on DEV-12774 - SparkFun BeagleBone Black Proto CapeCaseyTheRoboturn:uuid:35ad3b45-ad7a-dfd7-73d8-9b66b17967de2014-05-22T17:30:29-06:00<p>Correct. It's a run of the mill EEPROM for board identification.</p>
bfesser on DEV-12774 - SparkFun BeagleBone Black Proto Capebfesserurn:uuid:2b2ec9a3-8674-3512-8467-bc918bfee47f2014-05-22T17:22:31-06:00<p>I'm sure someone will ask, since SFE weren't particularly explicit in the description; it's a 256kb I²C EEPROM (according to the part number/datasheet).</p>