Re: [opensuse-arm] Re: Re : Re: Re : Re: Re : Re: [opensuse-arm] Issues booting OMAP5 board
Hi,
Le 03/03/2014 10:43, Andrew Wafaa a écrit :
> On 28 February 2014 10:37, Guillaume Gardet wrote:
>> Le 27/02/2014 18:43, Andrew Wafaa a écrit :
>>> On 27-02-2014 17:40, guillaume.gar...@free.fr wrote:
- Andrew Wafaa a écrit :
> On 27-02-2014 15:16, guillaume.gar...@free.fr wrote:
>>> 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=0x
>>> fdtaddr=0x80F8
>>> 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=0x8020
>>> 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=0x8100
>>> 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
>>>
>> You still have an old image. I mean your image does not include all
>> your patches for u-boot.
>>
>> Try to type:
>> mmc dev 1 (or mmc dev 0)
>> mmc rescan
>> load mmc 0:1 0x8200 boot.scr
>>
>> It should load your boot.scr script.
>>
> It seems to load the boot.scr without error, but still fails to boot.
Forgot to add 'source 0x8200' to run boot.scr script.
Maybe try also 'run loadbootscript' command.
>>> This results in ** Unrecognized filesystem type **
>> Look at your loadbootscript var:
>> loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
>>
>> I guess your boot partition is EXT2, 3 or 4, not FAT?
>>
> I'm somewhat confused. I can't see why it is getting fatload, everything
> I can see says either ext2 as the filesystem type and loadscript=load.
> Why fatload is getting there I just don't know.
>
Because you are using a non patched u-boot.
>>> I copied u-boot from openSUSE:Factory:ARM, so how come it's unpatched,
>>> where can I get the correct one?
>> I mean your are not using your latest u-boot-omap5uevm.
> Where should uEnv.txt be located?
We do not use it, so I do not know.
>>> OK, I'm not sure if it's needed or not. I know Nishanth mentioned using it,
>>> but I don't think it's vital.
>> If your boot.scr is ok, then you do not need it.
>>
>>
>> Guillaume
>>
>
> Getting a little closer to getting it working but still failing.
> Attached is the latest log I have from booting, any ideas?
Your error:
[1393545598.566144] Searching for boot device...
[1393545616.599068] Failed to find boot device !
[1393545616.605305] rebootException: reboot in 120 sec...
has been seen on other systems too. Maybe not related to your OMAP5.
It is a Factory image, right?
Could you try to build your image against 13.1, please?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: Re : Re: Re : Re: Re : Re: [opensuse-arm] Issues booting OMAP5 board
On 28 February 2014 10:37, Guillaume Gardet wrote:
>
> Le 27/02/2014 18:43, Andrew Wafaa a écrit :
>> On 27-02-2014 17:40, guillaume.gar...@free.fr wrote:
>>> - Andrew Wafaa a écrit :
On 27-02-2014 15:16, guillaume.gar...@free.fr wrote:
>>
>> 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=0x
>> fdtaddr=0x80F8
>> 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=0x8020
>> 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=0x8100
>> 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
>>
>
> You still have an old image. I mean your image does not include all
> your patches for u-boot.
>
> Try to type:
> mmc dev 1 (or mmc dev 0)
> mmc rescan
> load mmc 0:1 0x8200 boot.scr
>
> It should load your boot.scr script.
>
It seems to load the boot.scr without error, but still fails to boot.
>>>
>>> Forgot to add 'source 0x8200' to run boot.scr script.
>>>
>>>
>
>>
>> > Maybe try also 'run loadbootscript' command.
>> >
>> This results in ** Unrecognized filesystem type **
>
> Look at your loadbootscript var:
> loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
>
> I guess your boot partition is EXT2, 3 or 4, not FAT?
>
I'm somewhat confused. I can't see why it is getting fatload, everything
I can see says either ext2 as the filesystem type and loadscript=load.
Why fatload is getting there I just don't know.
>>>
>>> Because you are using a non patched u-boot.
>>>
>> I copied u-boot from openSUSE:Factory:ARM, so how come it's unpatched, where
>> can I get the correct one?
>
> I mean your are not using your latest u-boot-omap5uevm.
>>
>>>
Where should uEnv.txt be located?
>>>
>>> We do not use it, so I do not know.
>>>
>> OK, I'm not sure if it's needed or not. I know Nishanth mentioned using it,
>> but I don't think it's vital.
>
> If your boot.scr is ok, then you do not need it.
>
>
> Guillaume
>
Getting a little closer to getting it working but still failing.
Attached is the latest log I have from booting, any ideas?
ot SPL 2014.01 (Feb 26 2014 - 21:28:45)
OMAP5432 ES2.0
U-Boot 2014.01 (Mar 03 2014 - 09:27:36)
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
** File not found uEnv.txt **
2126 bytes read in 12 ms (172.9 KiB/s)
Running bootscript from mmc0 ...
## Executing script at 8200
mmc0 is current device
4713776 bytes read in 294 ms (15.3 MiB/s)
69071520 bytes read in 3992 ms (16.5 MiB/s)
47993
[opensuse-arm] Re: Re : Re: Re : Re: Re : Re: [opensuse-arm] Issues booting OMAP5 board
Le 27/02/2014 18:43, Andrew Wafaa a écrit :
> On 27-02-2014 17:40, guillaume.gar...@free.fr wrote:
>> - Andrew Wafaa a écrit :
>>> On 27-02-2014 15:16, guillaume.gar...@free.fr wrote:
>>> >>
>>> >> 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=0x
>>> >> fdtaddr=0x80F8
>>> >> 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=0x8020
>>> >> 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=0x8100
>>> >> 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
>>> >>
>>> >
>>> > You still have an old image. I mean your image does not include all
>>> > your patches for u-boot.
>>> >
>>> > Try to type:
>>> > mmc dev 1 (or mmc dev 0)
>>> > mmc rescan
>>> > load mmc 0:1 0x8200 boot.scr
>>> >
>>> > It should load your boot.scr script.
>>> >
>>> It seems to load the boot.scr without error, but still fails to boot.
>>
>> Forgot to add 'source 0x8200' to run boot.scr script.
>>
>>
>>>
>>> >
>>> >>
>>> >> > Maybe try also 'run loadbootscript' command.
>>> >> >
>>> >> This results in ** Unrecognized filesystem type **
>>> >
>>> > Look at your loadbootscript var:
>>> > loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
>>> >
>>> > I guess your boot partition is EXT2, 3 or 4, not FAT?
>>> >
>>> I'm somewhat confused. I can't see why it is getting fatload, everything
>>> I can see says either ext2 as the filesystem type and loadscript=load.
>>> Why fatload is getting there I just don't know.
>>>
>>
>> Because you are using a non patched u-boot.
>>
> I copied u-boot from openSUSE:Factory:ARM, so how come it's unpatched, where
> can I get the correct one?
I mean your are not using your latest u-boot-omap5uevm.
>
>>
>>> Where should uEnv.txt be located?
>>
>> We do not use it, so I do not know.
>>
> OK, I'm not sure if it's needed or not. I know Nishanth mentioned using it,
> but I don't think it's vital.
If your boot.scr is ok, then you do not need it.
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Re: Re : Re: Re : Re: Re : Re: [opensuse-arm] Issues booting OMAP5 board
On 02/27/2014 11:43 AM, Andrew Wafaa wrote: > On 27-02-2014 17:40, guillaume.gar...@free.fr wrote: >> - Andrew Wafaa a écrit : >>> On 27-02-2014 15:16, guillaume.gar...@free.fr wrote: [..] >>> Where should uEnv.txt be located? >> >> We do not use it, so I do not know. >> > OK, I'm not sure if it's needed or not. I know Nishanth mentioned using > it, but I don't think it's vital. > you can choose either to use boot.scr or the newer uEnv.txt -> traditional usage since a long time is uEnv.txt. boot.scr is binary and has additional benefit of having checksum etc, but uEnv.txt has the benefit of being easily readable (text file) and modifiable if needed (not that boot.scr cannot be regenerated with mkimage). Usually no modification to variables to u-boot defaults should be done For example: https://github.com/eewiki/u-boot-patches/blob/master/v2014.01/0001-omap5_common-uEnv.txt-bootz-n-fixes.patch +#define CONFIG_SUPPORT_RAW_INITRD +#define CONFIG_BOOTDELAY 1 are probably the only valid change All other modifications such as loadaddr, mmcroot can easily be done in boot.scr/uEnv.txt (depending on where zImage, dtbs are located). But I guess, distros prefer to have a different requirements - but I suggest debating them in u-boot mailing list as well. -- Regards, Nishanth Menon -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
