From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tegra board problems
Date: Tue, 25 Nov 2014 09:00:15 -0700 [thread overview]
Message-ID: <5474A78F.3040301@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ2ThcR0TQ29NCRe6VOd3bX4RFdFLvLyUYmPRNc-Zzt5mA@mail.gmail.com>
On 11/24/2014 09:03 PM, Simon Glass wrote:
> Hi,
>
> I'm a bit messed up with my testing now.
>
> 1. Jetson-TK1: While I2C testing I unfortunately erased part of the
> I2C board ID EEPROM, and now it will not boot. It says:
>
> Dummy read for TPS65913
> Board id = 0x1ff
>
> and then dies. I can probably change the board id back, but I'm not
> sure what it should be! It will boot U-Boot but not the AVP boot
> loader. If someone could list out the contents of their EEPROM (bus 1,
> address 56) that might help.
"AVP boot loader" isn't quite the right term; all bootloaders on Tegra
start out execution on the AVP, and typically transition to the main CPU
(CCPLEX). "fastboot" is unfortunately (since it's also a protocol name)
the term we typically use for the Android/L4T/binary bootloader on this
chip.
Here's my ID EEPROM dump; I don't recall if there's a serial number in
here, or just board type identification. It probably doesn't matter
either way though.
(I2C bus IDs are different in Linux I guess)
# i2cdump -f -y 0 0x56
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 01 00 07 00 77 01 00 00 03 42 00 ff ff ff ff ff ?.?.w?..?B......
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 2. beaver: I cannot get mainline U-Boot to boot a kernel. In fact
> 'part list mmc 0' just prints an error:
>
> ## Unknown partition table
>
> It is getting a partition ID of 0. Is there something wrong with
> Beaver's mmc support in mainline?
>
> The old 2011 U-Boot on the board works though.
Hmm. I haven't tried very recent U-Boot on Beaver; let me check.
> Also a question - are there any Jetson-like Tegra 132 boards available yet?
Not that I know of. Nexus 9 seems to be the best bet, although it's not
useful for bootloader work.
next prev parent reply other threads:[~2014-11-25 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 4:03 [U-Boot] Tegra board problems Simon Glass
2014-11-25 16:00 ` Stephen Warren [this message]
2014-11-25 16:11 ` Stephen Warren
2014-11-25 16:16 ` Simon Glass
2014-11-25 16:25 ` Stephen Warren
2014-11-26 15:39 ` Simon Glass
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=5474A78F.3040301@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.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