在kernel修改的代码烧录以后没有起作用

flowerking

我在kernel\drivers\video\rockchip\rk_fb.c中修改的代码，重新编译烧录以后，log显示修改没有生效。
然后我重新编译了uboot，把uboot.img和RK3128MiniLoaderAll_V2.25.bin也重新烧录了，但是kernel的修改还是没有生效，请教到底是什么原因？如何解决？谢谢！
例如，我在rk32_mipi_dsi_probe()函数的倒数第二句，dev_info(&pdev->dev, "rk mipi_dsi probe success!, flower\n");增加了flower的字样，但是运行的时候，日志里还是显示rk mipi_dsi probe success!，没有我增加的东西

leung先森

把带内核的boot.img给替换掉，建议重新编译不要加ota参数

flowerking

leung先森 发表于 2017-7-3 16:19
把带内核的boot.img给替换掉，建议重新编译不要加ota参数

重新编译什么不要加ota参数？
我没有加ota参数
我都是按照你们网页上的指示来做的
cd SDK/u-boot
make rk3128_defconfig
make
编译内核是：
make fireprime_defconfig
make -j8 rk3128-fireprime.img

leung先森

flowerking 发表于 2017-7-3 16:28
重新编译什么不要加ota参数？
我没有加ota参数
我都是按照你们网页上的指示来做的

你编译了内核那部分，没有编译上层

flowerking

leung先森 发表于 2017-7-3 16:36
你编译了内核那部分，没有编译上层

现在编译和下载没问题了，但是初始化的过程中，mali400 GPU没有起来，感觉根本就没有去初始化GPU，所以我的MiPi凭一直没有亮起来，下面是log，请帮忙分析一下是什么原因？
[   24.518290] ======== PULL WL_REG_ON LOW! ========
[   24.518304] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   24.521934] Cam_Powerdowm
[   24.536837] init: /dev/hw_random not found
[   24.536961] keychord: using input dev 20050030.pwm for fevent
[   24.536983] keychord: using input dev rk29-keypad for fevent
[   24.549375] init: /dev/hw_random not found
[   24.551603] fs_mgr: Running /sbin/resize2fs on /dev/block/platform/1021c000.rksdmmc/by-name/system
[   24.556285] resize2fs: resize2fs 1.42.9 (28-Dec-2013)resize2fs: /sbin/resize2fs: Bad magic number in super-block while trying to open /dev/block/platform/1021c000.rksdmmc/by-name/systemresize2fs: Couldn't find valid filesystem superblock.resize2fs: resize2fs terminated by exit(1)
[   24.559632] EXT4-fs (mmcblk0p12): VFS: Can't find ext4 filesystem
[   24.559849] fs_mgr: __mount(source=/dev/block/platform/1021c000.rksdmmc/by-name/system,target=/system,type=ext4)=-1
[   24.560609] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/1021c000.rksdmmc/by-name/system at /system options: noauto_da_alloc error: Invalid argument
[   24.575427] EXT4-fs (mmcblk0p8): recovery complete
[   24.576033] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
[   24.576206] fs_mgr: __mount(source=/dev/block/platform/1021c000.rksdmmc/by-name/cache,target=/cache,type=ext4)=0
[   24.581269] EXT4-fs (mmcblk0p10): recovery complete
[   24.581303] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
[   24.581448] fs_mgr: __mount(source=/dev/block/platform/1021c000.rksdmmc/by-name/metadata,target=/metadata,type=ext4)=0
[   24.590835] ret: 0
[   24.591740] EXT4-fs (mmcblk0p9): recovery complete
[   24.592131] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
[   24.592297] fs_mgr: __mount(source=/dev/block/platform/1021c000.rksdmmc/by-name/userdata,target=/data,type=ext4)=0
[   24.592384] init: fs_mgr_mount_all returned an error
[   24.592772] init: fs_mgr_mount_all returned unexpected error 255
[   24.595255] Unable to find swap-space signature
[   24.595361] fs_mgr: swapon failed for /dev/block/zram0
[   24.604775] Cannot change disksize for initialized device
[   24.606463] Unable to find swap-space signature
[   24.606572] fs_mgr: swapon failed for /dev/block/zram0
[   24.620348] [WLAN_RFKILL]: wifi shut off power.
[   24.620364] soc-camera-pdrv gc0329_front_5: Probing gc0329_front_5
[   24.620392] [WLAN_RFKILL]: rockchip_wifi_ref_voltage: 0
[   24.620407] [WLAN_RFKILL]: rockchip_wifi_ref_voltage: wifi io reference voltage control is disabled.
[   24.620524] dhd_module_init: Exit err=0
[   24.642856] EXT4-fs (mmcblk0p9): Unrecognized mount option "background_gc=on" or missing value
[   24.650105] init: cannot find '/system/bin/logd', disabling 'logd'
[   24.650819] init: cannot find '/system/bin/lmkd', disabling 'lmkd'
[   24.650886] init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
[   24.650947] init: cannot find '/system/bin/vold', disabling 'vold'
[   24.650996] init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
[   24.657365] init: property 'ro.serialno' doesn't exist while expanding '${ro.serialno}'
[   24.657406] init: cannot expand '${ro.serialno}' while writing to '/sys/class/android_usb/android0/iSerial'
[   24.657707] init: property 'ro.product.manufacturer' doesn't exist while expanding '${ro.product.manufacturer}'
[   24.657742] init: cannot expand '${ro.product.manufacturer}' while [u[   24.65893[[[   24.662499] bat_cap: oldcap path is /[[   [   24.666382] init: cannot find '/system[[ [   24.672725] read descriptors
[   24.672758] read strings
[   24.672[   24.689287] ret: 0
[   24.816163] rk818-battery rk818-battery: changed: dsoc=0, rsoc=0
[   24.827403] rk818-battery rk818-battery: set charge to digital termination mode
[   24.836796] Cam_Powerdowm
[   24.837335] min_w = 640,min_h = 480 ,max_real_w = 640,max_real_h = 480,max_w = 640,max_h =480
[   24.857455] gc0329_front_5(rk_cam_sensor:169): write reg(0xfc, val:0x16) failed, try to write again!
[   24.858413] gc0329_front_5(rk_cam_sensor:169): write reg(0xfc, val:0x16) failed, try to write again!
[   24.859362] gc0329_front_5(rk_cam_sensor:169): write reg(0xfc, val:0x16) failed, try to write again!
[   24.887236] gc0329_front_5(rk_cam_sensor:335): read reg(0x0 val:0x0) failed, try to read again!
[   24.887261] gc0329(917): gc0329 read chip id high byte failed
[   24.887261]
[   24.887278] gc0329(924): error: gc0329 mismatched   pid = 0x0
[   24.887278]
[   24.887295] gc0329_front_5(rk_cam_sensor:718): error: mismatched   pid = 0x0
[   24.887295]
[   24.994242] Cam_Powerdowm
[   25.063138] ret: 0
[   25.092657] soc-camera-pdrv gc2035_back_6: Probing gc2035_back_6
[   25.181207] ret: 0
[   25.328793] Cam_Powerdowm
[   25.328809] rk_cam_io(1128):SENSOR_PWRSEQ_PWRDN failed
[   25.328879] soc-camera-pdrv gc2035_back_6: Cannot get I2C adapter #2. No driver?
[   25.437015] Cam_Powerdowm
[   25.437031] rk_cam_io(1128):SENSOR_PWRSEQ_PWRDN failed
[   25.437043] rk_cam_io(1117):SENSOR_PWRSEQ_HWRST failed
[   25.505919] ret: 0
[   25.535452] soc-camera-pdrv gc0308_front_7: Probing gc0308_front_7
[   25.623993] ret: 0
[   25.647086] binder: 128:128 transaction failed 29189, size 0-0
[   25.771594] Cam_Powerdowm
[   25.771672] soc-camera-pdrv gc0308_front_7: Cannot get I2C adapter #2. No driver?
[   25.879829] Cam_Powerdowm
[   25.948714] ret: 0
[   26.631225] binder: 128:128 transaction failed 29189, size 0-0
[   27.615367] binder: 128:128 transaction failed 29189, size 0-0
[   28.599508] binder: 128:128 transaction failed 29189, size 0-0
[   29.583644] binder: 128:128 transaction failed 29189, size 0-0
[   30.567789] binder: 128:128 transaction failed 29189, size 0-0
[   31.551941] binder: 128:128 transaction failed 29189, size 0-0
[   32.536091] binder: 128:128 transaction failed 29189, size 0-0
[   33.520244] binder: 128:128 transaction failed 29189, size 0-0
[   34.504397] binder: 128:128 transaction failed 29189, size 0-0

leung先森

flowerking 发表于 2017-7-4 09:11
现在编译和下载没问题了，但是初始化的过程中，mali400 GPU没有起来，感觉根本就没有去初始化GPU，所以我 ...

你这个系统都没跑起来，上层似乎有缺失，或者配合内核配置的上层初始化失败了。
建议回退到官方提交然后重新编译，排查自己添加的修改

flowerking

leung先森 发表于 2017-7-4 09:53
你这个系统都没跑起来，上层似乎有缺失，或者配合内核配置的上层初始化失败了。
建议回退到官方提交然后 ...

我昨天退回到官方的最新版本，然后只修改了两个文件，新增加了一个文件，就是为了接入MiPi屏，其他的什么都没改动。烧录以后就这样了。我新建了一个目录，然后把fireprime_android5.1_git_20170624.7z（这个是你们官网的最新代码）解压在此目录，然后git reset --hard，然后修改了fireprime_defconfig和rk3128-fireprime.dts，增加了一个自己的Mipi初始化文件lcd-wk-mipi.dtsi，其他什么都没修改，然后先编译u-boot，再编译kernel，最后编译android，都是按照你们的官网指示来做的，最后烧录了全部的固件，结果就这样了
fireprime_defconfig的修改是在最后增加了
CONFIG_LCD_MIPI=y
CONFIG_MIPI_DSI=y
CONFIG_RK32_MIPI_DSI=y
修改的rk3128-fireprime.dts和lcd-wk-mipi.dtsi见附件

leung先森

flowerking 发表于 2017-7-4 10:02
我昨天退回到官方的最新版本，然后只修改了两个文件，新增加了一个文件，就是为了接入MiPi屏，其他的什么 ...

先烧官方的固件，然后单独修改内核，烧写内核resource这2个
背光要确认使能是否提高了，mipi供电。
fb不能关闭，否则即使使能上拉了也不会有显示

flowerking

leung先森 发表于 2017-7-4 10:20
先烧官方的固件，然后单独修改内核，烧写内核resource这2个
背光要确认使能是否提高了，mipi供电。
fb ...

我按照你所说的，下载了你们的最新固件：FirePrime_Android5.1_201704051109.img，然后用开发工具升级了，然后系统没有出现错误了。这时候我在ubuntu下新建了目录，把fireprime_android5.1_git_20170624.7z解压到此目录，然后git reset --hard，完了以后，我把我的那三个文件拷贝到对应的目录里面，然后make fireprime_defconfig，make -j8 rk3128-fireprime.img，编译成功以后，我只烧录kernel.img和resource.img，烧录成功重启以后就又复现了昨天的问题，所有的修改无效，感觉是kernel.img没有烧录一样？请问怎样才能让kernel.img生效？
[    0.853534] rk_battery_charger_detect_cb , battery_charger_detect 1
[    0.867229] fb disp policy is box
[    0.867340] rk-fb rockchip-fb: rk fb ion client create success!
[    0.867367] rk-fb rockchip-fb: rockchip framebuffer driver probe
[    0.867858] rk-screen rk_screen.9: rockchip screen probe success
[    0.868426] rk31xx-lvds 20038000.lvds: screen is not lvds/rgb!
[    0.868470] rk31xx-lvds: probe of 20038000.lvds failed with error -22
[    0.869527] rk312x-lcdc lcdc0: can't find power_ctr node for lcdc0
[    0.869556] rk_fb_trsm_ops_get:un supported transmitter:6!
[    0.870128] graphics fb0: rockchip framebuffer registerd:fb0
[    0.870923] graphics fb1: rockchip framebuffer registerd:fb1
[    0.871335] graphics fb2: rockchip framebuffer registerd:fb2
[    0.871954] rk312x-lcdc lcdc0: set lcdc0 dclk failed
[    0.871989] rk312x-lcdc lcdc0: lcdc0: dclk:74250000>>fps:60
[    0.872017] rk312x-lcdc lcdc0: wakeup from standby!
[    0.889890] alloc_buffer:ion_phy_addr=0x10000000
看日志，系统还是去检测lvds，但实际上我已经修改.dts文件屏蔽了lvds设备，要求检测mipi

flowerking

leung先森 发表于 2017-7-4 10:20
先烧官方的固件，然后单独修改内核，烧写内核resource这2个
背光要确认使能是否提高了，mipi供电。
fb ...

感觉现在进入了一个死循环里面一样了。请指示一下到底要怎么做才能弄好？谢谢