Argh, waiting on a pile of JST-XX connectors to get the Blue-world up and running. But thanks!
On Thursday, 18 May 2017 22:21:46 UTC+2, William Hermans wrote: > > UART0 looks to be tied to a 4pin JST-SH connector. How exactly that works > out, you'll have to tell me. I do not own a beaglebone blue. Software wise > though, it should be exactly the same. > > On Thu, May 18, 2017 at 6:01 AM, Niels Jakob Buch <njb...@gmail.com > <javascript:>> wrote: > >> Will try that if attaching the cable does not work.... >> >> Now comes the noob question: How do I attach the cable, seems that there >> is plenty BeagleBone Black tutorials on that, but not sure how to do it on >> the blue one. >> >> On Wednesday, 17 May 2017 23:49:32 UTC+2, William Hermans wrote: >>> >>> A couple of other things you could try. >>> >>> 1) Occasionally installing Linux to an sdcard for this purpose can fail >>> silently. You could try to re-image the sdcard in hopes that this might be >>> the case in your situation. >>> >>> 2) Pick a slightly newer, or slightly older sdcard image, install that. >>> Then see if the problem persists. >>> >>> On Wed, May 17, 2017 at 2:45 PM, William Hermans <yyr...@gmail.com> >>> wrote: >>> >>>> >>>> >>>> On Wed, May 17, 2017 at 2:12 PM, Niels Jakob Buch <njb...@gmail.com> >>>> wrote: >>>> >>>>> That makes sense, will try that. >>>>> >>>>> But are there no log-file where this kernel output is stored? >>>>> >>>> >>>> Well it could be, but I do not think Robert persists logs between >>>> reboots. Maybe I'm wrong. So then assuming if what I say is true, you'd >>>> have to hope the error is actually logged. Then the problem is that if you >>>> lose all connectivity, how do you propose to see that information ? >>>> >>>> With a serial debug cable, you'll be directly connected to a tty >>>> terminal, so networking issues will not effect that. Which means not only >>>> can you get additional debug info, but you can also log into the system, >>>> for further troubleshooting if needed. >>>> >>>> You can try to use: >>>> root@wgd:~# more /var/log/messages >>>> or >>>> root@wgd:~# more /var/log/kern.log >>>> >>>> But I do not think either of these will do you any good. You can check >>>> to make sure though. Do keep in mind there will be a lot of info in there >>>> that does not have anything to do with what you're looking for. So you may >>>> run out of time before you get done reading through the files. >>>> >>>> However, if you have another Linux machine, you could scp those files >>>> to a remote system. If you are using Windows, there is a program called >>>> WinSCP I believe that should allow you to traverse into the /var/log >>>> directory, and copy those files out to your desktop. >>>> >>>> >>>> >>> >>> -- >> 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:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/700db256-78a9-4198-8a41-4f9f477df553%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/700db256-78a9-4198-8a41-4f9f477df553%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/456811c9-7078-4c39-8297-88c2a33ddcb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
