From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout01.posteo.de ([185.67.36.65]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gIaQm-0000Kp-Nm for barebox@lists.infradead.org; Fri, 02 Nov 2018 14:28:14 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 58E50212A3 for ; Fri, 2 Nov 2018 15:27:53 +0100 (CET) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 42mktw4Tmmz6tm8 for ; Fri, 2 Nov 2018 15:27:52 +0100 (CET) Date: Fri, 2 Nov 2018 15:27:51 +0100 From: Patrick Boettcher Message-ID: <20181102152751.2a0b995c@yaise-pc1> 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: Barebox stops working if /env/boot/mmc is removed To: Barebox List Hi list, I'm using barebox 2017.04.0-BSP (phytec's fork though). I'm customizing my environment in a (Yocto) .bbappend-file. When I'm removing (or not adding) the /env/boot/mmc-file the barebox-image created by Yocto is not booting at all, that is, on the serial console I don't see anything. Maybe this is a problem of phytec's fork, but I'm wondering what could create this behavior in general? Missing env-files make barebox not boot. Thanks for any insights in advance. best regards, -- Patrick. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox