Hi Leon,
I tried booting the pandaboard as per your suggestions.
When I did that, I got the following error. Do I need to make any changes in
rc.sysinit file or any other initialization scripts?
[ 2.984191] EXT2-fs (mmcblk0p2): error: couldn't mount because of
unsupported optional features (244) [ 3.171356] EXT4-fs (mmcblk0p2):
warning: mounting unchecked fs, running e2fsck is recommended [ 3.182159]
EXT4-fs (mmcblk0p2): recovery complete [ 3.188690] EXT4-fs (mmcblk0p2):
mounted filesystem with ordered data mode. Opts: (null) [ 3.197204] VFS:
Mounted root (ext4 filesystem) on device 179:2.
[ 3.205261] devtmpfs: mounted
[ 3.208679] Freeing init memory: 396K
INIT: version 2.86 booting
[rc.sysinit : script starts]
[mount...]
[udev start]
udevd[1476]: failed to execute '/lib/udev/net.agent' 'net.agent': No such file
or directory
[ 6.100433] omap_vout omap_vout: Unable to apply changes [ 6.100433]
omap_vout omap_vout: Unable to apply changes [ 6.104675] omap_vout
omap_vout: Unable to apply changes [ 6.128082] omap_vout omap_vout: Unable
to apply changes e2fsck 1.41.9 (22-Aug-2009)
e2fsck: No such file or directory while trying to open #/dev/mmcblk0p1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem
(and not swap or ufs or something else), then the superblock is corrupt, and
you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
resize #/dev/mmcblk0p1
resize2fs 1.41.9 (22-Aug-2009)
open: No such file or directory while opening #/dev/mmcblk0p1 e2fsck 1.41.9
(22-Aug-2009)
e2fsck: Superblock invalid, trying backup blocks...
udevd[1493]: failed to execute '/sbin/blkid' '/sbin/blkid -o udev -p
/dev/mmcblk0p1': No such file or directory
Superblock has an invalid journal (inode 8).
Clear? yes
*** ext3 journal has been deleted - filesystem is now ext2 only ***
One or more block group descriptor checksums are invalid. Fix? Yes
Regards,
Prathamesh
-----Original Message-----
From: Leon Anavi [mailto:[email protected]]
Sent: 18 November 2013 14:15
To: Prathamesh P Ghanekar
Cc: [email protected]
Subject: RE: [Tizen General] Tizen on Raspbery pi?
Hi Prathamesh,
On 2013-11-18 04:57, Prathamesh P Ghanekar wrote:
> Hi Leon,
>
> My query goes on the similar lines. I am trying to port TIZEN IVI to
> the Freescale i.MX6 board. As you suggested, I am following GBS build
> process.
> I referred to the Porting guide for pandaboard.
>>
>>
>>
>>
>> s://wiki.tizen.org/wiki/Tizen_IVI_Getting_Started_Guide_For_PandaBoar
>> d
> But, I am not able to understand as to what will be the output of GBS
> build.
>
> My question goes as follows:
>
> Do we get bootloader,uImage,filesystem(modules,drivers etc.) bundled
> together in the image, when we perform GBS build??
> Or we need to compile kernel separately by conventional GNU make and
> then run the GBS-built image on top of it??
For the Tizen port to Allwinner ARMv7 devices that I am working on I had to
build for scratch u-boot (boot loader) and a linux-sunxi kernel specially for
the board that I own. I've mounted them to a bootable microSD card and I put
Tizen images (platform.img, data.img and UMS.img) on top of it. I guess you
should check the documentation of your dev board and do the same for it.
Each dev board has a different hardware and a specific boot loader must be
used. In my case I followed this guide:
b.com/linux-sunxi/u-boot-sunxi/wiki#how-to-make-a-bootable-sunxi-sd-card
The process is similar for PandaBoard. The wiki article contains sections for
"Building the Bootloaders" and "Building the kernel" which are compatible with
PandaBoard.
Best regards,
Leon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information contained and transmitted by this e-mail is confidential and
proprietary to iGATE and its affiliates and is intended for use only by the
recipient. If you are not the intended recipient, you are hereby notified that
any dissemination, distribution, copying or use of this e-mail is strictly
prohibited and you are requested to delete this e-mail immediately and notify
the originator or [email protected] <mailto:[email protected]>. iGATE does
not enter into any agreement with any party by e-mail. Any views expressed by
an individual do not necessarily reflect the view of iGATE. iGATE is not
responsible for the consequences of any actions taken on the basis of
information provided, through this email. The contents of an attachment to this
e-mail may contain software viruses, which could damage your own computer
system. While iGATE has taken every reasonable precaution to minimise this
risk, we cannot accept liability for any damage which you sustain as a result
of software viruses. You should carry out your own virus checks before opening
an attachment. To know more about iGATE please visit www.igate.com
<http://www.igate.com>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general
