Firefly开源社区

标题: Core3568J 自制扩展底板遇到的问题！ [打印本页]

作者: 王朝科56888 时间: 2022-7-25 15:46
标题: Core3568J 自制扩展底板遇到的问题！
问题用Core3568J 做产品开发，自己做的底板，现在遇到如下问题：
1，用USB线刷好debian10固件后，在其他firefly底板上可以正常运行，启动，在我们自己做的底板上，启动不了，Log如下：

U-Boot SPL 2017.09
......
......
[ 0.829499] mpp_service mpp-srv: probe start
[ 0.830725] iommu: Adding device fdf40000.rkvenc to group 5
[ 0.830829] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu

启动停止在[ 0.830829] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu 这一行。不知道是不是硬件上还需要加什么模块？？？

第二个问题：
如何制作用TF卡刷的固件系统，RK固件可以直接用RKDevTool_Release_v2.85_02 这个工具，通过OTG来线刷。我们的产品只预留了TF接口，是否有详细
的制作TF刷的固件的教程。或者说是否有专门的打包工具。按照WIKI上提供的编译方法，编译出来的固件不支持卡刷。

tchip_askquestions

log.txt

18.95 KB, 下载次数: 1, 下载积分: 灯泡 -1 , 经验 -1

作者: Liuth 时间: 2022-7-25 15:59
1. log没有任何报错，看不出来，你可以多等一会，看会不会打印卡在哪里了
2.sd卡升级查看wiki：
https://wiki.t-firefly.com/Core-3568J/05-upgrade_firmware_sd.html

作者: 王朝科56888 时间: 2022-7-25 16:19
我这边等待10多分钟了都没有反应，一直停在[ 0.830829] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu
我底板很简单，就扩展了USB 和 uart，没有扩展PCIe，有没有可能是这里的问题？ MPP 会检测什么硬件吗？

作者: 王朝科56888 时间: 2022-7-25 16:23
在你们底板上正常启动时这样的
0.301461] NET: Registered protocol family 1
[ 0.303541] Trying to unpack rootfs image as initramfs...
[ 0.786490] Freeing initrd memory: 8988K
[ 0.788328] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.789201] kvm [1]: 16-bit VMID
[ 0.789242] kvm [1]: GICv3: no GICV resource entry
[ 0.789256] kvm [1]: disabling GICv2 emulation
[ 0.789267] kvm [1]: GIC system register CPU interface enabled
[ 0.789444] kvm [1]: vgic interrupt IRQ1
[ 0.789656] kvm [1]: VHE mode initialized successfully
[ 0.792321] Initialise system trusted keyrings
[ 0.792584] workingset: timestamp_bits=45 max_order=20 bucket_order=0
[ 0.803467] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.803915] jffs2: version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
[ 0.804243] fuse init (API version 7.27)
[ 0.804972] SGI XFS with security attributes, no debug enabled
[ 0.809025] NET: Registered protocol family 38
[ 0.809084] Key type asymmetric registered
[ 0.809100] Asymmetric key parser 'x509' registered
[ 0.809158] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 0.809376] io scheduler noop registered
[ 0.809402] io scheduler deadline registered
[ 0.809612] io scheduler cfq registered (default)
[ 0.809630] io scheduler mq-deadline registered
[ 0.809654] io scheduler kyber registered
[ 0.811161] rockchip-csi2-dphy csi2-dphy0: csi2 dphy0 probe successfully!
[ 0.811428] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 0.814792] phy phy-fe8a0000.usb2-phy.0: Linked as a consumer to regulator.4
[ 0.815220] phy phy-fe8a0000.usb2-phy.1: Linked as a consumer to regulator.5
[ 0.816849] extcon extcon1: failed to create extcon usb2-phy link
[ 0.817023] phy phy-fe8b0000.usb2-phy.2: Linked as a consumer to regulator.4
[ 0.817299] phy phy-fe8b0000.usb2-phy.3: Linked as a consumer to regulator.4
[ 0.817496] phy phy-fe8b0000.usb2-phy.3: No vbus specified for otg port
[ 0.829712] rk-pcie 3c0800000.pcie: Linked as a consumer to regulator.17
[ 0.830409] mpp_service mpp-srv: 44f7b7b022d6 author: Caesar Wang 2022-04-27 Revert "Revert "video: rockchip: mpp: rkvdec2: set"
[ 0.830443] mpp_service mpp-srv: probe start
[ 0.831718] iommu: Adding device fdf40000.rkvenc to group 5
[ 0.831777] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu
[ 0.832062] mpp_rkvenc fdf40000.rkvenc: probing start
[ 0.832745] mpp_rkvenc fdf40000.rkvenc: venc regulator not ready, retry
[ 0.832775] rkvenc_init:1199: failed to add venc devfreq
[ 0.833232] mpp_rkvenc fdf40000.rkvenc: probing finish
[ 0.834898] iommu: Adding device fdea0400.vdpu to group 1
[ 0.834953] mpp_vdpu2 fdea0400.vdpu: Linked as a consumer to fdea0800.iommu
[ 0.835196] mpp_vdpu2 fdea0400.vdpu: probe device
[ 0.835945] mpp_vdpu2 fdea0400.vdpu: probing finish
[ 0.836726] iommu: Adding device fdee0000.vepu to group 3
[ 0.836780] mpp_vepu2 fdee0000.vepu: Linked as a consumer to fdee0800.iommu
[ 0.837043] mpp_vepu2 fdee0000.vepu: probe device
[ 0.837777] mpp_vepu2 fdee0000.vepu: probing finish
[ 0.838506] iommu: Adding device fdef0000.iep to group 4
[ 0.838554] mpp-iep2 fdef0000.iep: Linked as a consumer to fdef0800.iommu
[ 0.838773] mpp-iep2 fdef0000.iep: probe device
[ 0.839423] mpp-iep2 fdef0000.iep: allocate roi buffer failed
[ 0.839657] mpp-iep2 fdef0000.iep: probing finish
[ 0.840282] iommu: Adding device fded0000.jpegd to group 2
[ 0.840322] mpp_jpgdec fded0000.jpegd: Linked as a consumer to fded0480.iommu
[ 0.840525] mpp_jpgdec fded0000.jpegd: probe device
[ 0.841294] mpp_jpgdec fded0000.jpegd: probing finish
[ 0.841933] rk-pcie 3c0800000.pcie: missing legacy IRQ resource
[ 0.841982] rk-pcie 3c0800000.pcie: Missing *config* reg space
[ 0.842021] rk-pcie 3c0800000.pcie: host bridge /pcie@fe280000 ranges:
[ 0.842072] rk-pcie 3c0800000.pcie: err 0xf0000000..0xf00fffff -> 0xf0000000
[ 0.842109] rk-pcie 3c0800000.pcie: IO 0xf0100000..0xf01fffff -> 0xf0100000
[ 0.842138] rk-pcie 3c0800000.pcie: MEM 0xf0200000..0xf1ffffff -> 0xf0200000
[ 0.842169] rk-pcie 3c0800000.pcie: MEM 0x380000000..0x3bfffffff -> 0x380000000
[ 0.842213] iommu: Adding device fdf80200.rkvdec to group 6
[ 0.842270] mpp_rkvdec2 fdf80200.rkvdec: Linked as a consumer to fdf80800.iommu
[ 0.842589] mpp_rkvdec2 fdf80200.rkvdec: probing start
[ 0.842878] mpp_rkvdec2 fdf80200.rkvdec: 16 task capacity link mode detected
[ 0.843376] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found!
[ 0.843394] rkvdec2_init:661: No niu aclk reset resource define
[ 0.843412] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found!
[ 0.843437] rkvdec2_init:664: No niu hclk reset resource define
[ 0.843616] mpp_rkvdec2 fdf80200.rkvdec: sram_start 0x00000000fdcc0000
[ 0.843637] mpp_rkvdec2 fdf80200.rkvdec: rcb_iova 0x0000000010000000
[ 0.843651] mpp_rkvdec2 fdf80200.rkvdec: sram_size 45056
[ 0.843664] mpp_rkvdec2 fdf80200.rkvdec: rcb_size 65536
[ 0.843692] mpp_rkvdec2 fdf80200.rkvdec: min_width 512
[ 0.843774] mpp_rkvdec2 fdf80200.rkvdec: link mode probe finish
[ 0.843883] mpp_rkvdec2 fdf80200.rkvdec: probing finish
[ 0.844337] mpp_service mpp-srv: probe success
[ 0.850969] dma-pl330 fe530000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.850998] dma-pl330 fe530000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[ 0.854500] dma-pl330 fe550000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.854525] dma-pl330 fe550000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[ 0.856404] rockchip-system-monitor rockchip-system-monitor: system monitor probe
[ 0.858028] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[ 0.859260] fe670000.serial: ttyS3 at MMIO 0xfe670000 (irq = 68, base_baud = 1500000) is a 16550A
[ 0.860188] fe680000.serial: ttyS4 at MMIO 0xfe680000 (irq = 69, base_baud = 1500000) is a 16550A
[ 0.861104] fe6c0000.serial: ttyS8 at MMIO 0xfe6c0000 (irq = 70, base_baud = 1500000) is a 16550A
[ 0.864822] random: fast init done

中间有很多mpp和PCIe 的log，不知道扩展底板上是不是要添加什么必要的硬件电路？

作者: 时间的蝴蝶 时间: 2022-7-25 16:48

王朝科56888 发表于 2022-7-25 16:19
我这边等待10多分钟了都没有反应，一直停在[ 0.830829] mpp_rkvenc fdf40000.rkvenc: Linked as a cons ...

修改 dts，把没有用到的扩展，PCIe... 这些去掉，重新编译 kernel

作者: 王朝科56888 时间: 2022-7-28 11:02
之前的问题修改DTS都已经解决，系统正常跑起来了，现在还有最后一个问题，我们扩展了USB3.0hub，并且也工作正常，现在有个问题是
系统启动后一直会打印一个USB 错误
[  318.709154] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[  319.649079] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[  320.759093] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[  321.869099] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[  322.979059] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[  324.089031] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?

但是，如果我把USB3.0 hub断开的话，这个错误也都不提示了。感觉是扩展USBhub后，系统会自动检查一个USB设备。
请指教，系统是否在一直检查PCIe 接口呢？或者是其他什么原因？

作者: 时间的蝴蝶 时间: 2022-7-29 09:57

王朝科56888 发表于 2022-7-28 11:02
之前的问题修改DTS都已经解决，系统正常跑起来了，现在还有最后一个问题，我们扩展了USB3.0hub，并且也工作 ...

你确定所有扩展口都正常工作？
看起来是 USB口的硬件问题，PCIe 关掉了不会检测的，你可以接其它USB设备试一下。

欢迎光临 Firefly开源社区 (https://dev.t-firefly.com/)