Hello Roger,
I opened the /out/target/product/blaze/root/init.omap4430.rc file. I
found it is already been modified.
I think it is coped from ./device/ti/blaze/init.omap4430.rc during make
process.
Both LCD and HDMI interface is powered up. But nothing is displayed. I could
do "ls" in the console and can see all android file system
I suspect some display setting is wrong.
Please let me know which setting i should look for.
On Tue, Jul 12, 2011 at 4:39 PM, Roger Quadros <rog...@ti.com> wrote:
> Rajesh,
>
>
> On 07/12/2011 02:01 PM, Rajesh RV wrote:
>
>> Hello Roger,
>>
>> I recreated the .img files after editing the init.omap4430.rc file.
>>
>> Please find my command sequences below
>>
>> > vi ./device/ti/blaze/init.**omap4430.rc
>> deleted the critical settings for ducati
>>
>
> Try editing this file instead
>
> /out/target/product/blaze/**root/init.omap4430.rc
>
> and repeat the below steps.
>
>
> > find out/target/product/blaze -name *.img -exec rm -f {} \;
>> > make
>> > cp out/target/product/blaze/*.img ../../../omap4_emmc_files/.
>>
>>
> cheers,
> -roger
>
> Please let me know whether i edited the right startup script.
>>
>>
>> On Tue, Jul 12, 2011 at 4:25 PM, Roger Quadros <rog...@ti.com
>> <mailto:rog...@ti.com>> wrote:
>>
>> Rajesh,
>>
>>
>> On 07/12/2011 01:49 PM, Rajesh RV wrote:
>>
>> Hello Roger, Sam,
>> Now i downloaded the Database as per the following release notes
>>
>> http://www.omappedia.com/wiki/**__L27.G.2_OMAP4_GingerBread___**
>> Release_Notes<http://www.omappedia.com/wiki/__L27.G.2_OMAP4_GingerBread___Release_Notes>
>> <http://www.omappedia.com/**wiki/L27.G.2_OMAP4_**
>> GingerBread_Release_Notes<http://www.omappedia.com/wiki/L27.G.2_OMAP4_GingerBread_Release_Notes>
>> >
>>
>> That problem is gone and kernel booting happens without any issues.
>>
>> Now i have an other problem. I have removed "critical" setting
>> when the
>> syslink_daemon for ducati is booting as per the release notes.
>>
>>
>> Did you re-create the images after editing the startup script?
>>
>> cheers,
>> -roger
>>
>>
>> I dont see anything on the LCD screen as well as HDMI interface.
>>
>>
>> Please find my bootloader log below
>>
>>
>> Texas Instruments X-Loader 1.41 (Jul 12 2011 - 14:41:44)
>> Starting OS Bootloader from EMMC ...
>>
>>
>> U-Boot 1.1.4-L27.13.1^0 (Jul 12 2011 - 14:40:27)
>>
>> Load address: 0x80e80000
>> DRAM: 1024 MB
>> Flash: 0 kB
>> Using default environment
>>
>> In: serial
>> Out: serial
>> Err: serial
>>
>> efi partition table:
>> 256 128K xloader
>> 512 256K bootloader
>> 2048 8M recovery
>> 18432 8M boot
>> 34816 512M system
>> 1083392 256M cache
>> 1607680 512M userdata
>> 2656256 2183M media
>> Net: KS8851SNL
>> Hit any key to stop autoboot: 3 ^H^H^H 0
>> OMAP44XX SDP #
>>
>> OMAP44XX SDP # print
>> bootargs=console=ttyO2,__**115200n8 mem=456M@0x80000000
>> mem=512M@0xA0000000
>> init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2
>> bootcmd=booti mmc1
>> bootdelay=3
>> baudrate=115200
>> ipaddr=128.247.77.90
>> serverip=128.247.77.158
>> netmask=255.255.254.0
>> bootfile="uImage"
>> stdin=serial
>> stdout=serial
>> stderr=serial
>> ethact=KS8851SNL
>>
>> Environment size: 325/131068 bytes
>> OMAP44XX SDP #
>>
>> Let me know incase i'm missing something,
>>
>>
>>
>> On Tue, Jul 12, 2011 at 3:35 PM, Rajesh RV
>> <varadharajan.raj...@gmail.com
>> <mailto:varadharajan.rajesh@**gmail.com<varadharajan.raj...@gmail.com>
>> >
>> <mailto:varadharajan.rajesh@__**gmail.com <http://gmail.com>
>> <mailto:varadharajan.rajesh@**gmail.com<varadharajan.raj...@gmail.com>
>> >>>
>>
>> wrote:
>>
>> Hello Sam,
>> The latest release notes doesn't talk about the creating
>> system.img manually. system.img is built automatically at
>> the end.
>>
>> I'll try creating system.img manually as per your
>> instruction and
>> let you know the status.
>>
>>
>> On Tue, Jul 12, 2011 at 2:00 PM, Lee, Sam <ri...@softha.com
>> <mailto:ri...@softha.com>
>> <mailto:ri...@softha.com <mailto:ri...@softha.com>>> wrote:
>>
>> Hi, Rajesh RV.____
>>
>> __ __
>>
>> First, I didn’t run eMMC method but it seems that just file
>> issue.____
>>
>> __ __
>>
>> Second, so I offer to remake system.img, see section of
>> ‘Then
>> create system image” of below link.____
>>
>> Prepare files for eMMC then check files in ‘system/bin’
>> and make
>> system.img____
>>
>> __ __
>>
>> http://www.omappedia.org/wiki/**__L27.INC1.7.2_OMAP4_Froyo_**
>> ES2___Release_Notes____<http://www.omappedia.org/wiki/__L27.INC1.7.2_OMAP4_Froyo_ES2___Release_Notes____>
>> <http://www.omappedia.org/**wiki/L27.INC1.7.2_OMAP4_Froyo_**
>> ES2_Release_Notes____<http://www.omappedia.org/wiki/L27.INC1.7.2_OMAP4_Froyo_ES2_Release_Notes____>
>> >
>>
>> __ __
>>
>> I think that release note of TI is not details.____
>>
>> __ __
>>
>> Please add my address in mail thread.____
>>
>> Good luck : - )____
>>
>> __ __
>>
>> Regards,____
>>
>> Sam, Lee____
>>
>>
>> *From:*omapandroid-discussion-**__boun...@gforge.ti.com<omapandroid-discussion-__boun...@gforge.ti.com>
>>
>> <mailto:omapandroid-**discussion-boun...@gforge.ti.**com<omapandroid-discussion-boun...@gforge.ti.com>
>> >
>>
>> <mailto:omapandroid-__**discussion-boun...@gforge.ti.<omapandroid-__discussion-boun...@gforge.ti.>
>> _**_com
>>
>> <mailto:omapandroid-**discussion-boun...@gforge.ti.**com<omapandroid-discussion-boun...@gforge.ti.com>
>> >>
>>
>> [mailto:omapandroid-__**discussion-boun...@gforge.ti.<omapandroid-__discussion-boun...@gforge.ti.>
>> _**_com
>>
>>
>> <mailto:omapandroid-**discussion-boun...@gforge.ti.**com<omapandroid-discussion-boun...@gforge.ti.com>
>> >
>>
>> <mailto:omapandroid-__**discussion-boun...@gforge.ti.<omapandroid-__discussion-boun...@gforge.ti.>
>> _**_com
>>
>> <mailto:omapandroid-**discussion-boun...@gforge.ti.**com<omapandroid-discussion-boun...@gforge.ti.com>>>]
>> *On
>> Behalf Of *Rajesh RV
>> *Sent:* Tuesday, July 12, 2011 3:56 PM
>> *To:* omapandroid-discussion@gforge.**__ti.com
>>
>> <mailto:omapandroid-**discuss...@gforge.ti.com<omapandroid-discuss...@gforge.ti.com>
>> >
>>
>> <mailto:omapandroid-__**discuss...@gforge.ti.com<omapandroid-__discuss...@gforge.ti.com>
>>
>> <mailto:omapandroid-**discuss...@gforge.ti.com<omapandroid-discuss...@gforge.ti.com>
>> >>;
>> android-porting@googlegroups._**_com
>>
>> <mailto:android-porting@**googlegroups.com<android-porting@googlegroups.com>
>> >
>> <mailto:android-porting@__goog**legroups.com<http://googlegroups.com>
>>
>> <mailto:android-porting@**googlegroups.com<android-porting@googlegroups.com>
>> >>
>>
>> *Subject:* [Omapandroid-discussion] Problem booting OMAP
>> Blaze
>> from eMMC____
>>
>> __ __
>>
>> Hi All____
>>
>> I'm trying to boot OMAP Blaze ES 2.2 Version as per the
>> instruction in the following link____
>>
>> __ __
>>
>> http://www.omappedia.org/wiki/**__L27.G.1a_OMAP4430_**
>> GingerBread___Release_Notes___**_<http://www.omappedia.org/wiki/__L27.G.1a_OMAP4430_GingerBread___Release_Notes____>
>> <http://www.omappedia.org/**wiki/L27.G.1a_OMAP4430_**
>> GingerBread_Release_Notes____<http://www.omappedia.org/wiki/L27.G.1a_OMAP4430_GingerBread_Release_Notes____>
>> >
>>
>> __ __
>>
>> __ __
>>
>> But i'm getting the following error____
>>
>> __ __
>>
>> Freeing init memory: 240K____
>>
>> init: cannot open '/initlogo.rle'____
>>
>> Device is holding contsraint on l4per_pwrdm____
>>
>> omapdss HDMI: powerchg (a=0,v=0,s=0/0)->(a=0,v=1,s=0) =
>> (1:A)____
>>
>> omapdss HDMI: pwrchanged => (1,A) = 0____
>>
>> init: Unable to open persistent property directory
>> /data/property errno: 2____
>>
>> init: cannot find '/system/bin/servicemanager', disabling
>> 'servicemanager'____
>>
>> init: cannot find '/system/bin/vold', disabling 'vold'____
>>
>> init: cannot find '/system/bin/netd', disabling 'netd'____
>>
>> init: cannot find '/system/bin/debuggerd', disabling
>> 'debuggerd'____
>>
>> init: cannot find '/system/bin/rild', disabling
>> 'ril-daemon'____
>>
>> init: cannot find '/system/bin/app_process', disabling
>> 'zygote'____
>>
>> init: cannot find '/system/bin/mediaserver', disabling
>> 'media'____
>>
>> init: cannot find '/system/bin/dbus-daemon', disabling
>> 'dbus'____
>>
>> init: cannot find '/system/bin/installd', disabling
>> 'installd'____
>>
>> init: cannot find '/system/etc/install-recovery.**__sh',
>> disabling
>> 'flash_recovery'____
>>
>> init: cannot find '/system/bin/keystore', disabling
>> 'keystore'____
>>
>> init: cannot find '/system/bin/thermaldaemon', disabling
>> 'thermaldaemon'____
>>
>> init: cannot find '/system/bin/pvrsrvinit', disabling
>> 'pvrsrvinit'____
>>
>> init: cannot find '/system/bin/syslink_daemon.__**out',
>> disabling
>> 'baseimage'____
>>
>> init: cannot find '/system/bin/uim-sysfs', disabling
>> 'uim'____
>>
>> init: cannot find '/system/bin/sh', disabling 'console'____
>>
>> enabling adb____
>>
>> adb_open____
>>
>> CPU1: shutdown____
>>
>> __ __
>>
>> __ __
>>
>> Please give me some pointers to debug.____
>>
>> __ __
>>
>> --
>> Regards
>> RVR____
>>
>>
>>
>>
>> --
>> Regards
>> RVR
>>
>>
>>
>>
>> --
>> Regards
>> RVR
>>
>>
>>
>>
>>
>> --
>> Regards
>> RVR
>>
>
>
--
Regards
RVR
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
