U-Boot SPL 2011.09 does not boot on Pandaboard EA1

Bug #901577 reported by Marcin Juszkiewicz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro U-Boot
Fix Released
Undecided
John Rigby
u-boot-linaro (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have Pandaboard EA1 which was running fine with older Linaro images. Today I booted it with fresh image (after some time of offline) and got this:

U-Boot SPL 2011.09 (Nov 22 2011 - 20:54:48)
Texas Instruments OMAP4430 ES2.0
SDRAM: identified size not same as expected size identified: 0 expected: 40000000

Board hang.

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :
Download full text (4.0 KiB)

SPL output with DEBUG enabled:

U-Boot SPL 2011.09-rc2 (Dec 08 2011 - 10:07:02)
Texas Instruments OMAP4430 ES2.0
Enable clock domain - 0x4a009400
Enable clock domain - 0x4a009300
Enable clock domain - 0x4a008b00
Enable clock domain - 0x4a008d00
Enable clock module - 0x4a307838
Enable clock module - 0x4a009460
Enable clock module - 0x4a009468
Enable clock module - 0x4a009470
Enable clock module - 0x4a009478
Enable clock module - 0x4a009480
Enable clock module - 0x4a008b30
Enable clock module - 0x4a008b38
Enable clock module - 0x4a009360
Enable clock module - 0x4a0093e0
Enable clock module - 0x4a008d20
Enable clock module - 0x4a009438
Enable clock module - 0x4a009328
Enable clock module - 0x4a009330
Enable clock module - 0x4a0094f0
Enable clock module - 0x4a307840
Enable clock module - 0x4a0094a0
Enable clock module - 0x4a0094a8
Enable clock module - 0x4a0094b0
Enable clock module - 0x4a0094b8
Enable clock module - 0x4a307830
Enable clock module - 0x4a009550
Enable clock domain - 0x4a009400
Enable clock domain - 0x4a009300
Enable clock domain - 0x4a008b00
Enable clock domain - 0x4a008d00
do_scale_vcore: volt - 1417 offset_code - 0x39
do_scale_vcore: volt - 1200 offset_code - 0x28
do_scale_vcore: volt - 1200 offset_code - 0x28
setup_dplls
Core DPLL configured}
                     PER DPLL locked
MPU DPLL locked
Enable clock domain - 0x4a008900
Enable clock domain - 0x4a008f00
Enable clock domain - 0x4a004400
Enable clock domain - 0x4a009100
Enable clock domain - 0x4a009200
Enable clock domain - 0x4a004500
Enable clock domain - 0x4a008c00
Enable clock domain - 0x4a009000
Enable clock domain - 0x4a009100
Enable clock domain - 0x4a008a00
Enable clock module - 0x4a008920
Enable clock module - 0x4a008f20
Enable clock module - 0x4a008f28
Enable clock module - 0x4a004420
Enable clock module - 0x4a008828
Enable clock module - 0x4a008e20
Enable clock module - 0x4a008e28
Enable clock module - 0x4a008e40
Enable clock module - 0x4a009338
Enable clock module - 0x4a009368
Enable clock module - 0x4a004528
Enable clock module - 0x4a004530
Enable clock module - 0x4a004538
Enable clock module - 0x4a004540
Enable clock module - 0x4a004548
Enable clock module - 0x4a004550
Enable clock module - 0x4a004558
Enable clock module - 0x4a004560
Enable clock module - 0x4a004568
Enable clock module - 0x4a004570
Enable clock module - 0x4a004578
Enable clock module - 0x4a004580
Enable clock module - 0x4a004588
Enable clock module - 0x4a009450
Enable clock module - 0x4a009428
Enable clock module - 0x4a009430
Enable clock module - 0x4a009440
Enable clock module - 0x4a009448
Enable clock module - 0x4a009488
Enable clock module - 0x4a0094e0
Enable clock module - 0x4a0094f8
Enable clock module - 0x4a009500
Enable clock module - 0x4a009508
Enable clock module - 0x4a009520
Enable clock module - 0x4a009528
Enable clock module - 0x4a009560
Enable clock module - 0x4a009540
Enable clock module - 0x4a009548
Enable clock module - 0x4a009558
Enable clock module - 0x4a307878
Enable clock module - 0x4a307830
Enable clock module - 0x4a009020
Enable clock module - 0x4a009028
Enable clock module - 0x4a009120
Enable clock module - 0x4a009220
Enable clock module - 0x4a009358
Enable clock module -...

Read more...

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

http://<email address hidden>/msg65024.html says:

> X-load builds work just fine on my pandaboard, which is Rev EA1.
> Perhaps it is a board rev issue.

Yes it is. SPL works on everything other than a Panda with OMAP4430 ES2.0. I could reproduce it on an ES2.0 Panda. Please note that an SDP with OMAP4430 ES2.0 works too, which is rather strange. At the outset, it looked like a memory issue so I used CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS, which removed memory check failure. However, it still fails at the same point. The fact that Lauterbach is not working on my board is not helping my investigations. Also, the only ES2.0 Panda I could find here is also being used by another person. So, I have to time-share it with him. I will try to investigate it further today as soon as I get the board.

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

I just tested with my ES2.0 board but unfortunately I'm unable to reproduce the issue:

U-Boot SPL 2011.09 (Nov 22 2011 - 20:54:48)
Texas Instruments OMAP4430 ES2.0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09 (Nov 22 2011 - 20:54:48)

CPU : OMAP4430
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
WARNING: Caches not enabled
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
reading boot.scr

514 bytes read
Loaded script from boot.scr
Running bootscript from mmc0 ...
## Executing script at 82000000
reading uImage

5176344 bytes read
reading uInitrd

1848112 bytes read
reading board.dtb

356 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Ubuntu Kernel
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 5176280 Bytes = 4.9 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
   Image Name: Ubuntu Initrd
   Image Type: ARM Linux RAMDisk Image (uncompressed)
   Data Size: 1848048 Bytes = 1.8 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 815f0000
   Booting using the fdt blob at 0x815f0000
   Loading Kernel Image ... OK
OK
   reserving fdt memory region: addr=9d000000 size=3000000
   reserving fdt memory region: addr=b0000000 size=10000000
   Using Device Tree in place at 815f0000, end 815f3163

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Linux version 3.1.0-1402-linaro-lt-omap (buildd@buttercup) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #5~oneiric1-Ubuntu SMP PREEMPT Sat Nov 19 05:23:05 UTC 2011 (Ubuntu 3.1.0-1402.5~oneiric1-linaro-lt-omap 3.1.1)
[ 0.000000] CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: OMAP4 Panda board, model: TI OMAP4 PandaBoard
[ 0.000000] Reserving 50331648 bytes SDRAM for VRAM
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] OMAP4430 ES2.0
[ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c1fd5000 s12736 r8192 614
....

Changed in u-boot-linaro:
assignee: nobody → John Rigby (jcrigby)
Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

CPU got detected correctly, memory was set to 200MHz like it should but nothing more. I gave up.

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :
Changed in u-boot-linaro (Ubuntu):
status: New → Triaged
Changed in u-boot-linaro:
status: New → Triaged
Revision history for this message
John Rigby (jcrigby) wrote :

Looks like a newer fix arrived upstream between v2011.12 and v2012.03-rc1
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=fe7104b307a12f0d5f02526bea00162d95589616

Changed in u-boot-linaro (Ubuntu):
status: Triaged → Fix Released
Changed in u-boot-linaro:
status: Triaged → Fix Released
Marcin Juszkiewicz (hrw)
Changed in linaro-ubuntu:
status: New → Invalid
Fathi Boudra (fboudra)
no longer affects: linaro-ubuntu
Revision history for this message
Sukumar Ghorai (ghorai-sukumar) wrote :

Here I also faceing the same issue; is that I need to use some latest u-boot?
---------------
U-Boot SPL 2011.09 (Nov 19 2011 - 04:44:45)
Texas Instruments OMAP4430 ES2.2
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09 (Nov 19 2011 - 04:44:45)

CPU : OMAP4430
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
WARNING: Caches not enabled
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
Panda #
Panda #
Panda #
Panda # setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p3 rw rootwait rootfstype=ext4 init=/sbin/init ignore_loglevel debug printk.time=1 bootmem_debug=1 earlyprintk'
Panda # setenv bootcmd 'mmc rescan; fatload mmc 0 80200000 uImage-21dec; fatload mmc 0 80700000 omap4-panda-es.dtb; bootm 80200000 - 80700000'
Panda # boot
reading uImage-21dec

4236640 bytes read
reading omap4-panda-es.dtb

13602 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Linux-3.7.0-11091-gf01af9f-dirty
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4236576 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80700000
   Booting using the fdt blob at 0x80700000
   Loading Kernel Image ... OK
OK
   reserving fdt memory region: addr=9d000000 size=3000000
   Loading Device Tree to bfef1000, end bfef7521 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

Sukumar Ghorai: you have newer panda and different problem

Revision history for this message
Sukumar Ghorai (ghorai-sukumar) wrote :
Download full text (6.5 KiB)

I see the problem, not solution :)
---
U-Boot 2011.09 (Nov 19 2011 - 04:44:45)

CPU : OMAP4430
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
WARNING: Caches not enabled
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
Panda #
Panda #
Panda #
Panda #
Panda # setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p3 rw rootwait rootfstype=ext4 init=/sbin/init ignore_loglevel debug printk.time=1 bootmem_debug=1 earlyprintk'
Panda # setenv bootcmd 'mmc rescan; fatload mmc 0 80200000 uImage-21dec; fatload mmc 0 80700000 omap4-panda-es.dtb; bootm 80200000 - 80700000'
Panda # boot
reading uImage-21dec

4243816 bytes read
reading omap4-panda-es.dtb

13602 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Linux-3.7.0-11091-gf01af9f-dirty
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4243752 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80700000
   Booting using the fdt blob at 0x80700000
   Loading Kernel Image ... OK
OK
   reserving fdt memory region: addr=9d000000 size=3000000
   Loading Device Tree to bfef1000, end bfef7521 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.7.0-11091-gf01af9f-dirty (sghorai@bgsxgitb03) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #15 SMP Fri Dec 21 15:50:23 IST 2012
[ 0.000000] CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 PandaBoard
[ 0.000000] debug: ignoring loglevel setting.
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] bootmem::init_bootmem_core nid=0 start=80000 map=af7f5 end=af800 mapsize=5f00
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=80000 end=af800 reserve=0 flags=0
[ 0.000000] bootmem::__free nid=0 start=80000 end=af800
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=80004 end=80008 reserve=1 flags=0
[ 0.000000] bootmem::__reserve nid=0 start=80004 end=80008 flags=0
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=80008 end=80d6d reserve=1 flags=0
[ 0.000000] bootmem::__reserve nid=0 start=80008 end=80d6d flags=0
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=9d000 end=a0000 reserve=1 flags=0
[ 0.000000] bootmem::__reserve nid=0 start=9d000 end=a0000 flags=0
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=af7f5 end=af7fd reserve=1 flags=0
[ 0.000000] bootmem::__reserve nid=0 start=af7f5 end=af7fd flags=0
[ 0.000000] bootmem::mark_bootmem_node nid=0 start=af7fd end=af800 reserve=1 flags=0
[ 0.000000] bootmem::__reserve nid=0 start=af7fd end=af800 flags=0
[ 0.000000] On node 0 totalpages: 261888
[ 0.000000] bootmem::alloc_bootmem_bdata nid=0 size=800000 [2048 pages] align=40 goal=bfffffff limit=0
[ 0.000000] bootmem::__reserve...

Read more...

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

But your problem requires new bug report against kernel. This is about U-Boot bug on my EA1 pandaboard. And it was solved long time ago.

Complaining about random bugs in other random bugs does not make them solved.

Revision history for this message
Sukumar Ghorai (ghorai-sukumar) wrote :

Thanks... and I understand...
I am mange to boot Pandaboard using the latest u-boot:
U-Boot SPL 2013.01-rc2-00022-g42e1321 (Dec 21 2012 - 22:09:54)
OMAP4430 ES2.2
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2013.01-rc2-00022-g42e1321 (Dec 21 2012 - 22:09:54)

CPU : OMAP4430 ES2.2
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
Panda #
Panda #
Panda # setenv bootargs 'console=ttyO2,115200n8 root=/dev/mmcblk0p3 rw rootwait rootfstype=ext4 init=/sbin/init ignore_loglevel debug printk.time=1 bootmem_debug=1 earlyprintk'
Panda # setenv bootcmd 'mmc rescan; fatload mmc 0 82000000 uImage-21dec; fatload mmc 0 85000000 omap4-panda-es.dtb; bootm 82000000 - 85000000'
Panda # boot
reading uImage-21dec
4243816 bytes read in 256 ms (15.8 MiB/s)
reading omap4-panda-es.dtb
13602 bytes read in 8 ms (1.6 MiB/s)
## Booting kernel from Legacy Image at 82000000 ...
   Image Name: Linux-3.7.0-11091-gf01af9f-dirty
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4243752 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 85000000
   Booting using the fdt blob at 0x85000000
   Loading Kernel Image ... OK
OK
   reserving fdt memory region: addr=9d000000 size=3000000
   Using Device Tree in place at 85000000, end 85006521

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.7.0-11091-gf01af9f-dirty (sghorai@bgsxgitb03) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #15 SMP Fri Dec 21 15:50:23 IST 2012
[ 0.000000] CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 PandaBoard
...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.