From: Javier Fileiv <javier.fileiv@gmail.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Loading kernel issues
Date: Fri, 21 Oct 2016 09:41:15 +0200 [thread overview]
Message-ID: <CABvwO2C0MZGk2CC-v=67-Og7n4SZqSpdCfiZBz0QZTTfeckp1w@mail.gmail.com> (raw)
In-Reply-To: <201610210939.59537.jbe@pengutronix.de>
Hello Juerguen, I was looking to buy an ARM9 Jtag because it's what I
though... I would need a JTAG.
Regarding shorting the data lines... do you know exactly what would I
need to do?
Regarding JTAG, which ones are the steps?
Thank you so much
2016-10-21 9:39 GMT+02:00 Juergen Borleis <jbe@pengutronix.de>:
> Hi Javier,
>
> On Thursday 20 October 2016 19:59:54 Javier Fileiv wrote:
>> ups... I think Ive broken everything... I just put at the end of the
>> env/config file "boot nand" and now is looping and at some point it
>> says "ERROR: out of memory".
>> Another thing... I changed vivibootloader in NOR for the barebox, and
>> even if I change to NOR it's looping again and again... What do I do?
>> HELP!
>
> Seems you configured your board into a brick. You now can boot from NOR and
> short some data lines pins at the NAND device to make barebox fail to read its
> environment from NAND and fall back to the built-in default environment
> without that loop.
> Or you need some JTAG equipment to make the SoC working again.
>
> Cheers,
> Juergen
>
> --
> Pengutronix e.K. | Juergen Borleis |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-10-21 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABvwO2ARpHSzYE6Y3JrfFAQ2jEzw3EXfP36goL6kPogcBbNLKQ@mail.gmail.com>
2016-10-18 5:37 ` Sascha Hauer
2016-10-18 8:17 ` Juergen Borleis
2016-10-18 8:24 ` Javier Fileiv
2016-10-18 16:56 ` Javier Fileiv
2016-10-19 7:53 ` Juergen Borleis
2016-10-19 18:17 ` Javier Fileiv
2016-10-19 18:18 ` Javier Fileiv
2016-10-20 9:13 ` Juergen Borleis
2016-10-20 9:17 ` Javier Fileiv
2016-10-20 17:59 ` Javier Fileiv
2016-10-21 7:39 ` Juergen Borleis
2016-10-21 7:41 ` Javier Fileiv [this message]
2016-10-21 7:53 ` Juergen Borleis
2016-10-21 7:54 ` Javier Fileiv
2016-10-21 8:02 ` gianluca
2016-10-21 8:05 ` Juergen Borleis
2016-10-21 8:07 ` Sascha Hauer
2016-10-21 8:11 ` Javier Fileiv
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='CABvwO2C0MZGk2CC-v=67-Og7n4SZqSpdCfiZBz0QZTTfeckp1w@mail.gmail.com' \
--to=javier.fileiv@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=jbe@pengutronix.de \
/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