Hi Jose, If your having problems with the kernel, you might want to check how the port for PandaBoards works. [1] For this platform we actually use our own, pre-built kernel images.
Best regards Thomas [1] http://git.mozilla.org/?p=b2g/android-device-panda.git;a=summary On 18.03.2014 22:37, Jose Vidal wrote: > Hi Thomas, > > After a short break, I ready to continue. > > I put > > $(call inherit-product, device/fsl/imx6/arm2_6dq.mk) > > on full_arm2_6dq.mk file and, after the build, finally I have my boot.img > with the next files: > > ============= > drwxrwx--x 2 jvidal jvidal 4096 Mar 18 16:15 data > -rw-r--r-- 1 jvidal jvidal 151 Mar 18 16:15 default.prop > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 dev > -rw-r----- 1 jvidal jvidal 857 Mar 18 16:15 fstab.freescale > -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 16:15 init > -rwxr-x--- 1 jvidal jvidal 777 Mar 18 16:15 init.b2g.rc > -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 16:15 init.freescale.rc > -rwxr-x--- 1 jvidal jvidal 1930 Mar 18 16:15 init.freescale.usb.rc > -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 16:15 init.goldfish.rc > -rwxr-x--- 1 jvidal jvidal 23685 Mar 18 16:15 init.rc > -rwxr-x--- 1 jvidal jvidal 1795 Mar 18 16:15 init.trace.rc > -rwxr-x--- 1 jvidal jvidal 3947 Mar 18 16:15 init.usb.rc > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 proc > drwxr-x--- 2 jvidal jvidal 4096 Mar 18 16:15 sbin > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 sys > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 system > -rw-r--r-- 1 jvidal jvidal 272 Mar 18 16:15 ueventd.goldfish.rc > -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 16:15 ueventd.rc > > ==================== > > But, when I turn on my device, I get: > > ============ > > kernel @ 10808000 (4744188) > ramdisk @ 11800000 (186420) > kernel cmdline: > use boot.img command line: > console=ttymxc0,115200 init=/init androidboot.console=ttymxc0 > androidboot.hardware=freescale var_ts_type=ctw6120 > > Starting kernel ... > > ========== > > This is not booting. > What is the problem ? > Do you have any idea about how I can to debug ? > > > Thanks in advance > > Regards. > > jvidalsm > > > 2014-03-18 5:32 GMT-05:00 Thomas Zimmermann <[email protected]>: > >> Hi Jose, >> >> Good to see that you're making progress. :) I don't know in which parts >> of init.rc we really depend, but it's there on the other platforms, so >> it's probably necessary. >> >> On 18.03.2014 11:04, Jose Vidal wrote: >>> Hi Thomas, >>> >>> Ok, I edited my full_arm2_6dq.mk <http://full_arm2_6dq.mk> file. The >>> line that I used is: >>> >>> $(call inherit-product, >>> $(SRC_TARGET_DIR)/product/generic_no_telephony.mk >>> <http://generic_no_telephony.mk>) >> >> If possible, try to build an include chain like in the example of the >> Nexus 4. I don't know what exactly these files add to the build, but >> some of it might be important. Maybe this could also fix the missing >> init.rc. >> >> Best regards >> Thomas >> >>> >>> After the build, the files inside of boot.img are: >>> >>> drwxrwx--x 2 jvidal jvidal 4096 Mar 18 04:45 data >>> -rw-r--r-- 1 jvidal jvidal 151 Mar 18 04:45 default.prop >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 dev >>> -rw-r----- 1 jvidal jvidal 857 Mar 18 04:45 fstab.freescale >>> -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 04:45 init >>> -rwxr-x--- 1 jvidal jvidal 777 Mar 18 04:45 init.b2g.rc >>> -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 04:45 init.freescale.rc >>> -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 04:45 init.goldfish.rc >>> -rwxr-x--- 1 jvidal jvidal 1795 Mar 18 04:45 init.trace.rc >>> -rwxr-x--- 1 jvidal jvidal 3947 Mar 18 04:45 init.usb.rc >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 proc >>> drwxr-x--- 2 jvidal jvidal 4096 Mar 18 04:45 sbin >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 sys >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 system >>> -rw-r--r-- 1 jvidal jvidal 272 Mar 18 04:45 ueventd.goldfish.rc >>> -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 04:45 ueventd.rc >>> >>> >>> Only I have init.freescale.rc. Is necessary to have init.rc too? >>> >>> Thanks in advance. >>> >>> Best regards. >>> >>> >>> jvidalsm >>> >>> >>> 2014-03-18 4:34 GMT-05:00 Thomas Zimmermann <[email protected] >>> <mailto:[email protected]>>: >>> >>> Hi Jose >>> >>> On 18.03.2014 10:20, Jose Vidal wrote: >>> > Hi Thomas, >>> > >>> > I have the next result: >>> > >>> > ~/B2G$ find . -name "*.mk" -type f | xargs grep -n b2g\.mk >>> > >>> > ./gaia/Android.mk:17:# We will keep this flag in .b2g.mk >>> <http://b2g.mk> <http://b2g.mk> >>> > so |./flash.sh gaia| follows >>> > ./gaia/Android.mk:73:echo $(GAIA_MAKE_FLAGS) > >>> $(GAIA_PATH)/.b2g.mk <http://b2g.mk> >>> > <http://b2g.mk> >>> > ./build/target/product/generic_no_telephony.mk:89:$(call >>> > inherit-product, gonk-misc/b2g.mk <http://b2g.mk> <http://b2g.mk>) >>> > >>> > What it means that ? >>> > I should to edit generic_no_telephony.mk >>> <http://generic_no_telephony.mk> >>> > <http://generic_no_telephony.mk> file and to link to my device or >> I >>> > should to creat a new file? >>> >>> No, you need to make sure that the file is included from within your >>> device directory. For example for the Nexus 4 >>> >>> - device/lge/mako/full_mako.mk <http://full_mako.mk> includes >>> - build/target/product/aosp_base.mk <http://aosp_base.mk>, which >>> includes >>> - build/target/product/full_base.mk <http://full_base.mk>, which >>> includes >>> - build/target/product/generic_no_telephony.mk >>> <http://generic_no_telephony.mk>, which includes >>> - gonk-misc/b2g.mk <http://b2g.mk>. >>> >>> I don't know how your device makefile is called (full_arm2_6dq.mk? >>> <http://full_arm2_6dq.mk?>), but >>> it should provide something similar. And it should should override >> some >>> of the PRODUCT_ variables. Just have a look at the other platforms to >>> get an idea of what exactly is required. >>> >>> Best regards >>> Thomas >>> >>> >>> > >>> > In the bottom the generic_no_telephony.mk >>> <http://generic_no_telephony.mk> >>> > <http://generic_no_telephony.mk> file there is: >>> > >>> > # Overrides >>> > PRODUCT_BRAND := generic >>> > PRODUCT_DEVICE := generic >>> > PRODUCT_NAME := generic_no_telephony >>> > >>> > >>> > Thanks in advance >>> > >>> > Regards, >>> > >>> > jvidalsm >>> > >>> > >>> > >>> > 2014-03-18 4:07 GMT-05:00 Thomas Zimmermann >>> <[email protected] <mailto:[email protected]> >>> > <mailto:[email protected] <mailto:[email protected] >>>>> : >>> > >>> > Hi Jose >>> > >>> > On 18.03.2014 09:56, Jose Vidal wrote: >>> > > Hi Thomas, >>> > > >>> > > No, not that happens. >>> > > >>> > > I have actually: >>> > > >>> > > drwxrwx--x 2 jvidal jvidal 4096 Mar 18 03:37 data >>> > > -rw-r--r-- 1 jvidal jvidal 151 Mar 18 03:37 default.prop >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 dev >>> > > -rw-r----- 1 jvidal jvidal 857 Mar 18 03:37 >> fstab.freescale >>> > > -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 03:37 init >>> > > -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 03:37 >> init.freescale.rc >>> > > -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 03:37 >> init.goldfish.rc >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 proc >>> > > drwxr-x--- 2 jvidal jvidal 4096 Mar 18 03:37 sbin >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 sys >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 system >>> > > -rw-r--r-- 1 jvidal jvidal 272 Mar 18 03:37 >>> ueventd.goldfish.rc >>> > > -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 03:37 ueventd.rc >>> > > >>> > > >>> > > I should to edit gonk-misc/Android.mk ? >>> > >>> > Actually you shouldn't have to edit any files, except those in >>> > device/<your_device>. For the builds I have on my hard disk, >>> b2g.mk <http://b2g.mk> >>> > <http://b2g.mk> is >>> > included by an .mk file under build/target/product/, like >>> > >>> > find . -name "*.mk" -type f | xargs grep -n b2g\.mk >>> > ./build/target/product/full_base.mk:56:$(call >> inherit-product, >>> > gonk-misc/b2g.mk <http://b2g.mk> <http://b2g.mk>) >>> > >>> > You should check if such a line is present and if the >>> respective file is >>> > included from the *.mk files in your device directory; either >>> directly >>> > or via other files. >>> > >>> > Best regards >>> > Thomas >>> > >>> > >>> > > >>> > > Regards. >>> > > >>> > > >>> > > jvidalsm >>> > > >>> > > >>> > > 2014-03-18 3:48 GMT-05:00 Thomas Zimmermann >>> > <[email protected] <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>> >>> > > <mailto:[email protected] >>> <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>>>>: >>> > > >>> > > > the dependecies listed in gonk-misc/Android.mk are >>> included. >>> > > >>> > > s/Android.mk/b2g.mk <http://b2g.mk> <http://b2g.mk> >>> <http://b2g.mk> >>> > > >>> > > >>> > > > >>> > > > Best regards >>> > > > Thomas >>> > > > >>> > > > On 18.03.2014 08:39, Jose Vidal wrote: >>> > > >> Hi everyone, >>> > > >> >>> > > >> I have builded the image files: >>> > > >> >>> > > >> boot.img >>> > > >> system.img >>> > > >> userdata.img >>> > > >> recovery.img >>> > > >> >>> > > >> I'm using unmkbootimg to extract the files from >> boot.img. >>> > > >> When I extract the files from my boot.img I don't >>> have the same >>> > > files like boot.img from Hamachi. >>> > > >> >>> > > >> My device is a fsl/arm2_6dq and the files inside the >>> boot.img >>> > > (after the build) are: >>> > > >> >>> > > >> data >>> > > >> dev >>> > > >> proc >>> > > >> sbin >>> > > >> sys >>> > > >> system >>> > > >> init >>> > > >> init.freescale.rc >>> > > >> ueventd.goldfish.rc >>> > > >> default.prop >>> > > >> fstab.freescale >>> > > >> init.goldfish.rc >>> > > >> ueventd.rc >>> > > >> >>> > > >> The files inside the boot.img from Hamachi device >>> (downloaded >>> > > from http://elsimpicuitico.wordpress.com/firefoxos/) >> are: >>> > > >> >>> > > >> boot.ver >>> > > >> dev >>> > > >> proc >>> > > >> sbin >>> > > >> sys >>> > > >> system >>> > > >> init.qcom.class_core.sh >>> <http://init.qcom.class_core.sh> <http://init.qcom.class_core.sh> >>> > <http://init.qcom.class_core.sh> >>> > > >> init.qcom.syspart_fixup.sh >>> <http://init.qcom.syspart_fixup.sh> >>> > <http://init.qcom.syspart_fixup.sh> >>> <http://init.qcom.syspart_fixup.sh> >>> > > >> ueventd.goldfish.rc >>> > > >> charger >>> > > >> init >>> > > >> init.qcom.class_main.sh >>> <http://init.qcom.class_main.sh> <http://init.qcom.class_main.sh> >>> > <http://init.qcom.class_main.sh> >>> > > >> init.qcom.usb.rc >>> > > >> res >>> > > >> ueventd.rc >>> > > >> custpack >>> > > >> init.b2g.rc >>> > > >> init.qcom.early_boot.sh >>> <http://init.qcom.early_boot.sh> <http://init.qcom.early_boot.sh> >>> > <http://init.qcom.early_boot.sh> >>> > > >> init.qcom.usb.sh <http://init.qcom.usb.sh> >>> <http://init.qcom.usb.sh> >>> > <http://init.qcom.usb.sh> >>> > > >> data >>> > > >> init.goldfish.rc >>> > > >> init.qcom.rc >>> > > >> init.rc >>> > > >> default.prop >>> > > >> init.jrd.rc >>> > > >> init.qcom.sh <http://init.qcom.sh> >>> <http://init.qcom.sh> <http://init.qcom.sh> >>> > > >> init.target.rc >>> > > >> >>> > > >> >>> > > >> How I can make to get the init.b2g.rc, init.rc inside >> the >>> > boot.img ? >>> > > >> >>> > > >> I hope for your help. >>> > > >> >>> > > >> Thanks in advance. >>> > > >> >>> > > >> >>> > > >> Best regards >>> > > >> >>> > > >> jvidalsm >>> > > >> _______________________________________________ >>> > > >> dev-b2g mailing list >>> > > >> [email protected] >>> <mailto:[email protected]> >>> > <mailto:[email protected] >>> <mailto:[email protected]>> >>> <mailto:[email protected] <mailto:[email protected]> >>> > <mailto:[email protected] >>> <mailto:[email protected]>>> >>> > > >> https://lists.mozilla.org/listinfo/dev-b2g >>> > > >> >>> > > > >>> > > > _______________________________________________ >>> > > > dev-b2g mailing list >>> > > > [email protected] >>> <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>> >>> > <mailto:[email protected] >>> <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>>> >>> > > > https://lists.mozilla.org/listinfo/dev-b2g >>> > > > >>> > > >>> > > >>> > > >>> > > >>> > > -- >>> > > Jose Vidal Noblecilla >>> > > Ingeniero Electrónico >>> > > UNMSM >>> > > Lima-Perú >>> > > Cel:994 682 455 >>> > >>> > >>> > >>> > >>> > -- >>> > Jose Vidal Noblecilla >>> > Ingeniero Electrónico >>> > UNMSM >>> > Lima-Perú >>> > Cel:994 682 455 >>> >>> >> >> > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
