Hi William, I boot the BBB from the SD card but I purchased the Adafruit debugging cablehttp://www.adafruit.com/products/954.<http://www.adafruit.com/products/954>At first I was using Win7(64) and downloaded a copy of Putty for uSoft. The default settings for the BBB serial port is 115.2 Kb, 8 data bits,no parity, 1 stop bit and no handshaking. In putty create/load/save a profile for the serial port you are connected to. You can see which one by looking in control panel device manager serial ports. The com port you need will be connected to a Prolific USB to Serial bridge.
The physical connections from the cable to the BBB are BBB Wire Function Pin 1 Black Signal Ground Pin 4 Green Receive Pin 5 White Transmit I did the same thing in Ubuntu but the serial port is /dev/ttyUSB0 with the port configuration settings the same. In Ubuntu, from a terminal enter sudo putty prior to starting the BBB. It's a must have setup to debug u-boot and capture the kernel boot. U-boot is a piece of work all to itself. But if you know how to use it you can back drive the information you get from it to the area in uEnv.txt and the boot loader. Once the kernel is started the kernel messages reflect what you can get from dmesg after you log into the BBB. Yes it is very interesting and exciting/fun. I keep the serial cable connected all the time and my other work is done through the network connections. I use tightvncserver on the BBB and tightvncviwer on the pc for a remote desktop session or Cloud-9 from google chrome as advertised on BB website. Hope I helped. Mike On Thursday, April 17, 2014 11:54:04 AM UTC-7, William Hermans wrote: > > Serial boot ? I have not done that yet, Id like to read a write up of that > if you wrote one. e.g. I have no hands on with serial booting, and perhaps > would like to know how. > > > On Thu, Apr 17, 2014 at 11:45 AM, <mac...@msn.com <javascript:>> wrote: > >> Hi William and Cody, >> >> I have some partially good news. Using Robert's link I did successfully >> build and install v3.14.1-bone2 and I have my BBB up and running. Thanks >> for your support. BTW, watching the board boot over the serial port is jaw >> dropping-ly cool. The software checksum >> calculation speeds seems to be amazing. The arm4regs are reporting 685.2 >> MB/sec. Now I'm having fun. >> >> So now to the questions you are asking so that you can help me. >> >> Note: The USB hub is an externally powered Belkin HS USB 2.0 hub model >> F5U233. >> >> It is not recognized at boot time. I'll try a hot plug and look at dmesg. >> >> No messages appended to dmesg after the hot plug. >> >> the /sys/bus/usb/devices file is empty. >> >> >> On Thursday, April 17, 2014 7:48:42 AM UTC-7, cody wrote: >> >>> Was your hub plugged in at boot or after? I may have a workaround you >>> can try. >>> If you know the hub enumerates post the contents of /sys/bus/usb/devices >>> >>> >>> On Wed, Apr 16, 2014 at 9:59 PM, William Hermans <yyr...@gmail.com>wrote: >>> >>>> I have no hands on with this sort of thing, but I have noticed on >>>> many occations that "we" always need to research the hardware we use on a >>>> particular Linux Distro. >>>> >>>> .Which kernel are you using again ? 3.8.x does not do Hotplug very >>>> well, or even at all. SO if you're hot plugging USB devices into the hub >>>> after the system is up and running, It could be that the hub may buffer >>>> you >>>> from a kernel oops, but still does not recognize the devices. >>>> >>>> It could also be that you need to compile a module or two into the >>>> kernel statically for the HUB to work properly. But that is just a guess >>>> on >>>> my behalf that could be wrong. I have not personally noticed anything >>>> specific to this when browsing menuconfig, but I was not looking for this >>>> sort of thing when compiling my own kernel. >>>> >>>> *OR* Maybe you just need a different hub . . . Perhaps someone with >>>> more experience with this sort of thing will reply and give us their 2 >>>> cents. >>>> >>>> >>>> On Wed, Apr 16, 2014 at 7:40 PM, <mac...@msn.com> wrote: >>>> >>>>> Hi William, >>>>> >>>>> Yes, I realize that the pain is self-inflicted and I want to be clear >>>>> about that. I have a favourite golfer that once said,"I'm an idiot!". >>>>> I've >>>>> uttered those very words once or twice lately. Judging by the forums I >>>>> think others have said similar things. >>>>> >>>>> You would never believe it by my comments but in the late 1980's I was >>>>> doing this full time on a RT VME chassis running UniFlex (Unix variant). >>>>> I >>>>> wrote drivers in C and 68030 assembly language and did some very neat >>>>> stuff. The learning curve was steep back then too. Ah, but I was young! >>>>> Time didn't matter...So I had to see what the kids are getting into these >>>>> days. >>>>> >>>>> I am actually more concerned with another issue regarding attaching a >>>>> USB hub to the USB host on the BBB. After I've done that the system won't >>>>> enumerate any of the devices I've put into the hub. But according to >>>>> dmesg >>>>> the hub itself was successfully installed. >>>>> >>>>> Ideas? >>>>> >>>>> >>>>> >>>>> On Monday, April 14, 2014 3:24:04 PM UTC-7, William Hermans wrote: >>>>>> >>>>>> macarr, just so you know I have been using Debian for a good while >>>>>> and it took me 2-3 tries to get his steps right myself. At the time the >>>>>> instructions were a bit less clear, but the fault was my own ( I was a >>>>>> bit >>>>>> rusty with some of the steps / commands ). >>>>>> >>>>>> I am currently rebuilding my own kernel to the latest from scratch, >>>>>> and so far they seem to work perfectly ( I am about half way through, >>>>>> e.g. >>>>>> I've downloaded all the tools and have compiled the kernel). >>>>>> >>>>>> @Robert, I should be able to do the same steps I took back in >>>>>> December to get a working TFTP/NSF boot/root with the latest kernel ? >>>>>> >>>>>> What about 3.13 ? I remember you saying something about it being a >>>>>> "different animal" some months ago. >>>>>> >>>>>> I would ask on your comments pages for your site, but . . . Yeah >>>>>> editor wont stop loading. >>>>>> >>>>>> >>>>>> On Mon, Apr 14, 2014 at 1:15 PM, <mac...@msn.com> wrote: >>>>>> >>>>>>> Yes Robert, >>>>>>> >>>>>>> You are correct on all counts. I was unaware of the >>>>>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black<http://www.google.com/url?q=http%3A%2F%2Feewiki.net%2Fdisplay%2Flinuxonarm%2FBeagleBone%2BBlack&sa=D&sntz=1&usg=AFQjCNEwHvJG3PDxw3Sfxt5K8nmSnOnirA>. >>>>>>> I performed a google search and found the first site I mentioned. >>>>>>> >>>>>>> Being "new" can be a painful process. Not working on a staff with >>>>>>> others to learn from is even more painful. >>>>>>> >>>>>>> The biggest obstacle is that "you don't know what you don't know". >>>>>>> >>>>>>> Again, I thank you for your efforts. I will be persistent. >>>>>>> >>>>>>> Respectfully, >>>>>>> >>>>>>> -- >>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "BeagleBoard" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to beagleboard...@googlegroups.com. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>> For more options, visit http://beagleboard.org/discuss >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "BeagleBoard" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to beagleboard...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to beagleboard...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
