官方ubuntu&debian源代码编译后刷进开发板不开机

风火轮用户aDbC0 · 发表于 2024-7-4 09:28:21

本帖最后由风火轮用户aDbC0 于 2024-7-4 10:03 编辑

（为了高效，请按如下格式提问）

硬件主板型号：yy3568
固件名称/系统版本：debian11&ubuntu
自编的或固件下载地址：https://pan.baidu.com/s/1Au7gpG4 ... =2nfa#list/path=%2F
Log日志: (可以导出，用TXT附件上传)
编译结果:

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "game_test.gba"
mke2fs: Could not allocate block in ext2 filesystem while populating file system
Retring with increased size....(1/10)
Making /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/oem.img from /home/ubuntu18/Desktop/YY3568-Linux/output/oem with size(55284KB)
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 55284 1k blocks and 13832 inodes
Filesystem UUID: d281a2fb-3164-4b31-bf7b-98c0875b3c95
Superblock backups stored on blocks:
8193, 24577, 40961
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
tune2fs 1.44.1 (24-Mar-2018)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Done packing /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/oem.img
Preparing partiton userdata
Merging /home/ubuntu18/Desktop/YY3568-Linux/device/rockchip/common/images/userdata/userdata_normal into /home/ubuntu18/Desktop/YY3568-Linux/output/userdata
Packing /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/userdata.img from /home/ubuntu18/Desktop/YY3568-Linux/output/userdata.fs
Making /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/userdata.img from /home/ubuntu18/Desktop/YY3568-Linux/output/userdata (auto sized)
Making /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/userdata.img from /home/ubuntu18/Desktop/YY3568-Linux/output/userdata with size(4368KB)
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 4368 1k blocks and 1096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
tune2fs 1.44.1 (24-Mar-2018)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Done packing /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/userdata.img
Packed files:
MiniLoaderAll.bin(/home/ubuntu18/Desktop/YY3568-Linux/u-boot/rk356x_spl_loader_v1.17.112.bin): 447K
boot.img(/home/ubuntu18/Desktop/YY3568-Linux/kernel/boot.img): 42M
misc.img(/home/ubuntu18/Desktop/YY3568-Linux/device/rockchip/common/images/blank-misc.img): 48K
oem.img: 54M
parameter.txt(/home/ubuntu18/Desktop/YY3568-Linux/device/rockchip/.chips/rk3566_rk3568/parameter-yy3568.txt): 488
recovery.img(/home/ubuntu18/Desktop/YY3568-Linux/buildroot/output/rockchip_rk3568_recovery/images/recovery.img): 49M
rootfs.img(/home/ubuntu18/Desktop/YY3568-Linux/.repo/projects/rootfs/ubuntu.img): 7.9G
uboot.img(/home/ubuntu18/Desktop/YY3568-Linux/u-boot/uboot.img): 4.0M
userdata.img: 4.3M
Images in /home/ubuntu18/Desktop/YY3568-Linux/output/firmware are ready!
Running mk-firmware.sh - build_firmware succeeded.
==========================================
Start packing update image
==========================================
Generating package-file for update :
# NAME PATH
package-file package-file
parameter parameter.txt
bootloader MiniLoaderAll.bin
uboot uboot.img
misc misc.img
boot boot.img
recovery recovery.img
backup RESERVED
userdata userdata.img
oem oem.img
rootfs rootfs.img
Packing /home/ubuntu18/Desktop/YY3568-Linux/output/firmware/update.img for update...
Android Firmware Package Tool v2.2
------ PACKAGE ------
Add file: ./package-file
package-file,Add file: ./package-file done,offset=0x800,size=0xe1,userspace=0x1
Add file: ./parameter.txt
parameter,Add file: ./parameter.txt done,offset=0x1000,size=0x1f4,userspace=0x1,flash_address=0x00000000
Add file: ./MiniLoaderAll.bin
bootloader,Add file: ./MiniLoaderAll.bin done,offset=0x1800,size=0x6f9c0,userspace=0xe0
Add file: ./uboot.img
uboot,Add file: ./uboot.img done,offset=0x71800,size=0x400000,userspace=0x800,flash_address=0x00004000
Add file: ./misc.img
misc,Add file: ./misc.img done,offset=0x471800,size=0xc000,userspace=0x18,flash_address=0x00006000
Add file: ./boot.img
boot,Add file: ./boot.img done,offset=0x47d800,size=0x2908600,userspace=0x5211,flash_address=0x00008000
Add file: ./recovery.img
recovery,Add file: ./recovery.img done,offset=0x2d86000,size=0x30cec00,userspace=0x619e,flash_address=0x00028000
Add file: ./userdata.img
userdata,Add file: ./userdata.img done,offset=0x5e55000,size=0x444000,userspace=0x888,flash_address=0x00058000
Add file: ./oem.img
oem,Add file: ./oem.img done,offset=0x6299000,size=0x35fd000,userspace=0x6bfa,flash_address=0x00068000
Add file: ./rootfs.img
rootfs,Add file: ./rootfs.img done,offset=0x9896000,size=0x1f4000000,userspace=0x3e8000,flash_address=0x000a8000
Add CRC...
Make firmware OK!
------ OK ------
********rkImageMaker ver 2.23********
Generating new image, please wait...
Writing head info...
Writing boot file...
Writing firmware...
Generating MD5 data...
MD5 data generated successfully!
New image generated successfully!
Running mk-updateimg.sh - build_updateimg succeeded.
Running 99-all.sh - build_all succeeded.

复制代码

uart debug 结果:

[ 3.984339] CPU0 CPU1 CPU2 CPU3
[ 3.984900] 13: 329 495 213 431 GICv3 26 Level arch_timer
[ 3.985665] 14: 0 0 0 0 GICv3 141 Level rk_timer
[ 3.986417] 15: 0 0 0 0 GICv3 260 Level arm-pmu
[ 3.987159] 16: 0 0 0 0 GICv3 261 Level arm-pmu
[ 3.987901] 17: 0 0 0 0 GICv3 262 Level arm-pmu
[ 3.988643] 18: 0 0 0 0 GICv3 263 Level arm-pmu
[ 3.989385] 19: 0 0 0 0 GICv3 128 Level ahci[fc800000.sata]
[ 3.990220] 25: 0 0 0 0 GICv3 183 Level fde4b000.iommu
[ 3.991020] 29: 0 0 0 0 GICv3 171 Level fdea0400.vdpu
[ 3.991808] 30: 0 0 0 0 GICv3 170 Level fdea0800.iommu
[ 3.992606] 32: 0 0 0 0 GICv3 94 Level fded0000.jpegd
[ 3.993406] 33: 0 0 0 0 GICv3 93 Level fded0480.iommu
[ 3.994204] 34: 0 0 0 0 GICv3 96 Level fdee0000.vepu
[ 3.994991] 35: 0 0 0 0 GICv3 95 Level fdee0800.iommu
[ 3.995790] 36: 0 0 0 0 GICv3 88 Level fdef0800.iommu, fdef0000.iep
[ 3.996692] 38: 0 0 0 0 GICv3 173 Level fdf40f00.iommu
[ 3.997490] 39: 0 0 0 0 GICv3 174 Level fdf40f00.iommu
[ 3.998288] 41: 0 0 0 0 GICv3 124 Level fdf80800.iommu
[ 3.999088] 45: 0 0 0 0 GICv3 91 Level fdff1a00.iommu
[ 3.999886] 48: 0 0 0 0 GICv3 180 Level fe043e00.iommu
[ 4.000685] 53: 0 0 0 0 GICv3 197 Level pcie-sys
[ 4.001438] 56: 0 0 0 0 GICv3 194 Level (null)
[ 4.002170] 61: 0 0 0 0 GICv3 133 Level fe300000.spi
[ 4.002946] 62: 81 0 0 0 GICv3 51 Level mmc0
[ 4.003667] 66: 0 0 0 0 GICv3 46 Level fe530000.dmac
[ 4.004455] 67: 0 0 0 0 GICv3 45 Level fe530000.dmac
[ 4.005242] 68: 0 0 0 0 GICv3 48 Level fe550000.dmac
[ 4.006030] 69: 0 0 0 0 GICv3 47 Level fe550000.dmac
[ 4.006817] 70: 0 0 0 0 GICv3 34 Level can0
[ 4.007539] 81: 0 0 0 0 GICv3 147 Level rockchip_thermal
[ 4.008349] 83: 0 0 0 0 GICv3 167 Level rockchip_usb2phy
[ 4.009160] 84: 0 0 0 0 GICv3 168 Level rockchip_usb2phy
[ 4.009970] 85: 0 0 0 0 GICv3 65 Level (null)
[ 4.010701] 86: 0 0 0 0 GICv3 66 Level (null)
[ 4.011432] 87: 0 0 0 0 GICv3 67 Level (null)
[ 4.012163] 88: 0 0 0 0 GICv3 68 Level (null)
[ 4.012893] 89: 0 0 0 0 GICv3 69 Level (null)
[ 4.013623] 90: 0 0 0 0 GICv3 284 Edge debug-signal
[ 4.014400] 91: 0 0 0 0 GICv3 150 Level debug
[ 4.015127] PMU:
[ 4.015293] pwr 0x00a0: 0000005f 00000000 00000003 00000000
[ 4.015836] status 0x0098: 0000005f 00000000 0000005f 00000000
[ 4.016374] req 0x0050: 000001cc 00000000 00000000 00000000
[ 4.016913] idle 0x0068: 000001ce 00000000 0000ffff 0000000f
[ 4.017452] ack 0x0060: 000001ce 00000000 000001ce 00000000
[ 4.017991] THERMAL REGS:
[ 4.018233] 00000000: 00000fc0 00030033 00000301 00000002 00000000 00000000 00000000 00000000
[ 4.018988] 00000020: 0000086c 0000085c 00000000 00000000 00000940 00000000 00000000 00000000
[ 4.019743] 00000040: 00000a70 00000a70 00000000 00000000 00000000 00000000 00000000 00000000
[ 4.020499] 00000060: 00000004 00000004 00000656 00000656 00000000 00000000 00000000 00000000
[ 4.021249] 00000080: 00000000 00000000
[ 4.021587] Kernel Offset: disabled
[ 4.021903] CPU features: 0x000,08000026,2a00aa18
[ 4.022320] Memory Limit: none
[ 4.027437] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

复制代码

问题描述及复现步骤:
debian11 与ubuntu代码刷进去不开机,docker与直接编译都试过了,刷回老版固件就能开机,补充一点,官方编译好的固件我下载进去也开不了机,https://pan.baidu.com/s/1suSVoRE ... cs9p#list/path=%2F;

何浩钧 · 发表于 2024-7-4 10:47:07

你好！请参照wiki教程更新一下板载配置，链接如下：

https://wiki.youyeetoo.cn/zh/YY3568

风火轮用户aDbC0 · 发表于 2024-7-4 11:02:34

何浩钧发表于 2024-7-4 10:47
你好！请参照wiki教程更新一下板载配置，链接如下：

https://wiki.youyeetoo.cn/zh/YY3568

谢谢你我试试看

风火轮用户aDbC0 · 发表于 2024-7-4 11:09:09

何浩钧发表于 2024-7-4 10:47
你好！请参照wiki教程更新一下板载配置，链接如下：

https://wiki.youyeetoo.cn/zh/YY3568

何工你好,我想请问一下,我手上有好几块YY3568的电路板, 这些电路板需要每个都生成一个old.bin文件吗?还是说公共的即可, 未来的我们可能还会购入很多3568的核心板,后面升级还需要这么做吗

风火轮用户aDbC0 · 发表于 2024-7-4 11:58:25

何浩钧发表于 2024-7-4 10:47
你好！请参照wiki教程更新一下板载配置，链接如下：

https://wiki.youyeetoo.cn/zh/YY3568

这是我的old bin文件

何浩钧 · 发表于 2024-7-4 13:50:29

风火轮用户aDbC0 发表于 2024-7-4 11:09
何工你好,我想请问一下,我手上有好几块YY3568的电路板, 这些电路板需要每个都生成一个old.bin文件吗?还是 ...

后面购买的不需要，之前购买的可能需要。

何浩钧 · 发表于 2024-7-4 13:52:56

何浩钧发表于 2024-7-4 13:50
后面购买的不需要，之前购买的可能需要。

这个文件不是公用的。

风火轮用户aDbC0 · 发表于 2024-7-4 13:59:38

何浩钧发表于 2024-7-4 13:52
这个文件不是公用的。

何工你帮我更新一下这三个bin吧谢谢了,客服让我找你

何浩钧 · 发表于 2024-7-4 14:18:10

风火轮用户aDbC0 发表于 2024-7-4 11:58
这是我的old bin文件

你好！文件见附件。

风火轮用户aDbC0 · 发表于 2024-7-4 14:56:22

何浩钧发表于 2024-7-4 14:18
你好！文件见附件。

谢谢了何工我试试

风火轮用户aDbC0 · 发表于 2024-7-4 15:02:27

何浩钧发表于 2024-7-4 14:18
你好！文件见附件。

何工我看了一下好像你生成的这几个new bin 大小是0字节哦图片.png

,我用二进制看的也是这样

何浩钧 · 发表于 2024-7-4 18:30:47

风火轮用户aDbC0 发表于 2024-7-4 15:02
何工我看了一下好像你生成的这几个new bin 大小是0字节哦,我用二进制看的也是这样 ...

不好意思，我看看是不是搞错了。

何浩钧 · 发表于 2024-7-4 18:58:26

风火轮用户aDbC0 发表于 2024-7-4 15:02
何工我看了一下好像你生成的这几个new bin 大小是0字节哦,我用二进制看的也是这样 ...

你好！请试试这个最新的。见附件。