From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1klG0x-0003cc-Tx for barebox@lists.infradead.org; Fri, 04 Dec 2020 18:41:09 +0000 Message-ID: From: Rouven Czerwinski Date: Fri, 04 Dec 2020 19:41:03 +0100 In-Reply-To: References: 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: Running reset stress test To: Fabio Estevam , Barebox List On Fri, 2020-12-04 at 15:05 -0300, Fabio Estevam wrote: > Hi, > > This is probably an easy one :-) Kind of :-) > I would like to run reset stress test in Barebox > > In U-Boot, I do the following: > > => setenv bootcmd reset > => saveenv > => reset $ edit /env/boot/reset #!/bin/sh reset $ nv boot.default=reset $ nv autoboot.timeout=0 $ saveenv $ boot Note that barebox can still be interrupted by holding Ctrl+c and aborting the init sequence, which will not autoboot the board. At least the above lets the nitrogen6x on my desk happily cycle the bootloader. Regards, Rouven Czerwinski _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox