您尚未登录。

#1 Re: 技术人生/软件使用技巧/破解经验/技术吐槽/灌水 » 感觉被套路了 » 2023-12-21 14:09:07

资本家大善人 说:
scuppz 说:

各位前辈和大佬们,怎样才能获得更多的积分?

活跃起来,1回复1积分
发表优质帖子,晕哥给打赏

楼上的,积分还有 小数点

#2 Re: 全志 SOC » 【核桃派】核桃派1B Linux开发板(全志H616) » 2023-12-20 10:54:58

35号技师 说:

H616是好东西,但我发现大家还是更喜欢F1C200S/V3S这些板子

这是因为H616画PCB的要求更高

#3 Re: 工业芯 匠芯创 » RISC-V 相比ARM核,ArtInChip D211系列性能测试大解密,数据供参考。 » 2023-12-08 10:40:27

请问咱们的芯片里面有LVDS接口,这个接口有没有相关的使用说明。

#4 Re: 硬件设计 KiCAD/Protel/DXP/PADS/ORCAD/EAGLE » 求助:在Linux系统下安装和使用Allegro的教程 » 2023-12-06 00:35:06

最终还是在Windows下搞Allegro了,放弃Linux了.现在Linux 下有一些编译器还不错,ST公司有一个自己的工具,我也是刚安装上,感觉还不错.

#6 Re: DIY/综合/Arduino/写字机/3D打印机/智能小车/平衡车/四轴飞行/MQTT/物联网 » 怒开新坑,自制低成本高速USB分析仪(随缘更新) » 2023-11-24 20:15:22

HunanJLR 说:

普通的用BusHound软件抓取数据,HID通信够用了

BusHound的问题是软件驱动要读走数据才能看到,其他的都挺好。

#7 Re: 硬件设计 KiCAD/Protel/DXP/PADS/ORCAD/EAGLE » 求助:在Linux系统下安装和使用Allegro的教程 » 2023-11-16 21:12:05

ArtInChip 说:

@pldjn_V3S

用嘉立创的EDA

试用过了,做了一个LED灯板,感觉做简单的电路可以。

#8 Re: 硬件设计 KiCAD/Protel/DXP/PADS/ORCAD/EAGLE » 求助:在Linux系统下安装和使用Allegro的教程 » 2023-11-16 18:04:31

因为工作的关系平时用一点Linux,装的双系统。公司的管理系统只管到了Windows,所以最近半年一直主力是Linux。本人做一点点软件,主力开发是做硬件,在Windows下的,这不想以后想都搞在Linux下做开发。
Linux的Ui看个人,平时都是用ubuntu感觉还不错了,就是显卡驱动没有Windows下做的好。
其实如果使用LinuxMint的话,基本感觉不出与Windows的UI差别,体验还是很好的,预装的软件也很全,就连ubuntu的显卡驱动问题都不存在。个人感觉太像Windows了,反而有点排斥。
KiCAD吧,前段时间也想学的,系统上也装了,不过在行业内好多人以cadence为标杆,感觉用这个才算是高端的硬件设计。
其实我cadence 和KiCAD都不怎么熟,最熟的是大家都熟的那个软件。

#9 硬件设计 KiCAD/Protel/DXP/PADS/ORCAD/EAGLE » 求助:在Linux系统下安装和使用Allegro的教程 » 2023-11-15 15:22:29

pldjn_V3S
回复: 9

在网上下载了cadence SPB 17.2 linux,尝试着ubuntu安装了以后,不知道怎么设置环境变量,破解了没有完全做好,现在不能通过终端输入allegro &来启动软件,提示是没有这个命令。
有没有在Linux下正确安装和使用的朋友,帮介绍一下怎么安装。

#12 Re: 全志 SOC » 我画了一个f1c200s的sd小系统板,但是sd卡识别不起来,求各位指教!! » 2023-10-31 23:45:26

原理图有问题,TF卡D1上怎么有一个滤波电容 ,另外TF电源有没有做退耦。

#17 Re: 全志 SOC » 请教要怎样才能将 T113 的 UART0 波特率设置成 921600 ? » 2023-06-29 10:26:31

这个波特率最高可以调到多少?有没有测试过是不是可靠,这种几兆bps的通讯,没有找到合适的通讯接口。

#18 Re: 技术人生/软件使用技巧/破解经验/技术吐槽/灌水 » 年近四十的新人,如何快速学会电路设计和制作? » 2023-05-31 09:34:46

45了,工作需要搞FPGA,现在从头开始学习.还没入门,放下了所有的Linux学习来搞FPGA.

#19 Re: 技术人生/软件使用技巧/破解经验/技术吐槽/灌水 » 找个单片机做加密芯片用,有什么推荐的吗? » 2023-05-26 10:52:16

用什么算法,什么机制,想好了可以选不同的芯片,加密芯片可以选U盾里的那些,价格没有2块那么便宜,量少基本3块多点。包括了几乎所有国密安全算法。
所以你最先要做的是先把机制和算法选好。

#20 Xilinx/Altera/FPGA/CPLD/Verilog » 请问,从哪里开始学习Xlinx的光纤通讯,公司要做2.5Gb的光纤通讯,两块板之间的通讯。 » 2023-05-15 23:42:09

pldjn_V3S
回复: 0

自己平时只是对单片机MCU之类 的比较熟,对FPGA没入门,现在公司要做光纤通讯,传输速率2.5Gb,我查到要使用Serdes,具体不太懂,怎么从哪里开始入手系统点的学习。感觉没有头绪。

#23 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-17 19:35:33

在这里再记录一下,临时解决液晶颜色问题,第3种修改RGB到BGR的方法;

由于使用的是buildroot-tiny200,他的液晶驱动还是在uboot里通过参数传到内核的(见下面的代码,chosen)

       chosen {
                #address-cells = <1>;
                #size-cells = <1>;
                ranges;
                //for NAND or Nor
                bootargs = "console=tty0 console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3";
                //for sd-card
//              bootargs = "console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3";
                simplefb_lcd: framebuffer-lcd0 {
                        compatible = "allwinner,simple-framebuffer",
                                     "simple-framebuffer";
                        allwinner,pipeline = "de_be0-lcd0";
                        clocks = <&ccu CLK_BUS_DE_BE>, <&ccu CLK_DE_BE>,
                                 <&ccu CLK_DRAM_DE_BE>, <&ccu CLK_BUS_LCD>,
                                 <&ccu CLK_TCON>;
                        status = "disabled";
                };

我现在还不懂设备树的原理,试过的前两种方法也都没有解决问题,所以就想通过uboot的液晶驱动来改,最终经过分析找到了文件./output/build/uboot-2020.07/arch/arm/include/asm/arch-sunxi/lcdc.h,把文件的第79行,修改成下面这样。临时解决了液晶的颜色问题。

#define SUNXI_LCDC_TCON0_CTRL_ENABLE            ((1 << 31) | (1 << 23))
//#define SUNXI_LCDC_TCON0_CTRL_ENABLE          (1 << 31)

#24 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-16 17:25:46

在这个文件里board/widora/mangopi/r3/devicetree/linux/devicetree.dts 好像是没有使用内核的设备树里驱动LCD。
查了下chosen是从uboot传来的参数。

       chosen {
                #address-cells = <1>;
                #size-cells = <1>;
                ranges;
                //for NAND or Nor
                bootargs = "console=tty0 console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3";
                //for sd-card
//              bootargs = "console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3";
                simplefb_lcd: framebuffer-lcd0 {
                        compatible = "allwinner,simple-framebuffer",
                                     "simple-framebuffer";
                        allwinner,pipeline = "de_be0-lcd0";
                        clocks = <&ccu CLK_BUS_DE_BE>, <&ccu CLK_DE_BE>,
                                 <&ccu CLK_DRAM_DE_BE>, <&ccu CLK_BUS_LCD>,
                                 <&ccu CLK_TCON>;
                        status = "disabled";
                };

#25 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-16 00:51:45

哇酷小二 说:

@pldjn_V3S
我记得这个SDK里面的uboot没有支持lcd,如果确实要支持lcd得试一试荔枝派仓库里面的sdk了。




regmap_update_bits(tcon->regs, SUN4I_TCON0_CTL_REG,BIT(23),BIT(23));//SWAP R、B引脚

在这前后把寄存器值都打印出来看看。

linux/drivers/gpu/drm/sun4i/sun4i_tcon.c这个文件不知道是没有调用到其中的函数 ,还是我加的调试信息不对,我增加了条printk,然后sh rebuild-kernel.sh ,没有在串口上看到信息。

printk("sun4i_tcon.c printk test\n");

#26 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-15 21:32:20

uboot的LCD那个先跳过去了,现在是想把RGB改成GBR,试了2种方法都没有成功。

#27 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-15 20:46:07

@哇酷小二

再问一下怎么修改buildroot,把RGB改成BGR;尝试了2个方法都没成功。
1,参考https://whycan.com/t_6781.html,在文件 linux/drivers/gpu/drm/sun4i/sun4i_tcon.c添加 "regmap_update_bits(tcon->regs, SUN4I_TCON0_CTL_REG,BIT(23),BIT(23));//SWAP R、B引脚" 删除.stamp_built重新编译,没有效果;

2,参考https://gitee.com/IOTTS/f1c100s_buildroot,在文件./board/allwinner/suniv-f1c100s/devicetree/linux/suniv-f1c100s.dtsi中添加 rgb-channel-swap = <1>; /* 设置为1为BGR格式 */ ,重新编译,没有效果;

用busybox修改寄存器的值可以切换BGR,正确显示图片;

busybox devmem 0x01c0c040
busybox devmem 0x01c0c040 w 0x80800100

#28 Re: 全志 SOC » 关于如何将f1c100s/f1c200s linux中将RGB引脚交换为BGR » 2023-02-15 18:21:01

针对buildroot-tiny200,这个应该怎么改?
我在./output/build/linux-5.4.99/drivers/gpu/drm/sun4i/sun4i_tcon.c 文件中修改了,重编译没有起作用。不知道为什么。
用busybox devmem 0x01c0c040 指令去修改寄存器是可以切换的,哪位朋友能提供下具体修改方法。

#29 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-15 16:20:50

@哇酷小二
问一下,uboot那段时间LCD没有显示,直到Starting kernel ...以后LCD上才会有显示,小企鹅也没显示不知道哪里有问题。下面是uboot 的.config文件里的一些配置,看着LCD的部分都选上了,但就是不显示。有没有需要在uboot.defconfig里添加的参数。

......
CONFIG_VIDEO_SUNXI=y
CONFIG_VIDEO_LCD_MODE="x:480,y:272,depth:18,pclk_khz:20000,le:42,ri:8,up:11,lo:4,hs:1,vs:1,sync:3,vmode:0"
CONFIG_VIDEO_LCD_DCLK_PHASE=1
CONFIG_VIDEO_LCD_POWER=""
CONFIG_VIDEO_LCD_RESET=""
CONFIG_VIDEO_LCD_BL_EN=""
CONFIG_VIDEO_LCD_BL_PWM=""
CONFIG_VIDEO_LCD_BL_PWM_ACTIVE_LOW=y
# CONFIG_VIDEO_LCD_PANEL_I2C is not set
CONFIG_VIDEO_LCD_IF_PARALLEL=y
CONFIG_VIDEO_LCD_PANEL_PARALLEL=y
# CONFIG_VIDEO_LCD_PANEL_LVDS is not set
# CONFIG_VIDEO_LCD_PANEL_MIPI_4_LANE_513_MBPS_VIA_SSD2828 is not set
# CONFIG_VIDEO_LCD_PANEL_EDP_4_LANE_1620M_VIA_ANX9804 is not set
# CONFIG_VIDEO_LCD_PANEL_HITACHI_TX18D42VM is not set
# CONFIG_VIDEO_LCD_TL059WV5C0 is not set
......
#
# TrueType Fonts
#
# CONFIG_VIDEO_VESA is not set
# CONFIG_VIDEO_LCD_ANX9804 is not set
# CONFIG_VIDEO_LCD_SSD2828 is not set
# CONFIG_VIDEO_LCD_HITACHI_TX18D42VM is not set
# CONFIG_VIDEO_MVEBU is not set
# CONFIG_I2C_EDID is not set
# CONFIG_DISPLAY is not set
# CONFIG_VIDEO_FSL_DCU_FB is not set
# CONFIG_VIDEO_TEGRA20 is not set
# CONFIG_VIDEO_BRIDGE is not set
CONFIG_VIDEO=y
CONFIG_CFB_CONSOLE=y
# CONFIG_CFB_CONSOLE_ANSI is not set
CONFIG_VGA_AS_SINGLE_DEVICE=y
CONFIG_VIDEO_SW_CURSOR=y
# CONFIG_CONSOLE_EXTRA_INFO is not set
CONFIG_CONSOLE_SCROLL_LINES=1
CONFIG_SYS_CONSOLE_BG_COL=0x00
CONFIG_SYS_CONSOLE_FG_COL=0xa0
# CONFIG_LCD is not set
# CONFIG_VIDEO_SIMPLE is not set
CONFIG_VIDEO_DT_SIMPLEFB=y
# CONFIG_OSD is not set
......

这是现在的config文件
config-bak.txt

#30 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-15 09:29:08

哇酷小二 说:

@pldjn_V3S
buildroot 勾选fbv,就可以用这个命令显示图片了。

液晶还是不正常,没有显示输入的指令,只是显示调试信息这样。

#31 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-14 21:56:40

插了一张TF卡,可以正常挂载了。现在板上的RTC的NS2009没有测试了,但是Linux还是不太正常。液晶还不会显示图片,Linux下的编程还没开始学。

overlayfs:/overlay/rom
                          3072       268      2804   9% /
devtmpfs                 19108         0     19108   0% /dev
/dev/mtdblock3            3072       268      2804   9% /overlay
/dev/root                 5888      5888         0 100% /overlay/rom/lower
devtmpfs                 19108         0     19108   0% /overlay/rom/lower/dev
/dev/mtdblock3            3072       268      2804   9% /overlay/rom/lower/overlay
tmpfs                    27812         0     27812   0% /dev/shm
tmpfs                    27812        20     27792   0% /tmp
tmpfs                    27812        44     27768   0% /run
/dev/mmcblk0p1         3870464       128   3870336   0% /mnt

上个当时加工的时候的gerber文件F1C200S_DIY.zip

#32 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 22:44:03

整理总结一下;

代码默认使用的是Uart1做为log输出,若要修改成Uart0输出需要修改以下几个部分:

1,board/widora/mangopi/r3/uboot.defconfig

    CONFIG_CONS_INDEX=2

2,修改 board\widora\mangopi\r3\devicetree\uboot\suniv-f1c100s-generic.dts的下面这块,改成serial0 = &uart0;就有log输出了;

	aliases {
		serial0 = &uart0;
		spi0 = &spi0;
	};

	chosen {
		stdout-path = "serial0:115200n8";
	};

3, Linux 需要修改 ./board/widora/mangopi/r3/devicetree/linux/devicetree.dts ,增加下面这块,才会有log输出。

&uart0 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart0_pe_pins>;
        status = "okay";
};

 
代码修改成 16M nor spi flash ,需要修改以下几点:
1,需要修改:./board/widora/mangopi/r3/devicetree/linux/devicetree.dts

//for NAND or Nor
  bootargs = "console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs 
  overlayfsdev=/dev/mtdblock3";
//for sd-card
//bootargs = "console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3";

2,Linux的设备树board\widora\mangopi\r3\devicetree\linux\devicetree.dts里 spi-nor@0 部分要把 status = "disabled"  注掉,spi-nand@0 部分要把status = "disabled"加上。

&spi0 {
	status = "okay";

	spi-nor@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "winbond,w25q128", "jedec,spi-nor";
		reg = <0>;
		spi-max-frequency = <50000000>;
	//	status = "disabled";

		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x70000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x70000 0x590000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x700000>;
				read-only;
			};

			partition@3 {
				label = "overlay";
				reg = <0xd00000 0x300000>;
			};
		};
	};

	spi-nand@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "spi-nand";
		reg = <0>;
		spi-max-frequency = <50000000>;
                status = "disabled";
		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x100000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x100000 0x500000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x2a00000>;
				read-only;
			};

			partition@3 {
				label = "vendor";
				reg = <0x3000000 0x1000000>;
			};

			partition@4 {
				label = "overlay";
				reg = <0x4000000 0x3000000>;
			};
		};
	};
};

#33 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 21:01:39

找到问题原因了,还是Linux的设备树board\widora\mangopi\r3\devicetree\linux\devicetree.dts里 spi-nor@0 要把 status = "disabled"  注掉;

&spi0 {
	status = "okay";

	spi-nor@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "winbond,w25q128", "jedec,spi-nor";
		reg = <0>;
		spi-max-frequency = <50000000>;
		status = "disabled";

		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x70000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x70000 0x590000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x700000>;
				read-only;
			};

			partition@3 {
				label = "overlay";
				reg = <0xd00000 0x300000>;
			};
		};
	};

	spi-nand@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "spi-nand";
		reg = <0>;
		spi-max-frequency = <50000000>;

		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x100000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x100000 0x500000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x2a00000>;
				read-only;
			};

			partition@3 {
				label = "vendor";
				reg = <0x3000000 0x1000000>;
			};

			partition@4 {
				label = "overlay";
				reg = <0x4000000 0x3000000>;
			};
		};
	};
};
在线

全部的log,现在可以进shell了。

U-Boot SPL 2020.07 (Feb 13 2023 - 16:11:47 +0800)
DRAM: 64 MiB
Trying to boot from MMC1
Card did not respond to voltage select!
spl: mmc init failed with error: -95
Trying to boot from MMC2
Card did not respond to voltage select!
spl: mmc init failed with error: -95
Trying to boot from sunxi SPI


U-Boot 2020.07 (Feb 13 2023 - 16:11:47 +0800) Allwinner Technology

CPU:   Allwinner F Series (SUNIV)
Model: Allwinner F1C100s Generic Device
DRAM:  64 MiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Setting up a 800x480 lcd console (overscan 0x0)
In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
Card did not respond to voltage select!
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
=========================
Boot Device: spi
Boot Slot 0: empty
Boot Slot 1: spi-nor
=========================
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
device 0 offset 0x80000, size 0x80000
SF: 524288 bytes @ 0x80000 Read: OK
Unknown command 'bmp' - try 'help'
gpio - query and control gpio pins

Usage:
gpio <input|set|clear|toggle> <pin>
    - input/set/clear/toggle the specified pin
gpio status [-a] [<bank> | <pin>]  - show [all/claimed] GPIOs
DFU waiting on SPI-NOR...
musb-hdrc: peripheral reset irq lost!
Booting from SPI-NOR...
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
device 0 offset 0x100000, size 0x500000
SF: 5242880 bytes @ 0x100000 Read: OK
## Loading kernel from FIT Image at 81000000 ...
   Using 'conf@0' configuration
   Trying 'kernel@0' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x810000cc
     Data Size:    4309768 Bytes = 4.1 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x80000000
     Entry Point:  0x80000000
     Hash algo:    crc32
     Hash value:   4bfebdc8
   Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 81000000 ...
   Using 'conf@0' configuration
   Trying 'fdt@0' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x8141c4b8
     Data Size:    15714 Bytes = 15.3 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   9ff3b1b8
   Verifying Hash Integrity ... crc32+ OK
   Booting using the fdt blob at 0x8141c4b8
   Loading Kernel Image
   Loading Device Tree to 817f9000, end 817ffd61 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.99 (zl@ubuntu) (gcc version 8.4.0 (Buildroot -g4a14fb0-dirty)) #1 Mon Feb 13 17:40:57 CST 2023
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=0005317f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Widora MangoPi R3
[    0.000000] Memory policy: Data cache writeback
[    0.000000] cma: Reserved 16 MiB at 0x82c00000
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 15883
[    0.000000] Kernel command line: console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3 net.ifnames=0 vt.global_cursor_default=0
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 37232K/64036K available (6144K kernel code, 248K rwdata, 1676K rodata, 1024K init, 225K bss, 10420K reserved, 16384K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x254/0x444 with crng_init=0
[    0.000051] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000142] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000899] Console: colour dummy device 80x30
[    0.001004] Calibrating delay loop... 203.16 BogoMIPS (lpj=1015808)
[    0.070267] pid_max: default: 32768 minimum: 301
[    0.070803] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.070855] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.072831] CPU: Testing write buffer coherency: ok
[    0.074972] Setting up static identity map for 0x80100000 - 0x80100058
[    0.076286] devtmpfs: initialized
[    0.088117] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.088185] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.092488] pinctrl core: initialized pinctrl subsystem
[    0.095188] NET: Registered protocol family 16
[    0.098948] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.101308] cpuidle: using governor menu
[    0.142663] SCSI subsystem initialized
[    0.143037] usbcore: registered new interface driver usbfs
[    0.143195] usbcore: registered new interface driver hub
[    0.143354] usbcore: registered new device driver usb
[    0.143839] mc: Linux media interface: v0.10
[    0.143964] videodev: Linux video capture interface: v2.00
[    0.144081] pps_core: LinuxPPS API ver. 1 registered
[    0.144100] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.144157] PTP clock support registered
[    0.145261] ion_parse_dt_heap_common: id 4 type 4 name cma align 1000
[    0.146215] Advanced Linux Sound Architecture Driver Initialized.
[    0.148647] clocksource: Switched to clocksource timer
[    0.150609] simple-framebuffer 83e89000.framebuffer: framebuffer at 0x83e89000, 0x177000 bytes, mapped to 0x(ptrval)
[    0.150669] simple-framebuffer 83e89000.framebuffer: format=x8r8g8b8, mode=800x480x32, linelength=3200
[    0.177459] Console: switching to colour frame buffer device 100x30
[    0.202721] simple-framebuffer 83e89000.framebuffer: fb0: simplefb registered!
[    0.233211] thermal_sys: Registered thermal governor 'step_wise'
[    0.233945] NET: Registered protocol family 2
[    0.235541] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.235629] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.235686] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.235737] TCP: Hash tables configured (established 1024 bind 1024)
[    0.236052] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.236117] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.236669] NET: Registered protocol family 1
[    0.239606] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.241436] Initialise system trusted keyrings
[    0.242048] workingset: timestamp_bits=30 max_order=14 bucket_order=0
[    0.264106] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.264738] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.382897] Key type asymmetric registered
[    0.382940] Asymmetric key parser 'x509' registered
[    0.383117] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.383146] io scheduler mq-deadline registered
[    0.383164] io scheduler kyber registered
[    0.398379] suniv-f1c100s-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    0.422283] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    0.428416] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pe not found, using dummy regulator
[    0.429915] printk: console [ttyS0] disabled
[    0.450248] 1c25000.serial: ttyS0 at MMIO 0x1c25000 (irq = 26, base_baud = 6250000) is a 16550A
[    0.916781] printk: console [ttyS0] enabled
[    0.922184] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pa not found, using dummy regulator
[    0.954121] 1c25400.serial: ttyS1 at MMIO 0x1c25400 (irq = 27, base_baud = 6250000) is a 16550A
[    0.974026] SCSI Media Changer driver v0.25 
[    0.980097] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator
[    0.993446] spi-nor spi0.0: w25q128 (16384 Kbytes)
[    0.999616] 4 fixed-partitions partitions found on MTD device spi0.0
[    1.005979] Creating 4 MTD partitions on "spi0.0":
[    1.010939] 0x000000000000-0x000000070000 : "u-boot"
[    1.019746] 0x000000070000-0x000000600000 : "kernel"
[    1.028301] 0x000000600000-0x000000d00000 : "rom"
[    1.036923] 0x000000d00000-0x000001000000 : "overlay"
[    1.046241] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.052912] ehci-platform: EHCI generic platform driver
[    1.058542] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.064875] ohci-platform: OHCI generic platform driver
[    1.070683] usbcore: registered new interface driver usb-storage
[    1.077734] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[    1.091612] i2c /dev entries driver
[    1.095769] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator
[    1.109770] suniv-f1c100s-pinctrl 1c20800.pinctrl: pin PE0 already requested by 1c25000.serial; cannot claim for 1cb0000.csi
[    1.121100] suniv-f1c100s-pinctrl 1c20800.pinctrl: pin-128 (1cb0000.csi) status -22
[    1.128818] suniv-f1c100s-pinctrl 1c20800.pinctrl: could not request pin 128 (PE0) from group PE0  on device 1c20800.pinctrl
[    1.140050] sun4i-csi 1cb0000.csi: Error applying setting, reverse things back
[    1.147316] sun4i-csi: probe of 1cb0000.csi failed with error -22
[    1.155033] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[    1.165148] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pf not found, using dummy regulator
[    1.203560] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[    1.212947] usbcore: registered new interface driver usbhid
[    1.218525] usbhid: USB HID core driver
[    1.222835] sunxi-cedar 1c0e000.video-codec: sunxi cedar version 0.01alpha
[    1.230153] sunxi-cedar 1c0e000.video-codec: cedar-ve the get irq is 19
[    1.242273] debugfs: Directory '1c23c00.codec' with parent 'F1C100s Audio Codec' already present!
[    1.257496] sun4i-codec 1c23c00.codec: Codec <-> 1c23c00.codec mapping ok
[    1.273803] NET: Registered protocol family 17
[    1.278367] Key type dns_resolver registered
[    1.284033] Loading compiled-in X.509 certificates
[    1.302234] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    1.320389] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    1.327171] ALSA device list:
[    1.330279]   #0: F1C100s Audio Codec
[    1.334557] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.343320] cfg80211: failed to load regulatory.db
[    1.353259] random: fast init done
[    1.359101] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    1.372413] devtmpfs: mounted
[    1.380847] Freeing unused kernel memory: 1024K
[    1.385502] Run /preinit as init process
[    1.632357] random: crng init done
[    2.406852] overlayfs: upper fs does not support tmpfile.
[    2.412419] overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off.
Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev: [    3.253577] udevd[90]: starting version 3.2.9
[    3.466169] udevd[91]: starting eudev-3.2.9
[    5.398168] Goodix-TS 0-005d: 0-005d supply AVDD28 not found, using dummy regulator
[    5.406217] Goodix-TS 0-005d: 0-005d supply VDDIO not found, using dummy regulator
[    7.448769] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    9.528765] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    9.535441] Goodix-TS 0-005d: i2c test failed attempt 1: -110
[   11.608849] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   13.688786] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   13.695393] Goodix-TS 0-005d: i2c test failed attempt 2: -110
[   13.738803] Goodix-TS 0-005d: I2C communication failure: -110
[   13.744968] Goodix-TS: probe of 0-005d failed with error -110
[   15.768785] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   17.848774] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   19.928764] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   19.935332] ov2640 0-0030: Product ID error 92:92
done
Initializing random number generator: OK
Saving random seed: OK
Starting haveged: haveged: listening socket at 3
OK
Starting network: OK
Starting uMTPrd: [   21.621279] file system registered
[   21.975004] read descriptors
[   21.977964] read strings
OK

Welcome to Widora MangoPi R3
mangopi-r3 login: [   23.244353] configfs-gadget gadget: high-speed config #1: c
[   31.848736] vcc3v0: disabling
[   31.851739] vcc3v3: disabling
[   31.854708] vcc5v0: disabling

Welcome to Widora MangoPi R3
mangopi-r3 login: 
Welcome to Widora MangoPi R3
mangopi-r3 login: root
# ls
# ls
# 

#34 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 20:31:43

哇酷小二 说:

改完 uboot.env 要重新编译uboot :

rm output/build/uboot-2020.07/ -rf && make

这个不是从uboot.env文件获取的参数,是直接写死到Linux的设备树文件里的。在这个文件里./board/widora/mangopi/r3/devicetree/linux/devicetree.dts,这里为什么nor是root=/dev/mtdblock2,而sd卡是root=/dev/mmcblk0p3。

  //for NAND or Nor
  bootargs = "console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3";
  //for sd-card
  //bootargs = "console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3";

#35 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 17:16:32

@哇酷小二
修改完,linux没有进shell,不知道是哪个设备出问题了;

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.99 (zl@ubuntu) (gcc version 8.4.0 (Buildroot -g4a14fb0-dirty)) #1 Mon Feb 13 14:46:20 CST 2023
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=0005317f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Widora MangoPi R3
[    0.000000] Memory policy: Data cache writeback
[    0.000000] cma: Reserved 16 MiB at 0x82c00000
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 15883
[    0.000000] Kernel command line: console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3 net.ifnames=0 vt.global_cursor_default=0
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 37232K/64036K available (6144K kernel code, 248K rwdata, 1676K rodata, 1024K init, 225K bss, 10420K reserved, 16384K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x254/0x444 with crng_init=0
[    0.000049] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000143] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000901] Console: colour dummy device 80x30
[    0.001007] Calibrating delay loop... 203.16 BogoMIPS (lpj=1015808)
[    0.070265] pid_max: default: 32768 minimum: 301
[    0.070778] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.070821] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.072678] CPU: Testing write buffer coherency: ok
[    0.074829] Setting up static identity map for 0x80100000 - 0x80100058
[    0.076136] devtmpfs: initialized
[    0.087867] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.087933] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.092160] pinctrl core: initialized pinctrl subsystem
[    0.094857] NET: Registered protocol family 16
[    0.098552] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.100885] cpuidle: using governor menu
[    0.142142] SCSI subsystem initialized
[    0.142527] usbcore: registered new interface driver usbfs
[    0.142688] usbcore: registered new interface driver hub
[    0.142851] usbcore: registered new device driver usb
[    0.143347] mc: Linux media interface: v0.10
[    0.143478] videodev: Linux video capture interface: v2.00
[    0.143595] pps_core: LinuxPPS API ver. 1 registered
[    0.143614] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.143676] PTP clock support registered
[    0.144725] ion_parse_dt_heap_common: id 4 type 4 name cma align 1000
[    0.145608] Advanced Linux Sound Architecture Driver Initialized.
[    0.147947] clocksource: Switched to clocksource timer
[    0.149770] simple-framebuffer 83e89000.framebuffer: framebuffer at 0x83e89000, 0x177000 bytes, mapped to 0x(ptrval)
[    0.149830] simple-framebuffer 83e89000.framebuffer: format=x8r8g8b8, mode=800x480x32, linelength=3200
[    0.176789] Console: switching to colour frame buffer device 100x30
[    0.202033] simple-framebuffer 83e89000.framebuffer: fb0: simplefb registered!
[    0.232698] thermal_sys: Registered thermal governor 'step_wise'
[    0.233466] NET: Registered protocol family 2
[    0.235049] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.235132] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.235195] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.235246] TCP: Hash tables configured (established 1024 bind 1024)
[    0.235575] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.235655] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.236210] NET: Registered protocol family 1
[    0.238850] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.240708] Initialise system trusted keyrings
[    0.241361] workingset: timestamp_bits=30 max_order=14 bucket_order=0
[    0.263449] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.264071] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.375350] Key type asymmetric registered
[    0.375393] Asymmetric key parser 'x509' registered
[    0.375582] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.375609] io scheduler mq-deadline registered
[    0.375626] io scheduler kyber registered
[    0.391076] suniv-f1c100s-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    0.414967] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    0.421314] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pe not found, using dummy regulator
[    0.422577] printk: console [ttyS0] disabled
[    0.442902] 1c25000.serial: ttyS0 at MMIO 0x1c25000 (irq = 26, base_baud = 6250000) is a 16550A
[    0.906327] printk: console [ttyS0] enabled
[    0.911715] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pa not found, using dummy regulator
[    0.943705] 1c25400.serial: ttyS1 at MMIO 0x1c25400 (irq = 27, base_baud = 6250000) is a 16550A
[    0.963598] SCSI Media Changer driver v0.25 
[    0.969686] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator
[    0.988383] random: fast init done
[    1.378267] spi-nand: probe of spi0.0 failed with error -110
[    1.384516] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.391166] ehci-platform: EHCI generic platform driver
[    1.396784] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.403168] ohci-platform: OHCI generic platform driver
[    1.408984] usbcore: registered new interface driver usb-storage
[    1.415990] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[    1.429918] i2c /dev entries driver
[    1.434062] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator
[    1.447880] suniv-f1c100s-pinctrl 1c20800.pinctrl: pin PE0 already requested by 1c25000.serial; cannot claim for 1cb0000.csi
[    1.459240] suniv-f1c100s-pinctrl 1c20800.pinctrl: pin-128 (1cb0000.csi) status -22
[    1.466901] suniv-f1c100s-pinctrl 1c20800.pinctrl: could not request pin 128 (PE0) from group PE0  on device 1c20800.pinctrl
[    1.478150] sun4i-csi 1cb0000.csi: Error applying setting, reverse things back
[    1.485418] sun4i-csi: probe of 1cb0000.csi failed with error -22
[    1.493059] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[    1.503132] suniv-f1c100s-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pf not found, using dummy regulator
[    1.541507] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[    1.550975] usbcore: registered new interface driver usbhid
[    1.556556] usbhid: USB HID core driver
[    1.560838] sunxi-cedar 1c0e000.video-codec: sunxi cedar version 0.01alpha
[    1.568222] sunxi-cedar 1c0e000.video-codec: cedar-ve the get irq is 19
[    1.580324] debugfs: Directory '1c23c00.codec' with parent 'F1C100s Audio Codec' already present!
[    1.595518] sun4i-codec 1c23c00.codec: Codec <-> 1c23c00.codec mapping ok
[    1.612276] NET: Registered protocol family 17
[    1.616838] Key type dns_resolver registered
[    1.622332] Loading compiled-in X.509 certificates
[    1.640501] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    1.658588] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    1.665370] ALSA device list:
[    1.668472]   #0: F1C100s Audio Codec
[    1.672724] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.681477] cfg80211: failed to load regulatory.db
[    1.687384] Waiting for root device /dev/mmcblk0p3...
[   26.798104] random: crng init done
[   31.848004] vcc3v0: disabling
[   31.851004] vcc3v3: disabling
[   31.853970] vcc5v0: disabling

追加:
  分析可能是Waiting for root device /dev/mmcblk0p3...有问题,这里怎么是mmcblk0p3,
 
这块需要修改:./board/widora/mangopi/r3/devicetree/linux/devicetree.dts

  //for NAND or Nor
  bootargs = "console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3";
  //for sd-card
  //bootargs = "console=ttyS0,115200 earlyprintk rootwait init=/preinit root=/dev/mmcblk0p3";

修改完了还是不行,不知道啥原因。还是卡在这块。

[    1.674673] ALSA device list:
[    1.677662]   #0: F1C100s Audio Codec
[    1.682097] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.690867] cfg80211: failed to load regulatory.db
[    1.696482] Waiting for root device /dev/mtdblock2...
[   23.388435] random: crng init done
[   31.848374] vcc3v0: disabling
[   31.851375] vcc3v3: disabling
[   31.854343] vcc5v0: disabling

#36 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 16:38:21

哇酷小二 说:

@pldjn_V3S
对,改设备树。


改完设备树, 有一个快速编译的方法:

rm output/build/linux-5.4.66/.stamp_built -rf && make

这样就能重新生成linux 设备树二进制文件了.


uboot亦然.

试了,修改 board\widora\mangopi\r3\devicetree\uboot\suniv-f1c100s-generic.dts的下面这块,改成serial0 = &uart0;就有了;Linux的还是没有,到了Starting kernel ...␍␊就停了。

	aliases {
		serial0 = &uart0;
		spi0 = &spi0;
	};

	chosen {
		stdout-path = "serial0:115200n8";
	};

Linux 需要修改 ./board/widora/mangopi/r3/devicetree/linux/devicetree.dts ,增加下面这块,才会有log输出。

&uart0 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart0_pe_pins>;
        status = "okay";
};

#38 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 15:59:10

哇酷小二 说:

@pldjn_V3S

uboot 串口

改这个:
board/widora/mangopi/r3/uboot.defconfig

CONFIG_CONS_INDEX=2



然后删除uboot的编译目录:
rm output/build/uboot-2020.07/ -rf

重新make即可。

这样改过以后,确实有了log输出,uboot的前一半有了,后一半没出来。后一半是不是需要修改设备树;一会再去修改了试试先。

[15:46:31:768] ␍␊
[15:46:31:768] U-Boot SPL 2020.07 (Feb 13 2023 - 14:44:13 +0800)␍␊
[15:46:31:803] DRAM: 64 MiB␍␊
[15:46:31:803] Trying to boot from MMC1␍␊
[15:46:31:803] Card did not respond to voltage select!␍␊
[15:46:31:803] spl: mmc init failed with error: -95␍␊
[15:46:31:804] Trying to boot from MMC2␍␊
[15:46:31:818] Card did not respond to voltage select!␍␊
[15:46:31:820] spl: mmc init failed with error: -95␍␊
[15:46:31:823] Trying to boot from sunxi SPI␍␊

#39 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-13 13:35:44

研究了2天时间,不如你一句话,唉,要学的太多。

#40 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-12 15:38:54

@哇酷小二

修改F1C200S的uboot,console接口,都要改哪些 地方,我按照坛里的帖子修改了几个地,还是没有输出到uart0上。第3项我没找到声明的地方,不知道是什么原因;

1, board\widora\mangopi\r3\devicetree\uboot\suniv-f1c100s-generic.dts

	aliases {
		serial0 = &uart0;
		spi0 = &spi0;
	};

	chosen {
		stdout-path = "serial0:115200n8";
	};
&uart0 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart0_pins_a>;
        status = "okay";
};

&uart1 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart1_pins_a>;
        status = "okay";
};

2,board\allwinner\suniv-f1c100s\devicetree\uboot\suniv-f1c100s.dtsi

                        uart0_pins_a: uart-pins-pe {
                                pins = "PE0", "PE1";
                                function = "uart0";
                        };

                        uart1_pins_a: uart1-pins-pa {
                                pins = "PA2", "PA3";
                                function = "uart1";
                        };
                uart0: serial@1c25000 {
                        compatible = "snps,dw-apb-uart";
                        reg = <0x01c25000 0x400>;
                        interrupts = <1>;
                        reg-shift = <2>;
                        reg-io-width = <4>;
                        clocks = <&ccu CLK_BUS_UART0>;
                        resets = <&ccu RST_BUS_UART0>;
                        status = "disabled";
                };

                uart1: serial@1c25400 {
                        compatible = "snps,dw-apb-uart";
                        reg = <0x01c25400 0x400>;
                        interrupts = <2>;
                        reg-shift = <2>;
                        reg-io-width = <4>;
                        clocks = <&ccu CLK_BUS_UART1>;
                        resets = <&ccu RST_BUS_UART1>;
                        status = "disabled";
                };

3, 这块未找到,在文件/output/build/uboot-2020.07/include/configs/sunxi-common.h中没有找到CONFIG_CONS_INDEX这块的定义。

#define CONFIG_CONS_INDEX              1       /* UART0 */

4,uboot的.config中添加

CONFIG_BOOTARGS="console=ttyS0,115200 rootwait init=/preinit root=/dev/mtdblock2 rootfstype=squashfs overlayfsdev=/dev/mtdblock3"

#41 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-12 00:16:22

我在mangopi 的官网下载了一个sysimage-nor的镜像,烧到我的板上,也是没有跑起来系统,串口没有Log,液晶有显示uboot的log,进入了Linux系统,不知道为什么液晶没有显示。
不过可以确认的是,他的log不是从uart0输出的。
所以如果再搞两天还是搞不定这个的话,只能去试试mangopi R3的那版buildroot

改正一下:
看到了,原来mangopi R1的串口是uart0,R3的就默认是uart1了。

#42 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-11 23:30:54

哇酷小二 说:

都在这个文件里面:widora_mangopi_r3_defconfig

当执行 make widora_mangopi_r3_defconfig,就把这个文件复制到 .config

我之前测试好像是没有写,而且报出来的Log里也没有提到。

make widora_mangopi_r3_defconfig

mkdir -p /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/lxdialog
PKG_CONFIG_PATH="" make CC="/usr/bin/gcc" HOSTCC="/usr/bin/gcc" \
    obj=/home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config -C support/kconfig -f Makefile.br conf
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE  -I/home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config -DCONFIG_=\"\"  -MM *.c > /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/.depend 2>/dev/null || :
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE  -I/home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config -DCONFIG_=\"\"   -c conf.c -o /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/conf.o
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE  -I/home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config -DCONFIG_=\"\"  -I. -c /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/zconf.tab.c -o /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/zconf.tab.o
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE  -I/home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config -DCONFIG_=\"\"   /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/conf.o /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/zconf.tab.o  -o /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/conf
rm /home/zl/f1c200s/buildroot-tiny200/output/build/buildroot-config/zconf.tab.c
#
# configuration written to /home/zl/f1c200s/buildroot-tiny200/.config
#

#43 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-11 23:18:19

@哇酷小二
再问下,这个SDK里,uboot.defconfig、linux.defconfig是什么时候写到对应的.config文件中的?
执行 make widora_mangopi_r3_defconfig 的时候,并没有把uboot.defconfig、linux.defconfig连带着写了。

#44 Re: 全志 SOC » F1C100S USB口改为TYPE-C口引发的问题? » 2023-02-11 23:14:30

@dykxjh
增加使能控制Pin脚,使能U盘输出 。

#45 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-11 21:19:55

哇酷小二 说:

没有超过,_addr 是内存地址, 起始地址是 0x8000,0000


offset 是flash 偏移地址,取值范围 0 - 16M

在buildroot-tiny200\board\widora\mangopi\r3\devicetree\linux\devicetree.dts文件里spi-nor、spi-nand的分区配置是不一样的,而uboot.env的这个文件里只有一套分区地址设置,不知道是不是这块有问题。我按照spi-nand的参数配置了spi-nor 的分区,一样没启动,不知道为什么。

&spi0 {
	status = "okay";

	spi-nor@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "winbond,w25q128", "jedec,spi-nor";
		reg = <0>;
		spi-max-frequency = <50000000>;
		status = "disabled";

		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x70000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x70000 0x590000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x700000>;
				read-only;
			};

			partition@3 {
				label = "overlay";
				reg = <0xd00000 0x300000>;
			};
		};
	};

	spi-nand@0 {
		#address-cells = <1>;
		#size-cells = <1>;
		compatible = "spi-nand";
		reg = <0>;
		spi-max-frequency = <50000000>;

		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			partition@0 {
				label = "u-boot";
				reg = <0x000000 0x100000>;
				read-only;
			};

			partition@1 {
				label = "kernel";
				reg = <0x100000 0x500000>;
				read-only;
			};

			partition@2 {
				label = "rom";
				reg = <0x600000 0x2a00000>;
				read-only;
			};

			partition@3 {
				label = "vendor";
				reg = <0x3000000 0x1000000>;
			};

			partition@4 {
				label = "overlay";
				reg = <0x4000000 0x3000000>;
			};
		};
	};
};

#46 Re: 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-11 14:08:18

哇酷小二 说:

1. 可能是把 uart1 连接到 /dev/ttyS0 这个设备,纯属猜测。

2. 遍历所有启动介质,哪个正常就从那个介质启动

2,这项感觉用这几个参数,超出了16Mspiflash的空间了。是参数错了吗

#47 全志 SOC » 请教buildroot-tiny200和run distro_bootcmd里的一些问题 » 2023-02-11 00:23:03

pldjn_V3S
回复: 27

我准备使用buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND 给我的F1C200S小板编译Linux固件,遇到一些问题,特开贴请教。
1,我编译的固件烧录到芯片,串口没有信息输出,不知道是不是与DTS文件中的 serial0 = &uart1 有关,为什么这里要把uart1给serial0;
   

/dts-v1/;
#include "suniv-f1c100s.dtsi"

#include <dt-bindings/gpio/gpio.h>

/ {
        model = "Allwinner F1C100s Generic Device";
        compatible = "allwinner,suniv-f1c100s",
                     "allwinner,suniv";
        aliases {
                serial0 = &uart1;
                spi0 = &spi0;
        };

        chosen {
                stdout-path = "serial0:115200n8";
        };
};

2,  在uboot.env中为什么这些值都那么大?
          sf_size=0x1000000
          sf_splash_offset=0x80000
          sf_kernel_offset=0x100000
          sf_kernel_length=0x500000

          splash_addr=0x80000000
          splash_length=0x80000

          kernel_addr_r=0x81000000

          bootm_size=0x1800000
按照下面这行,那bootcomv好像不适合SPI Flash ,也不知道自己的理解对不对。

nor_boot=echo "Booting from SPI-NOR..."; sf probe; sf read ${kernel_addr_r} ${sf_kernel_offset} ${sf_kernel_length};

为了方便我把/board/allwinner/generic/uboot.env文件的内容贴出来;

mmc_kernel=kernel.itb
mmc_splash=splash.bmp
mmc_ubootpart=1
mmc_bootpart=2
mmc_rootpart=3

nand_size=0x8000000
nand_splash_offset=0x80000
nand_kernel_offset=0x100000
nand_kernel_length=0x500000

sf_size=0x1000000
sf_splash_offset=0x80000
sf_kernel_offset=0x100000
sf_kernel_length=0x500000

splash_addr=0x80000000
splash_length=0x80000

kernel_addr_r=0x81000000

bootm_size=0x1800000

stderr=serial
stdin=serial
stdout=serial

boot_slot_0=empty
boot_slot_1=empty
scan_boot_slot_0=if mmc dev 0; then setenv boot_slot_0 mmc0; fi;
scan_boot_slot_1=if mmc dev 1; then setenv boot_slot_1 mmc1; else if sf probe; then setenv boot_slot_1 spi-nor; else if mtd list; then setenv boot_slot_1 spi-nand; fi; fi; fi;
scan_boot_slot=run scan_boot_slot_0; run scan_boot_slot_1; echo "========================="; echo "Boot Device: ${boot_device}"; echo "Boot Slot 0: ${boot_slot_0}"; echo "Boot Slot 1: ${boot_slot_1}"; echo "=========================";

dfu_wait_timeout=3
mmc_dfu_info=setenv dfu_alt_info "all raw 0x0 0x37000;u-boot raw 0x10 0x7f0;boot part ${dfu_mmc_dev} ${mmc_bootpart};rom part ${dfu_mmc_dev} ${mmc_rootpart};kernel fat ${dfu_mmc_dev} ${mmc_bootpart}"
nand_dfu_info=setenv dfu_alt_info "all raw 0x0 ${nand_size};u-boot raw 0x0 0x80000;kernel raw ${nand_kernel_offset} ${nand_kernel_length};rom raw 0x600000 0x2a00000;vendor raw 0x3000000 0x1000000"
nor_dfu_info=setenv dfu_alt_info "all raw 0x0 ${sf_size};u-boot raw 0x0 0x80000;kernel raw ${sf_kernel_offset} ${sf_kernel_length};rom raw 0x600000 0x700000"
dfu_mmc=mmc dev ${dfu_mmc_dev}; run mmc_dfu_info; dfu 0 mmc ${dfu_mmc_dev} ${dfu_wait_timeout};
dfu_nand=run nand_dfu_info; dfu 0 mtd spi-nand0 ${dfu_wait_timeout};
dfu_nor=run nor_dfu_info; dfu 0 sf 0:0 ${dfu_wait_timeout};
dfu_boot=if test "${boot_slot_1}" = "spi-nand"; then echo "DFU waiting on SPI-NAND..."; run dfu_nand; fi; if test "${boot_slot_1}" = "spi-nor"; then echo "DFU waiting on SPI-NOR..."; run dfu_nor; fi; if test "${boot_slot_1}" = "mmc1"; then echo "DFU waiting on MMC1..."; setenv dfu_mmc_dev 1; run dfu_mmc; fi; if test "${boot_slot_1}" = "empty" && test "${boot_slot_0}" = "mmc0"; then echo "DFU waiting on MMC0..."; setenv dfu_mmc_dev 0; run dfu_mmc; fi;

fel_boot=echo "Booting from FEL..."; bootm ${kernel_addr_r};
mmc_boot=mmc dev ${devnum}; echo "Booting from MMC${devnum}..."; load mmc ${devnum}:${mmc_bootpart} $kernel_addr_r ${mmc_kernel}; bootm ${kernel_addr_r};
nor_nand_boot=if test "${boot_slot_1}" = "spi-nor"; then run nor_boot; fi; if test "${boot_slot_1}" = "spi-nand"; then run nand_boot; fi;
nor_boot=echo "Booting from SPI-NOR..."; sf probe; sf read ${kernel_addr_r} ${sf_kernel_offset} ${sf_kernel_length}; bootm ${kernel_addr_r};
nand_boot=echo "Booting from SPI-NAND..."; mtd read spi-nand0 ${kernel_addr_r} ${nand_kernel_offset} ${nand_kernel_length}; bootm ${kernel_addr_r};

bootcmd_fel=if test "${boot_device}" = "fel"; then run fel_boot; fi;
bootcmd_dfu=if test "${boot_device}" != "mmc0" || test "${boot_slot_1}" = "empty"; then run dfu_boot; fi;
bootcmd_mmc0=if test "${boot_device}" = "mmc0"; then devnum=0; run mmc_boot; fi;
bootcmd_mmc1=if test "${boot_device}" = "mmc1"; then devnum=1; run mmc_boot; fi;
bootcmd_spi=if test "${boot_device}" = "spi"; then run nor_nand_boot; fi;


boot_targets=fel dfu mmc0 mmc1 spi loopdfu

splash_nor=sf probe; sf read ${splash_addr} ${sf_splash_offset} ${splash_length};
splash_nand=mtd read spi-nand0 ${splash_addr} ${nand_splash_offset} ${splash_length};
splash_spi=if test "${boot_slot_1}" = "spi-nor"; then run splash_nor; fi; if test "${boot_slot_1}" = "spi-nand"; then run splash_nand; fi;
splash_mmc=load mmc ${devnum}:${mmc_bootpart} ${splash_addr} ${mmc_splash};
show_splash=run splash_${boot_device}; bmp display ${splash_addr}; gpio set ${lcd_bl_pin};

distro_bootcmd=run scan_boot_slot; run show_splash; for target in ${boot_targets}; do run bootcmd_${target}; done

#48 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-10 17:47:23

@哇酷小二
问一下晕哥:

board/widora/mangopi/r3/devicetree/uboot/suniv-f1c100s-generic.dts里的这段serial0 = &uart1;会影响到串口0的输出吗?

/dts-v1/;
#include "suniv-f1c100s.dtsi"

#include <dt-bindings/gpio/gpio.h>

/ {
	model = "Allwinner F1C100s Generic Device";
	compatible = "allwinner,suniv-f1c100s",
		     "allwinner,suniv";

	aliases {
		serial0 = &uart1;
		spi0 = &spi0;
	};

	chosen {
		stdout-path = "serial0:115200n8";
	};
};

#49 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-10 17:26:32

@哇酷小二
我今天试着读了一下写到芯片内的u-boot进行了对比,发现写进去与读出的是一样的,但这个bin文件并没有正常的串口信息输出,看不到uboot是否运行。
不知道有哪个设置会影响uboot的运行,按说设置了ARM及内核926,uboot就应该会在芯片上跑起来。
make widora_mangopi_r3_defconfig
应该会把基本配置写到.config文件里面去吧。
我看了一下mangopi r3的原理,console的串口应该也是uart0,实在不知道是哪里出了问题,还有哪里会影响uboot。

-rw-r--r-- 1 root   root     431378  2月 10 16:44 uboo-read.bin
-rw-r--r-- 1 zl zl  431378  2月 10 16:38 u-boot-sunxi-with-spl.bin
zl@zl-System-Product-Name:~/buildroot-image$ diff uboo-read.bin u-boot-sunxi-with-spl.bin 
zl@zl-System-Product-Name:~/buildroot-image$ 

#50 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-10 11:56:09

今天发现电流稍大一点的那块板子,原来是焊接问题,不是CPU短路,而是LCD的座子那块焊短路了。修复后焊接正常了。接下来还是要研究系统软件。

#52 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-08 16:07:05

@哇酷小二
@aodzip 的SDK我使用16M的W25Q128,一直不能正确的跑起Uboot,自己新手,这个问题解决不了,所以翻回头来搞这个能跑起来的代码,先把板子上能测的部分测试一下。后面再研究aodzip 的SDK。
现在是板上的LCD颜色没改对,分辨率发现搞对了。现在开机是这个状态。颜色先不管了,后面再弄,现在去找个TF试试。
f1c200s_no2.jpg

更正,分辨率好像还是不对,后面还有8行没有显示出来。

#53 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-08 12:37:18

今天遇到2个问题:
1 ,修改液晶RGB到BGR没有成功,按https://whycan.com/viewtopic.php?id=6781的方法添加下面的代码,修改linux的 linux/drivers/gpu/drm/sun4i/sun4i_tcon.c 文件,重新编译打包后,小企鹅的脚还是蓝的,没有变成黄色。

regmap_update_bits(tcon->regs, SUN4I_TCON0_CTL_REG,BIT(23),BIT(23));//SWAP R、B引脚

2,修改uboot的液晶分辨率,配置 LCD panel timing details为分辨率480x272,结果只有开始的小企鹅那块好像是对的,后面Linux的信息都不对。

x:480,y:272,depth:18,pclk_khz:10000,le:42,ri:8,up:11,lo:4,hs:1,vs:1,sync:3,vmode:0

查看env bootargs那段没有LCD的信息,也没有看到哪里把分辨率传给Linux

 printenv
arch=arm
baudrate=115200
board=sunxi
board_name=sunxi
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=fel 
bootargs=console=tty0 console=ttyS0,115200 panic=5 rootwait root=/dev/mtdblock3 rw rootfstype=jffs2 
bootcmd=sf probe 0 50000000; sf read 0x80C00000 0x100000 0x4000; sf read 0x80008000 0x110000 0x400000; bootz 0x80008000 - 0x80C00000
bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi
bootdelay=2
bootm_size=0x1700000
console=ttyS0,115200
cpu=arm926ejs
dfu_alt_info_ram=kernel ram 0x80500000 0x1000000;fdt ram 0x80C00000 0x100000;ramdisk ram 0x80D50000 0x4000000
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
fdt_addr_r=0x80C00000
fdtcontroladdr=82ea2dc8
fdtfile=suniv-f1c100s-licheepi-nano.dtb
fel_booted=1
kernel_addr_r=0x80500000
partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system};
pxefile_addr_r=0x80D00000
ramdisk_addr_r=0x80D50000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x80C50000
soc=sunxi
stderr=serial@1c25000
stdin=serial@1c25000
stdout=serial@1c25000
uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3

Environment size: 2533/131068 bytes
=> 

进linux用命令行查看应该是没有传参数进来。

[12:13:25:748] # cat /proc/cmdline␍␊
[12:13:57:860] console=tty0 console=ttyS0,115200 panic=5 rootwait root=/dev/mtdblock3 rw rootfstype=jffs2 ␍␊

#54 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-08 00:06:02

@哇酷小二
我现在用不起来,主要是烧写到16M的SPI Flash,串口没有输出信息,不知道SD卡或NAND Flash那些能不能工作,我现在还没有试到那一步。

#55 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-07 14:35:38

29719316-D03F-425F-B891-07F91334E8AC.jpegbuildroot-tiny200 的SDK还没有搞定,编译完后烧写到Spiflash uboot没有串口输出。
回头又去重新git了nano-lcd800480分支,编译了一个1M大的u-boot,打包以后,明显还是不正常,Linux没有正常shell,但是由于换了uboot,现在LCD可以显示了,需要换一下颜色改成GBR。
对Linux不太懂,学起来也是散的,自己是搞到哪不会了,就搜一下。还没有找到好的学习方法。

 [14:04:50:530] U-Boot SPL 2018.01-05682-gd83b2fefcf-dirty (Feb 07 2023 - 01:23:22)␍␊
[14:04:50:535] DRAM:␍␊
[14:04:50:768] U-Boot SPL 2018.01-05682-gd83b2fefcf-dirty (Feb 07 2023 - 01:23:22)␍␊
[14:04:50:774] DRAM: 64 MiB␍␊
[14:04:50:786] Trying to boot from MMC1␍␊
[14:04:50:807] Card did not respond to voltage select!␍␊
[14:04:50:810] mmc_init: -95, time 22␍␊
[14:04:50:813] spl: mmc init failed with error: -95␍␊
[14:04:50:816] Trying to boot from sunxi SPI␍␊
[14:04:51:901] ␍␊
[14:04:51:901] ␍␊
[14:04:51:901] U-Boot 2018.01-05682-gd83b2fefcf-dirty (Feb 07 2023 - 01:23:22 +0800) Allwinner Technology␍␊
[14:04:51:909] ␍␊
[14:04:51:909] CPU:   Allwinner F Series (SUNIV)␍␊
[14:04:51:912] Model: Lichee Pi Nano␍␊
[14:04:51:912] DRAM:  64 MiB␍␊
[14:04:52:456] MMC:   SUNXI SD/MMC: 0␍␊
[14:04:52:460] SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB␍␊
[14:04:55:201] *** Warning - bad CRC, using default environment␍␊
[14:04:55:205] ␍␊
[14:04:55:210] Setting up a 800x480 lcd console (overscan 0x0)␍␊
[14:04:55:366] In:    serial@1c25000␍␊
[14:04:55:366] Out:   serial@1c25000␍␊
[14:04:55:369] Err:   serial@1c25000␍␊
[14:04:55:371] Net:   No ethernet found.␍␊
[14:04:55:375] starting USB...␍␊
[14:04:55:375] No controllers found␍␊
[14:04:55:380] Hit any key to stop autoboot:  2 <0x08><0x08><0x08> 1 <0x08><0x08><0x08> 0 ␍␊
[14:04:57:403] Card did not respond to voltage select!␍␊
[14:04:57:406] mmc_init: -95, time 22␍␊
[14:04:57:409] starting USB...␍␊
[14:04:57:409] No controllers found␍␊
[14:04:57:412] USB is stopped. Please issue 'usb start' first.␍␊
[14:04:57:414] starting USB...␍␊
[14:04:57:417] No controllers found␍␊
[14:04:57:420] No ethernet found.␍␊
[14:04:57:420] missing environment variable: pxeuuid␍␊
[14:04:57:423] missing environment variable: bootfile␍␊
[14:04:57:428] Retrieving file: pxelinux.cfg/00000000␍␊
[14:04:57:431] No ethernet found.␍␊
[14:04:57:431] missing environment variable: bootfile␍␊
[14:04:57:437] Retrieving file: pxelinux.cfg/0000000␍␊
[14:04:57:439] No ethernet found.␍␊
[14:04:57:442] missing environment variable: bootfile␍␊
[14:04:57:445] Retrieving file: pxelinux.cfg/000000␍␊
[14:04:57:448] No ethernet found.␍␊
[14:04:57:450] missing environment variable: bootfile␍␊
[14:04:57:454] Retrieving file: pxelinux.cfg/00000␍␊
[14:04:57:456] No ethernet found.␍␊
[14:04:57:459] missing environment variable: bootfile␍␊
[14:04:57:462] Retrieving file: pxelinux.cfg/0000␍␊
[14:04:57:464] No ethernet found.␍␊
[14:04:57:467] missing environment variable: bootfile␍␊
[14:04:57:470] Retrieving file: pxelinux.cfg/000␍␊
[14:04:57:473] No ethernet found.␍␊
[14:04:57:475] missing environment variable: bootfile␍␊
[14:04:57:478] Retrieving file: pxelinux.cfg/00␍␊
[14:04:57:481] No ethernet found.␍␊
[14:04:57:484] missing environment variable: bootfile␍␊
[14:04:57:486] Retrieving file: pxelinux.cfg/0␍␊
[14:04:57:489] No ethernet found.␍␊
[14:04:57:489] missing environment variable: bootfile␍␊
[14:04:57:495] Retrieving file: pxelinux.cfg/default-arm-sunxi␍␊
[14:04:57:497] No ethernet found.␍␊
[14:04:57:500] missing environment variable: bootfile␍␊
[14:04:57:503] Retrieving file: pxelinux.cfg/default-arm␍␊
[14:04:57:506] No ethernet found.␍␊
[14:04:57:508] missing environment variable: bootfile␍␊
[14:04:57:511] Retrieving file: pxelinux.cfg/default␍␊
[14:04:57:517] No ethernet found.␍␊
[14:04:57:517] Config file not found␍␊
[14:04:57:520] starting USB...␍␊
[14:04:57:520] No controllers found␍␊
[14:04:57:523] No ethernet found.␍␊
[14:04:57:528] No ethernet found.␍␊
[14:04:57:528] => 

#56 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-06 21:32:41

这个SDK的u-boot,linux的配置在哪个文件里,我纯新手找不着配置的地,这个SDK的资料太少了,需要一定的基础。期望哪位给讲讲怎么用起来。

#57 Re: 全志 SOC » 基于f1c200s运行linux的学习记录. » 2023-02-06 18:27:20

严重支持,自己这些日子正在学习Linux,一直还没有搞明白。现在自己的板子还在调试。希望多出些针对小白的入门文章。

#58 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-06 10:56:43

今天对F1c200S进行了烧录,PCB上是焊接的W25Q128,写进去的是下面这个sysimage-nor.img文件,结果芯片上电串口没有输出任何字符,说明u-boot没有启动,这是为什么。是我烧写的文件不对吗?我自己编译的那个固件是可以启动linux进入shell的。不知道如何解决。我看自己编译的固件与sysimage-nor.img是同样大小的。

 -rw-r--r-- 1 zl zl  16777216 Feb  4 19:59 sysimage-nor.img 
 -rw-r--r-- 1 zl zl  16777216  2月  3 17:04 f1c100s_spiflash_16M.bin

更新一下,
烧进sysimage-nor.img以后,串口没有输出,但是F1C200S 已经不是跑在FEL了,应该还是跑了uboot了。

#59 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-05 09:32:42

来汇报一下,在服务器上安装了ubuntu 18.04 server版http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.6-server-amd64.iso,安装以下包

sudo apt install wget unzip build-essential git bc swig libncurses-dev libpython3-dev libssl-dev
sudo apt install python3-distutils

拉取源码

git clone https://github.com/aodzip/buildroot-tiny200.git

编译

cd buildroot-tiny200
make widora_mangopi_r3_defconfig
make

没有其他环境的安装操作,dl文件夹是自己下载的,没有复制进去。经过一夜的编译,正确的生成了目标文件。环境很重要,不能使用ubuntu 22.04。

zl@ubuntu:~/f1c200s/buildroot-tiny200/output/images$ ls -l
total 260912
-rw-r--r-- 1 zl zl   8388608 Feb  4 19:59 bootfs.vfat
-rw-r--r-- 1 zl zl     15666 Feb  4 19:35 devicetree.dtb
-rw-r--r-- 1 zl zl   4326936 Feb  4 19:59 kernel.itb
-rw-r--r-- 1 zl zl  18583040 Feb  4 19:59 rootfs.cpio
-rw-r--r-- 1 zl zl   5970377 Feb  4 19:59 rootfs.cpio.gz
-rw-r--r-- 1 zl zl 104857600 Feb  4 19:59 rootfs.ext2
lrwxrwxrwx 1 zl zl        11 Feb  4 19:59 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 zl zl   6021120 Feb  4 19:59 rootfs.squashfs
-rw-r--r-- 1 zl zl  19671040 Feb  4 19:59 rootfs.tar
-rw-r--r-- 1 zl zl     94514 Feb  4 19:59 splash.bmp
-rw-r--r-- 1 zl zl 134217728 Feb  4 19:59 sysimage-nand.img
-rw-r--r-- 1 zl zl  16777216 Feb  4 19:59 sysimage-nor.img
-rw-r--r-- 1 zl zl 114294784 Feb  4 19:59 sysimage-sdcard.img
-rw-r--r-- 1 zl zl    451858 Feb  4 19:59 u-boot-sunxi-with-nand-spl.bin
-rw-r--r-- 1 zl zl    431378 Feb  4 19:19 u-boot-sunxi-with-spl.bin
-rw-r--r-- 1 zl zl    398546 Feb  4 19:19 u-boot.bin
-rw-r--r-- 1 zl zl   4309472 Feb  4 19:35 zImage

#60 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-05 00:12:01

我现在使用的是ubuntu 22.04,编译遇到了自己能力解决不了的问题,狗也搜不到,不知道详细的log存在哪个文件里,从目前打印出来的信息,我找不到原因,不知道为什么mknod 没有权限。
正在服务器上装ubuntu 18.04,搞一回开发环境太麻烦了,我对Linux还不太熟。
目前报错是

table='/home/zl/buildroot-tiny200/output/build/buildroot-fs/full_devices_table.txt'
mknod: /home/zl/buildroot-tiny200/output/build/buildroot-fs/cpio/target/dev/console: Operation not permitted
make[1]: *** [fs/cpio/cpio.mk:72: /home/zl/buildroot-tiny200/output/images/rootfs.cpio] Error 1
make: *** [Makefile:84: _all] Error 2

在output/image/文件夹里面已经生成了4个文件,

 $ ls
devicetree.dtb  u-boot.bin  u-boot-sunxi-with-spl.bin  zImage

慢慢研究了,是不是可以直接把这4个文件打包或直接烧录到SpiFlash去测试,好像之前编译的时候,就是这几个文件用buildroot打一下包。

#61 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2023-02-04 15:06:44

用这这个SDK编译会报错,感觉是版本问题,不知道怎么拉取正确的版本。
我是按github上的步骤进行的操作。git clone https://github.com/aodzip/buildroot-tiny200.git 以后,先make widora_mangopi_r3_defconfig,然后再make,他会直接去下载dl文件夹等相关的环境。
然后就是报下面这个错,

In file included from /usr/include/signal.h:328,
                 from ./signal.h:52,
                 from c-stack.c:49:
c-stack.c:55:26: error: missing binary operator before token "("
   55 | #elif HAVE_LIBSIGSEGV && SIGSTKSZ < 16384
      |                          ^~~~~~~~
make[5]: *** [Makefile:1915: c-stack.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [Makefile:1674: all] Error 2
make[3]: *** [Makefile:1572: all-recursive] Error 1
make[2]: *** [Makefile:1528: all] Error 2

我把c-stack.c的这部分代码注掉,又会出新的错误。所以感觉是版本问题。

#elif HAVE_LIBSIGSEGV && SIGSTKSZ < 16384
/* libsigsegv 2.6 through 2.8 have a bug where some architectures use
   more than the Linux default of an 8k alternate stack when deciding
   if a fault was caused by stack overflow.  */
# undef SIGSTKSZ
# define SIGSTKSZ 16384

新的错误是一堆的_STAT_VER相关

libfakeroot.c: In function ‘chown’:
libfakeroot.c:99:40: error: ‘_STAT_VER’ undeclared (first use in this function)
   99 | #define INT_NEXT_STAT(a,b) NEXT_STAT64(_STAT_VER,a,b)

#63 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-04 10:37:35

问一下,我的u-boot没有液晶显示,在哪里可以添加,我现在用的是nano-2018.01这个分支。没有找到关于480x272液晶的相关配置。

#64 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-03 18:18:44

手焊的两片PCB,其中一片电流偏大了大概30mA,系统启动后PCB电流大概是90mA,F1C200S芯片微热;另一片正常的电流是60mA大概,看来主芯片手焊还是挺考验技术的。

#65 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-03 17:19:31

找到原因了,是u-boot 的suniv.h文件里修改过的内容,学习过程中给注掉了。
还原以后,就可以正常启动Linux了。
我是按照这个帖子一步步学习的https://whycan.com/viewtopic.php?id=3138 ,就是下面这段代码,我给注掉了。

#define CONFIG_BOOTCOMMAND   "sf probe 0 50000000; "                           \
                             "sf read 0x80C00000 0x100000 0x4000; "  \
                             "sf read 0x80008000 0x110000 0x400000; " \
                             "bootz 0x80008000 - 0x80C00000"

正常的启动了Linux。

 [17:10:57:965] U-Boot SPL 2018.01-05679-g013ca457fd-dirty (Feb 03 2023 - 16:59:55)␍␊
[17:10:57:971] DRAM: 64 MiB␍␊
[17:10:57:982] SPL: Unsupported Boot Device!␍␊
[17:10:57:985] Trying to boot from sunxi SPI␍␊
[17:10:59:201] ␍␊
[17:10:59:201] U-Boot SPL 2018.01-05679-g013ca457fd-dirty (Feb 03 2023 - 16:59:55)␍␊
[17:10:59:206] DRAM: 64 MiB␍␊
[17:10:59:218] SPL: Unsupported Boot Device!␍␊
[17:10:59:221] Trying to boot from sunxi SPI␍␊
[17:10:59:477] ␍␊
[17:10:59:477] ␍␊
[17:10:59:477] U-Boot 2018.01-05679-g013ca457fd-dirty (Feb 03 2023 - 16:59:55 +0800) Allwinner Technology␍␊
[17:10:59:485] ␍␊
[17:10:59:485] CPU:   Allwinner F Series (SUNIV)␍␊
[17:10:59:488] Model: Lichee Pi Nano␍␊
[17:10:59:488] DRAM:  64 MiB␍␊
[17:11:00:007] Using default environment␍␊
[17:11:00:007] ␍␊
[17:11:00:007] In:    serial@1c25000␍␊
[17:11:00:010] Out:   serial@1c25000␍␊
[17:11:00:012] Err:   serial@1c25000␍␊
[17:11:00:017] Hit any key to stop autoboot:  2 <0x08><0x08><0x08> 1 <0x08><0x08><0x08> 0 ␍␊
[17:11:02:022] SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB␍␊
[17:11:02:028] device 0 offset 0x100000, size 0x4000␍␊
[17:11:02:037] SF: 16384 bytes @ 0x100000 Read: OK␍␊
[17:11:02:040] device 0 offset 0x110000, size 0x400000␍␊
[17:11:03:130] SF: 4194304 bytes @ 0x110000 Read: OK␍␊
[17:11:03:133] ## Flattened Device Tree blob at 80c00000␍␊
[17:11:03:137]    Booting using the fdt blob at 0x80c00000␍␊
[17:11:03:140]    Loading Device Tree to 816fb000, end 816fff44 ... OK␍␊
[17:11:03:154] ␍␊
[17:11:03:154] Starting kernel ...␍␊
[17:11:03:154] ␍␊
[17:11:04:248] [    0.000000] Booting Linux on physical CPU 0x0␍␊
[17:11:04:251] [    0.000000] Linux version 4.15.0-rc8-licheepi-nano+ (zhaili@zhaili-f1c200s) (gcc version 7.5.0 (Linaro GCC 7.5-2019.12)) #7 Thu Feb 2 16:26:09 UTC 2023␍␊
[17:11:04:265] [    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=0005317f␍␊
[17:11:04:270] [    0.000000] CPU: VIVT data cache, VIVT instruction cache␍␊
[17:11:04:276] [    0.000000] OF: fdt: Machine model: Lichee Pi Nano␍␊
[17:11:04:281] [    0.000000] Memory policy: Data cache writeback␍␊
[17:11:04:287] [    0.000000] random: fast init done␍␊
[17:11:04:290] [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16256␍␊
[17:11:04:295] [    0.000000] Kernel command line: console=ttyS0,115200 panic=5 rootwait root=/dev/mtdblock3 rw rootfstype=jffs2␍␊
[17:11:04:309] [    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)␍␊
[17:11:04:313] [    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)␍␊
[17:11:04:320] [    0.000000] Memory: 56208K/65536K available (5120K kernel code, 232K rwdata, 1312K rodata, 1024K init, 228K bss, 9328K reserved, 0K cma-reserved, 0K highmem)␍␊
[17:11:04:334] [    0.000000] Virtual kernel memory layout:␍␊
[17:11:04:338] [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)␍␊
[17:11:04:343] [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)␍␊
[17:11:04:348] [    0.000000]     vmalloc : 0xc4800000 - 0xff800000   ( 944 MB)␍␊
[17:11:04:354] [    0.000000]     lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)␍␊
[17:11:04:360] [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)␍␊
[17:11:04:367] [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)␍␊
[17:11:04:373] [    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (6112 kB)␍␊
[17:11:04:379] [    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)␍␊
[17:11:04:384] [    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 233 kB)␍␊
[17:11:04:390] [    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 229 kB)␍␊
[17:11:04:395] [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1␍␊
[17:11:04:402] [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16␍␊
[17:11:04:406] [    0.000046] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns␍␊
[17:11:04:415] [    0.000108] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns␍␊
[17:11:04:423] [    0.000629] Console: colour dummy device 80x30␍␊
[17:11:04:428] [    0.000710] Calibrating delay loop... 203.16 BogoMIPS (lpj=1015808)␍␊
[17:11:04:434] [    0.070221] pid_max: default: 32768 minimum: 301␍␊
[17:11:04:440] [    0.070514] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)␍␊
[17:11:04:445] [    0.070553] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)␍␊
[17:11:04:453] [    0.071948] CPU: Testing write buffer coherency: ok␍␊
[17:11:04:457] [    0.073538] Setting up static identity map for 0x80100000 - 0x80100058␍␊
[17:11:04:465] [    0.076018] devtmpfs: initialized␍␊
[17:11:04:469] [    0.082488] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns␍␊
[17:11:04:476] [    0.082548] futex hash table entries: 256 (order: -1, 3072 bytes)␍␊
[17:11:04:484] [    0.082796] pinctrl core: initialized pinctrl subsystem␍␊
[17:11:04:490] [    0.084732] NET: Registered protocol family 16␍␊
[17:11:04:494] [    0.086016] DMA: preallocated 256 KiB pool for atomic coherent allocations␍␊
[17:11:04:501] [    0.087726] cpuidle: using governor menu␍␊
[17:11:04:504] [    0.109358] SCSI subsystem initialized␍␊
[17:11:04:506] [    0.109701] usbcore: registered new interface driver usbfs␍␊
[17:11:04:512] [    0.109852] usbcore: registered new interface driver hub␍␊
[17:11:04:517] [    0.110038] usbcore: registered new device driver usb␍␊
[17:11:04:523] [    0.110559] pps_core: LinuxPPS API ver. 1 registered␍␊
[17:11:04:528] [    0.110586] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>␍␊
[17:11:04:537] [    0.110645] PTP clock support registered␍␊
[17:11:04:545] [    0.111128] Advanced Linux Sound Architecture Driver Initialized.␍␊
[17:11:04:548] [    0.112567] clocksource: Switched to clocksource timer␍␊
[17:11:04:554] [    0.137684] NET: Registered protocol family 2␍␊
[17:11:04:560] [    0.139060] TCP established hash table entries: 1024 (order: 0, 4096 bytes)␍␊
[17:11:04:566] [    0.139135] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)␍␊
[17:11:04:570] [    0.139184] TCP: Hash tables configured (established 1024 bind 1024)␍␊
[17:11:04:576] [    0.139436] UDP hash table entries: 256 (order: 0, 4096 bytes)␍␊
[17:11:04:581] [    0.139490] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)␍␊
[17:11:04:590] [    0.139943] NET: Registered protocol family 1␍␊
[17:11:04:592] [    0.142327] NetWinder Floating Point Emulator V0.97 (double precision)␍␊
[17:11:04:598] [    0.144206] Initialise system trusted keyrings␍␊
[17:11:04:604] [    0.144732] workingset: timestamp_bits=30 max_order=14 bucket_order=0␍␊
[17:11:04:609] [    0.156676] squashfs: version 4.0 (2009/01/31) Phillip Lougher␍␊
[17:11:04:615] [    0.157263] jffs2: version 2.2. (NAND) <0xc2><0xa9> 2001-2006 Red Hat, Inc.␍␊
[17:11:04:623] [    0.171391] Key type asymmetric registered␍␊
[17:11:04:626] [    0.171428] Asymmetric key parser 'x509' registered␍␊
[17:11:04:632] [    0.171620] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)␍␊
[17:11:04:637] [    0.171652] io scheduler noop registered␍␊
[17:11:04:642] [    0.171670] io scheduler deadline registered␍␊
[17:11:04:645] [    0.172407] io scheduler cfq registered (default)␍␊
[17:11:04:651] [    0.172437] io scheduler mq-deadline registered␍␊
[17:11:04:657] [    0.172455] io scheduler kyber registered␍␊
[17:11:04:662] [    0.173684] sun4i-usb-phy 1c13400.phy: Couldn't request ID GPIO␍␊
[17:11:04:666] [    0.183361] suniv-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver␍␊
[17:11:04:673] [    0.345421] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled␍␊
[17:11:04:679] [    0.351800] console [ttyS0] disabled␍␊
[17:11:04:683] [    0.372045] 1c25000.serial: ttyS0 at MMIO 0x1c25000 (irq = 23, base_baud = 6250000) is a 16550A␍␊
[17:11:04:690] [    0.816420] console [ttyS0] enabled␍␊
[17:11:04:702] [    0.826601] panel-simple panel: panel supply power not found, using dummy regulator␍␊
[17:11:04:739] [    0.863614] brd: module loaded␍␊
[17:11:04:760] [    0.884461] loop: module loaded␍␊
[17:11:04:797] [    0.921281] rbd: loaded (major 254)␍␊
[17:11:04:801] [    0.925612] SCSI Media Changer driver v0.25 ␍␊
[17:11:04:809] [    0.933402] m25p80 spi0.0: w25q128 (16384 Kbytes)␍␊
[17:11:04:813] [    0.939017] 4 ofpart partitions found on MTD device spi0.0␍␊
[17:11:04:819] [    0.944616] Creating 4 MTD partitions on "spi0.0":␍␊
[17:11:04:824] [    0.949423] 0x000000000000-0x000000100000 : "u-boot"␍␊
[17:11:04:833] [    0.956948] 0x000000100000-0x000000110000 : "dtb"␍␊
[17:11:04:843] [    0.964193] 0x000000110000-0x000000510000 : "partition"␍␊
[17:11:04:848] [    0.971823] 0x000000510000-0x000001000000 : "rootfs"␍␊
[17:11:04:856] [    0.979790] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver␍␊
[17:11:04:861] [    0.986436] ehci-platform: EHCI generic platform driver␍␊
[17:11:04:867] [    0.991939] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver␍␊
[17:11:04:873] [    0.998231] ohci-platform: OHCI generic platform driver␍␊
[17:11:04:879] [    1.003901] usbcore: registered new interface driver usb-storage␍␊
[17:11:04:886] [    1.011096] i2c /dev entries driver␍␊
[17:11:04:948] [    1.072692] sunxi-mmc 1c0f000.mmc: base:0x0f5caf00 irq:19␍␊
[17:11:04:956] [    1.080094] usbcore: registered new interface driver usbhid␍␊
[17:11:04:963] [    1.085782] usbhid: USB HID core driver␍␊
[17:11:04:983] [    1.107260] NET: Registered protocol family 17␍␊
[17:11:04:986] [    1.111831] Key type dns_resolver registered␍␊
[17:11:04:992] [    1.116269] Key type ceph registered␍␊
[17:11:04:995] [    1.120684] libceph: loaded (mon/osd proto 15/24)␍␊
[17:11:05:003] [    1.127561] Loading compiled-in X.509 certificates␍␊
[17:11:05:018] [    1.142130] sun4i-drm display-engine: bound 1e60000.display-backend (ops 0xc0632718)␍␊
[17:11:05:025] [    1.151041] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc06319fc)␍␊
[17:11:05:033] [    1.158824] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).␍␊
[17:11:05:039] [    1.165486] [drm] No driver support for vblank timestamp query.␍␊
[17:11:05:050] [    1.174402] sun4i-drm display-engine: fb0:  frame buffer device␍␊
[17:11:05:057] [    1.181583] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0␍␊
[17:11:05:064] [    1.190699] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator␍␊
[17:11:05:077] [    1.202477] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver␍␊
[17:11:05:082] [    1.208393] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1␍␊
[17:11:05:096] [    1.219621] hub 1-0:1.0: USB hub found␍␊
[17:11:05:098] [    1.223637] hub 1-0:1.0: 1 port detected␍␊
[17:11:05:105] [    1.229693] cfg80211: Loading compiled-in X.509 certificates for regulatory database␍␊
[17:11:05:122] [    1.246753] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'␍␊
[17:11:05:128] [    1.253559] vcc3v3: disabling␍␊
[17:11:05:134] [    1.256538] ALSA device list:␍␊
[17:11:05:134] [    1.259501]   #0: Loopback 1␍␊
[17:11:05:139] [    1.263298] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2␍␊
[17:11:05:146] [    1.271910] cfg80211: failed to load regulatory.db␍␊
[17:11:05:248] [    1.372028] random: crng init done␍␊
[17:11:06:913] [    3.037660] VFS: Mounted root (jffs2 filesystem) on device 31:3.␍␊
[17:11:06:922] [    3.046563] devtmpfs: mounted␍␊
[17:11:06:930] [    3.054220] Freeing unused kernel memory: 1024K␍␊
[17:11:15:457] Starting syslogd: OK␍␊
[17:11:15:553] Starting klogd: OK␍␊
[17:11:15:775] Running sysctl: OK␍␊
[17:11:16:395] Saving random seed: SKIP (read-only file system detected)␍␊
[17:11:16:456] Starting network: OK␍␊
[17:11:16:852] ␍␍␊
[17:11:16:859] Welcome to Buildroot␍␊
[17:11:16:859] ␍buildroot login: root␍␊
[17:14:20:130] # ls␍␊ 

#66 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-03 15:02:13

研究U-boot,看看是不是Linux引导的地址不对,下面这些参数我现在还看不懂。一个个的放狗找,找找系统的介绍。

[14:24:12:844] => bdinfo␍␊
[14:24:58:592] arch_number = 0x00000000␍␊
[14:24:58:594] boot_params = 0x80000100␍␊
[14:24:58:594] DRAM bank   = 0x00000000␍␊
[14:24:58:597] -> start    = 0x80000000␍␊
[14:24:58:600] -> size     = 0x04000000␍␊
[14:24:58:603] baudrate    = 115200 bps␍␊
[14:24:58:606] TLB addr    = 0x83FF0000␍␊
[14:24:58:606] relocaddr   = 0x83FC9000␍␊
[14:24:58:608] reloc off   = 0x028C9000␍␊
[14:24:58:611] irq_sp      = 0x83EA6DB0␍␊
[14:24:58:614] sp start    = 0x83EA6DA0␍␊
[14:24:58:617] Early malloc usage: 118 / 400␍␊
[14:24:58:619] fdt_blob = 83ea6dc8␍␊
[14:24:58:619] => ␍␊
[14:24:58:651] => printenv␍␊
[14:43:19:897] arch=arm␍␊
[14:43:19:897] baudrate=115200␍␊
[14:43:19:900] board=sunxi␍␊
[14:43:19:900] board_name=sunxi␍␊
[14:43:19:903] boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}␍␊
[14:43:19:911] boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf␍␊
[14:43:19:922] boot_prefixes=/ /boot/␍␊
[14:43:19:925] boot_script_dhcp=boot.scr.uimg␍␊
[14:43:19:928] boot_scripts=boot.scr.uimg boot.scr␍␊
[14:43:19:930] boot_targets=fel ␍␊
[14:43:19:930] bootargs=console=ttyS0,115200 panic=5 rootwait root=/dev/mtdblock3 rw rootfstype=jffs2␍␊
[14:43:19:939] bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi␍␊
[14:43:19:950] bootdelay=2␍␊
[14:43:19:950] bootm_size=0x1700000␍␊
[14:43:19:953] console=ttyS0,115200␍␊
[14:43:19:955] cpu=arm926ejs␍␊
[14:43:19:955] dfu_alt_info_ram=kernel ram 0x80500000 0x1000000;fdt ram 0x80C00000 0x100000;ramdisk ram 0x80D50000 0x4000000␍␊
[14:43:19:966] distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done␍␊
[14:43:19:972] fdt_addr_r=0x80C00000␍␊
[14:43:19:975] fdtcontroladdr=83ea6dc8␍␊
[14:43:19:975] fdtfile=suniv-f1c100s-licheepi-nano.dtb␍␊
[14:43:19:980] fel_booted=1␍␊
[14:43:19:980] kernel_addr_r=0x80500000␍␊
[14:43:19:983] partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system};␍␊
[14:43:20:002] pxefile_addr_r=0x80D00000␍␊
[14:43:20:002] ramdisk_addr_r=0x80D50000␍␊
[14:43:20:005] scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;␍␊
[14:43:20:022] scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done␍␊
[14:43:20:044] scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi␍␊
[14:43:20:060] scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done␍␊
[14:43:20:083] scriptaddr=0x80C50000␍␊
[14:43:20:083] soc=sunxi␍␊
[14:43:20:085] stderr=serial@1c25000␍␊
[14:43:20:085] stdin=serial@1c25000␍␊
[14:43:20:088] stdout=serial@1c25000␍␊
[14:43:20:091] uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b␍␊
[14:43:20:094] uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3␍␊
[14:43:20:099] ␍␊
[14:43:20:099] Environment size: 2384/131068 bytes␍␊
[14:43:20:102] => ␍␊

#67 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-02-03 12:54:37

自己编译了u-boot,linux,buildroot,打包烧到了SpiFlash里,只启动了uboot,没有引导系统,不知道是哪里的原因。.config文件是论坛下载的,uboot编译完了大小是182940字节。不知道是应该查uboot,还是查linux。
下面是uboot 的log,感觉像是没有引导。

[12:47:48:885] U-Boot SPL 2018.01-05679-g013ca457fd-dirty (Feb 02 2023 - 09:36:48)␍␊
[12:47:48:891] DRAM: 64 MiB␍␊
[12:47:48:903] SPL: Unsupported Boot Device!␍␊
[12:47:48:906] Trying to boot from sunxi SPI␍␊
[12:47:49:161] ␍␊
[12:47:49:161] ␍␊
[12:47:49:161] U-Boot 2018.01-05679-g013ca457fd-dirty (Feb 02 2023 - 09:36:48 +0000) Allwinner Technology␍␊
[12:47:49:169] ␍␊
[12:47:49:169] CPU:   Allwinner F Series (SUNIV)␍␊
[12:47:49:172] Model: Lichee Pi Nano␍␊
[12:47:49:172] DRAM:  64 MiB␍␊
[12:47:49:690] Using default environment␍␊
[12:47:49:690] ␍␊
[12:47:49:690] In:    serial@1c25000␍␊
[12:47:49:693] Out:   serial@1c25000␍␊
[12:47:49:696] Err:   serial@1c25000␍␊
[12:47:49:700] => 

#68 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2023-01-18 16:22:11

1,个人资料里面没有自己的发贴列表,不知道在哪里可以看到。
2,好久没有实际的进展了,最近收到了一批快递,终于。。终于把这个板子焊齐了。
3,最近在学习编译uboot、内核、buildroot,现在都可以正确编译了,但是还没有烧录测试,不知道是不是能够运行在芯片里。
4,使用sunxi-fel工具把uboot烧进了SPIFlash里,串口工具里面看到了log信息。

  因为这是我刚开始学习Linux的开发,进展比较慢;
  这是CuteCom软件的uboot的输出信息,现在还不知道uboot是不是正确的,自己学着编译的版本,不是网上下载的。
 

  
U-Boot SPL 2018.01-05679-g013ca457fd-dirty (Jan 13 2023 - 17:44:02)
DRAM: 64 MiB
Trying to boot from MMC1
Card did not respond to voltage select!
mmc_init: -95, time 22
spl: mmc init failed with error: -95
Trying to boot from sunxi SPI


U-Boot 2018.01-05679-g013ca457fd-dirty (Jan 13 2023 - 17:44:02 +0800) Allwinner Technology

CPU:   Allwinner F Series (SUNIV)
Model: Lichee Pi Nano
DRAM:  64 MiB
MMC:   SUNXI SD/MMC: 0
SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial@1c25000
Out:   serial@1c25000
Err:   serial@1c25000
Net:   No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot:  2  1  0 
SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB
device 0 offset 0x100000, size 0x4000
SF: 16384 bytes @ 0x100000 Read: OK
device 0 offset 0x110000, size 0x400000
SF: 4194304 bytes @ 0x110000 Read: OK
=> 
  

#69 Re: 全志 SOC » 终于搞好了荔枝派nano linux uboot瘦身 + usb gadget hid + gt911触控 + littlevgl demo » 2023-01-13 22:51:35

下载来看看这个configs 文件,不知道能不能替换到我现在的环境里

#70 Re: 全志 SOC » 编译buildroot-2017.08一直不能成功,用github直接clone可以编译成功,不知道能不能用在F1C200S » 2023-01-13 10:54:28

github上下载的buildroot,编译完后,rootfs.tar文件大小是3645440,这个大小感觉差不多适合SPI Flash 用。

#71 全志 SOC » 编译buildroot-2017.08一直不能成功,用github直接clone可以编译成功,不知道能不能用在F1C200S » 2023-01-13 10:31:20

pldjn_V3S
回复: 1

按照https://whycan.com/t_3138.html 流程一步 步的搞自己的编译环境,u-boot和linux,现在基本上可以编译成功了,但是到了buildroot会报错;而我从github上直接下载来的git clone https://github.com/buildroot/buildroot.git是可以编译成功的;就是不知道能不能用在F1C200S上,第一回搞linux平台的东西,啥都不懂。

#72 全志 SOC » 编译buildroot-2017.08一直不能成功,用github直接clone可以编译成功,不知道能不能用在F1C200S » 2023-01-13 10:30:21

pldjn_V3S
回复: 0

按照https://whycan.com/t_3138.html 流程一步 步的搞自己的编译环境,u-boot和linux,现在基本上可以编译成功了,现在是buildroot会报错;而我从github上直接下载来的git clone https://github.com/buildroot/buildroot.git是可以编译成功的;就是不知道能不能用在F1C200S上,第一回搞linux平台的东西,啥都不懂。

帖子发重了,这个删不掉,不知道为什么,请版主给删一下吧。

#73 全志 SOC » F1C200S的LCD接口能否连接行车记录仪的那种串行RGB接口的屏? » 2022-12-27 15:25:23

pldjn_V3S
回复: 0

手里有8bit串口的RGB屏,是原来行车记录仪上拆出来的;看了F1C200S的器件手册,好像可以支持串口的RGB输出,不知道有没有人试过,能否接到SPI+8Bit RGB的那种液晶 。看液晶里面的驱动芯片是HX8268-c

#74 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-12-23 23:42:53

@Gentlepig
板子设计的是4层板,现在还缺少2个器件,我对Linux不是太熟,现在刚建起Uboot的编译环境,还在学习中。没有下载固件测试呢。

#75 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-12-22 22:05:04

骑猪去看海 说:

想复刻白嫖JLC,不知道有没有链接~~~~

目前还没有测试,有设计上自我感觉不完美的地,暂时还没有放出文件。

#76 Re: 全志 SOC » 请教V3S显示LCD镜面相反了是什么原因 » 2022-12-21 16:07:22

hd_xyz 说:

如图,800*480的LCD显示uboot的logo,显示反了一般是什么原因导致的   LCD排除质量问题
https://whycan.com/files/members/10924/1.jpg

初始化可以配置显示方向,这个检查一下你的LCD初始化代码。

#77 Re: 全志 SOC » LCD背光闪烁 » 2022-12-21 16:03:10

cris8259 说:
pldjn_V3S 说:

PWM的频率设置的是多少,PWM的频率调高点可能会好一点。这电路就是通过占空比来调亮度。频率低了是有闪的可能的。

PWM没有使用,R19没焊接或者LCD-PWM直接输出的高电平

那你用示波器看看,你的输出电压是不是振荡了,boost电路在设计的时候,Layout的要求要比Buck要高一点。
建议把C26拆掉试一下。

#78 Re: 全志 SOC » LCD背光闪烁 » 2022-12-20 22:59:22

PWM的频率设置的是多少,PWM的频率调高点可能会好一点。这电路就是通过占空比来调亮度。频率低了是有闪的可能的。

#79 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-12-20 15:14:35

Gentlepig 说:

ch340换个ssop封装或换个8脚的会更好看点。

那个脚多的不是CH340,是RTC Rx8025,实际CH340我用的SSOP10的封装的。

#80 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-12-20 00:32:40

板子做回来了,手焊了2片,现在板上还缺少几个器件,还没有寄到(北京的快递还是发不出来),初步测试,USB可以枚举到FEL,各部分的电压是对的。串口debug信息还没有显示,因为USB转ttl的芯片还没有寄到。f1c200s.jpg

#81 Re: 全志 SOC » [求助]各位大佬,我在为f1c100s编译u-boot的过程中遇到了问题,希望能得到指点! » 2022-12-03 12:50:06

新手,遇到了一样的问题,遇到问题的流程都一样。看了楼主的方法解决了。

#83 Re: 全志 SOC » v3s RGB 颜色不对 » 2022-11-29 12:16:09

看手册支持 RGB,GBR,BRG,怎么只切换RB的线序?
看错了,是有直接切换RB的位。
这样布线的时候应该可以方便点,省得PCB这块都要过孔绕线。
我对了一下,Lichee nano 和公版的F1C200S的原理图,在这块是反的。不知道当时设计的时候的原因是什么。如果按公版的原理图,这块的线都直连了,不需要绕线。

#84 Re: 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-11-28 16:25:19

lanlanzhilian 说:

还有人用microUSB

嗯,谢谢提醒,我手里的MicroUSB口还有几十支存货,就用了。Type-C的放这个板子,空间也可以。

#85 全志 SOC » 疫情之下器件无法邮寄到手了,就多画几块板了,画了一个F1C200S的小核心板。 » 2022-11-28 11:49:04

pldjn_V3S
回复: 33

身在帝都,最近疫情高发,器件除了用顺丰其他快递都停了,邮费太贵了,先缓缓了。先多做些设计,画一块F1C200S的小板玩玩。
小板参考了论坛好几位前辈的板子,放置了R8025 做为RTC,背了一个C1220的小电池,其他基本没有啥变化 。准备白嫖JLC。
放上原理图:
F1C200S_DIY.pdf

f1c200s.png

#86 Re: 全志 SOC » 问下,F1C200S的PWM1引脚是哪个,看公版原理图与手册不是同个脚。 » 2022-11-20 20:15:46

lanlanzhilian 说:
pldjn_V3S 说:

再问一个问题,电阻触摸部分芯片内部有TP控制部分,为什么还要外挂NS2009呢?

因为要节省2个IO

真是精打细算啊。

#87 Re: 全志 SOC » 问下,F1C200S的PWM1引脚是哪个,看公版原理图与手册不是同个脚。 » 2022-11-19 14:46:08

再问一个问题,电阻触摸部分芯片内部有TP控制部分,为什么还要外挂NS2009呢?

#88 全志 SOC » 问下,F1C200S的PWM1引脚是哪个,看公版原理图与手册不是同个脚。 » 2022-11-18 16:29:53

pldjn_V3S
回复: 3

F1C200S datasheets V 1.1 里,第14页 PWM1是在PE6、PF5两个脚上,而F1C200S的公版原理图里面是画在PE10这个脚上的。这应该是哪个为准?

#89 Re: 全志 SOC » 开源一个F1C200S的小板子,附带MDK+RTX+LVGL+NS2009测试工程 » 2022-11-17 00:54:17

这芯片跑Linux怎么样,感觉RTX还是8051那个级别在用的OS

#90 Re: 全志 SOC » 开源一个F1C200S的实用向板,极限压榨这片子的功能 » 2022-11-08 23:28:45

卓林 说:

@f_Endman
哈哈,我当初也是被这个USB整蒙了,最后才查到论坛里有人说不能超过三个端点。本来打算用hub挂usb4G网卡的,结果只能选择wifi网卡了。

USB只能挂3个端点是啥意思 ,一个设备不都要2-4个端点了吗

#92 Re: 感芯科技 » 能做CAN通信吗?能做几路啊?有手册吗?怎么配置啊? » 2022-11-04 20:56:06

你要用他们家的,可能能收发,但是过滤器好像没有资料,用起来估计还差了点。

#93 Re: 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-11-03 23:39:42

Gentlepig 说:

挺好看的。

希望好用,希望能顺利调起来。

#94 Re: 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-11-02 22:29:24

今天终于画完了板发到立创去做PCB了。

最终在板上增加了两个RS232接口的端子,可以跳线选择Uart1、Uart2是否输出RS232;
Type-c接口上外引了Uart0,通过CH340转换的USB;
增加了一个OTG接口,用于烧录芯片固件;可以通过跳线选择是USBHUB,还是OTG接口;
希望打样的板能顺利跑起来。
V3S_1.png
V3S_2.png

#96 Re: 感芯科技 » 能做CAN通信吗?能做几路啊?有手册吗?怎么配置啊? » 2022-10-26 23:18:49

bwolf1986 说:

看了一晚上感觉资料好少啊!想做多路CAN通信,不知道如何配置。还请大家赐教啊

CAN通讯的资料很多,你没有说你是要用什么芯片,打算怎么做,像STM32F4这样的芯片,内部带了2路CAN,如果是在V3S这样的芯片上扩展,可以查一下MCP2515、MCP2517。

#97 Re: 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-10-22 09:29:23

bright 说:

自己画多累呀,立创有个开源平台,上面有好多开源的v3s开发板,我不生产板子,我是板子的搬运工!

开源平台是只能用力创的EDA还设计才行吗?看着有不少的板子。
我想的是可以兼容当前市面上的一些派,可以使用40Pin的插针,搞一些板级的接口啥的。在系统要求不高的时候可以使用V3S,要求高了就换其他派。

#98 Re: 全志 SOC » 小智科技X3卡片电脑,仅有银行卡一半大,像艺术品般的硬件,多图慎入~ (开放购买) » 2022-10-21 14:20:17

这种结构在iphon10里面有,类似BGA焊接; 我觉得在开发板上用这个结构可能并不是最优选择,iPhone在重摔以后也很容易因为掉点,造成信号不断连。感觉开发板应该是个很皮实的东西。

#99 Re: 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-10-20 21:07:17

jxdqwer 说:

@Gentlepig

嘉立创打样可以代贴阻容了嘛?服务这么好

今天问了同事,他在力创刚下了单;据说现在力创的器件可以自动匹配,用起来比以前方便了,等我也试试。

#100 Re: 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-10-19 19:56:13

@Gentlepig
你这个还有无线呢,我就不想放这个了,感觉用的上的话,就在双排针上做扩展板吧。
现在JLC的贴片好像挺贵的吧,我好久没在那做了。简单的都自己手焊两块。

#101 全志 SOC » 翻出十几片V3S,打算画成树莓派同尺寸的板 » 2022-10-18 21:36:26

pldjn_V3S
回复: 13

最近收拾东西,翻出来大概前年买的剪板V3S的芯片,打算DIY一块树莓派同尺寸的小PCB试试。板上有40Pin的IO,引出3组Uart,3组IIC,一组SPI、一组SDIO;预留40Pin的LCD接口,板上留一个SPI Flash 和一个TF卡座;通过USB HUB芯片扩展4个USB口出来 。
头一回玩V3S这类的Linux芯片,没经验,以前是玩单片机的,希望多提意见。
原理图隔三差五的画,现在差不多了,摄像头的接口,还没想好需不需要。器件排布大概就是下面这样了。估计用不了几天就能画完了。
V3S_20221018.png

#102 Re: 全志 SOC » 恳请前辈指点v3s简易开发板设计---已立项 » 2022-10-18 21:17:30

你这个接口位置不限制的话,应该比较好做。
我最近收拾出来十几个V3S芯片,大概前年买的剪板的芯片,准备DIY成树莓派同尺寸的PCB。

#104 Re: DIY/综合/Arduino/写字机/3D打印机/智能小车/平衡车/四轴飞行/MQTT/物联网 » imx6ull开发板4层 » 2022-01-18 21:14:35

mzy2364 说:

https://whycan.com/files/members/2487/imx6ull_s1.png
最近抽空又画了一个带外壳的玩玩,大家觉得那种好看一些呢?

能讲讲DDR布线的经验吗?自己不会搞这种高速线。

页脚

工信部备案:粤ICP备20025096号 Powered by FluxBB

感谢为中文互联网持续输出优质内容的各位老铁们。 QQ: 516333132, 微信(wechat): whycan_cn (哇酷网/挖坑网/填坑网) service@whycan.cn