全志在线开发者论坛

whycanservice2

@z2500abc 不确定。。。有可能能行。

whycanservice2

@z2500abc 大概率有可能无法初始化。。。

whycanservice2

@tivon 大概率此引脚已经被占用了。。

whycanservice2

@eestr 定制串口屏？

whycanservice2

@pxclihai 上一次遇到这个问题是底部焊盘未良好焊接导致的。

whycanservice2

@kennsu clk=25 应该是不合适的 pll倍频分频一般偶数频率容易匹配，8的倍数比较好。你这种情况是典型的无法匹配最接近的频率导致的，在启动时会给出打印说选择频率是25000000 但实际频率是xxxxxx。。

whycanservice2

@kennsu 设备树 lcd0 配置不正确

whycanservice2

@nice0513 建议先看一下提问的艺术！

whycanservice2

@dazb3 需要切换声卡才可以使用i2s播放。给你一份文件吧。D1_Linux_AUDIOCODEC_开发指南.pdf

whycanservice2

@dazb3

修改如下：

	daudio2_pins_a: daudio2@0 {
		/* I2S_PIN: MCLK, BCLK, LRCK */
		pins = "PB7", "PB5", "PB6";
		function = "i2s2";
		drive-strength = <20>;
		bias-disable;
	};

	daudio2_pins_b: daudio2@1 {
		/* I2S_PIN: DOUT0 */
		pins = "PB4";
		function = "i2s2_dout";
		drive-strength = <20>;
		bias-disable;
	};

	daudio2_pins_c: daudio2@2 {
		/* I2S_PIN: DIN0 */
		pins = “PB7", "PB5", "PB6", "PB4";
		function = "io_disabled";
		drive-strength = <20>;
		bias-disable;
	};

whycanservice2

@dazb3 在 T113 I2S 音频输出至 Lontium 芯片 / T113 I2S Audio Output to Lontium chip 中说：

> &daudio2 {
> 	mclk_div = <0x00>;
> 	frametype = <0x00>;
> 	tdm_config = <0x01>;
> 	sign_extend = <0x00>;
> 	tx_data_mode = <0x00>;
> 	rx_data_mode = <0x00>;
> 	msb_lsb_first = <0x00>;
> 	pcm_lrck_period = <0x20>;
> 	slot_width_select = <0x20>;
> 	asrc_function_en = <0x00>;
> 	pinctrl-names   = "default", "sleep";
> 	pinctrl-0       = <&daudio2_pins_a  &daudio2_pins_b>;
> 	pinctrl-1       = <&daudio2_pins_c>;
> 	pinctrl_used	= <0x0>;
> 	daudio_type = <0x1>;
> 	status = "okay";
> };

whycanservice2

@huhanshuang124 底部引脚没焊接到

whycanservice2

@lyg116 双屏是有办法的，异显不可以但是可以添加spi屏异显。

whycanservice2

@c5kjz 应该也适用的

whycanservice2

@qz_18732517808 axp2101

whycanservice2

@boguang_li 检查屏驱动程序，内部初始化代码有可能进入死循环。遇到过类似情况。

whycanservice2

@ggy321 在 d1s + st7701s RGB颜色异常中说：

lcd_frm = <1>;这个配置要看你的屏驱动配置的是多少bit位宽的数据，如果配置不正确就是你看到的这样。过渡不平滑

whycanservice2

@fe3o4 还有这个芯片？啥规格说一下呗

whycanservice2

@godzhou0909 硬件电路 tf卡供电串2.2R电阻+对地10uf电容。

whycanservice2

@dazb3 我记得tplayerdemo可以压力测试可以循环播放一个文件夹路径下的所有视频文件，不知道这个是否有参考价值。

whycanservice2

@sofia 对于这个我也不太清楚可以参考手册确定。

whycanservice2

@cc3366cc 是的，此处spi1 主要是用于 spi显示器用的，如果不是显示用的话可以使用spi0，前提是spi0，可以配置独立cs引脚。因为spi是可以接多个设备的接口。

whycanservice2

@sofia 固件有问题

whycanservice2

@yuqingli 根据你的描述大概率硬件问题。信号回路存在串扰导致工作不稳定。

whycanservice2

@cc3366cc 复用的意思是只能选择其中一种使用。

whycanservice2

@sensiki ```
https://bbs.aw-ol.com/topic/4023/全志在线开源芯片-新-sdk-平台下载方法汇总/2

whycanservice2

@wyljkl 大概率是由于屏关机后没有使用 0x28 0x10 代码让屏进入休眠后关闭。然后应当在启动时候先给刷屏后给背光，关闭时候先关闭背光再停止刷新然后让屏休眠。按照这个步骤应该不会再出现残影了。

whycanservice2

@cjia3254 这俩引脚通常用于显示部分，请检查处理复用

whycanservice2

@whycan 这有点厉害了！！！

whycanservice2

@lyg116 你说的识别是指usb无法被识别嘛？

whycanservice2

@awwwwa 之前尝试修改过此文件，但结果烧录出来的卡始终是量产卡（烧录时选择启动卡烧录之后依然是量产卡）。。。。

whycanservice2

@baiwen 感谢回复，实际操作我参考了教程，也下载了论坛上各路大神编译好的固件烧录到tf卡，结果均如同1楼所示，并非编译环境配置问题，也参考手册修改了sys_config.fex，结果均无效，后来发现了image.cfg 缺少gpt配置文件，修改此处确实可以识别gpt，但不知为何，烧录的卡均为量产卡，即使是在使用PhoenixCard烧录选择启动卡的前提下，烧录出来的卡依然是“量产卡“！启动日志与烧录量产卡一样！。还追踪到是pack脚本文件中并未处理storage_type=5的情况，但这个脚本十分复杂不知道从哪下手修改。还请大佬多费点心帮忙看一下该如何处理。十分感谢！

whycanservice2

@zeeking 至今没有解决。。。。线刷了

whycanservice2

@yuzukitsuru 大佬 FFmpeg 不包含 FFplay 啊？

whycanservice2

@whycanservice2 最新进展情况发现 pack 脚本文件导出的最终 image.cfg 缺少 gpt配置fex文件？！

whycanservice2

@whycanservice2 顶起来问题还未解决。有大佬指点一下啥情况嘛？

whycanservice2

@awwwwa 这个尝试过 5和1 均无效，另一个sdk 这里配置的是5，且手册种指明 sd卡 nand emmc 用同一种img都是可以的。

whycanservice2

@kanken6174 经仔细查看，pack -d命令生成的是一个用于sd卡座式的debug接口固件。并非用于启动。我编译了Tina linux 使用pack命令可以得到一个固件，修改线刷文件后使用线刷可以启动进入控制台。线刷后取出sd卡挂载，用磁盘分析查看是 GUID分区格式的。但是用PhoenixCard直接烧录sd卡得到的是MBR分区格式的。

whycanservice2

@yuzukitsuru 使用了 docker镜像编译出来的固件也是这样的。无法启动，分区不是GUID

whycanservice2

@whycanservice2 经报错提示修改tina-v853-open/device/config/common/debug/目录下的两个文件，添加sun8iw21p1 引脚定义，如下：
card_debug_pin

sun8iw21p1  port:PF02<4><1><1><default>    port:PF04<4><1><1><default>     0       port:PF00<4><1><1><default>    port:PF05<4><1><1><default>    port:PF03<4><1><1><default>     port:PF01<4><1><1><default>    1

card_debug_string

sun8iw21p1  uart_para uart_debug_port uart_debug_tx uart_debug_rx uart0 uart0_used uart0_port uart0_tx uart0_rx uart1 jtag_para jtag_ms jtag_ck jtag_do jtag_di sdc0 sdc0_used

之后使用pack -d 生成v851s_linux_lizard_card0.img 的固件，烧录之后挂载到linux用磁盘工具查看依旧是 mbr分区。如1楼图片所示一样。
插入板子上电启动结果无引导输出，无uboot输出之后进入内核开始打印logo 最后卡在以下位置。跟之前烧录 pack命令打包出来的固件一样的位置，个人感觉是打包分区不是GUID的问题。但找不到在哪修改。

[    4.747967] List of all partitions:
[    4.752029] b300          248064 mmcblk0  driver: mmcblk
[    4.758000]   b301             512 mmcblk0p1 a0085546-4166-744a-a353-fca9272b8e45
[    4.766525]   b302             256 mmcblk0p2 a0085546-4166-744a-a353-fca9272b8e46
[    4.775011]   b303            6144 mmcblk0p3 a0085546-4166-744a-a353-fca9272b8e47
[    4.783424]   b304           25600 mmcblk0p4 a0085546-4166-744a-a353-fca9272b8e48
[    4.791821]   b305           51200 mmcblk0p5 a0085546-4166-744a-a353-fca9272b8e49
[    4.800215]   b306          139759 mmcblk0p6 a0085546-4166-744a-a353-fca9272b8e4a
[    4.808599] No filesystem could mount root, tried:  ext3 ext2 ext4 squashfs vfat msdos
[    4.817586] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,4)
[    4.827030] CPU: 0 PID: 1 Comm: swapper Not tainted 4.9.191 #1
[    4.833551] Hardware name: sun8iw21
[    4.837482] [<c010d5a0>] (unwind_backtrace) from [<c010a694>] (show_stack+0x10/0x14)
[    4.846153] [<c010a694>] (show_stack) from [<c017050c>] (panic+0xac/0x2b8)
[    4.853853] [<c017050c>] (panic) from [<c09012cc>] (mount_block_root+0x258/0x300)
[    4.862233] [<c09012cc>] (mount_block_root) from [<c0901500>] (prepare_namespace+0x118/0x178)
[    4.871777] [<c0901500>] (prepare_namespace) from [<c0900eb4>] (kernel_init_freeable+0x144/0x178)
[    4.881708] [<c0900eb4>] (kernel_init_freeable) from [<c06807c4>] (kernel_init+0x8/0x118)
[    4.890863] [<c06807c4>] (kernel_init) from [<c0106e08>] (ret_from_fork+0x14/0x2c)
[    4.899335] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,4)
[    4.909645] sunxi dump enabled
[    4.913055] dump regs done
[    4.916112] flush cache done
[    4.919350] crashdump enter

whycanservice2

@kanken6174 您好大佬，使用pack -d命令打包确实失败了日志如下：

lovexulu@lovexulu:~/tina-v853-open$ pack -d

/home/lovexulu/tina-v853-open/build/pack -c sun8iw21p1 -i v851s -p openwrt -b lizard -k linux-4.9 -d card0 -v none -m normal -w none -n default 

INFO: /home/lovexulu/tina-v853-open/out/v851s/common/keys

copying tools file

copying configs file

copying product configs file

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/aultls32.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/aultools.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package_nor.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardscript.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardscript_secure.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardtool.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/diskfs.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/dragon_toc.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/env_burn.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/env.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/esm.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_crashdump.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_linux.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_nor.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/jffs2.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/overlay.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/split_xxxx.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sunxi.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_config.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_dump.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_nor.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_private.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc0.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc0_ft.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc1.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool_crash.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool_test.fex

copying boot resource

copying boot file

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_nand_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_nand.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_sdcard_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_sdcard.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_spinor_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/fes1_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/fes1.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/optee_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/optee_sun8iw21p1-monitor.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-spinor-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-spinor-secure-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor-secure.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_nand_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_nand.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_sdcard_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_sdcard.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_spinor_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/fes1_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/fes1.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/optee_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/optee_sun8iw21p1-monitor.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-spinor-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-spinor-secure-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor-secure.fex'

copying boot file 2.0

'/home/lovexulu/tina-v853-open/out/v851s/lizard/openwrt/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

copying additional files

ERROR: uart_switch: sun8iw21p1 not configured in card_debug_pin/card_debug_string!

lovexulu@lovexulu:~/tina-v853-open$

使用pack命令打包日志如下：

lovexulu@lovexulu:~/tina-v853-open$ pack

/home/lovexulu/tina-v853-open/build/pack -c sun8iw21p1 -i v851s -p openwrt -b lizard -k linux-4.9 -d uart0 -v none -m normal -w none -n default 

INFO: /home/lovexulu/tina-v853-open/out/v851s/common/keys

copying tools file

copying configs file

copying product configs file

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/aultls32.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/aultools.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot_package_nor.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardscript.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardscript_secure.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/cardtool.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/diskfs.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/dragon_toc.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/env_burn.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/env.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/esm.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_crashdump.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_linux.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/image_nor.cfg

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/jffs2.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/overlay.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/split_xxxx.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sunxi.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_config.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_dump.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_nor.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition_private.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc0.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc0_ft.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/toc1.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool_crash.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool.fex

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/usbtool_test.fex

copying boot resource

copying boot file

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_nand_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_nand.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_sdcard_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_sdcard.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/boot0_spinor_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/fes1_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/fes1.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/optee_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/optee_sun8iw21p1-monitor.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-spinor-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s/bin/u-boot-spinor-secure-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor-secure.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_nand_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_nand.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_sdcard_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_sdcard.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/boot0_spinor_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/boot0_spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/fes1_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/fes1.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/optee_sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/optee_sun8iw21p1-monitor.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/optee.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-spinor-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor.fex'

'/home/lovexulu/tina-v853-open/device/config/chips/v851s//bin/u-boot-spinor-secure-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot-spinor-secure.fex'

copying boot file 2.0

'/home/lovexulu/tina-v853-open/out/v851s/lizard/openwrt/u-boot-sun8iw21p1.bin' -> '/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/u-boot.fex'

copying additional files

handle partition_size

sunxi_dtb create

p=soc c=product state=0

p=soc c=power_sply state=0

p=soc c=target state=0

p=soc c=card_boot state=0

p=soc c=card0_boot_para state=0

p=soc c=card2_boot_para state=0

p=soc c=spinor_para state=0

p=soc c=twi_para state=0

p=soc c=uart_para state=0

p=soc c=jtag_para state=0

p=soc c=dram state=0

Conver script to dts ok.

update optee

commit : 77d9f87226



sboot file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sboot.bin

script file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_config.bin



update:unable to open sboot file

script update sboot ok

do not set LINUX_DTBO_FILE

pack boot package

content_count=3

2:LICHEE_REDUNDANT_ENV_SIZE:

16150 块

16150 块

packing for linux

normal

make user resource for : sys_partition.fex

handle partition user-res

no user resource partitions

APP_PART_DOWNLOAD_FILE = /home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/app.fex

Need size of filesystem

no data resource partitions

====================================

show sys_partition.fex message

------------------------------------

  [mbr]

  mbr_size  : 4096 Kbyte

------------------------------------

  partition_name  : boot-res

  partition_size  : 1024

  downloadfile  : boot-resource.fex

  boot-resource.fex size : 80K byte

------------------------------------

  partition_name  : env

  partition_size  : 512

  downloadfile  : env.fex

  env.fex size : 128K byte

------------------------------------

  partition_name  : boot

  partition_size  : 25200

  downloadfile  : boot.fex

  boot.fex -> /home/lovexulu/tina-v853-open/out/v851s/lizard/openwrt/boot.img

  boot.img size : 7.6M byte

------------------------------------

  partition_name  : rootfs

  partition_size  : 102400

  downloadfile  : rootfs.fex

  rootfs.fex -> /home/lovexulu/tina-v853-open/out/v851s/lizard/openwrt/rootfs.img

  rootfs.img size : 29M byte

------------------------------------

  partition_name  : UDISK

------------------------------------

commit : f7388902e9-dirty

mbr count = 4



partitation file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition.bin

mbr_name file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sunxi_mbr.fex

download_name file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/dlinfo.fex



mbr size = 4096

mbr magic softw411

disk name=boot-res

disk name=env

disk name=boot

disk name=rootfs

disk name=UDISK

this is not a partition key

update_for_part_info 0

crc 0 = f8c0f1be

crc 1 = 6d7da0e3

crc 2 = 8cb5545

crc 3 = 9d760418

MBR addr = 0x2000,logic_offset = 0xa000 GPT:boot-res    : c000          c3ff        

MBR addr = 0x2400,logic_offset = 0xa000 GPT:env         : c400          c5ff        

MBR addr = 0x2600,logic_offset = 0xa000 GPT:boot        : c600          1286f       

MBR addr = 0x8870,logic_offset = 0xa000 GPT:rootfs      : 12870         2b86f       

MBR addr = 0x21870,logic_offset = 0xa000 GPT:UDISK       : 2b870         ffffffde    

gpt_head->header_crc32 = 0x825dc7c2

GPT----part num 5---

gpt_entry: 128

gpt_header: 92

GPT:boot-res    : c000          c3ff        

GPT:env         : c400          c5ff        

GPT:boot        : c600          1286f       

GPT:rootfs      : 12870         2b86f       

GPT:UDISK       : 2b870         ffffffde    

update gpt file ok

update mbr file ok

commit : f7388902e9-dirty

temp = 20

mbr count = 4 total_sectors = 15269888 logic_offset = 20 media = 0



partitation file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sys_partition.bin

mbr_name file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/sunxi_mbr.fex

download_name file Path=/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out/dlinfo.fex



mbr size = 4096

mbr magic softw411

disk name=boot-res

disk name=env

disk name=boot

disk name=rootfs

disk name=UDISK

this is not a partition key

update_for_part_info 0

crc 0 = f8c0f1be

crc 1 = 6d7da0e3

crc 2 = 8cb5545

crc 3 = 9d760418

MBR addr = 0x2000,logic_offset = 0x14 GPT:boot-res    : 2014          2413        

MBR addr = 0x2400,logic_offset = 0x14 GPT:env         : 2414          2613        

MBR addr = 0x2600,logic_offset = 0x14 GPT:boot        : 2614          8883        

MBR addr = 0x8870,logic_offset = 0x14 GPT:rootfs      : 8884          21883       

MBR addr = 0x21870,logic_offset = 0x14 GPT:UDISK       : 21884         e8ffde      

gpt_head->header_crc32 = 0x3727b79d

GPT----part num 5---

gpt_entry: 128

gpt_header: 92

GPT:boot-res    : 2014          2413        

GPT:env         : 2414          2613        

GPT:boot        : 2614          8883        

GPT:rootfs      : 8884          21883       

GPT:UDISK       : 21884         e8ffde      

update gpt file ok

update mbr file ok

/home/lovexulu/tina-v853-open/tools/pack/pctools/linux/eDragonEx/

/home/lovexulu/tina-v853-open/out/v851s/lizard/pack_out

Begin Parse sys_partion.fex

Add partion boot-resource.fex BOOT-RESOURCE_FEX

Add partion very boot-resource.fex BOOT-RESOURCE_FEX

FilePath: boot-resource.fex

FileLength=14000Add partion env.fex ENV_FEX000000000

Add partion very env.fex ENV_FEX000000000

FilePath: env.fex

FileLength=20000Add partion boot.fex BOOT_FEX00000000

Add partion very boot.fex BOOT_FEX00000000

FilePath: boot.fex

FileLength=781000Add partion rootfs.fex ROOTFS_FEX000000

Add partion very rootfs.fex ROOTFS_FEX000000

FilePath: rootfs.fex

FileLength=1c60000BuildImg 0

Dragon execute image.cfg SUCCESS !

----------image is at----------



39M	/home/lovexulu/tina-v853-open/out/v851s/lizard/openwrt/v851s_linux_lizard_uart0.img



pack finish

lovexulu@lovexulu:~/tina-v853-open$

显示可以打包成功，请问报错是什么原因？

whycanservice2

@whycanservice2 顶起来，有大佬指点一下嘛？！

whycanservice2

微信图片编辑_20240113213018.jpg

这是使用晕哥网盘提供的sdk编译的固件烧录后的分区。可以正常TF卡启动。显示分区是GUID。。

这是拉取最新853sdk后打上柚木大佬提供的补丁编译的固件烧录后的分区，不能正常启动，显示分区是MBR。。
求教如何改变打包分区格式为GUID？

whycanservice2

最近打算做个小玩意，需要驱动0.96寸的st7735，为此也踩了些坑，特此记录分享。
直接上配置吧：
1.电路图：

这里使用到spi0 以及 PD2 PD4 还有PH0 作为pwm0 没截图显示。
2.board.dts配置

&pio{
            .....
            	spi0_pins_a: spi0@0 {
            
            		allwinner,pins = "PC0", "PC2";
            
            		allwinner,pname = "spi0_sclk", "spi0_mosi";
            
            		allwinner,function = "spi0";
            
            		allwinner,muxsel = <4>;
            
            		allwinner,drive = <1>;
            
            		allwinner,pull = <0>;
            
            	};

            	spi0_pins_b: spi0@1 {
            
            		allwinner,pins = "PC1";
            
            		allwinner,pname = "spi0_cs0";
            
            		allwinner,function = "spi0";
            
            		allwinner,muxsel = <4>;
            
            		allwinner,drive = <1>;
            
            		allwinner,pull = <1>;   // only CS should be pulled up
            
            	};

            	spi0_pins_c: spi0@2 {
            
            		allwinner,pins = "PC0", "PC1", "PC2";
            
            		allwinner,function = "io_disabled";
            
            		allwinner,muxsel = <0xf>;
            
            		allwinner,drive = <1>;
            
            		allwinner,pull = <0>;
            
            	};

................
}；

以上为引脚配置，

&spi0 {
	clock-frequency = <100000000>;
	pinctrl-0 = <&spi0_pins_a &spi0_pins_b>;
	pinctrl-1 = <&spi0_pins_c>;
	pinctrl-names = "default", "sleep";
	spi0_cs_number = <1>;
	spi1_cs_bitmap = <1>;
	spi_slave_mode = <0>;
	spi_dbi_enable = <0>;
	status = "okay";

	st7789v@0 {
	    	status = "okay";
	    	compatible = "sitronix,st7735r";
		reg = <0>;
		spi-max-frequency = <32000000>;
		rotate = <90>;
		bgr;
		fps = <60>;
		buswidth = <8>;
		reset-gpios = <&pio PD 2 1 1 2 1>;
		dc-gpios = <&pio PD 4 1 1 2 0>;
		led-gpios = <&pio PH 0 1 1 2 1>;
		debug = <1>;
	    };
};

这里是spi0配置。

2.内核配置（可以选择关闭disp2，以及设备树删除disp lcd0 部分）
切记。一定要关闭uboot disp2 。

3.修改驱动代码
.../linux-4.9/drivers/staging/fbtft/fbtft-core.c 文件中
static int fbtft_request_one_gpio(struct fbtft_par *par, const char *name, int index, int *gpiop) 函数，修改后代码如下：

static int fbtft_request_one_gpio(struct fbtft_par *par,
				  const char *name, int index, int *gpiop)
{
	struct device *dev = par->info->device;
	struct device_node *node = dev->of_node;
	int gpio, flags, ret = 0;
	struct gpio_config gpio_of_flags;

	if (of_find_property(node, name, NULL)) {
		gpio = of_get_named_gpio_flags(node, name, index, (enum of_gpio_flags *)&gpio_of_flags);
		if (gpio == -ENOENT)
			return 0;
		if (gpio == -EPROBE_DEFER)
			return gpio;
		if (gpio < 0) {
			dev_err(dev,
				"failed to get '%s' from DT\n", name);
			return gpio;
		}

		/* active low translates to initially low */
		flags = (gpio_of_flags.data & OF_GPIO_ACTIVE_LOW) ? GPIOF_OUT_INIT_LOW :
							GPIOF_OUT_INIT_HIGH;
		ret = devm_gpio_request_one(dev, gpio, flags,
						dev->driver->name);
		if (ret) {
			dev_err(dev,
				"gpio_request_one('%s'=%d) failed with %d\n",
				name, gpio, ret);
			return ret;
		}
		if (gpiop)
			*gpiop = gpio;
		fbtft_par_dbg(DEBUG_REQUEST_GPIOS, par, "%s: '%s' = GPIO%d\n",
							__func__, name, gpio);
	}
	return ret;
}

修改 .../linux-4.9/drivers/staging/fbtft/fb_st7735r.c 文件

主要修改一下驱动初始化代码列表：

static int default_init_sequence[] = {
	-1, MIPI_DCS_SOFT_RESET,
	-2, 150,                               /* delay */

	-1, MIPI_DCS_EXIT_SLEEP_MODE,
	-2, 500,                               /* delay */

	/* FRMCTR1 - frame rate control: normal mode
	 * frame rate = fosc / (1 x 2 + 40) * (LINE + 2C + 2D)
	 */
	-1, 0xB1, 0x05, 0x3C, 0x3C,

	/* FRMCTR2 - frame rate control: idle mode
	 * frame rate = fosc / (1 x 2 + 40) * (LINE + 2C + 2D)
	 */
	-1, 0xB2, 0x05, 0x3C, 0x3C,

	/* FRMCTR3 - frame rate control - partial mode
	 * dot inversion mode, line inversion mode
	 */
	-1, 0xB3, 0x05, 0x3C, 0x3C, 0x05, 0x3C, 0x3C,

	/* INVCTR - display inversion control
	 * no inversion
	 */
	-1, 0xB4, 0x03,

	/* PWCTR1 - Power Control
	 * -4.6V, AUTO mode
	 */
	-1, 0xC0, 0xAB, 0x0B, 0x04,

	/* PWCTR2 - Power Control
	 * VGH25 = 2.4C VGSEL = -10 VGH = 3 * AVDD
	 */
	-1, 0xC1, 0xC5,

	/* PWCTR3 - Power Control
	 * Opamp current small, Boost frequency
	 */
	-1, 0xC2, 0x0D, 0x00,

	/* PWCTR4 - Power Control
	 * BCLK/2, Opamp current small & Medium low
	 */
	-1, 0xC3, 0x8D, 0x6A,

	/* PWCTR5 - Power Control */
	-1, 0xC4, 0x8D, 0xEE,

	/* VMCTR1 - Power Control */
	-1, 0xC5, 0x0F,

	-1, 0x21, 

	-1, 0x3A, 0x05,

	-1, MIPI_DCS_SET_DISPLAY_ON,
	-2, 100,                               /* delay */

	-1, MIPI_DCS_ENTER_NORMAL_MODE,
	-2, 10,                               /* delay */

	/* end marker */
	-3
};

！！修改屏偏移

static void set_addr_win(struct fbtft_par *par, int xs, int ys, int xe, int ye)
{
	xs = xs + 1 ; xe = xe + 1 ;
	ys = ys + 26 ; ye = ye + 26;

	write_reg(par, MIPI_DCS_SET_COLUMN_ADDRESS,
		  xs >> 8, xs & 0xFF, xe >> 8, xe & 0xFF);

	write_reg(par, MIPI_DCS_SET_PAGE_ADDRESS,
		  ys >> 8, ys & 0xFF, ye >> 8, ye & 0xFF);

	write_reg(par, MIPI_DCS_WRITE_MEMORY_START);
}

修改屏参数：

static struct fbtft_display display = {
	.regwidth = 8,
	.width = 80,
	.height = 160,
	.init_sequence = default_init_sequence,
	.gamma_num = 2,
	.gamma_len = 16,
	.gamma = DEFAULT_GAMMA,
	.fbtftops = {
		.set_addr_win = set_addr_win,
		.set_var = set_var,
		.set_gamma = set_gamma,
	},
};

至此编译即可在小机端看到有fb0生成，屏幕点亮。
最后一图：

如有疑问，请跟贴。

whycanservice2

如题如题，找了一圈没发现芯片手册啊之类的资料，这个芯片不是开放的嘛？

whycanservice2

@kanken6174 我记得在某个摄像头的硬件设计手册中看到过I2C 的上拉电阻典型2.2K.。。

whycanservice2

@kanken6174 事实上i2c通讯速率不高，但对“沿”的要求非常高，需小于130ns，因此一定程度上可以看做高速信号处理，由于其控制器均为开漏输出，所以上拉电阻与线路寄生电容决定了沿的延迟。此处可以不必提高电压，选择减小上拉电阻是正确的办法。提高驱动能力是变相的减少了上拉电阻阻值。

whycanservice2

@vuiot 只有一个显示模块，并不能双屏。

whycanservice2

@wj8331585 大佬是如何配置vscode 编译sdk的啊，给指点一下。

whycanservice2

@polarcode 目前这种情况应该是变砖了，但是不慌，D1可以优先tf卡启动，可以烧录tf卡启动板子，等固件正常后，断电取出tf卡，按住FEL按键后上电或者RESET，听到电脑叮咚一下再松开FEL，此时应该就是进入烧录模式了。再使用工具将固件烧录进板子上的emmc。

whycanservice2

@wd15365693548 事实上更倾向于内核跑起来了，但串口配置不正确。如果内核没起来，会报错的！报错的话串口有输出。

whycanservice2

@easytech 应该不是这么改的，参考这个 https://bbs.aw-ol.com/topic/1673/

whycanservice2

@lyg116 现在板子存在什么问题呢？

whycanservice2

@easytech 启动内核是uboot的工作。所以这三条都是由uboot打印的。

whycanservice2

@easytech 我觉的大概率内核配置的debug串口不对。。因此没有了打印信息。

whycanservice2

@wellschan ST7701 7703这个驱动芯片貌似都不带缓存，所以无法硬90°旋转，但可以180°。

whycanservice2

@lovehex99 不是触摸屏。

whycanservice2

@jmhh247

device/softwinner/smallwit-game_v1/smallwit_game_v1.mk

# set primary display orientation to 270
PRODUCT_PROPERTY_OVERRIDES += \
        ro.surface_flinger.primary_display_orientation=ORIENTATION_270 \

whycanservice2

@lovehex99 在【开源游戏机】新开源机器预告（全志A133芯片/Android）中说：

@whycanservice2 坐等套件開賣記得上殼
聽說香橙派掌機應該會延期

好的，到时候这个帖子发布。

@whycanservice2 大佬，这个屏是多大尺寸，分辨率多少

这个是4寸的

whycanservice2

横屏搞定！

whycanservice2

现在基本的问题都解决了，背光显示屏正常，I2S声卡输出耳机、喇叭正常，
竖屏安卓适配正常，横屏还在研究中。换一种按键，再改一版就能量产了。

whycanservice2

@whycanservice 不知为何烧录之后是黑屏的。。。。

whycanservice2

@awwwwa 太棒了。这个需要串口命令启动游戏还是开机自启动啊？

whycanservice2

@gb2047 全志目前应该还没有带xspi控制器的芯片，因此可能没有这种开发板，毕竟xspi协议比较新。

whycanservice2

@lovehex99 最近有点忙，适配调试中。

whycanservice2

@yofa2008 厉害厉害。。怎么用CAD的？

whycanservice2

@yofa2008 MO0 MO1 分别使用PB7 PB6 .

whycanservice2

@steward 太好了。特别期待中。。

whycanservice2

@hsinyuwang 不错不错。这个掌机有没有固件？

whycanservice2

@ubuntu 电脑100W充电器是啥样的。输出电压？

whycanservice2

@wyz1226 这个应该是驱动和配置有些问题，猜测这个屏使用TE触发，且开启了触发，由于驱动原因导致屏te信号频率正确，导致计算得帧率越来越低。看到skip也在增加，说明时序配置也有错误。如果是mipi屏这个分辨率已经到达极限，如果是rgb屏可能超出限制。

whycanservice2

@lovehex99

whycanservice2

@lovehex99 安卓已经正常运行，目前电源回路有点小问题，正在处理中。

whycanservice2

@steward 大佬666.这就移植上去了。。。。

whycanservice2

@steward 在 Gaviar Handheld (小志掌機) 中说：

iriver D88

搜了下貌似国内这价格买不到啊。。。

whycanservice2

@masterlu fb0_format = <0>;

whycanservice2

@masterlu 可能跟我用的屏硬件部分不一样。如果是A40显示正常，配置完全相同情况下，就需要看看硬件是不是有什么地方不一样。首先你要确保软件配置完全相同。通常这种情况是输出信号并非rgb888造成的硬件的供电部分也会造成类似情况。

whycanservice2

@masterlu 硬件部分 vh vl vcom 电压正常？

whycanservice2

@masterlu lcd_frm=<0>;

whycanservice2

@lyg116

whycanservice2

@lyg116 你最好检查出大部分的bug再重新打板，否则可能要重新打板很多次。

whycanservice2

@lyg116 PE端口PE-VCC你没给供电，这个端口gpio无法工作！

whycanservice2

@whycanservice2 将下列电容更换为0.1uF：C5 C8 C14 C16 C19 C13 C43 C44 C45 C39 C40
将C90 更换为10uF，R14 更换为10欧姆，R1 更换为3.3k，重要问题，reset引脚下添加0.01-0.1uf的对地RC时间常数去耦电容。至于usb不能连接问题，相关原因较多，主要是确定系统是否稳定启动，usb走线。

whycanservice2

@lyg116 很可能由于之前电压纹波过大，soc已经有损坏迹象了。建议更换soc之后，确保soc之后再做进一步检查。如果可以的话，发热时测试各个主要电源电压，ldo输出电压，与不发热时候做对比，先排查一下。

whycanservice2

@lyg116 安装驱动后重启电脑。

whycanservice2

@lyg116 还有你说的发热热到什么程度？温升大概多少？

whycanservice2

@lyg116 背光电路的FB采样电阻放10k的嘛？一般都是欧姆级的，。。

whycanservice2

@lyg116 三组电源上那个电容都拿掉。。。这跟哪里学来的，人家厂家建议可以有这个加速电容，但也没这么大容值的啊都是pf级的

whycanservice2

@lyg116 上面有个严重错误！！！R2并联的电容是C1 还是C4？容值太大了！！建议拿掉即可！！！

whycanservice2

@lovehex99 这个可以有的。

whycanservice2

@jordonwu 全志A133 跑安卓12.屏幕800*480 样机3.97寸屏无触摸，后面应该是用4.45寸屏带触摸。

whycanservice2

@lovehex99 开源机器，到时候可能会做一些半成品。。或者部件，自己拼装。

whycanservice2

@xiaowenge 尽量做到吧，这是实际设计的3D打印模型渲染，只要精度够就能有这种效果。

whycanservice2

@lyg116 你测量的是wifi芯片的晶振并非soc的。

whycanservice2

@lyg116 芯片手册有说明内部ldo输出带负载能力

whycanservice2

whycanservice2

@lyg116 你在pc上能看到这个说明d1s已经启动工作，但感叹号表示pc上没有驱动。d1s已经工作但是发热厉害说明大概率有硬件问题，检查焊接，检查外设焊接，且注意d1s内部ldo的带负载能力是否超标！

whycanservice2

@a17602198728 此处为保持引脚完整可用，并没有配置一个引脚接入soc，因此并不能动态切换状态，需要软件配置成host或device。而且如果用支持pd模式的充电器供电，误操作cc脚可能会导致烧毁soc。因此本板未配置此功能。

whycanservice2

@wjp2547532 这个问题有硬件部分的问题，也有软件部分的问题。
先说硬件，硬件这部分涉及较多，总的来说简单解决办法是在卡供电与3.3V电源之间串一个2.2R的电阻来解决插入重启的问题。
软件部分是因为这个芯片启动的bios逻辑是优先卡启动，如果在卡中没有找到系统引导则转为检查其他存储设备，这里注意是检查系统引导。这也是后面你格式化了但还是被引导启动了的原因，因为普通格式化仅仅是擦除了卡内的分区信息及文件信息，实际内容并没有擦除。所以依旧可以引导启动，但是又由于分区信息擦除，导致被引导的系统拿不到正确的分区信息，所以又启动失败了。

whycanservice2

@wjp2547532 什么板子？自制的还是开发板？

whycanservice2 发布的帖子