/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beaglebone-getting-startedInstalling SoftwareConnecting to the BeagleBone board is pretty easy, here’s the quick run down of how to do it: 1) Download and install the driver: 32 bit 64 bit 2) Download and install putty: PuTTY ConnectingNow that you hav...en-USTelligent Community 12https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beaglebone-getting-startedMon, 20 May 2013 22:21:41 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:b95b8133-d3d2-437c-b4e4-395c89d44416ericwertz1<p>&quot;<span>I don’t know why, but mine comes up blank and I have to hit enter before it does anything.</span>&quot;</p><p>&nbsp;</p><p>By the time you open putty, the login prompt has already been output and you&#39;ve missed it.&nbsp; By hitting enter (a blank username), it re-issues the prompt.&nbsp; If you open putty early enough, you&#39;ll likely catch the first prompt.&nbsp; Anything that you type before enter is going to be taken as a username, and the first enter will send that and then ask for a password.</p><p>&nbsp;</p><p>On a generic two-wire serial connection, this is pretty much how it has to be -- login (or getty on classic u*ix) can&#39;t tell that you&#39;ve connected and issue you a prompt at that time&nbsp; <span>Serial port logins have behaved this way for 40+ years.</span></p><p>&nbsp;</p><p>Getting a login prompt over the network (with telnet, ssh, etc.) relies on a totally different connection mechanism, and so doesn&#39;t have this behavior.</p><p>&nbsp;</p><p>Looks easy to get started -- thanks.</p><img src="https://community.element14.com/aggbug?PostID=15845&AppID=80&AppType=Weblog&ContentType=0" width="1" height="1">