MR Series

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

登录以发帖

各位大佬，有遇到过取指令访问错误异常么，是怎么触发的啊？
发布于 • zznzzn

0 赞同

0 回复

314 浏览

尚无回复

0
U

t113求助各位大佬：mmp sample在哪里配置呢在menuconfig似乎没有找到
发布于 • Uccccc

0 赞同

0 回复

633 浏览

尚无回复

0
J

全志D1烧录固件以后系统起不来
发布于 • jzxzky

0 赞同

7 回复

1616 浏览

 回复于

测试一下串口模块是不是好的

7
Y

请教T113S3串口2（PD1和PD2）和LCD引脚冲突
发布于 • yelong98

0 赞同

2 回复

1125 浏览

Y 回复于

@awwwwa 多谢指导，已经解决，整个clean以后重编就生效了，搞不懂之前咋回事，好在最后解决了

2
Q

D1S驱动MIPI屏幕怎么设置？求大佬帮助
发布于 • q2022

0 赞同

8 回复

3234 浏览

X 回复于

@xiaochusheng
mipi点亮大佬方便指导下吗，q951196174

8
K

T113 SPI无法通讯问题
发布于 • kaifan

0 赞同

0 回复

634 浏览

尚无回复

0
L

D1-H 使能spi0和spi1的问题
发布于 • lbuque

0 赞同

10 回复

2716 浏览

K 回复于

所以楼主最后怎么解决的，我也遇到了这个问题

10
L

D1s芯片烧录melis固件启动报错，大家帮我看看咋回事
发布于 • liu11372650

0 赞同

1 回复

878 浏览

A 回复于

@liu11372650 在 D1s芯片烧录melis固件启动报错，大家帮我看看咋回事中说：

0x000000004003049c

根据这个地址，objdump出来elf去找一下是哪一个函数报错

1
Q

D1s读取nor flash导致音频的DMA出问题
发布于 • qinchangzu

0 赞同

1 回复

831 浏览

Q 回复于

已解决，之前修改了底层的hal_dma.c中的中断回调函数导致的

1
H

T113-S3 Mango MQ-R Wi-Fi 8723ds 问题
发布于 • hongduc10

0 赞同

2 回复

1642 浏览

S 回复于

@gonboy 现在芒果的店里应该不卖了，到闲鱼上找找应该有

2
SDK的开发环境必须是Ubuntu14.04吗？
发布于 • houxc01

0 赞同

1 回复

698 浏览

 回复于

@houxc01 WSL2下用docker很方便

1
G

D1 Opensbi 直接启动内核
发布于 • geniusz

0 赞同

0 回复

559 浏览

尚无回复

0
N

tina SDK编译的buildroot文件系统，如何更改只读属性？
发布于 • NLJ_Moon

0 赞同

2 回复

1046 浏览

N 回复于

@awwwwa Tina 的SDK不是还能编译buildroot吗，文件系统咋buildroot上编译的

2
J

全志D1编译报错
发布于 • jzxzky

1 赞同

2 回复

843 浏览

 回复于

用的是哪个linux版本呢？

2
C

RGB的七寸屏（分辨率1024，600）配置后无法正常显示
发布于 • CHENNENGBIAO

0 赞同

5 回复

1771 浏览

 回复于

@ggk1989
感谢分享宝贵经验。

5
G

D1 内核设备树
发布于 • geniusz

1 赞同

1 回复

705 浏览

 回复于

@geniusz
那就按打包规则一起更新。

1
X

关于D1s,请问哪块板子最适合入门学习
发布于 • xmxjh

0 赞同

2 回复

734 浏览

X 回复于

@whycan 韦老师这个板子学习视频更了3个就停了，停更了几个月，纠结啊

2
T

在D1的tina上整上overlayfs
发布于 • TEVET

1 赞同

41 回复

13224 浏览

K 回复于

@qinhao4832 文档：D1(改T113)Tina 系统解决系统只读问题....
链接：http://note.youdao.com/noteshare?id=5278bec1c63e459ec38de1ee8fe86919&sub=3D0097C0B2034663AD93C73DAB922AD2

41
M

是不是驱动开启旋转之后，就没有/dev/fb0了？
发布于 • memory

0 赞同

1 回复

964 浏览

 回复于

感觉没有/dev/fb0，需要在应用刷屏的地方调用驱动的FBIOPAN_DISPLAY接口，同步旋转后的buffer才会显示到LCD上。

1
G

D1 用Xfel启动不了内核
发布于 • geniusz

0 赞同

3 回复

1255 浏览

A 回复于

@geniusz 自带的uboot的bootm命令会自动解压，主线的需要自行配置

3
A

D1s i80 接 ST7789V uboot有显示进入 Linux 没显示黑屏了
发布于 • awwwwa

0 赞同

1 回复

999 浏览

A 回复于

@awwwwa 在 D1s i80 接 ST7789V uboot有显示进入 Linux 没显示黑屏了中说：

lcd_gpio_0 = <&pio PD 0 GPIO_ACTIVE_LOW>;

配置成 lcd_gpio_0 = <&pio PD 0 GPIO_ACTIVE_HIGH>; 解决，Uboot 初始化后又拉低了rst脚

1
M

D1s可以实现 LCD + TV 双屏异显吗？
发布于 • memory

0 赞同

1 回复

774 浏览

 回复于

可以实现

1
芒果派MangoPi MQ Pro构建sqlite3并进行性能测试
发布于 • bayche

0 赞同

1 回复

1185 浏览

Y 回复于

不错.
学习学习.

1
K

mq-r t113 ov5640适配
发布于 • kw___

3 赞同

14 回复

5941 浏览

G 回复于

能否提供下，测试ov5640通过的如下文件。测试一直不通过：
/home/hi/TLinux/device/config/chips/t113/configs/mq_r/linux-5.4/board.dts /home/hi/TLinux/device/config/chips/t113/configs/mq_r/linux-5.4/config-5.4 /home/hi/TLinux/target/allwinner/t113-mq_r/defconfig

14
D

启动到这里停止了，是不是dram坏了？
发布于 • dort91011

0 赞同

4 回复

1303 浏览

A 回复于

@dort91011 请问使用的固件是哪一份

4
C

芒果派 MQ-Dual T113 官方镜像无法启动
发布于 • center1056

0 赞同

0 回复

579 浏览

尚无回复

0
D1 Tina-SDK V2.1编译直接报错！
发布于 • 100ask

0 赞同

5 回复

1974 浏览

B 回复于

@whycan 谢谢大佬！

5
A

按照官方文档去配置spinand切换spinor报错
发布于 • abcdef

0 赞同

2 回复

1078 浏览

 回复于

最好还是详细描述下修改的步骤以及详细的烧录、启动log，才好分析

2
H

D1-h开机时间最短能做到多少？
发布于 • haaland

0 赞同

2 回复

1002 浏览

Z 回复于

@livpo 怎么能做到两秒啊，有资料吗，谢谢

2
L

D1-H v2.1 SDK问题
发布于 • litengos

0 赞同

3 回复

1297 浏览

 回复于

下载 tina v2.1

3
J

Tina sdk(t113) 更改uart_debug口后，debug信息打印不全
发布于 • jr_online

0 赞同

10 回复

3054 浏览

G 回复于

@jr_online 这样改，测试通过了吗？

10
Lichee RV Dock的 type-c 支持网口吗？
发布于 • zznzzn

0 赞同

1 回复

875 浏览

 回复于

usb可以用 usb千兆网卡试试，理论上可以，实操应该会很多坑

1
B

d1s和t113在供电有啥区别？
发布于 • bigfly

0 赞同

1 回复

1029 浏览

 回复于

@bigfly 在 d1s和t113在供电有啥区别？中说：

这款板子可以直接替换吗?

可以直接pin to pin替换

1
S

求教，D1s uboot烧写问题。
发布于 • siguadao

0 赞同

17 回复

4605 浏览

Z 回复于

@siguadao 您好，我也遇到了相同的问题，请问您解决了吗

17
G

T113麻雀，TF卡启动，经常卡死
发布于 • gonboy

0 赞同

4 回复

1673 浏览

G 回复于

@whycan 1. 没有文件，在ext4分区，进行启动加载。
2. 这种现象，貌似是对 29G的空间进行，格式化。（偶尔会启动慢）
can't run '/etc/preinit': No such file or directory mount: mounting proc on /proc failed: Resource busy mount: mounting tmpfs on /run failed: No such file or directory hostname: can't open '/etc/hostname': No such file or directory ------run rc.preboot file----- [ 6.412934] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: (null) ------run rc.modules file----- insmod: can't insert '/lib/modules/5.4.61/usb-storage.ko': No such file or directory [ 6.467474] sunxi_gpadc_init,2151, success [ 6.472441] sunxi_gpadc_setup: get channel scan data failed [ 6.479050] input: sunxi-gpadc0 as /devices/virtual/input/input1 [ 6.491148] get ctp_power is fail, -22 [ 6.495359] get ctp_power_ldo_vol is fail, -22 [ 6.500392] sunxi_ctp_startup: ctp_power_io is invalid. [ 6.506288] get ctp_gesture_wakeup fail, no gesture wakeup [ 6.512475] gt9xxnew_ts 2-0014: 2-0014 supply ctp not found, using dummy regulator [ 6.709604] input: gt9xxnew_ts as /devices/virtual/input/input2 [ 6.996971] sunxi-rfkill soc@3000000:rfkill@0: wlan power on success [ 7.104136] sunxi-rfkill soc@3000000:rfkill@0: bus_index: 1 [ 7.110433] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B [ 7.122094] sunxi-mmc 4021000.sdmmc: no vqmmc,Check if there is regulator [ 7.142279] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 7.167200] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 7.182888] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B [ 7.196179] sunxi-mmc 4021000.sdmmc: card claims to support voltages below defined range [ 7.214867] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B [ 7.226470] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B [ 7.238313] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 4 timing SD-HS(SDR25) dt B [ 7.250839] mmc1: new high speed SDIO card at address 0001 Successfully initialized wpa_supplicant ------run rc.final file----- mount: mounting /dev/mmcblk0p1 on /mnt/extsd failed: No such file or directory

4
H

d1h的怎么开启矢量指令的支持
发布于 • haaland

0 赞同

2 回复

874 浏览

B 回复于

请问您会开启矢量指令的支持了吗？我也正在尝试解决这方面的问题

2
B

全志D1怎么开启V指令？并且正常使用？
发布于 • Brucelee24

0 赞同

0 回复

476 浏览

尚无回复

0
Z

T113-Pro开发板连接mipi屏幕，屏幕总是不亮
发布于 • z15612417860

1 赞同

2 回复

1393 浏览

K 回复于

lcd_driver_name改为tft08006
7c874b5e-bd57-4585-8613-89e433584a06-image.png

另外，驱动代码里将name也改为tft08006

3c3d3e63-e968-4d31-b9a6-1e588414db36-image.png

2
G

麻雀T113-s3, 触摸屏错误，总是提示
发布于 • gonboy

0 赞同

0 回复

669 浏览

尚无回复

0
G

增加Package, 生成的so 无法自动添加到 /usr/lib中
发布于 • gonboy

1 赞同

1 回复

873 浏览

 回复于

@gonboy

试一试这个，用buildroot：

--来自百度网盘超级会员V4的分享
hi，这是我用百度网盘分享的内容~复制这段内容打开「百度网盘」APP即可获取
链接:https://pan.baidu.com/s/1tADvigD1xtOWqieJmcuPkA?pwd=awol
提取码:awol

1
Z

Pack Error: F133-mq_r打包时出现no user resource partitions
发布于 • zhang21st

2 赞同

1 回复

771 浏览

尚无回复

1
N

服务平台D1-H的文档怎么没了以前有很多文档的
发布于 • nikola

0 赞同

1 回复

682 浏览

 回复于

D1文档从全志客户服务平台下架了，后续文档会从你看到的这个在线文档的地址（https://d1.docs.aw-ol.com/ ）发出&更新，这里的文档会更适合个人开发者和入门小白。

1
A

T113-S3 配置横屏显示系统跑不起来问题
发布于 • AW20221130

0 赞同

2 回复

1217 浏览

A 回复于

@whycan 在 T113-S3 配置横屏显示系统跑不起来问题中说：

横屏没有问题的，现在正常竖屏可以了吗？
因为这个驱动芯片自带GRAM，所以不需要soc参与也很容易各种旋转。

目前竖屏能显示了，但是有这种竖纹阴影显示，你看下图片，这种问题怎么解决？
屏幕异常.png

你所说的ST7701S自带GRAM，不需要soc参与也很容易各种旋转。那是不是在初始化代码里配置，
我把屏幕厂商给的初始化代码发出来，帮忙看看怎么修改的。多谢~~
SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x13); SPI_WriteComm(0xEF); SPI_WriteData(0x08); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x10); SPI_WriteComm(0xC0); SPI_WriteData(0x77); SPI_WriteData(0x00); SPI_WriteComm(0xC1); SPI_WriteData(0x0C); SPI_WriteData(0x0C); SPI_WriteComm(0xC2); SPI_WriteData(0x07); SPI_WriteData(0x02); SPI_WriteComm(0xCC); SPI_WriteData(0x10); SPI_WriteComm(0xB0); SPI_WriteData(0x00); SPI_WriteData(0x0C); SPI_WriteData(0x19); SPI_WriteData(0x0B); SPI_WriteData(0x0F); SPI_WriteData(0x06); SPI_WriteData(0x05); SPI_WriteData(0x08); SPI_WriteData(0x08); SPI_WriteData(0x1F); SPI_WriteData(0x04); SPI_WriteData(0x11); SPI_WriteData(0x0F); SPI_WriteData(0x26); SPI_WriteData(0x2F); SPI_WriteData(0x1D); SPI_WriteComm(0xB1); SPI_WriteData(0x00); SPI_WriteData(0x17); SPI_WriteData(0x19); SPI_WriteData(0x0F); SPI_WriteData(0x12); SPI_WriteData(0x05); SPI_WriteData(0x05); SPI_WriteData(0x08); SPI_WriteData(0x07); SPI_WriteData(0x1F); SPI_WriteData(0x03); SPI_WriteData(0x10); SPI_WriteData(0x10); SPI_WriteData(0x27); SPI_WriteData(0x2F); SPI_WriteData(0x1D); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x11); SPI_WriteComm(0xB0); SPI_WriteData(0x4D); SPI_WriteComm(0xB1); SPI_WriteData(0x4F); SPI_WriteComm(0xB2); SPI_WriteData(0x82); SPI_WriteComm(0xB3); SPI_WriteData(0x80); SPI_WriteComm(0xB5); SPI_WriteData(0x4E); SPI_WriteComm(0xB7); SPI_WriteData(0x85); SPI_WriteComm(0xB8); SPI_WriteData(0x20); SPI_WriteComm(0xC1); SPI_WriteData(0x78); SPI_WriteComm(0xC2); SPI_WriteData(0x78); SPI_WriteComm(0xD0); SPI_WriteData(0x88); SPI_WriteComm(0xE0); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x02); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x0C); SPI_WriteComm(0xE1); SPI_WriteData(0x02); SPI_WriteData(0x8C); SPI_WriteData(0x04); SPI_WriteData(0x8C); SPI_WriteData(0x01); SPI_WriteData(0x8C); SPI_WriteData(0x03); SPI_WriteData(0x8C); SPI_WriteData(0x00); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE2); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x03); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0xD4); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0xD4); SPI_WriteData(0x00); SPI_WriteComm(0xE3); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x33); SPI_WriteData(0x33); SPI_WriteComm(0xE4); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE5); SPI_WriteData(0x09); SPI_WriteData(0xD2); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x0B); SPI_WriteData(0xD4); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x05); SPI_WriteData(0xCE); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x07); SPI_WriteData(0xD0); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteComm(0xE6); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x33); SPI_WriteData(0x33); SPI_WriteComm(0xE7); SPI_WriteData(0x44); SPI_WriteData(0x44); SPI_WriteComm(0xE8); SPI_WriteData(0x08); SPI_WriteData(0xD1); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x0A); SPI_WriteData(0xD3); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x04); SPI_WriteData(0xCD); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteData(0x06); SPI_WriteData(0xCF); SPI_WriteData(0x35); SPI_WriteData(0x8C); SPI_WriteComm(0xEB); SPI_WriteData(0x00); SPI_WriteData(0x01); SPI_WriteData(0xE4); SPI_WriteData(0xE4); SPI_WriteData(0x44); SPI_WriteData(0x33); SPI_WriteComm(0xED); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteData(0xF7); SPI_WriteData(0x65); SPI_WriteData(0x4A); SPI_WriteData(0x10); SPI_WriteData(0x3B); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteData(0xB3); SPI_WriteData(0x01); SPI_WriteData(0xA4); SPI_WriteData(0x56); SPI_WriteData(0x7F); SPI_WriteData(0xFF); SPI_WriteData(0xFF); SPI_WriteComm(0xEF); SPI_WriteData(0x10); SPI_WriteData(0x0D); SPI_WriteData(0x04); SPI_WriteData(0x08); SPI_WriteData(0x3F); SPI_WriteData(0x1F); SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteComm(0x3A); SPI_WriteData(0x55); SPI_WriteComm(0x11); Delay(120); SPI_WriteComm(0x29); //自检模式 /* SPI_WriteComm(0xFF); SPI_WriteData(0x77); SPI_WriteData(0x01); SPI_WriteData(0x00); SPI_WriteData(0x00); SPI_WriteData(0x12); SPI_WriteComm(0xD1); SPI_WriteData(0x81); SPI_WriteComm(0xD2); SPI_WriteData(0x08); */

2
X

gadget做HID键盘报错
发布于 • xjy_5

0 赞同

0 回复

606 浏览

尚无回复

0
F

f133增加驱动未编译进固件中
发布于 • furyfangyu

0 赞同

0 回复

671 浏览

尚无回复

0
J

移植到全志D1-H开发板，找不到MMIO
发布于 • jaddyk

0 赞同

0 回复

439 浏览

尚无回复

0
X

全志D1烧写中断，开机卡[180]Loading boot-pkg fail(error=2)
发布于 • xjy_5

0 赞同

5 回复

1812 浏览

X 回复于

@moider 固件对了照这个教程https://d1.docs.aw-ol.com/study/study_4compile/ 的按住fel按键烧写

5
S

uart寄存器问题
发布于 • sfgy125110

0 赞同

2 回复

1081 浏览

S 回复于

@awwwwa 感谢感谢，翻手册的时候没注意到这一段，下次看手册要仔细点了49ad5c58-e407-4fe3-b775-a823ad8ce477-40e311d4-9b3b-4bf8-842a-3eec031002b7.png

2
P

d1-h是不支持KGDB吗？
发布于 • pineappleman

0 赞同

0 回复

439 浏览

尚无回复

0
X

修改了串口的波特率后uboot阶段乱码
发布于 • xingcongying

0 赞同

2 回复

1065 浏览

 回复于

uboot也需要配置对应的波特率，因为UART是boot0初始化的，进入UBOOT所计算的时钟如果没有修改就会出现乱码

2
L

T113裸跑不能产生中断请教：
发布于 • L13819506056

0 赞同

11 回复

3409 浏览

L 回复于

@l13819506056 你好，这段代码加在启动文件的哪个位置啊

11
L

芒果派 MQ-R T113 无法启动
发布于 • llqzx

0 赞同

5 回复

2129 浏览

C 回复于

@llqzx 在芒果派 MQ-R T113 无法启动中说：

https://mangopi.org/mqr

我也有同样的问题，使用尝试了官方的两个镜像8723和8189，包括自己跟着mangopi官方在ubuntu18下编译的固件，都会死在最后busybox提示这块，不知道怎么解决了。

5
L

D1s 无法从EMMC启动
发布于 • lvjun0728

0 赞同

9 回复

3151 浏览

L 回复于

@whycanservice 我替换了你的内核配置，可以正常启动了。应该默认的是nand的配置不支持emmc

9
C

USB Camera demo代码包问题
发布于 • Cool_Sir

0 赞同

2 回复

863 浏览

C 回复于

@whycanservice

解压出来了，谢谢

7a9f98d5-adc2-4f6a-a024-18bf1291305d-image.png

2
S

我的程序可以搜索出来，但是设置里看不到
发布于 • SongXuanYu

0 赞同

1 回复

579 浏览

S 回复于

@songxuanyu
哎呀，这个软件包make依赖那个位置多了个空格，所以是可以搜索到，但是勾选不了，make改正后就可以看到了。

1
播放wav的音频文件没有问题，播放视频mp4异常
发布于 • zznzzn

0 赞同

1 回复

601 浏览

S 回复于

@zznzzn 我也碰到过，当时是我的音频设置不对。

1
T

因为喜欢用ADB，因为不喜欢插拔TF卡，所以D1直接用PhoenixSuit烧录TF(SDNAND)
发布于 • TEVET

3 赞同

15 回复

7119 浏览

L 回复于

正想找这个，感谢分享

15
L

D1H 使用OV5640 报错
发布于 • liangjian

0 赞同

4 回复

1931 浏览

 回复于

D1-H （MQ-Pro）驱动 OV5640 摄像头
https://bbs.aw-ol.com/topic/4017/share/1

4
M

T113 摄像头无法打开
发布于 • myamoroso

0 赞同

2 回复

1439 浏览

 回复于

d4f0c2b4-9d2b-4283-9f1c-1a9a7b676e37-w.png

配置两个okay

参考：

D1-H （MQ-Pro）驱动 OV5640 摄像头
https://bbs.aw-ol.com/topic/4017/share/1

2
G

D1 的sdk包无法下载
发布于 • geniusz

0 赞同

1 回复

644 浏览

 回复于

新 SDK 平台下载 D1-H/D1s SDK
https://bbs.aw-ol.com/topic/3947/share/1

1
L

哪吒d1-h开发板mmap /dev/mem设备，gdb不能访问
发布于 • liuruyi

0 赞同

0 回复

512 浏览

尚无回复

0
H

编译错误，在进行make -j32时出现错误
发布于 • hanky

0 赞同

0 回复

281 浏览

尚无回复

0
K

MQ-Pro D1-H ov5640适配
发布于 • kw___

1 赞同

2 回复

1779 浏览

A 回复于

我现在在用MQ Pro + OV5640做项目，大佬是否愿意加我QQ？

2
D

adb 和usb虚拟串口的切换
发布于 • ddrddr

0 赞同

1 回复

1017 浏览

 回复于

adb用functionfs实现的
setusbconfig none, 再insmod g_serial.ko看看
不行再加一句 echo "" > /sys/kernel/config/usb_gadget/g1/UDC

1
Y

芒果派MangoPi MQ Pro+Tina Linux 开发环境搭建
发布于 • giao

0 赞同

0 回复

856 浏览

尚无回复

0
Z

有关编译c内联矢量指令时，unknown register name ‘v1’ in ‘asm’的问题
发布于 • zny666

0 赞同

17 回复

3933 浏览

 回复于

@zny666
可能里面有不支持的指令。

17
M

D1哪吒v1.2版本原理图与PCB源文件可以下载了
哪吒原理图 • 发布于 • memory

1 赞同

4 回复

2264 浏览

L 回复于

用什么文件打开的哦

4
J

T113 tina GPADC怎么用来电压测量呀？
发布于 • jr_online

0 赞同

6 回复

2056 浏览

J 回复于

@jr_online 电压采集做了没？怎么做的？

6
A

t113使用spinandflash作为存储介质往文件系统中复制文件一直提示空间不足
发布于 • ah669741

0 赞同

10 回复

2436 浏览

A 回复于

@whycanservice 把rootfs下面的所有分区都注释了就好了

10
A

有偿求芒果派MQ Pro全志D1 H主控驱动DVP OV5640
发布于 • AbuzzHarbor9999

0 赞同

1 回复

838 浏览

A 回复于

以下是I2C报错
root@TinaLinux:/lib/modules/5.4.61# i2cdetect 2 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-2. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 [ 7426.138537] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 9 a b c d e f 00: [ 7426.149268] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3) -- [ 7426.159610] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.168022] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4) -- [ 7426.175631] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.183924] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5) -- [ 7426.191503] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.199812] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6) -- [ 7426.207420] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.215712] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x7) -- [ 7426.223294] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.231584] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x8) -- [ 7426.239181] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.247531] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x9) -- [ 7426.255143] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.263414] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xa) -- [ 7426.271059] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.279329] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xb) -- [ 7426.286972] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.295239] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xc) -- [ 7426.302855] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.311132] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xd) -- [ 7426.318768] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.327043] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xe) -- [ 7426.334684] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.342952] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0xf) -- [ 7426.350615] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 10: [ 7426.358867] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x10) -- [ 7426.367095] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.375370] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x11) -- [ 7426.383063] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.391339] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x12) -- [ 7426.399062] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.407366] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x13) -- [ 7426.415125] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.423393] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x14) -- [ 7426.431098] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.439437] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x15) -- [ 7426.447157] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.455445] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x16) -- [ 7426.463123] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.471417] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x17) -- [ 7426.479120] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.487413] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x18) -- [ 7426.495117] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.503405] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x19) -- [ 7426.511119] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.519407] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1a) -- [ 7426.527111] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.535404] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1b) -- [ 7426.543082] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.551370] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1c) -- [ 7426.559071] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.567363] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1d) -- [ 7426.575070] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.583354] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1e) -- [ 7426.591059] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.599333] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x1f) -- [ 7426.607084] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 20: [ 7426.615424] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x20) -- [ 7426.623546] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.631819] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x21) -- [ 7426.639554] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.647830] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x22) -- [ 7426.655566] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.663844] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x23) -- [ 7426.671538] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.679817] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x24) -- [ 7426.687549] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.695827] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x25) -- [ 7426.703520] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.711796] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x26) -- [ 7426.719527] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.727805] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x27) -- [ 7426.735540] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.743819] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x28) -- [ 7426.751512] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.759792] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x29) -- [ 7426.767544] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.775822] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2a) -- [ 7426.783500] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.791792] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2b) -- [ 7426.799495] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.807788] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2c) -- [ 7426.815488] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.823801] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2d) -- [ 7426.831479] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.839771] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2e) -- [ 7426.847475] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.855767] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x2f) -- [ 7426.863490] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x30) 30: [ 7426.871387] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x31) -- [ 7426.879438] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x32) -- -- [ 7426.887322] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x33) -- [ 7426.895381] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x34) -- [ 7426.903255] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x35) -- [ 7426.911146] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x36) -- [ 7426.919077] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x37) -- [ 7426.926949] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.935260] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x38) -- [ 7426.942939] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.951224] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x39) -- [ 7426.958963] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.967237] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3a) -- [ 7426.974978] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.983246] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3b) -- [ 7426.990985] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7426.999256] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3c) -- [ 7427.006997] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.015273] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3d) -- [ 7427.022965] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.031258] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3e) -- [ 7427.038989] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.047266] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x3f) -- [ 7427.055023] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 40: [ 7427.063280] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x40) -- [ 7427.071507] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.079777] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x41) -- [ 7427.087516] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.095793] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x42) -- [ 7427.103504] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.111779] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x43) -- [ 7427.119476] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.127764] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x44) -- [ 7427.135475] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.143769] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x45) -- [ 7427.151446] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.159742] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x46) -- [ 7427.167448] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.175740] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x47) -- [ 7427.183418] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.191709] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x48) -- [ 7427.199408] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.207700] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x49) -- [ 7427.215406] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.223691] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4a) -- [ 7427.231399] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.239700] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4b) -- [ 7427.247405] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.255700] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4c) -- [ 7427.263379] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.271673] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4d) -- [ 7427.279371] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.287699] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4e) -- [ 7427.295441] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.303710] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x4f) -- [ 7427.311495] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x50) 50: [ 7427.319347] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x51) -- -- [ 7427.327494] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x52) -- [ 7427.335542] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x53) -- [ 7427.343450] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x54) -- [ 7427.351337] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x55) -- [ 7427.359253] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x56) -- [ 7427.367144] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x57) -- [ 7427.375064] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x58) -- [ 7427.382919] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x59) -- [ 7427.390845] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5a) -- [ 7427.398722] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5b) -- [ 7427.406644] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5c) -- [ 7427.414530] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5d) -- [ 7427.422422] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5e) -- [ 7427.430313] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x5f) -- [ 7427.438186] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 60: [ 7427.446532] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x60) -- [ 7427.454656] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.462942] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x61) -- [ 7427.470654] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.478940] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x62) -- [ 7427.486645] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.494940] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x63) -- [ 7427.502615] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.510910] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x64) -- [ 7427.518609] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.526903] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x65) -- [ 7427.534604] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.542893] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x66) -- [ 7427.550606] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.558895] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x67) -- [ 7427.566598] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.574893] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x68) -- [ 7427.582568] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.590861] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x69) -- [ 7427.598560] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.606840] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6a) -- [ 7427.614577] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.622849] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6b) -- [ 7427.630585] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.638858] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6c) -- [ 7427.646592] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.654895] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6d) -- [ 7427.662591] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.670867] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6e) -- [ 7427.678604] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.686878] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x6f) -- [ 7427.694634] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received 70: [ 7427.702888] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x70) -- [ 7427.711118] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.719388] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x71) -- [ 7427.727125] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.735401] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x72) -- [ 7427.743094] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.751374] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x73) -- [ 7427.759111] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.767389] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x74) -- [ 7427.775143] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.783415] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x75) -- [ 7427.791116] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.799409] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x76) -- [ 7427.807116] sunxi-i2c sunxi-i2c2: SLA+W has been transmitted; ACK not received [ 7427.815408] sunxi-i2c sunxi-i2c2: engine-mode: xfer failed(dev addr:0x77) --

1
Z

D1-H这块板子怎么打开矢量运算支持
发布于 • zny666

0 赞同

1 回复

869 浏览

 回复于

@zny666

看文章的这部分：

默认情况下，平头哥提供的交叉编译工具链已支持了V扩展的编译。只需要在编译选项中开启即可。

83183a23-e9aa-4516-b4ea-7197b25177d5-image.png

从传递给RISC-V的gcc的选项来看，带有v扩展即可。

1
C

T113-s3 求助帮忙dump内存
发布于 • czllong1989

0 赞同

0 回复

653 浏览

尚无回复

0
L

D1S GPIO的速率最高能到多少？
发布于 • LilaZhou

0 赞同

2 回复

844 浏览

L 回复于

@whycanservice 那引脚速度有多少

2
M

D1s 接 i80 ST7789 LCD 的线序
d1s st7789 i80 • 发布于 • memory

0 赞同

4 回复

2080 浏览

S 回复于

@memory 有没有固件或是原理图~~

4
Z

哪吒D1的内存带宽
发布于 • zhaodongyu

0 赞同

1 回复

942 浏览

 回复于

@zhaodongyu
带宽=频率*位宽测试结果与CPU主频，OS调度等有较大影响。

1
D1s 开发板 M2
d1s m2 • 发布于 • whycan晕哥

0 赞同

5 回复

1686 浏览

S 回复于

@whycan 这个板子很漂亮。不过上面USB Hub那颗芯片有点大，感觉不太和谐，根主芯片的长度一样了。请问这个USB Hub有没有性价比还不错的替代方案，比较小一些封装的。

5
rtos插入U盘挂载失败
发布于 • zznzzn

0 赞同

0 回复

742 浏览

尚无回复

0
自己画的D1s/T113板子，uboot能引导，进入系统有时会卡住死机
发布于 • 钟工

0 赞同

11 回复

3279 浏览

L 回复于

@edisondeng 56daae7c-a381-4373-9420-462962d5743a-image.png

11
L

D1s 通过内存映射方式，直接操作GPIO寄存器，输出速度很慢，如何提高？
发布于 • LilaZhou

0 赞同

3 回复

1170 浏览

 回复于

@lilazhou 考虑CPU调度问题，Kernel可能调度到其他事项了，需要高速处理建议使用RTOS等开销较小的系统

3
S

请问spi-nand的型号是什么？
发布于 • sorive

0 赞同

3 回复

1524 浏览

 回复于

@sorive 目前使用ubi方案的芯片（如R329、D1、V853、T113等），支持的spinand型号可以在以下路径查看：lichee/brandy-2.0/u-boot-2018/drivers/mtd/awnand/spinand/physic/id.c，需要适配新物料，可直接在改路径下添加物料配置信息即可。针对一些非ubi方案的芯片，如R328、R11等，该部分驱动代码不开源，需要自行在SDK下载界面下载对应开源物料补丁后才可适配新物料

3
C

求教怎么关掉XRADIO WIFI OPEN
发布于 • cfxcfx

0 赞同

5 回复

1548 浏览

 回复于

@cfxcfx
缺mkfs.ext4，要打开 e2fsprog 软件包。

5
【开源硬件】全志芯片系列优秀开源工程分享第三期
发布于 • budbool

0 赞同

0 回复

773 浏览

尚无回复

0
M

我想调整eMMC的频率，又不想重新烧固件，请问可以实现吗？
发布于 • memory

0 赞同

1 回复

699 浏览

U 回复于

按住s启动可以进入uboot命令行

进入uboot命令行后
输入命令
1.fdt set mmc0 max-frequency <100000000> 2.fdt save 3.boot
注：<100000000>就是要设置的频率，单位是hz。最大值<200000000>
比较新的一些平台步骤2不再支持，因此一旦系统重启，max-frequency会再次恢复固件里面的设置值。

1
L

D1s晶振不起振问题
发布于 • litengos

0 赞同

9 回复

2368 浏览

L 回复于

D1S的晶振不是24M 18PF的吗 12pf？

9
C

F133烧录nand flash失败
发布于 • CHENNENGBIAO

0 赞同

6 回复

2107 浏览

L 回复于

1、你可以换根好点的数据线，就是那种带屏蔽的，
2、可能有的nandF133不支持，烧录校验失败
3、可以试试这款MT29F2G01ABAGDWB

6
X

求助贴，自己制作的系统镜像，用于哪吒D1-H，但是网卡丢包情况严重
发布于 • xiaoxiaoji

0 赞同

0 回复

403 浏览

尚无回复

0
S

下载v2.1也是repo start product-smartx-d1-h-tina-stable-v2.0 --all？
发布于 • syemour

0 赞同

2 回复

660 浏览

S 回复于

@whycan 谢谢大佬

2
C

T113 网络摄像头
发布于 • chen189324

0 赞同

2 回复

902 浏览

 回复于

@memory
实际操作得结合码率，分辨率，剩余内存等参数，建议先录个文件到本地测试。

2
请教一下top命令支持，top -t 不支持应该如何处理？
发布于 • zznzzn

0 赞同

1 回复

579 浏览

 回复于

atop、ftop、htop和top都是用于监视系统资源和进程的命令行工具，但它们有一些区别：

① top：top 是最基本和最常见的命令行实用程序，可显示当前运行的进程列表，并提供有关 CPU 使用情况、内存使用情况和系统负载等信息。它以交互式方式更新数据，并且在使用过程中可以进行不同排序和过滤选项的设置。

② atop：atop 是一种高级的系统性能监视工具，相比于 top，它提供了更详细的资源和进程信息。atop 可以记录历史数据并生成报告，让你可以回顾过去的性能数据。它还提供了更多的自定义选项和功能，例如磁盘 I/O、网络活动和进程调度的监控。

③ htop：htop 是一个针对 top 的增强版本，提供了更友好和交互式的界面。与 top 不同，htop 允许通过鼠标或键盘进行直观的交互操作，如进程选择、排序和筛选。它还提供了更多的系统信息和资源使用图形化展示。

④ ftop：我无法找到与 ftop 相关的通用监视工具。如果您指的是特定的工具或应用程序，请提供更多详细信息。

总之，这些工具都提供了对系统资源和进程的监视功能，但在交互性、显示界面和可用功能方面有所不同。根据您的需求和个人偏好，可以选择适合的工具来监控和分析系统性能。

1
使用Docker 编译 Tina-Linux
发布于 • KunYi

0 赞同

0 回复

679 浏览

尚无回复

0
Y

芒果派MangoPi MQ Pro环境搭建
发布于 • giao

0 赞同

0 回复

831 浏览

尚无回复

0
S

F133启动rtk_hciattach报错
发布于 • shz18877605430

0 赞同

3 回复

1060 浏览

 回复于

@shz18877605430

一定要勾选H5协议:

2f59f2d0-4e44-4ba0-8d15-4f59681e51a9-b6db94f5ff75d6db510ebf3c0079167.png

4109bef7-ab4c-429f-9975-da53e55893a7-70f9c9757fde601f4c64962f574b834.jpg

3
A

ubuntu下xfel工具怎样识别到D1-H开发板
发布于 • a792947123

0 赞同

1 回复

544 浏览

 回复于

你确认芯片进入fel了吗？

1
S

尝试mq-r驱动mipi屏遇到问题
发布于 • soso90

0 赞同

3 回复

1484 浏览

F 回复于

请问楼主解决了吗，目前我也是遇到一样的问题

3
S

D1 ddr驱动问题咨询
发布于 • sfgy125110

0 赞同

3 回复

1052 浏览

S 回复于

@whycan 请问一下，这里能查看到的驱动只有一个.o文件和一个.S文件，这个文件是全志自己写的然后编译出来的，还是ddr厂商提供的，内部处理不需要自己管，只需要把这个添加到spl里面就好了

3
A

D1-H开发板裸机程序可以通过xfel或其他工具烧录到emmc吗
发布于 • a792947123

0 赞同

5 回复

1556 浏览

 回复于

@a792947123

参考这个帖子：用buildroot自带的genimage把tina dragon的活干完，让dragon无活可干。

5
T

深入研究全志SOC芯片EFUSE,并扩展xfel工具，实现efuse烧写。
发布于 • tripod9

1 赞同

0 回复

1176 浏览

尚无回复

0
U

以太网phy自动协商原理中，为什么千兆需要协商主从，百兆不需要？
发布于 • ubuntu

0 赞同

0 回复

514 浏览

尚无回复

0
lcd使用pwm作为背光控制亮度调节异常
发布于 • zznzzn

0 赞同

1 回复

1251 浏览

 回复于

搞定了，是当前内核pwm框架与我们的pwm驱动对于极性的判断相反导致，并且kernel阶段的pwm极性与uboot阶段的不一致

添加函数将极性配置与uboot阶段保持一致的极性状态。具体方法是在pwm代码中添加接口：
static void sunxi_pwm_get_state(struct pwm_chip *chip, struct pwm_device *pwm, struct pwm_state *state) { unsigned int reg_offset; u32 val, sel; sel = pwm->pwm - chip->base; reg_offset = PWM_PCR_BASE + sel * 0x20; val = sunxi_pwm_readl(chip, reg_offset); if (val & BIT_MASK(8)) { state->polarity = PWM_POLARITY_NORMAL; } else { state->polarity = PWM_POLARITY_INVERSED; } } static struct pwm_ops sunxi_pwm_ops = { ... .get_state = sunxi_pwm_get_state, ... };
这个函数的作用是在pwm驱动初始化阶段，读取uboot阶段设置的极性，并将kernel阶段的极性设置与其保持一致。具体内核操作可追流程。

除了修改驱动代码，还需要同对应修改每个板级目录下的board.dts。该修改主要是针对regulator使用pwm进行调压，会在dts中配置pwm调压的极性，为了保证与uboot阶段的电压一致，现在需要把dts中配置的极性的值置位1。
reg_vdd_cpu: vdd-cpu { compatible = "sunxi-pwm-regulator"; - pwms = <&pwm 0 5000 0>; // 第一个参数是使用的pwm通道，第二个参数是频率，第三个参数是极性 + pwms = <&pwm 0 5000 1>; // 第一个参数是使用的pwm通道，第二个参数是频率，第三个参数是极性 regulator-name = "vdd_cpu"; regulator-min-microvolt = <810000>; regulator-max-microvolt = <1160000>; regulator-ramp-delay = <25>; regulator-always-on; regulator-boot-on; status = "okay"; };
在修改完成后，编译打包，确认版型后烧录测试，先看板子能不能起来，起不来的话证明电压极性有误，可以拿万用表测量一下电压，看启动阶段电压有没有发生突变。成功起来后还需要测试一下pwm功能是否正常，最好使用示波器来测一下board.dts里配置的pwm通道的管脚，然后调试该通道看有无波形变化，具体方法如下：
进入/sys/class/pwm目录，该目录是linux内核为pwm子系统提供的类目录，遍历该目录：
/sys/class/pwm # ls pwmchip0
可以看到，上述 pwmchip0 就是我们注册的pwm控制器，进入该目录，然后遍历该目录：
sys/class/pwm # cd pwmchip0/ /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # ls device export npwm subsystem uevent unexport
其中npwm文件储存了该pwm控制器的pwm个数，而export和unexport是导出和删除某个pwm设备的文件，下面演示导出pwm1。
/sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # cat npwm 2 /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # echo 1 > export /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # ls device export npwm pwm1 subsystem uevent unexport
可以看到目录中多出pwm1目录，进入该目录，遍历：
/sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # cd pwm1/ /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # ls capture duty_cycle enable period polarity uevent
该目录中，enable是使能pwm，duty_cycle是占空比，period是周期，polarity是极性，可以配置相关的pwm并且使能：
/sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # echo 1000000000 > period /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # echo 500000000 > duty_cycle /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # echo normal > polarity /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # echo 1 > enable
如果相应的引脚外接了示波器，可以看到相关的波形。最后返回上层目录，删除该pwm设备：
/sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0/pwm1 # cd .. /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # ls device export npwm pwm1 subsystem uevent unexport /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # echo 1 > unexport /sys/devices/platform/soc/1c23400.pwm/pwm/pwmchip0 # ls device export npwm subsystem uevent unexport
在有条件的情况且能找到相应屏幕的情况下，最好接上屏幕进行验证，确认在uboot阶段进入kernel阶段出现闪屏的情况。
不带屏幕，且没有vdd-cpu的话，pwm初始化极性就不会影响到默认固件正常使用，使用示波器验证就好。

1
F

T113 RTL8363出现Initialize hardware error 问题
发布于 • fans168168

0 赞同

0 回复

531 浏览

尚无回复

0

6 / 19

行为准则 | 用户协议 | 隐私权政策

各位大佬，有遇到过 取指令访问错误异常么，是怎么触发的啊？ 发布于 • zznzzn

t113求助各位大佬：mmp sample在哪里配置呢在menuconfig似乎没有找到 发布于 • Uccccc

全志D1烧录固件以后系统起不来 发布于 • jzxzky

请教T113S3串口2（PD1和PD2）和LCD引脚冲突 发布于 • yelong98

D1S驱动MIPI屏幕怎么设置？求大佬帮助 发布于 • q2022

T113 SPI无法通讯问题 发布于 • kaifan

D1-H 使能spi0和spi1的问题 发布于 • lbuque

D1s芯片烧录melis固件启动报错，大家帮我看看咋回事 发布于 • liu11372650

D1s读取nor flash导致音频的DMA出问题 发布于 • qinchangzu

T113-S3 Mango MQ-R Wi-Fi 8723ds 问题 发布于 • hongduc10

SDK的开发环境必须是Ubuntu14.04吗？ 发布于 • houxc01

D1 Opensbi 直接启动内核 发布于 • geniusz

tina SDK编译的buildroot文件系统，如何更改只读属性？ 发布于 • NLJ_Moon

全志D1编译报错 发布于 • jzxzky

RGB的七寸屏（分辨率1024，600）配置后无法正常显示 发布于 • CHENNENGBIAO

D1 内核设备树 发布于 • geniusz

关于D1s,请问哪块板子最适合入门学习 发布于 • xmxjh

在D1的tina上整上overlayfs 发布于 • TEVET

是不是驱动开启旋转之后，就没有/dev/fb0了？ 发布于 • memory

D1 用Xfel启动不了内核 发布于 • geniusz

D1s i80 接 ST7789V uboot有显示进入 Linux 没显示黑屏了 发布于 • awwwwa

D1s可以实现 LCD + TV 双屏异显吗？ 发布于 • memory

芒果派MangoPi MQ Pro构建sqlite3并进行性能测试 发布于 • bayche

mq-r t113 ov5640适配 发布于 • kw___

启动到这里停止了，是不是dram坏了？ 发布于 • dort91011

芒果派 MQ-Dual T113 官方镜像无法启动 发布于 • center1056

D1 Tina-SDK V2.1编译直接报错！ 发布于 • 100ask

按照官方文档去配置spinand切换spinor报错 发布于 • abcdef

D1-h开机时间最短能做到多少？ 发布于 • haaland

D1-H v2.1 SDK问题 发布于 • litengos

Tina sdk(t113) 更改uart_debug口后，debug信息打印不全 发布于 • jr_online

Lichee RV Dock的 type-c 支持网口吗？ 发布于 • zznzzn

d1s和t113在供电有啥区别？ 发布于 • bigfly

求教，D1s uboot烧写问题。 发布于 • siguadao

T113麻雀，TF卡启动，经常卡死 发布于 • gonboy

d1h的怎么开启矢量指令的支持 发布于 • haaland

全志D1怎么开启V指令？并且正常使用？ 发布于 • Brucelee24

T113-Pro开发板连接mipi屏幕，屏幕总是不亮 发布于 • z15612417860

麻雀T113-s3, 触摸屏错误，总是提示 发布于 • gonboy

增加Package, 生成的so 无法自动添加到 /usr/lib中 发布于 • gonboy

Pack Error: F133-mq_r打包时出现no user resource partitions 发布于 • zhang21st

服务平台D1-H的文档怎么没了以前有很多文档的 发布于 • nikola

T113-S3 配置横屏显示系统跑不起来问题 发布于 • AW20221130

gadget做HID键盘报错 发布于 • xjy_5

f133增加驱动未编译进固件中 发布于 • furyfangyu

移植到全志D1-H开发板，找不到MMIO 发布于 • jaddyk

全志D1烧写中断，开机卡[180]Loading boot-pkg fail(error=2) 发布于 • xjy_5

uart寄存器问题 发布于 • sfgy125110

d1-h是不支持KGDB吗？ 发布于 • pineappleman

修改了串口的波特率后uboot阶段乱码 发布于 • xingcongying

T113裸跑不能产生中断请教： 发布于 • L13819506056

芒果派 MQ-R T113 无法启动 发布于 • llqzx

D1s 无法从EMMC启动 发布于 • lvjun0728

USB Camera demo代码包问题 发布于 • Cool_Sir

我的程序可以搜索出来，但是设置里看不到 发布于 • SongXuanYu

播放wav的音频文件没有问题，播放视频mp4异常 发布于 • zznzzn

因为喜欢用ADB，因为不喜欢插拔TF卡，所以D1直接用PhoenixSuit烧录TF(SDNAND) 发布于 • TEVET

D1H 使用OV5640 报错 发布于 • liangjian

T113 摄像头无法打开 发布于 • myamoroso

D1 的sdk包无法下载 发布于 • geniusz

哪吒d1-h开发板mmap /dev/mem设备，gdb不能访问 发布于 • liuruyi

编译错误，在进行make -j32时出现错误 发布于 • hanky

MQ-Pro D1-H ov5640适配 发布于 • kw___

adb 和usb虚拟串口的切换 发布于 • ddrddr

芒果派MangoPi MQ Pro+Tina Linux 开发环境搭建 发布于 • giao

有关编译c内联矢量指令时，unknown register name ‘v1’ in ‘asm’的问题 发布于 • zny666

D1哪吒v1.2版本原理图与PCB源文件 可以下载了 哪吒原理图 • 发布于 • memory

T113 tina GPADC怎么用来电压测量呀？ 发布于 • jr_online

t113使用spinandflash作为存储介质往文件系统中复制文件一直提示空间不足 发布于 • ah669741

有偿求芒果派MQ Pro全志D1 H主控驱动DVP OV5640 发布于 • AbuzzHarbor9999

D1-H这块板子怎么打开矢量运算支持 发布于 • zny666

T113-s3 求助帮忙dump内存 发布于 • czllong1989

D1S GPIO的速率最高能到多少？ 发布于 • LilaZhou

D1s 接 i80 ST7789 LCD 的线序 d1s st7789 i80 • 发布于 • memory

哪吒D1的内存带宽 发布于 • zhaodongyu

D1s 开发板 M2 d1s m2 • 发布于 • whycan晕哥

rtos插入U盘挂载失败 发布于 • zznzzn

自己画的D1s/T113板子，uboot能引导，进入系统有时会卡住死机 发布于 • 钟工

D1s 通过内存映射方式，直接操作GPIO寄存器，输出速度很慢，如何提高？ 发布于 • LilaZhou

请问spi-nand的型号是什么？ 发布于 • sorive

各位大佬，有遇到过取指令访问错误异常么，是怎么触发的啊？
发布于 • zznzzn

t113求助各位大佬：mmp sample在哪里配置呢在menuconfig似乎没有找到
发布于 • Uccccc

全志D1烧录固件以后系统起不来
发布于 • jzxzky

请教T113S3串口2（PD1和PD2）和LCD引脚冲突
发布于 • yelong98

D1S驱动MIPI屏幕怎么设置？求大佬帮助
发布于 • q2022

T113 SPI无法通讯问题
发布于 • kaifan

D1-H 使能spi0和spi1的问题
发布于 • lbuque

D1s芯片烧录melis固件启动报错，大家帮我看看咋回事
发布于 • liu11372650

D1s读取nor flash导致音频的DMA出问题
发布于 • qinchangzu

T113-S3 Mango MQ-R Wi-Fi 8723ds 问题
发布于 • hongduc10

SDK的开发环境必须是Ubuntu14.04吗？
发布于 • houxc01

D1 Opensbi 直接启动内核
发布于 • geniusz

tina SDK编译的buildroot文件系统，如何更改只读属性？
发布于 • NLJ_Moon

全志D1编译报错
发布于 • jzxzky

RGB的七寸屏（分辨率1024，600）配置后无法正常显示
发布于 • CHENNENGBIAO

D1 内核设备树
发布于 • geniusz

关于D1s,请问哪块板子最适合入门学习
发布于 • xmxjh

在D1的tina上整上overlayfs
发布于 • TEVET

是不是驱动开启旋转之后，就没有/dev/fb0了？
发布于 • memory

D1 用Xfel启动不了内核
发布于 • geniusz

D1s i80 接 ST7789V uboot有显示进入 Linux 没显示黑屏了
发布于 • awwwwa

D1s可以实现 LCD + TV 双屏异显吗？
发布于 • memory

芒果派MangoPi MQ Pro构建sqlite3并进行性能测试
发布于 • bayche

mq-r t113 ov5640适配
发布于 • kw___

启动到这里停止了，是不是dram坏了？
发布于 • dort91011

芒果派 MQ-Dual T113 官方镜像无法启动
发布于 • center1056

D1 Tina-SDK V2.1编译直接报错！
发布于 • 100ask

按照官方文档去配置spinand切换spinor报错
发布于 • abcdef

D1-h开机时间最短能做到多少？
发布于 • haaland

D1-H v2.1 SDK问题
发布于 • litengos

Tina sdk(t113) 更改uart_debug口后，debug信息打印不全
发布于 • jr_online

Lichee RV Dock的 type-c 支持网口吗？
发布于 • zznzzn

d1s和t113在供电有啥区别？
发布于 • bigfly

求教，D1s uboot烧写问题。
发布于 • siguadao

T113麻雀，TF卡启动，经常卡死
发布于 • gonboy

d1h的怎么开启矢量指令的支持
发布于 • haaland

全志D1怎么开启V指令？并且正常使用？
发布于 • Brucelee24

T113-Pro开发板连接mipi屏幕，屏幕总是不亮
发布于 • z15612417860

麻雀T113-s3, 触摸屏错误，总是提示
发布于 • gonboy

增加Package, 生成的so 无法自动添加到 /usr/lib中
发布于 • gonboy

Pack Error: F133-mq_r打包时出现no user resource partitions
发布于 • zhang21st

服务平台D1-H的文档怎么没了以前有很多文档的
发布于 • nikola

T113-S3 配置横屏显示系统跑不起来问题
发布于 • AW20221130

gadget做HID键盘报错
发布于 • xjy_5

f133增加驱动未编译进固件中
发布于 • furyfangyu

移植到全志D1-H开发板，找不到MMIO
发布于 • jaddyk

全志D1烧写中断，开机卡[180]Loading boot-pkg fail(error=2)
发布于 • xjy_5

uart寄存器问题
发布于 • sfgy125110

d1-h是不支持KGDB吗？
发布于 • pineappleman

修改了串口的波特率后uboot阶段乱码
发布于 • xingcongying

T113裸跑不能产生中断请教：
发布于 • L13819506056

芒果派 MQ-R T113 无法启动
发布于 • llqzx

D1s 无法从EMMC启动
发布于 • lvjun0728

USB Camera demo代码包问题
发布于 • Cool_Sir

我的程序可以搜索出来，但是设置里看不到
发布于 • SongXuanYu

播放wav的音频文件没有问题，播放视频mp4异常
发布于 • zznzzn

因为喜欢用ADB，因为不喜欢插拔TF卡，所以D1直接用PhoenixSuit烧录TF(SDNAND)
发布于 • TEVET

D1H 使用OV5640 报错
发布于 • liangjian

T113 摄像头无法打开
发布于 • myamoroso

D1 的sdk包无法下载
发布于 • geniusz

哪吒d1-h开发板mmap /dev/mem设备，gdb不能访问
发布于 • liuruyi

编译错误，在进行make -j32时出现错误
发布于 • hanky

MQ-Pro D1-H ov5640适配
发布于 • kw___

adb 和usb虚拟串口的切换
发布于 • ddrddr

芒果派MangoPi MQ Pro+Tina Linux 开发环境搭建
发布于 • giao

有关编译c内联矢量指令时，unknown register name ‘v1’ in ‘asm’的问题
发布于 • zny666

D1哪吒v1.2版本原理图与PCB源文件可以下载了
哪吒原理图 • 发布于 • memory

T113 tina GPADC怎么用来电压测量呀？
发布于 • jr_online

t113使用spinandflash作为存储介质往文件系统中复制文件一直提示空间不足
发布于 • ah669741

有偿求芒果派MQ Pro全志D1 H主控驱动DVP OV5640
发布于 • AbuzzHarbor9999

D1-H这块板子怎么打开矢量运算支持
发布于 • zny666

T113-s3 求助帮忙dump内存
发布于 • czllong1989

D1S GPIO的速率最高能到多少？
发布于 • LilaZhou

D1s 接 i80 ST7789 LCD 的线序
d1s st7789 i80 • 发布于 • memory

哪吒D1的内存带宽
发布于 • zhaodongyu

D1s 开发板 M2
d1s m2 • 发布于 • whycan晕哥

rtos插入U盘挂载失败
发布于 • zznzzn

自己画的D1s/T113板子，uboot能引导，进入系统有时会卡住死机
发布于 • 钟工

D1s 通过内存映射方式，直接操作GPIO寄存器，输出速度很慢，如何提高？
发布于 • LilaZhou

请问spi-nand的型号是什么？
发布于 • sorive