sofia 发布的帖子

小核907开发包有所有中断的统计功能吗?谢谢

@whycanservice2 问下在v851s平台上运行正常的E907固件,放到v851se平台上运行内核已经打印E907已经成功运行起来但之后内核就卡死了,问下这两个平台sdk对预留内存有什么区别地方?

具体如图,打开任何升级包都会出现如下图这个,大佬们有知道吗

已从之前全志工作的同学得知 硬件有点问题

这个跟开发板厂家没关系吧 只要开发板没坏 毕竟人家只卖开发板 不卖技术支持...

@jingyan spi clk配置应该是没问题的.因为我软件32k频率去读spi的接口数据时,spi clk是33M输出,我示波器量过确认spi clk 是33M输出. 然后我软件定时64k频率去读spi数据,spi clk就没有输出了,spi相关寄存器都没改动

spi clk是33M,设置软件32k 频率读取spi数据是正常的,但设置64k 频率去读取spi数据时,发现spi clk信号没有输出了,配置文件驱动能力改成3也无效.哪位能帮忙看下吗?谢谢
使用到的spi3 配置如下:
[spi3]
spi_frequency = 33000000
spi3_cs_bitmap = 1
spi3_sclk = port:PH11<6><1><3><default>
spi3_mosi = port:PH12<6><1><3><default>
spi3_miso = port:PH13<6><1><3><default>
spi3_cs = port:PH14<6><1><3><default>

如题,打印如下：
[ 685.526589] sunxi_spi_transfer_one()1470 - [spi0] xfer timeout
[ 685.533120] spi-nand spi0.0: SPI transfer failed: -1
[ 685.538718] spi_master spi0: failed to transfer one message from queue
[ 685.546004] sunxi-spinand: read single page failed: -1
[ 685.551833] ubi0 error: ubi_io_read: error -1 while reading 12288 bytes from PEB 148:4096, read 0 bytes
[ 685.562339] CPU: 0 PID: 916 Comm: kworker/0:2 Not tainted 4.9.191 #6
[ 685.569434] Hardware name: sun8iw21
[ 685.573330] Workqueue: ubiblock0_4 ubiblock_do_work
[ 685.578825] [<c010d5a0>] (unwind_backtrace) from [<c010a694>] (show_stack+0x10/0x14)
[ 685.587487] [<c010a694>] (show_stack) from [<c040a9b0>] (ubi_io_read+0x1d8/0x2ac)
[ 685.595837] [<c040a9b0>] (ubi_io_read) from [<c0408c64>] (ubi_eba_read_leb+0x29c/0x3c4)
[ 685.604785] [<c0408c64>] (ubi_eba_read_leb) from [<c0408e3c>] (ubi_eba_read_leb_sg+0xb0/0x118)
[ 685.614531] [<c0408e3c>] (ubi_eba_read_leb_sg) from [<c0407908>] (ubi_leb_read_sg+0x68/0xb0)
[ 685.623995] [<c0407908>] (ubi_leb_read_sg) from [<c0411ad4>] (ubiblock_do_work+0xc8/0x100)
[ 685.633262] [<c0411ad4>] (ubiblock_do_work) from [<c012cb2c>] (process_one_work+0x1dc/0x318)
[ 685.642704] [<c012cb2c>] (process_one_work) from [<c012d81c>] (worker_thread+0x318/0x464)
[ 685.651851] [<c012d81c>] (worker_thread) from [<c0131d64>] (kthread+0xcc/0xe4)
[ 685.659929] [<c0131d64>] (kthread) from [<c0106e08>] (ret_from_fork+0x14/0x2c)
[ 685.668024] blk_update_request: I/O error, dev ubiblock0_4, sector 51408
[ 685.676037] SQUASHFS error: squashfs_read_data failed to read block 0x191a28c
[ 685.684665] SQUASHFS error: Unable to read fragment cache entry [191a28c]
[ 685.692278] SQUASHFS error: Unable to read page, block 191a28c, size 15c8c
[ 688.486816] UBIFS error (ubi0:5 pid 5): make_reservation: cannot reserve 2769 bytes in jhead 2, error -30
[ 688.497576] UBIFS error (ubi0:5 pid 5): do_writepage: cannot write page 10 of inode 155, error -30
[ 690.566575] sunxi_spi_transfer_one()1470 - [spi0] xfer timeout
[ 690.573105] spi-nand spi0.0: SPI transfer failed: -1
[ 690.578702] spi_master spi0: failed to transfer one message from queue
[ 690.585982] sunxi-spinand: read single page failed: -1
[ 690.591748] ubi0 warning: ubi_io_read: error -1 while reading 31744 bytes from PEB 476:230400, read only 0 bytes, retry
[ 693.526819] UBIFS error (ubi0:5 pid 5): make_reservation: cannot reserve 2770 bytes in jhead 2, error -30
[ 693.537705] UBIFS error (ubi0:5 pid 5): do_writepage: cannot write page 11 of inode 155, error -30
[ 695.606592] sunxi_spi_transfer_one()1470 - [spi0] xfer timeout
[ 695.613116] spi-nand spi0.0: SPI transfer failed: -1
[ 695.618828] spi_master spi0: failed to transfer one message from queue
[ 695.626120] sunxi-spinand: read single page failed: -1
[ 695.631907] ubi0 warning: ubi_io_read: error -1 while reading 31744 bytes from PEB 476:230400, read only 0 bytes, retry
[ 698.566810] UBIFS error (ubi0:5 pid 5): make_reservation: cannot reserve 2762 bytes in jhead 2, error -30
[ 698.577569] UBIFS error (ubi0:5 pid 5): do_writepage: cannot write page 12 of inode 155, error -30
[ 700.646589] sunxi_spi_transfer_one()1470 - [spi0] xfer timeout
[ 700.653121] spi-nand spi0.0: SPI transfer failed: -1
[ 700.658726] spi_master spi0: failed to transfer one message from queue
[ 700.666008] sunxi-spinand: read single page failed: -1
[ 700.671775] ubi0 error: ubi_io_read: error -1 while reading 31744 bytes from PEB 476:230400, read 0 bytes
[ 700.682472] CPU: 0 PID: 718 Comm: kworker/0:3 Not tainted 4.9.191 #6
[ 700.689662] Hardware name: sun8iw21
[ 700.693560] Workqueue: ubiblock0_4 ubiblock_do_work
[ 700.699062] [<c010d5a0>] (unwind_backtrace) from [<c010a694>] (show_stack+0x10/0x14)
[ 700.707733] [<c010a694>] (show_stack) from [<c040a9b0>] (ubi_io_read+0x1d8/0x2ac)
[ 700.716086] [<c040a9b0>] (ubi_io_read) from [<c0408c64>] (ubi_eba_read_leb+0x29c/0x3c4)
[ 700.725036] [<c0408c64>] (ubi_eba_read_leb) from [<c0408e3c>] (ubi_eba_read_leb_sg+0xb0/0x118)
[ 700.734665] [<c0408e3c>] (ubi_eba_read_leb_sg) from [<c0407908>] (ubi_leb_read_sg+0x68/0xb0)
[ 700.744103] [<c0407908>] (ubi_leb_read_sg) from [<c0411ad4>] (ubiblock_do_work+0xc8/0x100)
[ 700.753338] [<c0411ad4>] (ubiblock_do_work) from [<c012cb2c>] (process_one_work+0x1dc/0x318)
[ 700.762778] [<c012cb2c>] (process_one_work) from [<c012d81c>] (worker_thread+0x318/0x464)
[ 700.771918] [<c012d81c>] (worker_thread) from [<c0131d64>] (kthread+0xcc/0xe4)
[ 700.779991] [<c0131d64>] (kthread) from [<c0106e08>] (ret_from_fork+0x14/0x2c)
[ 700.788080] blk_update_request: I/O error, dev ubiblock0_4, sector 28666

@logicsoft ssd不是挺好的？为啥转？

@xiaowenge 这个每次人肉太麻烦了 我想自己综合看下全志基本常用cpu内部的各个外设资源

如题，现在有这方面需求，谢谢

@xiaowenge x小文哥 能否给个全志cpu选型手册啊

@xjy_5 怀疑这个板子usb布线这块有点问题

@xjy_5 板子重启后usb默认device 然后接电脑看看 不要在板子做任何操作 看看电脑能不能adb到板子

@sofia 现在插不同手机版本有些能enum，有些就不能

现在使用v853的usb接口作为deivce，插上手机后此时我们v853是什么中断?挂起还是复位？谢谢

@xjy_5 _5 你好 能否把pc端的usb软件发我下 谢谢

@awwwwa 另外不知道速率能达到多少

@awwwwa 谢谢 查了下adb forward使用方法像这个"adb forward tcp:8888 tcp:9999" 是走网络协议? 这个有点意思 有相关文档吗

@haolisheng 谢谢 这个我了解过 看网上大家都是在host上使用 我device上用的比较少 另外内核上该怎么配置呢

所诉问题如题，谢谢。

@awwwwa 谢谢指点

@awwwwa 谢答。我现在是运行uvc gadget，但电脑端没反应，查了otg-rule也是usb_device。同样的在nxp板子上是可以的。两板子内核配置比对了下，没什么不一样的地方。这里我看大家做host比较多，实在想不出哪里问题

在韦东山开发板的v853终端上运行测试测试程序后，pc端没有出现新设备.然而在nxp平台上跑同样的的测试程序,pc端可以识别到设备!
v853平台内核配置如下:

终端板子操作:
root@TinaLinux:/etc# ./setusbconfig uvc
sh: bulk: unknown operand
[ 202.498111] name:ddd21cc0-4100000.udc-controller
[ 202.498111] ;page:4100000.udc-controller
[ 202.498111] ;len:23
[ 202.510595] usb_gadget_probe_driver name:4100000.udc-controller
[ 202.517599] configfs-gadget gadget: uvc_function_bind
root@TinaLinux:/etc#
root@TinaLinux:/tmp# cat /sys/devices/platform/soc/usbc0/usb_device
[ 313.085568]
[ 313.085568] rmmod_device_driver
[ 313.085568]
[ 313.093415]
[ 313.093415] insmod_device_driver
[ 313.093415]
device_chose finished!

@awwwwa 谢谢 请问下这个配置在menuconfig哪个地方呢

@awwwwa 谢谢，就是lib_ise_gdc.a中的函数与其他库中的函数如libvenc_codec.a存在重定义,不知道在哪修改。

@whycan 谢谢，就是lib_ise_gdc.a中的函数与其他库中的函数如libvenc_codec.a存在重定义,这个如何解决呢(对tina结构不是很熟)。我现在用v853作为uvc设备通过usb插到电脑上显示，menuconfig打开ise, eis配置并编译就出现这个问题了

@haaland 你好 有编译成功过吗

menuconfig打开ise, eis配置，然后编译就出错了,如下:

@whycanservicem 这个没有被linux占用哦，dts相关引脚配置都被删除，另外特意在E907下单独输出方波都是可以的。

目前我们使用到v851s中的E907中的一个gpio PE10引脚作为外部中断输入.现在测试发现gpio中断后,gpio PE10中断使能寄存器0x02000290相关位会自动清0！！！
msh >drvgpio
//初始完打印的相关寄存器,未发生中断
0x020000c0: e1666666 ff771eff 000000ff 00000000
0x020000d0: 00000c40 11333333 11111111 00000011
0x020000e0: 00000000 00500555 00000000 00000000
0x02000280: 00000000 00000100 00000000 00000000
0x02000290: 00000400 00000080 00000000 00000000
//中断后打印的相关寄存器值。
0x020000c0: e1666666 ff771eff 000000ff 00000000
0x020000d0: 00000440 11333333 11111111 00000011
0x020000e0: 00000000 00500555 00000000 00000000
0x02000280: 00000000 00000100 00000000 00000000
0x02000290: 00000000 00000480 00000000 00000000