Firefly开源社区

标题: Firefly-RK3288 跑Ubuntu系统,跑不起来,请指导 [打印本页]

作者: maurice    时间: 2016-1-19 20:06
标题: Firefly-RK3288 跑Ubuntu系统,跑不起来,请指导
以下是我按照wiki网上的方法,在Firefly-RK3288上跑Ubuntu系统,不知道自己哪里做的不对始终没有跑起来。

第一大步
我首先按照这个链接(http://wiki.t-firefly.com/index. ... 88/Build_Ubuntu_rfs)在TF卡中生成一个文件系统:
1、下载linux-boot-miniroot.img和misc.img,将 linux-boot-miniroot.img 写到 recovery 分区,misc.img 写到 misc 分区。板子之前烧录的是自己编译的Android rom,没有问题,正常运行
                烧录完毕板子起来进入miniroot# 进入miniroot的时候打印一下消息
                miniroot# [   12.972207] es8323_create file error
                [   19.820859] *****************vbus detect*******************
2、配置网络,miniroot# udhcpc  成功连接网络。
3、格式化TF卡并挂载到 miniroot 的/mnt 下,我的TF对应的是/dev/mmcblk1p1,mount 时候报错,但是也是mount成功了。
        miniroot# mkfs.ext4 -E nodiscard /dev/mmcblk1p1
        miniroot# mount /dev/mmcblk1p1 /mnt
[  208.689506] EXT3-fs (mmcblk1p1): error: couldn't mount because of unsupported optional features (240)
[  208.701357] EXT2-fs (mmcblk1p1): error: couldn't mount because of unsupported optional features (240)
[  208.720965] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)

4、下载和解压 ubuntu-core 此步骤没有任何问题
miniroot# cd /mnt
miniroot# wget -P /mnt http://cdimage.ubuntu.com/ubuntu ... 4-core-armhf.tar.gz
miniroot# mkdir /mnt/ubuntu
miniroot# tar -xpzf /mnt/ubuntu-core-14.04-core-armhf.tar.gz -C /mnt/ubuntu
5、设置主机名称
miniroot# echo firefly > /mnt/ubuntu/etc/hostname
miniroot# sed -e 's/miniroot/firefly/' < /etc/hosts > /mnt/ubuntu/etc/hosts
6、设置串口控制台,自动以 root 用户登录:
miniroot# sed -e 's/tty1/ttyS2/g' -e '/^exec/c exec /sbin/getty -a root -L 115200 ttyS2 vt100' \
          < /mnt/ubuntu/etc/init/tty1.conf > /mnt/ubuntu/etc/init/ttyS2.conf
7、启动 Ubuntu 我是把/dev/mmcblk1p1挂载到/mnt下了
miniroot# boot /mnt:/ubuntu
8、文件系统起来之后进入root@firefly:~#
9、设置网络
root@firefly:~# echo auto eth0 > /etc/network/interfaces.d/eth0
root@firefly:~# echo iface eth0 inet dhcp >> /etc/network/interfaces.d/eth0
root@firefly:~# ln -fs ../run/resolvconf/resolv.conf /etc/resolv.conf
root@firefly:~# ifup eth0
10、更新软件包
root@firefly:~# apt-get update
root@firefly:~# apt-get dist-upgrade
11、更新完毕之后,重启进入 miniroot,同样还是打印error信息
miniroot# [   12.913413] es8323_create file error
[   19.801318] *****************vbus detect*******************
12、在miniroot中编辑环境变量,加入 ubuntu 的启动参数:我的TF卡对应是/dev/mmcblk1p1。编辑完毕保存退出,并且保存环境变量,重启。
miniroot# editenv
boot=/dev/mmcblk1p1:/ubuntu
init=/sbin/init
autoboot=1

miniroot# saveenv
miniroot# reboot -f
13、重启之后还是进入了miniroot# 而我在miniroot中执行boot /dev/mmcblk1p1:/ubuntu,似乎环境变量没有起作用。
14、为什么环境变量设置了也没有挂载TF卡中的文件系统呢?这个问题先暂放一下。
现在TF卡中已经有做好的根文件系统,从开发板上取下,挂载到电脑上,一会往根文件系统中拷贝内核模块。       
第二大步
我按照这个链接(http://wiki.t-firefly.com/index.php/Firefly-RK3288/Build_kernel)生成boot.img和修改parameter.txt文件。
15、安装开发包 我是64位的Ubuntu,两个都安装了。
sudo apt-get install build-essential lzop libncurses5-dev libssl-dev
# 如果使用的是 64 位的 Ubuntu,还需要安装:
sudo apt-get install libc6:i386
16、安装 mkbootimg 工具 照做
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make && sudo make install
17、获取内核源码和安装交叉编译工具链,我没有用Firefly-RK3288 Android SDK中的kernel源码。单独下载了一份,交叉工具链是从Android SDK中拷贝的。
内核源码下载:
git clone https://bitbucket.org/T-Firefly/firefly-rk3288-kernel.git
18、编译内核映像
export ARCH=arm
export CROSS_COMPILE=/home/maurice/share/arm/arm-eabi-4.6/bin/arm-eabi-
make firefly-rk3288-linux_defconfig
make -j8 firefly-rk3288.img
19、编译内核模块
make modules
mkdir modules_install
make INSTALL_MOD_PATH=./modules_install modules_install
20、将内核模块是需要拷到根文件系统中,这一步我直接把用来做根文件系统的TF挂载到pc机上,挂载到/mnt下,直接拷贝到TF上的/ubuntu中
sudo rsync -av ./modules_install/ /mnt/ubuntu
sudo umount /mnt
将TF卡重新插入到开发板上。
21、创建内存盘 照做
git clone https://github.com/TeeFirefly/initrd.git
make -C initrd
22、创建 boot.img 打包内核和内存盘
mkbootimg --kernel firefly-rk3288-kernel/arch/arm/boot/zImage --ramdisk initrd.img -o boot.img
23、修改 parameter 文件  修改内容如下:
FIRMWARE_VER:5.0.0
MACHINE_MODEL:rk3288
MACHINE_ID:007
MANUFACTURER:RK3288
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3288
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x62008000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
#linux
CMDLINE:console=ttyS2 root=/dev/mmcblk1p1 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00300000@0x00092000(system),0x00008000@0x00392000(metadata),0x00200000@0x0039A000(userdata),0x00020000@0x0059A000(radical_update),-@0x005BA000(user)
24、使用AndroidTool_Release_v2.35烧录boot.img 和parameter.txt
boot.img 烧到boot分区,parameter.txt 烧录到parameter分区中。

25、等系统起来还是进入了miniroot中,我又把misc_zero.img烧录到misc分区,恢复回 boot 分区启动。

26、系统起来之后进入了(initramfs)。

这是为什么?哪里做的不对,请做过的给个指导,非常感谢!
作者: linjc    时间: 2016-1-20 09:47
13.你的文件系统是放在TF卡上的,wiki文档是直接放在板子上,这样会有些区别,你这里相当于在TF卡启动,默认的内核应该还不支持TF卡启动,你可以参考:http://bbs.t-firefly.com/forum.p ... &extra=page%3D1 如果要简单一点,你可以参考 http://wiki.t-firefly.com/index. ... 88/Build_Ubuntu_rfs 把TF卡上的文件系统制作成linuxroot.img 再烧进板子里
20.内核模块已经在boot.img里面,好像不用放到文件系统了吧
23.如果只想跑ubuntu单系统,parameter建议使用SDK下linux单系统的parameter: FFTools/parameter/rk3288-3.10-uboot-linux.parameter.txt
作者: maurice    时间: 2016-1-20 10:49
linjc 发表于 2016-1-20 09:47
13.你的文件系统是放在TF卡上的,wiki文档是直接放在板子上,这样会有些区别,你这里相当于在TF卡启动,默 ...

谢谢您的回复!
我已经生成了linuxroot.img,我是在虚拟机先开发的,但是rockusb device 连接不到虚拟中去,提示连接rockusb device 失败,驱动程序出错,所以我无法使用upgrade_tool和rkflashtool工具烧录。
我不清楚linuxroot.img能不能在Windows下使用AndroidTool_Release_v2.35烧录,应该烧录到那个分区呢?
我见您分析了一个pad版的Ubuntu图,请问你是怎么把他做成一个统一的img的?能否给一个指导文档呢?
这样我就可以用AndroidTool_Release_v2.35烧录了。非常感谢您的指导!
作者: maurice    时间: 2016-1-20 10:57
linjc 发表于 2016-1-20 09:47
13.你的文件系统是放在TF卡上的,wiki文档是直接放在板子上,这样会有些区别,你这里相当于在TF卡启动,默 ...

为什么我的SDK中FFTools下没有这个目录和对应的文件/parameter/rk3288-3.10-uboot-linux.parameter.txt
作者: linjc    时间: 2016-1-20 11:21
maurice 发表于 2016-1-20 10:57
为什么我的SDK中FFTools下没有这个目录和对应的文件/parameter/rk3288-3.10-uboot-linux.parameter.txt

你的SDK没有更新吧?更新到最新试试
作者: maurice    时间: 2016-1-20 11:43
linjc 发表于 2016-1-20 11:21
你的SDK没有更新吧?更新到最新试试

更新了还是没有,不知道怎么回事?
我现在把你的Firefly-RK3288_PAD_B101EW05_Ubuntu14.04_201503031651.img 解包了,把我自己做的linux_rootfs.img放进去试试,看能不能起来,但是打包的时候出现下面的情况,怎么回事啊?
这样写不对吗?img_maker -rk32 loader.img update_new.img release_update_new.img


maurice@maurice-vm:~/share/ubuntu_img$ img_maker -rk32 loader.img update_new.img release_update_new.img
USAGE:
img_maker [chiptype] [loader] [major ver] [minor ver] [subver] [old image] [out image]

Example:
img_maker -rk30 Loader.bin 1 0 23 rawimage.img rkimage.img      RK30 board
img_maker -rk31 Loader.bin 4 0 4 rawimage.img rkimage.img       RK31 board
img_maker -rk3128 Loader.bin 4 0 4 rawimage.img rkimage.img     RK3128 board
img_maker -rk32 Loader.bin 4 4 2 rawimage.img rkimage.img       RK32 board
img_maker -rk3368 Loader.bin 5 0 0 rawimage.img rkimage.img     RK3368 board


Options:
[chiptype]:
        -rk29
        -rk30
        -rk31
        -rk3128
        -rk32
        -rk3368

作者: linjc    时间: 2016-1-20 11:52
maurice 发表于 2016-1-20 10:49
谢谢您的回复!
我已经生成了linuxroot.img,我是在虚拟机先开发的,但是rockusb device 连接不到虚拟中 ...

可以在Windows下使用AndroidTool_Release_v2.35烧录的,具体的分区可以看parameter,可以参考我这个:
你也可以自己手动定义的。

QQ截图20160120115008.png (18.88 KB, 下载次数: 672)

QQ截图20160120115008.png

作者: maurice    时间: 2016-1-20 13:59
linjc 发表于 2016-1-20 11:52
可以在Windows下使用AndroidTool_Release_v2.35烧录的,具体的分区可以看parameter,可以参考我这个:
...

你好,linjc
我按照你说的,使用AndroidTool_Release_v2.35烧录,自己手动定义了分区,按照你的截图来的。然后对应分区的img文件对应自己生成的linux_boot.img、resource.img、还有linux_rootfs.img 烧录之后系统起来又进入(initramfs)了,一下是部分log信息。是我生成linuxroot.img的问题吗?我生成linuxroot大小是1G

DMMC_SHIFT_DEGREE_90         SDMMC_SHIFT_DEGREE_180         SDMMC_SHIFT_DEGREE_INVALID[mmc0]
[    4.890494] mmc0: new HS200 MMC card at address 0001
[    4.890853] mmcblk0: mmc0:0001 AWMB3R 14.5 GiB
[    4.891228]   resource: 0x000400000 -- 0x001400000 (16 MB)
[    4.891238]       boot: 0x001400000 -- 0x002400000 (16 MB)
[    4.891246]       misc: 0x002400000 -- 0x002800000 (4 MB)
[    4.891254]     backup: 0x002800000 -- 0x005c00000 (52 MB)
[    4.891261]  linuxroot: 0x005c00000 -- 0x3a3a00000 (14814 MB)
[    4.892128]  mmcblk0: p1 p2 p3 p4 p5rk_sdmmc: BOOT dw_mci_setup_bus: argue clk_mmc workaround out 800000Hz for init[mmc1]
[    5.000511] mmc1: Skipping voltage switch
[    5.152460] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    5.152480] rk_sdmmc: BOOT dw_mci_setup_bus: argue clk_mmc workaround out normal clock [mmc1]
[    5.168447] rk_sdmmc: BOOT Bus speed=50000000Hz,Bus width=4bits.[mmc1]
[    5.168460] mmc1: new high speed SDHC card at address aaaa
[    5.168792] mmcblk1: mmc1:aaaa SS08G 7.40 GiB
[    5.184042]  mmcblk1: p1
[    5.184403] 1381..dw_mci_set_ios:  no card. [mmc2]
[    5.632242] EHCI: rk_ehci_hcd_enable, disable host controller
[    5.640871] dwc_otg_hcd_enable, enable host controller
[    5.744228] Using Buffer DMA mode
[    5.744233] Periodic Transfer Interrupt Enhancement - disabled
[    5.744236] Multiprocessor Interrupt Enhancement - disabled
[    5.744240] OTG VER PARAM: 0, OTG VER FLAG: 0
[    5.744244] ^^^^^^^^^^^^^^^^^^Host Mode
[    5.787380] Init: Power Port (0)
[    5.816827] iep dpi mode inactivity
[    6.043540] ES8323 2-0010: ASoC: no dapm match for LINPUT1 --> NULL --> Left Line Mux
[    6.043547] ES8323 2-0010: ASoC: Failed to add route LINPUT1 -> NULL -> Left Line Mux
[    6.043553] ES8323 2-0010: ASoC: no dapm match for LINPUT2 --> NULL --> Left Line Mux
[    6.043558] ES8323 2-0010: ASoC: Failed to add route LINPUT2 -> NULL -> Left Line Mux
[    6.043565] ES8323 2-0010: ASoC: no dapm match for Left PGA Mux --> NULL --> Left Line Mux
[    6.043570] ES8323 2-0010: ASoC: Failed to add route Left PGA Mux -> NULL -> Left Line Mux
[    6.043576] ES8323 2-0010: ASoC: no dapm match for RINPUT1 --> NULL --> Right Line Mux
[    6.043580] ES8323 2-0010: ASoC: Failed to add route RINPUT1 -> NULL -> Right Line Mux
[    6.043586] ES8323 2-0010: ASoC: no dapm match for RINPUT2 --> NULL --> Right Line Mux
[    6.043591] ES8323 2-0010: ASoC: Failed to add route RINPUT2 -> NULL -> Right Line Mux
[    6.043596] ES8323 2-0010: ASoC: no dapm match for Right PGA Mux --> NULL --> Right Line Mux
[    6.043601] ES8323 2-0010: ASoC: Failed to add route Right PGA Mux -> NULL -> Right Line Mux
[    6.043607] ES8323 2-0010: ASoC: no dapm match for LINPUT1 --> LAMP --> Left PGA Mux
[    6.043612] ES8323 2-0010: ASoC: Failed to add route LINPUT1 -> LAMP -> Left PGA Mux
[    6.043618] ES8323 2-0010: ASoC: no dapm match for LINPUT2 --> LAMP --> Left PGA Mux
[    6.043622] ES8323 2-0010: ASoC: Failed to add route LINPUT2 -> LAMP -> Left PGA Mux
[    6.043628] ES8323 2-0010: ASoC: no dapm match for Differential Mux --> LAMP --> Left PGA Mux
[    6.043633] ES8323 2-0010: ASoC: Failed to add route Differential Mux -> LAMP -> Left PGA Mux
[    6.043638] ES8323 2-0010: ASoC: no dapm match for RINPUT1 --> RAMP --> Right PGA Mux
[    6.043642] ES8323 2-0010: ASoC: Failed to add route RINPUT1 -> RAMP -> Right PGA Mux
[    6.043648] ES8323 2-0010: ASoC: no dapm match for RINPUT2 --> RAMP --> Right PGA Mux
[    6.043652] ES8323 2-0010: ASoC: Failed to add route RINPUT2 -> RAMP -> Right PGA Mux
[    6.043658] ES8323 2-0010: ASoC: no dapm match for Differential Mux --> RAMP --> Right PGA Mux
[    6.043662] ES8323 2-0010: ASoC: Failed to add route Differential Mux -> RAMP -> Right PGA Mux
[    6.043669] ES8323 2-0010: ASoC: no dapm match for LINPUT1 --> LAMP --> Differential Mux
[    6.043674] ES8323 2-0010: ASoC: Failed to add route LINPUT1 -> LAMP -> Differential Mux
[    6.043679] ES8323 2-0010: ASoC: no dapm match for RINPUT1 --> RAMP --> Differential Mux
[    6.043683] ES8323 2-0010: ASoC: Failed to add route RINPUT1 -> RAMP -> Differential Mux
[    6.043689] ES8323 2-0010: ASoC: no dapm match for LINPUT2 --> LAMP --> Differential Mux
[    6.043693] ES8323 2-0010: ASoC: Failed to add route LINPUT2 -> LAMP -> Differential Mux
[    6.043699] ES8323 2-0010: ASoC: no dapm match for RINPUT2 --> RAMP --> Differential Mux
[    6.043703] ES8323 2-0010: ASoC: Failed to add route RINPUT2 -> RAMP -> Differential Mux
[    6.043724] ES8323 2-0010: ASoC: no dapm match for LINPUT1 --> LAMP --> Left Line Mux
[    6.043728] ES8323 2-0010: ASoC: Failed to add route LINPUT1 -> LAMP -> Left Line Mux
[    6.043733] ES8323 2-0010: ASoC: no dapm match for LINPUT2 --> LAMP --> Left Line Mux
[    6.043738] ES8323 2-0010: ASoC: Failed to add route LINPUT2 -> LAMP -> Left Line Mux
[    6.043743] ES8323 2-0010: ASoC: no dapm match for Left PGA Mux --> LAMP --> Left Line Mux
[    6.043747] ES8323 2-0010: ASoC: Failed to add route Left PGA Mux -> LAMP -> Left Line Mux
[    6.043753] ES8323 2-0010: ASoC: no dapm match for RINPUT1 --> RAMP --> Right Line Mux
[    6.043758] ES8323 2-0010: ASoC: Failed to add route RINPUT1 -> RAMP -> Right Line Mux
[    6.043764] ES8323 2-0010: ASoC: no dapm match for RINPUT2 --> RAMP --> Right Line Mux
[    6.043768] ES8323 2-0010: ASoC: Failed to add route RINPUT2 -> RAMP -> Right Line Mux
[    6.043774] ES8323 2-0010: ASoC: no dapm match for Right PGA Mux --> RAMP --> Right Line Mux
[    6.043778] ES8323 2-0010: ASoC: Failed to add route Right PGA Mux -> RAMP -> Right Line Mux
[    6.043944] ES8323 2-0010: ASoC: mux Right Line Mux has no paths
[    6.043952] ES8323 2-0010: ASoC: mux Left Line Mux has no paths
[    6.043960] ES8323 2-0010: ASoC: mux Right PGA Mux has no paths
[    6.043968] ES8323 2-0010: ASoC: mux Left PGA Mux has no paths
[    6.043991] ES8323 2-0010: ASoC: mux Differential Mux has no paths
[    6.046862] Enter::rk29_es8323_init----135
[    6.096906] rockchip-es8323 rockchip-es8323.28:  ES8323 HiFi <-> rockchip-i2s.0 mapping ok
[    6.097436] u32 classifier
[    6.097441]     Actions configured
[    6.097449] Netfilter messages via NETLINK v0.30.
[    6.097498] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    6.097775] ctnetlink v0.93: registering with nfnetlink.
[    6.097836] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[    6.097839] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[    6.098055] xt_time: kernel timezone is -0000
[    6.098217] ip_tables: (C) 2000-2006 Netfilter Core Team
[    6.098321] arp_tables: (C) 2002 David S. Miller
[    6.098352] TCP: cubic registered
[    6.098355] Initializing XFRM netlink socket
[    6.098539] NET: Registered protocol family 10
[    6.098969] mip6: Mobile IPv6
[    6.098989] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    6.099087] sit: IPv6 over IPv4 tunneling driver
[    6.099368] NET: Registered protocol family 17
[    6.099386] NET: Registered protocol family 15
[    6.099429] Bridge firewalling registered
[    6.099436] Ebtables v2.0 registered
[    6.099578] Bluetooth: RFCOMM TTY layer initialized
[    6.099597] Bluetooth: RFCOMM socket layer initialized
[    6.099601] Bluetooth: RFCOMM ver 1.11
[    6.099605] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.099608] Bluetooth: BNEP filters: protocol multicast
[    6.099615] Bluetooth: BNEP socket layer initialized
[    6.099619] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    6.099626] Bluetooth: HIDP socket layer initialized
[    6.099652] l2tp_core: L2TP core driver, V2.0
[    6.099661] l2tp_ppp: PPPoL2TP kernel driver, V2.0
[    6.099665] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    6.099879] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    6.099889] wlan_platdata_parse_dt: wifi_chip_type = bcmwifi
[    6.099894] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    6.099899] [WLAN_RFKILL]: wlan_platdata_parse_dt: disable wifi io reference voltage control.
[    6.099903] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    6.099919] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,poweren_gpio = 156, flags = 0.
[    6.099929] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,host_wake_irq = 158, flags = 0.
[    6.099933] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    6.099956] [WLAN_RFKILL]: rockchip_wifi_voltage_select: wifi & sdio reference voltage: 1.8V
[    6.099995] [WLAN_RFKILL]: Exit rfkill_wlan_probe
[    6.100035] [BT_RFKILL]: Enter rfkill_rk_init
[    6.100154] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 147.
[    6.100164] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,power_gpio = 155.
[    6.100171] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 157.
[    6.100178] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 154.
[    6.100185] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 159.
[    6.100227] [BT_RFKILL]: Request irq for bt wakeup host
[    6.100317] [BT_RFKILL]: ** disable irq
[    6.100392] [BT_RFKILL]: ap6335 device registered.
[    6.151401] Indeed it is in host mode hprt0 = 00021501
[    6.328509] usb 3-1: new high-speed USB device number 2 using usb20_host
[    6.343789] Indeed it is in host mode hprt0 = 00001101
[    6.630504] usb 3-1: New USB device found, idVendor=1a40, idProduct=0101
[    6.630510] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.630516] usb 3-1: Product: USB 2.0 Hub [MTT]
[    6.645706] hub 3-1:1.0: USB hub found
[    6.660900] hub 3-1:1.0: 4 ports detected
[    6.741799] ******** Show Sink Info ********
[    6.741803] Max tmds clk is 0
[    6.741805] Support video mode:
[    6.741808]         1920x1080p@60Hz
[    6.741810]         1920x1080p@50Hz
[    6.741813]         1920x1080p@30Hz
[    6.741815]         1280x720p@60Hz
[    6.741817]         1280x720p@50Hz
[    6.741820]         720x576p@50Hz
[    6.741822]         720x480p@60Hz
[    6.741824] Support video color mode:
[    6.741826]         RGB
[    6.741829]         YCbCr422
[    6.741832]         YCbCr444
[    6.741834] Support video color depth:
[    6.741836]         24bit
[    6.741838] Support audio type:
[    6.741840]         LPCM
[    6.741843] Support max audio channel is 2
[    6.741845] Support audio sample rate:
[    6.741847]         32000
[    6.741850]         44100
[    6.741852]         48000
[    6.741854] Support audio word lenght:
[    6.741856]         16bit
[    6.741857]         20bit
[    6.741859]         24bit
[    6.741861]
[    6.741863] ******** Show Sink Info ********
[    6.741876]
[    6.741876] rk_fb_switch_screen lcdc_id 0 type 6 enable 1
[    6.741885] fb0 win id 1 state 1
[    6.741902] rk3288-lcdc lcdc0: lcdc0: dclk:148500000>>fps:60
[    6.741922] fb1 win id 0 state 0
[    6.741925] fb2 win id 2 state 0
[    6.741928] fb3 win id 3 state 0
[    6.741931] fb4 win id 4 state 0
[    6.741935]
[    6.741935] rk_fb_switch_screen lcdc_id 0 type 6 enable 1 done
[    6.741935]
[    6.741947] pixel clk is 148500000 tmds clk is 148500000 last tmds clk 0 tmdsclk_ratio_change 0
[    6.741990] rk3288-hdmi ff980000.hdmi: [hdmi_dev_config_video] sucess output HDMI.
[    6.752027] rk3288-hdmi ff980000.hdmi: rk3288 hdmi probe sucess.
[    6.758055] VFP support v0.3: implementor 41 architecture 3 part 30 variant d rev 0
[    6.758063] rk3288_init_suspend
[    6.758070] rk3288_suspend_init enter
[    6.758240] rk3288_suspend_init: pm_ctrbits =40017
[    6.758272] gpio_get_dts_info suspend:8
[    6.758276] gpio_get_dts_info resume:8
[    6.758288] rockchip,pmic-suspend_gpios:1007c30 1007c40 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[    6.758300] rockchip,pmic-resume_gpios:2007c32 2007c42 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[    6.758401] clks_gating_suspend_init:clkgt info ok
[    6.758477] Registering SWP/SWPB emulation handler
[    6.758795] ddrfreq: verion 1.2 20140526
[    6.758803] ddrfreq: normal 456MHz video_1080p 0MHz video_4k 456MHz dualview 0MHz idle 0MHz suspend 200MHz reboot 456MHz
[    6.758806] ddrfreq: auto-freq=0
[    6.758809] ddrfreq: auto-freq-table[0] 240MHz
[    6.758812] ddrfreq: auto-freq-table[1] 324MHz
[    6.758815] ddrfreq: auto-freq-table[2] 456MHz
[    6.758818] ddrfreq: auto-freq-table[3] 528MHz
[    6.759279] act_ldo3: operation not allowed
[    6.762949] vga_edid_probe: turn on ldo3 done.
[    6.762997] act_ldo4: operation not allowed
[    6.769978] vga_edid_probe: turn on ldo done.
[    6.770016] act_ldo2: operation not allowed
[    6.770242] vga_edid_probe: turn on ldo2 done.
[    6.770262] act_ldo8: operation not allowed
[    6.770487] vga_edid_probe: turn on ldo done.
[    6.775523] unable to read EDID block.
[    6.810063] unable to read EDID block.
[    6.844607] unable to read EDID block.
[    6.844613] vga-ddc: read and parse edid failed errno:-5.
[    6.844617] vga_edid_probe: success. 10
[    6.844719] firefly_vga_get_enable 180, 0
[    6.844723] firefly_vga_get_status 186
[    6.844727] firefly_vga_set_enable 159 enable:0
[    6.844775] regulator-dummy: disabling
[    6.845057] rockchip-hdmi-spdif rockchip-hdmi-spdif.26: ASoC: CPU DAI (null) not registered
[    6.845076] rockchip_hdmi_spdif_audio_probe() register card failed:-517
[    6.845086] platform rockchip-hdmi-spdif.26: Driver rockchip-hdmi-spdif requests probe deferral
[    6.845163] pcd_pullup, is_on 0
[    6.845193] file system registered
[    6.845724] android_usb gadget: Mass Storage Function, version: 2009/09/11
[    6.845728] android_usb gadget: Number of LUNs=2
[    6.845732]  lun0: LUN: removable file: (no medium)
[    6.845735]  lun1: LUN: removable file: (no medium)
[    6.845867] android_usb gadget: android_usb ready
[    6.845937] sensor_init: Probe name sensors
[    6.845949] sensor-dev.c v1.4 add angle calculation support between two gsensors 2013-09-01
[    6.847754] rtc_hym8563 0-0051: setting system clock to 2011-01-01 15:50:07 UTC (1293897007)
[    6.853148] usbcore: registered new interface driver snd-usb-audio
[    6.853154] ALSA device list:
[    6.853158]   #0: RK_ES8323
[    6.866616] rockchip-hdmi-spdif rockchip-hdmi-spdif.26:  rk-hdmi-spdif-hifi <-> rockchip-spdif mapping ok
[    7.568245] 2, baud is:115200
[    7.573556] Freeing unused kernel memory: 2368K (c0a9c000 - c0cec000)
Loading, please wait...
[    7.625951] udevd[148]: starting version 175
Begin: Loading essential drivers ... FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
ext4
Begin: Running /scripts/local-premount ... FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
done.
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
[    8.762908] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/3.10.0/modules.dep: No such file or directory
/bin/sh: can't access tty; job control turned off
(initramfs) [   11.553769] [otg id chg] last id -1 current id 1
[   11.576673] PortPower off
[   11.583045] rk_battery_charger_detect_cb , battery_charger_detect 6
[   11.692502] Using Buffer DMA mode
[   11.697711] Periodic Transfer Interrupt Enhancement - disabled
[   11.705447] Multiprocessor Interrupt Enhancement - disabled
[   11.712951] OTG VER PARAM: 0, OTG VER FLAG: 0
[   11.719235] ^^^^^^^^^^^^^^^^^Device Mode
[   12.213042] ***************vbus detect*****************
[   12.239362] rk_battery_charger_detect_cb , battery_charger_detect 1
[   12.695236] es8323_create file error

(initramfs)
(initramfs)
(initramfs)
(initramfs)
(initramfs)
作者: linjc    时间: 2016-1-20 14:36
maurice 发表于 2016-1-20 13:59
你好,linjc
我按照你说的,使用AndroidTool_Release_v2.35烧录,自己手动定义了分区,按照你的截图来的 ...

你的parameter是不是这样:
  1. FIRMWARE_VER:4.4.2
  2. MACHINE_MODEL:rk30sdk
  3. MACHINE_ID:007
  4. MANUFACTURER:RK30SDK
  5. MAGIC: 0x5041524B
  6. ATAG: 0x60000800
  7. MACHINE: 3066
  8. CHECK_MASK: 0x80
  9. PWR_HLD: 0,0,A,0,1
  10. #KERNEL_IMG: 0x62008000
  11. #FDT_NAME: rk-kernel.dtb
  12. #RECOVER_KEY: 1,1,0,20,0
  13. CMDLINE:console=tty0 console=ttyS2 earlyprintk root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(resource),0x00008000@0x0000A000(boot),0x00002000@0x00012000(misc),0x0001a000@0x00014000(backup),-@0x0002e000(linuxroot)
复制代码

作者: maurice    时间: 2016-1-20 14:45
linjc 发表于 2016-1-20 14:36
你的parameter是不是这样:

是的,是这样的
作者: linjc    时间: 2016-1-20 15:20
maurice 发表于 2016-1-20 14:45
是的,是这样的

那就看不出问题在哪了,从log看是挂载文件系统的时候出错,你可以换个官方的文件系统试试吧,排除一下,看是问题在哪
作者: maurice    时间: 2016-1-20 15:29
maurice 发表于 2016-1-20 13:59
你好,linjc
我按照你说的,使用AndroidTool_Release_v2.35烧录,自己手动定义了分区,按照你的截图来的 ...

linjc,问题解决了。
我是在固话系统的时候出了问题,cp -a /mnt/ubuntu/ /opt/ 我当时是把ubuntu文件夹拷贝了过去,我重新做了一遍就可以了
作者: maurice    时间: 2016-1-20 15:43
linjc 发表于 2016-1-20 15:20
那就看不出问题在哪了,从log看是挂载文件系统的时候出错,你可以换个官方的文件系统试试吧,排除一下, ...

有一个其他的问题请教你,就是我下载Android Ubuntu桌面,老是有下面的提示,是不是网络上不提供这个包了。但是我安装其他的包是可以的。

root@firefly:~# apt-get install lubuntu-desktop
Reading package lists... Done
Building dependency tree      
Reading state information... Done
E: Unable to locate package lubuntu-desktop
root@firefly:~#
作者: linjc    时间: 2016-1-20 16:48
maurice 发表于 2016-1-20 15:43
有一个其他的问题请教你,就是我下载Android Ubuntu桌面,老是有下面的提示,是不是网络上不提供这个包了 ...

先更新一下软件包吧:
  1. root@ubuntu:~# apt-get update
  2. root@ubuntu:~# apt-get dist-upgrade
复制代码

还不行的话可能是源的问题了
作者: maurice    时间: 2016-1-20 18:36
linjc 发表于 2016-1-20 16:48
先更新一下软件包吧:

还不行的话可能是源的问题了

这两步我都做了,还是不行。
Ubuntu的root用户密码是这样设置吗?
sudo passwd 然后输入密码。
但是我使用ssh无法登陆,其他的用户可以。
root登陆Access denied
作者: linjc    时间: 2016-1-21 09:23
maurice 发表于 2016-1-20 18:36
这两步我都做了,还是不行。
Ubuntu的root用户密码是这样设置吗?
sudo passwd 然后输入密码。

ubuntu好像不能用root登陆的吧
可以先用sudo passwd设置密码,再用su root切换到root用户
作者: maurice    时间: 2016-1-21 14:38
linjc 发表于 2016-1-21 09:23
ubuntu好像不能用root登陆的吧
可以先用sudo passwd设置密码,再用su root切换到root用户

linjc 你好,问你一个交叉编译的问题。
我的主机是Ubuntu 14.04 Desktop 64位的。firefly_rk3288上面跑的lubuntu 是在这个上面制作的,所以lubuntu应该也是64位的吧,现在我想在lubuntu上跑自己的应用程序,我安装32位的arm交叉编译工具可以把应用程序编译过去,但是当在lubuntu上运行时出现:
root@firefly:/home/ubuntu/share# ./net_video_app
-bash: ./net_video_app: No such file or directory
而我使用sdk本身64位的arm交叉编译工具时,应用程序编译不过去,老是提示找不到头文件,这个应该怎么解决啊
maurice@maurice-vm:~/share/firefly_rk3288/linux/video/network/net_video_app$ make
arm-eabi-gcc  -Wall -O2   -Wall -I./include -c source/main.c -o source/main.o
source/main.c:1:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make: *** [source/main.o] Error 1
你的主机开发环境是32位的还是64位的。

作者: maurice    时间: 2016-1-21 15:24
linjc 发表于 2016-1-21 09:23
ubuntu好像不能用root登陆的吧
可以先用sudo passwd设置密码,再用su root切换到root用户

linjc 问题解决了
http://developer.t-firefly.com/thread-4908-1-1.html




欢迎光临 Firefly开源社区 (https://dev.t-firefly.com/) Powered by Discuz! X3.1