[opensuse-arm] Does NOT boot on Pandaboard-ES Rev B3
Hi all, Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 Regards, SunYu -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000
It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS. And why upstream u-boot keep things like that if it is known to be broken? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000
It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken?
Could we convert this into a runtime check against some easily accessible version register? Alex
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000
It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken?
Could we convert this into a runtime check against some easily accessible version register?
Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/ -- Regards, Nishanth Menon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 18/02/2014 15:22, Nishanth Menon a écrit :
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken? Could we convert this into a runtime check against some easily accessible version register?
Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/
So ,we could upgrade to latest u-boot (2014.01) from Base:System project to 13.1:Ports. Dirk or Alex, could you do that, please? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
I will test the new image on RevB3 2014-02-18 23:05 GMT+08:00 Guillaume Gardet <guillaume.gardet@free.fr>:
Le 18/02/2014 15:22, Nishanth Menon a écrit :
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken? Could we convert this into a runtime check against some easily accessible version register?
Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/
So ,we could upgrade to latest u-boot (2014.01) from Base:System project to 13.1:Ports.
Dirk or Alex, could you do that, please?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- 孙钰 Address:北航新主楼F1015 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 20/02/2014 11:54, 孙钰 a écrit :
I will test the new image on RevB3
Before getting a new image for 13.1, you can try the Factory image which should already have u-boot 2014.01. Guillaume
2014-02-18 23:05 GMT+08:00 Guillaume Gardet <guillaume.gardet@free.fr>:
Le 18/02/2014 15:22, Nishanth Menon a écrit :
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken? Could we convert this into a runtime check against some easily accessible version register? Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/
So ,we could upgrade to latest u-boot (2014.01) from Base:System project to 13.1:Ports.
Dirk or Alex, could you do that, please?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 18.02.2014, at 16:05, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 18/02/2014 15:22, Nishanth Menon a écrit :
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken? Could we convert this into a runtime check against some easily accessible version register?
Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/
So ,we could upgrade to latest u-boot (2014.01) from Base:System project to 13.1:Ports.
Dirk or Alex, could you do that, please?
Do you really think it's a good idea to update to the latest u-boot for 13.1? There's a good chance other boards break, no? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
The Uboot in Factory (u-boot 2014.01) works for RevB3, But the kernal fails.... Here follows the message: U-Boot SPL 2014.01 (Feb 05 2014 - 15:07:29) OMAP4460 ES1.1 U-Boot 2014.01 (Feb 05 2014 - 15:07:29) CPU : OMAP4460 ES1.1 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0 Using default environment Net: No ethernet found. Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 2113 bytes read in 3 ms (687.5 KiB/s) Running bootscript from mmc0 ... ## Executing script at 82000000 mmc0 is current device 4690280 bytes read in 215 ms (20.8 MiB/s) 68363617 bytes read in 3077 ms (21.2 MiB/s) 23288 bytes read in 8 ms (2.8 MiB/s) Kernel image @ 0x80000000 [ 0x000000 - 0x479168 ] ## Loading init Ramdisk from Legacy Image at 82000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 68363553 Bytes = 65.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f88af7 Starting kernel ... 2014-02-20 19:04 GMT+08:00 Alexander Graf <agraf@suse.de>:
On 18.02.2014, at 16:05, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 18/02/2014 15:22, Nishanth Menon a écrit :
On 02/18/2014 03:15 AM, Alexander Graf wrote:
Am 18.02.2014 um 09:57 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 16/02/2014 15:31, 孙钰 a écrit :
Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM
Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 It seems to be a known problem. See: http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ
Not sure how it will affect other board revision if we rebuild u-boot without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS.
And why upstream u-boot keep things like that if it is known to be broken? Could we convert this into a runtime check against some easily accessible version register?
Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream also for the very latest, consider: http://patchwork.ozlabs.org/patch/320811/
So ,we could upgrade to latest u-boot (2014.01) from Base:System project to 13.1:Ports.
Dirk or Alex, could you do that, please?
Do you really think it's a good idea to update to the latest u-boot for 13.1? There's a good chance other boards break, no?
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- 孙钰 Address:北航新主楼F1015 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/20/2014 07:19 AM, 孙钰 wrote:
The Uboot in Factory (u-boot 2014.01) works for RevB3, But the kernal fails....
Here follows the message: U-Boot SPL 2014.01 (Feb 05 2014 - 15:07:29) OMAP4460 ES1.1
U-Boot 2014.01 (Feb 05 2014 - 15:07:29)
CPU : OMAP4460 ES1.1 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0 Using default environment
Net: No ethernet found. Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 2113 bytes read in 3 ms (687.5 KiB/s) Running bootscript from mmc0 ... ## Executing script at 82000000 mmc0 is current device 4690280 bytes read in 215 ms (20.8 MiB/s) 68363617 bytes read in 3077 ms (21.2 MiB/s) 23288 bytes read in 8 ms (2.8 MiB/s) Kernel image @ 0x80000000 [ 0x000000 - 0x479168 ] ## Loading init Ramdisk from Legacy Image at 82000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 68363553 Bytes = 65.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f88af7
Starting kernel ...
on my non B3 board: http://slexy.org/view/s2YhugU4oW (3.13) http://slexy.org/view/s2mU9djKVq (3.14-rc3) Looking at the dts, I guessed there are cs1 is being attempted, could someone with a B3 board try http://slexy.org/raw/s20dkh58XR out (not an official patch, just to get an idea). I am trying to get my hands to a B3 board to verify as well, but might take a few days. -- Regards, Nishanth Menon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Is there any instrucution I could follow to compile the kernel or build a image for panda board B3 2014-02-21 5:36 GMT+08:00 Nishanth Menon <nm@ti.com>:
On 02/20/2014 07:19 AM, 孙钰 wrote:
The Uboot in Factory (u-boot 2014.01) works for RevB3, But the kernal fails....
Here follows the message: U-Boot SPL 2014.01 (Feb 05 2014 - 15:07:29) OMAP4460 ES1.1
U-Boot 2014.01 (Feb 05 2014 - 15:07:29)
CPU : OMAP4460 ES1.1 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0 Using default environment
Net: No ethernet found. Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 2113 bytes read in 3 ms (687.5 KiB/s) Running bootscript from mmc0 ... ## Executing script at 82000000 mmc0 is current device 4690280 bytes read in 215 ms (20.8 MiB/s) 68363617 bytes read in 3077 ms (21.2 MiB/s) 23288 bytes read in 8 ms (2.8 MiB/s) Kernel image @ 0x80000000 [ 0x000000 - 0x479168 ] ## Loading init Ramdisk from Legacy Image at 82000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 68363553 Bytes = 65.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f88af7
Starting kernel ...
on my non B3 board: http://slexy.org/view/s2YhugU4oW (3.13) http://slexy.org/view/s2mU9djKVq (3.14-rc3)
Looking at the dts, I guessed there are cs1 is being attempted, could someone with a B3 board try http://slexy.org/raw/s20dkh58XR out (not an official patch, just to get an idea). I am trying to get my hands to a B3 board to verify as well, but might take a few days.
-- Regards, Nishanth Menon
-- 孙钰 Address:北航新主楼F1015 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/20/2014 06:56 PM, 孙钰 wrote:
Is there any instrucution I could follow to compile the kernel or build a image for panda board B3
Let me try a generic linux approach for the same: on xubuntu 12.04 (yeah, I know it is sacrilege in a suse list ;) ): sudo apt-get install gcc-arm-linux-gnueabi you could alternatively pick up a cross compiler from http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/ed... git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout v3.14-rc3 patch -p1< a.diff make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm omap2plus_defconfig make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm zImage dtbs mount the sdcard -> if /media/boot is where MLO and u-boot.img is located, (without an uEnv.txt and using the u-boot defaults:) cp arch/arm/boot/zImage /media/boot/zImage cp arch/arm/boot/dts/omap4-panda-es.dtb /media/boot/zImage sync; sudo umount /media/boot/ -- Regards, Nishanth Menon
I patch and compile the kernel, replace the zImage in the factory image but the kernel does not start as the old kernel here is the new kernel i build, could you check is on older verison board whether I build it correctly? here is the kernel in arch/arm/boot/zImage: http://pan.baidu.com/s/1AHWce 2014-02-21 9:19 GMT+08:00 Nishanth Menon <nm@ti.com>:
On 02/20/2014 06:56 PM, 孙钰 wrote:
Is there any instrucution I could follow to compile the kernel or build a image for panda board B3
Let me try a generic linux approach for the same:
on xubuntu 12.04 (yeah, I know it is sacrilege in a suse list ;) ): sudo apt-get install gcc-arm-linux-gnueabi
you could alternatively pick up a cross compiler from http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/ed...
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout v3.14-rc3
patch -p1< a.diff
make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm omap2plus_defconfig make -j6 CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm zImage dtbs
mount the sdcard -> if /media/boot is where MLO and u-boot.img is located, (without an uEnv.txt and using the u-boot defaults:) cp arch/arm/boot/zImage /media/boot/zImage cp arch/arm/boot/dts/omap4-panda-es.dtb /media/boot/zImage
sync; sudo umount /media/boot/
-- Regards, Nishanth Menon
-- 孙钰 Address:北航新主楼F1015 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/21/2014 12:35 AM, 孙钰 wrote:
I patch and compile the kernel, replace the zImage in the factory image but the kernel does not start as the old kernel
here is the new kernel i build, could you check is on older verison board whether I build it correctly? here is the kernel in arch/arm/boot/zImage: http://pan.baidu.com/s/1AHWce
Darned.. my corporate network prevents me from downloading it for some reason.. anyways, I am trying to get me a B3 later today or so, will give it a shot on my end as well.. -- Regards, Nishanth Menon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/21/2014 01:13 AM, Nishanth Menon wrote:
On 02/21/2014 12:35 AM, 孙钰 wrote:
I patch and compile the kernel, replace the zImage in the factory image but the kernel does not start as the old kernel
here is the new kernel i build, could you check is on older verison board whether I build it correctly? here is the kernel in arch/arm/boot/zImage: http://pan.baidu.com/s/1AHWce
Darned.. my corporate network prevents me from downloading it for some reason.. anyways, I am trying to get me a B3 later today or so, will give it a shot on my end as well..
just realized - the change was for the dts -> so you need to change the dtb as well in the image i guess. -- Regards, Nishanth Menon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 02/20/2014 05:19 AM, 孙钰 wrote:
The Uboot in Factory (u-boot 2014.01) works for RevB3, But the kernal fails....
Did this get resolved? Reading thru thread I don't see any resolution. FYI I see exact same issue using Factory (*1) on my ES Rev B1 (nothing after "Starting kernel ...). Also, I only tried the Factory image as there is no 'openSUSE-13.1-ARM-XFCE-panda-*.raw.xz' image at http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances but the docs at http://en.opensuse.org/HCL:PandaBoard suggest there should be. tony [1] http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Factory-A... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Alexander Graf -
Guillaume Gardet -
Nishanth Menon -
Tony Jones -
孙钰