DIY的8.1EMMC固件无法开机，卡在mmc初始化位置

hiking · February 8, 2019, 11:13am

emmc固件下载完成后，Uboot正常，LED灯亮正常，HDMI初始化正常但是没有输出，显示器布显示，Debug卡在这个位置：

[    1.657817] usb usb5:  strings: Mfr=3, Product=2, Serisb5: Manufacturer: Linux 4.4.126etected
[    1.660330] ohci-platform fe3a0000.usb: Generic Plat[    1.715519] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    1.715640] usbsb6: New USB device strings: Mfr[    1.720061] dwmmc_rockchip fe
[    1.720436] dwmmc_rockchip fe310000.dwmmc: DW MMC controlle 'clock-freq-min-max' property w[    1.721423] dwmmc_rockchip fe[    1.734431] m)
[    1.747851] dwmmc_rockchip fe310000.dwmmc: 1 slots initialized
[    1.749044] rt5640 1-001c: rt5640 have no aux_det_adc_valu[    1.753277] asoc-simple-card spdif-sound: dit-hifi <-> ff870000.spdif mapping k
[    1.755671] rk-hdmi-dp-sound hdmi-dp-sound: control 3:0:0:ELD:0 is already present
[    1.755716] hdmi-2s mapping ok
[    1.756861] hdcodec.10.auto: ASoC: Failed to cvalue defined
[    1.761368] rk808-rtc rk808-rtc: setting system clock to 2013[    1.771094] mmc_host mmc2: Bus speed (slot 0) = 300000Hz (slot req 300000Hz)
u�
[    1.810959] mmc_host mmc2: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ v = 0)

2019年第一坑

leung · February 12, 2019, 10:03am

烧写官方固件试试

hiking · February 12, 2019, 1:05pm

烧写官方的正常启动。

hiking · February 12, 2019, 1:53pm

本帖最后由 hiking 于 2019-2-13 01:22 编辑

按官方教程文档http://wiki.t-firefly.com/zh_CN/ … mpile_android8.html
自动编译的，EMMC卡死；
手动编译，第一步编译内核找不到rk3399-roc-pc.dts文件;
这里下载：https://gitlab.com/TeeFirefly/fi … p/rk3399-roc-pc.dts
并且注释981~985行，否则编译报错。
第二步编译u-boot奇迹般的竟然正常了；
第三步编译android 出现下面的错误：

king@MacBookPro-ubuntu:/media/king/Android/roc-rk3399-cc$ lunch roc_rk3399_pc_box-userdebug
build/core/product_config.mk:227: *** Can not locate config makefile for product "roc_rk3399_pc_box"。 停止。
//lunch 看看根本没有这个选项
king@MacBookPro-ubuntu:/media/king/Android/roc-rk3399-cc$ lunch

You're building on Linux

Lunch menu... pick a combo:
     1. aosp_arm-eng
     2. aosp_arm64-eng
     3. aosp_mips-eng
     4. aosp_mips64-eng
     5. aosp_x86-eng
     6. aosp_x86_64-eng
     7. rk3399_firefly_mid-userdebug
     8. rk3399_firefly_mid
     9. rk3399_firefly_edp_mid-userdebug
     10. rk3399_firefly_edp_mid
     11. rk3399_firefly_mipi_mid-userdebug
     12. rk3399_firefly_mipi_mid
     13. rk3399_firefly_aio_mid-userdebug
     14. rk3399_firefly_aio_mid
     15. rk3399_firefly_aio_lvds_mid-userdebug
     16. rk3399_firefly_aio_lvds_mid

Which would you like? [aosp_arm-eng]

只好选7，继续编译；
总算也编译通过了;打包也正常了
Firefly-RK3399_Android8.1.0_HDMI_190212.img
文件大小1.4G左右，和官方的解压出来3.8G相差不少。
不知道是不是 lunch roc_rk3399_pc_box-userdebug 这个步骤出错了，目前手动编译的也是卡死在emmc那里；

//////////////
重新同步源码，好像之前同步没有成功；
修改仓库地址：
git remote set-url gitlab https://gitlab.com/TeeFirefly/firenow-oreo-rk3399.git

否则按教程同步源码报如下错:
Permission denied (publickey).
fatal: Could not read from remote repository.

leung · February 13, 2019, 1:33am

hiking 发表于 2019-2-12 21:53
按官方教程文档http://wiki.t-firefly.com/zh_CN/ … mpile_android8.html
自动编译的，EMMC卡死；
手动 …

你还是先同步更新一下代码，要lunch对应的product

hiking · February 13, 2019, 7:37am

本帖最后由 hiking 于 2019-2-13 16:08 编辑

是源码同步的问题，已经编译好了，谢谢；EMMC可以启动了，但是进入系统后点击设置–>system报错
logcat 如下:

01-18 08:56:03.319   439   450 E ActivityManager: getPackageFerformanceMode--ComponentInfo{com.android.settings/com.android.settings.Sets
01-18 08:56:03.334   439   451 E ActivityManager: getPackageFerformanceMode--ComponentInfo{com.android.settings/com.android.settings.Sets
01-18 08:56:03.342   439   453 E memtrack: Couldn't load memtrack module
01-18 08:56:03.421  1458  1458 E AndroidRuntime: FATAL EXCEPTION: main
01-18 08:56:03.421  1458  1458 E AndroidRuntime: Process: com.android.settings, PID: 1458
01-18 08:56:03.421  1458  1458 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settingsd
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2778)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread.-wrap11(Unknown Source:0)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:164)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6494)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
01-18 08:56:03.421  1458  1458 E AndroidRuntime: Caused by: java.lang.RuntimeException: Only one Looper may be created per thread
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.os.Looper.prepare(Looper.java:95)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.os.Looper.prepare(Looper.java:90)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.system.ConnectToPcPreferenceController.<init>(ConnectToP)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.system.SystemDashboardFragment.buildPreferenceController)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.system.SystemDashboardFragment.getPreferenceControllers()
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.dashboard.DashboardFragment.onAttach(DashboardFragment.j)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1223)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2407)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2186)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentM)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2043)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.FragmentManagerImpl.executePendingTransactions(FragmentManager.ja)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.SettingsActivity.switchToFragment(SettingsActivity.java:)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.SettingsActivity.launchSettingFragment(SettingsActivity.)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:322)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7036)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7027)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1214)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2731)
01-18 08:56:03.421  1458  1458 E AndroidRuntime:        ... 9 more
01-18 08:56:03.927   439   454 E ActivityManager: getPackageFerformanceMode--ComponentInfo{com.android.launcher3/com.android.launcher3.L3
01-18 08:57:00.006   439   453 E memtrack: Couldn't load memtrack module

麻烦指导一下，谢谢

hiking · February 13, 2019, 8:02am

leung先森发表于 2019-2-13 09:33
你还是先同步更新一下代码，要lunch对应的product

点击设置-系统报错；
设置闪退了，麻烦帮我看看吧，谢谢；

leung · February 13, 2019, 10:00am

hiking 发表于 2019-2-13 16:02
点击设置-系统报错；
设置闪退了，麻烦帮我看看吧，谢谢；

再同步更新一次代码，最新提交已经修复这个问题