From owner-freebsd-embedded@FreeBSD.ORG Fri Jan 30 07:12:59 2015 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A616C376 for ; Fri, 30 Jan 2015 07:12:59 +0000 (UTC) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68B6AD1A for ; Fri, 30 Jan 2015 07:12:59 +0000 (UTC) Received: by mail-oi0-f47.google.com with SMTP id a141so33525421oig.6 for ; Thu, 29 Jan 2015 23:12:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SyPNQHS79QKas0NxcVCo4jzejO9kzcosuU5w/5f7DXE=; b=hpx0obzKVMQQp4pRNpcSEraI9Cb/y/teRXEmPnmHR3QEBCmtGJcQwAlaLuxAfzdLk7 eE67AVE3V50GM4Tj3rA4kUvVKm4q8LyZSFmoSuFS/28wRzuLlFOQ2UKkEXfDJGm/k/pN PjDZVA118/lUMXb3+OSrXLoWLyWsSYBNFAvRvgipFYvYIg4eyeETRuFCv8eRUrFgEid+ 6xFGZESpFQFASbKXiJrLBfl7a/Vp5ULUCNE21R/JJBZKTPiNLFUKd/3eKtniqOZEX6Lw oBkihZi8kNYGAWAb/yx7gz91x+h6+larQPZ1XbY6q/om3DBtxl6m2S0tcKUbm37dpB/g lFpQ== MIME-Version: 1.0 X-Received: by 10.202.62.70 with SMTP id l67mr2706723oia.59.1422601978862; Thu, 29 Jan 2015 23:12:58 -0800 (PST) Received: by 10.76.114.47 with HTTP; Thu, 29 Jan 2015 23:12:58 -0800 (PST) In-Reply-To: <89D38B3E-5315-469F-97D5-EA3CA4D22D23@van-laarhoven.org> References: <68D3F200-5FF2-4C06-A029-4A753387B0F3@van-laarhoven.org> <89D38B3E-5315-469F-97D5-EA3CA4D22D23@van-laarhoven.org> Date: Thu, 29 Jan 2015 23:12:58 -0800 Message-ID: Subject: Re: RBPi Doesn't Boot With GPS GPIO Board Attached From: Reza Nikoopour To: Nick Hibma Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2015 07:12:59 -0000 Nick, Sorry, the previous email was supposed to go to the entire mailing list and it looks like I messaged only you. I'm currently working on figuring out the right way to get CrochetBSD to build the build uboot using the configuration file I set up. I will send an email detailing the steps I took to resolve the problem as soon as I solve it. Reza On Thu, Jan 29, 2015 at 11:09 PM, Nick Hibma wrote= : > And how are you going. To resolve this? > > Met vriendelijke groet, > > Nick Hibma > > Op 30 jan. 2015 om 07:27 heeft Reza Nikoopour het > volgende geschreven: > > Hey guys, > > I wanted to update everyone in case someone has similar issues in the > future. The problem isn't with FreeBSD's serial console. It's actually = an > issue with the GPIO board communicating with u-boot's serial console. > > Thanks for your help! > Reza > > On Thu, Jan 22, 2015 at 2:45 AM, Nick Hibma > wrote: > >> This problem has been haunting us for quite some years, and we have >> always separate hardware to enable GPS manually only after boot. It -mig= ht- >> hit the keystroke to enter the BIOS, which is a big no-no for embedded >> devices in remote environments. You really want to make sure you don=E2= =80=99t get >> bitten by that. There is usually no way to disable BIOS entry completely >> (Soekris BIOS, ALIX BIOS, CoreBoot BIOS). >> >> Note: I am talking about BIOS, not even boot loader here=E2=80=A6 >> >> Nick >> >> > On 21 Jan 2015, at 23:25, Reza Nikoopour wrote: >> > >> > Adrian, >> > >> > It seems like you were right about the serial port taking in the GPS >> output >> > as valid input. I disabled the serial port login for Raspbian and I w= as >> > able to boot into a shell with the GPS board attached. >> > >> > Reza >> > >> > On Wed, Jan 21, 2015 at 11:16 AM, Adrian Chadd >> wrote: >> > >> >> Hi, >> >> >> >> Does the GPS add-on speak to the raspberry PI serial console? If so, >> >> it's likely outputting a whole lot of GPS data via serial, and the >> >> boot loaders for both operating systems are interpreting that as vali= d >> >> input. >> >> >> >> >> >> >> >> -a >> >> >> >> >> >> On 21 January 2015 at 09:57, Reza Nikoopour >> wrote: >> >>> Hello, >> >>> >> >>> I'm currently building an NTP server using the following set up: >> >>> >> >>> Raspberry Pi B+ < >> >>> >> >> >> http://www.amazon.com/gp/product/B00LPESRUK/ref=3Doh_aui_detailpage_o01_= s00?ie=3DUTF8&psc=3D1 >> >>>> >> >>> Raspberry PI GPS Add-on < >> >>> http://imall.iteadstudio.com/raspberry-pi-gps-add-on.html > >> >>> FreeBSD 10.1 built with CrochetBSD >> >>> >> >>> I was able to build an img with Crochet and get the Pi to boot into = a >> >>> shell. However, whenever I booting the Pi with the GPS board >> attached it >> >>> will not boot. >> >>> >> >>> When I plug in the GPS Add-on into the GPIO connector, my Pi fails t= o >> >> boot >> >>> before starting the kernel. It boots to the point where it says >> "Press >> >>> enter to prevent auto boot" and then the letter 'L' shows up and >> starts >> >>> erasing text from the screen. >> >>> >> >>> I was initially using a 1.5A power supply. It was suggested to me t= o >> try >> >>> using a stronger power supply so I tried a 2.1A power supply, but th= at >> >>> didn't work either. Using the 2.1A power supply resulted in the sam= e >> >> boot >> >>> problem described above. >> >>> >> >>> Next I tried using Raspbian to boot the Pi, but a similar problem >> >>> occurred. The Pi boots without the GPS board attached. When the GP= S >> >> board >> >>> is attached, it boots kernel and when the screen to start Raspbian >> >> Software >> >>> Configuration then the following message prints to the screen >> >> indefinitely: >> >>> >> >>> SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(= e) >> >>> memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystem(j) sak(k) >> >>> show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) >> show-registers(p) >> >>> show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) >> >>> show-blocked-test(w) >> >>> >> >>> Could I get some guidance with fixing this problem? >> >>> >> >>> Thanks! >> >>> Reza >> >>> _______________________________________________ >> >>> freebsd-embedded@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >> >>> To unsubscribe, send any mail to " >> >> freebsd-embedded-unsubscribe@freebsd.org" >> >> >> > _______________________________________________ >> > freebsd-embedded@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >> > To unsubscribe, send any mail to " >> freebsd-embedded-unsubscribe@freebsd.org" >> >> >