From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout02.posteo.de ([185.67.36.66]) by merlin.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gK197-0006V9-2Q for barebox@lists.infradead.org; Tue, 06 Nov 2018 13:11:55 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 8B4622400E6 for ; Tue, 6 Nov 2018 14:11:31 +0100 (CET) Date: Tue, 6 Nov 2018 14:11:26 +0100 From: Patrick Boettcher Message-ID: <20181106141126.1d930ce2@posteo.de> In-Reply-To: <20181106082914.ykoffbmdfqkdaflg@pengutronix.de> References: <20181102152751.2a0b995c@yaise-pc1> <20181104170705.0ad35065@yaise-pc1> <20181106082914.ykoffbmdfqkdaflg@pengutronix.de> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Barebox stops working if /env/boot/mmc is removed To: Sascha Hauer Cc: Barebox List On Tue, 6 Nov 2018 09:29:14 +0100 Sascha Hauer wrote: > > The issue seems to have come from a file which was maybe in a > > previous default environment and has been modified in the > > user-environment and was now remove in the default-env or > > overwritten or whatnot. > > > > It seems that I fixed it by erasing > > the /dev/barebox-environment-partition after flashing the new > > barebox-version. > > > > For the moment this is not an issue for my system/application. It's > > a bit scary though. > > What does "Stops working" mean? Doesn't start at all? Doesn't start > kernel? Your description is a bit vague. Stops working means no more output on the serial port after having barebox_updated the image and issued 'reset'. Hardware reset did not do anything. -- Patrick. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox