Navigation

    全志在线开发者论坛

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • 在线文档
    • 社区主页
    1. Home
    2. Popular
    Log in to post
    • All categories
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All Time
    • Day
    • Week
    • Month

    • 公告
    • 芯片
    •          T Series
    •          A Series
    •          V Series
    •          MR Series
    •          H/F/TV Series
    •          Wireless & Analog Series
    • Special
    •          创龙科技专区
    •          飞凌嵌入式专区
    •          爱搞机专区
    • Technical topics
    •          RTOS
    •          Linux
    •          GUI
    • Others
    •          代码下载问题专区
    •          编译和烧写问题专区
    •          其它全志芯片讨论区
    •          灌水区
    • Y

      想将t113-s3的usb模拟成一个串口,要怎么做
      其它全志芯片讨论区 • Posted at • giao

      0 Votes
      1 Replies
      769 Views

      whycan Replied at

      @yanmingjian
      用前面那个或许简单一些,后面那个是复合USB设备。

      1
    • G

      USB键盘适配问题
      MR Series • Posted at • godzhou0909

      0 Votes
      1 Replies
      1100 Views

      Z Replied at

      @godzhou0909 大佬,解决了吗?我也是这个问题

      1
    • hqdz8

      【华秋干货铺】一文轻松搞定PCB叠层和阻抗设计
      灌水区 • Posted at • hqdz8

      0 Votes
      1 Replies
      1050 Views

      J Replied at

      @hqdz8 感谢分享!

      1
    • A

      有偿求芒果派MQ Pro全志D1 H主控驱动DVP OV5640
      MR Series • Posted at • AbuzzHarbor9999

      0 Votes
      1 Replies
      1115 Views

      A Replied at

      以下是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
    • D

      adb 和usb虚拟串口的切换
      MR Series • Posted at • ddrddr

      0 Votes
      1 Replies
      1277 Views

      livpo Replied at

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

      1
    • newcastle

      开关显示输出设备能关不能开
      其它全志芯片讨论区 • Posted at • newcastle

      0 Votes
      1 Replies
      1022 Views

      WhycanService Replied at

      @newcastle 失败报错什么?没有进入初始化流程吗

      1
    • H

      有没有用F133GPADC采集过电压值的大神?
      其它全志芯片讨论区 • Posted at • haaland

      0 Votes
      1 Replies
      689 Views

      livpo Replied at

      F133只支持检测0-1.8v,精度很低的,速度也慢
      当普通adc可能不太够用,如果只是采集个电压值还可以

      1
    • H

      V853s如何修改文件系统为ext4,启动介质为emmc
      V Series • Posted at • hzhy1234

      0 Votes
      1 Replies
      1216 Views

      WhycanService Replied at

      用户自定义脚本请添加到下列位置

      tina/target/allwinner/v853s-perf1/busybox-init-base-files/

      在打包的时候会打包进去,切换启动介质参考这篇

      https://bbs.aw-ol.com/topic/1701/tina-linux-存储介质切换-emmc-spi-nand-spi-nor-sd-card-sd-nand

      1
    • YuzukiTsuru

      V536的4K高清摄像头
      其它全志芯片讨论区 • Posted at • 柚木 鉉

      2 Votes
      1 Replies
      762 Views

      Z Replied at

      @yuzukitsuru
      请问这款有做成开发板还是?我蛮感兴趣的。370092495 QQ

      1
    • G

      D1 的sdk包无法下载
      MR Series • Posted at • geniusz

      0 Votes
      1 Replies
      765 Views

      whycan Replied at

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

      1
    • zznzzn

      播放wav的音频文件没有问题,播放视频mp4异常
      MR Series • Posted at • zznzzn

      0 Votes
      1 Replies
      741 Views

      S Replied at

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

      1
    • S

      我的程序可以搜索出来,但是设置里看不到
      MR Series • Posted at • SongXuanYu

      0 Votes
      1 Replies
      681 Views

      S Replied at

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

      1
    • J

      V853S MPP模块API调用
      V Series • Posted at • J_Biao

      0 Votes
      1 Replies
      850 Views

      WhycanService Replied at

      在MPP框架下编译 将MPP框架全部lib打包,拆分编译
      1
    • N

      wifi模块延迟高
      Wireless & Analog Series • Posted at • NLJ_Moon

      0 Votes
      1 Replies
      1219 Views

      WhycanService Replied at

      @nlj_moon 检查系统是否存在大量占用CPU时间的程序,也可以通过MTR等工具进行链路测试来判断问题来源。

      1.MTR基本信息
      MTR(My traceroute)是几乎所有Linux发行版本预装的网络测试工具,此工具也有对应的Windows版本,名称为WinMTR。
      MTR工具将ping和traceroute命令的功能并入了同一个工具中,实现更强大的功能。
      Linux版本的mtr命令默认发送ICMP数据包进行链路探测。可以通过“-u”参数来指定使用UDP数据包用于探测。
      相对于traceroute命令只会做一次链路跟踪测试,mtr命令会对链路上的相关节点做持续探测并给出相应的统计信息。所以,mtr命令能避免节点波动对测试结果的影响,所以其测试结果更正确,建议优先使用。
      2.MTR使用方法
      在Linux系统上使用
      用法说明

      mtr [-hvrctglspni46] [-help] [-version] [-report] [-report-cycles=COUNT] [-curses] [-gtk] [-raw] [-split] [-no-dns] [-address interface] [-psize=bytes/-s bytes] [-interval=SECONDS] HOSTNAME [PACKETSIZE]

      常见可选参数说明:

      -r 或 -report:以报告模式显示输出。 -p 或 -split:将每次追踪的结果分别列出来。 -s 或 -psize:指定ping数据包的大小。 -n 或 -no-dns:不对IP地址做域名反解析。 -a 或 -address:设置发送数据包的IP地址。用于主机有多个IP时。 -4:只使用IPv4协议。 -6:只使用IPv6协议。 另外,也可以在mtr命令运行过程中,输入相应字母来快速切换模式。 ?或 h:显示帮助菜单。 d:切换显示模式。 n:切换启用或禁用DNS域名解析。 u:切换使用ICMP或UDP数据包进行探测。

      3.示例输出
      66551dfc-e715-4d2f-8f07-d2960523e4b8-image.png
      默认配置下,返回结果中各数据列的说明如下。
      第一列(Host):节点IP地址和域名。如前面所示,按n键可以切换显示。
      第二列(Loss%):节点丢包率。
      第三列(Snt):每秒发送数据包数。默认值是10,可以通过参数“-c”指定。
      第四列(Last):最近一次的探测延迟值。
      第五、六、七列(Avg、Best、Wrst):分别是探测延迟的平均值、最小值和最大值。
      第八列(StDev):标准偏差。越大说明相应节点越不稳定。

      1
    • Z

      将网卡的MAC保存i2c的EEPROM
      Linux • Posted at • z

      0 Votes
      1 Replies
      1089 Views

      whycan Replied at

      建议先用 i2c-utils测试,i2cset, i2cset命令通过 /dev/i2c-X 测试。

      1
    • R

      R329官方开发板在哪里购买?
      其它全志芯片讨论区 • Posted at • ROSHEN_007

      0 Votes
      1 Replies
      621 Views

      WhycanService Replied at

      目前可以购买 Sipeed 提供的 R329开发板,官方开发板已经停止售卖了。

      1
    • X

      水贴,来下全志D1开发板资料的
      灌水区 • Posted at • xjy_5

      0 Votes
      1 Replies
      781 Views

      WhycanService Replied at

      【资料汇总】D1-H和D1s的芯片手册,开发资料文档
      https://bbs.aw-ol.com/topic/1216/share/1

      1
    • R

      repo 拉取代码不正常
      代码下载问题专区 • Posted at • ROSHEN_007

      0 Votes
      1 Replies
      892 Views

      WhycanService Replied at

      https://storage.googleapis.com/ 这个网址是谷歌官方源,由于众所周知的原因国内无法访问,请使用国内镜像源代替,另外,安装repo需要Python3环境,使用 sudo apt install python3 安装

      $ mkdir -p ~/.bin $ PATH="${HOME}/.bin:${PATH}" $ curl https://mirrors.bfsu.edu.cn/git/git-repo > ~/.bin/repo $ chmod a+rx ~/.bin/repo
      1
    • U

      手机120W的充电器都做得那么小,为什么电脑的100W充电器这么大
      灌水区 • Posted at • ubuntu

      0 Votes
      1 Replies
      778 Views

      W Replied at

      @ubuntu 电脑100W充电器是啥样的。输出电压?

      1
    • Y

      A133+AXP717 ADC读VBUS电压
      其它全志芯片讨论区 • Posted at • yyf1202

      0 Votes
      1 Replies
      1676 Views

      R Replied at

      @yyf1202 问题解决了吗?AXP717数据手册 能分享一下吗,谢谢

      1
    • H

      V853无法烧写SPI Nand
      V Series • Posted at • haaland

      0 Votes
      1 Replies
      1274 Views

      A Replied at

      @haaland

      [05.750]sunxi-spinand-phy: read id failed : -110 try nand fail

      nand找不到,确认一下sys_config.fex的spi引脚配置对不对

      1
    • zznzzn

      T113 Framebuffer编程 LCD无法显示字符
      创龙科技专区 • Posted at • zznzzn

      0 Votes
      1 Replies
      967 Views

      livpo Replied at

      修改一下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); /* 黑 */ } } } }
      1
    • X

      gadget做HID键盘报错
      MR Series • Posted at • xjy_5

      0 Votes
      1 Replies
      977 Views

      G Replied at

      @xjy_5 请问解决了吗?

      1
    • N

      服务平台D1-H的文档怎么没了以前有很多文档的
      MR Series • Posted at • nikola

      0 Votes
      1 Replies
      776 Views

      xiaowenge Replied at

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

      1
    • Z

      Pack Error: F133-mq_r打包时出现no user resource partitions
      MR Series • Posted at • zhang21st

      2 Votes
      1 Replies
      1045 Views

      No one has replied

      1
    • G

      增加Package, 生成的so 无法自动添加到 /usr/lib中
      MR Series • Posted at • gonboy

      1 Votes
      1 Replies
      998 Views

      whycan Replied at

      @gonboy

      试一试这个,用buildroot:

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

      1
    • X

      Tina编译库依赖问题
      Linux • Posted at • xiaye

      0 Votes
      1 Replies
      974 Views

      A Replied at

      @xiaye

      单个包:

      define Package/程序包名/extra_provides echo 'libz.so'; endef

      多个包:

      define Package/程序包名/extra_provides echo 'libstdc++.so.6'; \ echo 'libm.so.6'; \ echo 'libc.so.6'; \ echo 'libz.so'; endef
      1
    • baiwen

      ubuntu 18编译 R818 TinaSDK 2.0 ROS包,提示 host python 错误,有遇到过的同学么?
      其它全志芯片讨论区 • Posted at • 100ask

      0 Votes
      1 Replies
      1537 Views

      A Replied at

      试试使用Ubuntu 14.04

      1
    • Y

      使用docker环境arm交叉编译OpenCV出错
      其它全志芯片讨论区 • Posted at • giao

      0 Votes
      1 Replies
      1053 Views

      A Replied at

      libopencv_highgui.so.4.8.0: file not recognized: File format not recognized

      opencv不是交叉编译的

      1
    • newcastle

      V851s 设备添加了开机logo后提示can't find partition bootloader,并且无法显示开机logo
      V Series • Posted at • newcastle

      0 Votes
      1 Replies
      1363 Views

      A Replied at

      @newcastle 在 V851s 设备添加了开机logo后提示can't find partition bootloader,并且无法显示开机logo 中说:

      ** Unable to read file bootlogo.bmp **

      找不到文件,bootlogo应该是在boot-resource里不在bootloader分区

      1
    • D

      t113-s3 + sr8201,有一块连不上网络
      其它全志芯片讨论区 • Posted at • ddrddr

      0 Votes
      1 Replies
      1183 Views

      K Replied at

      @ddrddr 解决了吗?我跟你的情况一样,我的能ping通自己(127.0.0.1)

      1
    • B

      d1s和t113在供电有啥区别?
      MR Series • Posted at • bigfly

      0 Votes
      1 Replies
      1219 Views

      livpo Replied at

      @bigfly 在 d1s和t113在供电有啥区别? 中说:

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

      可以直接pin to pin替换

      1
    • zznzzn

      Lichee RV Dock的 type-c 支持网口吗?
      MR Series • Posted at • zznzzn

      0 Votes
      1 Replies
      1086 Views

      bayche Replied at

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

      1
    • D

      请教全志方案ota包有办法转成线刷包吗
      编译和烧写问题专区 • Posted at • dort91011

      0 Votes
      1 Replies
      884 Views

      A Replied at

      @dort91011 ota包仅包含部分文件,缺失一些必要文件,不可以转换

      1
    • Y

      香橙派One(全志H3芯片)编译烧写U-boot、Linux内核zImage、dtb
      H/F/TV Series • Posted at • giao

      4 Votes
      1 Replies
      2466 Views

      K Replied at

      @yanmingjian H3的刷入系统文件一直重启,能解决吗?

      1
    • N

      调用摄像头头驱动时VIN报错[VIN_ERR]buffer count is invalid, set to 3
      V Series • Posted at • NULL037

      0 Votes
      1 Replies
      1372 Views

      X Replied at

      @null037 我遇到了类似的问题,请问你后来是怎么解决的?

      1
    • L

      请教东山派 D1S DDR2 初始化方法
      MR Series • Posted at • lee1242624933

      0 Votes
      1 Replies
      791 Views

      D Replied at

      1、利用xfel软件

      6534bb0c-76f9-4502-8592-9924f5e10cf8-image.png

      利用xfel软件去初始化内存,并将bin文件直接烧录到内存中执行。这种方式需要注意程序的链接地址,链接脚本要做相应修改。

      2、剥离内存初始化代码

      (1)在xfel软件的源码里有这部分代码;源码地址:https://github.com/xboot/xfel;
      (2)在SDK包里的spl代码里也有内存初始化代码;
      我还没有将内存初始化代码部分剥离出来,最近也不打算继续研究,后续有剥离出内存初始化代码的同志,请@我分享一下,谢谢。

      1
    • H

      adb调试报错
      V Series • Posted at • H2631436132

      0 Votes
      1 Replies
      979 Views

      H Replied at

      @h2631436132
      重启一下电脑好了

      1
    • T

      有用过F133 melis系统的g2d吗?
      MR Series • Posted at • tianj03

      0 Votes
      1 Replies
      1311 Views

      B Replied at

      rect 的size 需要比dst_image 的小。你有没高反啊?

      1
    • bayche

      芒果派MangoPi MQ Pro构建sqlite3并进行性能测试
      MR Series • Posted at • bayche

      0 Votes
      1 Replies
      1473 Views

      Y Replied at

      不错.
      学习学习.

      1
    • D

      A40i将hdmi输出改为 tft_lcd
      创龙科技专区 • Posted at • ddrddr

      0 Votes
      1 Replies
      1340 Views

      livpo Replied at

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

      QQ图片20230828105111.jpg

      1
    • zznzzn

      OV9716,初始化异常
      V Series • Posted at • zznzzn

      0 Votes
      1 Replies
      1276 Views

      livpo Replied at

      @zznzzn 看一下驱动[VIN_DEV_I2C_ERR]ov9716_mipi sensor write array Error, array_size 1701!,这里为什么会出现这种写入数组的错误,由于写入数据失败了,导致后面获取不到数据

      1
    • O

      XR806开发板烧录报错
      Wireless & Analog Series • Posted at • oiouou123

      0 Votes
      1 Replies
      1020 Views

      O Replied at

      @oiouou123 已经解决,忘了勾选硬件复位烧写模式模式了

      1
    • M

      是不是驱动开启旋转之后,就没有/dev/fb0了?
      MR Series • Posted at • memory

      0 Votes
      1 Replies
      1354 Views

      whycan Replied at

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

      1
    • M

      D1s可以实现 LCD + TV 双屏异显吗?
      MR Series • Posted at • memory

      0 Votes
      1 Replies
      967 Views

      whycan Replied at

      可 以 实 现

      1
    • A

      D1s i80 接 ST7789V uboot有显示进入 Linux 没显示黑屏了
      MR Series • Posted at • awwwwa

      0 Votes
      1 Replies
      1306 Views

      A Replied at

      @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
    • G

      D1 内核设备树
      MR Series • Posted at • geniusz

      1 Votes
      1 Replies
      780 Views

      whycan Replied at

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

      1
    • K

      哪吒D1鸿蒙编译显示ninja: build stopped: subcommand failed. build: ninja error
      编译和烧写问题专区 • Posted at • karrena

      0 Votes
      1 Replies
      1026 Views

      K Replied at

      @karrena 重新编译后报错信息不一样,如下:
      Starting Ninja...
      ninja: Entering directory `/usr/OpenHarmony/out/ohos-riscv64-release'
      [1/8521] COPY ../../drivers/peripheral/camera/hal/pipeline_core/pipeline_impl/src/strategy/config/config.c obj/drivers/peripheral/camera/hal/adapter/platform/v4l2/drivers/peripheral/camera/hal/pipeline_core/pipeline_impl/src/strategy/config/config.c
      [2/8521] COPY ../../drivers/peripheral/camera/hal/pipeline_core/pipeline_impl/src/strategy/config/params.c obj/drivers/peripheral/camera/hal/adapter/platform/v4l2/drivers/peripheral/camera/hal/pipeline_core/pipeline_impl/src/strategy/config/params.c
      [3/8521] STAMP obj/drivers/peripheral/camera/hal/adapter/platform/v4l2/params.c.stamp
      [4/8521] STAMP obj/drivers/peripheral/camera/hal/adapter/platform/v4l2/config.c.stamp
      [5/8521] CXX obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set.o
      FAILED: obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set.o
      /usr/bin/ccache ../../prebuilts/clang/ohos/linux-x86_64/llvm-riscv/bin/clang++ -MMD -MF obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set.o.d -DHAVE_PTHREAD -DV8_DEPRECATION_WARNINGS -DNO_TCMALLOC -D_GNU_SOURCE -DHAVE_SYS_UIO_H -D__MUSL__ -D_LIBCPP_HAS_MUSL_LIBC -D__BUILD_LINUX_WITH_CLANG -D_LIBCPP_NO_NATIVE_SEMAPHORES -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DCOMPONENT_BUILD -D__GNU_SOURCE=1 -DCHROMIUM_CXX_TWEAK_INLINES -D__MUSL__ -D_LIBCPP_HAS_MUSL_LIBC -D__BUILD_LINUX_WITH_CLANG -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Iobj/third_party/musl/usr/include/riscv64-linux-ohosmusl -I../../prebuilts/clang/ohos/linux-x86_64/llvm-riscv/include/c++/v1 -I../.. -Igen -I../../third_party/protobuf/src -I../../third_party/protobuf/src/google -I../../third_party/protobuf/src/google/protobuf -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector-strong -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -funwind-tables -fPIC -fcolor-diagnostics -fmerge-all-constants -Xclang -mllvm -Xclang -instcombine-lower-dbg-declare=0 -no-canonical-prefixes -ffunction-sections -fno-short-enums --target=riscv64-linux-ohosmusl -mno-relax -march=rv64imafdc -mabi=lp64d -mno-relax -Wall -Wextra -Wimplicit-fallthrough -Wthread-safety -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-unneeded-internal-declaration -Wno-error=c99-designator -Wno-error=anon-enum-enum-conversion -Wno-error=implicit-fallthrough -Wno-error=sizeof-array-div -Wno-error=reorder-init-list -Wno-error=range-loop-construct -Wno-error=deprecated-copy -Wno-error=implicit-int-float-conversion -Wno-error=inconsistent-dllimport -Wno-error=unknown-warning-option -Wno-error=abstract-final-class -Wno-error=sign-compare -Wno-error=int-in-bool-context -Wno-error=xor-used-as-pow -Wno-error=return-stack-address -Wno-error=dangling-gsl -Wno-undefined-var-template -Wno-nonportable-include-path -Wno-user-defined-warnings -Wno-unused-lambda-capture -Wno-null-pointer-arithmetic -Wno-enum-compare-switch -Wno-gnu-folding-constant -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g2 -ggnu-pubnames -fno-common -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall -Werror -fPIC -frtti -U__ANDROID__ -Wno-sign-compare -Wno-error=unused-parameter -Wno-error=unused-const-variable -Wno-error=unneeded-internal-declaration -Wno-inconsistent-missing-override -std=c++17 -fno-exceptions --sysroot=obj/third_party/musl -fvisibility-inlines-hidden -frtti -c ../../third_party/protobuf/src/google/protobuf/extension_set.cc -o obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set.o
      expected ':' in depfile[6/8521] CXX obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set_heavy.o

      FAILED: obj/third_party/protobuf/src/google/protobuf/protobuf_standard/extension_set_heavy.o

      1
    • N

      如何将Libuvc编译到tina系统中
      V Series • Posted at • netube

      0 Votes
      1 Replies
      1160 Views

      A Replied at

      参照opencv的编写使用cmake的makefile

      include $(TOPDIR)/rules.mk PKG_NAME:=opencv PKG_VERSION:=4.1.1 PKG_RELEASE:=1 PKG_SOURCE_PROTO:=git PKG_SOURCE_URL:=https://github.com/opencv/opencv PKG_SOURCE_VERSION:=$(PKG_VERSION) PKG_MIRROR_HASH:=c8587820421d2f22acdafe4712d068ae490897dc445bdb4aa128ecaa8e65d3a1 PKG_MAINTAINER:= PKG_LICENSE:=BSD-3-Clause PKG_LICENSE_FILES:=LICENSE CMAKE_INSTALL:=1 CMAKE_BINARY_SUBDIR:=build PKG_BUILD_PARALLEL:=1 PKG_USE_MIPS16:=0 include $(INCLUDE_DIR)/package.mk include $(INCLUDE_DIR)/cmake.mk define Package/opencv/Default/description OpenCV (Open Source Computer Vision Library) is an open source computer vision and machine learning software library. OpenCV was built to provide a common infrastructure for computer vision applications and to accelerate the use of machine perception in the commercial products. Being a BSD-licensed product, OpenCV makes it easy for businesses to utilize and modify the code. endef define Package/opencv SECTION:=libs CATEGORY:=Libraries TITLE:=OpenCV URL:=https://opencv.org/ DEPENDS:=+libpthread +librt +libatomic +libstdcpp +zlib +libjpeg +python3 +python3-numpy endef CMAKE_OPTIONS += \ -DBUILD_opencv_gpu:BOOL=OFF \ -DWITH_1394:BOOL=OFF -DBUILD_opencv_stitching:BOOL=OFF \ -DBUILD_opencv_superres:BOOL=OFF -DBUILD_opencv_ts:BOOL=OFF \ -DBUILD_opencv_highgui:BOOL=ON \ -DBUILD_opencv_videostab:BOOL=OFF \ -DWITH_FFMPEG:BOOL=OFF \ -DWITH_GSTREAMER:BOOL=OFF \ -DWITH_LIBV4L:BOOL=ON \ -DWITH_PNG:BOOL=OFF \ -DWITH_GTK:BOOL=OFF \ -DWITH_TIFF:BOOL=OFF \ -DCMAKE_VERBOSE:BOOL=OFF \ -DENABLE_PRECOMPILED_HEADERS=OFF \ -DPYTHON3_INCLUDE_PATH=$(STAGING_DIR)/usr/include/python3.9 \ -DPYTHON3_LIBRARIES=$(STAGING_DIR)/usr/lib/libpython3.9.so \ -DPYTHON3_NUMPY_INCLUDE_DIRS=$(TARGET_ROOTFS_DIR)/pypi/numpy-1.20.1/ipkg-install/usr/lib/python3.9/site-packages/numpy/core/include \ -DBUILD_OPENCV_PYTHON3:BOOL=ON TARGET_LDFLAGS += -latomic define Package/opencv/install $(INSTALL_DIR) $(1)/usr/lib $(CP) $(PKG_INSTALL_DIR)/usr/lib/* $(1)/usr/lib/ endef $(eval $(call BuildPackage,opencv))
      1
    • S

      853板子作为uvc通过usb0 out到pc,对UDC文件操作出现"Resource busy"
      V Series • Posted at • sofia

      0 Votes
      1 Replies
      611 Views

      No one has replied

      1
    • G

      T113编译时,总是需要确认,什么含义?
      其它全志芯片讨论区 • Posted at • gonboy

      0 Votes
      1 Replies
      1420 Views

      A Replied at

      这通常是由于kernel更新而defconfig没有更新导致的,需要同步更新defconfig

      1
    • G

      mq-r T113 的 8189的蓝牙,是否有人调通,HCI怎么都不通
      其它全志芯片讨论区 • Posted at • gonboy

      0 Votes
      1 Replies
      934 Views

      G Replied at

      坑死。 刚发现, 8189竟然没蓝牙

      1
    • Q

      D1s读取nor flash导致音频的DMA出问题
      MR Series • Posted at • qinchangzu

      0 Votes
      1 Replies
      1197 Views

      Q Replied at

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

      1
    • houxc01

      SDK的开发环境必须是Ubuntu14.04吗?
      MR Series • Posted at • houxc01

      0 Votes
      1 Replies
      787 Views

      walker2048 Replied at

      @houxc01 WSL2下用docker很方便

      1
    • L

      OTA升级,执行swupdate_make_recovery_img报错
      其它全志芯片讨论区 • Posted at • lancer

      0 Votes
      1 Replies
      938 Views

      A Replied at

      @lancer make -j1 看看报错,这样看不到

      1
    • L

      OTA升级,执行swupdate_make_recovery_img报错
      其它全志芯片讨论区 • Posted at • lancer

      0 Votes
      1 Replies
      728 Views

      J Replied at

      你好,请问大佬你实现tina的recovery系统OTA功能了么,可以请教下如何实现么

      1
    • L

      D1s芯片烧录melis固件启动报错,大家帮我看看咋回事
      MR Series • Posted at • liu11372650

      0 Votes
      1 Replies
      1174 Views

      A Replied at

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

      0x000000004003049c

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

      1
    • L

      RotatePictureHw函数使用
      GUI • Posted at • Liyunpeng

      0 Votes
      1 Replies
      1064 Views

      A Replied at

      ls /dev 看一下输出

      1
    • N

      wifi 模块无法使用问题
      Wireless & Analog Series • Posted at • NLJ_Moon

      0 Votes
      1 Replies
      1581 Views

      X Replied at

      @nlj_moon 执行wifi_daemon 然后wifi的测试命令就可以使用了

      1
    • B

      UART1~UART5驱动配置
      创龙科技专区 • Posted at • bigfly

      0 Votes
      1 Replies
      1111 Views

      Tronlong_support Replied at

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

      1
    • Y

      【米尔T113测评】开机点灯+TCP编程
      其它全志芯片讨论区 • Posted at • giao

      0 Votes
      1 Replies
      1269 Views

      Y Replied at

      udp --- 用户数据报协议,是一个无连接的简单的面向数据报的运输层协议。
      udp不提供可靠性,它只是把应用程序传给IP层的数据报发送出去,但是并不能保证它们能到达目的地。
      udp在传输数据报前不用在客户和服务器之间建立一个连接,且没有超时重发等机制,故而传输速度很快。
      udp是一种面向无连接的协议,每个数据报都是一个独立的信息,包括完整的源地址或目的地址,它在网络上以任何可能的路径传往目的地,因此能否到达目的地,到达目的地的时间以及内容的正确性都是不能被保证的。

      udp通讯流程很简单,具体步骤如下:

      微信图片_20230908105059.png

      udp服务端代码

      #include <stdio.h> #include <string.h> #include <unistd.h> #include <sys/types.h> #include <sys/socket.h> #include <stdlib.h> #include <netinet/in.h> #include <arpa/inet.h> #include <stdbool.h> #include <pthread.h> #define BUFFER_SIZE 1024 // buf size struct CONNECT_INFO { struct sockaddr_in client_addr; }; static int sock_fd; static volatile bool is_connect = false; bool udp_server_init(short port) { struct sockaddr_in server_addr; sock_fd = socket(AF_INET, SOCK_DGRAM, 0); if (sock_fd == -1) { perror("socket"); return false; } // initialize address. bzero(&server_addr, sizeof(server_addr)); server_addr.sin_family = AF_INET; server_addr.sin_port = htons(port); server_addr.sin_addr.s_addr = htonl(INADDR_ANY); // bind the local port. if ((bind(sock_fd, (struct sockaddr *)&server_addr, sizeof(struct sockaddr_in))) == -1) { perror("bind"); return false; } return true; } void *send_thread(void *arg) { struct CONNECT_INFO *info = (struct CONNECT_INFO *)arg; if (info == NULL) { printf("error connect info"); return (void*)-1; } while (1) { char send_buf[BUFFER_SIZE]; bzero(send_buf, sizeof(send_buf)); // input from keyboard. char *str = fgets(send_buf, sizeof(send_buf), stdin); if (str == NULL) { perror("fgets"); continue; } if (strlen(str) <= 1) { continue; } if(is_connect == false) { printf("No client are available!\n"); continue; } // send data. if ((sendto(sock_fd, send_buf, strlen(str) - 1, 0, (struct sockaddr *)&info->client_addr, sizeof(struct sockaddr_in))) < 0) { perror("sendto"); continue; } } return (void*)0; } int main(int argc, char *argv[]) { // check your input. if (argc != 2) { printf("Usage:\n"); printf(" %s <port number>\n", argv[0]); return -1; } short port = atoi(argv[1]); bool ret = udp_server_init(port); if (ret == false) { goto err; } pthread_t t_id; struct CONNECT_INFO info; socklen_t addr_len = sizeof(struct sockaddr_in); memset(&info, 0, sizeof(info)); pthread_create(&t_id, NULL, send_thread, (void *)&info); pthread_detach(t_id); printf("Waiting for client connectionn\n"); while (1) { // recive from client. char recv_buf[BUFFER_SIZE]; bzero(recv_buf, sizeof(recv_buf)); if ((recvfrom(sock_fd, recv_buf, sizeof(recv_buf), 0, (struct sockaddr *)&info.client_addr, &addr_len)) <= 0) { perror("recvfrom"); goto err; } printf("[Recv from client %s:%d] : %s\n", inet_ntoa(info.client_addr.sin_addr), htons(info.client_addr.sin_port), recv_buf); is_connect = true; } close(sock_fd); return 0; err: close(sock_fd); return -1; }

      udp客户端代码:

      #include <stdio.h> #include <string.h> #include <netinet/in.h> #include <sys/types.h> #include <sys/socket.h> #include <stdlib.h> #include <unistd.h> #include <errno.h> #include <arpa/inet.h> #define BUFFER_SIZE 1024 // buf size int main(int argc, char *argv[]) { // check the arguments. if (argc != 3) { printf("Usage:\n"); printf(" %s <server_addr> <portnumber>\n", argv[0]); return -1; } int sock_fd; char send_buf[BUFFER_SIZE]; char recv_buf[BUFFER_SIZE]; struct sockaddr_in server_addr; char *addr = argv[1]; short port = atoi(argv[2]); // initialize address. bzero(&server_addr, sizeof(server_addr)); server_addr.sin_family = AF_INET; server_addr.sin_addr.s_addr = inet_addr(addr); server_addr.sin_port = htons(port); // create udp socket. sock_fd = socket(AF_INET, SOCK_DGRAM, 0); if (sock_fd == -1) { perror("socket"); return -1; } pid_t pid = fork(); if (pid > 0) { // The parent process is responsible for sending messages. while (1) { bzero(send_buf, sizeof(send_buf)); // read from stdin. char *str = fgets(send_buf, sizeof(send_buf), stdin); if (str == NULL) { perror("fgets"); goto err; } if (strlen(str) <= 1) { continue; } // send data. if ((sendto(sock_fd, send_buf, strlen(str) - 1, 0, (struct sockaddr *)&server_addr, sizeof(struct sockaddr_in))) < 0) { perror("sendto"); goto err; } } } else if (pid == 0) { // The child process is responsible for receiving messages. while (1) { bzero(recv_buf, sizeof(recv_buf)); socklen_t addr_len = sizeof(struct sockaddr_in); if ((recvfrom(sock_fd, recv_buf, sizeof(recv_buf), 0, (struct sockaddr *)&server_addr, &addr_len)) <= 0) { perror("recvfrom"); goto err; } printf("[Recv from server %s:%d] : %s\n", inet_ntoa(server_addr.sin_addr), htons(server_addr.sin_port), recv_buf); } } close(sock_fd); return 0; err: close(sock_fd); return -1; }

      编译后运行结果:

      160406w8j9cocly2a3ncsl.png.thumb.jpg

      160442vfuv6gvfuq518fuf.png.thumb.jpg

      1
    • zznzzn

      v853读取usb摄像头,在sdk里面需要开启或者关闭哪个
      V Series • Posted at • zznzzn

      0 Votes
      1 Replies
      1191 Views

      livpo Replied at

      fcd59f05caa3bb2decc2d0e4e843b52d7906f211.png

      1
    • B

      100ask-t113pro lvds调试问题
      其它全志芯片讨论区 • Posted at • bigfly

      0 Votes
      1 Replies
      1184 Views

      A Replied at

      @bigfly colorbar正常吗

      1
    • newcastle

      用mpp:sample_virvi2vo测试时出现的ISP文件,GC2053从何而来
      V Series • Posted at • newcastle

      0 Votes
      1 Replies
      1249 Views

      N Replied at

      @newcastle MPP测试文件使用有对应的libisp,那可以在,mpp的依赖文件中找到

      1
    • L

      h616 怎么加BGA96的DDR4,现在的兼容器件有哪些?
      H/F/TV Series • Posted at • lisom

      0 Votes
      1 Replies
      1182 Views

      L Replied at

      SUPPER LIST 中只有一颗是测试过的:H5AN4G6NBJR,有更新吗

      1
    • newcastle

      如何确认是什么中断唤醒的芯片
      Wireless & Analog Series • Posted at • newcastle

      0 Votes
      1 Replies
      1290 Views

      livpo Replied at

      @newcastle
      该部分对应的代码是:src/pm/pm.c : pm_check_wakeup_irqs

      /* Check if there are any interrupts pending */ addr = (unsigned int *)NVIC->ISPR; for (i = 0; i < DIV_ROUND_UP(NVIC_PERIPH_IRQ_NUM, 32); i++) { val = addr[i]; irq[i] = val & nvic_int_mask[i]; if (irq[i]) { PM_LOGD("nvic[%d]:%x, mask:%x en:%x\n", i, val, nvic_int_mask[i], NVIC->ISER[i]); ret |= PM_WAKEUP_SRC_DEVICES; } }

      NVIC->ISPR寄存器也就是中断挂起控制寄存器组,代表有中断产生,每一位对应一个中断,可以看到唤醒中断是nvic[1],8也就是0b1000,也就是对应(nvic[0])31 + 4 = 35号中断。

      XR806对应的芯片中断序号在include/driver/chip/chip.h里面定义。

      /*!< Interrupt Number Definition */ typedef enum { /* Cortex-M4/3 Processor Exceptions Numbers*/ NonMaskableInt_IRQn = -14, /*!< 2 Non Maskable Interrupt */ MemoryManagement_IRQn = -12, /*!< 4 Cortex-M3 Memory Management Interrupt */ BusFault_IRQn = -11, /*!< 5 Cortex-M3 Bus Fault Interrupt */ UsageFault_IRQn = -10, /*!< 6 Cortex-M3 Usage Fault Interrupt */ #if defined(CONFIG_CPU_CM33F) SecureFault_IRQn = -9, /*!< 7 Cortex-M33 Secure Fault Interrupt */ #endif SVCall_IRQn = -5, /*!< 11 Cortex-M3 SV Call Interrupt */ DebugMonitor_IRQn = -4, /*!< 12 Cortex-M3 Debug Monitor Interrupt */ PendSV_IRQn = -2, /*!< 14 Cortex-M3 Pend SV Interrupt */ SysTick_IRQn = -1, /*!< 15 Cortex-M3 System Tick Interrupt */ /* Specific Interrupt Numbers */ DMA_IRQn = 0, GPIOA_IRQn = 1, #if (CONFIG_CHIP_ARCH_VER == 2) SDC0_IRQn = 2, #endif UART0_IRQn = 4, UART1_IRQn = 5, SPI0_IRQn = 6, #if (CONFIG_CHIP_ARCH_VER == 2) SPI1_IRQn = 7, #endif I2C0_IRQn = 8, I2C1_IRQn = 9, WDG_IRQn = 10, TIMER0_IRQn = 11, TIMER1_IRQn = 12, RTC_SEC_ALARM_IRQn = 13, RTC_WDAY_ALARM_IRQn = 14, #if (CONFIG_CHIP_ARCH_VER == 2) CSI_JPEG_IRQn = 15, #endif I2S_IRQn = 16, PWM_ECT_IRQn = 17, CE_IRQn = 18, GPADC_IRQn = 19, GPIOB_IRQn = 20, IRRX_IRQn = 22, IRTX_IRQn = 23, A_WAKEUP_IRQn = 25, FLASHC_IRQn = 26, UART2_IRQn = 27, #if (CONFIG_CHIP_ARCH_VER == 2) SDC1_IRQn = 28, #endif WIFIC_IRQn = 29, CODEC_DAC_IRQn = 30, CODEC_ADC_IRQn = 31, AVS_IRQn = 32, /* AVS psensor */ #if (CONFIG_CHIP_ARCH_VER == 2) GPIOC_IRQn = 33, PSRAMC_IRQn = 34, #endif #if (CONFIG_CHIP_ARCH_VER == 3) BLE_LL_IRQn = 35, BTCOEX_IRQn = 36, KEYSCAN_IRQn = 37, SMCARD_IRQn = 38, DMA_SEC_IRQn = 39, CAPSEN_IRQn = 40, LPUART0_IRQn = 41, LPUART1_IRQn = 42, TZASC_IRQn = 43, #endif } IRQn_Type;

      可以看到是因为蓝牙中断唤醒的,在休眠关闭蓝牙前关闭广播可以解决。

      1
    • D

      JPEG拍照设置旋转90、270度出图异常
      V Series • Posted at • dort91011

      0 Votes
      1 Replies
      843 Views

      livpo Replied at

      JPEG拍照旋转需设置Exif info信息中的旋转参数,否则图片显示时会默认认为旋转角度为0。设置方法如下:

      VENC_EXIFINFO_S stExitfInfo; memset(&stExitfInfo, 0, sizeof(VENC_EXIFINFO_S)); stExitfInfo.Orientation = rotate; AW_MPI_VENC_SetJpegExifInfo(venc_chn, &stExitfInfo);
      1
    • F

      SDK 如何下载
      MR Series • Posted at • fuyao

      0 Votes
      1 Replies
      808 Views

      baiwen Replied at

      参考阿志的SDK教程 ttps://d1.docs.aw-ol.com/study/study_3getsdktoc/
      另外建议您放一下出错的截图信息,方便分析 解决问题!

      1
    • U

      tina文件系统
      MR Series • Posted at • Uccccc

      0 Votes
      1 Replies
      1046 Views

      T Replied at

      @uccccc 使用overlayfs

      1
    • C

      MYC-YT507 openwrt编译
      编译和烧写问题专区 • Posted at • cainianqiuzu

      0 Votes
      1 Replies
      780 Views

      N Replied at

      @cainianqiuzu 米尔不是有FAE吗?

      1
    • baiwen

      万能的群友,如何才能表达出R128三核异构的独特之处,能做出形象的图我们赠送 R128 DevKit板+U盘资料!
      A Series • Posted at • 100ask

      0 Votes
      1 Replies
      849 Views

      baiwen Replied at

      @baiwen b2919670-24f7-475c-afee-849ac9e84d7a-132395bbe9f821ac998b25ca0079691.jpg 某位不知名大佬 YuzukiHD 推荐参考这种风格

      1
    • gb2047

      请问D1H怎样接jlink开发板呢?
      MR Series • Posted at • mm

      0 Votes
      1 Replies
      870 Views

      baiwen Replied at

      @gb2047 只用过平头哥的Cklink,没有试过Jlink

      1
    • newcastle

      启动阶段应用自启动时从/dev/random设备中获取随机数阻塞时间长
      V Series • Posted at • newcastle

      0 Votes
      1 Replies
      809 Views

      livpo Replied at

      对于随机数要求不高的应用,可以选择从/dev/urandom设备获取随机数来避免该问题,因为它在熵源不足时会使用伪随机数算法来生成数据,不会出现阻塞现场。

      缺点:获取的是伪随机数,随机性差

      1
    • D

      F1C200S TINA3.5 使用spinand
      其它全志芯片讨论区 • Posted at • dort91011

      0 Votes
      1 Replies
      1561 Views

      DAIZEBIN Replied at

      1、第一次烧录成功了,证明你的flash驱动应该是支持这颗nand的,所以可以烧进去
      2、但烧录进去不代表你flash驱动中的ID配置一定是正确的,有可能你拿到的flash驱动中对这颗物料的参数配置(坏块标记位、oob区域划分、ecc校验能力等)配置不正确,导致你第一次烧录的时候,在这颗flash上误标记了bad block,故后续烧录或者启动会提示很多的“bad block......”
      3、建议找一个常用型号的flash,先替换上去,看下是否能正常启动,可以试一下这款(MX35LF1GE4AB),这款在很早之前的驱动已经是支持的了

      1
    • H

      uart2 蓝牙播放音乐时会出现overrun问题
      V Series • Posted at • haaland

      0 Votes
      1 Replies
      757 Views

      livpo Replied at

      建议在uart中使用dma搬运数据,V853只有一个核,当uart频率升高,中断频率过高,此时cpu来不及响应uart的中断,所以出现overrun

      1
    • zznzzn

      四线电阻触摸屏测试tslib无法校准,而且点击按钮无反应
      飞凌嵌入式专区 • Posted at • zznzzn

      0 Votes
      1 Replies
      1017 Views

      livpo Replied at

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

      1
    • Z

      t113 mipi点不亮
      其它全志芯片讨论区 • Posted at • zzz555

      2 Votes
      1 Replies
      1854 Views

      A Replied at

      @zzz555 The clock signal may be operating at a speed outside the bandwidth of your oscilloscope. Check the Hz setting of your clock, and ensure it is less than the bandwidth of the oscilloscope (likely 100 MHz).

      If it is higher, then the signal will be attenuated. Configure the scope to be AC-coupled and try increasing the scope gain to see a faint signal.

      1
    • S

      v853开发板使用make menuconfig在哪里配置本地网卡和wifi
      V Series • Posted at • sunxi

      1 Votes
      1 Replies
      1278 Views

      N Replied at

      @sunxi 我记得menuconfig里面也有kernelmodel的配置项,里面也有network的配置项,在这里就有网卡和wifi驱动的配置

      1
    • U

      麻烦问一下大佬在使用trecorderdemo出现这个错误怎么解决
      MR Series • Posted at • Uccccc

      0 Votes
      1 Replies
      582 Views

      No one has replied

      1
    • H

      R329这个芯片现在还在推吗?新设计是否还推荐使用?
      A Series • Posted at • hqin2001

      0 Votes
      1 Replies
      807 Views

      DAIZEBIN Replied at

      @hqin2001 没有放弃吧,现在联系代理还是正常支持的

      1
    • zznzzn

      t113单独aplay可以播放语音文件但是mplayer没声音报错
      其它全志芯片讨论区 • Posted at • zznzzn

      0 Votes
      1 Replies
      1328 Views

      Y Replied at

      我也遇到这个问题 跟楼主是一样的 希望大佬们帮助解决一下
      如果用aplay 也是这样

      # aplay /root/test.wav ALSA lib pcm_hw.c:2021:(_snd_pcm_hw_open) Unknown field slave aplay: main:828: audio open error: Invalid argument
      1
    • H

      UDSIK分区表的大小和实际系统挂载的大小不对应
      Linux • Posted at • haaland

      1 Votes
      1 Replies
      1220 Views

      A Replied at

      UDISK属性写错了

      1
    • D

      OV5640摄像头画质问题
      其它全志芯片讨论区 • Posted at • dort91011

      0 Votes
      1 Replies
      1457 Views

      Q Replied at

      @dort91011 佬,你这个调通了吗?想找你交流一下416567819

      1
    • S

      参考adb代码写了个简单测试代码,在v853运行结果ep1能接收到pc发送的数据,但ep2却发不了数据
      V Series • Posted at • sofia

      0 Votes
      1 Replies
      629 Views

      No one has replied

      1
    • bayche

      linux的qspi接nor flash 读写
      Linux • Posted at • bayche

      0 Votes
      1 Replies
      894 Views

      livpo Replied at

      因为1线写速度都够了,qpi默认一线写,xip是四线指令四线读

      1
    • D

      韦东山官网提供的 T113SDK , tina-d1-h测试WIFI 和4G的方法好像与原来buildroot_100ask_t113-pro 的测试方法不一样吧
      MR Series • Posted at • ddrddr

      0 Votes
      1 Replies
      927 Views

      N Replied at

      @ddrddr

      ifconfig wlan0 up

      然后如果有wifi_scan_results_test命令可直接执行扫描WiFi,如果没有就用

      iw dev wlan0 scan |grep SSID
      1
    • zznzzn

      sqlite库文件如何放到img里面
      其它全志芯片讨论区 • Posted at • zznzzn

      0 Votes
      1 Replies
      791 Views

      livpo Replied at

      用adb push 或者U盘传到根文件目录下的/usr/lib/目录下

      1
    • B

      启动卡在这,就不会动了,然后也无法烧录了
      Wireless & Analog Series • Posted at • bigfly

      0 Votes
      1 Replies
      808 Views

      Y Replied at

      短接这两个触点
      然后上电烧录

      微信图片_20230922105738.jpg

      1
    • A

      D1网络连接问题
      MR Series • Posted at • a1370239560

      1 Votes
      1 Replies
      1184 Views

      whycan Replied at

      D1就是D1-H

      1
    • Y

      T133 使用键盘按2方式烧录成砖了
      Linux • Posted at • yuwei

      0 Votes
      1 Replies
      1043 Views

      whycan Replied at

      执行 muboot && mboot

      1
    • Z

      t113 mipi不能点亮
      其它全志芯片讨论区 • Posted at • zzz555

      0 Votes
      1 Replies
      1032 Views

      D Replied at

      @zzz555 在 t113 mipi不能点亮 中说:

      1142003732

      老铁 搞定了没?

      1
    • A

      R128-S2 驱动 1024x600 RGB 显示屏 并运行 LVGL
      A Series • Posted at • awwwwa

      6 Votes
      1 Replies
      1777 Views

      A Replied at

      屏参改一下

      lcd_driver_name = "default_lcd" lcd_backlight = 150 lcd_if = 0 lcd_x = 1024 lcd_y = 600 lcd_width = 150 lcd_height = 94 lcd_rb_swap = 0 lcd_dclk_freq = 48 lcd_pwm_used = 1 lcd_pwm_ch = 7 lcd_pwm_freq = 500000 lcd_pwm_pol = 1 lcd_hbp = 160 lcd_ht = 1344 lcd_hspw = 20 lcd_vbp = 20 lcd_vt = 635 lcd_vspw = 3 lcd_lvds_if = 0 lcd_lvds_colordepth = 1 lcd_lvds_mode = 0 lcd_frm = 0 lcd_io_phase = 0x0000 lcd_gamma_en = 0 lcd_bright_curve_en = 0 lcd_cmap_en = 0
      1
    • zznzzn

      H616低温reboot过程中进入休眠
      H/F/TV Series • Posted at • zznzzn

      0 Votes
      1 Replies
      1526 Views

      livpo Replied at

      在reboot老化的时候,关闭休眠

      从kernel的log来看,安卓层先发起了reboot,内核也收到reboot的消息

      #1[2023-07-11,16:56:45][ 41.176369][ T164] init: Received sys.powerctl=‘reboot,’ from pid: 490 (system_server) [2023-07-11,16:56:45][ 41.185428][ T164] init: sys.powerctl: do_shutdown: 0 IsShuttingDown: 0

      同时从安卓的log来看,安卓层也会有息屏关机的动作。

      downloadFileByUrl.jpg

      所以这个时候是刚好在reboot的过程中,安卓执行休眠打断了reboot并且休眠成功。一般建议做reboot老化的时候要关掉休眠,之前也出过类似现象

      1
    • newcastle

      XR806是不是可以直接用命令行和脚本进行编程,不需要再次烧录了呢
      Wireless & Analog Series • Posted at • newcastle

      0 Votes
      1 Replies
      803 Views

      L Replied at

      鸿蒙,没玩过。一直用的freertos

      1
    • H

      100ask-t113-pro board 如何 通过buildroot 搭建QT环境
      其它全志芯片讨论区 • Posted at • haaland

      0 Votes
      1 Replies
      819 Views

      livpo Replied at

      可以访问:https://github.com/DongshanPI/buildroot_100ask_t113-pro/blob/master/docs/07-Buildroot-SDK_DevelopmentGuide.md

      使用buildroot-SDK编译构建系统 简介 此套构建系统基于全志T113-S3芯片,适配了buildroot 2022lts主线版本,兼容了百问网的项目课程以及相关组件,真正做到了低耦合,高可用,使用不同的buildroot external tree规格,讲不同的项目 不同的组件分别管理,来实现更容易上手 也更容易学习理解。 安装必要依赖包 ubuntu-18.04

      运行环境配置: 此系统基于ubuntu18.04进行验证,在之前的基础之上还需要安装以下必要依赖

      book@100ask:~$ sudo apt-get install build-essential subversion git-core libncurses5-dev zlib1g-dev gawk flex quilt libssl-dev xsltproc libxml-parser-perl mercurial bzr ecj cvs unzip lib32z1 lib32z1-dev lib32stdc++6 libstdc++6 libncurses-dev u-boot-tools -y

      参考

      bb10ced5b443c6b7af2cf52871b987406faa37b9_2_690x358.png

      修改编译指定的配置文件

      book@100ask:~/buildroot-100ask_t113-pro/buildroot$ make BR2_EXTERNAL="../br2t113pro ../br2lvgl ../br2qt5" 100ask_t113-pro_sdcard_qt5_defconfig book@100ask:~/buildroot-100ask_t113-pro/buildroot$ make V=1

      最终编译生成一个 sdcard.img 烧录至开发板内 启动,就包含了 qt lib库等,同时QT 环境 也会在 buildroot源码根目录下 的 output/host内。

      1
    • S

      tina编译demo失败
      V Series • Posted at • sunxi

      0 Votes
      1 Replies
      756 Views

      A Replied at

      @sunxi source后 mkmpp,你的环境变量没有导入,不能直接make mk文件

      1
    • newcastle

      100ASK_V853-PRO开发板运行mpp例程sample_rtsp的问题
      V Series • Posted at • newcastle

      0 Votes
      1 Replies
      869 Views

      livpo Replied at

      @newcastle 可以尝试关闭在线模式

      15da8a41fab2b1a172a43069889d55e994285632.png

      1
    • D

      T113Pro开发板,改成TF卡启动后,系统分区异常
      其它全志芯片讨论区 • Posted at • ddrddr

      0 Votes
      1 Replies
      1253 Views

      X Replied at

      @ddrddr 跟踪学习一下

      1
    • zznzzn

      t113i编译失败
      创龙科技专区 • Posted at • zznzzn

      0 Votes
      1 Replies
      1009 Views

      livpo Replied at

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

      1
    • D

      t113的spi设置clk的频率
      其它全志芯片讨论区 • Posted at • dort91011

      0 Votes
      1 Replies
      1454 Views

      A Replied at

      你要注意一下,这儿的 spi 速度值并不是可以随便设置的! 因為 cpu 除频后会配不上! 会跳到默认的 10Mhz 的速度。

      建议你可以在 .... spi 中,加打印,看看你那值是否可以通过!

      /driver/spi/spi-sunxi.c 中

      /* set spi clock */ static void spi_set_clk(u32 spi_clk, u32 ahb_clk, struct sunxi_spi *sspi) { u32 spi_test = 100000000; u32 get_spi; dprintk(DEBUG_INFO, "set spi clock %d, mclk %d\n", spi_clk, ahb_clk); for(spi_test = 50000000; spi_test >= 20000000; spi_test -= 1000000) { clk_set_rate(sspi->mclk, spi_test); get_spi = clk_get_rate(sspi->mclk); printk("spi_test %d == get %d \n", spi_test, get_spi); }

      像我以 100Mhz 到 80Mhz , 每 1Mhz 做变化!

      [ 1.079831] spi_test 100000000 == get 100000000 ␍␊ [ 1.093426] spi_test 99000000 == get 96000000 ␍␊ [ 1.098527] spi_test 98000000 == get 96000000 ␍␊ [ 1.103587] spi_test 97000000 == get 96000000 ␍␊ [ 1.108714] spi_test 96000000 == get 96000000 ␍␊ [ 1.113807] spi_test 95000000 == get 92307692 ␍␊ [ 1.118905] spi_test 94000000 == get 92307692 ␍␊ [ 1.123996] spi_test 93000000 == get 92307692 ␍␊ [ 1.129127] spi_test 92000000 == get 87771428 ␍␊ [ 1.134193] spi_test 91000000 == get 87771428 ␍␊ [ 1.139293] spi_test 90000000 == get 87771428 ␍␊ [ 1.144406] spi_test 89000000 == get 87771428 ␍␊ [ 1.149506] spi_test 88000000 == get 87771428 ␍␊ [ 1.154601] spi_test 87000000 == get 85714285 ␍␊ [ 1.159739] spi_test 86000000 == get 85714285 ␍␊ [ 1.164835] spi_test 85000000 == get 80000000 ␍␊ [ 1.169939] spi_test 84000000 == get 80000000 ␍␊ [ 1.175074] spi_test 83000000 == get 80000000 ␍␊ [ 1.180142] spi_test 82000000 == get 80000000 ␍␊ [ 1.185243] spi_test 81000000 == get 80000000 ␍␊ [ 1.190346] spi_test 80000000 == get 80000000 ␍␊

      就可以知道,有一些值设置是不行的! 要特定值才行!

      1

    精华推荐

    • 【水经验混下载权限专用贴】如何升级LV2拉取SDK
    • T113/D1-H (MQ-Pro)驱动 OV5640 摄像头(内含驱动源码)
    • 全志在线开源芯片 新 SDK 平台下载方法汇总
    • 新 SDK 平台下载 D1-H/D1s SDK
    • 新 SDK 平台下载 V853 SDK
    • 新 SDK 平台下载 R329 SDK
    • 新 SDK 平台下载 MR813 SDK
    • 新 SDK 平台下载 XR806 SDK
    • D1s 哪吒开发板,电阻屏的配置方法
    • V85x E907 小核开发与使用
    • [哪吒开发板]Tina Linux SPI主从通信验证实录
    • T113-S3入门资料汇总(避坑指南)一
    • 【加精】D1 tina Docker 编译环境制作和使用
    • Tina Linux 存储介质切换:eMMC,SPI NAND,SPI NOR,SD Card,SD NAND
    • 【资料】V853&&V851 硬件参考设计
    换一批

    随便看看

    • 关于全志显示图层的问题
    • 分享个26键的lvgl-8拼音输入法,作者 @xfdr0805
    • 为什么D1的buildroot编译出来内存只有400多M
    • 助力智能穿戴设备新体验,华秋携手惠伦晶体提供全套选型方案
    • 萌新在淘宝整了一台“台电” P85 TLA016 平板电脑
    • t113 recovery模式无法进入,no ATAGS support: can't continue
    • R329按照官方文档下载无法编译
    • tlt113-MiniEVM调试问题
    • T507跳转U-boot失败
    • 仅用5000行代码,在V853上AI渲染出一亿幅山水画
    • T113使用gt911竖屏(longan SDK),触摸坐标不对!
    • PCM音频编码为AAC
    • v853断电后时间自动复位到1970,rtc还需要怎么设置吗?
    • v853如何接入4路AHD
    • v853 sdk 编译qt 无法通过
    • 1
    • 2
    • 34
    • 35
    • 36
    • 37
    • 38
    • 60
    • 61
    • 36 / 61

    精华推荐

    • 【水经验混下载权限专用贴】如何升级LV2拉取SDK
    • T113/D1-H (MQ-Pro)驱动 OV5640 摄像头(内含驱动源码)
    • 全志在线开源芯片 新 SDK 平台下载方法汇总
    • 新 SDK 平台下载 D1-H/D1s SDK
    • 新 SDK 平台下载 V853 SDK
    • 新 SDK 平台下载 R329 SDK
    • 新 SDK 平台下载 MR813 SDK
    • 新 SDK 平台下载 XR806 SDK
    • D1s 哪吒开发板,电阻屏的配置方法
    • V85x E907 小核开发与使用
    • [哪吒开发板]Tina Linux SPI主从通信验证实录
    • T113-S3入门资料汇总(避坑指南)一
    • 【加精】D1 tina Docker 编译环境制作和使用
    • Tina Linux 存储介质切换:eMMC,SPI NAND,SPI NOR,SD Card,SD NAND
    • 【资料】V853&&V851 硬件参考设计
    换一批

    随便看看

    • 关于全志显示图层的问题
    • 分享个26键的lvgl-8拼音输入法,作者 @xfdr0805
    • 为什么D1的buildroot编译出来内存只有400多M
    • 助力智能穿戴设备新体验,华秋携手惠伦晶体提供全套选型方案
    • 萌新在淘宝整了一台“台电” P85 TLA016 平板电脑
    • t113 recovery模式无法进入,no ATAGS support: can't continue
    • R329按照官方文档下载无法编译
    • tlt113-MiniEVM调试问题
    • T507跳转U-boot失败
    • 仅用5000行代码,在V853上AI渲染出一亿幅山水画
    • T113使用gt911竖屏(longan SDK),触摸坐标不对!
    • PCM音频编码为AAC
    • v853断电后时间自动复位到1970,rtc还需要怎么设置吗?
    • v853如何接入4路AHD
    • v853 sdk 编译qt 无法通过