@chrisvista
可以了👼
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
改成
curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > ~/bin/repo

@whycanservice2 哈哈 打算開賣了嗎

我是服了，编译个SDK还要自己改代码吗？
http://bbs.eeworld.com.cn/thread-1219810-1-1.html
按照这个改完可以往下跑了，
另外我有个疑问，我买的是4G eMMC的不是Nand版本的，配置选择的时候也是选择7吗？

All available board: 0. evb1 1. evb1_auto 2. evb1_auto_nand 3. evb1_auto_nor 4. tlt113-evm-emmc 5. tlt113-evm-nand 6. tlt113-minievm-emmc 7. tlt113-minievm-nand Choice [tlt113-minievm-emmc]: 7

选择7的话是可以编译过了，选择6就编译不过了
然后又遇到问题：

strerror-sym.c: In function 'gpg_strerror_sym': strerror-sym.c:45:13: warning: implicit declaration of function 'errnos_msgidxof'; did you mean 'msgidxof'? [-Wimplicit-function-declaration] idx = errnos_msgidxof (code); ^~~~~~~~~~~~~~~ msgidxof strerror-sym.c:47:9: error: 'errnos_msgstr' undeclared (first use in this function) return errnos_msgstr + errnos_msgidx[idx]; ^~~~~~~~~~~~~ strerror-sym.c:47:9: note: each undeclared identifier is reported only once for each function it appears in strerror-sym.c:47:25: error: 'errnos_msgidx' undeclared (first use in this function); did you mean 'errnos_msgstr'? return errnos_msgstr + errnos_msgidx[idx]; ^~~~~~~~~~~~~ errnos_msgstr make[5]: *** [Makefile:1120: gpg_error-strerror-sym.o] Error 1 make[5]: *** Waiting for unfinished jobs.... make[4]: *** [Makefile:648: all] Error 2 make[3]: *** [Makefile:508: all-recursive] Error 1 make[2]: *** [Makefile:440: all] Error 2 make[1]: *** [package/pkg-generic.mk:241: /home/slamdunk/work/Tronlong/LinuxSDK-v1.2/T113-i_v1.0/out/t113_i/tlt113-minievm-emmc/longan/buildroot/build/libgpg-error-1.33/.stamp_built] Error 2 make: *** [Makefile:96: _all] Error 2 make: Leaving directory '/home/slamdunk/work/Tronlong/LinuxSDK-v1.2/T113-i_v1.0/buildroot/buildroot-201902'

飞凌提供了一个关于camera的一个qt_demo程序，可以参考forlinx_desktop的源码中/OKT507-desktop-release/platform/framework/auto/qt_demo

T113 登录SSH异常问题，修改/etc/init.d/rcS
取消注释 #/etc/adb_conf.sh start &

我用MangoPI官网的github包编译出能正常启动的img，网址（https://mangopi.org/mqr）；
!LOG_.png
但用司徒大神的包编译的img始终不能正常引导，提示如之前反馈的错误，大致意思是两个ERROR：没有找到uboot.fex头和opensbi.fex头；
!
对比了一些目录发现差异还是比较多的，特别是lichee\brandy-2.0\spl下面：
司徒大神的包里面没有找到sboot文件夹，不知道是啥原因；
LOG_2.png
我按@steward 你的包编译的固件日志第二行直接调用了include\commit_info.h的CI_INFO那个hash，但你编译好的Img第二行是sh脚本调用log文件生成的。能提示可能是什么原因吗？
MangoPI使用的是lichee\brandy-2.0\目录下的spl-pub，里面内容和你的spl文件目录相差还是比较大。目前已经重新在github上多次下载并编译，问题仍然一致。基本可以排除文件 不一致造成的

LIBS += -L/root/workspace/allwinner/A40i/bsp/lichee/out/sun8iw11p1/linux/common/buildroot/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/ -lasound

在pro文件种添加这句好使了➿

@asoul_ava 当然，这个＋10还是+多少还得看自己板子的文件

重新执行./build.sh config配置

@dort91011 这个是UDISK分区，是烧录软件在烧录的时候自动划分的空间。如果需要手动配置，请在sys_partition.fex里手动配置这个分区的size

@nzdzhd
这是虚拟键盘存放路径，

Image_20230911085535.png.thumb.jpg

可以先尝试修改/home/forlinx/work/OKT507-linux-sdk/platform/framework/auto/sdk_lib/DWKeyboard/src路径下的inputview.cpp文件，具体路径根据你的源码解压路径而定。

/home/forlinx/work/OKT507-linux-sdk/platform/framework/auto/sdk_lib/DWKeyboard这个路径是所调用的虚拟键盘qt工程的存放位置，改完之后需要修改该路径下Makefile里编写的一些路径，推荐用别的代码编辑器批量替换，因为有700多处需要改，改完之后该路径下执行make生成新的可执行文件，然后回到源码路径全编译，打包新镜像烧写即可

大佬，想问一下，你有测试过80k以下波特率的吗？我试了一下，会报这个错误。
ip link set can0 type can bitrate 50000
sunxi_can 2504000.can can0: bitrate error 8589934.5% too high。你有遇到过吗？

@nzdzhd 看看驱动的教程，我记得改改设备树就能用了，不过没实际弄过

還是線的問題?每條usb延長線刀能刷機嗎?

您好，可以参考TLT113-EVM的设备树配置即可，无需编写驱动。

@zznzzn 您好，可以屏蔽/etc/init.d/rcS脚本中对应代码

尝试将android工具getevent移植到linux中，可以成功查看电阻屏的反馈速度。
参考了 https://www.cnblogs.com/liangliangge/p/12921889.html 中的办法
工具的源码路径为：android/system/core/toolbox/getevent.c
其中源码中getevent.c文件中内容有修改
由于头文件input.h-labels.h生成过程中涉及权限问题，直接新建了input.h-labels.h文件并复制黏贴了参考链接中的内容
Makefile文件参考了 lichee/buildroot-201611/target/user_rootfs_apps/cmd/subs 下的工程里的Makefile

用getevent -lrt命令输出时间戳、上报速率等，要计算事件之间的时间间隔，我们可以取两个连续事件的时间戳（括号内的数值）并计算它们之间的差值。这个时间戳的单位不太清楚。

@zznzzn 这个是由于编译过程需要从github下载东西，但您的网络有问题，所以编译失败，可以更换源试试。

您可以尝试一下在驱动里面加一些打印信息，看看您这个驱动是否有正常加载，看您这样像是没有把驱动正常加载进去。

@awwwwa 太棒了 能分享移植步驟和源碼嗎 謝謝

看了一下是NES模拟器吧，应该设置RGB555的画布试试看

src.zip

尝试选择其他显示方式，看是否可以切换成功 从log看，SDK包文件夹名字有改动，不确定是否影响。

QQ图片20230828105111.jpg

@lovehex99 @jordonwu 帮各位大佬问过作者本人了，没有套件卖😁

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

@hsinyuwang 在 T113 tina linux 移植 gpsp 模拟器 中说：

大佬

感謝回答

顶起来 顶起来 哈哈

@hsinyuwang 感謝分享 等待後續更新

修改一下lcd_put_ascii函数

void lcd_put_ascii(int x, int y, unsigned char c) { unsigned char *dots = (unsigned char *)&fontdata_8x16[c*16]; int i, b; unsigned char byte; for (i = 0; i < 16; i++) { byte = dots[i]; for (b = 7; b >= 0; b--) { if (byte & (1<<b)) { /* show */ lcd_put_pixel(x+7-b, y+i, 0xffffffff); /* 白 */ } else { /* hide */ lcd_put_pixel(x+7-b, y+i, 0); /* 黑 */ } } } }

@whycan 謝謝 下一步等带模拟器&游戏 烧进去就能玩的固件
哈哈

@ddrddr apt install busybox

想买。。。求量产

以及 有没有结构设计的大佬，求帮忙设计一个酷炫的外壳

液晶触摸屏的框贴合和全贴合是两种不同的屏幕贴合方式：

① 框贴合（Frame Bonding）：框贴合是指将液晶屏与触摸层通过一定的胶水或胶带粘贴在一起，形成一个边框。该方法在屏幕边缘处留有一定的空隙，以容纳胶水或胶带，使得屏幕周围有一条明显的黑色边框。

② 全贴合（Full Lamination）：全贴合是指将液晶屏、触摸层和外层玻璃等贴合物料通过特殊工艺处理，使它们完全贴合在一起。这种方式可以消除层间空气，提高触摸灵敏度和显示效果，并减少光折射，提供更好的视觉体验。全贴合技术通常会使屏幕更薄，没有明显的黑色边框。

综上所述，框贴合和全贴合区别在于贴合方式和效果。框贴合会有明显的黑色边框，而全贴合则实现了更好的视觉和触控效果，没有明显的黑色边框。

音频输出和音频录制

之前在芯片公司的时候，基本没有看过音频这一块，只知道有个alsa框架这么个知识点。要驱动音频，需要两部分，一部分就是底层驱动，一部分就是alsa上层接口，两者缺一不可。对于荔枝派来说，底层的驱动其实都已经包含在linux kernel里面了，客户只要自己port好一个alsa库，或者类alsa库，就可以开始播放音频、录制音频了。

1、电路

电路分成两个部分，一个是mic，也就是麦克风，录制音频用，

27c4b9919eb34cc98650b6ea2db670ef.png

另外一个是headphone，也就是耳机，输出音频用，

fd7814995c2a4cd2be5c48b1a36c5e08.png

不管是哪一个电路，通过观察发现，电路中并没有音频电路经常出现的iis接口。这就说明，v3s和网卡一样，本身已经集成了数模转换和功放功能了，不需要额外芯片了。遇到这种情况，一般soc厂商都会自己默默把驱动代码准备好，省着使用者去二次开发了。毕竟都是自己的东西，驱动写起来也得心应手，不用外人劳神劳力了。

2、设备树

本次使用的内核依然是linux-zero-4.14.y，顶层设备树是 sun8i-v3s-licheepi-zero-dock.dts。查看一下设备树的内容，可以发现声卡驱动已经集成到里面了，

&codec { allwinner,audio-routing = "Headphone", "HP", "Headphone", "HPCOM", "MIC1", "Mic", "Mic", "HBIAS"; status = "okay"; };

当然仅仅有这些还是不够的，进一步阅读sun8i-v3s.dtsi文件，可以看到codec的具体实现细节，

codec: codec@01c22c00 { #sound-dai-cells = <0>; compatible = "allwinner,sun8i-v3s-codec"; reg = <0x01c22c00 0x400>; interrupts = <GIC_SPI 29 IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_CODEC>, <&ccu CLK_AC_DIG>; clock-names = "apb", "codec"; resets = <&ccu RST_BUS_CODEC>; dmas = <&dma 15>, <&dma 15>; dma-names = "rx", "tx"; allwinner,codec-analog-controls = <&codec_analog>; status = "disabled"; }; codec_analog: codec-analog@01c23000 { compatible = "allwinner,sun8i-v3s-codec-analog"; reg = <0x01c23000 0x4>; };

有了这两个配置，基本上声卡驱动就有保证了。好在这些都是默认配置，对于用户来说，就是什么都不需要做，系统上电后，声卡就已经加载好了。

3、判断声卡是否正确加载

判断声卡有没有加载好，主要有两个办法。第一，就是看内核启动日志；第二，就是看/dev/snd下面的节点有没有正确生成。查看日志的话，如果启动ok，应该是可以看到这些打印的，

[ 1.380188] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [ 1.388822] sun6i-rtc 1c20400.rtc: setting system clock to 1970-01-01 00:00:40 UTC (40) [ 1.397167] vcc5v0: disabling [ 1.400142] ALSA device list: [ 1.403106] #0: V3s Audio Codec

不放心日志的话，可以输入ls -l /dev/snd进一步确认下，

# ls -l /dev/snd total 0 crw------- 1 root root 116, 0 Jan 1 00:00 controlC0 crw------- 1 root root 116, 24 Jan 1 00:00 pcmC0D0c crw------- 1 root root 116, 16 Jan 1 00:00 pcmC0D0p crw------- 1 root root 116, 33 Jan 1 00:00 timer

另外，也可以查看下/sys/class/sound下面的节点，也可以算是一种方法，

# cd /sys/class/sound/ # ls card0 controlC0 pcmC0D0c pcmC0D0p timer

不管是哪一种方法，基本上看到这些打印或者节点信息，就可以认为声卡被系统正确加载了。

4、编译安装TinyAlsa

前面我们说过，如果需要让声卡驱动起来，除了驱动本身之外，还需要一个alsa的库。TinyAlsa就是比较适合使用的那个库，下载位置在这，

https://github.com/tinyalsa/tinyalsa

下载好压缩包之后，拷贝到ubuntu虚拟机，直接用arm-linux-gnueabihf-交叉编译器来编译。解压一下，接着cd到解压目录后，直接输入这个命令，

make CROSS_COMPILE=arm-linux-gnueabihf-

不出意外的话，在utils子目录下面，就可以看到四个编译好的工具，

tinycap tinymix tinypcminfo tinyplay

通过观察编译日志，发现这四个程序都是静态链接libtinyalsa.a，所以直接拷贝四个文件即可，不需要拷贝其他动态库。

make -C src make[1]: Entering directory '/home/feixiaoxing/Desktop/tinyalsa-master/src' arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o limits.o limits.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o mixer.o mixer.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o pcm.o pcm.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o pcm_plugin.o pcm_plugin.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o pcm_hw.o pcm_hw.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o snd_card_plugin.o snd_card_plugin.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o mixer_plugin.o mixer_plugin.c arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -c -o mixer_hw.o mixer_hw.c arm-linux-gnueabihf-ar rv libtinyalsa.a limits.o mixer.o pcm.o pcm_plugin.o pcm_hw.o snd_card_plugin.o mixer_plugin.o mixer_hw.o arm-linux-gnueabihf-ar: creating libtinyalsa.a a - limits.o a - mixer.o a - pcm.o a - pcm_plugin.o a - pcm_hw.o a - snd_card_plugin.o a - mixer_plugin.o a - mixer_hw.o arm-linux-gnueabihf-gcc -shared -Wl,-soname,libtinyalsa.so.2 limits.o mixer.o pcm.o pcm_plugin.o pcm_hw.o snd_card_plugin.o mixer_plugin.o mixer_hw.o -o libtinyalsa.so.2.0.0 ln -sf libtinyalsa.so.2.0.0 libtinyalsa.so.2 ln -sf libtinyalsa.so.2 libtinyalsa.so make[1]: Leaving directory '/home/feixiaoxing/Desktop/tinyalsa-master/src' make -C utils make[1]: Entering directory '/home/feixiaoxing/Desktop/tinyalsa-master/utils' arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -O2 -c -o tinyplay.o tinyplay.c arm-linux-gnueabihf-gcc -L ../src -pie tinyplay.o ../src/libtinyalsa.a -ldl -o tinyplay arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -O2 -c -o tinycap.o tinycap.c arm-linux-gnueabihf-gcc -L ../src -pie tinycap.o ../src/libtinyalsa.a -ldl -o tinycap arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -O2 -c -o tinymix.o tinymix.c arm-linux-gnueabihf-gcc -L ../src -pie tinymix.o ../src/libtinyalsa.a -ldl -o tinymix arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include -fPIC -O2 -c -o tinypcminfo.o tinypcminfo.c arm-linux-gnueabihf-gcc -L ../src -pie tinypcminfo.o ../src/libtinyalsa.a -ldl -o tinypcminfo make[1]: Leaving directory '/home/feixiaoxing/Desktop/tinyalsa-master/utils' make -C doxygen make[1]: Entering directory '/home/feixiaoxing/Desktop/tinyalsa-master/doxygen' Makefile:11: "doxygen is not available please install it" make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/feixiaoxing/Desktop/tinyalsa-master/doxygen' make -C examples make[1]: Entering directory '/home/feixiaoxing/Desktop/tinyalsa-master/examples' arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include pcm-readi.c ../src/libtinyalsa.so -ldl -o pcm-readi arm-linux-gnueabihf-gcc -Wall -Wextra -Werror -Wfatal-errors -I ../include pcm-writei.c ../src/libtinyalsa.so -ldl -o pcm-writei make[1]: Leaving directory '/home/feixiaoxing/Desktop/tinyalsa-master/examples'

如何把四个文件拷贝到开发板，这个就不再赘述了。主要还是使用python http库和开发板上的wget命令来共同完成的。

5、寻找音频文件

目前，tinyalsa的工具只能播放wav文件，所以我们还需要找一个可以下载wav文件的网站。这里推荐一个网站链接给大家，

https://www.xmwav.com/

下载好音频文件之后，还是用同样的方法下载到开发板上面。

6、播放音频和录制音频

6.1 播放音频

播放音频的时候，除了正常插入耳机，还有三个地方需要注意下，不然听不到音频输出。第一，就是打开播放开关；第二，设置音量；第三，确认下前面的设置有没有对。这三个步骤都做完了，就可以播放音频了。设置命令主要是tinymix，播放命令是tinyplay。

# ./tinymix set 1 40 # ./tinymix set 2 1 # ./tinymix contents Number of controls: 13 ctl type num name value 0 INT 1 DAC Playback Volume 63 (range 0->63) 1 INT 1 Headphone Playback Volume 40 (range 0->63) 2 BOOL 2 Headphone Playback Switch On, Off 3 INT 1 Mic1 Playback Volume 3 (range 0->7) 4 INT 1 Mic1 Boost Volume 4 (range 0->7) 5 INT 1 ADC Gain Capture Volume 3 (range 0->7) 6 BOOL 2 DAC Playback Switch Off, Off 7 BOOL 2 DAC Reversed Playback Switch Off, Off 8 BOOL 2 Mic1 Playback Switch Off, Off 9 BOOL 2 Mixer Capture Switch Off, Off 10 BOOL 2 Mixer Reversed Capture Switch Off, Off 11 BOOL 2 Mic1 Capture Switch Off, Off 12 ENUM 2 Headphone Source Playback Route > DAC, Mixer, , > DAC, Mixer,

播放刚才下载的音频，

# ./tinyplay test.wav playing 'test.wav': 2 ch, 44100 hz, 16-bit signed PCM

6.2 录制音频

录制音频和播放音频差不多。第一步打开录制开关，第二步确认配置ok。前两步都做好了之后，就可以用tinycap录制音频了，结束录制用ctrl+c，

# ./tinymix set 11 1 # ./tinymix contents Number of controls: 13 ctl type num name value 0 INT 1 DAC Playback Volume 63 (range 0->63) 1 INT 1 Headphone Playback Volume 40 (range 0->63) 2 BOOL 2 Headphone Playback Switch On, Off 3 INT 1 Mic1 Playback Volume 3 (range 0->7) 4 INT 1 Mic1 Boost Volume 4 (range 0->7) 5 INT 1 ADC Gain Capture Volume 3 (range 0->7) 6 BOOL 2 DAC Playback Switch Off, Off 7 BOOL 2 DAC Reversed Playback Switch Off, Off 8 BOOL 2 Mic1 Playback Switch Off, Off 9 BOOL 2 Mixer Capture Switch Off, Off 10 BOOL 2 Mixer Reversed Capture Switch Off, Off 11 BOOL 2 Mic1 Capture Switch On, Off 12 ENUM 2 Headphone Source Playback Route > DAC, Mixer, , > DAC, Mixer, # ./tinycap record.wav Capturing sample: 2 ch, 48000 hz, 16 bit

如果想要确认录制的音频有没有问题，那么直接用tinyplay播放下即可，

# ./tinyplay record.wav playing 'record.wav': 2 ch, 48000 hz, 16-bit signed PCM Played 1601536 bytes. Remains 0 bytes.

@hsinyuwang 终于看到有点i80接口的帖子，此处缺少一个原理图~~ 有机会复刻的话，到时传一个，哈哈哈

@hsinyuwang
想买。。。求量产

可以查阅tools/pack/chips/sun8iw11p1/configs/tlt3_a40i-evm目录下的fex文件。

@steward 感谢司徒的研究，发现了一个大BUG，中断号偏移计算错误，现已修复，打补丁如下：

diff --git a/src/arch/arm32/mach-t113s3/romdisk/boot/mangopi.json b/src/arch/arm32/mach-t113s3/romdisk/boot/mangopi.json index 0f1f34283..4bc02d253 100644 --- a/src/arch/arm32/mach-t113s3/romdisk/boot/mangopi.json +++ b/src/arch/arm32/mach-t113s3/romdisk/boot/mangopi.json @@ -386,12 +386,12 @@ "reset-t113@0x02001d0c": { "reset-base": 1184, "reset-count": 32 }, "irq-gic400@0x03020000": { "interrupt-base": 32, "interrupt-count": 224 }, - "irq-t113-gpio@0x02000220": { "interrupt-base": 224, "interrupt-count": 8, "interrupt-parent": 101 }, - "irq-t113-gpio@0x02000240": { "interrupt-base": 256, "interrupt-count": 8, "interrupt-parent": 103 }, - "irq-t113-gpio@0x02000260": { "interrupt-base": 288, "interrupt-count": 23, "interrupt-parent": 105 }, - "irq-t113-gpio@0x02000280": { "interrupt-base": 320, "interrupt-count": 14, "interrupt-parent": 107 }, - "irq-t113-gpio@0x020002a0": { "interrupt-base": 352, "interrupt-count": 7, "interrupt-parent": 109 }, - "irq-t113-gpio@0x020002c0": { "interrupt-base": 384, "interrupt-count": 16, "interrupt-parent": 111 }, + "irq-t113-gpio@0x02000220": { "interrupt-base": 256, "interrupt-count": 8, "interrupt-parent": 101 }, + "irq-t113-gpio@0x02000240": { "interrupt-base": 288, "interrupt-count": 8, "interrupt-parent": 103 }, + "irq-t113-gpio@0x02000260": { "interrupt-base": 320, "interrupt-count": 23, "interrupt-parent": 105 }, + "irq-t113-gpio@0x02000280": { "interrupt-base": 352, "interrupt-count": 14, "interrupt-parent": 107 }, + "irq-t113-gpio@0x020002a0": { "interrupt-base": 384, "interrupt-count": 7, "interrupt-parent": 109 }, + "irq-t113-gpio@0x020002c0": { "interrupt-base": 416, "interrupt-count": 16, "interrupt-parent": 111 }, "gpio-t113@0x02000030": { "gpio-base": 32, "gpio-count": 8, "interrupt-offset": 256 }, "gpio-t113@0x02000060": { "gpio-base": 64, "gpio-count": 8, "interrupt-offset": 288 },

完整补丁见这个链接
https://github.com/xboot/xboot/commit/4e502b7ad6e4f589832d36a4513de00f0cb8de07

@steward 我只想跟司徒大佬学习一下！😃

@tronlong_support 你好，这个方法修改后的img文件大小也会增大，7个G 的img，烧写一次得用多久

@cj1916
您好，PWM案例目前在计划中。关于PWM设备节点参考附件截图。
3.png 2.png 1.png

@ubuntu

6eac54e2-f9a5-4281-95c9-1458b7c86106-image.png

还有一个IM3的模式设置位😲

@whycan 好的，我稍后买一个试试，谢谢了大神！！！

看看log，确认一下有没有烧进去，以及烧到哪个存储介质去了

@masterlu
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd.conf
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: key_mgmt=0xd0f enc=0xf auth=0x7 flags=0x800d8c0 rrm_flags=0x0 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=5000 max_scan_ssids=9
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 7 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x1dfbdd0 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=04 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0501 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0503 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0504 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=06 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=08 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=09 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=0a multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=11 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1dfbdd0 match=7f multicast=0
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1dfbdd0 match= multicast=0
nl80211: Enable Probe Request reporting nl_preq=0x1e00ea0
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x1e00ea0 match= multicast=0
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
nl80211: Add own interface ifindex 7 (ifidx_reason -1)
nl80211: if_indices[16]: 7(-1)
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: No channel number found for frequency 5920 MHz
nl80211: No channel number found for frequency 5940 MHz
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR)
nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR)
nl80211: 57240-63720 @ 2160 MHz 0 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5170[DISABLED] 5180[DISABLED] 5190[DISABLED] 5200[DISABLED] 5210[DISABLED] 5220[DISABLED] 5230[DISABLED] 5240[DISABLED] 5260[DISABLED] 5280[DISABLED] 5300[DISABLED] 5320[DISABLED] 5500[DISABLED]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
Completing interface initialization
Mode: IEEE 802.11g Channel: 3 Frequency: 2422 MHz
DFS 0 channels required radar detection
nl80211: Set freq 2422 (ht_enabled=0, vht_enabled=0, he_enabled=0, bandwidth=20 MHz, cf1=2422 MHz, cf2=0 MHz)

freq=2422 he_enabled=0 vht_enabled=0 ht_enabled=0 channel_type=0
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
hostapd_setup_bss(hapd=0x1dfb060 (wlan0), first=1)
nl80211: flush -> DEL_STATION wlan0 (all)
Using interface wlan0 with hwaddr f0:c8:14:7b:5a:4b and ssid "hostapd_test"
Deriving WPA PSK based on passphrase
SSID - hexdump_ascii(len=12):
68 6f 73 74 61 70 64 5f 74 65 73 74 hostapd_test
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
random: Got 20/20 random bytes
Get randomness: len=32 entropy=0
GMK - hexdump(len=32): [REMOVED]
Get randomness: len=32 entropy=0
Key Counter - hexdump(len=32): [REMOVED]
WPA: Delay group state machine start until Beacon frames have been configured
nl80211: Set beacon (beacon_set=0)
nl80211: Beacon head - hexdump(len=63): 80 00 00 00 ff ff ff ff ff ff f0 c8 14 7b 5a 4b f0 c8 14 7b 5a 4b 00 00 00 00 00 00 00 00 00 00 64 00 11 04 00 0c 68 6f 73 74 61 70 64 5f 74 65 73 74 01 08 82 84 8b 96 0c 12 18 24 03 01 03
nl80211: Beacon tail - hexdump(len=35): 2a 01 04 32 04 30 48 60 6c 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
nl80211: ifindex=7
nl80211: beacon_int=100
nl80211: beacon_rate=0
nl80211: rate_type=0
nl80211: dtim_period=2
nl80211: ssid=hostapd_test beacon_int=100 dtim_period=2
nl80211: hidden SSID not in use
nl80211: privacy=2
nl80211: auth_algs=0x3
nl80211: wpa_version=0x2
nl80211: key_mgmt_suites=0x2
nl80211: pairwise_ciphers=0x18
nl80211: group_cipher=0x8
wlan0: Deauthenticate all stations at BSS start
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
WPA: Start group state machine to set initial keys
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
Get randomness: len=32 entropy=0
GTK - hexdump(len=32): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
wpa_driver_nl80211_set_key: ifindex=7 (wlan0) alg=2 addr=0x8560c key_idx=1 set_tx=1 seq_len=0 key_len=32 key_flag=0x1a
nl80211: NEW_KEY
nl80211: KEY_DATA - hexdump(len=32): [REMOVED]
broadcast key
nl80211: NL80211_CMD_SET_KEY - default key
nl80211: Set wlan0 operstate 0->1 (UP)
netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
nl80211: TX queue param set: queue=0 aifs=1 cw_min=3 cw_max=7 burst_time=15 --> res=-95
Failed to set TX queue parameters for queue 0.
nl80211: TX queue param set: queue=1 aifs=1 cw_min=7 cw_max=15 burst_time=30 --> res=-95
Failed to set TX queue parameters for queue 1.
nl80211: TX queue param set: queue=2 aifs=3 cw_min=15 cw_max=63 burst_time=0 --> res=-95
Failed to set TX queue parameters for queue 2.
nl80211: TX queue param set: queue=3 aifs=7 cw_min=15 cw_max=1023 burst_time=0 --> res=-95
Failed to set TX queue parameters for queue 3.
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: Setup of interface done.
ctrl_iface not configured!
RTM_NEWLINK: ifi_index=7 ifname=wlan0 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 78:62:56:c1:26:31
nl80211: Assoc Req IEs - hexdump(len=0): [NULL]
wlan0: Event ASSOC (0) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: associated
STA did not include WPS/RSN/WPA IE in (Re)AssocReq
New STA
ap_sta_add: register ap_handle_timer timeout for 78:62:56:c1:26:31 (300 seconds - ap_max_inactivity)
No WPA/RSN IE from STA
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
nl80211: Set STA flags - ifname=wlan0 addr=78:62:56:c1:26:31 total_flags=0x0 flags_or=0x0 flags_and=0xfffffff1 authorized=0
nl80211: sta_remove -> DEL_STATION wlan0 78:62:56:c1:26:31 --> 0 (Success)
ap_free_sta: cancel ap_handle_timer for 78:62:56:c1:26:31
nl80211: Event message available
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 78:62:56:c1:26:31
wlan0: Event DISASSOC (1) received
wlan0: STA 78:62:56:c1:26:31 IEEE 802.11: disassociated
Disassociation notification for unknown STA 78:62:56:c1:26:31

hdmi的分辨率可以指定，也可以使用fb1、fb0双显

我在T3下mcp2515只能发送一帧数据，中断就一直拉低了，用的飞凌的驱动，请帮忙分析下什么原因啊？谢谢@tigger @uuuuid @xiaowenge

@bedrock 好的，谢谢

https://steward-fu.github.io/website/handheld.htm
司徒的教學網站

分類的部分 要看源代碼才會知道 有一些老玩家會知道 MIPS模擬器的意思是使用MIPS汇编做加速 專門跑在MIPS CPU上面的模擬器 例如:reGBA模擬器 是GBA模擬器(ARM晶片) 但是 reGBA是MIPS專用的模擬器。

有些源代碼會包含ARM MIPS X86，但是 不是每個模擬器都會有全部平台的支援，開源模擬器 的缺點是 幾乎沒有說明文件 所以搞起來 比較累，很多東西 都是要看源代碼才會知道是支援什麼平台，不過比較新的模擬器 RetroArch 是使用C/C++ 寫的 因此 很多CPU都可以跑，缺點是過於肥大，大致上是這樣的情況。