From: AndrewCz <andrewcz@neomailbox.net>
To: barebox@lists.infradead.org
Subject: Zyxel NAS540 bricked?
Date: Mon, 27 Feb 2017 05:03:57 -0500 [thread overview]
Message-ID: <20170227100356.GA3007@tharch.hub> (raw)
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.
--Andrew Cz
[1] https://l.unchti.me/2016/02/12/debian-nas540.html
[2] http://zyxel.nas-central.org/wiki/Category:NAS540
--
Only an idiot fights a war on two fronts. Only the heir to the throne
of the kingdom of idiots would fight a war on twelve fronts.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-02-27 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 10:03 AndrewCz [this message]
2017-02-28 7:29 ` Sascha Hauer
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=20170227100356.GA3007@tharch.hub \
--to=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