Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 966771 - Cannot boot tegra20-paz00 (aka AC100)
Summary: Cannot boot tegra20-paz00 (aka AC100)
Alias: None
Product: Fedora
Classification: Fedora
Component: arm-boot-config
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Brendan Conoboy
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2013-05-23 22:38 UTC by Nicolas Chauvet (kwizart)
Modified: 2013-08-12 09:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-08-12 09:34:37 UTC
Type: Bug

Attachments (Terms of Use)
boot from tegrarcm and u-boot with kb support (1.48 MB, image/jpeg)
2013-05-24 23:42 UTC, Nicolas Chauvet (kwizart)
no flags Details
boot from a-b-c rc4.1 with modified sleep (1.46 MB, image/jpeg)
2013-05-25 10:00 UTC, Nicolas Chauvet (kwizart)
no flags Details
A boot.scr with test -z's replaced with test -n's (18.50 KB, application/octet-stream)
2013-05-25 18:21 UTC, Brendan Conoboy
no flags Details
Updated boot.scr with small debug addition (18.94 KB, application/octet-stream)
2013-06-04 02:23 UTC, Brendan Conoboy
no flags Details
output latest boot.bcl (4.40 MB, image/jpeg)
2013-06-04 17:23 UTC, Nicolas Chauvet (kwizart)
no flags Details
More diagnostic info boot.scr (19.04 KB, application/octet-stream)
2013-06-04 18:46 UTC, Brendan Conoboy
no flags Details
working boot.cmd for the AC100 (21.95 KB, text/plain)
2013-07-30 20:40 UTC, Nicolas Chauvet (kwizart)
no flags Details

Description Nicolas Chauvet (kwizart) 2013-05-23 22:38:26 UTC
Description of problem:
a-b-c cannot discover the appropriate config option for my device.

Version-Release number of selected component (if applicable):
from f19-rc4 (0.49)

How reproducible:

Steps to Reproduce:
1. boot using an AC100

Actual results:
boot fails

Expected results:
should boot on a kernel-tegra

Additional info:
target configuration.
setenv bootargs console=ttyS0,115200n8 root=UUID=be62c538-034c-40a2-a761-02b7c7d5cec0 ro rootwait 3 cma=64M irqpool LANG=fr_FR.UTF-8 rhgb quiet
ext2load mmc 1:1 4880000 uInitrd
ext2load mmc 1:1 4080000 uImage
ext2load mmc 1:1 5880000 tegra20.dtb
bootm 4080000 4880000 5880000

from there, there is no support to boot from external mmc (1 instead of 0).

To me, the soc is tegra20 on tegra2 devices.
if test -n $soc; then
  if test $soc = tegra20; then
    if test $board = trimslice; then
      run config_trimslice
      run config_tegra
      setenv u_dtb ${soc}-${board}.dtb

But then I miss a u_kernel parameter (not set in config_tegra ?)

Comment 1 Brendan Conoboy 2013-05-23 23:53:57 UTC
On trimslice devices soc is set to "tegra2" which appears different than on your device.  I don't know which is the outlier in this regard.  Please send me the output of "printenv" on your system before boot.scr is loaded.  I will add support for your device.

Comment 2 Nicolas Chauvet (kwizart) 2013-05-24 06:59:54 UTC
A quick copy. (best would be to take a picture, will do later).

boot_targets=mmc1 mmc0 usb0 dhcp

I'm using upstream u-boot from 2013.04 or later.

Comment 3 Brendan Conoboy 2013-05-24 17:10:32 UTC
Ah, this is the first time I've seen upstream uboot used for tegra. Neat.

I made a few changes to arm-boot-config 0.51 so it recognizes soc set to tegra2 and tegra20 as being one in the same.  Your device should end up with the defaults once you use the new version:

u_extraargs "console=ttyS0,115200n8"
setenv u_k_addr 4080000
setenv u_ramfs_addr 4800000
setenv u_dtb_addr 0x02000000 (This gets grabbed from $fdt_addr_r)
setenv skip_dtb ""
setenv pass_dtb 1
setenv u_iodevs usb mmc
setenv u_fs ext2
setenv u_boot bootz

It's not uploaded yet, but in a few minutes/hours RC4.1 will be available with the new version at this location:

Comment 4 Nicolas Chauvet (kwizart) 2013-05-24 22:14:36 UTC
Last message on boot:

No kernel provides dtb named tegra20-paz00.dtb
No value for u_kernel. Use klist dtblist to select.

Comment 5 Nicolas Chauvet (kwizart) 2013-05-24 23:42:26 UTC
Created attachment 752910 [details]
boot from tegrarcm and u-boot with kb support

Comment 6 Nicolas Chauvet (kwizart) 2013-05-24 23:45:13 UTC
board=paz00 but is displayed earlier. (others fields might miss).

Comment 7 Brendan Conoboy 2013-05-25 00:17:30 UTC
Based on the picture it should work.  Are there any errors before the "No kernel provides..." bit?  Another screen capture is fine.

Comment 8 Nicolas Chauvet (kwizart) 2013-05-25 09:58:46 UTC
I need to script to sleep before message disappear 
I've made some experiments (switch mmc usb , bootz -> bootm)
At this step it should autodetect the k3 tegra kernel.

Comment 9 Nicolas Chauvet (kwizart) 2013-05-25 10:00:02 UTC
Created attachment 752980 [details]
boot from a-b-c rc4.1 with modified sleep

Comment 10 Brendan Conoboy 2013-05-25 18:21:41 UTC
Created attachment 753144 [details]
A boot.scr with test -z's replaced with test -n's

Comment 11 Brendan Conoboy 2013-05-25 18:22:22 UTC
Try replacing the RC4.1's boot.scr with the attached file and let me know how it goes.  Thanks!

Comment 12 Nicolas Chauvet (kwizart) 2013-05-25 19:26:31 UTC
No improvement.
still Using k3 tegra3 varriant.
no kernel provides dtb named tegra20-paz00.dtb
No value for u_kernel...

Comment 13 Nicolas Chauvet (kwizart) 2013-05-28 06:36:23 UTC
I've tried so re-use the boot.cmd from f18 adapted to 3.9 beta or my own 3.10 kernel and I've failed to load the initramfs with CRC check failure.
That's probably another problem hidden behing this one.

I've successfully managed to load the kernel initramfs dtb using:
setenv fdt_high 0x2C000000 
and changing the related loadaddr to:
bootm 0x00800000 0x01100000 0x5880000

But then the kernel doesn't seems to load (need to have earlyprintk or boot with more verbosity).

Comment 14 Nicolas Chauvet (kwizart) 2013-05-30 10:40:43 UTC
quick note for me to better understand this loadder stuff:;a=blob;f=include/configs/tegra20-common.h;hb=HEAD

Comment 15 Brendan Conoboy 2013-06-04 02:23:27 UTC
Created attachment 756607 [details]
Updated boot.scr with small debug addition

This boot.scr is against the latest a-b-c which includes better generic tegra support and a "sleep " after claiming no value for u_dtb, plus more debugging output.  Please give it a try and take a picture if it fails.  Thanks!

Comment 16 Nicolas Chauvet (kwizart) 2013-06-04 17:23:47 UTC
Created attachment 756890 [details]
output latest boot.bcl

Comment 17 Brendan Conoboy 2013-06-04 18:46:23 UTC
Created attachment 756925 [details]
More diagnostic info boot.scr

This is an even noisier boot.scr.  The information will scroll off your screen so I added a sleep 1 statement to each set_u_k7.  Please snap a picture that includes the line:
Using kernel k3 (3.9.2-301.fc19.armv7hl.tegra).                                 

u_kernel 3.9.2-301.fc19.armv7hl.tegra                                           

Then finally, when it shows

(IE, where the value for u_kernel is again null).  On my system it doesn't disappear, so things look like this:

catin k3_10
catout tegra20-trimslice.dtb
in set_u_k7 , tegra20-trimslice.dtb, tegra20-trimslice.dtb
Using kernel k3 (3.9.2-301.fc19.armv7hl.tegra).
on_d 11
in set_u_k6 3.9.2-301.fc19.armv7hl.tegra
catin k3_11
catout tegra20-ventana.dtb
u_kernel 3.9.2-301.fc19.armv7hl.tegra
in set_u_k7 3.9.2-301.fc19.armv7hl.tegra, tegra20-ventana.dtb, tegra20-trimslice
on_d 12
in set_u_k6 3.9.2-301.fc19.armv7hl.tegra
catin k3_12

Comment 18 Nicolas Chauvet (kwizart) 2013-06-04 20:52:04 UTC
I fail to understand how it defers than the previous.
I'm not sure to have tested the right version.

Anyway, I don't think we should rewrite all 0:0 1:1 combination but instead rely on upstream builtins: (mmc0 mmc1 usb0 notation and detection methods).;a=blob;f=include/configs/tegra-common-post.h;a=blob;f=include/configs/tegra20-common.h

Also I don't know how the (patched) u-boot on trimslice differs from the this upstream paz00 version.

PS: I won't be able to test again until the end of the week.

Comment 19 Brendan Conoboy 2013-06-04 21:12:43 UTC
Not clear what you're proposing re 0:0 1:1 etc.

Perhaps you downloaded the latest boot.scr and it was saved as boot.scr.1?

The md5sum of the most recent is:
9b01a9390d97e8da89a8fd0c943bd6bb  boot.scr

Comment 20 Nicolas Chauvet (kwizart) 2013-07-23 19:51:41 UTC
Fixed with 0.56 somehow.

Comment 21 Nicolas Chauvet (kwizart) 2013-07-30 20:38:32 UTC
Re-opening as I've missed some rpmnew files, so removing them made the boot to fail again.

Comment 22 Nicolas Chauvet (kwizart) 2013-07-30 20:40:18 UTC
Created attachment 780835 [details]
working boot.cmd for the AC100

Comment 23 Nicolas Chauvet (kwizart) 2013-08-12 09:34:37 UTC
back to the closed state for this bug as I have found that some rpmnew files where still present.

That been said, I expect a-b-c should use something like /usr/share/a-b-c.d instead of /etc/a-b-c.d to store the system wide configuration instead of using /etc/a-b-c.d that should be reserved for administrators.
(I can open a new report if needed).

Note You need to log in before you can comment on or make changes to this bug.