导航

    全志在线开发者论坛
    • 注册
    • 登录
    • 搜索
    • 版块
    • 话题
    • 在线文档
    • 社区主页
    1. 主页
    2. cvwithd1
    3. 帖子
    C
    • 资料
    • 关注 0
    • 粉丝 1
    • 我的积分 736
    • 主题 3
    • 帖子 16
    • 最佳 1
    • 群组 0

    cvwithd1 发布的帖子

    • 回复: D1出厂系统TinaLinux如何开机自动连接WIFI?

      @whycan 我在没有刷系统的前提下，把sleep和wifi_connect_ap_test加入到/etc/init.d/S99swupdate_autorun就可以了。

      发布在 MR Series
      C
      cvwithd1
    • 回复: D1出厂系统TinaLinux如何开机自动连接WIFI?

      @whycan 请问是加入到哪个文件？还是在/etc/init.d里面自己写一个文件？

      发布在 MR Series
      C
      cvwithd1
    • D1出厂系统TinaLinux如何开机自动连接WIFI?

      大家好。我用wifi_connect_ap_test可以成功连接无线网，但是我尝试开机自动连接WIFI失败。我尝试过把wifi_connect_ap_test <SSID> <PWD>加入到/etc/rc.local和/etc/init.d/S99swupdate_autorun，以及crontab @reboot wifi_connect_ap_test <SSID> <PWD>都不行。我估计是因为wlan0在开机最后一步初始化导致的，但是我也找不到wlan0初始化的地方。请问一下大家如何让D1用出厂系统TinaLinux时设置开机自动连接WIFI？

      发布在 MR Series
      C
      cvwithd1
    • 回复: D1 SDK附带的g++对RVV的支持问题

      @cvwithd1 问题已解决：https://github.com/opencv/opencv/wiki/OpenCV-RISC-V

      发布在 MR Series
      C
      cvwithd1
    • D1 SDK附带的g++对RVV的支持问题

      我在使用全志D1 SDK交叉编译OpenCV时遇到下面提示：

      Performing Test HAVE_CPU_RVV_SUPPORT (check file: cmake/checks/cpu_rvv.cpp)
Performing Test HAVE_CPU_RVV_SUPPORT - Failed
RVV is not supported by C++ compiler
Optimization RVV is not available, skipped
Dispatch optimization RVV is not available, skipped

      根据这个提示，应该是全志D1 SDK附带的g++不支持RVV。请问有办法解决这个问题吗？

      我交叉编译OpenCV时参考的是这个帖子：https://bbs.aw-ol.com/topic/227/在ubuntu中交叉编译opencv-4-5-1-运行于tina-linux中-整合帖/18

      发布在 MR Series
      C
      cvwithd1
    • 回复: mac下如何安装USB转串口线驱动

      @zhilong-wb 不用安装。直接usb连接，我这边可以用以下命令寻找和连接

      $ ll /dev/tty.usb*
/dev/tty.usbserial-A50285BI # 可能名字会不同
$ screen /dev/tty.usbserial-A50285BI 115200 # 用screen命令连接串口
      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @whycan FEL模式应该是可以进的，因为之前我就是通过这个方式尝试在mac下用phoenixsuit刷默认固件。

      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @whycan 特意搞了一台windows设备，但是故障板子插上去phoenixSuit检测不到。为了排除是windows上的问题，我把一块全新的D1插上去，倒是能够识别。看来是故障板子挂了。

      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @whycan 串口错误提示信息（见最后几行）如下：

      phoenixsuit_mac_v1.0.0 sudo ./phoenixsuit ../D1哪吒HDMI测试固件20210804（ 开机HDMI就有小企鹅启动logo）.img
*************Allwinnertech************
AW MacOS Burn firmware software V1.0.0
*************Allwinnertech************
-----LoadPluginCenter-------
library file path: /Users/fengyuantao/Downloads/phoenixsuit_mac_v1.0.0/plgvector.dll
library file path: /Users/fengyuantao/Downloads/phoenixsuit_mac_v1.0.0/LiveProc.Plg
-----SetLiveProc-------
library file path: /Users/fengyuantao/Downloads/phoenixsuit_mac_v1.0.0/plgvector.dll
library file path: /Users/fengyuantao/Downloads/phoenixsuit_mac_v1.0.0/luaeFex.dll
-----OnImage-------
DeviceThreadEntryForMac called
Register./luaBase.dll l_RegAllFun Sucess!
Register./luaeFex.dll l_RegAllFun Sucess!
Register./luadec.dll l_RegAllFun Sucess!
copy luatool from local
----enter sem_wait-------
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
Begin Burn the image!
progress 0%Register./luaBase.dll l_RegAllFun Sucess!
Register./luaeFex.dll l_RegAllFun Sucess!
Register./luadec.dll l_RegAllFun Sucess!
copy luatool from local
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
--------------Init Called------------------
workDir	/Users/fengyuantao/Downloads/phoenixsuit_mac_v1.0.0
ImgLenHigh	0
ImgLenLow	29854720
Mode	8
hWnd	0
imgFilePath	../D1哪吒HDMI测试固件20210804（开机HDMI就有小企鹅启动logo）.img
[TL_MSG]:Mode = 8, ImgLenHigh=0, ImgLenLow = 1c78c00, imgFilePath = ../D1哪吒HDMI测试固件20210804（开机HDMI就有小企鹅启动logo）.img

IMAGEWTY
ItemTableSize = 1048576
[TL_MSG]:Tools Open Img

---fun end---
--------------entry-fel2fes Called-----------
felDevName	01130000
[TL_MSG]:Hi, I'm fel, dev=01130000

./AllWinnerDevice.cpp Fex_Open 604
FEL RecordDev: 01130000
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
[TL_MSG]:To down and Run fes1-1

[TL_MSG]:fes1 down addr = 0x28000, retAddr =0x28340

[TL_MSG]:To clear fes aide log

[TL_FEX]:fel UP addr=0x28340, len=136

[TL_MSG]:SYS_PARA_LOG read = 0x4d415244

[TL_MSG]:dram paras[0]: 0x318

[TL_MSG]:dram paras[1]: 0x3

[TL_MSG]:dram paras[2]: 0x7b7bfb

[TL_MSG]:dram paras[3]: 0x1

[TL_MSG]:dram paras[4]: 0x10f210f2

[TL_MSG]:dram paras[5]: 0x4001000

[TL_MSG]:dram paras[6]: 0x1c70

[TL_MSG]:dram paras[7]: 0x42

[TL_MSG]:dram paras[8]: 0x18

[TL_MSG]:dram paras[9]: 0x0

[TL_MSG]:dram paras[10]: 0x4a2195

[TL_MSG]:dram paras[11]: 0x2423190

[TL_MSG]:dram paras[12]: 0x8b061

[TL_MSG]:dram paras[13]: 0xb4787896

[TL_MSG]:dram paras[14]: 0x0

[TL_MSG]:dram paras[15]: 0x48484848

[TL_MSG]:dram paras[16]: 0x48

[TL_MSG]:dram paras[17]: 0x1620121e

[TL_MSG]:dram paras[18]: 0x0

[TL_MSG]:dram paras[19]: 0x0

[TL_MSG]:dram paras[20]: 0x0

[TL_MSG]:dram paras[21]: 0x870000

[TL_MSG]:dram paras[22]: 0x24

[TL_MSG]:dram paras[23]: 0x34056103

[TL_MSG]:dram paras[24]: 0x0

[TL_MSG]:dram paras[25]: 0x0

[TL_MSG]:dram paras[26]: 0x0

[TL_MSG]:dram paras[27]: 0x0

[TL_MSG]:dram paras[28]: 0x0

[TL_MSG]:dram paras[29]: 0x0

[TL_MSG]:dram paras[30]: 0x0

[TL_MSG]:dram paras[31]: 0x0

[TL_MSG]:To down and Run uboot

[TL_MSG]:u-boot down addr = 0x42000000

[TL_MSG]:workmode = 0x10

[TL_MSG]:dtb down addr = 0x42200000

[TL_MSG]:sysconfig down addr = 0x42300000

---fun end---
Fel Thread Finished!
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
FES find FEL RecordDev: 01130000
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
--------------entry fes_thread Called---------
portId	0
fesDevName	01130000
hubId	0
DeviceId	1
[TL_MSG]:enter FES--01130000

./AllWinnerDevice.cpp Fex_Open 604
Found allwinner usb device (vendor 7994, product 61416), location id 01130000
Found 1 devices
[TL_MSG]:set erase flag 0

[TL_MSG]:Verify: media crc = 0

progress 3%[TL_MSG]:save item to mem :(12345678,1234567890___MBR) realLen(65536)

./buffer.cpp, pBuffer = 0x7fa160008004, nLen = 16380, crc32 = 1283179231[TL_MSG]:name = boot-resource, keydata = 0

[TL_MSG]:name = env, keydata = 0

[TL_MSG]:name = env-redund, keydata = 0

[TL_MSG]:name = boot, keydata = 0

[TL_MSG]:name = rootfs, keydata = 0

[TL_MSG]:name = dsp0, keydata = 0

[TL_MSG]:name = recovery, keydata = 0

[TL_MSG]:name = UDISK, keydata = 0

[TL_MSG]:name = , keydata = 0

Fex_transmit_receive ./AllWinnerDevice.cpp, 782 status stage status Error 		   CSWStatus=fd(0) Magic=53555741(53555741)
Fex_transmit_receive ./AllWinnerDevice.cpp, 782 status stage status Error 		   CSWStatus=fd(0) Magic=53555741(53555741)
Fex_transmit_receive ./AllWinnerDevice.cpp, 782 status stage status Error 		   CSWStatus=fd(0) Magic=53555741(53555741)
<TL_FEX>Err./usbtool.lua_1536>:Fail to send fex cmd verify status

<TL_ERR>:./usbtool.lua_3030>:verify status error

<TL_ERR>:./usbtool.lua_3326>:Verify status error

progress 4%<TL_ERR>:./usbtool.lua_3994>:down mbr error

L296, Exception, returned value of Tools.entry_fes_thread is error.

Error!!!: returned value of Tools.entry_fes_thread is error
./DeviceMessage/ASuitDeviceMessage.cpp 128 failed
----exit-------
      发布在 MR Series
      C
      cvwithd1
    • 回复: 【实践操作】自己从头构建riscv 64 ubuntu等发行版系统！

      @allwinnertech 我看这里用的ubuntu是ubuntu-base，不是满血的python。ubuntu现在有释出一个给另一个厂商做的risc v镜像，不知道那个能不能直接跑在d1上。

      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @cvwithd1 给大伙提个醒，不要直接把改了rootfs的固件直接刷到板子上，要不然会报错，而且再尝试刷默认固件也会失败....

      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @cvwithd1 我把$sdk/tina-d1-open/device/config/chips/d1/configs/nezha/sys_partition.fex里面rootfs的大小翻倍，pack就可以了

      发布在 MR Series
      C
      cvwithd1
    • 回复: Tina打包img出现过大的问题应该怎么设置

      @xiaowenge 请问这个应该怎么修改？vim打开是二进制文件。

      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @whycan

      勾选python3之后编译通过，但是pack的时候报如下错误：

      D1@63d132a0f2eb:~/tinalinux-sdk/tina-d1-open-v1.0$ pack
--==========--
PACK_CHIP         sun20iw1p1
PACK_PLATFORM     tina
PACK_BOARD        d1-nezha
PACK_KERN
PACK_DEBUG        uart0
PACK_SIG          none
PACK_SECURE       none
PACK_MODE         normal
PACK_FUNC         android
PACK_PROGRAMMER   none
PACK_TAR_IMAGE    none
PACK_TOPDIR       /home/D1/tinalinux-sdk/tina-d1-open-v1.0
--==========--
No kernel param, parse it from d1
copying tools file
copying configs file
storage_type value is 5
rm /home/D1/tinalinux-sdk/tina-d1-open-v1.0/out/d1-nezha/image/sys_partition_nor.fex
rm /home/D1/tinalinux-sdk/tina-d1-open-v1.0/out/d1-nezha/image/image_nor.cfg
copying boot resource

LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03
copying boot file
make user resource for : /home/D1/tinalinux-sdk/tina-d1-open-v1.0/out/d1-nezha/image/sys_partition.fex
handle partition user-res
no user resource partitions
APP_PART_DOWNLOAD_FILE = /home/D1/tinalinux-sdk/tina-d1-open-v1.0/out/d1-nezha/image/app.fex
Need size of filesystem
no data resource partitions
don't build dtbo ...
update_chip
pack boot package
GetPrivateProfileSection read to end
content_count=3
LICHEE_REDUNDANT_ENV_SIZE config in BoardConfig.mk
--mkenvimage create redundant env data!--
---redundant env data size 0x20000---
packing for tina linux
normal
ERROR: dl file rootfs.fex size too large
ERROR: filename = rootfs.fex
ERROR: dl_file_size = 79104 sector
ERROR: part_size = 40824 sector
ERROR: update mbr file fail
ERROR: update_mbr failed
D1@63d132a0f2eb:~/tinalinux-sdk/tina-d1-open-v1.0$
      发布在 MR Series
      C
      cvwithd1
    • 回复: 在D1 TinaLinux SDK中编译Python报错

      @whycan

      谢谢你的回答！

      其实我是有需求要在D1上用python调用opencv。如果编译python同时能够编译到numpy+pyyaml的话会方便很多。我看menuconfig里自带的python3.5就没有numpy和pyyaml，所以就没有尝试编译python3.5。

      不过非常感谢你的尝试！我现在想根据你提供的buildroot，试试看有没有办法可以编译到python3.6+numpy+pyyaml。

      发布在 MR Series
      C
      cvwithd1
    • 在D1 TinaLinux SDK中编译Python报错

      我尝试在TinaLinux SDK v1.0上编译Python 2.7 & 3.5：

      make menuconfig
# Language -> Python -> python (这会导致python-ctypes强制开启)

      然后编译时，在编译到python-ctypes的时候报错：

        File "/tmp/tmpfsbMt5/pip-9.0.3-py2.py3-none-any.whl/pip/__init__.py", line 45, in <module>
  File "/tmp/tmpfsbMt5/pip-9.0.3-py2.py3-none-any.whl/pip/vcs/mercurial.py", line 9, in <module>
  File "/tmp/tmpfsbMt5/pip-9.0.3-py2.py3-none-any.whl/pip/download.py", line 36, in <module>
  File "/tmp/tmpfsbMt5/pip-9.0.3-py2.py3-none-any.whl/pip/utils/glibc.py", line 4, in <module>
  File "/home/d1/tinalinux-sdk/tina-d1-open-v1.0/out/d1-nezha/compile_dir/target/host/Python-2.7.15/Lib/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: No module named _ctypes
make[4]: *** [install] Error 1

      请问有解决方案吗？或者我应该根据文档刷debian，这样用python会更方便一点？

      发布在 MR Series
      C
      cvwithd1
    • 1 / 1