页次: 1
idf版本:v3.3 v4.2
esp32开发板:nodemcu,esp32s
问题描述:
esp32作为spi master与stm32g0作为spi slave进行dma 全双工通讯,在26.67MHz时钟下满带宽持续将两个芯片各自32字节的内容使用DMA发送给对方。代码修改自idf的spi master demo,修改寄存器实现SPI_DMA_CONTINUE模式持续将32字节内容发送和接收。
测试发现,在上电开始SPI开始传输后每过161秒接收到的数据都会有一个字节的丢失,导致接收到的数据错位。多次测量或修改寄存器设置后也都是这种现象。如果将时钟改慢为20M则会每215秒丢失一字节。个人推测可能是esp32接收的某种机制导致错开一个字节(8位),否则无法解释为什么每次都会每隔同样的时间、丢失同样大小的(8位bit,一个字节)数据,ESP32发给STM32的数据始终是正确的(MOSI),STM32发给ESP32的数据通过逻辑分析仪确认也没问题(MISO)。
针对这个问题现已调试多日不见解决,还望赐教。
运动捕捉系统GLMocap包括多相机硬件开源方案和上位机软件算法方案的低成本运动捕捉系统。目前设计指标为低成本实现毫米级空间定位,辅助无人机等有室内定位需求的装置和设备。
源码地址:
https://github.com/guanglun/GLMocap
https://gitee.com/guanglunking/GLMocap
OPENVIO摄像头
视频:
[GLMocap开源视觉运动捕捉系统V0.1.0软件基本介绍](https://www.bilibili.com/video/BV1eg411F7gY/)
[GLMocap开源视觉运动捕捉系统轨迹飞行演示](https://www.bilibili.com/video/BV1f44y1t7sN/)
[GLMocap开源视觉运动捕捉系统PX4空间定位](https://www.bilibili.com/video/BV1WM4y1G7vQ/)
[开源视觉运动捕捉GLMocap项目最新进展(2021-8-17)](https://www.bilibili.com/video/BV16L411J7ir/)
图片:
GLDrone是独立自制机架和电调飞控的开源项目,轴距在140左右的小机型,为GLMocap项目的室内飞行与室内编队实验而研发。
GLDrone项目使用MIT协议,代码及机架、电调飞控PCB皆开放源文件。
废话不多说直接上文件:
机架设计文件(使用Fusion360)
电调原理图PCB(立创EDA)
飞控原理图PCB(立创EDA)
修改后的PX4源码
机架设计文件Fusion360分享地址(在线查阅)
飞行及相关测试视频:
【硬核开源】自制运动捕捉我的自制飞行器!自研开源项目GLMocap与GLDrone最新进展
自制机架GLMocap室内定位效果
硬核开源! GLDrone开源四旋翼无人机项目
一些图片:
发一下GLMocap最新的进度,顺便求个赞
开源视觉运动捕捉GLMocap项目最新进展,定位精度1mm左右,PX4飞控控制精度±10cm,速度45fps。视频中为4目同时定位,三个Mark作为定位点提供三维四轴位置和姿态反馈。
运动捕捉系统GLMocap包括多相机硬件开源方案和上位机软件算法方案的低成本运动捕捉系统。目前设计指标为以30帧每秒速度实现毫米级空间定位。
更多开源信息请关注 http://guanglundz.com/mocap
刚发现页面没法贴B站视频,只能给链接了。。
树莓派上有使用DMA实现的软件PWM,如下
https://github.com/xinkaiwang/rpio-pwm
https://stackoverflow.com/questions/50427275/raspberry-how-does-the-pwm-via-dma-work
如此实现了任意GPIO的PWM功能,而且精度也不错,现在想在V3s上实现,不知诸位有何建议?
由于阅读一些开源代码的过程中有一些不方便之处,特在vscode平台下开发了CodeNotes插件辅助阅读和做笔记
CodeNotes(代码笔记)
* 添加注释
* 代码标记
* 快速跳转
* 快速使用
1.打开一个工作区,在该工作区初始化CodeNotes(会在该工作区创建.codenotes文件夹存储标记)
2.在需要做标记的位置(选择需要做标记的文件内容)右击CodeNotes Insert Mark将插入一则标记
3.右侧可编辑标记名称、颜色、描述。描述内容支持markdown,将在鼠标在选择的文字上放置时显示
真鸡儿便宜,能把商家链接发下吗。
https://detail.1688.com/offer/564667023596.html?spm=a360q.8274423.0.0.49c84c9aQ78b8W
承接上贴 https://whycan.cn/t_2760.html
这次在更新了一些软件的基础上硬件新加了铝合金外壳(HUB的)
方案:ESP32+CH374U+CP2102
下载资源
手机APP
源码和资料
ATouch安卓APP源码【开发环境:AndroidStudio】
ATouch WIN&LINUX客户端源码(支持嵌入式LINUX)【开发环境:gcc or MinGW】
ATouch板子源码【开发环境:Linux SDK:ESP-DIF3.2】
ATouch安卓后台程序源码【开发环境:android-ndk-r13b】
说一下存在的问题,铝合金外壳会屏蔽WIFI和蓝牙信号,3米以外基本信号就没了,所以固件升级或者WIFI应用的距离就只能打折扣了。
使用PC端的话,windows还存在问题,最好别用,用linux版本的即可。之前硬件打算用V3s做来着,软硬件都调试ok了,可惜受制于成本和外壳不合适所以下马了这个方案,还是沿用了ESP32的方案。
定价60我感觉还算良心吧,外壳找厂家定了500套(最低了),外壳加上丝印加两端堵头一个八块多,剩余的料多少钱大家也都有个数。
还可以远程控制的,反向控制手机
guanglun 说:checkout 说:触摸事件和你的原理应该一样,延迟高的是图像,scrcpy不只是投屏
移植不难,这是移植到v3s上的效果:https://whycan.cn/t_2736.html这个应该是只读了event吧?
那不错 如果能多点控制就更好了
触摸事件和你的原理应该一样,延迟高的是图像,scrcpy不只是投屏
移植不难,这是移植到v3s上的效果:https://whycan.cn/t_2736.html
这个应该是只读了event吧?
这种投屏的的模拟触摸方式太慢,没有直接写event的方式速度快
先不说废话,资料先甩上来:
ATouch安卓APP源码:https://gitee.com/guanglunking/ATouch 【开发环境:AndroidStudio】
ATouch板子源码:https://gitee.com/guanglunking/ESP32_CH374U 【开发环境:Linux SDK:ESP-DIF3.2】
ATouch安卓后台程序源码: https://gitee.com/guanglunking/ATouchService 【开发环境:android-ndk-r13b】
APP下载地址: https://gitee.com/guanglunking/ATouch/blob/master/app/release/ATouchV1.0.apk
淘宝店铺:https://item.taobao.com/item.htm?id=595635571591
演示视频:https://www.bilibili.com/video/av53687214
说起这个项目的起源,可能大概也许是源于自己用手搓手机菜的抠脚吧,也或许是因为对开发的热情大过于玩的热情哈哈,反正这个东西反反复复得折腾了半年之久了,对这个东西的定位也渐渐从做一个人人都能玩的商品到单纯做一个有吃鸡功能的开发板。现在把他开源出来,也算是回报互联网上良多开源的资料教程吧!
从上面的资料可以看到有三份源码,其中两份(APP和板子源码)还可以理解,另外那个后台源码是啥东西?干啥的?这个还要从实现安卓模拟触屏的功能谈起,主要是因为手机APP无法实现触摸非己界面的功能,而我们有需要在游戏运行的时候触摸屏幕该怎么办呢?解决办法是使用android的ndk开发实现一段后台程序来对触屏文件/dev/input/event进行写操作来实现,所以相对要复杂一些,下面是整个交互的流程概括:
流程说明:
1.CH374U是一个支持8位并口或者SPI的3端USBHUB芯片,将他通过8位并口与ESP32连起来为ESP32实现了3个USB端口的操作。
2.ESP32通过CH374U模拟ADB协议与手机连接,手机需要打开开发者模式。连接成功后使用端口映射 adb forward tcp:local_port tcp:remote_port 来将安卓后台程序ATouchService与开发板ESP32_CH374U建立socket的通讯连接。
3.ESP32通过CH374U采集键盘鼠标数据(USB HID协议),如果已连接手机就将数据打包发送至手机后台程序ATouchService。
4.后台程序ATouchService将接收到的键鼠信息进行处理,如果此时APPATouch配置并开启了键鼠映射就将其键鼠对应的控制信息发送至手机的 /dev/input/event 文件模拟触摸操作。
其实东西早就做好开源出来了,后来感觉不发论坛的话没几个人看得到所以补发一下哈哈。。
更多详细的内容请看上面的博客地址和演示视频。
描述一下问题,nano插上hub,hub上查有鼠标和键盘,鼠标能够cat到动作的时候,按键盘按键会有如下打印信息:
[ 89.010405] usb 1-1.4: USB disconnect, device number 10
[ 89.270521] usb 1-1.4: new low-speed USB device number 11 using sunxi_hcd_host0
[ 89.411022] input: SIGMACH1P USB Keykoard as /devices/soc.0/1c13000.otghci0-controller/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
[ 89.441648] hid-generic 0003:1C4F:0002.0010: input,hidraw1: USB HID v1.10 Keyboard [SIGMACH1P USB Keykoard] on usb-1c13000.otghci0-controller-1.4/input0
[ 89.477534] input: SIGMACH1P USB Keykoard as /devices/soc.0/1c13000.otghci0-controller/usb1/1-1/1-1.4/1-1.4:1.1/input/input18
[ 89.511491] hid-generic 0003:1C4F:0002.0011: input,hidraw2: USB HID v1.10 Device [SIGMACH1P USB Keykoard] on usb-1c13000.otghci0-controller-1.4/input1
lsusb:
# lsusb
Bus 001 Device 002: ID 05e3:0610
Bus 001 Device 001: ID 1d6b:0001
Bus 001 Device 003: ID 09da:c10a
Bus 001 Device 011: ID 1c4f:0002
简单总结一下编译BSP的步骤
按照 step by step 编译全志 f1c100s 官方linux bsp 装好编译环境需要的软件
然后更新一下awk
sudo apt-get install gawk
更新依据 https://blog.csdn.net/dpppppp/article/details/53018132下载源代码包并解压,第一楼里面的有链接
@assert 大神的f1c100s.tar.bz2代码包里面,需要将linux-3.10/drivers/mtd/devices/m25p80.c恢复原来的文件,@assert的代码包对spi做了分区处理,但和原厂bsp冲突,所以要恢复
还有,如果用@assert的包,需要重新下载buildroot/dl目录里面的文件(nano官方的包是文件最齐全的,可以用nano官方的包里面的文件)进入解压目录,执行./build.sh,运行过程中有三次出错,参照下面的链接修正错误
https://blog.csdn.net/laohuang1122/article/details/44098291/build完成后,运行./build.sh pack 生成镜像文件
镜像文件 tools/pack/sunivw1p1_linux_evb_uart0.img,用全志的工具刷进去nano就可以了
这个镜像文件有29M多,实际上包含了spi系统用的16M镜像和sd卡用的镜像,全志的工具可以自动识别具体环境刷镜像(我尝试刷sd卡,能正常刷完成,但sd卡启动到内核,显示start kernel就停住了,因为我计划用spi,所以没有继续研究下去)
如果用sunxi-fel.exe来刷,直接找tools/pack/out/full_img.fex这个文件,这个就是spi用的镜像如果接串口调试,要接uart1
之前我一直接uart0,看代码包里面也针对nano硬件改了设备树的参数,以为是uart0,一直没输出,没找到问题,后来是晕哥提醒我用其他uart试一下,结果发现官方的bsp是用uart1的
我用一楼的bsp build & pack之后直接sunxi-fel 你说的那个full_img.fex看到log在内核启动处卡住了:
read partition: boot or recovery
boota: bad boot image magic, maybe not a boot.img?
try to read partition(boot) all
[ 0.653]sunxi flash read :offset 4000, 2359296 bytes OK
## Booting kernel from Legacy Image at 80007800 ...
Image Name: Linux-3.10.65
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2313480 Bytes = 2.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ...
OK
## Transferring control to Linux (at address 80008000)...
arch/arm/lib/bootm.c 72 Starting kernel ...
--r2 0x8096e120,images->ft_len= = 0 , working_fdt = 8096e120, bi_boot_params = 0
你直接烧写你直接用sunxi-fel烧写spiflash没遇到这种情况吗?
解决方法:
1.
/bin/bash: 行 2: /lichee/out/sun8iw8p1/linux/common/buildroot/external-toolchain/bin/arm-linux-gnueabi-gcc: 没有那个文件或目录在网上查了一下,大概说是我的系统是64位的,而这个程序是32位的,存在兼容问题,需要安装lsb-core,即命令sudo apt-get install lsb-core。
2.但是在这之后又有了新的问题:
./arm-linux-gnueabi-gcc: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory这个问题安装一下下面软件就好了。
apt-get install lib32z1 lib32ncurses5
apt-get install lib32stdc++6有几个问题需要处理。
我编译也遇到了这种情况:
read partition: boot or recovery
boota: bad boot image magic, maybe not a boot.img?
try to read partition(boot) all
[ 0.653]sunxi flash read :offset 4000, 2359296 bytes OK
## Booting kernel from Legacy Image at 80007800 ...
Image Name: Linux-3.10.65
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2313480 Bytes = 2.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ...
OK
## Transferring control to Linux (at address 80008000)...
arch/arm/lib/bootm.c 72 Starting kernel ...
--r2 0x8096e120,images->ft_len= = 0 , working_fdt = 8096e120, bi_boot_params = 0
然后就一直不动了,
晕哥怎么解决的啊!
Nano f1c100s 使用网盘中linux固件:Nano_tf_800480.dd,进入系统后执行mplayer /test/fuchouzhe.mp4,屏幕无反应,现象如下:
# mplayer /test/fuchouzhe.mp4
MPlayer 1.3.0-4.8.3 (C) 2000-2016 MPlayer Team
Playing /test/fuchouzhe.mp4.
libavformat version 57.25.100 (internal)
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f2af8]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
[lavf] stream 0: video (mpeg4), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang und
VIDEO: [MP4V] 800x480 24bpp 18.000 fps 383.7 kbps (46.8 kbyte/s)
Could not find a UTF-8 locale,
character keys beyond Latin-1 will not be handled.
vo: couldn't open the X11 display ()!
VO XOverlay need a subdriver
[VO_SDL] SDL initialization failed: Unable to open mouse.
notice: Can't open /dev/tty: No such device or address
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 57.24.102 (internal)
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
Clip info:
major_brand: isom
minor_version: 1
compatible_brands: isom
creation_time: 2018-06-04 07:27:46
encoder: FormatFactory : www.pcfreetime.com
Load subtitles in /test/
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 22050 Hz, 2 ch, floatle, 64.8 kbit/4.59% (ratio: 8098->176400)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [oss] 22050Hz 2ch s16le (2 bytes per sample)
Starting playback...
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]bicubic scaler, from yuv420p to bgra using C
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
[swscaler @ 0xa36cc0]using unscaled yuv420p -> bgra special converter
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from
MPlayer interrupted by signal 2 in module: decode video
Movie-Aspect is 1.67:1 - prescaling to correct movie aspect.
[swscaler @ 0xa36cc0]No accelerated colorspace conversion found from yuv420p to bgra.
VO: [fbdev] 800x480 => 800x480 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
看起来是屏幕的问题,执行echo 123 >/dev/fb0屏幕无反应,只有Log信息和光标显示在LCD上,求助大侠解决思路!
页次: 1