http://elinux.org/api.php?action=feedcontributions&user=Rkherod&feedformat=atom 2013-05-25T10:03:47Z User contributions MediaWiki 1.22alpha http://elinux.org/BeagleBoard 2013-04-01T18:27:51Z

<p>Rkherod: </p> <hr /> <div>[[Category: Linux]]<br /> [[Category: OMAP]]<br /> [[Category:Development Boards]]<br /> [[Category: BeagleBoard]]<br /> <br /> This page collects information about [http://beagleboard.org BeagleBoard.org's] open hardware embedded computer boards based on [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] processors. Most of this material is applicable to the BeagleBoard and BeagleBoard-xM. See the [[BeagleBone]] page for information on that board.<br /> <br /> &lt;div style=&quot;margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; &quot;&gt;<br /> '''NEWS:'''<br /> * Limited numbers of Pixel Qi LCD kits and LVDs kits are now available from [http://www.tincantools.com TinCanTools]<br /> * [http://www.tincantools.com TinCanTools] has now discontinued [[BeagleBoard_Zippy2|Zippy2]], and [[BeagleBoard_Zippy|Zippy Boards]].<br /> * [http://www.nxelec.com/products/hmi BeadaFrame] 7&quot; LCD display kits for BeagleBoard and BeagleBone are available now!<br /> * [http://www.chalk-elec.com/ 10&quot; LCD LVDS plug-and-play bundle with capacitance touchscreen and ambient light sensor] is available in stock now!<br /> * LVDS LCD add-on board [http://www.chalk-elec.com/ LVDS LCD] has been released and is available for order<br /> * An [http://www.liquidware.com/shop/show/BB-BT/BeagleTouch OLED touchscreen module &quot;BeagleTouch&quot;] and [http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice lithium battery module &quot;BeagleJuice&quot;] are now available from [http://www.liquidware.com/shop Liquidware]<br /> &lt;/div&gt;<br /> &lt;br&gt;<br /> =Events=<br /> * [http://jefro.wordpress.com/open-source-conferences/ Jeff's list of open source conferences]<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Event <br /> ! Location <br /> ! Date <br /> |-<br /> | [http://makerfaire.com/newyork/2012/index.html Maker Faire New York] <br /> | New York Hall of Science, Queens, NY, USA<br /> | Sep 29 - 30, 2012 <br /> |-<br /> | [http://www.t-dose.org/ T-Dose]<br /> | Eindhoven, The Netherlands<br /> | Oct 27 - 28, 2012<br /> |-<br /> | [http://e.ubmelectronics.com/armtechcon/index.html ARM Techcon]<br /> | Santa Clara, CA, USA<br /> | Oct 30 - Nov 1, 2012<br /> |-<br /> | [https://events.linuxfoundation.org/events/embedded-linux-conference-europe Embedded Linux Conference Europe]<br /> | Barcelona, Spain<br /> | Nov 5 - 7, 2012<br /> |}<br /> <br /> =Hardware=<br /> <br /> The BeagleBoard is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600&amp;nbsp;MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.<br /> <br /> The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.<br /> <br /> ==Components==<br /> <br /> {|border=0<br /> !Top view of rev B:<br /> !Top view of rev C:<br /> |-<br /> |[[Image:Bb revb top numbered.jpg]]<br /> |[[Image:Bb revc top numbered.jpg]]<br /> |-<br /> |}<br /> {|border=1<br /> !No.<br /> !Name<br /> !Comment<br /> |-<br /> |'''1'''<br /> |[http://www.ti.com/omap35x OMAP3530] processor + 256&amp;nbsp;MB NAND<br /> <br /> + 128&amp;nbsp;MB DDR (rev B)<br /> <br /> + 256&amp;nbsp;MB DDR (rev C)<br /> |PoP: Package-On-Package implementation for Memory Stacking<br /> [http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256&amp;nbsp;MB NAND/128&amp;nbsp;MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]<br /> <br /> ([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])<br /> <br /> [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]<br /> |-<br /> |'''2'''<br /> |[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]<br /> |<br /> |-<br /> |'''3'''<br /> |[[BeagleBoard#DVI|DVI-D]]<br /> |Connection via HDMI connector<br /> |-<br /> |'''4'''<br /> |[[BeagleBoard#JTAG|14-pin JTAG]]<br /> |1.8V only!<br /> |-<br /> |'''5'''<br /> |Expansion connector: I2C, I2S, SPI, MMC/SD<br /> |User must solder desired header into place<br /> |-<br /> |'''6'''<br /> |[[BeagleBoard#User_button|User button]] <br /> |Allows setting boot order.<br /> |-<br /> |'''7'''<br /> | Reset button<br /> |<br /> |-<br /> | '''8'''<br /> |[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]<br /> |Rev A and B: not working, unpopulated<br /> <br /> Rev C: populated and working<br /> |-<br /> |'''9'''<br /> |SD/MMC+<br /> | SDHC cards are supported<br /> |-<br /> |'''10'''<br /> |[[BeagleBoard#RS232|RS-232 serial]]<br /> |<br /> |-<br /> |'''11'''<br /> |Alternate power <br /> |normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])<br /> |-<br /> |'''12'''<br /> |[[BeagleBoard#OTG|USB 2.0 HS OTG]] <br /> |Mini-AB connector. Board can be powered from port. <br /> |-<br /> |'''13'''<br /> |Stereo In<br /> |<br /> |-<br /> |'''14'''<br /> |Stereo Out<br /> |<br /> |-<br /> |'''15'''<br /> |S-Video<br /> |<br /> |-<br /> |'''16'''<br /> |TWL4030 (Rev A thru C2 inc.)<br /> [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)<br /> |Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.<br /> |-<br /> |'''17'''<br /> |LCD<br /> |only rev C<br /> |-<br /> |'''18'''<br /> |USB power<br /> |<br /> |-<br /> |'''19'''<br /> |Host PHY<br /> |<br /> |-<br /> |'''20'''<br /> |32&amp;nbsp;kHz<br /> |<br /> |-<br /> |'''21'''<br /> |12&amp;nbsp;MHz<br /> |<br /> |-<br /> |'''22'''<br /> |RS-232 XVCR<br /> |<br /> |-<br /> |'''23'''<br /> |PWR SW<br /> |<br /> |-<br /> |'''24'''<br /> |VBAT<br /> |<br /> |-<br /> |}<br /> <br /> * Board size: 3&quot; x 3&quot; (about 76.2 x 76.2&amp;nbsp;mm)<br /> * Weight: ~37&amp;nbsp;g<br /> * Currently six-layer PCB; target: four layer PCB<br /> <br /> '''Bottom of rev B:'''<br /> <br /> [[Image:Beagle_bottom.jpg]]<br /> <br /> See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.<br /> <br /> ==Manual==<br /> <br /> See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].<br /> <br /> ==Schematic==<br /> <br /> Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br /> <br /> ==Layout== <br /> <br /> Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.<br /> <br /> ==Errata==<br /> <br /> # ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5&amp;nbsp;V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.<br /> # ''Boards revision &lt; A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1&amp;nbsp;ohm instead of a 1&amp;nbsp;ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.<br /> # ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.<br /> # ''Boards revision &lt; A5 only'': There is an issue where on some boards the 1.8&amp;nbsp;V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1&amp;nbsp;uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with &quot;102&quot; (== 1uH). If any of these three inductors are labeled with &quot;104&quot; (== 100&amp;nbsp;uH) they are wrong and have to be exchanged.<br /> # ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.<br /> # ''Boards revision A and &lt; B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with Git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2&amp;nbsp;µF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!<br /> # ''Boards revision A and &lt; B5'': There is some issue with a 32&amp;nbsp;kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on BeagleBoard might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. The symptom from this is that after booting the Linux kernel, the serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use the 32&amp;nbsp;kHz timer to clock Linux, instead use the MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32&amp;nbsp;kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision &gt;= B5 removes capacitor C70.<br /> # ''Random boards, quite rare, revision &lt; B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from the host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but the Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.<br /> <br /> For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list &amp; issue tracker], too.<br /> <br /> Note: BeagleBoard revision B6 uses different package for U9/U11.<br /> <br /> ==Clocking==<br /> <br /> Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:<br /> <br /> * ARM Cortex-A8 processor is currently clocked at 500&amp;nbsp;MHz<br /> * 500&amp;nbsp;MHz is the default used because it is a balance of performance and longevity<br /> * For OMAP35x 600&amp;nbsp;MHz is maximum recommended<br /> * An additional 720&amp;nbsp;MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the BeagleBoard C4<br /> * At 600&amp;nbsp;MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy<br /> * Higher than 600/720&amp;nbsp;MHz is out of specification and no guarantee it will work at all (or not damage itself)<br /> <br /> * Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:<br /> <br /> {| border=&quot;1&quot;<br /> ||'''ARM'''||'''DSP'''||'''core voltage'''<br /> |-<br /> |720&amp;nbsp;MHz||520&amp;nbsp;MHz||1.35&amp;nbsp;V<br /> |-<br /> |600&amp;nbsp;MHz||430&amp;nbsp;MHz||1.35&amp;nbsp;V<br /> |-<br /> |550&amp;nbsp;MHz||400&amp;nbsp;MHz||1.27&amp;nbsp;V<br /> |-<br /> |500&amp;nbsp;MHz||360&amp;nbsp;MHz||1.2&amp;nbsp;V<br /> |}<br /> <br /> * For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.<br /> * The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].<br /> * There is a thermal monitor in the core, you could use to scale frequency up and down<br /> <br /> To set the CPU clock to 600&amp;nbsp;MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:<br /> <br /> * The U-Boot command &quot;mw 48004940 0012580c&quot; will temporarily set the CPU clock to 600&amp;nbsp;MHz (not permanent over reset).<br /> * To permanently set the CPU clock to 600&amp;nbsp;MHz, include the above command in the &quot;bootcmd&quot; variable or equivalent script.<br /> <br /> * To set the DSP clock to 430&amp;nbsp;MHz use &quot;mw 48004040 0x0009ae0c&quot;.<br /> <br /> ==Power management==<br /> <br /> * Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]<br /> * Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]<br /> * Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8&amp;nbsp;mW sleep for Beagle Board]<br /> <br /> Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5&amp;nbsp;watts idle, however it also uses the same amount under load] (see bottom of that page).<br /> <br /> ==DLP Pico projector==<br /> <br /> Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the BeagleBoard. The stand-alone pico projector will support VGA resolution (640 x 480 pixels), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.<br /> <br /> It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.<br /> <br /> See [http://blog.makezine.com/archive/2009/01/tis-beagleboard-and-dlp-pico-projec.html article from Make], too.<br /> <br /> DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].<br /> <br /> ==Interfacing to Raw LCD Panels==<br /> <br /> Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the BeagleBoard exist:<br /> <br /> * [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article <br /> * [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm HDMI-to-parallel] workaround method<br /> * [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap DIY HDMI-to-parallel converter]<br /> <br /> =Availability=<br /> <br /> BeagleBoard Rev. C3 boards are available from<br /> <br /> * [http://www.mouser.com/beagleboard Mouser]<br /> * [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].<br /> <br /> BeagleBoard Rev. C4 boards are available from:<br /> <br /> * [http://www.liquidware.com/shop/show/BB-C4/BeagleBoard+C4 Liquidware]<br /> <br /> Note: For non-US Digi-Key free shipping orders:<br /> <br /> * Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page<br /> * Select ''Order Online'' for your country<br /> * Add quantity ''1'' and part number ''296-23428-ND''<br /> * Click ''Add to order''<br /> <br /> When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.<br /> <br /> Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.<br /> <br /> Note: While you get free shipping, most probably you have to pay tax, for example, ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.<br /> <br /> Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2&amp;nbsp;GB MMC, power supply, Linux BSP).<br /> <br /> Note: German (Europe) users can order through German shops, too. For higher price, though. <br /> * [http://shop.embedded-projects.net/index.php?module=artikel&amp;action=artikel&amp;id=259 Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.<br /> * [http://www.watterott.com/en/BeagleBoard Watterott electronic] sells BeagleBoard for EUR 124,95 + shipping.<br /> <br /> See below for ''hardware'' differences of the revisions. There are no ''software'' differences. <br /> <br /> ==Revision A==<br /> <br /> There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.<br /> <br /> ==Revision B==<br /> <br /> Revision B is same as revision A, except<br /> * fix for shorted LEDs 0/1<br /> * fix for wrong power jack pinout<br /> * revision B6 uses different package for U9/U11<br /> Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.<br /> <br /> There are 4 revisions of the B board in the field: B4, B5, B6 and B7.<br /> <br /> The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.<br /> <br /> ==Revision C2==<br /> Revision C2 is same as revision B7 except:<br /> * USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.<br /> * Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])<br /> * It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:<br /> ** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code<br /> * Power measurement feature<br /> * Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030<br /> * Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])<br /> * Revision detection (to be able to identify C2 board from older boards by software, for example, for different pin mux)<br /> * 256&amp;nbsp;MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256&amp;nbsp;MB NAND like rev B)<br /> <br /> Note: Revision C2 is the first production version, and all orders from Digi-Key are shipped as Rev C2.<br /> <br /> ==Revision C3==<br /> As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.<br /> <br /> Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:<br /> * Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery<br /> * Mounting holes conected to ground<br /> * Slightly improved S-Video<br /> <br /> ==Revision C4==<br /> Revision C4 boards are the same as Revision C3 except:<br /> * Processor is 720&amp;nbsp;MHz capable OMAP3<br /> * Improved USB Host PHY power rails<br /> <br /> ==Revision C5==<br /> Revision C5 boards are the same as Revision C4 [http://circuitco.com/support/index.php?title=BeagleBoard#Image_Files except]:<br /> * The memory chip is upgraded to 512&amp;nbsp;MB NAND<br /> <br /> ==Clones==<br /> ===EBVBeagle===<br /> EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].<br /> It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB-to-Ethernet adapter, MMC card, USB hub and some cables.<br /> More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].<br /> <br /> ===Mini Board===<br /> [[Mini_Board|ICETEK-OMAP3530-Mini]] is a Chinese BeagleBoard clone.<br /> <br /> ===DevKit8000===<br /> [http://www.armkits.com/Product/devkit8000.asp DevKit8000] is from [http://www.armkits.com Embest], China. It is a compact development board based on TI OMAP3530.<br /> <br /> ===DevKit8500D===<br /> [http://www.armkits.com/Product/devkit8500d.asp DevKit8500D] is from [http://www.armkits.com Embest], China. It is a high-performance development board based on TI DM3730.<br /> <br /> ===SBC8530===<br /> [http://www.armkits.com/Product/sbc8530.asp SBC8530] is from [http://www.armkits.com Embest], China. It is a compact single board computer based on TI DM3730 and features UART, 4 USB Host, USB OTG, Ethernet, Audio, TF, WiFi/Bluetooth, LCD/VGA, DVI-D and S-Video.<br /> <br /> ===Tianyeit CIP312===<br /> [http://www.tianyeit.com CIP312 ] is from [http://www.tianyeit.com Tianyeit], China. It is has many functions ,such as WLAN/BT/ dual 10/100M Ethernet Contoller-LAN9221I/MCP2512 CAN BUS/ Touch Screen Controller/USB HUB/USB host/USB OTG Etc. Our module is base on DM3730/omap3530 all functions are packaged in 40x40x3.5&amp;nbsp;mm package ; For detailed information, please visit our website<br /> [[Image:http://www.tianyeit.com/download/cip312.jpg]]<br /> <br /> ===IGEPv2===<br /> [http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like, for example, Ethernet connector, Wi-Fi and Bluetooth.<br /> * 720&amp;nbsp;MHz OMAP3 Processor<br /> * 512&amp;nbsp;MB RAM / 512&amp;nbsp;MB Flash<br /> <br /> ===SOM3530===<br /> [[SOM3530]] is a Chinese BeagleBoard clone [[System-on-Module]], dimensions 40x40x4&amp;nbsp;mm, maybe the smallest [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530]-based modules in the world! Including 100&amp;nbsp;Mbit/s high perfomance Ethernet I/F.<br /> <br /> ==BeagleBoard-based products==<br /> * [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]<br /> <br /> ==Beagle case==<br /> <br /> *[http://specialcomp.com/beagleboard/ Special Computing acrilyic case]<br /> ** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]<br /> * [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]<br /> * [http://aspectrt.web.fc2.com/support/ Aspect metal case for BeagleBoard-xM]<br /> <br /> =Adapters=<br /> <br /> For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].<br /> <br /> See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for BeagleBoard.<br /> <br /> ==Expansion boards==<br /> See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards<br /> <br /> [http://www.nxelec.com/products/hmi BeadaFrame] - A 7&quot; TFT LCD Screen with resistive touch for BeagleBoard and BeagleBone. A plastic (ABS) frame is included also for ease of mounting.<br /> <br /> [http://www.chalk-elec.com LVDS LCD] - small add-on board to connect any LVDS LCD panel (like those in notebooks) to BeagleBoard (-xM) and PandaBoard. Also, they offer plug-and-play bundle with 10&quot; 1024x600 LCD with capacitance touchscreen and ambient light sensor for automatic brightness control. The board is open-source.<br /> <br /> [http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular &quot;shield&quot; that snaps on top of the BeagleBoard and provides a touch-screen OLED interface<br /> <br /> [http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the BeagleBoard that powers the BeagleBoard.<br /> <br /> [http://www.picklejar.org/lox LOX] - A dual channel internet linking radio (Ham, GMRS, etc.) interface that can run any combination of two repeaters, simplex nodes, or remote bases.<br /> <br /> ==JTAG==<br /> <br /> Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.<br /> See [[BeagleBoardJTAG]] for more information.<br /> <br /> The [http://www.armkits.com/Product/xds100.asp XDS100v2 USB JTAG Emulator] is available from [http://www.armkits.com Embest] which is the second release of the XDS100 JTAG emulator technology supporting debug of a variety of TI devices.<br /> <br /> ==RS-232==<br /> <br /> The pinout on the BeagleBoard is &quot;AT/Everex&quot; or &quot;IDC10&quot;. You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&amp;cat=0&amp;page=1&amp;featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.<br /> <br /> Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&amp;cat=0&amp;page=1&amp;featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.<br /> <br /> ==USB-to-Serial Converter==<br /> <br /> Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.<br /> <br /> ==USB==<br /> There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.<br /> <br /> ===EHCI===<br /> The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.<br /> <br /> According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5&amp;nbsp;V at 500&amp;nbsp;mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5&amp;nbsp;V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an &quot;extremely limited&quot; ampount of power (probably 100&amp;nbsp;mA or so) so you'll need a &quot;self-powered&quot; USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]<br /> <br /> '''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8&amp;nbsp;V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22&amp;nbsp;µF 0805 package SMT capacitor atop the existing capacitor on C97. If SMT parts are not available, some boards can be repaired by a 22&amp;nbsp;µF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.<br /> <br /> ===OTG===<br /> The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.<br /> <br /> When using the OTG port in host mode, you must power the BeagleBoard using the +5&amp;nbsp;V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100&amp;nbsp;mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.<br /> <br /> The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are &quot;A&quot; or &quot;B&quot;.<br /> <br /> You can find &quot;mini A&quot; adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]<br /> &lt;table&gt;<br /> &lt;tr&gt;&lt;td&gt;<br /> Since the right cables might be hard to get, you simply can<br /> * short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.<br /> or<br /> * use a &quot;mini B&quot; cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.<br /> &lt;/td&gt;&lt;td&gt;[[Image:usb_otg.png]]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;<br /> The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.<br /> See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.<br /> <br /> ==DVI==<br /> <br /> DVI-D connection on BeagleBoard uses an [http://en.wikipedia.org/wiki/HDMI HDMI connector]:<br /> <br /> ''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''<br /> <br /> BeagleBoard can be connected to a DVI monitor using an HDMI male to DVI male cable.<br /> <br /> The BeagleBoard does not connect the HDMI shell to ground or any other BeagleBoard signal. This is not a problem with high-quality HDMI to DVI cables that connect all the ground wires. However, there are lots of cheap HDMI to HDMI cables that do not connect the ground wires and only use the shell as a combined shield and ground. To use one of these you would need to connect the BeagleBoard's HDMI shell to ground. The BeagleBoard-xM connects the HDMI shell to frame ground, which is in turn connected to system ground through R119. For more information, see this thread: [http://groups.google.com/group/beagleboard/browse_thread/thread/861da101804da56b].<br /> <br /> == Arduino ==<br /> <br /> * [[BeagleBoard_Trainer|Trainer Board]] from [http://www.tincantools.com TinCanTools] has an Arduino compatible Atmel AVR on board<br /> * Arduino [http://arduino.cc/en/Main/ArduinoBoardNano Nano] uses an FTDI FT-232 based interface which is supported by the ftdi_sio kernel driver- [[BeagleBoard_with_Arduino|How To Notes]]<br /> * Arduino [http://arduino.cc/en/Main/ArduinoBoardUno Uno] uses a Atmel ATmega8U2 based interface which is supported by the cdc_acm kernel driver - [[BeagleBoard_with_Arduino|How To Notes]]<br /> <br /> =BootRom=<br /> <br /> OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98]. <br /> <br /> ==User button==<br /> <br /> With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):<br /> <br /> * User button ''not'' pressed: NAND -&gt; USB -&gt; UART -&gt; MMC<br /> * User button ''is'' pressed: USB -&gt; UART -&gt; MMC -&gt; NAND<br /> <br /> Technically speaking, the user button configures pin SYS.BOOT[5]. See the Initialization chapter of [http://www.ti.com/lit/pdf/spruf98 SPRUF98] for more details.<br /> <br /> ==Serial and USB boot==<br /> <br /> Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|U-Boot environment from Linux]].<br /> <br /> ===OMAP U-Boot Utils===<br /> <br /> Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide<br /> <br /> * ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.<br /> * ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.<br /> * ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.<br /> * ''ukermit - Download a file from host without using kermit to U-Boot.<br /> <br /> See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.<br /> <br /> ===Serial boot===<br /> <br /> Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there is one tool for UART boot:<br /> <br /> * [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)<br /> <br /> See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br /> <br /> ===USB boot===<br /> <br /> There is a patch to x-loader to allow it to do a USB boot. It can boot all the way to a Linux login.<br /> It's is used with a new version of omap3_usbload.<br /> <br /> * [http://members.efn.org/~rick/pub/x-loader-usb.tar.bz2 x-loader-usb]<br /> <br /> Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:<br /> <br /> * [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]<br /> <br /> See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.<br /> <br /> See the [[BeagleBoardRecovery#USB_recovery|USB recovery section]] on how to use USB boot for board recovery.<br /> <br /> ==NAND boot==<br /> <br /> See [[BeagleBoardNAND|NAND boot]] article.<br /> <br /> ==MMC/SD boot==<br /> <br /> Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.<br /> <br /> ===MMC/SD formatting===<br /> <br /> As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using, for example, Windows or Linux tools.<br /> <br /> '''Windows'''<br /> <br /> See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.<br /> <br /> You can download this tool from [http://www.sysanalyser.com/sp27213.exe here]. Make sure the version is 2.0.6; newer versions may not work.<br /> <br /> '''Linux'''<br /> <br /> Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].<br /> <br /> ===Dual partition card===<br /> <br /> You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.<br /> <br /> To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (for example, in U-Boot using ''setenv bootargs''):<br /> <br /> console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait<br /> <br /> ===U-Boot booting===<br /> <br /> If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a U-Boot prompt after booting the BeagleBoard. For example (output from terminal program with 115200 8N1):<br /> <br /> ...40T.........XH.H.U�..Instruments X-Loader 1.41<br /> Starting on with MMC<br /> Reading boot sector<br /> <br /> 717948 Bytes Read from MMC<br /> Starting OS Bootloader from MMC...<br /> <br /> U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)<br /> <br /> OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz<br /> TI 3430Beagle 2.0 Version + mDDR (Boot ONND)<br /> DRAM: 128 MB<br /> Flash: 0 kB<br /> NAND:256 MiB<br /> In: serial<br /> Out: serial<br /> Err: serial<br /> Audio Tone on Speakers ... complete<br /> OMAP3 beagleboard.org #<br /> <br /> Using this U-Boot prompt, you now can start kernel uImage stored on MMC card manually:<br /> <br /> OMAP3 beagleboard.org # mmc init<br /> OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage<br /> OMAP3 beagleboard.org # bootm<br /> <br /> If you like to make that happen every boot:<br /> <br /> OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv<br /> <br /> Note: saveenv will not work on the xM. You will need to create a &lt;tt&gt;boot.scr&lt;/tt&gt; file in the FAT partition for the xM. See [https://fedoraproject.org/wiki/Architectures/ARM/BeagleBoardxMSDCard#Set_up_u-boot set up u-boot]&lt;br&gt;<br /> Note2: after a saveenv, u-boot will not read your boot.scr any more. To make it use boot.src again, type &quot;nand erase&quot; in the u-boot promt (works on C4, older versions may need a &quot;nand unlock&quot; too).<br /> <br /> ===Barebox booting===<br /> <br /> You can also use barebox to boot.<br /> <br /> On barebox you will have to generate it two time.<br /> <br /> The first time as a x-loader via defconfig: omap3530_beagle_xload_defconfig<br /> <br /> The second time as the real boot loader omap3530_beagle_defconfig<br /> <br /> =Code=<br /> <br /> Code and binaries for BeagleBoard are available at various places.<br /> <br /> ==Binaries==<br /> <br /> BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where &quot;official&quot; TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it. <br /> <br /> Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt BeagleBoard demo images] are up to date binaries including e17 as window manager, the AbiWord word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:<br /> <br /> * [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]<br /> * [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]<br /> * [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]<br /> * [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]<br /> <br /> See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.<br /> <br /> ==Source==<br /> '''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].<br /> <br /> '''Update on March 3 - 2011''': Sources for the SD card shipped with revisions Ax and Bx of the BeagleBoard-xM are in the Angstrom Distribution. The script used to build the sources is documented at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext. The sources at http://gitorious.org/beagleboard-validation are meant to mimic what was used in the OpenEmbedded-based build.<br /> <br /> Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available. <br /> <br /> ===X-Loader===<br /> <br /> Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://gitorious.org/x-load-omap3 X-Loader git repository]. Get it by<br /> <br /> git clone git://gitorious.org/x-loader/x-loader.git xloader<br /> cd xloader/<br /> <br /> Build:<br /> <br /> make distclean<br /> make omap3530beagle_config<br /> make<br /> <br /> Result will be a ~20k sized ''MLO'' in the main directory. This is the signed x-loader and is ready for use.<br /> <br /> ===U-Boot===<br /> <br /> [http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard (except for revision C4; see note below). Get it by:<br /> <br /> git clone git://git.denx.de/u-boot.git u-boot-main<br /> cd u-boot-main<br /> git checkout --track -b omap3 origin/master<br /> <br /> Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):<br /> <br /> make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper<br /> make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config<br /> make CROSS_COMPILE=arm-none-linux-gnueabi- <br /> <br /> Result will be a ~160&amp;nbsp;KB sized ''u-boot.bin'' in the main directory.<br /> <br /> Note: Due to (patch and binary) size, the BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].<br /> <br /> Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:<br /> <br /> git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3<br /> cd u-boot-omap3<br /> git checkout --track -b omap3-dev origin/omap3-dev<br /> <br /> Note: For changing the screen resolution there is one option modifying the file in &quot;include/configs/omap3_beagle.h&quot; and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]<br /> <br /> Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...<br /> Get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/<br /> ('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])<br /> <br /> Note: If you want to activate I²C from the expansion header, modify board/ti/beagle/beagle.h :<br /> <br /> MUX_VAL(CP(I2C2_SCL), (IEN | PTU | EN | M4)) /*GPIO_168*/<br /> MUX_VAL(CP(I2C2_SDA), (IEN | PTU | EN | M4)) /*GPIO_183*/<br /> <br /> to<br /> <br /> MUX_VAL(CP(I2C2_SCL), (IEN | PTU | DIS | M0)) /*I2C2_SCL*/<br /> MUX_VAL(CP(I2C2_SDA), (IEN | PTU | DIS | M0)) /*I2C2_SDA*/<br /> <br /> ===Linux kernel===<br /> <br /> [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:<br /> <br /> git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git linux-omap<br /> cd linux-omap<br /> <br /> Build:<br /> <br /> make distclean<br /> make ARCH=arm omap2plus_defconfig<br /> make ARCH=arm menuconfig # Only needed if you want to change the default configuration<br /> make ARCH=arm uImage<br /> <br /> The result will be a ''uImage'' in ''arch/arm/boot/'' directory.<br /> <br /> '''Note: The following does not work. There is no defconfig &quot;omap3_beagle_defconfig&quot; nor any omap3 in the tree.'''<br /> <br /> If you use the OE toolchain and want to build outside of the OE tree you should do<br /> <br /> ARCH=arm<br /> export ARCH<br /> PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path<br /> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean<br /> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig<br /> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration<br /> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage<br /> <br /> Note: the staging dir in the path is for mkimage. If you've built a kernel before with oe, the program should be there<br /> <br /> Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.<br /> <br /> ===Experimental kernel patches and hacks===<br /> <br /> Some BeagleBoard developers maintain their own kernel experimental patches and hacks not ready for upstream:<br /> <br /> * [http://veter-project.blogspot.com/2012/03/comfortable-kernel-workflow-on.html Build Angstrom 2.6.38 Kernel] to compile kernel modules natively, see [https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/sam/beagleboard/eg6zYMcdMMA/KA3y0CS6n5cJ Angstrom package to natively compile kernel modules post] for corrections to the how-to.<br /> * [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches] '''(Broken Link)'''<br /> * [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related. '''(broken link)'''<br /> * [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of the main OMAP Git repository with additional patches, mainly display &amp; framebuffer related. '''(Link to Unknown Project)'''<br /> * [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of the main OMAP Git repository with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.<br /> <br /> =Compiler=<br /> <br /> TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.<br /> <br /> ==ARM==<br /> <br /> There is broad compiler support, including GCC - please see [http://www.elinux.org/ARMCompilers ARM Compilers]<br /> <br /> ==C64x+ DSP==<br /> <br /> A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).<br /> <br /> Note: my.TI account required. You may create an account [https://my.ti.com here]<br /> <br /> Note: An pld c6000 Linux compiler is available on the [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. It does NOT support c64x+ core in OMAP3 devices. Not recommended.<br /> <br /> You can also use the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&amp;sectionId=3&amp;tabId=416&amp;toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.<br /> <br /> See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.<br /> <br /> =Cortex A8 ARM features =<br /> <br /> ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.<br /> <br /> It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.<br /> <br /> See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an introduction into VFP-lite and NEON.<br /> <br /> ===ARM NEON===<br /> <br /> NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:<br /> * 64-bit signed/unsigned<br /> * 32-bit signed/unsigned<br /> * 32-bit single precision floating point<br /> * 16-bit signed/unsigned<br /> * 8-bit signed/unsigned<br /> <br /> The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.<br /> <br /> The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].<br /> <br /> For NEON optimized libraries, see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].<br /> <br /> NEON is used by various opensource projects:<br /> * [http://www.libav.org/ Libav] - libavcodec used by mplayer, omapfbplay, and many other Linux applications<br /> * libpixman - used by X.org and Mozilla &amp; Webkit browsers to render text and graphics<br /> * [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack<br /> * [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math, etc.)<br /> * [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec<br /> <br /> Compilation tools support for NEON:<br /> * ARM RVDS<br /> * GCC<br /> * [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]<br /> <br /> === ARM Cortex-A8 Floating Point ===<br /> <br /> There are two types of instructions in the ARM v7 ISA that handle floating point:<br /> <br /> 1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).<br /> These is used by GCC for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.<br /> <br /> 2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (two values in a D-register, or four values in a Q-register)<br /> These can be use by GCC when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases, the VFPv3 scalar ops will be used.<br /> <br /> ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.<br /> <br /> On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain one cycle/instruction throughput (processing two single-precision values at once) for consumer multimedia. The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.<br /> <br /> If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:<br /> * Use GCC with -ftree-vectorize (possibly modify source code to make it vector friendly)<br /> * Use NEON instrinsics (#include &lt;arm_neon.h&gt;, float32x2_t datatype and vmul_f32() etc)<br /> * Use NEON assembly language directly<br /> <br /> On Cortex-A9, there is a much higher performance floating point unit which can sustain one cycle/instruction throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.<br /> <br /> =Board recovery=<br /> <br /> If you played, for example, with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the BeagleBoard doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this. Do not panic and think you somehow 'bricked' the board unless you did apply 12&amp;nbsp;V to it.<br /> <br /> =Development environments=<br /> <br /> Instead of just using compiler + editor, you can use complete image create &quot;development tool chains&quot; which integrate compiler, build system, packaging tools, etc. in one tool chain.<br /> <br /> ==OpenEmbedded==<br /> <br /> For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]],[[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.<br /> <br /> In the OE getting started document, for BeagleBoard replace ''MACHINE = &quot;om-gta01&quot;'' by ''MACHINE = &quot;beagleboard&quot;''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.<br /> <br /> Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.&lt;!-- DEAD LINK: resulting in something like [http://scap.linuxtogo.org/files/fc987d4acb2c745fb7e19cf4dca8de70.png this].--&gt;<br /> <br /> ===One very important note:=== <br /> <br /> It's important to have an X-Loader on your BeagleBoard that uses the uImage on the SD card that goes with Angstrom. The B6 BeagleBoards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:<br /> * Make an SD card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more information on making the SD card.<br /> * Put the SD card in the BeagleBoard, and boot up to the U-Boot prompt.<br /> * Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section. <br /> * Reboot the BeagleBoard to see that the new X-Loader is properly loaded.<br /> <br /> This will update the X-Loader to a newer version that will automatically load uImage from the SD card when present -- rather than always using the uImage in the BeagleBoard NAND.<br /> <br /> ==Eclipse==<br /> The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a fully functional C and C++ integrated development environment (IDE) for the Eclipse platform. The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a &quot;Remote System Explorer&quot; (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the Target Communications Framework ([[TCF]]) component. Information on how RSE is used for, for example, Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].<br /> <br /> See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging).<br /> <br /> ==Android==<br /> The [http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.<br /> <br /> There are several resources for Android on OMAP (Beagle) available:<br /> <br /> '''OMAPZOOM'''<br /> <br /> You can find Android port for OMAP ZOOM architecture on [https://gforge.ti.com/gf/project/omapandroid/ OMAPZoom.org's wiki page on Android]. <br /> <br /> '''EMBINUX'''<br /> <br /> [http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX&amp;trade;] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review. <br /> <br /> Detailed instructions, for porting Android on BeagleBoard, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.<br /> <br /> You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on BeagleBoard.<br /> <br /> '''Android on OMAP wiki'''<br /> <br /> Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]].<br /> <br /> '''0xdroid'''<br /> <br /> [http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on BeagleBoard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.<br /> <br /> The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard &amp; mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].<br /> <br /> You can watch the 0xdroid demo video on the BeagleBoard:<br /> * [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]<br /> * [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]<br /> * [http://www.youtube.com/watch?v=OGpYk1p1UPI 0xdroid demo video (3)]<br /> <br /> ==Mamona==<br /> <br /> [http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&amp;navigationId=12013&amp;contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support BeagleBoard.<br /> <br /> ==Ubuntu==<br /> <br /> See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.<br /> * [[BeagleBoardLucid]] Details about Ubuntu Lucid on the BeagleBoard.<br /> * [[BeagleBoardUbuntuKernel]] Details about the Ubuntu Kernel on the BeagleBoard.<br /> * [[BeagleBoard Ubuntu]]<br /> * [[BeagleBoardUbuntuKarmic]]<br /> <br /> ==Debian ARM==<br /> <br /> See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.<br /> <br /> ==Arch Linux ARM==<br /> <br /> See [http://archlinuxarm.org/platforms/armv7] how to install Arch Linux ARM on BeagleBoard.<br /> <br /> ==GeeXboX ARM==<br /> <br /> See [[GeeXboX|GeeXboX (ARM)]] installation guide how to install GeeXboX on BeagleBoard (including clones).<br /> <br /> ==Scratchbox==<br /> <br /> [http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 introduction], too.<br /> <br /> =Software hints=<br /> <br /> This section collects hints, tips &amp; tricks for various software components running on BeagleBoard.<br /> * [[RPM_jffs2_issue]]<br /> <br /> ==QEMU==<br /> <br /> [[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.<br /> <br /> ==Linux hints==<br /> <br /> See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:<br /> <br /> * Switching video output between DVI-D and S-Video<br /> * Disabling framebuffer blanking<br /> * Listing USB devices<br /> <br /> ==lmbench==<br /> <br /> Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on BeagleBoard.<br /> <br /> ==Mediaplayer (FFmpeg)==<br /> <br /> There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on BeagleBoard. Includes compiler hints and patches.<br /> <br /> ==Java==<br /> <br /> ===Open source===<br /> <br /> When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:<br /> * JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)<br /> * Cacao + GNU Classpath (JIT compiler, J2SE-like)<br /> * PhoneME Advanced Foundation (JIT compiler, CDC)<br /> <br /> Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].<br /> <br /> See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.<br /> <br /> OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.<br /> <br /> The recipes offer the following functionality:<br /> <br /> * OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)<br /> * OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)<br /> * OpenJDK + Hotspot (Shark port) (not working yet)<br /> <br /> [http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.<br /> <br /> People interested in getting this stuff working better should contact people on:<br /> * [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]<br /> * [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]<br /> <br /> You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].<br /> <br /> ===Oracle Java===<br /> <br /> As of August 2012, there is a binary version of Oracle JDK 7 available for Linux/ARM under a free (but not open source) license. More information:<br /> * [http://www.oracle.com/technetwork/java/javase/downloads/index.html Download on java.oracle.com]<br /> * [http://www.oracle.com/technetwork/java/javase/7u6-relnotes-1729681.html#LinuxARM Release notes for JDK 7 Update 6]<br /> * [http://www.oracle.com/us/corporate/press/1735645 Original announcement]<br /> * [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux Oracle blog with FAQ]<br /> * [http://www.oracle.com/technetwork/java/javase/terms/license/index.html Oracle Binary Code License]<br /> <br /> Supported features:<br /> * Java SE 7 compliant<br /> * Almost all development tools from the Linux/x86 JDK<br /> * Client and server JIT compilers<br /> * Swing/AWT support (requires X11R6)<br /> * Softfloat ABI only<br /> <br /> Oracle states in the [https://blogs.oracle.com/henrik/entry/oracle_releases_jdk_for_linux FAQ] that they are working on hard float support, as well as a JavaFX 2 port to Linux/ARM.<br /> <br /> == Booting Android (TI_Android_DevKit) from a USB stick ==<br /> '''Please note'''<br /> * This procedure was tested on BeagleBoard-xM revision B(A3)<br /> * An SD card will be still needed to load the kernel.<br /> * An SD card will contain boot parameters for the kernel to use a USB stick as the root filesystem<br /> <br /> '''Procedure'''<br /> # Download Android Froyo for BeagleBoard-xM from [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_00_00/index_FDS.html TI]<br /> # Follow the installation procedure for an SD card card.<br /> # Test if Froyo is working with your BeagleBoard-xM with an SD card.<br /> # You will notice that Android has a slow performance. That is why we will install root filesystem on a USB stick.<br /> # Format your USB stick and create one ext3 partition.<br /> # Mount newly created ext3 partition and extract TI's root filesystem to it: sudo tar jxvf rootfs_am37x.tar.bz2 -C /media/ROOT<br /> # Unmount flashdisk and insert it into the BeagleBoard.<br /> # Mount your SD card to your computer.<br /> # Now we need to tell the BeagleBoard to use the root filesystem from the /dev/sda1 partition instead of the SD card partition. That is done by overwriting boot.scr on the SD card with [http://www.apksoft.eu/android/boot.scr this one]<br /> # Unmount the SD card and insert it into the BeagleBoard and test.<br /> <br /> =Graphics accelerator=<br /> <br /> OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&amp;navigationId=12700&amp;contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.<br /> <br /> Tutorial:<br /> * [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]<br /> * [http://labs.qt.nokia.com/2009/11/20/building-qt-to-make-use-of-the-beagle-boards-sgx-gpu/ Building Qt to make use of the Beagle board’s SGX GPU]<br /> <br /> Some videos:<br /> <br /> * [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]<br /> * [http://www.youtube.com/watch?v=24TXpqa9jG0&amp;feature=related OpenGL ES 2.0 shader effects on OMAP3]<br /> * [http://www.youtube.com/watch?v=-UFUbqoNgs8&amp;feature=related 3D User Interface on OMAP3 Platform]<br /> * [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]<br /> * [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br /> * [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]<br /> * [http://www.youtube.com/watch?v=cfeqSOYkBJg&amp;feature=player_embedded Video of the Beagle Board turned into a portable battery powered Linux tablet]<br /> <br /> =Beginners guide=<br /> <br /> You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].<br /> <br /> =FAQ=<br /> <br /> For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and &quot;official&quot; [http://beagleboard.org/support/faq BeagleBoard.org FAQ].<br /> <br /> =Links=<br /> ==Home page==<br /> [http://beagleboard.org/ beagleboard.org] (BeagleBoard home)<br /> * Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org &lt;search term&gt;''<br /> <br /> ==Manuals and resources==<br /> * [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]<br /> * [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]<br /> * [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]<br /> * [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]<br /> * [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]<br /> * [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]<br /> * [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals<br /> * [http://code.google.com/p/beagleboard/ Beagle at code.google.com]<br /> * [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&amp;tabId=409&amp;familyId=1526&amp;documentCategoryId=4&amp;techDoc=4 OMAP3530/25 CBB BSDL Model]<br /> * [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for BeagleBoard]<br /> * [http://beagleboard.org/resources BeagleBoard resources page with hardware documentation]<br /> * Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.<br /> * OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]<br /> * [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]<br /> <br /> ==Contact and communication==<br /> * [http://groups.google.com/group/beagleboard BeagleBoard discussion list]<br /> * [http://code.google.com/p/beagleboard/issues/list BeagleBoard open point list and issue tracker]<br /> * [http://beagleboard.blogspot.com/ BeagleBoard blog]<br /> * [http://feeds.feedburner.com/BeagleBoard BeagleBoard RSS feed]<br /> * Chat:<br /> ** [http://beagleboard.org/chat BeagleBoard chat]<br /> ** IRC: #beagle channel on irc.freenode.net<br /> ** [http://www.beagleboard.org/irclogs/index.php IRC archive]<br /> * [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications<br /> * [http://www.beagleboard.de/ German BeagleBoard Forum and Wiki]<br /> <br /> ==TI resources==<br /> * [http://opensource.ti.com/ TI open source page]<br /> * [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]<br /> * [http://marc.info/?l=linux-omap&amp;m=120761100810527&amp;w=2 DSP Bridge driver for OMAP3 platform]<br /> * [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]<br /> * [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)<br /> * [http://amethyst.openembedded.net/~koen/index.php?sort=date&amp;order=desc&amp;path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]<br /> * [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]<br /> * [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]<br /> <br /> ==Articles==<br /> * [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about BeagleBoard]<br /> * [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]<br /> * [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about BeagleBoard Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]<br /> * [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]<br /> <br /> ==Books==<br /> * [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]<br /> <br /> ==BeagleBoard based training materials==<br /> * http://free-electrons.com/blog/beagle-labs/<br /> <br /> ==Past BeagleBoard events==<br /> * TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also BeagleBoard<br /> * [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&amp;t=4094&amp;st=0&amp;sk=t&amp;sd=a&amp;sid=d69cc807569ab41e33f93af698c536b8&amp;start=15#p41549 video]<br /> * LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]<br /> * [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at BeagleBoard. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]<br /> * [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008<br /> * [http://www.linuxworldexpo.com LinuxWorld Conference &amp; Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living BeagleBoard] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]<br /> * BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm<br /> * [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]<br /> * NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008<br /> * [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008<br /> * [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]<br /> * Free Open &quot;Embedded Linux&quot; Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&amp;ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&amp;feature=PlayList&amp;p=1BAB6EE9CC7285AD&amp;index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]<br /> * [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008<br /> * [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]<br /> * [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008<br /> * [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]<br /> * [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009<br /> * [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]<br /> * [[BeagleBoard/contest|BeagleBoard contest #2]], until February 27, 2009: Create a cool BeagleBoard application and win a Rev C2!<br /> * [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009<br /> * SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP &amp; Piccolo], May 13th 2009: Poing (Munich) - Germany<br /> * 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 BeagleBoard presentation]<br /> * until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])<br /> * TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').<br /> * Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.<br /> * 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])<br /> <br /> ==BeagleBoard wiki pages==<br /> * [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard<br /> * [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has information about status and usage of open source JTAG software OpenOCD with Beagle<br /> * [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]<br /> * [[BeagleBoardSugar|Sugar on BeagleBoard]]<br /> * [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]<br /> * [[BeagleBoard/video|BeagleBoard video]]<br /> * [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]<br /> * [[U-boot_musb_gadget_support|U-boot musb gadget support]]<br /> * [[BeagleBoard-JP|Japanese translation of this BeagleBoard page]]<br /> * [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]<br /> * [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]<br /> * BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]<br /> * [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]<br /> * [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with BeagleBoard<br /> * [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]<br /> * '''[[BeagleBoard/contest|BeagleBoard contest]]'''<br /> * [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]<br /> * [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard<br /> * [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]<br /> * [[Zoom2Beginners|Zoom2 for Beginners]]<br /> * [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]<br /> * [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]<br /> * [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the BeagleBoard] from Make:Online<br /> * [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private BeagleBoard wiki] (please don't add anything there, do it here. It will help to avoid splittering. Thanks!)<br /> * [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP<br /> * [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)<br /> * [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON introduction<br /> * [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html BeagleBoard setting date via GPS]<br /> * [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard<br /> * [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.<br /> * [[BeagleBrick]] software defined radio project<br /> <br /> ==BeagleBoard photos==<br /> * [http://www.flickr.com/groups/beagleboard/pool/ BeagleBoard pictures at flickr]<br /> * [http://www.flickr.com/photos/32615155@N00/2439256116/ BeagleBoard and USRP]<br /> * [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for BeagleBoard]<br /> * [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on BeagleBoard]<br /> <br /> ==BeagleBoard videos==<br /> * [http://uk.youtube.com/watch?v=fL_XMieanSc BeagleBoard Beginnings]<br /> * [http://www.youtube.com/watch?v=cXr-D1wROfQ BeagleBoard in the Living Room]<br /> * [http://uk.youtube.com/watch?v=FuVwh_VrIxk BeagleBoard 3D, Angstrom, and Ubuntu]<br /> * [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with BeagleBoard]<br /> * [http://uk.youtube.com/watch?v=9Z4ZTovtFKk BeagleBoard LED demo]<br /> * [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a BeagleBoard]<br /> * [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]<br /> * [http://www.youtube.com/watch?v=-tUBXD-KRp4 BeagleBoard Running Angstrom (VGA) on DLP Pico Projector]<br /> * [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on BeagleBoard working with Linux 2.6.27]<br /> * Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]<br /> * [http://in.youtube.com/watch?v=nADn_vNVEKw BeagleBoard booting Android]<br /> * [http://www.youtube.com/watch?v=UHQdUS0i-nw BeagleBoard, SGX, and libfreespace demo]<br /> <br /> ==BeagleBoard manufacturing==<br /> * [http://www.youtube.com/watch?v=C-CwkjT9z_0&amp;feature=related BeagleBoard Solder Paste Screening]<br /> * [http://www.youtube.com/watch?v=9LLjDovIG2M&amp;feature=related BeagleBoard Assembly Inspection]<br /> * [http://www.youtube.com/watch?v=sbOZfBnoVnM&amp;feature=related BeagleBoard Functional Test]<br /> * [http://www.youtube.com/watch?v=cvDtXmJJcEI&amp;feature=related BeagleBoard Reflow]<br /> * [http://www.youtube.com/watch?v=W2o4NTASxN0&amp;feature=related BeagleBoard Assembly at Circuitco]<br /> <br /> =Other OMAP boards=<br /> * OMAP 4430 Based 40X40&amp;nbsp;mm size [http://www.tianyeit.com CIP410] computer in package from [http://www.tianyeit.com Tianyeit]<br /> * OMAP DM3730/OMAP3530 Based 40X40mm size [http://www.tianyeit.com CIP312] Computer In Package from [http://www.tianyeit.com Tianyeit]<br /> * OMAP 4430 based [[PandaBoard]]<br /> * OMAP-L138 Based [[Hawkboard]]<br /> * OMAP3530 based [http://www.armkits.com/Product/devkit8000.asp DevKit8000] development board from [http://www.armkits.com Embest]<br /> * OMAP3530 based [http://www.armkits.com/Product/sbc8100.asp SBC8100] Single-board computer from [http://www.armkits.com Embest]<br /> * OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.<br /> * OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].<br /> * OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]<br /> * OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]<br /> * OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)<br /> * OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&amp;navigationId=12013&amp;contentId=28741 Software Development Platform (SDP)]<br /> * OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]<br /> * OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&amp;lang=en Archos 5, ARCHOS 5G and ARCHOS 7]<br /> * OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]<br /> * OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]<br /> * OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone<br /> * OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]<br /> * OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]<br /> * OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]<br /> * OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]<br /> * OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]<br /> * OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)<br /> * OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, Wi-Fi and Bluetooth.<br /> * OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]<br /> * OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]<br /> * OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]<br /> * OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]<br /> * OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.<br /> * OMAP35x System-on-Module [[SOM3530]], the smallest(40x40x4&amp;nbsp;mm) OMAP35XX-based system on module in the world! (It is not-Gumstix Overo is smaller at 17&amp;nbsp;mm*58&amp;nbsp;mm)<br /> * OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]<br /> <br /> =Subpages=<br /> &lt;splist<br /> parent=<br /> showparent=no<br /> sort=asc<br /> sortby=title<br /> liststyle=ordered<br /> showpath=no<br /> kidsonly=no<br /> debug=0<br /> /&gt;</div>

Rkherod http://elinux.org/BeagleBoard_Zippy2 2012-06-11T09:19:37Z

<p>Rkherod: </p> <hr /> <div><br /> <br /> [[File:zippy2-base.jpg|400px]]<br /> <br /> The Zippy2 Ethernet Combo Board (KSZ8851SNL-BBE-EVAL) is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10/100BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> <br /> The Zippy2 (KSZ8851SNL-BBE-EVAL) board was jointly developed by [http://www.micrel.com Micrel] and [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here].<br /> . <br /> <br /> <br /> <br /> = Hardware =<br /> == Ethernet ==<br /> The Zippy2 provides a standard 10/100BaseT (10/100 Mbit) Ethernet interface and uses Micrel's [http://www.micrel.com/page.do?page=/product-info/embedded_control.jsp KSZ8851SNL] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy2 provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy2 provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy2 provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy2 and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy2-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy2-battery2.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy2 provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy2 provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy2. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy2-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy2-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy2-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy2-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy2-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy2-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy2 combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy2 combination:<br /> #[[media:MLO-zippy2.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy2.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy2.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs2.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> = Automated script to create a bootable SD card =<br /> <br /> The following script will create a formatted SD card using your Linux PC. <br /> <br /> *[[media:mksdcard2.sh| mksdcard.sh]]<br /> <br /> Make a working directory for the files: mksdcard.sh, MLO, u-boot.bin, uImage, and test-rootfs.tar.gz and copy them into it. <br /> <br /> You will also need to make two mount points:<br /> <br /> mkdir /mnt/sdcard1<br /> mkdir /mnt/sdcard2<br /> <br /> Then from inside the working directory you created above, issue the command like this:<br /> <br /> ./mksdcard.sh /dev/sdb<br /> <br /> Where /dev/sdb is the drive for the SD card.<br /> <br /> This should generate a fresh bootable SD card for you!<br /> <br /> = Design Documents =<br /> The following are the design documents for the Zippy2 (KSZ8851SNL-BBE-EVAL) board:<br /> * [[media:zippy2_schematic.pdf|Zippy2_schematic]] <br /> * [[media:zippy2_gerbers.zip|Zippy2_gerbers.zip]]<br /> * [[media:zippy2_BOM.pdf|Zippy2_BOM.pdf]]<br /> <br /> = Software Links =<br /> <br /> The latest Linux driver for the KSZ8851SNL is included in the mainline Linux kernel and can be downloaded here:<br /> <br /> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.7.tar.bz2<br /> <br /> Also, Linus' GIT repo can be pulled from here:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary<br /> <br /> Or you can view just the driver:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/ks8851.c;h=6d3ac65bc35cfcd1ae3eb27e6249a8be38efe705;hb=HEAD<br /> <br /> = Programming the Zippy2 =<br /> All of the devices on the Zippy2 work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> <br /> To set the real time clock (RTC) on the Zippy2 board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Where to purchase the Zippy2 (KSZ8851SNL-BBE-EVAL)=<br /> <br /> The Zippy2 can be purchased from TinCanTools.com<br /> [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here.]<br /> [[Category: BeagleBoard]]<br /> [[Category: BeagleBoard Expansion Boards]]<br /> [[Category: TinCanTools]]</div>

Rkherod http://elinux.org/BeagleBoard_Zippy 2012-06-11T09:19:13Z

<p>Rkherod: </p> <hr /> <div><br /> The Zippy board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]). <br /> <br /> You can purchase the Zippy board from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16147 www.tincantools.com]&lt;br&gt;<br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]&lt;br&gt;<br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]&lt;br&gt;<br /> &lt;br&gt;<br /> == Hardware ==<br /> The BeagleBuddy Zippy Ethernet Combo Board is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> == Ethernet ==<br /> The Zippy provides a standard 10BaseT (10/100 Mbit) Ethernet interface and uses Microchip's [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en022889 ENC28J60] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> Compatible batteries are available from Mouser Electronics:<br /> <br /> [http://www.mouser.com/ProductDetail/Renata/CR1220TS/?qs=sGAEpiMZZMtz8P%2feuiupSd2F%2fX%2ffEmeEyLDGD5JMOeY%3d CR1220]<br /> <br /> [http://www.mouser.com/ProductDetail/Sanyo-Batteries/CR1220-SANYO/?qs=sGAEpiMZZMtz8P%2feuiupSYq8MKOV5mn3%2f%2fvaRL4TkWg%3d CR1220]<br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy-battery02.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy combination:<br /> #[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> = Programming the Zippy =<br /> All of the devices on the Zippy work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> = Setting the Real Time Clock (RTC) =<br /> To set the real time clock (RTC) on the Zippy board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Software =<br /> <br /> *[http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=8ded6c1580b907494b0ea95e36d91ca8d64122e8 patches in oe git]<br /> *Demo/Test Files<br /> **[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> **[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> **[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> **[[media:defconfig.txt|Kernel Config]]<br /> **[[media:zippy-0xdroid.patch|0xdroid kernel patch]]<br /> <br /> *place these files on your formated SD card per the instuctions at the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat] page<br /> *boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> All drivers are in the mainline kernel source:<br /> *ethernet - drivers/net/enc28j60.c<br /> *rtc - drivers/rtc/rtc-ds1307.c<br /> *uart - drivers/serial/8250.c<br /> *mmc - drivers/mmc/omap_hsmmc.c<br /> *eeprom - drivers/misc/eeprom/at24.c<br /> <br /> = System boot =<br /> <br /> &lt;pre&gt;<br /> Texas Instruments X-Loader 1.4.2 (Sep 9 2009 - 09:20:15)<br /> Reading boot sector<br /> Loading u-boot.bin from mmc<br /> <br /> <br /> U-Boot 2009.06-rc2 (Sep 09 2009 - 13:12:40)<br /> <br /> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz<br /> OMAP3 Beagle board + LPDDR/NAND<br /> DRAM: 256 MB<br /> NAND: 256 MiB<br /> *** Warning - bad CRC or NAND, using default environment<br /> <br /> In: serial<br /> Out: serial<br /> Err: serial<br /> Board revision C<br /> Die ID #197a0003000000000403230911004012<br /> Hit any key to stop autoboot: 0 <br /> mmc1 is available<br /> reading boot.scr<br /> <br /> ** Unable to read &quot;boot.scr&quot; from mmc 0:1 **<br /> reading uImage<br /> <br /> 2994264 bytes read<br /> Booting from mmc ...<br /> ## Booting kernel from Legacy Image at 82000000 ...<br /> Image Name: Angstrom/2.6.29/beagleboard<br /> Image Type: ARM Linux Kernel Image (uncompressed)<br /> Data Size: 2994200 Bytes = 2.9 MB<br /> Load Address: 80008000<br /> Entry Point: 80008000<br /> Verifying Checksum ... OK<br /> Loading Kernel Image ... OK<br /> OK<br /> <br /> Starting kernel ...<br /> <br /> Uncompressing Linux...................................................................................................................................................................................<br /> [ 0.000000] Linux version 2.6.29-omap1 (dave@linuxdev) (gcc version 4.3.3 (GCC) ) #6 PREEMPT Thu Sep 17 10:11:54 CDT 2009<br /> [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f<br /> [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache<br /> [ 0.000000] Machine: OMAP3 Beagle Board<br /> [ 0.000000] Memory policy: ECC disabled, Data cache writeback<br /> [ 0.000000] OMAP3430 ES3.0<br /> [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000<br /> [ 0.000000] Reserving 12582912 bytes SDRAM for VRAM<br /> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024<br /> [ 0.000000] Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait<br /> [ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz<br /> [ 0.000000] GPMC revision 5.0<br /> [ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts<br /> [ 0.000000] Total of 96 interrupts on 1 active controller<br /> [ 0.000000] OMAP34xx GPIO hardware version 2.5<br /> [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)<br /> [ 0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz<br /> [ 0.000000] Console: colour dummy device 80x30<br /> [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)<br /> [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)<br /> [ 0.000000] Memory: 128MB 128MB = 256MB total<br /> [ 0.000000] Memory: 240896KB available (5632K code, 575K data, 204K init)<br /> [ 0.000000] Calibrating delay loop... 486.31 BogoMIPS (lpj=1900544)<br /> [ 0.000000] Mount-cache hash table entries: 512<br /> [ 0.000000] CPU: Testing write buffer coherency: ok<br /> [ 0.000000] net_namespace: 1036 bytes<br /> [ 0.000000] regulator: core version 0.5<br /> [ 0.000000] NET: Registered protocol family 16<br /> [ 0.000000] Found NAND on CS0<br /> [ 0.000000] Registering NAND on CS0<br /> [ 19.307373] OMAP DMA hardware revision 4.0<br /> [ 19.353057] bio: create slab &lt;bio-0&gt; at 0<br /> [ 19.411468] OMAP DSS rev 2.0<br /> [ 19.411590] OMAP DISPC rev 3.0<br /> [ 19.411590] OMAP VENC rev 2<br /> [ 19.411773] OMAP DSI rev 1.0<br /> [ 19.414916] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz<br /> [ 19.418914] twl4030: PIH (irq 7) chaining IRQs 368..375<br /> [ 19.418945] twl4030: power (irq 373) chaining IRQs 376..383<br /> [ 19.419586] twl4030: gpio (irq 368) chaining IRQs 384..401<br /> [ 19.422668] regulator: VMMC1: 1850 &lt;--&gt; 3150 mV normal standby<br /> [ 19.423645] regulator: VDAC: 1800 mV normal standby<br /> [ 19.424560] regulator: VUSB1V5: 1500 &lt;--&gt; 0 mV normal standby<br /> [ 19.425506] regulator: VUSB1V8: 1800 &lt;--&gt; 0 mV normal standby<br /> [ 19.426422] regulator: VUSB3V1: 3100 &lt;--&gt; 0 mV normal standby<br /> [ 19.427398] regulator: VPLL2: 1800 mV normal standby<br /> [ 19.428375] regulator: VMMC2: 2800 &lt;--&gt; 3150 mV normal standby<br /> [ 19.429321] regulator: VSIM: 1800 &lt;--&gt; 3000 mV normal standby<br /> [ 19.441925] i2c_omap i2c_omap.2: bus 2 rev3.12 at 10 kHz<br /> [ 19.457122] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz<br /> [ 19.459289] SCSI subsystem initialized<br /> [ 19.462982] twl4030_usb twl4030_usb: Initialized TWL4030 USB module<br /> [ 19.464752] usbcore: registered new interface driver usbfs<br /> [ 19.465393] usbcore: registered new interface driver hub<br /> [ 19.465850] usbcore: registered new device driver usb<br /> [ 19.469146] Bluetooth: Core ver 2.14<br /> [ 19.469696] NET: Registered protocol family 31<br /> [ 19.469726] Bluetooth: HCI device and connection manager initialized<br /> [ 19.469757] Bluetooth: HCI socket layer initialized<br /> [ 19.470520] cfg80211: Using static regulatory domain info<br /> [ 19.470520] cfg80211: Regulatory domain: US<br /> [ 19.470550] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)<br /> [ 19.470581] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)<br /> [ 19.470581] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470611] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470672] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)<br /> [ 19.470703] cfg80211: Calling CRDA for country: US<br /> [ 19.474670] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0<br /> [ 19.477416] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92<br /> [ 19.478698] NET: Registered protocol family 2<br /> [ 19.478973] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)<br /> [ 19.479614] TCP established hash table entries: 8192 (order: 4, 65536 bytes)<br /> [ 19.479888] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)<br /> [ 19.480041] TCP: Hash tables configured (established 8192 bind 8192)<br /> [ 19.480072] TCP reno registered<br /> [ 19.480468] NET: Registered protocol family 1<br /> [ 19.484863] VFS: Disk quotas dquot_6.5.2<br /> [ 19.484985] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)<br /> [ 19.485626] squashfs: version 4.0 (2009/01/31) Phillip Lougher<br /> [ 19.486450] JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.<br /> [ 19.487457] msgmni has been set to 470<br /> [ 19.492523] alg: No test for stdrng (krng)<br /> [ 19.492645] io scheduler noop registered<br /> [ 19.492645] io scheduler anticipatory registered<br /> [ 19.492675] io scheduler deadline registered<br /> [ 19.492889] io scheduler cfq registered (default)<br /> [ 19.519348] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled<br /> [ 19.541748] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654<br /> [ 19.563201] serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654<br /> [ 19.583740] serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654<br /> [ 19.583801] console [ttyS2] enabled<br /> [ 20.108825] brd: module loaded<br /> [ 20.118408] loop: module loaded<br /> [ 20.122741] enc28j60 spi4.0: enc28j60 Ethernet driver 1.01 loaded<br /> [ 20.133117] net eth0: enc28j60 driver registered<br /> [ 20.139099] usbcore: registered new interface driver catc<br /> [ 20.144683] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver<br /> [ 20.150939] usbcore: registered new interface driver kaweth<br /> [ 20.156616] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver<br /> [ 20.164489] usbcore: registered new interface driver pegasus<br /> [ 20.170257] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver<br /> [ 20.177520] usbcore: registered new interface driver rtl8150<br /> [ 20.183563] usbcore: registered new interface driver asix<br /> [ 20.189300] usbcore: registered new interface driver cdc_ether<br /> [ 20.195495] usbcore: registered new interface driver dm9601<br /> [ 20.201507] usbcore: registered new interface driver smsc95xx<br /> [ 20.207641] usbcore: registered new interface driver gl620a<br /> [ 20.213531] usbcore: registered new interface driver net1080<br /> [ 20.219573] usbcore: registered new interface driver plusb<br /> [ 20.225463] usbcore: registered new interface driver rndis_host<br /> [ 20.231781] usbcore: registered new interface driver cdc_subset<br /> [ 20.238128] usbcore: registered new interface driver zaurus<br /> [ 20.244018] usbcore: registered new interface driver MOSCHIP usb-ethernet driver<br /> [ 20.251861] Broadcom 43xx driver loaded [ Features: L, Firmware-ID: FW13 ]<br /> [ 20.259307] usbcore: registered new interface driver zd1211rw<br /> [ 20.265441] usbcore: registered new interface driver rtl8187<br /> [ 20.271545] usbcore: registered new interface driver rndis_wlan<br /> [ 20.277832] usbcore: registered new interface driver zd1201<br /> [ 20.283813] usbcore: registered new interface driver usb8xxx<br /> [ 20.289916] usbcore: registered new interface driver rt2500usb<br /> [ 20.296173] usbcore: registered new interface driver rt73usb<br /> [ 20.302246] usbcore: registered new interface driver p54usb<br /> [ 20.307861] i2c /dev entries driver<br /> [ 20.313446] Driver 'sd' needs updating - please use bus_type methods<br /> [ 20.320220] Driver 'sr' needs updating - please use bus_type methods<br /> [ 20.327789] omap2-nand driver initializing<br /> [ 20.332305] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)<br /> [ 20.341369] cmdlinepart partition parsing not available<br /> [ 20.346649] Creating 5 MTD partitions on &quot;omap2-nand&quot;:<br /> [ 20.351867] 0x000000000000-0x000000080000 : &quot;X-Loader&quot;<br /> [ 20.359283] 0x000000080000-0x000000260000 : &quot;U-Boot&quot;<br /> [ 20.366485] 0x000000260000-0x000000280000 : &quot;U-Boot Env&quot;<br /> [ 20.373352] 0x000000280000-0x000000680000 : &quot;Kernel&quot;<br /> [ 20.381347] 0x000000680000-0x000010000000 : &quot;File System&quot;<br /> [ 20.494232] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br /> [ 20.501220] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller<br /> [ 20.507995] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1<br /> [ 20.515869] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800<br /> [ 20.534942] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00<br /> [ 20.541564] usb usb1: configuration #1 chosen from 1 choice<br /> [ 20.547698] hub 1-0:1.0: USB hub found<br /> [ 20.551635] hub 1-0:1.0: 3 ports detected<br /> [ 20.557983] Initializing USB Mass Storage driver...<br /> [ 20.563385] usbcore: registered new interface driver usb-storage<br /> [ 20.569519] USB Mass Storage support registered.<br /> [ 20.574920] mice: PS/2 mouse device common for all mice<br /> [ 20.580841] input: gpio-keys as /devices/platform/gpio-keys/input/input0<br /> [ 20.590545] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-0049/twl4030_pwrbutton/input/input1<br /> [ 20.605438] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc0<br /> [ 20.611663] rtc-ds1307 2-0068: 56 bytes nvram<br /> [ 20.617980] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec<br /> [ 20.624481] Bluetooth: HCI UART driver ver 2.2<br /> [ 20.628997] Bluetooth: HCI H4 protocol initialized<br /> [ 20.633819] Bluetooth: HCI BCSP protocol initialized<br /> [ 20.638885] Bluetooth: HCILL protocol initialized<br /> [ 20.643646] Bluetooth: Broadcom Blutonium firmware driver ver 1.2<br /> [ 20.650146] usbcore: registered new interface driver bcm203x<br /> [ 20.655944] Bluetooth: Digianswer Bluetooth USB driver ver 0.10<br /> [ 20.662445] usbcore: registered new interface driver bpa10x<br /> [ 20.668121] Bluetooth: BlueFRITZ! USB driver ver 1.2<br /> [ 20.673431] usbcore: registered new interface driver bfusb<br /> [ 20.679046] Bluetooth: Generic Bluetooth USB driver ver 0.4<br /> [ 20.685028] usbcore: registered new interface driver btusb<br /> [ 20.690582] Bluetooth: Generic Bluetooth SDIO driver ver 0.1<br /> [ 20.697509] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock<br /> [ 20.808563] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock<br /> [ 20.815155] regulator: Unable to get requested regulator: vmmc_aux<br /> [ 20.823669] Registered led device: beagleboard::usr0<br /> [ 20.829101] Registered led device: beagleboard::usr1<br /> [ 20.841583] usbcore: registered new interface driver usbhid<br /> [ 20.847229] usbhid: v2.6:USB HID core driver<br /> [ 20.852844] Advanced Linux Sound Architecture Driver Version 1.0.18a.<br /> [ 20.860321] usbcore: registered new interface driver snd-usb-audio<br /> [ 20.867004] No device for DAI twl4030<br /> [ 20.870910] No device for DAI omap-mcbsp-dai-0<br /> [ 20.875366] No device for DAI omap-mcbsp-dai-1<br /> [ 20.880004] No device for DAI omap-mcbsp-dai-2<br /> [ 20.884490] No device for DAI omap-mcbsp-dai-3<br /> [ 20.888977] No device for DAI omap-mcbsp-dai-4<br /> [ 20.893463] OMAP3 Beagle SoC init<br /> [ 20.897308] TWL4030 Audio Codec init <br /> [ 20.902618] asoc: twl4030 &lt;-&gt; omap-mcbsp-dai-0 mapping ok<br /> [ 20.918914] ALSA device list:<br /> [ 20.921905] #0: omap3beagle (twl4030)<br /> [ 20.934082] oprofile: using arm/armv7<br /> [ 20.938049] TCP cubic registered<br /> [ 20.941467] NET: Registered protocol family 17<br /> [ 20.945983] NET: Registered protocol family 15<br /> [ 20.950592] Bluetooth: L2CAP ver 2.11<br /> [ 20.954284] Bluetooth: L2CAP socket layer initialized<br /> [ 20.959411] Bluetooth: SCO (Voice Link) ver 0.6<br /> [ 20.963958] Bluetooth: SCO socket layer initialized<br /> [ 20.969116] Bluetooth: RFCOMM socket layer initialized<br /> [ 20.974365] Bluetooth: RFCOMM TTY layer initialized<br /> [ 20.979278] Bluetooth: RFCOMM ver 1.10<br /> [ 20.983123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3<br /> [ 20.988494] Bluetooth: BNEP filters: protocol multicast<br /> [ 20.993774] Bluetooth: HIDP (Human Interface Emulation) ver 1.2<br /> [ 21.002319] RPC: Registered udp transport module.<br /> [ 21.007110] RPC: Registered tcp transport module.<br /> [ 21.011993] lib80211: common routines for IEEE802.11 drivers<br /> [ 21.017761] ThumbEE CPU extension supported.<br /> [ 21.022094] Power Management for TI OMAP3.<br /> [ 21.035552] Disabling unused clock &quot;sr2_fck&quot;<br /> [ 21.039855] Disabling unused clock &quot;sr1_fck&quot;<br /> [ 21.044219] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.048675] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.053192] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.057678] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.062194] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.066680] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.071166] Disabling unused clock &quot;gpt2_ick&quot;<br /> [ 21.075592] Disabling unused clock &quot;gpt3_ick&quot;<br /> [ 21.079956] Disabling unused clock &quot;gpt4_ick&quot;<br /> [ 21.084381] Disabling unused clock &quot;gpt5_ick&quot;<br /> [ 21.088775] Disabling unused clock &quot;gpt6_ick&quot;<br /> [ 21.093200] Disabling unused clock &quot;gpt7_ick&quot;<br /> [ 21.097625] Disabling unused clock &quot;gpt8_ick&quot;<br /> [ 21.101989] Disabling unused clock &quot;gpt9_ick&quot;<br /> [ 21.106414] Disabling unused clock &quot;wdt3_ick&quot;<br /> [ 21.110809] Disabling unused clock &quot;wdt3_fck&quot;<br /> [ 21.115234] Disabling unused clock &quot;gpio2_dbck&quot;<br /> [ 21.119781] Disabling unused clock &quot;gpio3_dbck&quot;<br /> [ 21.124389] Disabling unused clock &quot;gpio4_dbck&quot;<br /> [ 21.128967] Disabling unused clock &quot;gpio5_dbck&quot;<br /> [ 21.133544] Disabling unused clock &quot;gpio6_dbck&quot;<br /> [ 21.138122] Disabling unused clock &quot;gpt9_fck&quot;<br /> [ 21.142517] Disabling unused clock &quot;gpt8_fck&quot;<br /> [ 21.146942] Disabling unused clock &quot;gpt7_fck&quot;<br /> [ 21.151336] Disabling unused clock &quot;gpt6_fck&quot;<br /> [ 21.155761] Disabling unused clock &quot;gpt5_fck&quot;<br /> [ 21.160156] Disabling unused clock &quot;gpt4_fck&quot;<br /> [ 21.164550] Disabling unused clock &quot;gpt3_fck&quot;<br /> [ 21.168975] Disabling unused clock &quot;gpt2_fck&quot;<br /> [ 21.173339] Disabling unused clock &quot;gpt1_ick&quot;<br /> [ 21.177764] Disabling unused clock &quot;wdt1_ick&quot;<br /> [ 21.182159] Disabling unused clock &quot;wdt2_ick&quot;<br /> [ 21.186584] Disabling unused clock &quot;wdt2_fck&quot;<br /> [ 21.190948] Disabling unused clock &quot;gpio1_dbck&quot;<br /> [ 21.195556] Disabling unused clock &quot;gpt1_fck&quot;<br /> [ 21.199981] Disabling unused clock &quot;cam_ick&quot;<br /> [ 21.204315] Disabling unused clock &quot;cam_mclk&quot;<br /> [ 21.208740] Disabling unused clock &quot;des1_ick&quot;<br /> [ 21.213134] Disabling unused clock &quot;sha11_ick&quot;<br /> [ 21.217620] Disabling unused clock &quot;rng_ick&quot;<br /> [ 21.221923] Disabling unused clock &quot;aes1_ick&quot;<br /> [ 21.226348] Disabling unused clock &quot;ssi_ick&quot;<br /> [ 21.230682] Disabling unused clock &quot;mailboxes_ick&quot;<br /> [ 21.235504] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.239990] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.244476] Disabling unused clock &quot;gpt10_ick&quot;<br /> [ 21.248992] Disabling unused clock &quot;gpt11_ick&quot;<br /> [ 21.253448] Disabling unused clock &quot;hdq_ick&quot;<br /> [ 21.257781] Disabling unused clock &quot;mspro_ick&quot;<br /> [ 21.262298] Disabling unused clock &quot;des2_ick&quot;<br /> [ 21.266693] Disabling unused clock &quot;sha12_ick&quot;<br /> [ 21.271179] Disabling unused clock &quot;aes2_ick&quot;<br /> [ 21.275573] Disabling unused clock &quot;icr_ick&quot;<br /> [ 21.279907] Disabling unused clock &quot;pka_ick&quot;<br /> [ 21.284210] Disabling unused clock &quot;ssi_ssr_fck&quot;<br /> [ 21.288879] Disabling unused clock &quot;hdq_fck&quot;<br /> [ 21.293212] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.297698] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.302185] Disabling unused clock &quot;mspro_fck&quot;<br /> [ 21.306671] Disabling unused clock &quot;gpt11_fck&quot;<br /> [ 21.311187] Disabling unused clock &quot;gpt10_fck&quot;<br /> [ 21.315643] Disabling unused clock &quot;dpll4_m6x2_ck&quot;<br /> [ 21.320526] Disabling unused clock &quot;dpll3_m3x2_ck&quot;<br /> [ 21.325378] Disabling unused clock &quot;sys_clkout1&quot;<br /> [ 21.330047] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1<br /> [ 21.342468] registered taskstats version 1<br /> [ 21.348236] fbcvt: 1024x768@60: CVT Name - .786M3-R<br /> [ 21.379608] Console: switching to colour frame buffer device 128x48<br /> [ 21.400665] clock: clksel_round_rate_div: dpll4_m4_ck target_rate 48000000<br /> [ 21.407592] clock: new_div = 9, new_rate = 48000000<br /> [ 21.417175] rtc-ds1307 2-0068: setting system clock to 2009-09-27 16:42:23 UTC (1254069743)<br /> [ 21.426086] Waiting for root device /dev/mmcblk0p2...<br /> [ 21.448944] mmc0: new high speed SD card at address ddce<br /> [ 21.455108] mmcblk0: mmc0:ddce SD02G 1.83 GiB <br /> [ 21.460021] mmcblk0: p1 p2<br /> [ 21.539916] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended<br /> [ 21.548187] kjournald starting. Commit interval 5 seconds<br /> [ 21.556823] EXT3 FS on mmcblk0p2, internal journal<br /> [ 21.561737] EXT3-fs: mounted filesystem with ordered data mode.<br /> [ 21.567779] VFS: Mounted root (ext3 filesystem) on device 179:2.<br /> [ 21.574066] Freeing init memory: 204K<br /> INIT: version 2.86 booting<br /> Please wait: booting...<br /> &lt;/pre&gt;<br /> <br /> = I2C analysis =<br /> <br /> Using [http://www.lm-sensors.org/wiki/I2CTools I2C tools] you can analyze the I2C bus:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -l<br /> i2c-1 i2c OMAP I2C adapter I2C adapter<br /> i2c-2 i2c OMAP I2C adapter I2C adapter<br /> i2c-3 i2c OMAP I2C adapter I2C adapter<br /> &lt;/pre&gt;<br /> <br /> Zippy Board uses i2c-2 for the RTC and EEPROM:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -y -r 2<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f<br /> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- <br /> 70: -- -- -- -- -- -- -- -- <br /> &lt;/pre&gt;<br /> <br /> * EEPROM is at 0x50<br /> * RTC is at 0x68<br /> <br /> =EEPROM=<br /> <br /> AT24 EEPROM ([http://www.atmel.com/dyn/resources/prod_documents/doc5156.pdf AT24C01B]) is used to identify Zippy board. See [[BeagleBoardPinMux#Expansion_boards|expansion board]] how this is done.<br /> <br /> Using Linux i2cdump tool at bus 2 address 0x50 the content of this EEPROM is given:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:~# i2cdump 2 0x50 b<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef<br /> 00: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 80: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> &lt;/pre&gt;<br /> <br /> <br /> = Schematic Diagram =<br /> <br /> * [[media:zippy_schematic.pdf|Zippy_schematic]]<br /> <br /> = Where to purchase the Zippy board =<br /> <br /> The Zippy board can be purchased from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16149&amp;cat=0&amp;page=1&amp;featured www.tincantools.com]<br /> <br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]<br /> <br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]<br /> <br /> <br /> [[Category:TinCanTools]]<br /> [[Category:BeagleBoard Expansion Boards]]<br /> [[Category:BeagleBoard]]</div>

Rkherod http://elinux.org/BeagleBoard_Trainer 2012-06-11T09:18:49Z

<p>Rkherod: </p> <hr /> <div>[[File:trainer1a.jpg|240px]]<br /> <br /> Trainer Features:<br /> * I2C interface(+3.3v or +5v selectable)<br /> ** Can be used with the [http://en.wikipedia.org/wiki/Wii_Remote#Nunchuk Nintendo Wii NunChuk] interface<br /> ** Pin compatible with [http://todbot.com/blog/2008/02/18/wiichuck-wii-nunchuck-adapter-available WiiChuk Adapter]<br /> ** WiiChuk Adapter is available from [http://www.sparkfun.com/commerce/product_info.php?products_id=9281 SparkFun]<br /> ** [[BeagleBoard_Trainer_Nunchuk|Wii Nunchuk project]]<br /> * SPI inteface (+3.3v)<br /> * GPIO's(+3.3v)<br /> * Large prototyping area (0.1&quot; x 0.1&quot; matrix with access to power bus)<br /> * Atmega328 processor (user programmable)<br /> ** Arduino compatible<br /> ** ATmega328 power is +3.3v or +5v selectable<br /> ** Communicate to the ATmega328 via the BeagleBoard's second RS-232 uart<br /> <br /> Available from [http://www.tincantools.com/product.php?productid=16149&amp;cat=0&amp;page=1&amp;featured www.tincantools.com]&lt;br&gt;&lt;br&gt;<br /> = Hardware =<br /> <br /> [[File:trainer2.jpg|800px| Trainer Rev-A]]<br /> <br /> <br /> [[File:Trainer Rev-A Interface 800.jpg|800px| Trainer Rev-A Interface]]<br /> <br /> <br /> == I²C Interface ==<br /> <br /> The Trainer provides an interface to the BeagleBoard's I²C port. The I²C signals are level translated to either +3.3V or +5V (user selectable with a jumper). The I²C signals are located next the the prototyping area.<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> == SPI Interface ==<br /> <br /> The Trainer provides an interface the the BeagleBoard's SPI port and the signals are level translated to +3.3V. The SPI signals are located next to the prototyping area.<br /> <br /> * [http://beagleboardxm.org/blog/2011/03/22/progress-spi-is-working-on-the-beagleboard-xm/ SPI is working on the BeagleBoard-xM]<br /> * Accessing the SPI interface<br /> **[http://www.kernel.org/doc/Documentation/spi/spidev user-space]<br /> **[http://www.kernel.org/doc/Documentation/spi/spi-summary kernel-space]<br /> <br /> == GPIO Interface ==<br /> <br /> The Trainer provides an interface to several of the BeagleBoard's GPIO signals. The GPIO signals are level translated to +3.3V and are located next to the prototyping area.<br /> <br /> == Serial EEPROM ==<br /> The Trainer board provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Trainer. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> == ATmega328 (Arduino Hardware Compatible) ==<br /> <br /> An ATmega328 embedded processor is located on the Trainer board that is user programmable. The ATmega328 is hardware compatible with the Arduino and it's I/O signals are available next to the prototyping area. The ATmega328 can be user jumpered to run at either +3.3V or +5V. One of the BeagleBoard's GPIO signals (GPIO 162) controls the ATmega328's power supply and can turn on or off the power to the ATmega328. The ATmega328 can run off it's internal RC oscillator or it also has an external 8.0 Mhz ceramic resonator.<br /> <br /> '''Note:''' The ATmega328 must be programmed with an external hardware programmer (not included) like the [http://www.sparkfun.com/commerce/product_info.php?products_id=9231 Pocket AVR Programmer] or the [http://www.mouser.com/ProductDetail/Atmel/ATAVRISP2/?qs=sGAEpiMZZMv256HIxPBQcA8%252bsNH3cLLR ATAVRISP2].<br /> <br /> * [http://www.atmel.com/dyn/products/product_card_mcu.asp?PN=ATmega328 Atmel Atmega328 Product Page]<br /> * Flash Programming<br /> ** [http://www.nongnu.org/avrdude/ AVRDUDE] software<br /> ** [http://www.sparkfun.com/commerce/categories.php?c=7 AVR ISP] hardware<br /> * [http://www.linuxjournal.com/article/7289?page=0,3 Introduction to programming Atmel AVR's under Linux]<br /> * [http://www.arduino.cc/ Arduino Homepage]<br /> * Arduino bootloader compatible with [http://code.google.com/p/arduino/source/browse/tags/latest/hardware/arduino/bootloaders/atmega/ATmegaBOOT_168_atmega328_pro_8MHz.hex ATmega328 Pro at 8MHz]<br /> * Arduino bootloader source can be found at [http://code.google.com/p/arduino/source/browse/#svn/tags/latest/hardware/arduino/bootloaders/atmega www.arduino.cc]<br /> * Arduino bootloader configuration using ISP programmer:<br /> &lt;pre&gt;<br /> avrdude -c usbtiny -p atmega328p -e -u -U lock:w:0x3f:m -U efuse:w:0x05:m -U hfuse:w:0xda:m -U lfuse:w:0xff:m<br /> avrdude -c usbtiny -p atmega328p -U flash:w:ATmegaBOOT_168_atmega328_pro_8MHz.hex -U lock:w:0x0f:m<br /> &lt;/pre&gt;<br /> * AVR code and Arduino sketches can be uploaded using avrdude on the BeagleBoard:<br /> &lt;pre&gt;<br /> avrdude -V -F -c stk500v1 -p m328p -P /dev/ttyS1 -b 57600 -U flash:w:main.hex<br /> &lt;/pre&gt;<br /> * AVR code and Arduino sketches can be uploaded using [[avrgal]] on the BeagleBoard:<br /> &lt;pre&gt;<br /> avrgal main.hex<br /> &lt;/pre&gt;<br /> <br /> == Prototyping / Breakout Area ==<br /> <br /> *provides a prototyping / breakout area with a standard 0.1&quot; x 0.1&quot; spacing matrix<br /> *Access to BeagleBoard's level translated signals<br /> *Access to the ATmega328's I/O pins<br /> <br /> = PC Board Test Point Locations =<br /> <br /> [[File:trainer_rev-a_tp_800.jpg|800px| Trainer Rev-A]]<br /> <br /> <br /> = PC Board Silkscreen Errata =<br /> <br /> There are errors on four silkscreen labels on the Trainer Rev-A board. The silkscreen for the signals: GP135, GP134, GP133, and GP132 are mislabeled. The correct labels are indicated on the following image:<br /> <br /> [[File:trainer_rev-a_errata_800.jpg|800px| Trainer Errata Rev-A]]<br /> <br /> <br /> Note: Trainer Rev-B has fixed these errors.<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy2-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy2-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy2-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy2-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy2-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy2-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Trainer board combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Trainer board combination:<br /> #[[media:MLO-trainer.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-trainer.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-trainer.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs3.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> = Trainer Schematics =<br /> <br /> The Trainer Rev-A schematic is avalible here:<br /> * [[media:Trainer_Rev-A1_schematic.pdf|Trainer_Rev-A1_schematic]]<br /> <br /> The Trainer Rev-B schematic is avalible here:<br /> * [[media:Trainer_Rev-B_schematic.pdf|Trainer_Rev-B_schematic]]<br /> <br /> = Where to purchase the Trainer board =<br /> <br /> The Trainer board can be purchased from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16149&amp;cat=0&amp;page=1&amp;featured www.tincantools.com]<br /> <br /> Canada: [http://www.robotcraft.ca/webshop/ www.robotcraft.ca]<br /> <br /> Germany: [http://www.watterott.com/index.php?page=product&amp;info=1494 www.watterott.com]<br /> <br /> = RevB Changes =<br /> <br /> * Fix the silkscreen errors on the signals: GP135, GP134, GP133, and GP132. They are currently mislabeled.<br /> * Change the pushbutton switch (S1 - ATMEL reset switch) to a different part. <br /> * Move TP58 (+5V) away from the mounting hole about 0.050 inches. It can sometimes short when the mounting screw touches it.<br /> * Add a 2x2 header break-out for the TXD and RXD signals going to the ATMEGA328.<br /> ** Some people want to be able to use the level translated serial signals to communicate with the Beagle/Beagle-xM instead of using it for the ATMEGA328.<br /> ** Add two traces on the back of the board connecting the two header holes so that jumper are not required.<br /> * Fix the footprint on the ceramic resonator.<br /> * Change the I2C level translator to a PCA9306. This will allow smaller pull-ups for the I2C signals going to the AT24C01 EEPROM.<br /> * Eliminate resistor network RN1 and replace it with three individual 2.2K pull-up resistors (0402).<br /> <br /> = Other Links =<br /> Makezine post about the Trainer Board is located [http://blog.makezine.com/archive/2010/09/playing-with-the-arduino-compatible.html here.]<br /> <br /> <br /> [[Category: BeagleBoard]]<br /> [[Category: BeagleBoard Expansion Boards]]<br /> [[Category: TinCanTools]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:26:21Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is a low cost LVDS LCD expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]. The <br /> <br /> The Animal LVDS Mini board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured here].<br /> <br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS 20455 Adapter Schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/TinCanTools 2012-04-21T01:24:54Z

<p>Rkherod: </p> <hr /> <div>[http://www.tincantools.com TinCanTools Website]<br /> <br /> <br /> Tin Can Tools was founded to respond to a need in the marketplace for high performance embedded processors and support boards. We design leading edge products but give you the ability to add features for your specific application.<br /> <br /> There are many manufacturers and suppliers of embedded products in today’s marketplace. We are different from the others because of the following: <br /> <br /> 1. We design and manufacture our own products. We control the quality and therefore <br /> maximize the flexibility and reliability of our products.<br /> 2. We design our products with connectors that simplify prototyping, soldering and<br /> testing. For example, instead of using high-density surface mount connectors,<br /> we intentionally design in headers and connectors with 0.1” lead spacing. This<br /> allows our customers to use standard prototyping boards and soldering tools.<br /> 3. Our designs are modular so that they are easy to integrate into our customer’s<br /> products and designs. You have the ability to use a “building block” design<br /> approach with our products. You can take the core functionality and add features<br /> to make it unique to your needs. <br /> 4. We take out the complexity of designing high end products by giving you a simple<br /> clean interface. This design approach maximizes the customer’s ability to<br /> configure our products. <br /> 5. Our designs are open. We furnish schematics and source code with each product.<br /> 6. 100% Satisfaction Guarantee. If for any reason you are not satisfied with our<br /> products, we offer a 30-day money back guarantee. <br /> <br /> Products:<br /> *[[Hammer Board]] - first of the product launches from TinCanTools<br /> *[[Flyswatter]] - FTDI FT2232 usb based [[JTAG]] device<br /> *[[Flyswatter2]] - FTDI FT2232H USB based [[JTAG]] device<br /> *[[Animal LVDS Mini Board]] - LVDS expansion board for BeagleBoard and PandaBoard<br /> *[[BeagleBoard_Zippy]] - Microchip ENC28J60 10baseT ethernet accessory board for the [[BeagleBoard]]<br /> *[[BeagleBoard_Zippy2]] - Micrel KSZ8851SNL 100baseT ethernet accessory board for the [[BeagleBoard]]<br /> *[[BeagleBoard_Trainer]] - Expansion bus breakout board for the [[BeagleBoard]]<br /> <br /> [http://linuxdevices.com/news/NS6212564523.html Hammer Press Release on Linuxdevices.com]<br /> <br /> Discussion of TinCanTools products is available on the #edev channel on irc.freenode.net<br /> <br /> [[Category:TinCanTools]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:22:40Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is a low cost expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]. The <br /> <br /> The Animal LVDS Mini board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured here].<br /> <br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS 20455 Adapter Schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:21:25Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]. The <br /> <br /> The Animal LVDS Mini board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured here].<br /> <br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS 20455 Adapter Schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:18:16Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]. The Animal LVDS Mini Board is designed by TinCanTools.com.<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS 20455 Adapter Schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:CLAA101NB01.pdf 2012-04-21T01:13:13Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/File:LVDS_20455_Adapter_schematic.pdf 2012-04-21T01:09:35Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:05:02Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS 20455 Adapter Schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:04:39Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Animal LVDS Mini Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS_20455_Adapter_schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:04:09Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS_20455_Adapter_schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCD Datasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T01:03:40Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:LVDS_20455_Adapter_schematic.pdf|LVDS_20455_Adapter_schematic]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> * [[Media:PQ3QI-01.pdf|Pixel Qi PQ3Qi-01 10.1&quot; LVDS LCDDatasheet]]<br /> * [[Media:CLAA101NB01.pdf|Chunghwa CLAA101NB01 10.1&quot; LVDS LCD Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:57:41Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:I-PEX_20455-040E-12.pdf‎ |I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:I-PEX_20455-040E-12.pdf 2012-04-21T00:55:10Z

<p>Rkherod: uploaded a new version of &amp;quot;File:I-PEX 20455-040E-12.pdf&amp;quot;</p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:53:38Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:20455-040E-12.pdf|I-PEX 20455-040E-12 surface mount LVDS connector]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:51:27Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:20455-040E-12.pdf|I-PEX 20455-040E-12 surface mount LVDS connector datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:50:05Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:I-PEX_20455-040E-12.pdf|I-PEX 20455-040E-12 surface mount LVDS connector datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:I-PEX_20455-040E-12.pdf 2012-04-21T00:48:38Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:48:12Z

<p>Rkherod: /* Design */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> * [[Media:I-PEX 20455-040E-12.pdf|I-PEX 20455-040E-12 surface mount LVDS connector datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:45:23Z

<p>Rkherod: /* Cable Connections */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be varied from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin ribbon cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:43:55Z

<p>Rkherod: /* Cable Connections */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable assembly length is 6&quot;. We intentionally kept this cable short to keep the cost down. You can use longer LVDS Cable assemblies without any problem.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:41:35Z

<p>Rkherod: /* Cable Connections */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> * Animal LVDS Mini Board - this board uses a standard 0.1&quot; x 0.1&quot; pitch 40-pin connector as it's output interface. It will interface to standard 40-pin ribbon cables (i.e. 40-pin IDE cables).<br /> * 40-pin Ribbon Cable - the length of this cable can be from 1&quot; to 36&quot; (we have tested cables up to 36&quot; in length).<br /> * LVDS 20455 Adapter - this board simply converts the 40-pin cable to a standard 40-pin LVDS surface mount connector (I-PEX p/n: 20455-040E-12). <br /> * LVDS Cable Assembly - this LVDS cable was kept short to keep the cost down.<br /> * LVDS LCD - standard LVDS LCD's (i.e. Pixel Qi 10.1&quot; PQ3Qi-01 or 10.1&quot; Chunghwa CLAA101NB01)<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:26:20Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|300px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|300px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:26:05Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|250px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|2500px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:24:44Z

<p>Rkherod: /* Cable Connections */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|800px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|800px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> The above picture illustrates the typical cable connections.<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:22:55Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|800px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|800px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:21:46Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:20:35Z

<p>Rkherod: /* Cable Connections */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:20:00Z

<p>Rkherod: /* Supported LCD Panels with IPEX 20455 Connector */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Cable Connections =<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:18:47Z

<p>Rkherod: /* Supported Boards */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard-xM<br /> * BeagleBoard Rev-C - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:Animal_LVDS_Mini_Cable_Connections.jpg 2012-04-21T00:17:01Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-21T00:16:40Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> [[File:Animal LVDS Mini Cable Connections.jpg|1024px| Animal LVDS Mini Cables]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard xM<br /> * BeagleBoard RevC - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Design =<br /> <br /> * [[media:animal_lvds_mini_schematic-a.pdf|Schematic]]<br /> * [[Media:sn75lvds83b.pdf| TI SN75VLDS83B Datasheet]]<br /> * [[Media:pca9633.pdf|NXP PCA9633 Datasheet]]<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-04-17T01:24:24Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for BeagleBoard Rev-C, BeagleBoard-xM, PandaBoard, PandaBoard-ES and compatible clones. For an introduction to LVDS display panels, please visit [[Elc-lcd|HERE]]<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|200px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|200px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Supported Boards =<br /> * BeagleBoard xM<br /> * BeagleBoard RevC - Note: requires headers to be populated<br /> * PandaBoard-ES (4460) - Note: requires headers to be populated<br /> * PandaBoard (4430) - Note: requires resistors and headers to be populated<br /> <br /> Note: there are wide range of BeagleBoard clones available on the open market. the Animal LVDS Mini may work with these board but are not tested or guaranteed to work with them.<br /> <br /> = Supported LCD Panels with IPEX 20455 Connector =<br /> <br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L Series<br /> * AUO B101AW01 Series <br /> * Samsung LTN101NT02 series <br /> * HANN STAR HSD101PFW2 series<br /> * Laptop Models Displays<br /> ** DELL MINI 10 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** Acer Aspire one (10.1&quot; LED BACKLIGHT PANEL)<br /> ** LENOVO IdeaPad S10-2 (10.1&quot; LED BACKLIGHT PANEL)<br /> ** ASUS Eee PC (10.1&quot; LED BACKLIGHT PANEL)<br /> ** HP 2133,2140/5101<br /> ** HP Mini 1000 / 210-1000 ~ 1099<br /> ** Compaq Mini 210c-1000~1099<br /> ** ACER DELL EPC10<br /> ** Lenovo S10-2<br /> <br /> = Design =<br /> <br /> * Schematic<br /> <br /> = Software Support =<br /> <br /> * Core display support uses the OMAP DSS driver.<br /> * Mainline support for the panel-generic-dpi driver<br /> * Support for the PWM backlight driver is provided as a patch.<br /> * Support will be provided for the following distros<br /> ** Ubuntu for PandaBoard<br /> ** Angstrom for PandaBoard and BeagleBoard<br /> ** AOSP(Android) for PandaBoard<br /> * other support will be provided on a case by case basis<br /> <br /> <br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Breakout Boards and cables available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> * Complete LCD kits available [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-03-13T01:00:40Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for the BeagleBoard, PandaBoard and compatible clones.<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|800px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|800px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Compatibility =<br /> == Boards ==<br /> * BeagleBoard RevC<br /> * BeagleBoard xM<br /> * PandaBoard 4430<br /> == LCD Panels ==<br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L02, N101L6-L03<br /> * more listings soon.....<br /> <br /> = Design =<br /> <br /> * Schematic<br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:Animal_LVDS_Mini_-Panda.jpg 2012-03-13T00:59:41Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-03-13T00:57:05Z

<p>Rkherod: </p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for the BeagleBoard, PandaBoard and compatible clones.<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|1024px| Animal LVDS Mini]]<br /> <br /> [[File:Animal LVDS Mini -Panda.jpg|1024px| Animal LVDS Mini - Panda]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Compatibility =<br /> == Boards ==<br /> * BeagleBoard RevC<br /> * BeagleBoard xM<br /> * PandaBoard 4430<br /> == LCD Panels ==<br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L02, N101L6-L03<br /> * more listings soon.....<br /> <br /> = Design =<br /> <br /> * Schematic<br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/File:Animal_LVDS_Mini.jpg 2012-03-13T00:54:26Z

<p>Rkherod: </p> <hr /> <div></div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-03-13T00:53:43Z

<p>Rkherod: /* Description */</p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for the BeagleBoard, PandaBoard and compatible clones.<br /> <br /> <br /> [[File:Animal LVDS Mini.jpg|1024px| Animal LVDS Mini]]<br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Compatibility =<br /> == Boards ==<br /> * BeagleBoard RevC<br /> * BeagleBoard xM<br /> * PandaBoard 4430<br /> == LCD Panels ==<br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L02, N101L6-L03<br /> * more listings soon.....<br /> <br /> = Design =<br /> <br /> * Schematic<br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/Animal_LVDS_Mini_Board 2012-03-13T00:24:36Z

<p>Rkherod: </p> <hr /> <div>= Description =<br /> <br /> Animal LVDS Mini Board is an expansion board for the BeagleBoard, PandaBoard and compatible clones.<br /> <br /> <br /> = Features =<br /> <br /> * I2C interface for EDID communication<br /> * 4 Backlight PWM/ENABLE controls<br /> * LVDS interface via a SN75LVDS83B<br /> ** 18-bit mode<br /> ** 24-bit 2-LSB mode<br /> * 3.3V I2C interface<br /> <br /> = Compatibility =<br /> == Boards ==<br /> * BeagleBoard RevC<br /> * BeagleBoard xM<br /> * PandaBoard 4430<br /> == LCD Panels ==<br /> * [http://www.pixelqi.com/products Pixel Qi Model 3QI] available from [http://www.makershed.com/ProductDetails.asp?ProductCode=MKPQ01 MakerShed]<br /> * LG LP101WSA-TLA1<br /> * ChiMei: N101L6-L02, N101L6-L03<br /> * more listings soon.....<br /> <br /> = Design =<br /> <br /> * Schematic<br /> <br /> = Availability =<br /> <br /> * Animal LVDS Mini will be available from [http://www.tincantools.com/product.php?productid=16158&amp;cat=0&amp;page=1&amp;featured TinCanTools]<br /> <br /> [[Category:BeagleBoard]]<br /> [[Category:PandaBoard]]</div>

Rkherod http://elinux.org/BeagleBoardJTAG 2011-10-21T15:56:13Z

<p>Rkherod: /* TinCanTools Flyswatter */</p> <hr /> <div>[[Category: Linux]]<br /> [[Category: OMAP]]<br /> [[Category:Development Boards]]<br /> [[Category: BeagleBoard]]<br /> The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].<br /> <br /> =Beagle JTAG connection=<br /> The [[BeagleBoard]] comes with a 14 pin [[JTAG-TI|TI JTAG]] connector. For JTAG pin out see section 8.16 of [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_B_5.pdf BeagleBoard HW Reference Manual (rev. B5)]. This is the same header interface as used in other TI products and is ''NOT'' the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a [[JTAG-TI|20-pin to 14-pin TI adapter]].<br /> <br /> '''Attention: JTAG on BeagleBoard uses 1.8V!'''<br /> <br /> The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Green Hills, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.<br /> <br /> The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:<br /> <br /> [[Image:Ti arm jtag.jpg]]<br /> <br /> Beagle uses the 14-pin TI header.<br /> <br /> Note: TI uses some different pin names. Translation:<br /> * TVD =&gt; VREF at Beagle<br /> * TCLKR == RTCK<br /> * TCLKO == TCK<br /> * #### == Key (empty))<br /> * TDIS =&gt; GND at Beagle<br /> <br /> See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.<br /> <br /> == Beagle adapter ==<br /> The [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] we plan to use has a 14 pin ARM layout, so we need to create a converter. From [http://www.tincantools.com/assets/JTAG_pin_assignments.pdf JTAG pin assignments] document:<br /> <br /> ''' ARM-14-JTAG TI-14-JTAG'''<br /> <br /> VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST<br /> JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND<br /> JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)<br /> JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND<br /> JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND<br /> JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND<br /> VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1<br /> FlySwatter TOP Beagle<br /> <br /> See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].<br /> <br /> * [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]<br /> * Nishanth Menon's [http://www.flickr.com/photos/nishanthmenon/2814595201/in/pool-beagleboard adapter] with explanation and [http://nishanthmenon.blogspot.com/2008/08/low-cost-jtag-for-beagle.html Nishanth's blog]<br /> * Lauterbach [http://www.lauterbach.com/frames.html?ord__7748.html JTAG converter to TI Target Adapter 14] (LA-7748) ([[media:Jtag-ti-front.jpg|front]] &amp; [[media:Jtag-ti-back.jpg|back]])<br /> * [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]<br /> <br /> = Open source JTAG software= <br /> It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is [http://openocd.berlios.de/web/ OpenOCD]. See [[BeagleBoardOpenOCD|Beagle board OpenOCD page]] about status and usage of OpenOCD for Beagle.<br /> <br /> =JTAG hardware=<br /> <br /> For BeagleBoard JTAG debugging, there are some HW interfaces available. Each is covered below.<br /> <br /> ==TinCanTools Flyswatter2==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a new JTAG debugger at [http://www.tincantools.com/product.php?productid=16153&amp;cat=0&amp;page=1&amp;featured Flyswatter2] that has support for OpenOCD and ARM Cortex A8 processors: OMAP3530 BeagleBoard and DM3730 BeagleBoard-xM. The Flyswatter2 is 5 to 10 times faster than the original Flyswatter. <br /> <br /> They also have a [http://www.tincantools.com/product.php?productid=16154&amp;cat=251&amp;page=1 ARM20TI14 JTAG Adapter]. This JTAG adapter board works with the BeagleBoard and BeagleBoard-xM.<br /> <br /> The Flyswatter2 can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support is complete).<br /> <br /> ==TinCanTools Flyswatter==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a working JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&amp;cat=0&amp;page=1&amp;featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br /> <br /> Costs:<br /> <br /> In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br /> <br /> * Flyswatter: US-$ 49.95<br /> * BeagleBoard Adapter Kit: US-$ 18.00<br /> * International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br /> * Video about using Flyswatter with BeagleBoard<br /> <br /> Sum: US-$ 94.95 =&gt; EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br /> <br /> Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support is complete).<br /> <br /> '''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 &amp; EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).<br /> <br /> ==BDI 2000==<br /> <br /> ===Example===<br /> <br /> [http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:<br /> <br /> The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:<br /> <br /> beagle&gt;reset<br /> - TARGET: processing reset request<br /> - TARGET: BDI executes scan chain init string<br /> - TARGET: Bypass check 0x00000001 =&gt; 0x00000002<br /> - TARGET: JTAG exists check passed<br /> - Core#0: ID code is 0x0B6D602F<br /> - Core#0: DP-CSW is 0xF0000000<br /> - Core#0: DBG-AP at 0xD4011000<br /> - Core#0: DIDR is 0x15141012<br /> - TARGET: BDI removes RESET<br /> - TARGET: BDI waits for RESET inactive<br /> - TARGET: Reset sequence passed<br /> - TARGET: resetting target passed<br /> - TARGET: processing target startup ....<br /> - TARGET: processing target startup passed<br /> beagle&gt;halt<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Debug Request<br /> Current PC : 0x40200000<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;rdall<br /> User FIQ Superv Abort IRQ Undef<br /> GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc<br /> GPR01: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR02: 00000001 00000001 00000001 00000001 00000001 00000001<br /> GPR03: 00000060 00000060 00000060 00000060 00000060 00000060<br /> GPR04: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88<br /> GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc<br /> GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8<br /> GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018<br /> GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc<br /> GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e<br /> GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045<br /> GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8<br /> PC : 40200000<br /> CPSR : 000001d3<br /> SPSR : 00000000 00000000 00000000 00000000 00000000<br /> beagle&gt;md 0x40200000<br /> 40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .<br /> 40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....<br /> 40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..<br /> 40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI<br /> 40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.<br /> 40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q&gt;.d.&lt;n..\_'=<br /> 40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m<br /> 40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%<br /> 40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$<br /> 40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5<br /> 402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..&lt;...b.)I..9<br /> 402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......<br /> 402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-<br /> 402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG&lt;.:W.j<br /> 402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]<br /> 402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200004<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200008<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;<br /> <br /> ===BDI config===<br /> <br /> The [ftp://94.230.212.16/bdigdb/config/arm/cortex-a/ BDI config files] might help getting OpenOCD to work with BeagleBoard.<br /> <br /> This configuration assumes the &quot;default&quot; EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) <br /> to enable access to the core:<br /> <br /> SCANINIT t1:w1000:t0:w1000: ;toggle TRST,<br /> SCANINIT ch10:w1000: ;clock TCK with TMS high and wait<br /> SCANINIT i6=07:d8=89:i6=02: ;connect and select router<br /> SCANINIT d32=81000080: ;IP control: KeepPowered<br /> SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive<br /> SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset<br /> SCANINIT d32=a3002148: ;enable TAP3<br /> SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass<br /> <br /> ==Lauterbach==<br /> <br /> Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].<br /> <br /> ==XDS100, XDS510, USB560 and CCSV4==<br /> <br /> Texas Instruments (TI) offers a set of JTAG emulators for debugging Beagle Board, and related, targets. These include the low-cost XDS100v2, and the higher-priced XDS510 et al. In addition, there is en Eclipse-based IDE called Code Composer Studio (ccs). As of early 2011, the latest version is [http://processors.wiki.ti.com/index.php/CCSv5_Getting_Started_Guide ccsv5], and it can be run on either a [http://processors.wiki.ti.com/index.php/Linux_Host_Support Linux host] or a Windows host. Debugging is possible in both [http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 run-mode and stop-mode].<br /> <br /> XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30.<br /> <br /> Some of these tools can be found on the [http://focus.ti.com/dsp/docs/dspfindtoolswresults.tsp?sectionId=3&amp;tabId=1620&amp;familyId=1526&amp;toolTypeId=12&amp;go=Go TI tools directory]. <br /> <br /> For CCS setup you see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).<br /> <br /> ===BeagleBoard Linux Kernel Aware Debugging using CCSV4===<br /> Linux Aware debugging using CCSV4 is described in [http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug CCSV4 Linux Aware Debugging]. CCSV4 is available for download from [http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 CCSV4].<br /> <br /> ====CCSV4 Current Status ====<br /> * CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.<br /> * Although CCSV4 is based on Eclipse, it will not work on Linux as there are currently no Linux Drivers for the JTAG Emulators. TI are developing Linux Drivers, but have not disclosed a release date<br /> * CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing<br /> * TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date<br /> * When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery<br /> * TI have produced a very good debugger, but there are still several bugs that TI are actively working to resolve and should be released in an update shortly. Most of these bugs are not show stoppers, but merely operational annoyances. <br /> * Blackhawk have released a $99 [http://www.blackhawk-dsp.com/products/usb100.aspx USB100], which is compatible with CCSV4. Please refer to [http://www.tiexpressdsp.com/index.php/XDS100 XDS100] about compatibility. Update: While CCSV4 does support XDB100, XDS100 does not yet support CortexA8 or C64X+. So, 4.02 (due in 11/09) will have XDS100 beagleboard support.<br /> <br /> ==PEEDI==<br /> <br /> [http://www.ronetix.at/peedi.html PEEDI] JTAG/BDM Emulator and Flash Programmer of [http://www.ronetix.at Ronetix] supports OMAP3. A configuration file for the Beagleboard can be found here: [http://download.ronetix.info/peedi/cfg_examples/cortex-a8/omap3530.cfg omap3530.cfg]<br /> <br /> PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.<br /> The Flash Programmer is capable to program:<br /> * NOR Flash devices (over 900)<br /> * NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.<br /> * DataFlash devices<br /> * SPI DataFlash devices<br /> * images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).<br /> <br /> The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.<br /> <br /> ===Linux Kernel Aware Debugging using PEEDI Emulator===<br /> * For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:<br /> * PEEDI JTAG emulator<br /> * Firmware version 9.8.216 or later<br /> * Arm Insight Debugger available on the Ronetix CDROM<br /> <br /> &lt;I&gt;Note: Enter all commands executed from the Linux Kernel build folder.&lt;/I&gt;<br /> <br /> ====Stopping the Debugger at start_kernel====<br /> * In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel<br /> * To obtain the address of start_kernel, use &quot;nm vmlinux |grep -w start_kernel&quot;<br /> * If your u-boot counts down from 10, you will need to extend the debugger timeout<br /> * Two lines down, change the line to &quot;wait 25000 stop&quot;<br /> * Power up the BeagleBoard and PEEDI<br /> * Let u-boot countdown and load the Linux Kernel<br /> * PEEDI will stop at &quot;start_kernel&quot;<br /> ====Launching the Insight Debugger====<br /> * Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder<br /> * From the Linux Kernel build folder type &quot;/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &amp;&quot;<br /> * In the Console Window, type &quot;target remote &lt;xxx.xxx.xxx.xxx&gt;:2000, where &lt;xxx.xxx.xxx.xxx&gt; is the BeagleBoard IP address<br /> * Next, type &quot;ni&quot;. The Source Window will load /init/main.c and highlight a line in start_kernel<br /> * Step through the code, or enter breakpoints and run the program. <br /> <br /> ====Thread List====<br /> * If you are doing multi-threaded debugging, this feature is invaluable<br /> * The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel<br /> * The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section<br /> * This information is obtained from the Insight GDB Console Window<br /> * print &amp;init_task ; BASE<br /> * print &amp;((struct task_struct*)0)-&gt;tasks.next ; NEXT<br /> * print &amp;((struct task_struct*)0)-&gt;pid ; PID<br /> * print &amp;((struct task_struct*)0)-&gt;comm ; NAME<br /> * print &amp;((struct task_struct*)0)-&gt;stack ; second CONTEXT arg<br /> * print &amp;((struct thread_info*)0)-&gt;cpu_context ; third CONTEXT arg<br /> <br /> For Linux Kernel v2.6.29, this section looks something like this:<br /> * BASE = 4, 0xC066B110<br /> * NEXT = 4, -0x1B8<br /> * PID = 4, 0x1E4<br /> * NAME = 16, 0x2DB<br /> * CONTEXT = 10*4, 0x4, 0x1C<br /> <br /> Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.<br /> <br /> Ronetix technical support is excellent and they added features like the Thread List in just over a week. When I reported what seemed like a bug, they fixed most of them in just a few days. Overall, I am very impressed with the PEEDI emulator and it works great with the BeagleBoard. PEEDI is certainly the most responsive emulator I have worked with and what I like most is it is one of the few that works natively within Linux.<br /> <br /> ==ARM RealView ICE==<br /> <br /> The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors. All you could buy RealviewICE at [http://www.realviewice.com]<br /> <br /> =Linux kernel debugging=<br /> <br /> If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[Debugging The Linux Kernel Using Gdb]] article.</div>

Rkherod http://elinux.org/BeagleBoardJTAG 2011-10-21T15:54:59Z

<p>Rkherod: /* TinCanTools Flyswatter2 */</p> <hr /> <div>[[Category: Linux]]<br /> [[Category: OMAP]]<br /> [[Category:Development Boards]]<br /> [[Category: BeagleBoard]]<br /> The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].<br /> <br /> =Beagle JTAG connection=<br /> The [[BeagleBoard]] comes with a 14 pin [[JTAG-TI|TI JTAG]] connector. For JTAG pin out see section 8.16 of [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_B_5.pdf BeagleBoard HW Reference Manual (rev. B5)]. This is the same header interface as used in other TI products and is ''NOT'' the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a [[JTAG-TI|20-pin to 14-pin TI adapter]].<br /> <br /> '''Attention: JTAG on BeagleBoard uses 1.8V!'''<br /> <br /> The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Green Hills, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.<br /> <br /> The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:<br /> <br /> [[Image:Ti arm jtag.jpg]]<br /> <br /> Beagle uses the 14-pin TI header.<br /> <br /> Note: TI uses some different pin names. Translation:<br /> * TVD =&gt; VREF at Beagle<br /> * TCLKR == RTCK<br /> * TCLKO == TCK<br /> * #### == Key (empty))<br /> * TDIS =&gt; GND at Beagle<br /> <br /> See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.<br /> <br /> == Beagle adapter ==<br /> The [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] we plan to use has a 14 pin ARM layout, so we need to create a converter. From [http://www.tincantools.com/assets/JTAG_pin_assignments.pdf JTAG pin assignments] document:<br /> <br /> ''' ARM-14-JTAG TI-14-JTAG'''<br /> <br /> VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST<br /> JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND<br /> JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)<br /> JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND<br /> JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND<br /> JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND<br /> VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1<br /> FlySwatter TOP Beagle<br /> <br /> See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].<br /> <br /> * [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]<br /> * Nishanth Menon's [http://www.flickr.com/photos/nishanthmenon/2814595201/in/pool-beagleboard adapter] with explanation and [http://nishanthmenon.blogspot.com/2008/08/low-cost-jtag-for-beagle.html Nishanth's blog]<br /> * Lauterbach [http://www.lauterbach.com/frames.html?ord__7748.html JTAG converter to TI Target Adapter 14] (LA-7748) ([[media:Jtag-ti-front.jpg|front]] &amp; [[media:Jtag-ti-back.jpg|back]])<br /> * [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]<br /> <br /> = Open source JTAG software= <br /> It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is [http://openocd.berlios.de/web/ OpenOCD]. See [[BeagleBoardOpenOCD|Beagle board OpenOCD page]] about status and usage of OpenOCD for Beagle.<br /> <br /> =JTAG hardware=<br /> <br /> For BeagleBoard JTAG debugging, there are some HW interfaces available. Each is covered below.<br /> <br /> ==TinCanTools Flyswatter2==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a new JTAG debugger at [http://www.tincantools.com/product.php?productid=16153&amp;cat=0&amp;page=1&amp;featured Flyswatter2] that has support for OpenOCD and ARM Cortex A8 processors: OMAP3530 BeagleBoard and DM3730 BeagleBoard-xM. The Flyswatter2 is 5 to 10 times faster than the original Flyswatter. <br /> <br /> They also have a [http://www.tincantools.com/product.php?productid=16154&amp;cat=251&amp;page=1 ARM20TI14 JTAG Adapter]. This JTAG adapter board works with the BeagleBoard and BeagleBoard-xM.<br /> <br /> The Flyswatter2 can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support is complete).<br /> <br /> ==TinCanTools Flyswatter==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a working JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&amp;cat=0&amp;page=1&amp;featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br /> <br /> Costs:<br /> <br /> In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br /> <br /> * Flyswatter: US-$ 49.95<br /> * BeagleBoard Adapter Kit: US-$ 18.00<br /> * International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br /> * Video about using Flyswatter with BeagleBoard<br /> <br /> Sum: US-$ 94.95 =&gt; EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br /> <br /> Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support under development).<br /> <br /> '''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 &amp; EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).<br /> <br /> ==BDI 2000==<br /> <br /> ===Example===<br /> <br /> [http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:<br /> <br /> The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:<br /> <br /> beagle&gt;reset<br /> - TARGET: processing reset request<br /> - TARGET: BDI executes scan chain init string<br /> - TARGET: Bypass check 0x00000001 =&gt; 0x00000002<br /> - TARGET: JTAG exists check passed<br /> - Core#0: ID code is 0x0B6D602F<br /> - Core#0: DP-CSW is 0xF0000000<br /> - Core#0: DBG-AP at 0xD4011000<br /> - Core#0: DIDR is 0x15141012<br /> - TARGET: BDI removes RESET<br /> - TARGET: BDI waits for RESET inactive<br /> - TARGET: Reset sequence passed<br /> - TARGET: resetting target passed<br /> - TARGET: processing target startup ....<br /> - TARGET: processing target startup passed<br /> beagle&gt;halt<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Debug Request<br /> Current PC : 0x40200000<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;rdall<br /> User FIQ Superv Abort IRQ Undef<br /> GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc<br /> GPR01: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR02: 00000001 00000001 00000001 00000001 00000001 00000001<br /> GPR03: 00000060 00000060 00000060 00000060 00000060 00000060<br /> GPR04: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88<br /> GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc<br /> GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8<br /> GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018<br /> GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc<br /> GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e<br /> GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045<br /> GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8<br /> PC : 40200000<br /> CPSR : 000001d3<br /> SPSR : 00000000 00000000 00000000 00000000 00000000<br /> beagle&gt;md 0x40200000<br /> 40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .<br /> 40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....<br /> 40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..<br /> 40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI<br /> 40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.<br /> 40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q&gt;.d.&lt;n..\_'=<br /> 40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m<br /> 40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%<br /> 40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$<br /> 40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5<br /> 402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..&lt;...b.)I..9<br /> 402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......<br /> 402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-<br /> 402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG&lt;.:W.j<br /> 402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]<br /> 402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200004<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200008<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;<br /> <br /> ===BDI config===<br /> <br /> The [ftp://94.230.212.16/bdigdb/config/arm/cortex-a/ BDI config files] might help getting OpenOCD to work with BeagleBoard.<br /> <br /> This configuration assumes the &quot;default&quot; EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) <br /> to enable access to the core:<br /> <br /> SCANINIT t1:w1000:t0:w1000: ;toggle TRST,<br /> SCANINIT ch10:w1000: ;clock TCK with TMS high and wait<br /> SCANINIT i6=07:d8=89:i6=02: ;connect and select router<br /> SCANINIT d32=81000080: ;IP control: KeepPowered<br /> SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive<br /> SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset<br /> SCANINIT d32=a3002148: ;enable TAP3<br /> SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass<br /> <br /> ==Lauterbach==<br /> <br /> Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].<br /> <br /> ==XDS100, XDS510, USB560 and CCSV4==<br /> <br /> Texas Instruments (TI) offers a set of JTAG emulators for debugging Beagle Board, and related, targets. These include the low-cost XDS100v2, and the higher-priced XDS510 et al. In addition, there is en Eclipse-based IDE called Code Composer Studio (ccs). As of early 2011, the latest version is [http://processors.wiki.ti.com/index.php/CCSv5_Getting_Started_Guide ccsv5], and it can be run on either a [http://processors.wiki.ti.com/index.php/Linux_Host_Support Linux host] or a Windows host. Debugging is possible in both [http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 run-mode and stop-mode].<br /> <br /> XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30.<br /> <br /> Some of these tools can be found on the [http://focus.ti.com/dsp/docs/dspfindtoolswresults.tsp?sectionId=3&amp;tabId=1620&amp;familyId=1526&amp;toolTypeId=12&amp;go=Go TI tools directory]. <br /> <br /> For CCS setup you see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).<br /> <br /> ===BeagleBoard Linux Kernel Aware Debugging using CCSV4===<br /> Linux Aware debugging using CCSV4 is described in [http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug CCSV4 Linux Aware Debugging]. CCSV4 is available for download from [http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 CCSV4].<br /> <br /> ====CCSV4 Current Status ====<br /> * CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.<br /> * Although CCSV4 is based on Eclipse, it will not work on Linux as there are currently no Linux Drivers for the JTAG Emulators. TI are developing Linux Drivers, but have not disclosed a release date<br /> * CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing<br /> * TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date<br /> * When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery<br /> * TI have produced a very good debugger, but there are still several bugs that TI are actively working to resolve and should be released in an update shortly. Most of these bugs are not show stoppers, but merely operational annoyances. <br /> * Blackhawk have released a $99 [http://www.blackhawk-dsp.com/products/usb100.aspx USB100], which is compatible with CCSV4. Please refer to [http://www.tiexpressdsp.com/index.php/XDS100 XDS100] about compatibility. Update: While CCSV4 does support XDB100, XDS100 does not yet support CortexA8 or C64X+. So, 4.02 (due in 11/09) will have XDS100 beagleboard support.<br /> <br /> ==PEEDI==<br /> <br /> [http://www.ronetix.at/peedi.html PEEDI] JTAG/BDM Emulator and Flash Programmer of [http://www.ronetix.at Ronetix] supports OMAP3. A configuration file for the Beagleboard can be found here: [http://download.ronetix.info/peedi/cfg_examples/cortex-a8/omap3530.cfg omap3530.cfg]<br /> <br /> PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.<br /> The Flash Programmer is capable to program:<br /> * NOR Flash devices (over 900)<br /> * NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.<br /> * DataFlash devices<br /> * SPI DataFlash devices<br /> * images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).<br /> <br /> The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.<br /> <br /> ===Linux Kernel Aware Debugging using PEEDI Emulator===<br /> * For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:<br /> * PEEDI JTAG emulator<br /> * Firmware version 9.8.216 or later<br /> * Arm Insight Debugger available on the Ronetix CDROM<br /> <br /> &lt;I&gt;Note: Enter all commands executed from the Linux Kernel build folder.&lt;/I&gt;<br /> <br /> ====Stopping the Debugger at start_kernel====<br /> * In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel<br /> * To obtain the address of start_kernel, use &quot;nm vmlinux |grep -w start_kernel&quot;<br /> * If your u-boot counts down from 10, you will need to extend the debugger timeout<br /> * Two lines down, change the line to &quot;wait 25000 stop&quot;<br /> * Power up the BeagleBoard and PEEDI<br /> * Let u-boot countdown and load the Linux Kernel<br /> * PEEDI will stop at &quot;start_kernel&quot;<br /> ====Launching the Insight Debugger====<br /> * Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder<br /> * From the Linux Kernel build folder type &quot;/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &amp;&quot;<br /> * In the Console Window, type &quot;target remote &lt;xxx.xxx.xxx.xxx&gt;:2000, where &lt;xxx.xxx.xxx.xxx&gt; is the BeagleBoard IP address<br /> * Next, type &quot;ni&quot;. The Source Window will load /init/main.c and highlight a line in start_kernel<br /> * Step through the code, or enter breakpoints and run the program. <br /> <br /> ====Thread List====<br /> * If you are doing multi-threaded debugging, this feature is invaluable<br /> * The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel<br /> * The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section<br /> * This information is obtained from the Insight GDB Console Window<br /> * print &amp;init_task ; BASE<br /> * print &amp;((struct task_struct*)0)-&gt;tasks.next ; NEXT<br /> * print &amp;((struct task_struct*)0)-&gt;pid ; PID<br /> * print &amp;((struct task_struct*)0)-&gt;comm ; NAME<br /> * print &amp;((struct task_struct*)0)-&gt;stack ; second CONTEXT arg<br /> * print &amp;((struct thread_info*)0)-&gt;cpu_context ; third CONTEXT arg<br /> <br /> For Linux Kernel v2.6.29, this section looks something like this:<br /> * BASE = 4, 0xC066B110<br /> * NEXT = 4, -0x1B8<br /> * PID = 4, 0x1E4<br /> * NAME = 16, 0x2DB<br /> * CONTEXT = 10*4, 0x4, 0x1C<br /> <br /> Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.<br /> <br /> Ronetix technical support is excellent and they added features like the Thread List in just over a week. When I reported what seemed like a bug, they fixed most of them in just a few days. Overall, I am very impressed with the PEEDI emulator and it works great with the BeagleBoard. PEEDI is certainly the most responsive emulator I have worked with and what I like most is it is one of the few that works natively within Linux.<br /> <br /> ==ARM RealView ICE==<br /> <br /> The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors. All you could buy RealviewICE at [http://www.realviewice.com]<br /> <br /> =Linux kernel debugging=<br /> <br /> If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[Debugging The Linux Kernel Using Gdb]] article.</div>

Rkherod http://elinux.org/BeagleBoardJTAG 2011-10-21T15:49:26Z

<p>Rkherod: /* TinCanTools Flyswatter */</p> <hr /> <div>[[Category: Linux]]<br /> [[Category: OMAP]]<br /> [[Category:Development Boards]]<br /> [[Category: BeagleBoard]]<br /> The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].<br /> <br /> =Beagle JTAG connection=<br /> The [[BeagleBoard]] comes with a 14 pin [[JTAG-TI|TI JTAG]] connector. For JTAG pin out see section 8.16 of [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_B_5.pdf BeagleBoard HW Reference Manual (rev. B5)]. This is the same header interface as used in other TI products and is ''NOT'' the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a [[JTAG-TI|20-pin to 14-pin TI adapter]].<br /> <br /> '''Attention: JTAG on BeagleBoard uses 1.8V!'''<br /> <br /> The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Green Hills, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.<br /> <br /> The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:<br /> <br /> [[Image:Ti arm jtag.jpg]]<br /> <br /> Beagle uses the 14-pin TI header.<br /> <br /> Note: TI uses some different pin names. Translation:<br /> * TVD =&gt; VREF at Beagle<br /> * TCLKR == RTCK<br /> * TCLKO == TCK<br /> * #### == Key (empty))<br /> * TDIS =&gt; GND at Beagle<br /> <br /> See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.<br /> <br /> == Beagle adapter ==<br /> The [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] we plan to use has a 14 pin ARM layout, so we need to create a converter. From [http://www.tincantools.com/assets/JTAG_pin_assignments.pdf JTAG pin assignments] document:<br /> <br /> ''' ARM-14-JTAG TI-14-JTAG'''<br /> <br /> VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST<br /> JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND<br /> JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)<br /> JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND<br /> JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND<br /> JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND<br /> VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1<br /> FlySwatter TOP Beagle<br /> <br /> See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].<br /> <br /> * [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]<br /> * Nishanth Menon's [http://www.flickr.com/photos/nishanthmenon/2814595201/in/pool-beagleboard adapter] with explanation and [http://nishanthmenon.blogspot.com/2008/08/low-cost-jtag-for-beagle.html Nishanth's blog]<br /> * Lauterbach [http://www.lauterbach.com/frames.html?ord__7748.html JTAG converter to TI Target Adapter 14] (LA-7748) ([[media:Jtag-ti-front.jpg|front]] &amp; [[media:Jtag-ti-back.jpg|back]])<br /> * [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]<br /> <br /> = Open source JTAG software= <br /> It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is [http://openocd.berlios.de/web/ OpenOCD]. See [[BeagleBoardOpenOCD|Beagle board OpenOCD page]] about status and usage of OpenOCD for Beagle.<br /> <br /> =JTAG hardware=<br /> <br /> For BeagleBoard JTAG debugging, there are some HW interfaces available. Each is covered below.<br /> <br /> ==TinCanTools Flyswatter2==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a new JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&amp;cat=0&amp;page=1&amp;featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br /> <br /> Costs:<br /> <br /> In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br /> <br /> * Flyswatter: US-$ 49.95<br /> * BeagleBoard Adapter Kit: US-$ 18.00<br /> * International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br /> * Video about using Flyswatter with BeagleBoard<br /> <br /> Sum: US-$ 94.95 =&gt; EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br /> <br /> Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support under development).<br /> <br /> '''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 &amp; EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).<br /> <br /> <br /> ==TinCanTools Flyswatter==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a working JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&amp;cat=0&amp;page=1&amp;featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br /> <br /> Costs:<br /> <br /> In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br /> <br /> * Flyswatter: US-$ 49.95<br /> * BeagleBoard Adapter Kit: US-$ 18.00<br /> * International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br /> * Video about using Flyswatter with BeagleBoard<br /> <br /> Sum: US-$ 94.95 =&gt; EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br /> <br /> Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support under development).<br /> <br /> '''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 &amp; EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).<br /> <br /> ==BDI 2000==<br /> <br /> ===Example===<br /> <br /> [http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:<br /> <br /> The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:<br /> <br /> beagle&gt;reset<br /> - TARGET: processing reset request<br /> - TARGET: BDI executes scan chain init string<br /> - TARGET: Bypass check 0x00000001 =&gt; 0x00000002<br /> - TARGET: JTAG exists check passed<br /> - Core#0: ID code is 0x0B6D602F<br /> - Core#0: DP-CSW is 0xF0000000<br /> - Core#0: DBG-AP at 0xD4011000<br /> - Core#0: DIDR is 0x15141012<br /> - TARGET: BDI removes RESET<br /> - TARGET: BDI waits for RESET inactive<br /> - TARGET: Reset sequence passed<br /> - TARGET: resetting target passed<br /> - TARGET: processing target startup ....<br /> - TARGET: processing target startup passed<br /> beagle&gt;halt<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Debug Request<br /> Current PC : 0x40200000<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;rdall<br /> User FIQ Superv Abort IRQ Undef<br /> GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc<br /> GPR01: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR02: 00000001 00000001 00000001 00000001 00000001 00000001<br /> GPR03: 00000060 00000060 00000060 00000060 00000060 00000060<br /> GPR04: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88<br /> GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc<br /> GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8<br /> GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018<br /> GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc<br /> GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e<br /> GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045<br /> GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8<br /> PC : 40200000<br /> CPSR : 000001d3<br /> SPSR : 00000000 00000000 00000000 00000000 00000000<br /> beagle&gt;md 0x40200000<br /> 40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .<br /> 40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....<br /> 40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..<br /> 40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI<br /> 40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.<br /> 40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q&gt;.d.&lt;n..\_'=<br /> 40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m<br /> 40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%<br /> 40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$<br /> 40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5<br /> 402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..&lt;...b.)I..9<br /> 402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......<br /> 402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-<br /> 402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG&lt;.:W.j<br /> 402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]<br /> 402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200004<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200008<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;<br /> <br /> ===BDI config===<br /> <br /> The [ftp://94.230.212.16/bdigdb/config/arm/cortex-a/ BDI config files] might help getting OpenOCD to work with BeagleBoard.<br /> <br /> This configuration assumes the &quot;default&quot; EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) <br /> to enable access to the core:<br /> <br /> SCANINIT t1:w1000:t0:w1000: ;toggle TRST,<br /> SCANINIT ch10:w1000: ;clock TCK with TMS high and wait<br /> SCANINIT i6=07:d8=89:i6=02: ;connect and select router<br /> SCANINIT d32=81000080: ;IP control: KeepPowered<br /> SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive<br /> SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset<br /> SCANINIT d32=a3002148: ;enable TAP3<br /> SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass<br /> <br /> ==Lauterbach==<br /> <br /> Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].<br /> <br /> ==XDS100, XDS510, USB560 and CCSV4==<br /> <br /> Texas Instruments (TI) offers a set of JTAG emulators for debugging Beagle Board, and related, targets. These include the low-cost XDS100v2, and the higher-priced XDS510 et al. In addition, there is en Eclipse-based IDE called Code Composer Studio (ccs). As of early 2011, the latest version is [http://processors.wiki.ti.com/index.php/CCSv5_Getting_Started_Guide ccsv5], and it can be run on either a [http://processors.wiki.ti.com/index.php/Linux_Host_Support Linux host] or a Windows host. Debugging is possible in both [http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 run-mode and stop-mode].<br /> <br /> XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30.<br /> <br /> Some of these tools can be found on the [http://focus.ti.com/dsp/docs/dspfindtoolswresults.tsp?sectionId=3&amp;tabId=1620&amp;familyId=1526&amp;toolTypeId=12&amp;go=Go TI tools directory]. <br /> <br /> For CCS setup you see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).<br /> <br /> ===BeagleBoard Linux Kernel Aware Debugging using CCSV4===<br /> Linux Aware debugging using CCSV4 is described in [http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug CCSV4 Linux Aware Debugging]. CCSV4 is available for download from [http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 CCSV4].<br /> <br /> ====CCSV4 Current Status ====<br /> * CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.<br /> * Although CCSV4 is based on Eclipse, it will not work on Linux as there are currently no Linux Drivers for the JTAG Emulators. TI are developing Linux Drivers, but have not disclosed a release date<br /> * CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing<br /> * TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date<br /> * When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery<br /> * TI have produced a very good debugger, but there are still several bugs that TI are actively working to resolve and should be released in an update shortly. Most of these bugs are not show stoppers, but merely operational annoyances. <br /> * Blackhawk have released a $99 [http://www.blackhawk-dsp.com/products/usb100.aspx USB100], which is compatible with CCSV4. Please refer to [http://www.tiexpressdsp.com/index.php/XDS100 XDS100] about compatibility. Update: While CCSV4 does support XDB100, XDS100 does not yet support CortexA8 or C64X+. So, 4.02 (due in 11/09) will have XDS100 beagleboard support.<br /> <br /> ==PEEDI==<br /> <br /> [http://www.ronetix.at/peedi.html PEEDI] JTAG/BDM Emulator and Flash Programmer of [http://www.ronetix.at Ronetix] supports OMAP3. A configuration file for the Beagleboard can be found here: [http://download.ronetix.info/peedi/cfg_examples/cortex-a8/omap3530.cfg omap3530.cfg]<br /> <br /> PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.<br /> The Flash Programmer is capable to program:<br /> * NOR Flash devices (over 900)<br /> * NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.<br /> * DataFlash devices<br /> * SPI DataFlash devices<br /> * images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).<br /> <br /> The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.<br /> <br /> ===Linux Kernel Aware Debugging using PEEDI Emulator===<br /> * For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:<br /> * PEEDI JTAG emulator<br /> * Firmware version 9.8.216 or later<br /> * Arm Insight Debugger available on the Ronetix CDROM<br /> <br /> &lt;I&gt;Note: Enter all commands executed from the Linux Kernel build folder.&lt;/I&gt;<br /> <br /> ====Stopping the Debugger at start_kernel====<br /> * In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel<br /> * To obtain the address of start_kernel, use &quot;nm vmlinux |grep -w start_kernel&quot;<br /> * If your u-boot counts down from 10, you will need to extend the debugger timeout<br /> * Two lines down, change the line to &quot;wait 25000 stop&quot;<br /> * Power up the BeagleBoard and PEEDI<br /> * Let u-boot countdown and load the Linux Kernel<br /> * PEEDI will stop at &quot;start_kernel&quot;<br /> ====Launching the Insight Debugger====<br /> * Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder<br /> * From the Linux Kernel build folder type &quot;/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &amp;&quot;<br /> * In the Console Window, type &quot;target remote &lt;xxx.xxx.xxx.xxx&gt;:2000, where &lt;xxx.xxx.xxx.xxx&gt; is the BeagleBoard IP address<br /> * Next, type &quot;ni&quot;. The Source Window will load /init/main.c and highlight a line in start_kernel<br /> * Step through the code, or enter breakpoints and run the program. <br /> <br /> ====Thread List====<br /> * If you are doing multi-threaded debugging, this feature is invaluable<br /> * The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel<br /> * The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section<br /> * This information is obtained from the Insight GDB Console Window<br /> * print &amp;init_task ; BASE<br /> * print &amp;((struct task_struct*)0)-&gt;tasks.next ; NEXT<br /> * print &amp;((struct task_struct*)0)-&gt;pid ; PID<br /> * print &amp;((struct task_struct*)0)-&gt;comm ; NAME<br /> * print &amp;((struct task_struct*)0)-&gt;stack ; second CONTEXT arg<br /> * print &amp;((struct thread_info*)0)-&gt;cpu_context ; third CONTEXT arg<br /> <br /> For Linux Kernel v2.6.29, this section looks something like this:<br /> * BASE = 4, 0xC066B110<br /> * NEXT = 4, -0x1B8<br /> * PID = 4, 0x1E4<br /> * NAME = 16, 0x2DB<br /> * CONTEXT = 10*4, 0x4, 0x1C<br /> <br /> Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.<br /> <br /> Ronetix technical support is excellent and they added features like the Thread List in just over a week. When I reported what seemed like a bug, they fixed most of them in just a few days. Overall, I am very impressed with the PEEDI emulator and it works great with the BeagleBoard. PEEDI is certainly the most responsive emulator I have worked with and what I like most is it is one of the few that works natively within Linux.<br /> <br /> ==ARM RealView ICE==<br /> <br /> The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors. All you could buy RealviewICE at [http://www.realviewice.com]<br /> <br /> =Linux kernel debugging=<br /> <br /> If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[Debugging The Linux Kernel Using Gdb]] article.</div>

Rkherod http://elinux.org/BeagleBoardJTAG 2011-10-21T15:47:36Z

<p>Rkherod: /* TinCanTools Flyswatter */</p> <hr /> <div>[[Category: Linux]]<br /> [[Category: OMAP]]<br /> [[Category:Development Boards]]<br /> [[Category: BeagleBoard]]<br /> The page is about [http://en.wikipedia.org/wiki/JTAG JTAG] on OMAP3530 used at [[BeagleBoard|BeagleBoard]].<br /> <br /> =Beagle JTAG connection=<br /> The [[BeagleBoard]] comes with a 14 pin [[JTAG-TI|TI JTAG]] connector. For JTAG pin out see section 8.16 of [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_B_5.pdf BeagleBoard HW Reference Manual (rev. B5)]. This is the same header interface as used in other TI products and is ''NOT'' the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a [[JTAG-TI|20-pin to 14-pin TI adapter]].<br /> <br /> '''Attention: JTAG on BeagleBoard uses 1.8V!'''<br /> <br /> The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Green Hills, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.<br /> <br /> The following picture is from a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation]:<br /> <br /> [[Image:Ti arm jtag.jpg]]<br /> <br /> Beagle uses the 14-pin TI header.<br /> <br /> Note: TI uses some different pin names. Translation:<br /> * TVD =&gt; VREF at Beagle<br /> * TCLKR == RTCK<br /> * TCLKO == TCK<br /> * #### == Key (empty))<br /> * TDIS =&gt; GND at Beagle<br /> <br /> See [[OMAP3530_ICEPICK|ICEPICK configuration page]] for more details about how OMAP3 JTAG hardware needs to be configured.<br /> <br /> == Beagle adapter ==<br /> The [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] we plan to use has a 14 pin ARM layout, so we need to create a converter. From [http://www.tincantools.com/assets/JTAG_pin_assignments.pdf JTAG pin assignments] document:<br /> <br /> ''' ARM-14-JTAG TI-14-JTAG'''<br /> <br /> VREF 1 - - 2 GND JTAG_TMS 1 - - 2 JTAG_nTRST<br /> JTAG_nTRST 3 - - 4 GND JTAG_TDI 3 - - 4 GND<br /> JTAG_TDI 5 - - 6 GND VREF 5 - x 6 KEY (empty)<br /> JTAG_TMS 7 - - 8 GND JTAG_TDO 7 - - 8 GND<br /> JTAG_TCK 9 - - 10 GND JTAG_RTCK 9 - - 10 GND<br /> JTAG_TDO 11 - - 12 JTAG_SRST_N JTAG_TCK 11 - - 12 GND<br /> VREF 13 - - 14 GND JTAG_EMU0 13 - - 14 JTAG_EMU1<br /> FlySwatter TOP Beagle<br /> <br /> See [[media:flyswatter-ti-jtag.pdf|14 pin ARM to TI adapter]] for a verified JTAG adapter from [http://www.tincantools.com/ TinCanTools].<br /> <br /> * [http://tincantools.com/product.php?productid=16144 TinCanTools BeagleBoard Adapter Kit]<br /> * Nishanth Menon's [http://www.flickr.com/photos/nishanthmenon/2814595201/in/pool-beagleboard adapter] with explanation and [http://nishanthmenon.blogspot.com/2008/08/low-cost-jtag-for-beagle.html Nishanth's blog]<br /> * Lauterbach [http://www.lauterbach.com/frames.html?ord__7748.html JTAG converter to TI Target Adapter 14] (LA-7748) ([[media:Jtag-ti-front.jpg|front]] &amp; [[media:Jtag-ti-back.jpg|back]])<br /> * [http://www.flickr.com/photos/51025379@N00/2822556950/in/photostream/ xdaiabx adapter]<br /> <br /> = Open source JTAG software= <br /> It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is [http://openocd.berlios.de/web/ OpenOCD]. See [[BeagleBoardOpenOCD|Beagle board OpenOCD page]] about status and usage of OpenOCD for Beagle.<br /> <br /> =JTAG hardware=<br /> <br /> For BeagleBoard JTAG debugging, there are some HW interfaces available. Each is covered below.<br /> <br /> ==TinCanTools Flyswatter==<br /> <br /> [http://www.tincantools.com/ TinCanTools] has a working JTAG debugger at [http://www.tincantools.com/product.php?productid=16134&amp;cat=0&amp;page=1&amp;featured Flyswatter] that has support for OpenOCD and the OMAP3530 (ARM Cortex A8). They also have a [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit].<br /> <br /> Costs:<br /> <br /> In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):<br /> <br /> * Flyswatter: US-$ 49.95<br /> * BeagleBoard Adapter Kit: US-$ 18.00<br /> * International shipping: US-$ 27.00 (select USPS, it's the cheapest!)<br /> * Video about using Flyswatter with BeagleBoard<br /> <br /> Sum: US-$ 94.95 =&gt; EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04<br /> <br /> Flyswatter can be used with [[BeagleBoardJTAG#Open_source_JTAG_software|OpenOCD]] (Beagle (OMAP3xx) support under development).<br /> <br /> '''Attention''': If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way (in contrast to the picture EMU0 &amp; EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2) because EMU0 and EMU1 must be set in order for the ICEpick JTAG TAP router within the DM37x to be the only device exposed after power on, which is what OpenOCD expects to see).<br /> <br /> ==BDI 2000==<br /> <br /> ===Example===<br /> <br /> [http://groups.google.com/group/beagleboard/msg/8463086de562ee00 Chuck Fleming] reports:<br /> <br /> The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:<br /> <br /> beagle&gt;reset<br /> - TARGET: processing reset request<br /> - TARGET: BDI executes scan chain init string<br /> - TARGET: Bypass check 0x00000001 =&gt; 0x00000002<br /> - TARGET: JTAG exists check passed<br /> - Core#0: ID code is 0x0B6D602F<br /> - Core#0: DP-CSW is 0xF0000000<br /> - Core#0: DBG-AP at 0xD4011000<br /> - Core#0: DIDR is 0x15141012<br /> - TARGET: BDI removes RESET<br /> - TARGET: BDI waits for RESET inactive<br /> - TARGET: Reset sequence passed<br /> - TARGET: resetting target passed<br /> - TARGET: processing target startup ....<br /> - TARGET: processing target startup passed<br /> beagle&gt;halt<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Debug Request<br /> Current PC : 0x40200000<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;rdall<br /> User FIQ Superv Abort IRQ Undef<br /> GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc<br /> GPR01: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR02: 00000001 00000001 00000001 00000001 00000001 00000001<br /> GPR03: 00000060 00000060 00000060 00000060 00000060 00000060<br /> GPR04: 00000000 00000000 00000000 00000000 00000000 00000000<br /> GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4<br /> GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88<br /> GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc<br /> GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8<br /> GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018<br /> GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc<br /> GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e<br /> GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045<br /> GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8<br /> PC : 40200000<br /> CPSR : 000001d3<br /> SPSR : 00000000 00000000 00000000 00000000 00000000<br /> beagle&gt;md 0x40200000<br /> 40200000 : e320f000 e320f000 e320f000 e320f000 .. ... ... ... .<br /> 40200010 : e320f000 e320f000 e320f000 eafffffc .. ... ... .....<br /> 40200020 : b6273502 e7aa052b 047694c8 91ca77d8 .5'.+.....v..w..<br /> 40200030 : 12b9579e ef2eef1b 00543892 494f9bc1 .W.......8T...OI<br /> 40200040 : 3f63013d 82eee656 b7adfe8d 993f1368 =.c?V.......h.?.<br /> 40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c ...Q&gt;.d.&lt;n..\_'=<br /> 40200060 : 76554290 6776c892 a6cd088f 6dd4529a .BUv..vg.....R.m<br /> 40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95 .ar.....u.N....%<br /> 40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6 ...w{Y..Z._}.L.$<br /> 40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8 .F......zV4...5<br /> 402000a0 : a16b6760 fe863cf7 29046202 39fb0d49 `gk..&lt;...b.)I..9<br /> 402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91 ....lS...f......<br /> 402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e ..k...y.......;-<br /> 402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a ...CG...RG&lt;.:W.j<br /> 402000e0 : 3570da77 9a1dc961 324b876c 5d592060 w.p5a...l.K2` Y]<br /> 402000f0 : b870f487 1277c035 4609dcf4 53b534c4 ..p.5.w....F.4.S<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200004<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;ti<br /> Core number : 0<br /> Core state : debug mode (ARM)<br /> Debug entry cause : Single Step<br /> Current PC : 0x40200008<br /> Current CPSR : 0x000001d3 (Supervisor)<br /> beagle&gt;<br /> <br /> ===BDI config===<br /> <br /> The [ftp://94.230.212.16/bdigdb/config/arm/cortex-a/ BDI config files] might help getting OpenOCD to work with BeagleBoard.<br /> <br /> This configuration assumes the &quot;default&quot; EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) <br /> to enable access to the core:<br /> <br /> SCANINIT t1:w1000:t0:w1000: ;toggle TRST,<br /> SCANINIT ch10:w1000: ;clock TCK with TMS high and wait<br /> SCANINIT i6=07:d8=89:i6=02: ;connect and select router<br /> SCANINIT d32=81000080: ;IP control: KeepPowered<br /> SCANINIT d32=a3002048: ;TAP3: DebugConnect, ForcePower, ForceActive<br /> SCANINIT d32=81000081: ;IP control: KeepPowered, SysReset<br /> SCANINIT d32=a3002148: ;enable TAP3<br /> SCANINIT cl10:i10=ffff ;clock 10 times in RTI, scan bypass<br /> <br /> ==Lauterbach==<br /> <br /> Lauterbach Debugger supports [http://www.lauterbach.com/news_288.html OMAP3503/15/25/30].<br /> <br /> ==XDS100, XDS510, USB560 and CCSV4==<br /> <br /> Texas Instruments (TI) offers a set of JTAG emulators for debugging Beagle Board, and related, targets. These include the low-cost XDS100v2, and the higher-priced XDS510 et al. In addition, there is en Eclipse-based IDE called Code Composer Studio (ccs). As of early 2011, the latest version is [http://processors.wiki.ti.com/index.php/CCSv5_Getting_Started_Guide ccsv5], and it can be run on either a [http://processors.wiki.ti.com/index.php/Linux_Host_Support Linux host] or a Windows host. Debugging is possible in both [http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5 run-mode and stop-mode].<br /> <br /> XDS510, BlackHawk USB560 and CCSV4 (code composer studio) can be used to debug OMAP3503/15/25/30.<br /> <br /> Some of these tools can be found on the [http://focus.ti.com/dsp/docs/dspfindtoolswresults.tsp?sectionId=3&amp;tabId=1620&amp;familyId=1526&amp;toolTypeId=12&amp;go=Go TI tools directory]. <br /> <br /> For CCS setup you see [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf TI OMAP JTAG presentation], too (start page: 16).<br /> <br /> ===BeagleBoard Linux Kernel Aware Debugging using CCSV4===<br /> Linux Aware debugging using CCSV4 is described in [http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug CCSV4 Linux Aware Debugging]. CCSV4 is available for download from [http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4 CCSV4].<br /> <br /> ====CCSV4 Current Status ====<br /> * CCSV4 is a Windows based application, which means that Linux Kernel Code compiled an a Linux machine must be shared using NFS for SAMBA.<br /> * Although CCSV4 is based on Eclipse, it will not work on Linux as there are currently no Linux Drivers for the JTAG Emulators. TI are developing Linux Drivers, but have not disclosed a release date<br /> * CCSV4 is based on Eclipse V3.1.0, which means that many of the features added through Eclipse based V3.4.2 are missing<br /> * TI are updating CCSV4 to use Eclipse V3.4.2, but have not disclosed a release date<br /> * When TI release CCSV4 using Eclipse V3.4.2, I expect TI to release a CCSV4 plugin for Code Sourcery<br /> * TI have produced a very good debugger, but there are still several bugs that TI are actively working to resolve and should be released in an update shortly. Most of these bugs are not show stoppers, but merely operational annoyances. <br /> * Blackhawk have released a $99 [http://www.blackhawk-dsp.com/products/usb100.aspx USB100], which is compatible with CCSV4. Please refer to [http://www.tiexpressdsp.com/index.php/XDS100 XDS100] about compatibility. Update: While CCSV4 does support XDB100, XDS100 does not yet support CortexA8 or C64X+. So, 4.02 (due in 11/09) will have XDS100 beagleboard support.<br /> <br /> ==PEEDI==<br /> <br /> [http://www.ronetix.at/peedi.html PEEDI] JTAG/BDM Emulator and Flash Programmer of [http://www.ronetix.at Ronetix] supports OMAP3. A configuration file for the Beagleboard can be found here: [http://download.ronetix.info/peedi/cfg_examples/cortex-a8/omap3530.cfg omap3530.cfg]<br /> <br /> PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.<br /> The Flash Programmer is capable to program:<br /> * NOR Flash devices (over 900)<br /> * NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.<br /> * DataFlash devices<br /> * SPI DataFlash devices<br /> * images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).<br /> <br /> The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.<br /> <br /> ===Linux Kernel Aware Debugging using PEEDI Emulator===<br /> * For Linux Aware debugging, PEEDI is a great solution. Here is what you will need:<br /> * PEEDI JTAG emulator<br /> * Firmware version 9.8.216 or later<br /> * Arm Insight Debugger available on the Ronetix CDROM<br /> <br /> &lt;I&gt;Note: Enter all commands executed from the Linux Kernel build folder.&lt;/I&gt;<br /> <br /> ====Stopping the Debugger at start_kernel====<br /> * In OMAP3530.CFG, change the hardware breakpoint address in the [INIT_LINUX] section to the address of start_kernel<br /> * To obtain the address of start_kernel, use &quot;nm vmlinux |grep -w start_kernel&quot;<br /> * If your u-boot counts down from 10, you will need to extend the debugger timeout<br /> * Two lines down, change the line to &quot;wait 25000 stop&quot;<br /> * Power up the BeagleBoard and PEEDI<br /> * Let u-boot countdown and load the Linux Kernel<br /> * PEEDI will stop at &quot;start_kernel&quot;<br /> ====Launching the Insight Debugger====<br /> * Install the ARM Insight Debbugger from the Ronetix CDROM, which is normally installed in the /opt folder<br /> * From the Linux Kernel build folder type &quot;/opt/arm-linux-4.3.3/bin/arm-linux-insight vmlinux &amp;&quot;<br /> * In the Console Window, type &quot;target remote &lt;xxx.xxx.xxx.xxx&gt;:2000, where &lt;xxx.xxx.xxx.xxx&gt; is the BeagleBoard IP address<br /> * Next, type &quot;ni&quot;. The Source Window will load /init/main.c and highlight a line in start_kernel<br /> * Step through the code, or enter breakpoints and run the program. <br /> <br /> ====Thread List====<br /> * If you are doing multi-threaded debugging, this feature is invaluable<br /> * The PEEDI config file (OMAP3530.CFG) must be setup to read this info from your kernel<br /> * The information needed by Insight GDB is in the [OS_ARM_LINUX_v26] section<br /> * This information is obtained from the Insight GDB Console Window<br /> * print &amp;init_task ; BASE<br /> * print &amp;((struct task_struct*)0)-&gt;tasks.next ; NEXT<br /> * print &amp;((struct task_struct*)0)-&gt;pid ; PID<br /> * print &amp;((struct task_struct*)0)-&gt;comm ; NAME<br /> * print &amp;((struct task_struct*)0)-&gt;stack ; second CONTEXT arg<br /> * print &amp;((struct thread_info*)0)-&gt;cpu_context ; third CONTEXT arg<br /> <br /> For Linux Kernel v2.6.29, this section looks something like this:<br /> * BASE = 4, 0xC066B110<br /> * NEXT = 4, -0x1B8<br /> * PID = 4, 0x1E4<br /> * NAME = 16, 0x2DB<br /> * CONTEXT = 10*4, 0x4, 0x1C<br /> <br /> Note: the BASE address will most definitely be different to the one provided here, but the other values should be similar.<br /> <br /> Ronetix technical support is excellent and they added features like the Thread List in just over a week. When I reported what seemed like a bug, they fixed most of them in just a few days. Overall, I am very impressed with the PEEDI emulator and it works great with the BeagleBoard. PEEDI is certainly the most responsive emulator I have worked with and what I like most is it is one of the few that works natively within Linux.<br /> <br /> ==ARM RealView ICE==<br /> <br /> The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors. All you could buy RealviewICE at [http://www.realviewice.com]<br /> <br /> =Linux kernel debugging=<br /> <br /> If you like to debug Linux kernel (with one of the above JTAG tools?) using GDB have a look to [[Debugging The Linux Kernel Using Gdb]] article.</div>

Rkherod http://elinux.org/BeagleBoard_Zippy2 2011-07-27T14:20:15Z

<p>Rkherod: </p> <hr /> <div>[[File:zippy2-base.jpg|400px]]<br /> <br /> The Zippy2 Ethernet Combo Board (KSZ8851SNL-BBE-EVAL) is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10/100BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> <br /> The Zippy2 (KSZ8851SNL-BBE-EVAL) board was jointly developed by [http://www.micrel.com Micrel] and [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here].<br /> . <br /> <br /> <br /> <br /> = Hardware =<br /> == Ethernet ==<br /> The Zippy2 provides a standard 10/100BaseT (10/100 Mbit) Ethernet interface and uses Micrel's [http://www.micrel.com/page.do?page=/product-info/embedded_control.jsp KSZ8851SNL] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy2 provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy2 provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy2 provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy2 and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy2-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy2-battery2.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy2 provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy2 provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy2. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy2-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy2-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy2-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy2-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy2-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy2-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy2 combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy2 combination:<br /> #[[media:MLO-zippy2.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy2.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy2.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs2.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> = Automated script to create a bootable SD card =<br /> <br /> The following script will create a formatted SD card using your Linux PC. <br /> <br /> *[[media:mksdcard2.sh| mksdcard.sh]]<br /> <br /> Make a working directory for the files: mksdcard.sh, MLO, u-boot.bin, uImage, and test-rootfs.tar.gz and copy them into it. <br /> <br /> You will also need to make two mount points:<br /> <br /> mkdir /mnt/sdcard1<br /> mkdir /mnt/sdcard2<br /> <br /> Then from inside the working directory you created above, issue the command like this:<br /> <br /> ./mksdcard.sh /dev/sdb<br /> <br /> Where /dev/sdb is the drive for the SD card.<br /> <br /> This should generate a fresh bootable SD card for you!<br /> <br /> = Design Documents =<br /> The following are the design documents for the Zippy2 (KSZ8851SNL-BBE-EVAL) board:<br /> * [[media:zippy2_schematic.pdf|Zippy2_schematic]] <br /> * [[media:zippy2_gerbers.zip|Zippy2_gerbers.zip]]<br /> * [[media:zippy2_BOM.pdf|Zippy2_BOM.pdf]]<br /> <br /> = Software Links =<br /> <br /> The latest Linux driver for the KSZ8851SNL is included in the mainline Linux kernel and can be downloaded here:<br /> <br /> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.7.tar.bz2<br /> <br /> Also, Linus' GIT repo can be pulled from here:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary<br /> <br /> Or you can view just the driver:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/ks8851.c;h=6d3ac65bc35cfcd1ae3eb27e6249a8be38efe705;hb=HEAD<br /> <br /> = Programming the Zippy2 =<br /> All of the devices on the Zippy2 work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> <br /> To set the real time clock (RTC) on the Zippy2 board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Where to purchase the Zippy2 (KSZ8851SNL-BBE-EVAL)=<br /> <br /> The Zippy2 can be purchased from TinCanTools.com<br /> [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here.]<br /> [[Category: BeagleBoard]]<br /> [[Category: BeagleBoard Expansion Boards]]<br /> [[Category: TinCanTools]]</div>

Rkherod http://elinux.org/BeagleBoard_Zippy2 2011-07-27T14:20:01Z

<p>Rkherod: </p> <hr /> <div>[[File:zippy2-base.jpg|400px]]<br /> <br /> The Zippy2 Ethernet Combo Board (KSZ8851SNL-BBE-EVAL) is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10/100BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> <br /> The Zippy2 (KSZ8851SNL-BBE-EVAL) board was jointly developed by [http://www.micrel.com Micrel] and [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 | here].<br /> . <br /> <br /> <br /> <br /> = Hardware =<br /> == Ethernet ==<br /> The Zippy2 provides a standard 10/100BaseT (10/100 Mbit) Ethernet interface and uses Micrel's [http://www.micrel.com/page.do?page=/product-info/embedded_control.jsp KSZ8851SNL] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy2 provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy2 provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy2 provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy2 and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy2-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy2-battery2.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy2 provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy2 provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy2. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy2-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy2-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy2-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy2-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy2-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy2-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy2 combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy2 combination:<br /> #[[media:MLO-zippy2.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy2.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy2.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs2.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> = Automated script to create a bootable SD card =<br /> <br /> The following script will create a formatted SD card using your Linux PC. <br /> <br /> *[[media:mksdcard2.sh| mksdcard.sh]]<br /> <br /> Make a working directory for the files: mksdcard.sh, MLO, u-boot.bin, uImage, and test-rootfs.tar.gz and copy them into it. <br /> <br /> You will also need to make two mount points:<br /> <br /> mkdir /mnt/sdcard1<br /> mkdir /mnt/sdcard2<br /> <br /> Then from inside the working directory you created above, issue the command like this:<br /> <br /> ./mksdcard.sh /dev/sdb<br /> <br /> Where /dev/sdb is the drive for the SD card.<br /> <br /> This should generate a fresh bootable SD card for you!<br /> <br /> = Design Documents =<br /> The following are the design documents for the Zippy2 (KSZ8851SNL-BBE-EVAL) board:<br /> * [[media:zippy2_schematic.pdf|Zippy2_schematic]] <br /> * [[media:zippy2_gerbers.zip|Zippy2_gerbers.zip]]<br /> * [[media:zippy2_BOM.pdf|Zippy2_BOM.pdf]]<br /> <br /> = Software Links =<br /> <br /> The latest Linux driver for the KSZ8851SNL is included in the mainline Linux kernel and can be downloaded here:<br /> <br /> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.7.tar.bz2<br /> <br /> Also, Linus' GIT repo can be pulled from here:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary<br /> <br /> Or you can view just the driver:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/ks8851.c;h=6d3ac65bc35cfcd1ae3eb27e6249a8be38efe705;hb=HEAD<br /> <br /> = Programming the Zippy2 =<br /> All of the devices on the Zippy2 work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> <br /> To set the real time clock (RTC) on the Zippy2 board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Where to purchase the Zippy2 (KSZ8851SNL-BBE-EVAL)=<br /> <br /> The Zippy2 can be purchased from TinCanTools.com<br /> [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here.]<br /> [[Category: BeagleBoard]]<br /> [[Category: BeagleBoard Expansion Boards]]<br /> [[Category: TinCanTools]]</div>

Rkherod http://elinux.org/BeagleBoard_Zippy2 2011-07-27T14:19:21Z

<p>Rkherod: </p> <hr /> <div>[[File:zippy2-base.jpg|400px]]<br /> <br /> The Zippy2 Ethernet Combo Board (KSZ8851SNL-BBE-EVAL) is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10/100BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> <br /> The Zippy2 (KSZ8851SNL-BBE-EVAL) board was jointly developed by [http://www.micrel.com Micrel] and [[TinCanTools]] ([http://www.tincantools.com Company Website]) and is available here[http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1].<br /> . <br /> <br /> <br /> <br /> = Hardware =<br /> == Ethernet ==<br /> The Zippy2 provides a standard 10/100BaseT (10/100 Mbit) Ethernet interface and uses Micrel's [http://www.micrel.com/page.do?page=/product-info/embedded_control.jsp KSZ8851SNL] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy2 provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy2 provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy2 provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy2 and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy2-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy2-battery2.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy2 provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy2 provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy2. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy2-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy2-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy2-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy2-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy2-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy2-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy2-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy2 combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy2 combination:<br /> #[[media:MLO-zippy2.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy2.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy2.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs2.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> = Automated script to create a bootable SD card =<br /> <br /> The following script will create a formatted SD card using your Linux PC. <br /> <br /> *[[media:mksdcard2.sh| mksdcard.sh]]<br /> <br /> Make a working directory for the files: mksdcard.sh, MLO, u-boot.bin, uImage, and test-rootfs.tar.gz and copy them into it. <br /> <br /> You will also need to make two mount points:<br /> <br /> mkdir /mnt/sdcard1<br /> mkdir /mnt/sdcard2<br /> <br /> Then from inside the working directory you created above, issue the command like this:<br /> <br /> ./mksdcard.sh /dev/sdb<br /> <br /> Where /dev/sdb is the drive for the SD card.<br /> <br /> This should generate a fresh bootable SD card for you!<br /> <br /> = Design Documents =<br /> The following are the design documents for the Zippy2 (KSZ8851SNL-BBE-EVAL) board:<br /> * [[media:zippy2_schematic.pdf|Zippy2_schematic]] <br /> * [[media:zippy2_gerbers.zip|Zippy2_gerbers.zip]]<br /> * [[media:zippy2_BOM.pdf|Zippy2_BOM.pdf]]<br /> <br /> = Software Links =<br /> <br /> The latest Linux driver for the KSZ8851SNL is included in the mainline Linux kernel and can be downloaded here:<br /> <br /> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.7.tar.bz2<br /> <br /> Also, Linus' GIT repo can be pulled from here:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary<br /> <br /> Or you can view just the driver:<br /> <br /> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/ks8851.c;h=6d3ac65bc35cfcd1ae3eb27e6249a8be38efe705;hb=HEAD<br /> <br /> = Programming the Zippy2 =<br /> All of the devices on the Zippy2 work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> <br /> To set the real time clock (RTC) on the Zippy2 board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Where to purchase the Zippy2 (KSZ8851SNL-BBE-EVAL)=<br /> <br /> The Zippy2 can be purchased from TinCanTools.com<br /> [http://www.tincantools.com/product.php?productid=16148&amp;cat=255&amp;page=1 here.]<br /> [[Category: BeagleBoard]]<br /> [[Category: BeagleBoard Expansion Boards]]<br /> [[Category: TinCanTools]]</div>

Rkherod http://elinux.org/BeagleBoard_Zippy 2011-06-23T18:05:06Z

<p>Rkherod: </p> <hr /> <div>[[File:zippy-base.jpg|400px]]<br /> <br /> <br /> The Zippy board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]). <br /> <br /> You can purchase the Zippy board from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16147 www.tincantools.com]&lt;br&gt;<br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]&lt;br&gt;<br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]&lt;br&gt;<br /> &lt;br&gt;<br /> == Hardware ==<br /> The BeagleBuddy Zippy Ethernet Combo Board is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> == Ethernet ==<br /> The Zippy provides a standard 10BaseT (10/100 Mbit) Ethernet interface and uses Microchip's [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en022889 ENC28J60] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> Compatible batteries are available from Mouser Electronics:<br /> <br /> [http://www.mouser.com/ProductDetail/Renata/CR1220TS/?qs=sGAEpiMZZMtz8P%2feuiupSd2F%2fX%2ffEmeEyLDGD5JMOeY%3d CR1220]<br /> <br /> [http://www.mouser.com/ProductDetail/Sanyo-Batteries/CR1220-SANYO/?qs=sGAEpiMZZMtz8P%2feuiupSYq8MKOV5mn3%2f%2fvaRL4TkWg%3d CR1220]<br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy-battery02.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy combination:<br /> #[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> = Programming the Zippy =<br /> All of the devices on the Zippy work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> = Setting the Real Time Clock (RTC) =<br /> To set the real time clock (RTC) on the Zippy board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Software =<br /> <br /> *[http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=8ded6c1580b907494b0ea95e36d91ca8d64122e8 patches in oe git]<br /> *Demo/Test Files<br /> **[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> **[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> **[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> **[[media:defconfig.txt|Kernel Config]]<br /> **[[media:zippy-0xdroid.patch|0xdroid kernel patch]]<br /> <br /> *place these files on your formated SD card per the instuctions at the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat] page<br /> *boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> All drivers are in the mainline kernel source:<br /> *ethernet - drivers/net/enc28j60.c<br /> *rtc - drivers/rtc/rtc-ds1307.c<br /> *uart - drivers/serial/8250.c<br /> *mmc - drivers/mmc/omap_hsmmc.c<br /> *eeprom - drivers/misc/eeprom/at24.c<br /> <br /> = System boot =<br /> <br /> &lt;pre&gt;<br /> Texas Instruments X-Loader 1.4.2 (Sep 9 2009 - 09:20:15)<br /> Reading boot sector<br /> Loading u-boot.bin from mmc<br /> <br /> <br /> U-Boot 2009.06-rc2 (Sep 09 2009 - 13:12:40)<br /> <br /> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz<br /> OMAP3 Beagle board + LPDDR/NAND<br /> DRAM: 256 MB<br /> NAND: 256 MiB<br /> *** Warning - bad CRC or NAND, using default environment<br /> <br /> In: serial<br /> Out: serial<br /> Err: serial<br /> Board revision C<br /> Die ID #197a0003000000000403230911004012<br /> Hit any key to stop autoboot: 0 <br /> mmc1 is available<br /> reading boot.scr<br /> <br /> ** Unable to read &quot;boot.scr&quot; from mmc 0:1 **<br /> reading uImage<br /> <br /> 2994264 bytes read<br /> Booting from mmc ...<br /> ## Booting kernel from Legacy Image at 82000000 ...<br /> Image Name: Angstrom/2.6.29/beagleboard<br /> Image Type: ARM Linux Kernel Image (uncompressed)<br /> Data Size: 2994200 Bytes = 2.9 MB<br /> Load Address: 80008000<br /> Entry Point: 80008000<br /> Verifying Checksum ... OK<br /> Loading Kernel Image ... OK<br /> OK<br /> <br /> Starting kernel ...<br /> <br /> Uncompressing Linux...................................................................................................................................................................................<br /> [ 0.000000] Linux version 2.6.29-omap1 (dave@linuxdev) (gcc version 4.3.3 (GCC) ) #6 PREEMPT Thu Sep 17 10:11:54 CDT 2009<br /> [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f<br /> [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache<br /> [ 0.000000] Machine: OMAP3 Beagle Board<br /> [ 0.000000] Memory policy: ECC disabled, Data cache writeback<br /> [ 0.000000] OMAP3430 ES3.0<br /> [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000<br /> [ 0.000000] Reserving 12582912 bytes SDRAM for VRAM<br /> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024<br /> [ 0.000000] Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait<br /> [ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz<br /> [ 0.000000] GPMC revision 5.0<br /> [ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts<br /> [ 0.000000] Total of 96 interrupts on 1 active controller<br /> [ 0.000000] OMAP34xx GPIO hardware version 2.5<br /> [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)<br /> [ 0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz<br /> [ 0.000000] Console: colour dummy device 80x30<br /> [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)<br /> [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)<br /> [ 0.000000] Memory: 128MB 128MB = 256MB total<br /> [ 0.000000] Memory: 240896KB available (5632K code, 575K data, 204K init)<br /> [ 0.000000] Calibrating delay loop... 486.31 BogoMIPS (lpj=1900544)<br /> [ 0.000000] Mount-cache hash table entries: 512<br /> [ 0.000000] CPU: Testing write buffer coherency: ok<br /> [ 0.000000] net_namespace: 1036 bytes<br /> [ 0.000000] regulator: core version 0.5<br /> [ 0.000000] NET: Registered protocol family 16<br /> [ 0.000000] Found NAND on CS0<br /> [ 0.000000] Registering NAND on CS0<br /> [ 19.307373] OMAP DMA hardware revision 4.0<br /> [ 19.353057] bio: create slab &lt;bio-0&gt; at 0<br /> [ 19.411468] OMAP DSS rev 2.0<br /> [ 19.411590] OMAP DISPC rev 3.0<br /> [ 19.411590] OMAP VENC rev 2<br /> [ 19.411773] OMAP DSI rev 1.0<br /> [ 19.414916] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz<br /> [ 19.418914] twl4030: PIH (irq 7) chaining IRQs 368..375<br /> [ 19.418945] twl4030: power (irq 373) chaining IRQs 376..383<br /> [ 19.419586] twl4030: gpio (irq 368) chaining IRQs 384..401<br /> [ 19.422668] regulator: VMMC1: 1850 &lt;--&gt; 3150 mV normal standby<br /> [ 19.423645] regulator: VDAC: 1800 mV normal standby<br /> [ 19.424560] regulator: VUSB1V5: 1500 &lt;--&gt; 0 mV normal standby<br /> [ 19.425506] regulator: VUSB1V8: 1800 &lt;--&gt; 0 mV normal standby<br /> [ 19.426422] regulator: VUSB3V1: 3100 &lt;--&gt; 0 mV normal standby<br /> [ 19.427398] regulator: VPLL2: 1800 mV normal standby<br /> [ 19.428375] regulator: VMMC2: 2800 &lt;--&gt; 3150 mV normal standby<br /> [ 19.429321] regulator: VSIM: 1800 &lt;--&gt; 3000 mV normal standby<br /> [ 19.441925] i2c_omap i2c_omap.2: bus 2 rev3.12 at 10 kHz<br /> [ 19.457122] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz<br /> [ 19.459289] SCSI subsystem initialized<br /> [ 19.462982] twl4030_usb twl4030_usb: Initialized TWL4030 USB module<br /> [ 19.464752] usbcore: registered new interface driver usbfs<br /> [ 19.465393] usbcore: registered new interface driver hub<br /> [ 19.465850] usbcore: registered new device driver usb<br /> [ 19.469146] Bluetooth: Core ver 2.14<br /> [ 19.469696] NET: Registered protocol family 31<br /> [ 19.469726] Bluetooth: HCI device and connection manager initialized<br /> [ 19.469757] Bluetooth: HCI socket layer initialized<br /> [ 19.470520] cfg80211: Using static regulatory domain info<br /> [ 19.470520] cfg80211: Regulatory domain: US<br /> [ 19.470550] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)<br /> [ 19.470581] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)<br /> [ 19.470581] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470611] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470672] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)<br /> [ 19.470703] cfg80211: Calling CRDA for country: US<br /> [ 19.474670] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0<br /> [ 19.477416] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92<br /> [ 19.478698] NET: Registered protocol family 2<br /> [ 19.478973] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)<br /> [ 19.479614] TCP established hash table entries: 8192 (order: 4, 65536 bytes)<br /> [ 19.479888] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)<br /> [ 19.480041] TCP: Hash tables configured (established 8192 bind 8192)<br /> [ 19.480072] TCP reno registered<br /> [ 19.480468] NET: Registered protocol family 1<br /> [ 19.484863] VFS: Disk quotas dquot_6.5.2<br /> [ 19.484985] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)<br /> [ 19.485626] squashfs: version 4.0 (2009/01/31) Phillip Lougher<br /> [ 19.486450] JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.<br /> [ 19.487457] msgmni has been set to 470<br /> [ 19.492523] alg: No test for stdrng (krng)<br /> [ 19.492645] io scheduler noop registered<br /> [ 19.492645] io scheduler anticipatory registered<br /> [ 19.492675] io scheduler deadline registered<br /> [ 19.492889] io scheduler cfq registered (default)<br /> [ 19.519348] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled<br /> [ 19.541748] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654<br /> [ 19.563201] serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654<br /> [ 19.583740] serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654<br /> [ 19.583801] console [ttyS2] enabled<br /> [ 20.108825] brd: module loaded<br /> [ 20.118408] loop: module loaded<br /> [ 20.122741] enc28j60 spi4.0: enc28j60 Ethernet driver 1.01 loaded<br /> [ 20.133117] net eth0: enc28j60 driver registered<br /> [ 20.139099] usbcore: registered new interface driver catc<br /> [ 20.144683] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver<br /> [ 20.150939] usbcore: registered new interface driver kaweth<br /> [ 20.156616] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver<br /> [ 20.164489] usbcore: registered new interface driver pegasus<br /> [ 20.170257] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver<br /> [ 20.177520] usbcore: registered new interface driver rtl8150<br /> [ 20.183563] usbcore: registered new interface driver asix<br /> [ 20.189300] usbcore: registered new interface driver cdc_ether<br /> [ 20.195495] usbcore: registered new interface driver dm9601<br /> [ 20.201507] usbcore: registered new interface driver smsc95xx<br /> [ 20.207641] usbcore: registered new interface driver gl620a<br /> [ 20.213531] usbcore: registered new interface driver net1080<br /> [ 20.219573] usbcore: registered new interface driver plusb<br /> [ 20.225463] usbcore: registered new interface driver rndis_host<br /> [ 20.231781] usbcore: registered new interface driver cdc_subset<br /> [ 20.238128] usbcore: registered new interface driver zaurus<br /> [ 20.244018] usbcore: registered new interface driver MOSCHIP usb-ethernet driver<br /> [ 20.251861] Broadcom 43xx driver loaded [ Features: L, Firmware-ID: FW13 ]<br /> [ 20.259307] usbcore: registered new interface driver zd1211rw<br /> [ 20.265441] usbcore: registered new interface driver rtl8187<br /> [ 20.271545] usbcore: registered new interface driver rndis_wlan<br /> [ 20.277832] usbcore: registered new interface driver zd1201<br /> [ 20.283813] usbcore: registered new interface driver usb8xxx<br /> [ 20.289916] usbcore: registered new interface driver rt2500usb<br /> [ 20.296173] usbcore: registered new interface driver rt73usb<br /> [ 20.302246] usbcore: registered new interface driver p54usb<br /> [ 20.307861] i2c /dev entries driver<br /> [ 20.313446] Driver 'sd' needs updating - please use bus_type methods<br /> [ 20.320220] Driver 'sr' needs updating - please use bus_type methods<br /> [ 20.327789] omap2-nand driver initializing<br /> [ 20.332305] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)<br /> [ 20.341369] cmdlinepart partition parsing not available<br /> [ 20.346649] Creating 5 MTD partitions on &quot;omap2-nand&quot;:<br /> [ 20.351867] 0x000000000000-0x000000080000 : &quot;X-Loader&quot;<br /> [ 20.359283] 0x000000080000-0x000000260000 : &quot;U-Boot&quot;<br /> [ 20.366485] 0x000000260000-0x000000280000 : &quot;U-Boot Env&quot;<br /> [ 20.373352] 0x000000280000-0x000000680000 : &quot;Kernel&quot;<br /> [ 20.381347] 0x000000680000-0x000010000000 : &quot;File System&quot;<br /> [ 20.494232] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br /> [ 20.501220] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller<br /> [ 20.507995] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1<br /> [ 20.515869] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800<br /> [ 20.534942] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00<br /> [ 20.541564] usb usb1: configuration #1 chosen from 1 choice<br /> [ 20.547698] hub 1-0:1.0: USB hub found<br /> [ 20.551635] hub 1-0:1.0: 3 ports detected<br /> [ 20.557983] Initializing USB Mass Storage driver...<br /> [ 20.563385] usbcore: registered new interface driver usb-storage<br /> [ 20.569519] USB Mass Storage support registered.<br /> [ 20.574920] mice: PS/2 mouse device common for all mice<br /> [ 20.580841] input: gpio-keys as /devices/platform/gpio-keys/input/input0<br /> [ 20.590545] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-0049/twl4030_pwrbutton/input/input1<br /> [ 20.605438] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc0<br /> [ 20.611663] rtc-ds1307 2-0068: 56 bytes nvram<br /> [ 20.617980] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec<br /> [ 20.624481] Bluetooth: HCI UART driver ver 2.2<br /> [ 20.628997] Bluetooth: HCI H4 protocol initialized<br /> [ 20.633819] Bluetooth: HCI BCSP protocol initialized<br /> [ 20.638885] Bluetooth: HCILL protocol initialized<br /> [ 20.643646] Bluetooth: Broadcom Blutonium firmware driver ver 1.2<br /> [ 20.650146] usbcore: registered new interface driver bcm203x<br /> [ 20.655944] Bluetooth: Digianswer Bluetooth USB driver ver 0.10<br /> [ 20.662445] usbcore: registered new interface driver bpa10x<br /> [ 20.668121] Bluetooth: BlueFRITZ! USB driver ver 1.2<br /> [ 20.673431] usbcore: registered new interface driver bfusb<br /> [ 20.679046] Bluetooth: Generic Bluetooth USB driver ver 0.4<br /> [ 20.685028] usbcore: registered new interface driver btusb<br /> [ 20.690582] Bluetooth: Generic Bluetooth SDIO driver ver 0.1<br /> [ 20.697509] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock<br /> [ 20.808563] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock<br /> [ 20.815155] regulator: Unable to get requested regulator: vmmc_aux<br /> [ 20.823669] Registered led device: beagleboard::usr0<br /> [ 20.829101] Registered led device: beagleboard::usr1<br /> [ 20.841583] usbcore: registered new interface driver usbhid<br /> [ 20.847229] usbhid: v2.6:USB HID core driver<br /> [ 20.852844] Advanced Linux Sound Architecture Driver Version 1.0.18a.<br /> [ 20.860321] usbcore: registered new interface driver snd-usb-audio<br /> [ 20.867004] No device for DAI twl4030<br /> [ 20.870910] No device for DAI omap-mcbsp-dai-0<br /> [ 20.875366] No device for DAI omap-mcbsp-dai-1<br /> [ 20.880004] No device for DAI omap-mcbsp-dai-2<br /> [ 20.884490] No device for DAI omap-mcbsp-dai-3<br /> [ 20.888977] No device for DAI omap-mcbsp-dai-4<br /> [ 20.893463] OMAP3 Beagle SoC init<br /> [ 20.897308] TWL4030 Audio Codec init <br /> [ 20.902618] asoc: twl4030 &lt;-&gt; omap-mcbsp-dai-0 mapping ok<br /> [ 20.918914] ALSA device list:<br /> [ 20.921905] #0: omap3beagle (twl4030)<br /> [ 20.934082] oprofile: using arm/armv7<br /> [ 20.938049] TCP cubic registered<br /> [ 20.941467] NET: Registered protocol family 17<br /> [ 20.945983] NET: Registered protocol family 15<br /> [ 20.950592] Bluetooth: L2CAP ver 2.11<br /> [ 20.954284] Bluetooth: L2CAP socket layer initialized<br /> [ 20.959411] Bluetooth: SCO (Voice Link) ver 0.6<br /> [ 20.963958] Bluetooth: SCO socket layer initialized<br /> [ 20.969116] Bluetooth: RFCOMM socket layer initialized<br /> [ 20.974365] Bluetooth: RFCOMM TTY layer initialized<br /> [ 20.979278] Bluetooth: RFCOMM ver 1.10<br /> [ 20.983123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3<br /> [ 20.988494] Bluetooth: BNEP filters: protocol multicast<br /> [ 20.993774] Bluetooth: HIDP (Human Interface Emulation) ver 1.2<br /> [ 21.002319] RPC: Registered udp transport module.<br /> [ 21.007110] RPC: Registered tcp transport module.<br /> [ 21.011993] lib80211: common routines for IEEE802.11 drivers<br /> [ 21.017761] ThumbEE CPU extension supported.<br /> [ 21.022094] Power Management for TI OMAP3.<br /> [ 21.035552] Disabling unused clock &quot;sr2_fck&quot;<br /> [ 21.039855] Disabling unused clock &quot;sr1_fck&quot;<br /> [ 21.044219] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.048675] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.053192] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.057678] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.062194] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.066680] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.071166] Disabling unused clock &quot;gpt2_ick&quot;<br /> [ 21.075592] Disabling unused clock &quot;gpt3_ick&quot;<br /> [ 21.079956] Disabling unused clock &quot;gpt4_ick&quot;<br /> [ 21.084381] Disabling unused clock &quot;gpt5_ick&quot;<br /> [ 21.088775] Disabling unused clock &quot;gpt6_ick&quot;<br /> [ 21.093200] Disabling unused clock &quot;gpt7_ick&quot;<br /> [ 21.097625] Disabling unused clock &quot;gpt8_ick&quot;<br /> [ 21.101989] Disabling unused clock &quot;gpt9_ick&quot;<br /> [ 21.106414] Disabling unused clock &quot;wdt3_ick&quot;<br /> [ 21.110809] Disabling unused clock &quot;wdt3_fck&quot;<br /> [ 21.115234] Disabling unused clock &quot;gpio2_dbck&quot;<br /> [ 21.119781] Disabling unused clock &quot;gpio3_dbck&quot;<br /> [ 21.124389] Disabling unused clock &quot;gpio4_dbck&quot;<br /> [ 21.128967] Disabling unused clock &quot;gpio5_dbck&quot;<br /> [ 21.133544] Disabling unused clock &quot;gpio6_dbck&quot;<br /> [ 21.138122] Disabling unused clock &quot;gpt9_fck&quot;<br /> [ 21.142517] Disabling unused clock &quot;gpt8_fck&quot;<br /> [ 21.146942] Disabling unused clock &quot;gpt7_fck&quot;<br /> [ 21.151336] Disabling unused clock &quot;gpt6_fck&quot;<br /> [ 21.155761] Disabling unused clock &quot;gpt5_fck&quot;<br /> [ 21.160156] Disabling unused clock &quot;gpt4_fck&quot;<br /> [ 21.164550] Disabling unused clock &quot;gpt3_fck&quot;<br /> [ 21.168975] Disabling unused clock &quot;gpt2_fck&quot;<br /> [ 21.173339] Disabling unused clock &quot;gpt1_ick&quot;<br /> [ 21.177764] Disabling unused clock &quot;wdt1_ick&quot;<br /> [ 21.182159] Disabling unused clock &quot;wdt2_ick&quot;<br /> [ 21.186584] Disabling unused clock &quot;wdt2_fck&quot;<br /> [ 21.190948] Disabling unused clock &quot;gpio1_dbck&quot;<br /> [ 21.195556] Disabling unused clock &quot;gpt1_fck&quot;<br /> [ 21.199981] Disabling unused clock &quot;cam_ick&quot;<br /> [ 21.204315] Disabling unused clock &quot;cam_mclk&quot;<br /> [ 21.208740] Disabling unused clock &quot;des1_ick&quot;<br /> [ 21.213134] Disabling unused clock &quot;sha11_ick&quot;<br /> [ 21.217620] Disabling unused clock &quot;rng_ick&quot;<br /> [ 21.221923] Disabling unused clock &quot;aes1_ick&quot;<br /> [ 21.226348] Disabling unused clock &quot;ssi_ick&quot;<br /> [ 21.230682] Disabling unused clock &quot;mailboxes_ick&quot;<br /> [ 21.235504] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.239990] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.244476] Disabling unused clock &quot;gpt10_ick&quot;<br /> [ 21.248992] Disabling unused clock &quot;gpt11_ick&quot;<br /> [ 21.253448] Disabling unused clock &quot;hdq_ick&quot;<br /> [ 21.257781] Disabling unused clock &quot;mspro_ick&quot;<br /> [ 21.262298] Disabling unused clock &quot;des2_ick&quot;<br /> [ 21.266693] Disabling unused clock &quot;sha12_ick&quot;<br /> [ 21.271179] Disabling unused clock &quot;aes2_ick&quot;<br /> [ 21.275573] Disabling unused clock &quot;icr_ick&quot;<br /> [ 21.279907] Disabling unused clock &quot;pka_ick&quot;<br /> [ 21.284210] Disabling unused clock &quot;ssi_ssr_fck&quot;<br /> [ 21.288879] Disabling unused clock &quot;hdq_fck&quot;<br /> [ 21.293212] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.297698] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.302185] Disabling unused clock &quot;mspro_fck&quot;<br /> [ 21.306671] Disabling unused clock &quot;gpt11_fck&quot;<br /> [ 21.311187] Disabling unused clock &quot;gpt10_fck&quot;<br /> [ 21.315643] Disabling unused clock &quot;dpll4_m6x2_ck&quot;<br /> [ 21.320526] Disabling unused clock &quot;dpll3_m3x2_ck&quot;<br /> [ 21.325378] Disabling unused clock &quot;sys_clkout1&quot;<br /> [ 21.330047] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1<br /> [ 21.342468] registered taskstats version 1<br /> [ 21.348236] fbcvt: 1024x768@60: CVT Name - .786M3-R<br /> [ 21.379608] Console: switching to colour frame buffer device 128x48<br /> [ 21.400665] clock: clksel_round_rate_div: dpll4_m4_ck target_rate 48000000<br /> [ 21.407592] clock: new_div = 9, new_rate = 48000000<br /> [ 21.417175] rtc-ds1307 2-0068: setting system clock to 2009-09-27 16:42:23 UTC (1254069743)<br /> [ 21.426086] Waiting for root device /dev/mmcblk0p2...<br /> [ 21.448944] mmc0: new high speed SD card at address ddce<br /> [ 21.455108] mmcblk0: mmc0:ddce SD02G 1.83 GiB <br /> [ 21.460021] mmcblk0: p1 p2<br /> [ 21.539916] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended<br /> [ 21.548187] kjournald starting. Commit interval 5 seconds<br /> [ 21.556823] EXT3 FS on mmcblk0p2, internal journal<br /> [ 21.561737] EXT3-fs: mounted filesystem with ordered data mode.<br /> [ 21.567779] VFS: Mounted root (ext3 filesystem) on device 179:2.<br /> [ 21.574066] Freeing init memory: 204K<br /> INIT: version 2.86 booting<br /> Please wait: booting...<br /> &lt;/pre&gt;<br /> <br /> = I2C analysis =<br /> <br /> Using [http://www.lm-sensors.org/wiki/I2CTools I2C tools] you can analyze the I2C bus:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -l<br /> i2c-1 i2c OMAP I2C adapter I2C adapter<br /> i2c-2 i2c OMAP I2C adapter I2C adapter<br /> i2c-3 i2c OMAP I2C adapter I2C adapter<br /> &lt;/pre&gt;<br /> <br /> Zippy Board uses i2c-2 for the RTC and EEPROM:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -y -r 2<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f<br /> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- <br /> 70: -- -- -- -- -- -- -- -- <br /> &lt;/pre&gt;<br /> <br /> * EEPROM is at 0x50<br /> * RTC is at 0x68<br /> <br /> =EEPROM=<br /> <br /> AT24 EEPROM ([http://www.atmel.com/dyn/resources/prod_documents/doc5156.pdf AT24C01B]) is used to identify Zippy board. See [[BeagleBoardPinMux#Expansion_boards|expansion board]] how this is done.<br /> <br /> Using Linux i2cdump tool at bus 2 address 0x50 the content of this EEPROM is given:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:~# i2cdump 2 0x50 b<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef<br /> 00: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 80: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> &lt;/pre&gt;<br /> <br /> <br /> = Schematic Diagram =<br /> <br /> * [[media:zippy_schematic.pdf|Zippy_schematic]]<br /> <br /> = Where to purchase the Zippy board =<br /> <br /> The Zippy board can be purchased from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16149&amp;cat=0&amp;page=1&amp;featured www.tincantools.com]<br /> <br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]<br /> <br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]<br /> <br /> <br /> [[Category:TinCanTools]]<br /> [[Category:BeagleBoard Expansion Boards]]<br /> [[Category:BeagleBoard]]</div>

Rkherod http://elinux.org/BeagleBoard_Zippy 2011-06-23T18:04:53Z

<p>Rkherod: </p> <hr /> <div>[[File:zippy-base.jpg|400px]]<br /> <br /> <br /> The Zippy board was developed by [[TinCanTools]] ([http://www.tincantools.com Company Website]). <br /> <br /> You can purchase the Zippy board from:<br /> USA: [http://www.tincantools.com/product.php?productid=16147 www.tincantools.com]&lt;br&gt;<br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]&lt;br&gt;<br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]&lt;br&gt;<br /> &lt;br&gt;<br /> == Hardware ==<br /> The BeagleBuddy Zippy Ethernet Combo Board is a low cost expansion board for the [[BeagleBoard]] that provides the following peripherals:<br /> * 10BaseT Ethernet<br /> * Second SD/MMC Interface<br /> * Second RS232 Serial Interface<br /> * Real-Time clock with Battery Back-up<br /> * I2C Interface (+5V level)<br /> * AT24C01 Serial EEPROM for Board Identification<br /> <br /> == Ethernet ==<br /> The Zippy provides a standard 10BaseT (10/100 Mbit) Ethernet interface and uses Microchip's [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en022889 ENC28J60] SPI to Ethernet controller.<br /> <br /> == SD/MMC Interface ==<br /> <br /> The Zippy provides a second SD/MMC interface that supports both 3.3V and 1.8V SD memory cards.<br /> <br /> == RS232 Serial Interface ==<br /> <br /> The Zippy provides a second RS-232 serial port for the BeagleBoard:<br /> There are two serial connectors provided. <br /> * Standard DB9 Male connector<br /> * 2x5 shrouded header (0.1 inch pin spacing).<br /> <br /> == Real-time Clock ==<br /> <br /> The Zippy provides a battery backed-up Real Time Clock (RTC) which uses the Maxim [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2688RTC DS1307]. The backup power is provided by a small 3V lithium coin battery and is held in place by a battery holder.<br /> <br /> Compatible 3V Lithium Coin Batteries:<br /> <br /> * CR1216<br /> * CR1220<br /> * CR1225<br /> <br /> Battery cell size = 12mm.<br /> <br /> The battery is not included with the Zippy and must be purchased separately. Compatible batteries are available from Digi-Key:<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=P032-ND Panasonic CR1216]<br /> <br /> [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=N032-ND Energizer CR1216]<br /> <br /> Compatible batteries are available from Mouser Electronics:<br /> <br /> [http://www.mouser.com/ProductDetail/Renata/CR1220TS/?qs=sGAEpiMZZMtz8P%2feuiupSd2F%2fX%2ffEmeEyLDGD5JMOeY%3d CR1220]<br /> <br /> [http://www.mouser.com/ProductDetail/Sanyo-Batteries/CR1220-SANYO/?qs=sGAEpiMZZMtz8P%2feuiupSYq8MKOV5mn3%2f%2fvaRL4TkWg%3d CR1220]<br /> <br /> <br /> Installing the 3V lithium coin battery:<br /> <br /> [[File:zippy-battery01.jpg|400px]]<br /> <br /> Insert the battery with the positive &quot;+&quot; side up.<br /> <br /> <br /> [[File:zippy-battery02.jpg|400px]]<br /> <br /> Slide the battery all the way into the battery holder.<br /> <br /> == I²C Interface ==<br /> <br /> The Zippy provides a 4-pin header expansion connector for access to the BeagleBoard's I²C signals. The signals have been level translated to 5V to allow easy connection to standard 5V peripherals.<br /> <br /> I²C expansion header pin assignments:<br /> <br /> * pin 1 - +5V Power<br /> * pin 2 - SDA (5V signal level)<br /> * pin 3 - SCL (5V signal level)<br /> * pin 4 - Ground<br /> <br /> == Serial EEPROM ==<br /> The Zippy provides an AT24C01 serial EEPROM that contains a Vendor ID and a Device ID that the BeagleBoard uses to identify the type of board connected to the expansion header. This information enables the BeagleBoard to auto-configure the pin mux for signals needed by the Zippy. More information can be found on the [[BeagleBoardPinMux|Beagle Board Pin Mux Page]].<br /> <br /> = Soldering BeagleBoard's Expansion Header =<br /> This is a quick guide showing you how to solder the 2x14 Header into the BeagleBoard’s Expansion connector (J3).<br /> <br /> [[File:zippy-expansion_connector1.jpg|400px]]<br /> <br /> Insert the 2x14 Header’s SHORT PINS from the back side of the BeagleBoard into the BeagleBoard’s<br /> expansion connector (J3).<br /> <br /> <br /> [[File:zippy-expansion_connector2.jpg|400px]]<br /> <br /> Position the 2x14 Header so the LONG PINS are on the BACK SIDE of the BeagleBoard.<br /> <br /> <br /> [[File:zippy-expansion_connector3.jpg|400px]]<br /> <br /> Solder the SHORT PINS of the 2x14 Header from the TOP SIDE of the BeagleBoard.<br /> <br /> == Attaching to the BeagleBoard ==<br /> <br /> [[File:zippy-expansion_connector7.jpg|400px]]<br /> <br /> Attach the four board spacers with the screws provided.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector4.jpg|400px]]<br /> <br /> Connect the expansion board onto the BACK SIDE of the BeagleBoard by mating<br /> with the 2x14 Header you just soldered. Make sure all of the pins align correctly.<br /> <br /> <br /> [[File:zippy-expansion_connector5.jpg|400px]]<br /> <br /> Continue pushing the two boards together until the connectors mate together.<br /> <br /> <br /> [[File:zippy-expansion_connector6.jpg|400px]]<br /> <br /> Attach the male standoffs as shown.<br /> <br /> <br /> <br /> [[File:zippy-expansion_connector8.jpg|400px]]<br /> <br /> = Creating a bootable SD card in Ubuntu =<br /> <br /> This guide will demonstate how to create a '''dual-partition''' SD card for the BeagleBoard/Zippy combination to boot Linux from the first partition and have the root file system located on the second partition. <br /> <br /> This guide covers the same procedure as [[BeagleBoardBeginners|SDCard setup]] and [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat].<br /> <br /> This guide will use a '''2GB SD card''' for all examples.<br /> <br /> '''Determine which device the SD Card Reader is on your system'''<br /> <br /> Insert the SD Card into the SD Card Reader reader on your Linux PC. Then determine which device it is on your system:<br /> <br /> dmesg | tail<br /> ...<br /> [2079456.496092] sd 34:0:0:0: [sdb] Mode Sense: 03 00 00 00<br /> [2079456.496096] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513743] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.513751] sdb: sdb1<br /> [2079456.529193] sd 34:0:0:0: [sdb] Assuming drive cache: write through<br /> [2079456.529201] sd 34:0:0:0: [sdb] Attached SCSI removable disk<br /> <br /> In this case it shows up as /dev/sdb (note sdb insite the square brackets above).<br /> <br /> '''Check to see if the automounter has mounted the SD Card:'''<br /> <br /> df -h<br /> Filesystem Size Used Avail Use% Mounted on<br /> ... 1.8G 0 1.8G 0% /lib/init/rw<br /> /dev/sdb1 1.9G 0 1.9G 0% /media/6262-9331<br /> ...<br /> <br /> '''If mounted, unmount the SD card'''<br /> <br /> umount /media/6262-9331<br /> <br /> '''Start fdisk:'''<br /> <br /> sudo fdisk /dev/sdb<br /> '''Print the partition record:'''<br /> &lt;pre&gt;<br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 57 heads, 56 sectors/track, 1203 cylinders<br /> Units = cylinders of 3192 * 512 = 1634304 bytes<br /> Disk identifier: 0x00000000<br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 1204 1920955+ 6 FAT16<br /> &lt;/pre&gt;<br /> Note card size in bytes listed above (in this example: '''1967128576'''). '''Write this number down, it will be needed later below'''.<br /> <br /> '''Delete any partitions that are already on the SD card'''<br /> <br /> Command (m for help): ''d''<br /> Selected partition 1<br /> <br /> '''Set the Geometry of the SD Card'''<br /> <br /> Go into &quot;Expert mode&quot;:<br /> <br /> Command (m for help): ''x''<br /> <br /> Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD card you are using:<br /> &lt;pre&gt;<br /> Expert command (m for help): h<br /> Number of heads (1-256, default 57): 255<br /> <br /> Expert command (m for help): s<br /> Number of sectors (1-63, default 56): 63<br /> Warning: setting sector offset for DOS compatiblity<br /> <br /> Expert command (m for help): c<br /> Number of cylinders (1-1048576, default 1203): 239<br /> &lt;/pre&gt;<br /> The '''239''' entered in the cylinders above must be calculated based upon the size of your particular SD card.<br /> <br /> '''Now Calculate the number of Cylinders for your SD card:''' <br /> <br /> '''''number of cylinders = FLOOR (the number of Bytes on the SD Card (from above) / 255 heads / 63 sectors / 512 sector size in bytes )'''''<br /> <br /> So for this example: 1967128576 / 255 / 63 / 512 = 239.156427 (use Google to calculate). So we use 239 (i.e. truncate, don't round).<br /> <br /> Return to &quot;Normal&quot; mode:<br /> <br /> Expert command (m for help): ''r''<br /> <br /> <br /> '''Print the partition record to check your work:''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> Device Boot Start End Blocks Id System<br /> <br /> &lt;/pre&gt;<br /> <br /> '''Create the FAT32 partition for booting and transferring files from your PC'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> p<br /> Partition number (1-4): 1<br /> First cylinder (1-15, default 1): 1<br /> Last cylinder or +size or +sizeM or +sizeK (1-239, default 239): 50<br /> <br /> Command (m for help): t<br /> Selected partition 1<br /> Hex code (type L to list codes): c<br /> Changed system type of partition 1 to c (W95 FAT32 (LBA))<br /> &lt;/pre&gt;<br /> We use 50 cylinders of the total of 239 for the FAT32 partition above. The remainder of the cylinders will be used for the Linux root file system below.<br /> <br /> '''Mark this FAT32 partition as bootable:'''<br /> <br /> Command (m for help): a<br /> Partition number (1-4): 1<br /> <br /> '''Create the Linux partition for the root file system'''<br /> &lt;pre&gt;<br /> Command (m for help): n<br /> Command action<br /> e extended<br /> p primary partition (1-4)<br /> ''p''<br /> Partition number (1-4): 2<br /> First cylinder (51-239, default 51): 51<br /> Last cylinder or +size or +sizeM or +sizeK (51-239, default 239): 239<br /> &lt;/pre&gt;<br /> <br /> '''Print the partition record to check your work''' <br /> &lt;pre&gt; <br /> Command (m for help): p<br /> <br /> Disk /dev/sdb: 1967 MB, 1967128576 bytes<br /> 255 heads, 63 sectors/track, 239 cylinders<br /> Units = cylinders of 16065 * 512 = 8225280 bytes<br /> <br /> <br /> Device Boot Start End Blocks Id System<br /> /dev/sdb1 1 50 1920955+ c w95 FAT32 (LBA)<br /> /dev/sdb2 51 239 83 Linux<br /> &lt;/pre&gt;<br /> '''Save the new partition records on the SD card'''<br /> <br /> This is an important step. All work up to now has been temporary.<br /> &lt;pre&gt;<br /> Command (m for help): w<br /> The partition table has been altered!<br /> <br /> Calling ioctl() to re-read partition table.<br /> <br /> WARNING: If you have created or modified any DOS 6.x<br /> partitions, please see the fdisk manual page for additional<br /> information.<br /> Syncing disks.<br /> &lt;/pre&gt;<br /> '''Format the partitions'''<br /> &lt;pre&gt;<br /> sudo mkfs.msdos -F 32 /dev/sdb1 -n boot<br /> mkfs.msdos 3.0.3 (18 May 2009)<br /> <br /> sudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linuxsudo mkfs.ext3 -L rootfs /dev/sdb2<br /> mke2fs 1.41.9 (22-Aug-2009)<br /> Filesystem label=rootfs<br /> OS type: Linux<br /> Block size=4096 (log=2)<br /> Fragment size=4096 (log=2)<br /> 95040 inodes, 379535 blocks<br /> 18976 blocks (5.00%) reserved for the super user<br /> First data block=0<br /> Maximum filesystem blocks=390070272<br /> 12 block groups<br /> 32768 blocks per group, 32768 fragments per group<br /> 7920 inodes per group<br /> Superblock backups stored on blocks:<br /> 32768, 98304, 163840, 229376, 294912<br /> <br /> Writing inode tables: done<br /> Creating journal (8192 blocks): done<br /> Writing superblocks and filesystem accounting information: done<br /> &lt;/pre&gt;<br /> <br /> ==Copy files onto the BOOT partition ==<br /> <br /> You will need to download the demo/test files for the BeagleBoard/Zippy combination:<br /> #[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> #[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> #[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> #[[media:test.rootfs.tar.gz|test.rootfs.tar.gz]] (save as test.rootfs.tar.gz)<br /> <br /> <br /> And now copy the first three files onto the boot partition ('''IMPORTANT: Copy MLO FIRST!''' because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition).<br /> <br /> cp MLO /media/boot/MLO<br /> cp u-boot.bin /media/boot/u-boot.bin<br /> cp uImage /media/boot/uImage<br /> <br /> ==Copy the files onto the Linux partition==<br /> <br /> The next step is to extract the files in '''test-rootfs.tar.gz''' into the rootfs partition (NOT the boot partition) on the SD card. This can only be done by using Linux. <br /> <br /> sudo tar -zxvf test-rootfs.tar.gz -C /media/rootfs<br /> <br /> Unmount the SD card from the Linux PC and insert it into the BeagleBoard's SD connector.<br /> <br /> Then boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> = Programming the Zippy =<br /> All of the devices on the Zippy work as standard linux devices which means any reference material for these devices is applicable:<br /> <br /> How to access the I2C bus (from software): http://i2c.wiki.kernel.org/index.php/Linux_2.6_I2C_development_FAQ<br /> <br /> How to access the second UART: http://tldp.org/HOWTO/Serial-HOWTO.html<br /> and http://www.vanemery.com/Linux/Serial/serial-console.html<br /> <br /> How to use and configure the Ethernet port: http://tldp.org/HOWTO/Ethernet-HOWTO.html<br /> <br /> How to access the SD card:<br /> If you are using the Angstrom images, then all you have to do is insert the SD card and it will be automatically mounted. To check just issue the command &quot;mount&quot; at the prompt to view the currently mounted devices.<br /> <br /> = Setting the Real Time Clock (RTC) =<br /> To set the real time clock (RTC) on the Zippy board:<br /> <br /> First: Set the date:<br /> date -s 2010.02.15-17:52<br /> (date -s YYYY.MM.DD-HH:SS (the time HH:SS is in 24 hour format)<br /> <br /> Then write the current date into the RTC's hardware registers:<br /> <br /> hwclock -w<br /> <br /> As long as you have a good backup battery (the small coin battery), the RTC should keep the time correct even if you remove power and boot-up the BeagleBoard at a later time.<br /> <br /> = Software =<br /> <br /> *[http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=8ded6c1580b907494b0ea95e36d91ca8d64122e8 patches in oe git]<br /> *Demo/Test Files<br /> **[[media:MLO-zippy.ift|MLO]] (save as MLO)<br /> **[[media:u-boot-zippy.bin|u-boot.bin]] (save as u-boot.bin)<br /> **[[media:uImage-zippy.bin|uImage]] (save as uImage)<br /> **[[media:defconfig.txt|Kernel Config]]<br /> **[[media:zippy-0xdroid.patch|0xdroid kernel patch]]<br /> <br /> *place these files on your formated SD card per the instuctions at the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat LinuxBootDiskFormat] page<br /> *boot your BeagleBoard while holding down the &quot;User&quot; button.<br /> <br /> <br /> All drivers are in the mainline kernel source:<br /> *ethernet - drivers/net/enc28j60.c<br /> *rtc - drivers/rtc/rtc-ds1307.c<br /> *uart - drivers/serial/8250.c<br /> *mmc - drivers/mmc/omap_hsmmc.c<br /> *eeprom - drivers/misc/eeprom/at24.c<br /> <br /> = System boot =<br /> <br /> &lt;pre&gt;<br /> Texas Instruments X-Loader 1.4.2 (Sep 9 2009 - 09:20:15)<br /> Reading boot sector<br /> Loading u-boot.bin from mmc<br /> <br /> <br /> U-Boot 2009.06-rc2 (Sep 09 2009 - 13:12:40)<br /> <br /> OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz<br /> OMAP3 Beagle board + LPDDR/NAND<br /> DRAM: 256 MB<br /> NAND: 256 MiB<br /> *** Warning - bad CRC or NAND, using default environment<br /> <br /> In: serial<br /> Out: serial<br /> Err: serial<br /> Board revision C<br /> Die ID #197a0003000000000403230911004012<br /> Hit any key to stop autoboot: 0 <br /> mmc1 is available<br /> reading boot.scr<br /> <br /> ** Unable to read &quot;boot.scr&quot; from mmc 0:1 **<br /> reading uImage<br /> <br /> 2994264 bytes read<br /> Booting from mmc ...<br /> ## Booting kernel from Legacy Image at 82000000 ...<br /> Image Name: Angstrom/2.6.29/beagleboard<br /> Image Type: ARM Linux Kernel Image (uncompressed)<br /> Data Size: 2994200 Bytes = 2.9 MB<br /> Load Address: 80008000<br /> Entry Point: 80008000<br /> Verifying Checksum ... OK<br /> Loading Kernel Image ... OK<br /> OK<br /> <br /> Starting kernel ...<br /> <br /> Uncompressing Linux...................................................................................................................................................................................<br /> [ 0.000000] Linux version 2.6.29-omap1 (dave@linuxdev) (gcc version 4.3.3 (GCC) ) #6 PREEMPT Thu Sep 17 10:11:54 CDT 2009<br /> [ 0.000000] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f<br /> [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache<br /> [ 0.000000] Machine: OMAP3 Beagle Board<br /> [ 0.000000] Memory policy: ECC disabled, Data cache writeback<br /> [ 0.000000] OMAP3430 ES3.0<br /> [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000<br /> [ 0.000000] Reserving 12582912 bytes SDRAM for VRAM<br /> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024<br /> [ 0.000000] Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait<br /> [ 0.000000] Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz<br /> [ 0.000000] GPMC revision 5.0<br /> [ 0.000000] IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts<br /> [ 0.000000] Total of 96 interrupts on 1 active controller<br /> [ 0.000000] OMAP34xx GPIO hardware version 2.5<br /> [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)<br /> [ 0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz<br /> [ 0.000000] Console: colour dummy device 80x30<br /> [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)<br /> [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)<br /> [ 0.000000] Memory: 128MB 128MB = 256MB total<br /> [ 0.000000] Memory: 240896KB available (5632K code, 575K data, 204K init)<br /> [ 0.000000] Calibrating delay loop... 486.31 BogoMIPS (lpj=1900544)<br /> [ 0.000000] Mount-cache hash table entries: 512<br /> [ 0.000000] CPU: Testing write buffer coherency: ok<br /> [ 0.000000] net_namespace: 1036 bytes<br /> [ 0.000000] regulator: core version 0.5<br /> [ 0.000000] NET: Registered protocol family 16<br /> [ 0.000000] Found NAND on CS0<br /> [ 0.000000] Registering NAND on CS0<br /> [ 19.307373] OMAP DMA hardware revision 4.0<br /> [ 19.353057] bio: create slab &lt;bio-0&gt; at 0<br /> [ 19.411468] OMAP DSS rev 2.0<br /> [ 19.411590] OMAP DISPC rev 3.0<br /> [ 19.411590] OMAP VENC rev 2<br /> [ 19.411773] OMAP DSI rev 1.0<br /> [ 19.414916] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz<br /> [ 19.418914] twl4030: PIH (irq 7) chaining IRQs 368..375<br /> [ 19.418945] twl4030: power (irq 373) chaining IRQs 376..383<br /> [ 19.419586] twl4030: gpio (irq 368) chaining IRQs 384..401<br /> [ 19.422668] regulator: VMMC1: 1850 &lt;--&gt; 3150 mV normal standby<br /> [ 19.423645] regulator: VDAC: 1800 mV normal standby<br /> [ 19.424560] regulator: VUSB1V5: 1500 &lt;--&gt; 0 mV normal standby<br /> [ 19.425506] regulator: VUSB1V8: 1800 &lt;--&gt; 0 mV normal standby<br /> [ 19.426422] regulator: VUSB3V1: 3100 &lt;--&gt; 0 mV normal standby<br /> [ 19.427398] regulator: VPLL2: 1800 mV normal standby<br /> [ 19.428375] regulator: VMMC2: 2800 &lt;--&gt; 3150 mV normal standby<br /> [ 19.429321] regulator: VSIM: 1800 &lt;--&gt; 3000 mV normal standby<br /> [ 19.441925] i2c_omap i2c_omap.2: bus 2 rev3.12 at 10 kHz<br /> [ 19.457122] i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz<br /> [ 19.459289] SCSI subsystem initialized<br /> [ 19.462982] twl4030_usb twl4030_usb: Initialized TWL4030 USB module<br /> [ 19.464752] usbcore: registered new interface driver usbfs<br /> [ 19.465393] usbcore: registered new interface driver hub<br /> [ 19.465850] usbcore: registered new device driver usb<br /> [ 19.469146] Bluetooth: Core ver 2.14<br /> [ 19.469696] NET: Registered protocol family 31<br /> [ 19.469726] Bluetooth: HCI device and connection manager initialized<br /> [ 19.469757] Bluetooth: HCI socket layer initialized<br /> [ 19.470520] cfg80211: Using static regulatory domain info<br /> [ 19.470520] cfg80211: Regulatory domain: US<br /> [ 19.470550] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)<br /> [ 19.470581] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)<br /> [ 19.470581] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470611] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470642] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)<br /> [ 19.470672] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)<br /> [ 19.470703] cfg80211: Calling CRDA for country: US<br /> [ 19.474670] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0<br /> [ 19.477416] musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92<br /> [ 19.478698] NET: Registered protocol family 2<br /> [ 19.478973] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)<br /> [ 19.479614] TCP established hash table entries: 8192 (order: 4, 65536 bytes)<br /> [ 19.479888] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)<br /> [ 19.480041] TCP: Hash tables configured (established 8192 bind 8192)<br /> [ 19.480072] TCP reno registered<br /> [ 19.480468] NET: Registered protocol family 1<br /> [ 19.484863] VFS: Disk quotas dquot_6.5.2<br /> [ 19.484985] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)<br /> [ 19.485626] squashfs: version 4.0 (2009/01/31) Phillip Lougher<br /> [ 19.486450] JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.<br /> [ 19.487457] msgmni has been set to 470<br /> [ 19.492523] alg: No test for stdrng (krng)<br /> [ 19.492645] io scheduler noop registered<br /> [ 19.492645] io scheduler anticipatory registered<br /> [ 19.492675] io scheduler deadline registered<br /> [ 19.492889] io scheduler cfq registered (default)<br /> [ 19.519348] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled<br /> [ 19.541748] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654<br /> [ 19.563201] serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654<br /> [ 19.583740] serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654<br /> [ 19.583801] console [ttyS2] enabled<br /> [ 20.108825] brd: module loaded<br /> [ 20.118408] loop: module loaded<br /> [ 20.122741] enc28j60 spi4.0: enc28j60 Ethernet driver 1.01 loaded<br /> [ 20.133117] net eth0: enc28j60 driver registered<br /> [ 20.139099] usbcore: registered new interface driver catc<br /> [ 20.144683] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver<br /> [ 20.150939] usbcore: registered new interface driver kaweth<br /> [ 20.156616] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver<br /> [ 20.164489] usbcore: registered new interface driver pegasus<br /> [ 20.170257] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver<br /> [ 20.177520] usbcore: registered new interface driver rtl8150<br /> [ 20.183563] usbcore: registered new interface driver asix<br /> [ 20.189300] usbcore: registered new interface driver cdc_ether<br /> [ 20.195495] usbcore: registered new interface driver dm9601<br /> [ 20.201507] usbcore: registered new interface driver smsc95xx<br /> [ 20.207641] usbcore: registered new interface driver gl620a<br /> [ 20.213531] usbcore: registered new interface driver net1080<br /> [ 20.219573] usbcore: registered new interface driver plusb<br /> [ 20.225463] usbcore: registered new interface driver rndis_host<br /> [ 20.231781] usbcore: registered new interface driver cdc_subset<br /> [ 20.238128] usbcore: registered new interface driver zaurus<br /> [ 20.244018] usbcore: registered new interface driver MOSCHIP usb-ethernet driver<br /> [ 20.251861] Broadcom 43xx driver loaded [ Features: L, Firmware-ID: FW13 ]<br /> [ 20.259307] usbcore: registered new interface driver zd1211rw<br /> [ 20.265441] usbcore: registered new interface driver rtl8187<br /> [ 20.271545] usbcore: registered new interface driver rndis_wlan<br /> [ 20.277832] usbcore: registered new interface driver zd1201<br /> [ 20.283813] usbcore: registered new interface driver usb8xxx<br /> [ 20.289916] usbcore: registered new interface driver rt2500usb<br /> [ 20.296173] usbcore: registered new interface driver rt73usb<br /> [ 20.302246] usbcore: registered new interface driver p54usb<br /> [ 20.307861] i2c /dev entries driver<br /> [ 20.313446] Driver 'sd' needs updating - please use bus_type methods<br /> [ 20.320220] Driver 'sr' needs updating - please use bus_type methods<br /> [ 20.327789] omap2-nand driver initializing<br /> [ 20.332305] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)<br /> [ 20.341369] cmdlinepart partition parsing not available<br /> [ 20.346649] Creating 5 MTD partitions on &quot;omap2-nand&quot;:<br /> [ 20.351867] 0x000000000000-0x000000080000 : &quot;X-Loader&quot;<br /> [ 20.359283] 0x000000080000-0x000000260000 : &quot;U-Boot&quot;<br /> [ 20.366485] 0x000000260000-0x000000280000 : &quot;U-Boot Env&quot;<br /> [ 20.373352] 0x000000280000-0x000000680000 : &quot;Kernel&quot;<br /> [ 20.381347] 0x000000680000-0x000010000000 : &quot;File System&quot;<br /> [ 20.494232] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br /> [ 20.501220] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller<br /> [ 20.507995] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1<br /> [ 20.515869] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800<br /> [ 20.534942] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00<br /> [ 20.541564] usb usb1: configuration #1 chosen from 1 choice<br /> [ 20.547698] hub 1-0:1.0: USB hub found<br /> [ 20.551635] hub 1-0:1.0: 3 ports detected<br /> [ 20.557983] Initializing USB Mass Storage driver...<br /> [ 20.563385] usbcore: registered new interface driver usb-storage<br /> [ 20.569519] USB Mass Storage support registered.<br /> [ 20.574920] mice: PS/2 mouse device common for all mice<br /> [ 20.580841] input: gpio-keys as /devices/platform/gpio-keys/input/input0<br /> [ 20.590545] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-0049/twl4030_pwrbutton/input/input1<br /> [ 20.605438] rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc0<br /> [ 20.611663] rtc-ds1307 2-0068: 56 bytes nvram<br /> [ 20.617980] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec<br /> [ 20.624481] Bluetooth: HCI UART driver ver 2.2<br /> [ 20.628997] Bluetooth: HCI H4 protocol initialized<br /> [ 20.633819] Bluetooth: HCI BCSP protocol initialized<br /> [ 20.638885] Bluetooth: HCILL protocol initialized<br /> [ 20.643646] Bluetooth: Broadcom Blutonium firmware driver ver 1.2<br /> [ 20.650146] usbcore: registered new interface driver bcm203x<br /> [ 20.655944] Bluetooth: Digianswer Bluetooth USB driver ver 0.10<br /> [ 20.662445] usbcore: registered new interface driver bpa10x<br /> [ 20.668121] Bluetooth: BlueFRITZ! USB driver ver 1.2<br /> [ 20.673431] usbcore: registered new interface driver bfusb<br /> [ 20.679046] Bluetooth: Generic Bluetooth USB driver ver 0.4<br /> [ 20.685028] usbcore: registered new interface driver btusb<br /> [ 20.690582] Bluetooth: Generic Bluetooth SDIO driver ver 0.1<br /> [ 20.697509] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock<br /> [ 20.808563] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock<br /> [ 20.815155] regulator: Unable to get requested regulator: vmmc_aux<br /> [ 20.823669] Registered led device: beagleboard::usr0<br /> [ 20.829101] Registered led device: beagleboard::usr1<br /> [ 20.841583] usbcore: registered new interface driver usbhid<br /> [ 20.847229] usbhid: v2.6:USB HID core driver<br /> [ 20.852844] Advanced Linux Sound Architecture Driver Version 1.0.18a.<br /> [ 20.860321] usbcore: registered new interface driver snd-usb-audio<br /> [ 20.867004] No device for DAI twl4030<br /> [ 20.870910] No device for DAI omap-mcbsp-dai-0<br /> [ 20.875366] No device for DAI omap-mcbsp-dai-1<br /> [ 20.880004] No device for DAI omap-mcbsp-dai-2<br /> [ 20.884490] No device for DAI omap-mcbsp-dai-3<br /> [ 20.888977] No device for DAI omap-mcbsp-dai-4<br /> [ 20.893463] OMAP3 Beagle SoC init<br /> [ 20.897308] TWL4030 Audio Codec init <br /> [ 20.902618] asoc: twl4030 &lt;-&gt; omap-mcbsp-dai-0 mapping ok<br /> [ 20.918914] ALSA device list:<br /> [ 20.921905] #0: omap3beagle (twl4030)<br /> [ 20.934082] oprofile: using arm/armv7<br /> [ 20.938049] TCP cubic registered<br /> [ 20.941467] NET: Registered protocol family 17<br /> [ 20.945983] NET: Registered protocol family 15<br /> [ 20.950592] Bluetooth: L2CAP ver 2.11<br /> [ 20.954284] Bluetooth: L2CAP socket layer initialized<br /> [ 20.959411] Bluetooth: SCO (Voice Link) ver 0.6<br /> [ 20.963958] Bluetooth: SCO socket layer initialized<br /> [ 20.969116] Bluetooth: RFCOMM socket layer initialized<br /> [ 20.974365] Bluetooth: RFCOMM TTY layer initialized<br /> [ 20.979278] Bluetooth: RFCOMM ver 1.10<br /> [ 20.983123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3<br /> [ 20.988494] Bluetooth: BNEP filters: protocol multicast<br /> [ 20.993774] Bluetooth: HIDP (Human Interface Emulation) ver 1.2<br /> [ 21.002319] RPC: Registered udp transport module.<br /> [ 21.007110] RPC: Registered tcp transport module.<br /> [ 21.011993] lib80211: common routines for IEEE802.11 drivers<br /> [ 21.017761] ThumbEE CPU extension supported.<br /> [ 21.022094] Power Management for TI OMAP3.<br /> [ 21.035552] Disabling unused clock &quot;sr2_fck&quot;<br /> [ 21.039855] Disabling unused clock &quot;sr1_fck&quot;<br /> [ 21.044219] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.048675] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.053192] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.057678] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.062194] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.066680] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.071166] Disabling unused clock &quot;gpt2_ick&quot;<br /> [ 21.075592] Disabling unused clock &quot;gpt3_ick&quot;<br /> [ 21.079956] Disabling unused clock &quot;gpt4_ick&quot;<br /> [ 21.084381] Disabling unused clock &quot;gpt5_ick&quot;<br /> [ 21.088775] Disabling unused clock &quot;gpt6_ick&quot;<br /> [ 21.093200] Disabling unused clock &quot;gpt7_ick&quot;<br /> [ 21.097625] Disabling unused clock &quot;gpt8_ick&quot;<br /> [ 21.101989] Disabling unused clock &quot;gpt9_ick&quot;<br /> [ 21.106414] Disabling unused clock &quot;wdt3_ick&quot;<br /> [ 21.110809] Disabling unused clock &quot;wdt3_fck&quot;<br /> [ 21.115234] Disabling unused clock &quot;gpio2_dbck&quot;<br /> [ 21.119781] Disabling unused clock &quot;gpio3_dbck&quot;<br /> [ 21.124389] Disabling unused clock &quot;gpio4_dbck&quot;<br /> [ 21.128967] Disabling unused clock &quot;gpio5_dbck&quot;<br /> [ 21.133544] Disabling unused clock &quot;gpio6_dbck&quot;<br /> [ 21.138122] Disabling unused clock &quot;gpt9_fck&quot;<br /> [ 21.142517] Disabling unused clock &quot;gpt8_fck&quot;<br /> [ 21.146942] Disabling unused clock &quot;gpt7_fck&quot;<br /> [ 21.151336] Disabling unused clock &quot;gpt6_fck&quot;<br /> [ 21.155761] Disabling unused clock &quot;gpt5_fck&quot;<br /> [ 21.160156] Disabling unused clock &quot;gpt4_fck&quot;<br /> [ 21.164550] Disabling unused clock &quot;gpt3_fck&quot;<br /> [ 21.168975] Disabling unused clock &quot;gpt2_fck&quot;<br /> [ 21.173339] Disabling unused clock &quot;gpt1_ick&quot;<br /> [ 21.177764] Disabling unused clock &quot;wdt1_ick&quot;<br /> [ 21.182159] Disabling unused clock &quot;wdt2_ick&quot;<br /> [ 21.186584] Disabling unused clock &quot;wdt2_fck&quot;<br /> [ 21.190948] Disabling unused clock &quot;gpio1_dbck&quot;<br /> [ 21.195556] Disabling unused clock &quot;gpt1_fck&quot;<br /> [ 21.199981] Disabling unused clock &quot;cam_ick&quot;<br /> [ 21.204315] Disabling unused clock &quot;cam_mclk&quot;<br /> [ 21.208740] Disabling unused clock &quot;des1_ick&quot;<br /> [ 21.213134] Disabling unused clock &quot;sha11_ick&quot;<br /> [ 21.217620] Disabling unused clock &quot;rng_ick&quot;<br /> [ 21.221923] Disabling unused clock &quot;aes1_ick&quot;<br /> [ 21.226348] Disabling unused clock &quot;ssi_ick&quot;<br /> [ 21.230682] Disabling unused clock &quot;mailboxes_ick&quot;<br /> [ 21.235504] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.239990] Disabling unused clock &quot;mcbsp_ick&quot;<br /> [ 21.244476] Disabling unused clock &quot;gpt10_ick&quot;<br /> [ 21.248992] Disabling unused clock &quot;gpt11_ick&quot;<br /> [ 21.253448] Disabling unused clock &quot;hdq_ick&quot;<br /> [ 21.257781] Disabling unused clock &quot;mspro_ick&quot;<br /> [ 21.262298] Disabling unused clock &quot;des2_ick&quot;<br /> [ 21.266693] Disabling unused clock &quot;sha12_ick&quot;<br /> [ 21.271179] Disabling unused clock &quot;aes2_ick&quot;<br /> [ 21.275573] Disabling unused clock &quot;icr_ick&quot;<br /> [ 21.279907] Disabling unused clock &quot;pka_ick&quot;<br /> [ 21.284210] Disabling unused clock &quot;ssi_ssr_fck&quot;<br /> [ 21.288879] Disabling unused clock &quot;hdq_fck&quot;<br /> [ 21.293212] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.297698] Disabling unused clock &quot;mcbsp_fck&quot;<br /> [ 21.302185] Disabling unused clock &quot;mspro_fck&quot;<br /> [ 21.306671] Disabling unused clock &quot;gpt11_fck&quot;<br /> [ 21.311187] Disabling unused clock &quot;gpt10_fck&quot;<br /> [ 21.315643] Disabling unused clock &quot;dpll4_m6x2_ck&quot;<br /> [ 21.320526] Disabling unused clock &quot;dpll3_m3x2_ck&quot;<br /> [ 21.325378] Disabling unused clock &quot;sys_clkout1&quot;<br /> [ 21.330047] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1<br /> [ 21.342468] registered taskstats version 1<br /> [ 21.348236] fbcvt: 1024x768@60: CVT Name - .786M3-R<br /> [ 21.379608] Console: switching to colour frame buffer device 128x48<br /> [ 21.400665] clock: clksel_round_rate_div: dpll4_m4_ck target_rate 48000000<br /> [ 21.407592] clock: new_div = 9, new_rate = 48000000<br /> [ 21.417175] rtc-ds1307 2-0068: setting system clock to 2009-09-27 16:42:23 UTC (1254069743)<br /> [ 21.426086] Waiting for root device /dev/mmcblk0p2...<br /> [ 21.448944] mmc0: new high speed SD card at address ddce<br /> [ 21.455108] mmcblk0: mmc0:ddce SD02G 1.83 GiB <br /> [ 21.460021] mmcblk0: p1 p2<br /> [ 21.539916] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended<br /> [ 21.548187] kjournald starting. Commit interval 5 seconds<br /> [ 21.556823] EXT3 FS on mmcblk0p2, internal journal<br /> [ 21.561737] EXT3-fs: mounted filesystem with ordered data mode.<br /> [ 21.567779] VFS: Mounted root (ext3 filesystem) on device 179:2.<br /> [ 21.574066] Freeing init memory: 204K<br /> INIT: version 2.86 booting<br /> Please wait: booting...<br /> &lt;/pre&gt;<br /> <br /> = I2C analysis =<br /> <br /> Using [http://www.lm-sensors.org/wiki/I2CTools I2C tools] you can analyze the I2C bus:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -l<br /> i2c-1 i2c OMAP I2C adapter I2C adapter<br /> i2c-2 i2c OMAP I2C adapter I2C adapter<br /> i2c-3 i2c OMAP I2C adapter I2C adapter<br /> &lt;/pre&gt;<br /> <br /> Zippy Board uses i2c-2 for the RTC and EEPROM:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:/bin# i2cdetect -y -r 2<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f<br /> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- <br /> 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- <br /> 70: -- -- -- -- -- -- -- -- <br /> &lt;/pre&gt;<br /> <br /> * EEPROM is at 0x50<br /> * RTC is at 0x68<br /> <br /> =EEPROM=<br /> <br /> AT24 EEPROM ([http://www.atmel.com/dyn/resources/prod_documents/doc5156.pdf AT24C01B]) is used to identify Zippy board. See [[BeagleBoardPinMux#Expansion_boards|expansion board]] how this is done.<br /> <br /> Using Linux i2cdump tool at bus 2 address 0x50 the content of this EEPROM is given:<br /> <br /> &lt;pre&gt;<br /> root@beagleboard:~# i2cdump 2 0x50 b<br /> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef<br /> 00: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> 80: 00 01 00 01 01 00 00 00 ff ff ff ff ff ff ff ff .?.??...........<br /> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................<br /> &lt;/pre&gt;<br /> <br /> <br /> = Schematic Diagram =<br /> <br /> * [[media:zippy_schematic.pdf|Zippy_schematic]]<br /> <br /> = Where to purchase the Zippy board =<br /> <br /> The Zippy board can be purchased from:<br /> <br /> USA: [http://www.tincantools.com/product.php?productid=16149&amp;cat=0&amp;page=1&amp;featured www.tincantools.com]<br /> <br /> Canada: [http://www.robotcraft.ca/webshop/p363/BeagleBuddy-Zippy-Ethernet-Combo-Board/product_info.html?osCsid=vf1k1td5vuckpag60fknoebc43 www.robotcraft.ca]<br /> <br /> Germany: [http://www.watterott.com/en/BeagleBuddy-Zippy-Ethernet-Combo-Board www.watterott.com]<br /> <br /> <br /> [[Category:TinCanTools]]<br /> [[Category:BeagleBoard Expansion Boards]]<br /> [[Category:BeagleBoard]]</div>

Rkherod