您尚未登录。

#1 Re: 全志 SOC » F1c100s / F1c200s 移植 LVGL v8.3,基于xboot » 2024-03-16 17:07:15

原版的xboot代码就不会有这个警告,生成的xboot.bin烧录后也能正常启动,大小有4MB,同样的工具连。

#2 Re: 全志 SOC » F1c100s / F1c200s 移植 LVGL v8.3,基于xboot » 2024-03-16 16:00:13

楼主,你好:
                连接的时候出了警告,生成的xboot.bin很少,只有900多kb,烧录后,不能启动,这个
会是那里出问题?换了工具连也一样的问题。

FluxBB bbcode 测试

#3 Re: 全志 SOC » buildroot-tiny200 (F1C100/200s) 开发包近期更新内容 * 已支持DVP摄像头 *,支持SPI NAND » 2024-03-13 16:16:43

晕哥 说:
aaayao 说:

请问楼主,这个是用什么版本的ubuntu编译的?

16.04,18.04,20.04都可以,其他没有验证。

好的,谢谢!目前用14.0.6编译老是出错,看来要换个系统试试了。

#5 Re: 全志 SOC » F1C200s tina系统,硬解码mpeg2 ts码流CPU占用达99% » 2022-08-31 16:46:22

解码MP4时CPU占用50%左右是正常的了。但是解码mpeg2 ts码流占用99%就是不正常的了,就是不知道那里出问题了?

#6 全志 SOC » F1C200s tina系统,硬解码mpeg2 ts码流CPU占用达99% » 2022-08-31 10:54:13

aaayao
回复: 2

如题,解码mp4文件时,CPU占用50%左右。但解码mpeg2 ts码流CPU占用达99%
这个有什么办法可以优化呢?

#7 Re: 全志 SOC » PhoenixSuit软件发现不了设备 » 2020-08-06 09:32:37

手动把那个叹号的驱动删除,加载烧录文件,检测到板子后,会自动开始烧录。

#8 Re: 全志 SOC » 试一试 Ubuntu 18.04 编译f1c200s tina 3.x » 2020-08-06 09:28:54

tina123456 说:

输入pack命令:
...

你好!这个image is for nor的配置能分享一下吗?谢谢了!
我用默认配置编译出来的是image is for nand/emmc,这个没有办法烧录成功。

#9 Re: 全志 SOC » 试一试 Ubuntu 18.04 编译f1c200s tina 3.x » 2020-08-04 22:31:31

楼主:
       你好,烧录时提示这个错误,nor flash为25Q128;试过插入TF卡也一样提示这个错误,这个有办法解决吗?
QQ图片20200804222838.png

#13 Re: 全志 SOC » v3s实现流水灯显示 » 2019-12-02 20:36:02

晕哥 说:

不好意思,5楼这个回复不是 leds-gpio 驱动配套的应用程序

https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt

参考这个: https://blog.csdn.net/jklinux/article/details/78645106

晕哥,你好:
               按照这个方法,没有看到leds目录,会是那里出问题了呢?

#14 Re: 全志 SOC » 荔枝派Nano Pi PWM背光设置问题 » 2019-12-02 16:50:36

楼主,你好:
               正好要做leds驱动,请教一个问题,没有看到有leds目录,是少了那个配置文件呢?
板子log:

# ls /sys/bus/platform/devices                                                                         
10000.sram               1c20ca0.watchdog         regulatory.0
1c00000.sram-controller  1c25000.serial           serial8250
1c05000.spi              1e60000.display-backend  snd-soc-dummy
1c0c000.lcd-controller   alarmtimer               snd_aloop.0
1c0f000.mmc              display-engine           soc
1c13000.usb              musb-hdrc.1.auto         usb_phy_generic.0.auto
1c13400.phy              my-leds2                 vcc3v3
1c20800.pinctrl          panel
1c20c00.timer            reg-dummy
# ls /sys/bus/platform/devices/my-leds2                                                                
driver_override  of_node          subsystem
modalias         power            uevent
# 

设备树:

    my-leds2 {
        compatible = "gpio-leds";        /* 才能被识别为Led */
        pinctrl-names = "default";
        pinctrl-0 = <&leds_pins>;
             blue_led {
                     label = "licheepi:blue:usr";
                     gpios = <&pio 4 4 GPIO_ACTIVE_LOW>; /* PE4 */
             };

             green_led {
                     label = "licheepi:green:usr";
                     gpios = <&pio 4 5 GPIO_ACTIVE_LOW>; /* PE5 */
                     default-state = "on";
             };

             red_led {
                     label = "licheepi:red:usr";
                     gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PE6 */
             };
    };



		pio: pinctrl@1c20800 {
			compatible = "allwinner,suniv-pinctrl";
			reg = <0x01c20800 0x400>;
			interrupts = <38>, <39>, <40>;
			clocks = <&ccu CLK_BUS_PIO>, <&osc24M>, <&osc32k>;
			clock-names = "apb", "hosc", "losc";
			gpio-controller;
			interrupt-controller;
			#interrupt-cells = <3>;
			#gpio-cells = <3>;


			leds_pins: leds-pins {
				pins = "PE4","PE5","PE6";
				function = "gpio_out";
			};
                  };

#15 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-12-01 16:37:40

少了个参数-p,加上后可以烧录了。不过这速度也太慢了,只有32kB/s,在WIN下最少也有80多kB/s

QQ图片20191201163515.png

#16 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-12-01 06:54:30

晕哥 说:

用一楼下载的windows版本可以用吗?

1楼的windows版本是可以用的。有没有可能git上面的代码已经被修改了呢?

#17 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-11-30 22:48:35

编译和安装:

yaoming@yaoming-VirtualBox:~$ cd sunxi-tools
yaoming@yaoming-VirtualBox:~/sunxi-tools$ ls
adb-devprobe.sh                     nand-common.h
autoversion.sh                      nand-image-builder.c
bin                                 nand-part-a10.h
boot_head.lds                       nand-part-a20.h
boot_head.S                         nand-part.c
bootinfo.c                          nand-part-main.c
common.h                            phoenix_info.c
fel.c                               pio.c
fel-gpio                            progress.c
fel_lib.c                           progress.h
fel_lib.h                           README.md
fel-remotefunc-compiler.rb          script_bin.c
fel-remotefunc-spi-data-transfer.c  script_bin.h
fel-remotefunc-spi-data-transfer.h  script.c
fel-sdboot.lds                      script_extractor.c
fel-sdboot.S                        script_fex.c
fel-spiflash.c                      script_fex.h
fel-spiflash.h                      script.h
fexc.c                              script_uboot.c
fexc.h                              script_uboot.h
find-arm-gcc.sh                     soc_info.c
include                             soc_info.h
jtag-loop.c                         tests
jtag-loop.lds                       thunk.c
jtag-loop.S                         thunk.h
LICENSE.md                          thunks
Makefile                            uart0-helloworld-sdboot.c
meminfo.c                           uart0-helloworld-sdboot.lds
yaoming@yaoming-VirtualBox:~/sunxi-tools$ make
Setting version information: v1.4.1-104-g11a9d20

cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/   -o sunxi-fexc fexc.c script.c script_uboot.c script_bin.c script_fex.c
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/   -o sunxi-bootinfo bootinfo.c
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/  `pkg-config --cflags libusb-1.0` `pkg-config --cflags zlib`  -o sunxi-fel \
                fel.c thunk.c progress.c soc_info.c fel_lib.c fel-spiflash.c  `pkg-config --libs libusb-1.0` `pkg-config --libs zlib`
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/  -c -o nand-part-main.o nand-part-main.c
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/  -c -o nand-part-a10.o nand-part.c -D A10
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/  -c -o nand-part-a20.o nand-part.c -D A20
cc  -o sunxi-nand-part nand-part-main.o nand-part-a10.o nand-part-a20.o
cc -std=c99 -Wall -Wextra -Wno-unused-result -D_POSIX_C_SOURCE=200112L -D_BSD_SOURCE -D_DEFAULT_SOURCE -Iinclude/   -o sunxi-pio pio.c
ln -nsf sunxi-fexc bin2fex
ln -nsf sunxi-fexc fex2bin
yaoming@yaoming-VirtualBox:~/sunxi-tools$ sudo make install
[sudo] password for yaoming:
install -d /usr/local/bin
+ install -m0755 sunxi-fexc /usr/local/bin/sunxi-fexc
+ install -m0755 sunxi-bootinfo /usr/local/bin/sunxi-bootinfo
+ install -m0755 sunxi-fel /usr/local/bin/sunxi-fel
+ install -m0755 sunxi-nand-part /usr/local/bin/sunxi-nand-part
+ install -m0755 sunxi-pio /usr/local/bin/sunxi-pio
+ ln -nfs sunxi-fexc /usr/local/bin/bin2fex
+ ln -nfs sunxi-fexc /usr/local/bin/fex2bin

#19 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-11-30 22:13:38

插上USB第一次运行时,提示这个:

yaoming@yaoming-VirtualBox:~/f1c100s$ sudo sunxi-fel spiflash-write 0 f1c100s_spiflash_16M.bin
Warning: no 'soc_sram_info' data for your SoC (id=1663)
usb_bulk_send() ERROR -7: Operation timed out

#21 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-11-30 22:03:46

能看到USB设备

yaoming@yaoming-VirtualBox:~$ lsusb
Bus 001 Device 003: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


但是提示烧录timed out
yaoming@yaoming-VirtualBox:~/f1c100s$ sudo sunxi-fel spiflash-write 0 f1c100s_spiflash_16M.bin
usb_bulk_send() ERROR -7: Operation timed out

#22 Re: 全志 SOC » 编译、安装Windows版本sunxi-fel步骤 (32M spi flash补丁,支持W25Q256/MX25L256) » 2019-11-30 21:39:30

晕哥,你好:
                能上传一个ubuntu 能用的sunxi-fel执行文件吗?

#23 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-29 16:38:58

用的是libusb 的驱动,可能是这个原因。那还是现在这样用好啦!万一改了驱动可能烧录又有问题。

#24 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-29 16:07:15

晕哥,你好:
               终于把ADB给调通了,感谢各位大神的帮忙!另外,电脑设备上显示的为什么会是USB Function Filesystem呢?而不是显示ADB Interface设备?
QQ图片20191129160340.png

#25 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 21:32:56

重做了根文件系统,可以跑起来啦!但是在电脑上只见到USB串行设备(COM3),看不到ADB设备?是内核选择不对?

# ls
bin           lib32         opt           run_adbd1.sh  usr
dev           linuxrc       proc          sbin          var
etc           media         root          sys
lib           mnt           run           tmp
# ./run_adbd1.sh
[   33.480045] file system registered
# install_listener('tcp:5037','*smartsocket*')
[   36.030694] read descriptors
[   36.033918] read strings
[   36.133406] using random self ethernet address
[   36.138008] using random host ethernet address
[   36.142522] using random self ethernet address
[   36.147061] using random host ethernet address
[   36.152770] usb0: HOST MAC fa:7a:56:21:29:54
[   36.157286] usb0: MAC 5a:cb:da:ba:81:fb
[   36.162531] g_ffs gadget: g_ffs ready
[   36.832124] g_ffs gadget: high-speed config #1: FunctionFS + RNDIS


QQ%E5%9B%BE%E7%89%8720191128213148.png

#26 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 20:48:54

并夕夕 说:

文件系统里面啊, buildroot的 output/target 目录

找到了,在buildroot/output/target/usr/bin里,这个应该怎么调用呢?

#27 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 19:47:33

adbd这个文件没有找到呢,内核目录里也没有,怎么产生这个文件呢?

晕哥 说:

找一下 adbd 有没有拷贝到文件系统

#28 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 17:42:47

那这个adbd &启动不了哦?什么是什么问题?

#29 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 17:34:27

搜索ADB相关的选项如下,还有什么需要打开的吗?
QQ图片20191128173233.png
QQ图片20191128173239.png

#31 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 17:04:45

g_ffs.ko编译出来了
QQ图片20191128170411.png


可以加载g_ffs驱动了,但是提示line 5: adbd: not found,这个是什么意思呢?

# ls
bin           lib32         opt           run_adbd1.sh  usr
dev           linuxrc       proc          sbin          var
etc           media         root          sys
lib           mnt           run           tmp
# ./run_adbd1.sh
[   29.951996] file system registered
# ./run_adbd1.sh: line 5: adbd: not found
lsmod
Module                  Size  Used by    Not tainted
g_ffs                  16384  1
usb_f_fs               40960  3 g_ffs
usb_f_rndis            24576  1 g_ffs
u_ether                20480  2 g_ffs,usb_f_rndis
libcomposite           40960  3 g_ffs,usb_f_fs,usb_f_rndis
#

#32 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 16:17:14

晕哥,没找到这个 g_ffs.ko,应该怎么样产生这个文件的?

#33 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 15:48:03

usb gadget相关模块已经打开了
QQ图片20191128152106.png

但是启动是提示这样,没有找到模块
# ls
bin           lib32         opt           run_adbd1.sh  usr
dev           linuxrc       proc          sbin          var
etc           media         root          sys
lib           mnt           run           tmp
# ./run_adbd1.sh
modprobe: module g_ffs not found in modules.dep
[   41.655771] ------------[ cut here ]------------
[   41.660473] WARNING: CPU: 0 PID: 98 at fs/filesystems.c:282 get_fs_type+0xf8/0x110
[   41.668171] request_module fs-functionfs succeeded, but still no fs?
[   41.674514] Modules linked in: usb_f_fs libcomposite
[   41.679565] CPU: 0 PID: 98 Comm: mount Not tainted 4.15.0-rc8-licheepi-nano #8
[   41.686809] Hardware name: Allwinner suniv Family
[   41.691591] [<c010e604>] (unwind_backtrace) from [<c010b74c>] (show_stack+0x10/0x14)
[   41.699411] [<c010b74c>] (show_stack) from [<c01166c8>] (__warn+0xcc/0xf4)
[   41.706344] [<c01166c8>] (__warn) from [<c0116728>] (warn_slowpath_fmt+0x38/0x48)
[   41.713842] [<c0116728>] (warn_slowpath_fmt) from [<c01e7878>] (get_fs_type+0xf8/0x110)
[   41.721905] [<c01e7878>] (get_fs_type) from [<c01eab80>] (do_mount+0x1c0/0xb58)
[   41.729264] [<c01eab80>] (do_mount) from [<c01eb850>] (SyS_mount+0x54/0xc0)
[   41.736281] [<c01eb850>] (SyS_mount) from [<c0107d80>] (ret_fast_syscall+0x0/0x50)
[   41.743837] ---[ end trace 7631d98e80bc747e ]---
mount: mounting adb on /dev/usb-ffs/adb failed: No such device
# ./run_adbd1.sh: line 5: adbd: not found


内核usb gadget模块应该是有编译出来了:
QQ图片20191128134244.png
QQ图片20191128134252.png

buildroot里面这个fastboot需要打开吗?
QQ图片20191128154307.png

#34 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 11:11:54

晕哥,你好:
               以下这样操作之后,再打包zImage就行了吗?这个ADB的modules好像没有看到?

ubuntu@VM-0-16-ubuntu:~/f1c100s/linux-f1c100s-480272lcd-test$ make ARCH=arm CROS      S_COMPILE=arm-linux-gnueabi- -j4 modules
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     scripts/mod/devicetable-offsets.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/bounds.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  Building modules, stage 2.
  MODPOST 16 modules
ubuntu@VM-0-16-ubuntu:~/f1c100s/linux-f1c100s-480272lcd-test$ make ARCH=arm CROS      S_COMPILE=arm-linux-gnueabi- modules_install INSTALL_MOD_PATH="./out"
  INSTALL crypto/echainiv.ko
  INSTALL drivers/input/touchscreen/goodix.ko
  INSTALL drivers/mtd/tests/mtd_nandbiterrs.ko
  INSTALL drivers/mtd/tests/mtd_nandecctest.ko
  INSTALL drivers/mtd/tests/mtd_oobtest.ko
  INSTALL drivers/mtd/tests/mtd_pagetest.ko
  INSTALL drivers/mtd/tests/mtd_readtest.ko
  INSTALL drivers/mtd/tests/mtd_speedtest.ko
  INSTALL drivers/mtd/tests/mtd_stresstest.ko
  INSTALL drivers/mtd/tests/mtd_subpagetest.ko
  INSTALL drivers/mtd/tests/mtd_torturetest.ko
  INSTALL drivers/net/mii.ko
  INSTALL drivers/net/usb/rtl8150.ko
  INSTALL drivers/staging/rtl8723bs/r8723bs.ko
  INSTALL drivers/usb/mon/usbmon.ko
  INSTALL drivers/video/backlight/lcd.ko
  DEPMOD  4.15.0-rc8-licheepi-nano
ubuntu@VM-0-16-ubuntu:~/f1c100s/linux-f1c100s-480272lcd-test$

#35 Re: 全志 SOC » 分享个licheepi nano镜像,支持adb调试 » 2019-11-28 08:45:04

checkout 说:

漏了,脚本如下:

#! /bin/sh
modprobe g_ffs idVendor=0x18d1 idProduct=0x4e42 iSerialNumber="buildroot"
mkdir -p /dev/usb-ffs/adb
mount -t functionfs adb /dev/usb-ffs/adb -o uid=2000,gid=2000
adbd &

楼主,你好:
               使用了这个脚本,但是提示失败了,内核和buildroot都打开了相关配置的,这个会是什么原因呢?

# ls
bin           lib32         opt           run_adbd1.sh  usr
dev           linuxrc       proc          sbin          var
etc           media         root          sys
lib           mnt           run           tmp
# ./run_adbd1.sh
modprobe: can't change directory to '/lib/modules': No such file or directory
mount: mounting adb on /dev/usb-ffs/adb failed: No such device
# ./run_adbd1.sh: line 5: adbd: not found

#37 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-25 09:58:34

晕哥 说:

arm-none-linux-gnueabi-gcc 这个是 4.x 的
你要把这个 gcc 升级成 7.x


不是系统的GCC吗?工具琏的这个GCC要怎么升级呢?

#38 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-25 09:56:46

晕哥 说:

arm-none-linux-gnueabi-gcc -o hello hello.c -static


这样是可以了,但是程序的容量大了几百倍?buildroot编译出来的才不到10KB
QQ%E5%9B%BE%E7%89%8720191125095203.png

#39 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-25 09:25:42

我在24楼贴出来了log,GCC是7.X的,后面再编译UBOOT就出错了

晕哥 说:

不可能, 我的就是 7.x 编译的,大家都是用7.x

#40 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-25 09:21:37

晕哥,你好:
               使用arm-2014.05-29-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2这个工具编译程序,还是运行不了?是那里有问题呢?uboot和内核不是用这个工具编译的。


主机log:
ubuntu@VM-0-16-ubuntu:~$ vi hello.c
ubuntu@VM-0-16-ubuntu:~$ arm-none-linux-gnueabi-gcc -o hello hello.c
ubuntu@VM-0-16-ubuntu:~$ ls
f1c100s  hello  hello.c
ubuntu@VM-0-16-ubuntu:~$


以下是板子lgo:
# ./hello                                                                         
-sh: ./hello: not found
# ./hello                                                                         
-sh: ./hello: not found
# ./hello                                                                         
-sh: ./hello: not found
#

#41 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-25 09:17:39

我编译的是u-boot-nano-lcd800480,不行呢?不知道为什么了?

jimmy 说:

7.x 可以编译新 u-boot的啊

#42 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-23 17:14:11

用了 gcc 7.x 还是不行啊,这U-BOOT编译看来只能用gcc-linaro-7.2.1


ubuntu@VM-0-16-ubuntu:~/f1c100s/u-boot$ arm-none-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-none-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/arm-2014.05/bin/../libexec/gcc/arm-none-linux-gnueabi/4.8.3/lto-wrapper
Target: arm-none-linux-gnueabi
Configured with: /scratch/maciej/arm-linux-2014.05-rel/src/gcc-4.8-2014.05/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --enable-extra-sgxxlite-multilibs --with-arch=armv5te --with-gnu-as --with-gnu-ld --with-specs='%{save-temps: -fverbose-asm} %{funwind-tables|fno-unwind-tables|mabi=*|ffreestanding|nostdlib:;:-funwind-tables} -D__CS_SOURCERYGXX_MAJ__=2014 -D__CS_SOURCERYGXX_MIN__=5 -D__CS_SOURCERYGXX_REV__=29' --enable-languages=c,c++ --enable-shared --enable-lto --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion='Sourcery CodeBench Lite 2014.05-29' --with-bugurl=https://sourcery.mentor.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/libc --with-gmp=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-mpfr=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-mpc=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-isl=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-cloog=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --disable-libgomp --disable-libitm --enable-libatomic --disable-libssp --enable-poison-system-directories --with-build-time-tools=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/bin SED=sed
Thread model: posix
gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29)
ubuntu@VM-0-16-ubuntu:~/f1c100s/u-boot$ gcc --version
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

ubuntu@VM-0-16-ubuntu:~/f1c100s/u-boot$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- -j4
*** Your GCC is older than 6.0 and is not supported
arch/arm/config.mk:69: recipe for target 'checkgcc6' failed
make: *** [checkgcc6] Error 1
ubuntu@VM-0-16-ubuntu:~/f1c100s/u-boot$

#43 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-23 09:37:33

晕哥 说:

这个问题基本上 zImage不完整,或者 dtb文件错误。

我现在又全部再试一次,看看那里出问题了

#44 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-23 09:36:51

编译u-boot又出问题了,是不是这个编译工具太老了?

ubuntu@VM-0-16-ubuntu:~/f1c100s/u-boot$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- -j4
*** Your GCC is older than 6.0 and is not supported
make: *** [checkgcc6] Error 1
make: INTERNAL: Exiting with 5 jobserver tokens available; should be 4!

#45 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-22 15:14:18

工具琏显示是这样的

ubuntu@VM-0-16-ubuntu:~/f1c100s$ arm-none-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-none-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/arm-2014.05/bin/../libexec/gcc/arm-none-linux-gnueabi/4   .8.3/lto-wrapper
Target: arm-none-linux-gnueabi
Configured with: /scratch/maciej/arm-linux-2014.05-rel/src/gcc-4.8-2014.05/confi   gure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-   gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdc   xx-pch --enable-extra-sgxxlite-multilibs --with-arch=armv5te --with-gnu-as --wit   h-gnu-ld --with-specs='%{save-temps: -fverbose-asm} %{funwind-tables|fno-unwind-   tables|mabi=*|ffreestanding|nostdlib:;:-funwind-tables} -D__CS_SOURCERYGXX_MAJ__   =2014 -D__CS_SOURCERYGXX_MIN__=5 -D__CS_SOURCERYGXX_REV__=29' --enable-languages   =c,c++ --enable-shared --enable-lto --enable-symvers=gnu --enable-__cxa_atexit -   -with-pkgversion='Sourcery CodeBench Lite 2014.05-29' --with-bugurl=https://sour   cery.mentor.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sy   sroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratc   h/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/l   ibc --with-gmp=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none   -linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-li   nux-gnu/usr --with-mpfr=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29   -arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i   686-pc-linux-gnu/usr --with-mpc=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-20   14.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/hos   t-libs-i686-pc-linux-gnu/usr --with-isl=/scratch/maciej/arm-linux-2014.05-rel/ob   j/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.ex   tras/host-libs-i686-pc-linux-gnu/usr --with-cloog=/scratch/maciej/arm-linux-2014   .05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-   gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --disable-libgomp --disable-libit   m --enable-libatomic --disable-libssp --enable-poison-system-directories --with-   build-time-tools=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/   arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/maciej/arm-linux-201   4.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/bin SED=sed
Thread model: posix
gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29)
ubuntu@VM-0-16-ubuntu:~/f1c100s$

#46 Re: 全志 SOC » 荔枝派Nano使用gcc-linaro-7.2.1进行交叉编译得到的可执行文件,一运行就"segmentation fault" » 2019-11-22 15:12:41

晕哥 说:

建议用: arm-2014.05-29-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

https://sourcery.mentor.com/GNUToolchain/package12813/public/arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

http://sources.buildroot.net/toolchain-external-codesourcery-arm/arm-2014.05-29-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2


这个绝对可以的, 经过实战检验的:

whycan@ubuntu:/opt/arm-2014.05/bin$ ./arm-none-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=./arm-none-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/arm-2014.05/bin/../libexec/gcc/arm-none-linux-gnueabi/4.8.3/lto-wrapper
Target: arm-none-linux-gnueabi
Configured with: /scratch/maciej/arm-linux-2014.05-rel/src/gcc-4.8-2014.05/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --enable-extra-sgxxlite-multilibs --with-arch=armv5te --with-gnu-as --with-gnu-ld --with-specs='%{save-temps: -fverbose-asm} %{funwind-tables|fno-unwind-tables|mabi=*|ffreestanding|nostdlib:;:-funwind-tables} -D__CS_SOURCERYGXX_MAJ__=2014 -D__CS_SOURCERYGXX_MIN__=5 -D__CS_SOURCERYGXX_REV__=29' --enable-languages=c,c++ --enable-shared --enable-lto --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion='Sourcery CodeBench Lite 2014.05-29' --with-bugurl=https://sourcery.mentor.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/libc --with-gmp=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-mpfr=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-mpc=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-isl=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --with-cloog=/scratch/maciej/arm-linux-2014.05-rel/obj/pkg-2014.05-29-arm-none-linux-gnueabi/arm-2014.05-29-arm-none-linux-gnueabi.extras/host-libs-i686-pc-linux-gnu/usr --disable-libgomp --disable-libitm --enable-libatomic --disable-libssp --enable-poison-system-directories --with-build-time-tools=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/maciej/arm-linux-2014.05-rel/install/opt/codesourcery/arm-none-linux-gnueabi/bin SED=sed
Thread model: posix
gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29)
whycan@ubuntu:/opt/arm-2014.05/bin$

晕哥,你好:
               用了这个工具琏,编译完内核启动不了啊,原来gcc-linaro-7.2.1这个编译是能正常启动的,这个是什么原因呢?
QQ图片20191122150900.png

#47 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-21 22:57:49

全部重新来一次,又可以启动了,之前那个错误应该是JFFS2文件系统加载失败。
QQ图片20191121225330.png


这次是把内核换成5.2,修改还是成功的
QQ图片20191121225507.png

#48 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-20 23:06:11

uboot启动时,输入print命令查看打印:


Hit any key to stop autoboot:  0
=>
=>
=>
=>
=> printf
Unknown command 'printf' - try 'help'
=> print 
arch=arm
baudrate=115200
board=sunxi
board_name=sunxi
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=fel mmc0 usb0 pxe dhcp
bootcmd=sf probe 0 50000000; sf read 0x80C00000 0x100000 0x4000; sf read 0x80008000 0x110000 0x400000; bootz 0x80008000 - 0x80C00000
bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00010:UNDI:003000;setenv bootp_arch 0xa;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci;
bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi
bootcmd_usb0=setenv devnum 0; run usb_boot
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
efi_dtb_prefixes=/ /dtb/ /dtb/current/
fdt_addr_r=0x80C00000
fdtcontroladdr=83e6ada8
fdtfile=suniv-f1c100s-licheepi-nano.dtb
fel_booted=1
kernel_addr_r=0x80500000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
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};
preboot=usb start
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;run scan_dev_for_efi;
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_efi=setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile
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
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi
uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3

Environment size: 4560/32764 bytes
=>

#49 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-20 23:02:34

晕哥 说:

你的 bootargs 是什么? root=???

按照楼主这个来的:

(2)更改配置
    回到 uboot 源码一级目录, 进入TUI配置
    make ARCH=arm menuconfig
    取消勾选 [] Enable a default value for bootcmd
    勾选 [v] Enable boot arguments;
    在下方一项中填入 bootargs 参数:
        console=ttyS0,115200 panic=5 rootwait root=/dev/mtdblock3 rw rootfstype=jffs2



这个是要和buildroot的那个参数要对应呢?

#50 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-20 22:11:23

重新生成BIN文件,再烧录,到VFS系统这里就出错了;重做了rootfs系统,再生成BIN文件,还是一样的出错,不知道那里出问题了?
QQ图片20191120220455.png
QQ图片20191120220517.png

在LCD上也可以看到出错信息
QQ图片20191120220620.jpg

#51 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-13 21:26:33

查看CPU实时运行频率,用什么命令呢?

#52 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-13 20:53:56

换回W25Q128,启动终于成成了!
QQ图片20191113205209.png

#53 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-13 17:34:08

原来的板子果然是有问题,现在新的板子可以读写,终于能见到串口启到到U-BOOT了,但是卡在最前面。
QQ%E5%9B%BE%E7%89%8720191113173037.png
QQ图片20191113172554.png

#54 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-11 17:34:22

晕哥 说:

注意引脚,不要反了,芯片有个小凹槽的是第一脚。

如果你实在不确定的话,可以买widora的板子,今天包邮,自带了TTL调试,boot键,reset键,焊好了flash。

晕哥,刚刚拍了一套,等收到看看是不是硬件的问题了。

#55 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-11 16:11:45

楼主,你的是NANO板子吗?FLASH是买回来就焊好的吗?

我这个是买回来要自己焊的FLASH,不知道硬件上会不会有问题?
QQ图片20191111160826.jpg

#56 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-11 15:10:10

晕哥 说:

那是因为你的程序没烧进去,所以再次插入,按流程又进入了usb fel,你现在需要解决为什么没有烧录进去

整到无办法了,能读写,但是读出来全是0。

QQ图片20191111114609.png
QQ图片20191111114703.png


现在只能试试在LINUX下面烧写。

#57 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-11 09:51:35

LinjieGuo 说:
aaayao 说:

楼主,你好:
                能提供一下你的SPI FLASH的型号和规格书吗?我这板子估计是FLASH出问题了。

我这里用的是winband 25Q128JV50,容量为16MB,应该跟flash无关,淘宝随便买两片,容量一样即可。

我的也是在淘宝是购买的,型号和楼主的一样。
楼主你这个能正常启动的NANO板子,只插上USB到电脑,电脑会识别成FEL模式吗?不短接FLASH引脚的情况下。

#58 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-11 09:48:35

晕哥 说:

可以烧, 你是不是 spi flash 引脚一直都下拉了?进入FEL 就不能下拉.

晕哥,我这个NANO板子,SPI FLASH引脚不短接,插上USB就直接识别为FEL模式,这个会是什么问题?

#59 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-10 22:36:13

楼主,你好:
                能提供一下你的SPI FLASH的型号和规格书吗?我这板子估计是FLASH出问题了。

#60 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-10 12:23:51

不用短路FLASH 1、2脚,插上USB就可以烧录和读取,当短路1、2脚再插USB,也是一样的结果

#61 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-10 08:39:10

晕哥 说:

新鲜出炉 windows 版本 32M spi nor flash 版本烧录软件: sunxi-tools-win32-support_f1c100s_32M.7z

测试OK!

这个程序能烧32M的,那也可以烧16M的吗?
我试了烧W25Q128,烧进去正常,但是读出来全部为0。

#62 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-10 08:27:37

晕哥 说:

@aaayao  https://whycan.cn/t_444.html 下载1楼最底下那个

----------------------------------------------------------------------
以下是 2018-12-19 更新 (16楼):

为了不再给大家造成困扰,我把文件重新整理了 V3s 和 F1C100s 两个文件夹,

欢迎下载测试: sunxi-tools-win32support_f1c100s_v3s_201812219.7z


这个接USB HUB之后可以读写了,但是写入之后读出来,还是全0? 难道要换个W25Q256吗?

#63 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-09 21:33:09

楼主,请问是用25Q128吗?也是用那个16M的烧录程序吗?

#64 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-09 21:27:13

启动不了,烧录显示正常的,但FLASH读出来全是0,这个是使用32M的烧录程序,我的FLASH是W25Q128,16M的,可能是这样引起出错了
QQ图片20191109211100.png

另外,如果使用16M的烧录程序,就会出错,烧录不了,读也不行,能测试一下16M的烧录程序是那里有问题吗?
QQ图片20191109212022.png
QQ图片20191109212240.png

最后还发现一个问题,就是外接了USB HUB之后,烧录会提示找不到USB设备,但在WIN的设备管理器里是能看到USB设备的,这个有办法解决吗?

#65 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-09 16:58:54

晕哥 说:

@aaayao 换win7 电脑试一试

谢谢晕哥提醒,换了另一台WIN10 64位电脑,烧录正常了,但是烧写速度实在也太慢啦!SPIFLASH是W25Q128

QQ图片20191109165334.png

#66 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-09 11:17:56

Zadig显示的USB ID是对的,驱动也装上了
QQ图片20191109111643.png

#67 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-09 11:14:16

烧录又遇到问题了,在WIN10下安装了USB驱动,但是烧录时提示找不到设备?
QQ图片20191109111129.png

QQ图片20191109111157.png

#68 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-08 14:28:15

smartcar 说:

看错误提示, 缺 SPI 的引脚定义: spi0_pins_a

谢谢提醒,补上了引脚定义,编译通过了

   spi0_pins_a: spi0-pins-pc {
                pins = "PC0", "PC1", "PC2", "PC3";
                function = "spi0";
            };


QQ图片20191108142716.png

#69 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-08 10:34:38

晕哥 说:

检查 "suniv-f1c100s.dtsi" 等包含文件里面有没有关于 spi0 的定义.

谢谢晕哥提醒,原来的这个内核在suniv-f1c100s.dtsi里没有发现SPI0的定义,增加定义后代码如下:

// SPDX-License-Identifier: (GPL-2.0+ OR X11)
/*
 * Copyright 2018 Icenowy Zheng <icenowy@aosc.io>
 * Copyright 2018 Mesih Kilinc <mesihkilinc@gmail.com>
 */

#include <dt-bindings/clock/suniv-ccu-f1c100s.h>
#include <dt-bindings/reset/suniv-ccu-f1c100s.h>

/ {
	#address-cells = <1>;
	#size-cells = <1>;
	interrupt-parent = <&intc>;

	clocks {
		osc24M: clk-24M {
			#clock-cells = <0>;
			compatible = "fixed-clock";
			clock-frequency = <24000000>;
			clock-output-names = "osc24M";
		};

		osc32k: clk-32k {
			#clock-cells = <0>;
			compatible = "fixed-clock";
			clock-frequency = <32768>;
			clock-output-names = "osc32k";
		};
	};

	cpus {
		cpu {
			compatible = "arm,arm926ej-s";
			device_type = "cpu";
		};
	};
	
	de: display-engine {
		compatible = "allwinner,suniv-f1c100s-display-engine";
		allwinner,pipelines = <&fe0>;
		status = "disabled";
	};

	soc {
		compatible = "simple-bus";
		#address-cells = <1>;
		#size-cells = <1>;
		ranges;

		sram-controller@1c00000 {
			compatible = "allwinner,suniv-f1c100s-system-control",
				     "allwinner,sun4i-a10-system-control";
			reg = <0x01c00000 0x30>;
			#address-cells = <1>;
			#size-cells = <1>;
			ranges;

			sram_d: sram@10000 {
				compatible = "mmio-sram";
				reg = <0x00010000 0x1000>;
				#address-cells = <1>;
				#size-cells = <1>;
				ranges = <0 0x00010000 0x1000>;

				otg_sram: sram-section@0 {
					compatible = "allwinner,suniv-f1c100s-sram-d",
						     "allwinner,sun4i-a10-sram-d";
					reg = <0x0000 0x1000>;
					status = "disabled";
				};
			};
		};

		spi0: spi@1c05000 {
			compatible = "allwinner,suniv-spi",
				     "allwinner,sun8i-h3-spi";
			reg = <0x01c05000 0x1000>;
			interrupts = <10>;
			clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_BUS_SPI0>;
			clock-names = "ahb", "mod";
			resets = <&ccu RST_BUS_SPI0>;
			status = "disabled";
			#address-cells = <1>;
			#size-cells = <0>;
		};

		spi1: spi@1c06000 {
			compatible = "allwinner,suniv-spi",
				     "allwinner,sun8i-h3-spi";
			reg = <0x01c06000 0x1000>;
			interrupts = <11>;
			clocks = <&ccu CLK_BUS_SPI1>, <&ccu CLK_BUS_SPI1>;
			clock-names = "ahb", "mod";
			resets = <&ccu RST_BUS_SPI1>;
			status = "disabled";
			#address-cells = <1>;
			#size-cells = <0>;
		};
		tcon0: lcd-controller@1c0c000 {
			compatible = "allwinner,suniv-f1c100s-tcon";
			reg = <0x01c0c000 0x1000>;
			interrupts = <29>;
			clocks = <&ccu CLK_BUS_LCD>,
				 <&ccu CLK_TCON>;
			clock-names = "ahb",
				      "tcon-ch0";
			clock-output-names = "tcon-pixel-clock";
			resets = <&ccu RST_BUS_LCD>;
			reset-names = "lcd";
			status = "disabled";

			ports {
				#address-cells = <1>;
				#size-cells = <0>;

				tcon0_in: port@0 {
					#address-cells = <1>;
					#size-cells = <0>;
					reg = <0>;

					tcon0_in_be0: endpoint@0 {
						reg = <0>;
						remote-endpoint = <&be0_out_tcon0>;
					};
				};

				tcon0_out: port@1 {
					#address-cells = <1>;
					#size-cells = <0>;
					reg = <1>;
				};
			};
		};

		ccu: clock@1c20000 {
			compatible = "allwinner,suniv-f1c100s-ccu";
			reg = <0x01c20000 0x400>;
			clocks = <&osc24M>, <&osc32k>;
			clock-names = "hosc", "losc";
			#clock-cells = <1>;
			#reset-cells = <1>;
		};

		intc: interrupt-controller@1c20400 {
			compatible = "allwinner,suniv-f1c100s-ic";
			reg = <0x01c20400 0x400>;
			interrupt-controller;
			#interrupt-cells = <1>;
		};

		pio: pinctrl@1c20800 {
			compatible = "allwinner,suniv-f1c100s-pinctrl";
			reg = <0x01c20800 0x400>;
			interrupts = <38>, <39>, <40>;
			clocks = <&ccu CLK_BUS_PIO>, <&osc24M>, <&osc32k>;
			clock-names = "apb", "hosc", "losc";
			gpio-controller;
			interrupt-controller;
			#interrupt-cells = <3>;
			#gpio-cells = <3>;

			uart0_pe_pins: uart0-pe-pins {
				pins = "PE0", "PE1";
				function = "uart0";
			};
			
			lcd_rgb666_pins: lcd-rgb666-pins {
				pins = "PD0", "PD1", "PD2", "PD3", "PD4",
				       "PD5", "PD6", "PD7", "PD8", "PD9",
				       "PD10", "PD11", "PD12", "PD13", "PD14",
				       "PD15", "PD16", "PD17", "PD18", "PD19",
				       "PD20", "PD21";
				function = "lcd";
			};
			
			mmc0_pins: mmc0-pins {
				pins = "PF0", "PF1", "PF2", "PF3", "PF4", "PF5";
				function = "mmc0";
			};
		};

		timer@1c20c00 {
			compatible = "allwinner,suniv-f1c100s-timer";
			reg = <0x01c20c00 0x90>;
			interrupts = <13>;
			clocks = <&osc24M>;
		};

		mmc0: mmc@1c0f000 {
			compatible = "allwinner,suniv-f1c100s-mmc",
				     "allwinner,sun7i-a20-mmc";
			reg = <0x01c0f000 0x1000>;
			clocks = <&ccu CLK_BUS_MMC0>,
				 <&ccu CLK_MMC0>,
				 <&ccu CLK_MMC0_OUTPUT>,
				 <&ccu CLK_MMC0_SAMPLE>;
			clock-names = "ahb",
					      "mmc",
					      "output",
				    	  "sample";
			resets = <&ccu RST_BUS_MMC0>;
			reset-names = "ahb";
			interrupts = <23>;
			pinctrl-names = "default";
			pinctrl-0 = <&mmc0_pins>;
			status = "disabled";
			#address-cells = <1>;
			#size-cells = <0>;
		};

		wdt: watchdog@1c20ca0 {
			compatible = "allwinner,suniv-f1c100s-wdt",
				     "allwinner,sun4i-a10-wdt";
			reg = <0x01c20ca0 0x20>;
		};

		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";
		};

		uart2: serial@1c25800 {
			compatible = "snps,dw-apb-uart";
			reg = <0x01c25800 0x400>;
			interrupts = <3>;
			reg-shift = <2>;
			reg-io-width = <4>;
			clocks = <&ccu CLK_BUS_UART2>;
			resets = <&ccu RST_BUS_UART2>;
			status = "disabled";
		};
		usb_otg: usb@1c13000 {
			compatible = "allwinner,suniv-musb";
			reg = <0x01c13000 0x0400>;
			clocks = <&ccu CLK_BUS_OTG>;
			resets = <&ccu RST_BUS_OTG>;
			interrupts = <26>;
			interrupt-names = "mc";
			phys = <&usbphy 0>;
			phy-names = "usb";
			extcon = <&usbphy 0>;
			allwinner,sram = <&otg_sram 1>;
			status = "disabled";
		};

		usbphy: phy@1c13400 {
			compatible = "allwinner,suniv-usb-phy";
			reg = <0x01c13400 0x10>;
			reg-names = "phy_ctrl";
			clocks = <&ccu CLK_USB_PHY0>;
			clock-names = "usb0_phy";
			resets = <&ccu RST_USB_PHY0>;
			reset-names = "usb0_reset";
			#phy-cells = <1>;
			status = "disabled";
		};
		fe0: display-frontend@1e00000 {
			compatible = "allwinner,suniv-f1c100s-display-frontend";
			reg = <0x01e00000 0x20000>;
			interrupts = <30>;
			clocks = <&ccu CLK_BUS_DE_FE>, <&ccu CLK_DE_FE>,
				 <&ccu CLK_DRAM_DE_FE>;
			clock-names = "ahb", "mod",
				      "ram";
			resets = <&ccu RST_BUS_DE_FE>;
			status = "disabled";

			ports {
				#address-cells = <1>;
				#size-cells = <0>;

				fe0_out: port@1 {
					#address-cells = <1>;
					#size-cells = <0>;
					reg = <1>;

					fe0_out_be0: endpoint@0 {
						reg = <0>;
						remote-endpoint = <&be0_in_fe0>;
					};
				};
			};
		};

		be0: display-backend@1e60000 {
			compatible = "allwinner,suniv-f1c100s-display-backend";
			reg = <0x01e60000 0x10000>;
			reg-names = "be";
			interrupts = <31>;
			clocks = <&ccu CLK_BUS_DE_BE>, <&ccu CLK_DE_BE>,
				 <&ccu CLK_DRAM_DE_BE>;
			clock-names = "ahb", "mod",
				      "ram";
			resets = <&ccu RST_BUS_DE_BE>;
			reset-names = "be";
			assigned-clocks = <&ccu CLK_DE_BE>;
			assigned-clock-rates = <300000000>;

			ports {
				#address-cells = <1>;
				#size-cells = <0>;

				be0_in: port@0 {
					#address-cells = <1>;
					#size-cells = <0>;
					reg = <0>;

					be0_in_fe0: endpoint@0 {
						reg = <0>;
						remote-endpoint = <&fe0_out_be0>;
					};
				};

				be0_out: port@1 {
					#address-cells = <1>;
					#size-cells = <0>;
					reg = <1>;

					be0_out_tcon0: endpoint@0 {
						reg = <0>;
						remote-endpoint = <&tcon0_in_be0>;
					};
				};
			};
		};
	};
};

但是编译还是出错:

yaoming@yaoming-VirtualBox:~/f1c100s/linux$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs -j4
  DTC     arch/arm/boot/dts/suniv-f1c100s-licheepi-nano.dtb
arch/arm/boot/dts/suniv-f1c100s.dtsi:74.21-85.5: ERROR (phandle_references): /soc/spi@1c05000: Reference to non-existent node or label "spi0_pins_a"

  also defined at arch/arm/boot/dts/suniv-f1c100s-licheepi-nano.dts:92.7-132.3
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [arch/arm/boot/dts/suniv-f1c100s-licheepi-nano.dtb] 错误 2
make[1]: *** [dtbs] 错误 2
make: *** [sub-make] 错误 2

#70 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-08 10:19:49

LinjieGuo 说:
aaayao 说:

加在下面这个位置,但是编译出错了。

https://whycan.cn/files/members/2261/QQ图片20191107223200.png


// SPDX-License-Identifier: (GPL-2.0+ OR X11)
/*
 * Copyright 2018 Icenowy Zheng <icenowy@aosc.io>
 */

/dts-v1/;
#include "suniv-f1c100s.dtsi"
#include <dt-bindings/gpio/gpio.h>

/ {
	model = "Lichee Pi Nano";
	compatible = "licheepi,licheepi-nano", "allwinner,suniv-f1c100s";

	aliases {
		serial0 = &uart0;
	};

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

	panel: panel {
		compatible = "qiaodian,qd43003c0-40", "simple-panel";
		#address-cells = <1>;
		#size-cells = <0>;
		enable-gpios = <&pio 4 6 GPIO_ACTIVE_HIGH>;
		power-supply = <&reg_vcc3v3>;

 		port@0 {
			reg = <0>;
			#address-cells = <1>;
			#size-cells = <0>;

 			panel_input: endpoint@0 {
				reg = <0>;
				remote-endpoint = <&tcon0_out_lcd>;
			};
		};
	};

	reg_vcc3v3: vcc3v3 {
		compatible = "regulator-fixed";
		regulator-name = "vcc3v3";
		regulator-min-microvolt = <3300000>;
		regulator-max-microvolt = <3300000>;
	};
};

&be0 {
	status = "okay";
};

&de {
	status = "okay";
};

&tcon0 {
	pinctrl-names = "default";
	pinctrl-0 = <&lcd_rgb666_pins>;
	status = "okay";
};

&tcon0_out {
	tcon0_out_lcd: endpoint@0 {
		reg = <0>;
		remote-endpoint = <&panel_input>;
	};
};

&mmc0 {
	vmmc-supply = <&reg_vcc3v3>;
	bus-width = <4>;
	broken-cd;
	status = "okay";
};

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

&otg_sram {
	status = "okay";
};

&usb_otg {
	dr_mode = "otg";
	status = "okay";
};

&spi0 {
    pinctrl-names = "default";
    pinctrl-0 = <&spi0_pins_a>;
    status = "okay";
    spi-max-frequency = <50000000>;
    flash: w25q128@0 {
        #address-cells = <1>;
        #size-cells = <1>;
        compatible = "winbond,w25q128", "jedec,spi-nor";
        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@100000 {
                label = "dtb";
                reg = <0x100000 0x10000>;
                read-only;
            };

            partition@110000 {
                label = "kernel";
                reg = <0x110000 0x400000>;
                read-only;
            };

            partition@510000 {
                label = "rootfs";
                reg = <0x510000 0xAF0000>;
            };
        };
    };
};   

&usbphy {
	usb0_id_det-gpio = <&pio 4 2 GPIO_ACTIVE_HIGH>; /* PE2 */
	status = "okay";
};

代码比较工具对比了一下,一模一样,我上我这边的源码给你看看把。能力有限,你多折腾几遍,/笑/哈

linux内核源码链接: https://pan.baidu.com/s/1YpbDNFXn_2QdTh8YIcF_jg 提取码:bc35



感谢楼主提供的内核,编译通过了
QQ图片20191108082626.png
QQ图片20191108082633.jpg

代码不同的地方是在suniv.dtsi里还有相关的SPI配置代码:
        spi0: spi@1c05000 {
            compatible = "allwinner,suniv-spi",
                     "allwinner,sun8i-h3-spi";
            reg = <0x01c05000 0x1000>;
            interrupts = <10>;
            clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_BUS_SPI0>;
            clock-names = "ahb", "mod";
            resets = <&ccu RST_BUS_SPI0>;
            status = "disabled";
            #address-cells = <1>;
            #size-cells = <0>;
        };

        spi1: spi@1c06000 {
            compatible = "allwinner,suniv-spi",
                     "allwinner,sun8i-h3-spi";
            reg = <0x01c06000 0x1000>;
            interrupts = <11>;
            clocks = <&ccu CLK_BUS_SPI1>, <&ccu CLK_BUS_SPI1>;
            clock-names = "ahb", "mod";
            resets = <&ccu RST_BUS_SPI1>;
            status = "disabled";
            #address-cells = <1>;
            #size-cells = <0>;
        };

#71 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-07 22:35:03

加在下面这个位置,但是编译出错了。

QQ图片20191107223200.png


// SPDX-License-Identifier: (GPL-2.0+ OR X11)
/*
 * Copyright 2018 Icenowy Zheng <icenowy@aosc.io>
 */

/dts-v1/;
#include "suniv-f1c100s.dtsi"
#include <dt-bindings/gpio/gpio.h>

/ {
	model = "Lichee Pi Nano";
	compatible = "licheepi,licheepi-nano", "allwinner,suniv-f1c100s";

	aliases {
		serial0 = &uart0;
	};

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

	panel: panel {
		compatible = "qiaodian,qd43003c0-40", "simple-panel";
		#address-cells = <1>;
		#size-cells = <0>;
		enable-gpios = <&pio 4 6 GPIO_ACTIVE_HIGH>;
		power-supply = <&reg_vcc3v3>;

 		port@0 {
			reg = <0>;
			#address-cells = <1>;
			#size-cells = <0>;

 			panel_input: endpoint@0 {
				reg = <0>;
				remote-endpoint = <&tcon0_out_lcd>;
			};
		};
	};

	reg_vcc3v3: vcc3v3 {
		compatible = "regulator-fixed";
		regulator-name = "vcc3v3";
		regulator-min-microvolt = <3300000>;
		regulator-max-microvolt = <3300000>;
	};
};

&be0 {
	status = "okay";
};

&de {
	status = "okay";
};

&tcon0 {
	pinctrl-names = "default";
	pinctrl-0 = <&lcd_rgb666_pins>;
	status = "okay";
};

&tcon0_out {
	tcon0_out_lcd: endpoint@0 {
		reg = <0>;
		remote-endpoint = <&panel_input>;
	};
};

&mmc0 {
	vmmc-supply = <&reg_vcc3v3>;
	bus-width = <4>;
	broken-cd;
	status = "okay";
};

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

&otg_sram {
	status = "okay";
};

&usb_otg {
	dr_mode = "otg";
	status = "okay";
};

&spi0 {
    pinctrl-names = "default";
    pinctrl-0 = <&spi0_pins_a>;
    status = "okay";
    spi-max-frequency = <50000000>;
    flash: w25q128@0 {
        #address-cells = <1>;
        #size-cells = <1>;
        compatible = "winbond,w25q128", "jedec,spi-nor";
        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@100000 {
                label = "dtb";
                reg = <0x100000 0x10000>;
                read-only;
            };

            partition@110000 {
                label = "kernel";
                reg = <0x110000 0x400000>;
                read-only;
            };

            partition@510000 {
                label = "rootfs";
                reg = <0x510000 0xAF0000>;
            };
        };
    };
};   

&usbphy {
	usb0_id_det-gpio = <&pio 4 2 GPIO_ACTIVE_HIGH>; /* PE2 */
	status = "okay";
};

#72 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-07 21:00:49

我这个suniv-f1c100s-licheepi-nano.dts没有找到&spi0{...}段落,应该在那个位置加上去呢?

// SPDX-License-Identifier: (GPL-2.0+ OR X11)
/*
 * Copyright 2018 Icenowy Zheng <icenowy@aosc.io>
 */

/dts-v1/;
#include "suniv-f1c100s.dtsi"
#include <dt-bindings/gpio/gpio.h>

/ {
	model = "Lichee Pi Nano";
	compatible = "licheepi,licheepi-nano", "allwinner,suniv-f1c100s";

	aliases {
		serial0 = &uart0;
	};

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

	panel: panel {
		compatible = "qiaodian,qd43003c0-40", "simple-panel";
		#address-cells = <1>;
		#size-cells = <0>;
		enable-gpios = <&pio 4 6 GPIO_ACTIVE_HIGH>;
		power-supply = <&reg_vcc3v3>;

 		port@0 {
			reg = <0>;
			#address-cells = <1>;
			#size-cells = <0>;

 			panel_input: endpoint@0 {
				reg = <0>;
				remote-endpoint = <&tcon0_out_lcd>;
			};
		};
	};

	reg_vcc3v3: vcc3v3 {
		compatible = "regulator-fixed";
		regulator-name = "vcc3v3";
		regulator-min-microvolt = <3300000>;
		regulator-max-microvolt = <3300000>;
	};
};

&be0 {
	status = "okay";
};

&de {
	status = "okay";
};

&tcon0 {
	pinctrl-names = "default";
	pinctrl-0 = <&lcd_rgb666_pins>;
	status = "okay";
};

&tcon0_out {
	tcon0_out_lcd: endpoint@0 {
		reg = <0>;
		remote-endpoint = <&panel_input>;
	};
};

&mmc0 {
	vmmc-supply = <&reg_vcc3v3>;
	bus-width = <4>;
	broken-cd;
	status = "okay";
};

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

&otg_sram {
	status = "okay";
};

&usb_otg {
	dr_mode = "otg";
	status = "okay";
};

&usbphy {
	usb0_id_det-gpio = <&pio 4 2 GPIO_ACTIVE_HIGH>; /* PE2 */
	status = "okay";
};

#73 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-07 14:05:01

楼主,你好:
               按照你的连接下载的内核源码目录里没有 ./arch/arm/boot/dts/suniv-f1c100s-licheepi-nano.dts 这个文件啊?

QQ图片20191107135919.png

#74 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-07 09:55:45

搬瓦工现在全部升级到KVM,不能显示续费的,都需要重新购买,旧的VPS都要报废。

#75 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-07 09:19:28

xgui 说:

双十一搬瓦工bwh可能有促销的VPS, 在这上面速度比起墙内快多了。克隆torvalds的Linux仓库最多1分钟搞定。

这个方法真好,在VPS上克隆真的非常的快啊!
QQ图片20191107090703.png
QQ图片20191107090823.png
QQ图片20191107082435.png

但是要传回本地就非常的慢了,看来要在VPS上进行编译才行了。编译好之处只传回目标文件。
QQ图片20191107090158.png


可惜现在的搬瓦工都没有以前19刀一年的了,最便宜都要49刀一年。

#77 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-06 17:20:21

QT不是需要的,能不能简单说说只编译根文件系统,需要些什么配置?

#78 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-06 16:57:40

晕哥 说:

@aaayao 这个文件下载失败: https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.12.10.tar.xz

你可以手动下载拷贝到 dl/ 目录。

下载了linux-4.12.10.tar.xz,放到dl目录里,现在还一直在编译,不知道还要编译多久?

#79 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-06 16:48:46

现在编译了3个小时,还在编译,这根文件系统为什么要编译这么久的?

#80 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-06 16:47:04

看来真的要试试在VPS上搭开发环境了。

#82 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-06 09:58:05

楼主,你好:
               我在编译根文件系统时,编译了一个多小时都没有编译完,看日志在下载很多东西,经常请求超时.dl文件夹里已经下载了楼主提供的文件,请问是那里出问题了?上传日志帮忙看看。log.txtQQ图片20191106095627.png

#83 Re: 全志 SOC » 尝试从零构建F1C100s开发环境 » 2019-11-05 11:20:27

楼主加油,正在按前面的教程一步一步来!

页脚

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

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