From: Andre Wolokita <andre.wolokita@analog.com>
To: <linux-crypto@vger.kernel.org>
Subject: Re: griffin u-boot failing to boot
Date: Thu, 19 Mar 2015 13:36:36 +1100 [thread overview]
Message-ID: <550A3634.5020903@analog.com> (raw)
In-Reply-To: <550A2E29.6050209@analog.com>
On 19/03/15 13:02, Andre Wolokita wrote:
> Hi guys,
>
> I'm experiencing a strange issue when booting up u-boot on my older ezkit (red board, pre-1.0). Yesterday I updated u-boot and openocd to the 1.0.0.BR tag and build u-boot. I tried running u-boot on a 1.0 ezkit but found that the board was faulty. Then I went back to using the old ezkit, booting via JTAG, init.elf, u-boot, all that stuff, and everything was still working fine. Today when I get in to work I try to boot up again and get no response over the serial connection. When I check the Griffin registers on GDB, I find that the PC doesn't move from its boot position (0x5094 or thereabouts). Basically the ezkit will no longer boot into uboot. I've tried both my LPC and HPC boards and neither work. Unfortunately I don't have access to a 1.0 board as we only have one and it is being use
d by someone else.
>
> Any ideas?
>
> Regards,
>
> Andre.
>
Oops! Just ignore this - it was meant for the blackfin mailing list. I guess that's what happens when you haven't had your first coffee and forget that most Linux lists begin with linux-*.
--
Andre Wolokita (andre.wolokita@analog.com)
Design Engineer, Analog Devices Australia Pty Ltd
Unit 3, 97 Lewis Road, Wantirna, Victoria, 3152, AUSTRALIA
Direct: +61 3 9881 9933 Main: +61 3 9881 9999
Fax: +61 3 9881 9988 Web: www.analog.com/au
Embedded DSP software for multimedia & telecommunications.
This communication is proprietary and confidential.
prev parent reply other threads:[~2015-03-19 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 2:02 griffin u-boot failing to boot Andre Wolokita
2015-03-19 2:36 ` Andre Wolokita [this message]
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=550A3634.5020903@analog.com \
--to=andre.wolokita@analog.com \
--cc=linux-crypto@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.