On 2013-11-20 15:30, Prathamesh P Ghanekar wrote:
Please note that you should create
4 partitions on your SD card. Vfat for the boot patition, ext4 for the
rest.
Yea, I have created 4 partitions on SD card and flashed images accordingly.

I don't have a PandaBoard so I cannot reproduce that case. It seems like an issue related the the file system.
Ok. But I have a fundamental doubt here. Can I use any kernel that is
customized for my platform (here pandaboard) and expect it to work
fine, with suitable changes done using local build to platform build?
Or I have to use the kernel from the git repos of Tizen project?

You have to use a Linux kernel that is compatible with your board. Following the instructions at section 7 of the wiki article about PandaBoard download the latest kernel for OMAP4 and build it: /wiki/Tizen_IVI_Getting_Started_Guide_For_PandaBoard#Building_the_kernel

You will need a Tizen_defconifg file which is also available at the wiki: https://wiki.tizen.org/wiki/Tizen_defconfig

Best regards,
Leon


Regards,
Prathamesh

-----Original Message-----
From: Leon Anavi [mailto:[email protected]]
Sent: 20 November 2013 18:48
To: Prathamesh P Ghanekar
Cc: [email protected]
Subject: RE: [Tizen General] Tizen on Raspbery pi?

Hi Prathamesh,

On 2013-11-20 09:29, Prathamesh P Ghanekar wrote:
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?

I don't have a PandaBoard so I cannot reproduce that case. It seems
like an issue related the the file system. Please note that you should
create
4 partitions on your SD card. Vfat for the boot patition, ext4 for the
rest:
























ki/Tizen_IVI_Getting_Started_Guide_For_PandaBoard#Formatting_Partitions

Although I do not have a PandaBoard I have successfully booted the same
Tizen platform images on open-source hardware device with Allwinner
processor so the tutorial must be ok.

Best regards,
Leon


_[    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:


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


































































mer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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>.






























































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--
http://anavi.org/
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general

Reply via email to