On 27-02-2014 15:02, [email protected] wrote:
----- Andrew Wafaa <[email protected]> a écrit :
Hi Guillaume,
On 27-02-2014 12:46, Guillaume Gardet wrote:
> Hi,
>
> Le 27/02/2014 10:50, Andrew Wafaa a écrit :
>> On 27-02-2014 09:34, Andrew Wafaa wrote:
>>> Hi,
>>>
>>> I'm currently trying to bring up a uEVM board, and have what I
>>> believe all the correct components for it [0]. Regardless of having a
>>> dtb package and using kernel 3.14-rc2 it still fails to boot, with
>>> u-boot complaining. Below is my boot log, does anyone have ideas/tips
>>> to resolve this?
>>>
>>> U-Boot SPL 2014.01 (Feb 25 2014 - 21:55:07)
>>> OMAP5432 ES2.0
>>>
>>>
>>> U-Boot 2014.01 (Feb 25 2014 - 21:55:07)
>>>
>>> CPU : OMAP5432 ES2.0
>>> Board: OMAP5432 uEVM
>>> I2C: ready
>>> DRAM: 2 GiB
>>> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
>>> Using default environment
>>>
>>> SATA link 0 timeout.
>>> AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
>>> flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
>>> scanning bus for devices...
>>> Found 0 device(s).
>>> Net: No ethernet found.
>>> Hit any key to stop autoboot: 0
>>> mmc0 is current device
>>> SD/MMC found on device 0
>>> ** Unrecognized filesystem type **
>>> 4713776 bytes read in 271 ms (16.6 MiB/s)
>>> ** File not found /boot/omap5-uevm.dtb **
>>> Booting from mmc0 ...
>>> Kernel image @ 0x80200000 [ 0x000000 - 0x47ed30 ]
>>> ERROR: Did not find a cmdline Flattened Device Tree
>>> Could not find a valid device tree
>>> mmc1(part 0) is current device
>>> SD/MMC found on device 1
>>> ** Unrecognized filesystem type **
>>> ** No partition table - mmc 1 **
>>>
>>> I'm hoping to be able to demo this at Linaro Connect next week with
>>> Xen running ontop.
>>>
>>> Thanks,
>>> Andy
>>
>> Sorry I forgot the pointer to the repo with the modified packages!
>>
>> https://build.opensuse.org/project/show/home:FunkyPenguin:ARM:OMAP5
>
> According to your error message, you are missing the omap5-uevm.dtb
> file in /boot folder.
> Maybe it is in /boot/dtb instead. Try to copy it in the /boot folder.
>
Indeed the .dtb was only in /boot/dtb. I copied it into /boot/boot and
into /boot but still fail with the same error.
Just to be sure, you copy it in /boot folder on boot partition (1st
partition)?
It seems that your u-boot does not load boot.scr. Could you stop auto
boot and give us the result of the 'print' command, please?
Output from print command:
# print
arch=arm
baudrate=115200
board=omap5_uevm
board_name=omap5_uevm
bootcmd=run findfdt; run mmcboot;setenv mmcdev 1; setenv bootpart 1:2;
setenv mmcroot /dev/mmcblk0p2 rw; run mmcboot;
bootdelay=1
bootdir=/boot
bootfile=zImage
bootpart=0:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source
${loadaddr}
console=ttyO2,115200n8
cpu=armv7
fdt_high=0xffffffff
fdtaddr=0x80F80000
fdtfile=undefined
findfdt=if test $board_name = omap5_uevm; then setenv fdtfile
omap5-uevm.dtb; fi; if test $board_name = dra7xx; then setenv fdtfile
dra7-evm.dtb; fi;if test $fdtfile = undefined; then echo WARNING: Could
not determine device tree to use; fi;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env
import -t ${loadaddr} ${filesize}
loadaddr=0x80200000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} uEnv.txt
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile};
loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmcargs=setenv bootargs console=${console} ${optargs} vram=${vram}
root=${mmcroot} rootfstype=${mmcrootfstype}
mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on
device ${mmcdev};if run loadbootenv; then echo Loaded environment from
${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running
uenvcmd ...;run uenvcmd;fi;if run loadimage; then run loadfdt; echo
Booting from mmc${mmcdev} ...; run mmcargs; bootz ${loadaddr} -
${fdtaddr}; fi;fi;
mmcdev=0
mmcroot=/dev/mmcblk1p2 rw
mmcrootfstype=ext4 rootwait
partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs}
rdaddr=0x81000000
scsidevs=0
soc=omap5
stderr=serial
stdin=serial
stdout=serial
usbethaddr=02:21:03:5f:0e:70
usbtty=cdc_acm
vendor=ti
ver=U-Boot 2014.01 (Feb 25 2014 - 21:55:07)
vram=16M
Environment size: 1904/131067 bytes
Maybe try also 'run loadbootscript' command.
This results in ** Unrecognized filesystem type **
Regards,
Andy
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
