From: Sascha Hauer <s.hauer@pengutronix.de>
To: AndrewCz <andrewcz@neomailbox.net>
Cc: barebox@lists.infradead.org
Subject: Re: Zyxel NAS540 bricked?
Date: Tue, 28 Feb 2017 08:29:53 +0100 [thread overview]
Message-ID: <20170228072953.avocsrdr52guzyye@pengutronix.de> (raw)
In-Reply-To: <20170227100356.GA3007@tharch.hub>
Hi Andrew,
On Mon, Feb 27, 2017 at 05:03:57AM -0500, AndrewCz wrote:
> Hello all, hope you are well.
>
> Recently, I followed a guide[1] to reflash my Zyxel NAS540[2] in order
> to put Debian on it. I'm pretty sure I bricked it and am just looking
> for confirmation.
>
> I seem to be running into a bootloop where it will restart every two
> minutes or so. At least that is what seems to be indicated based on the
> frequency of the front panel lights lighting up. I reflashed the 'env'
> and 'kernel2' sections of the NOR flash, but neither went the right way.
> I can dive into the specifics if necessary. However, my concern is that
> I was unable to receive any output from the serial connection.
>
> Given that the barebox 'env' may be corrupt as well as the kernel, is it
> correct to expect that there would be no serial output? Thanks for your
> consideration in this matter.
The Zyxel NAS540 seems to have a Freescale QorIQ LS1024A SoC. There is
no mainline barebox support for this SoC, so Zyxel must have created
their own patches. I know nothing about these patches nor about the SoC,
so I'm sorry I can't really help you.
What I can say is that normally barebox outputs stuff out of the console
even without valid environment or kernel. That is configurable though,
so I can't tell for sure.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-02-28 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 10:03 AndrewCz
2017-02-28 7:29 ` Sascha Hauer [this message]
2017-03-01 17:51 ` Jean-Christophe PLAGNIOL-VILLARD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170228072953.avocsrdr52guzyye@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andrewcz@neomailbox.net \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox