天嵌 ARM开发社区

 找回密码
 注册
查看: 12026|回复: 14

can总线,已经写好了。包括hal,jni和app 源码已经在4楼贴出来了

[复制链接]
wangdapengxp 发表于 2013-6-17 12:14:07 | 显示全部楼层 |阅读模式
本帖最后由 wangdapengxp 于 2013-6-27 10:21 编辑

源码已经在4楼贴出来了  
源码已经在4楼贴出来了
源码已经在4楼贴出来了






因为技术支持没有时间,还想研究android下的can总线,各种查找资料终于测试通过了。

在天嵌提供的android文件系统中,替换掉以下四个文件,就可以直接调用can总线的接口了。
mycan.default.so      放到开发板system/lib/hw目录下
libandroid_servers.so 放到开发板system/lib目录下
framework.jar          放到开发板system/framework/目录下
services.jar             放到开发板system/framework/目录下
第一个可以直接复制到其目录下,其他3个需要覆盖原来的文件,记得拷贝和覆盖以后,用chmod 777 xxx.xx来修改权限,都拷贝和覆盖完并且修改权限以后,重启开发板,第一次测试的同学,记得要在启动的时候,把配置修改为can总线,默认好像是串口。

我写了一个app不过我是模仿广告机写了一个电梯的多媒体,有兴趣的可以安装玩玩,很简单。

根据can总线上的数据,来对电梯状态进行一下显示,语音报站(需要在sd卡里有声音文件)

想自己写app玩的同学,can总线的接口函数是
初始化:没有接口,我在系统初始化的时候,把它写死了,是50kbps
接受数据:mycandump(0x00000000,0x0000007f)    参数1:ID   参数2:屏蔽滤波  例子中就是只接受id后7位为0的can数据(我主节点是后7位为0的数据,都是广播数据)。
发送数据:set_data(i,data) 然后 mycansend(0x01010025,8,1,0,0,1); 先设置要发送的数据内容,然后用mycansend()来发送,参数1:发送节点的id  参数2:数据长度 参数3:标准贞/扩展贞 参数4:数据贞/请求贞 参数5和参数6配合使用:10无限发/01发一次/平时00(找网络的例子,没有改参数这一块,这地方郁闷了) 建议后两个参数就用 0 1 这样就只发一次就好了。

覆盖完上面的4个文件以后,可以在java中在eclipse里直接
import android.os.ServiceManager;
import android.os.IMycanService;
然后private IMycanService mycanservice = null;
用ret = mycanservice.mycandump(0x00000000,0x0000007f); 接收
用mycanservice.set_data(i,data);
int ret = mycanservice.mycansend(0x01010025,8,1,0,0,1);来发送


这样写的郁闷之处是,写的app不能用eclipse直接写,它不认那个ServiceManager和IMycanService
你需要用用eclipse做ui和简单的界面操作,当需要用can的时候,你把这个工程拷贝到天嵌给的那个android文件系统中packages/expermental文件夹下,全部拷贝过去,然后删除gen文件夹,用gedit来编辑你的源文件,然后用mmm来编译你的工程,记得写个android.mk  这个操作网络上有很多说明,可以找个看看,就是想用什么系统包/系统服务什么之类的,我是参考一个说用电源高亮显示的一篇文章,按照他说的如何编译弄的。

编译之后会在out/***一堆文件夹/system/app里找到你编译后的app文件,安装到开发板OK

可以用我的app先测试下,用usb转can(自己买的,500多块 好贵啊)链接到开发板,模拟发送就可以看见显示效果了,想测试下的同学可以发送(id为0x0000a380  扩展贞格式  数据内容:31 30 02 02 04 05 06 07)来看一下,会播放视频,但是报站的语音文件需要放到SD卡里,我的视频文件,是放到sd卡根目录下天嵌提供的测试视频,那个兔子弄蝴蝶那个视频文件,不知道如果sd卡里没有这个视频的话可能会出错,我程序里好像没处理如果找不到这个文件的异常。

反正弄了能有两个月了,哎呀我去,终于能通讯了,小小感慨下,希望技术支持能多弄点新产品的测试程序,至少没弄也给点思路是吧,我们这么支持新产品,希望给你们带来所谓的引爆点是吧,你们也应该给我们这种人点支持。

我晕,jar格式的还不能上传,弄个文件夹压缩下

还少2个文件,framework.jar这个文件超过4M 我研究下怎么能发上来 (改天发吧,今天上传文件大小被限制了)

有兴趣自己写的我推荐下这个文章,挺好的   android驱动开发全过程(有图有真相).doc  我上传不了了,我就是按照这个写的,有兴趣的百度一下就能找到。。

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?注册

x

评分

参与人数 3 +7 收起 理由
mj6947 + 2 很给力!
wilbur01 + 3
freewing + 2 很给力!

查看全部评分

 楼主| wangdapengxp 发表于 2013-6-27 09:01:21 | 显示全部楼层
本帖最后由 wangdapengxp 于 2013-6-27 09:39 编辑















上源码了,和编译过程

整理的有点乱哈,说明一下:

解压完以后,应该是
jni 文件夹:里面有Android.mk com_android_server_MycanService.cpp onload.cpp
java 文件夹:里面有Frame.java  MycanService.java SystemServer.java
libmycan文件夹:里面有Android.mk  mycan.c
linux文件夹:里面有can.h 和can文件夹
os文件夹:里面有IMycanService.aidl
还有单独的两个文件 mycan.h 和 Android.mk

操作目录是天嵌带的android文件系统源码目录。
第一步:头文件
把mycan.h 放到hardware/libhardware/include/hardware  下面,把linux文件夹拷贝到hardware/libhardware/include 下,因为编译的时候总是提示少这少那的,头文件包含的东西我一搜索找到7,8个,也不知道用的是哪个,索性不管了把用的自己弄过来就没找不到的提示了。
第二步:实现文件
把libmycan文件夹拷贝到device/embedsky/tq335x下面

编译,设置编译环境,手册上有,然后用 mmm device/embedsky/tq335x/libmycan  编译后 会生成mycan.default.so 这个库文件

第三步:JNI
把jni文件夹下的文件,拷贝到 frameworks/base/services/jni 目录下,需要覆盖部分原来的文件
编译:mmm frameworks/base/services/jni   生成 libandroid_servers.so 这个库文件

把os文件夹下的IMycanService.aidl 拷贝到 frameworks/base/core/java/android/os 下,接着,把单独的那个Android.mk文件覆盖到frameworks/base 下。
编译:mmm frameworks/base  生成 framework.jar 这个包

把java文件夹下的文件 拷贝到 frameworks/base/services/java/com/android/server 下,其中需要覆盖sys……那个文件
编译:mmm frameworks/base/services/java  生成 services.jar 这个包  

一共编译后,生成了,  mycan.default.so       libandroid_servers.so     framework.jar     services.jar 这四个文件
位置分别在
out/target/product/tq335x/system/lib/hw/
out/target/product/tq335x/system/lib/
out/target/product/tq335x/system/framework/
out/target/product/tq335x/system/framework/

把这几个文件拷贝到开发板相应的文件夹下  替换掉原来的文件就可以了,需要chmod 777  xxx   这个几个文件

写app应用程序的时候,需要
import android.os.IMycanService;
private IMycanService mycanservice = null;
接受
mycanservice.mycandump(xxx,xxx);
发送
mycanservice.set_data(xx);
mycanservice.mycansend(xxxxxxx);

参数自己看下源码里吧,十分简单,测试啥的足够用了。

can的初始化都在libmycan里了,可以自己进去修改波特率什么的,有时间也可以弄成动态加载设置的,如果有人有空写了记得发给我一份啊

谢谢大家

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?注册

x
回复 支持 3 反对 0

使用道具 举报

亚瑟王 发表于 2013-6-17 14:14:00 | 显示全部楼层
亲,给你加精了,送10个金币。
TQ-lkp 发表于 2013-6-20 18:03:56 | 显示全部楼层
嘿,能否将你编绎过的源码共享下,我将其加到我们的android系统源码中分享给更多的人,我们会将你的名字添加到源码的说明中。谢谢!
zhengpyu 发表于 2013-10-8 11:11:22 | 显示全部楼层
wangdapengxp 发表于 2013-6-27 09:01
上源码了,和编译过程

整理的有点乱哈,说明一下:

感谢楼主,下载学习了,我主要是不懂socket can的编程
gjh123 发表于 2013-10-16 09:48:06 | 显示全部楼层
@wangdapengxp 你好,我按照帖子操作步骤做的时候遇到了一个问题求帮助。四个附件下载后,有三个文件可以复制或替换过去,但是libandroid_servers.so这个文件替换的时候出问题了,显示正在覆盖的界面时很快就自动重启系统进入到了boot界面,卡在了显示ANDROID这个界面无限循环了,重新上电依然如此。之后我又试着将这四个文件在天嵌带的文件系统里替换,之后重新编译文件系统生成root.bin,重新烧写yaffs,之后系统还是一直卡在ANDROID界面,CAN总线的配置也选择过了。用串口交互工具截取到卡在ANDROID处时的串口信息如下:(最下面重复出现的语句就是卡在ANDROID界面时候对应的语句。请问怎样才能修改正常,并且能使用can通信功能)
gjh123 发表于 2013-10-16 09:49:41 | 显示全部楼层
Welcome to use TQ3358 Board!
boot from NAND...


##### EmbedSky BIOS for TQ3358 #####
This Board: SDRAM is 512MB; LCD display size is: 800X480
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x280000, size 0x300000
3145728 bytes read: OK
setting bootargs ...
bootargs=console=ttyO0,115200n8 androidboot.console=ttySAC0 root=/dev/mtdblock8 rootfstype=yaffs2 rw rootwait=1 init=/init ip=off lcd=X800Y480 uart1_d_can=d_can uart2_i2c2=uart2
Booting from nand ...

NAND read: device 0 offset 0x580000, size 0x500000
5242880 bytes read: OK
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.2.0-EmbedSky
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4110904 Bytes = 3.9 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0-EmbedSky (root@embedsk-server) (gcc version 4.4.6 (for TQ210 EmbedSky Tech) ) #10 Fri Mar 22 11:04:02 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: tq3358
Memory policy: ECC disabled, Data cache writeback
AM335X ES1.0 (sgx neon )
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyO0,115200n8 androidboot.console=ttySAC0 root=/dev/mtdblock8 rootfstype=yaffs2 rw rootwait=1 init=/init ip=off lcd=X800Y480 uart1_d_can=d_can uart2_i2c2=uart2
user X800Y480 lcd.
uart1_d_can, user select d_can.
uart2_i2c2, user select uart2.
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 509964k/509964k available, 14324k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc0796000   (7736 kB)
      .init : 0xc0796000 - 0xc07f1000   ( 364 kB)
      .data : 0xc07f2000 - 0xc084ca60   ( 363 kB)
       .bss : 0xc084ca84 - 0xc098e408   (1287 kB)
NR_IRQS:396
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
OMAP clockevent source: GPTIMER2 at 24000000 Hz
omap_dm_timer_switch_src: Switching to HW default clocksource(sys_clkin_ck) for timer1, this may impact timekeeping in low power state
OMAP clocksource: GPTIMER1 at 24000000 Hz
sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
Console: colour dummy device 80x30
Calibrating delay loop... 718.02 BogoMIPS (lpj=3590144)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
omap_hwmod: gfx: failed to hardreset
omap_hwmod: pruss: failed to hardreset
print_constraints: dummy:
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
da8xx_lcdc.0: alias fck already exists
TSC connected to beta GP EVM
omap_i2c.1: alias fck already exists
omap_i2c.2: alias fck already exists
davinci-mcasp.1: alias fck already exists
omap_hsmmc.0: alias fck already exists
d_can.0: alias fck already exists
d_can.1: alias fck already exists
omap2_mcspi.1: alias fck already exists
omap2_mcspi.2: alias fck already exists
edma.0: alias fck already exists
edma.0: alias fck already exists
edma.0: alias fck already exists
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
tps65910 1-002d: JTAGREVNUM 0x1
print_constraints: VRTC:
print_constraints: VIO: at 1500 mV
print_constraints: VDD1: 600 <--> 1500 mV at 1262 mV normal
print_constraints: VDD2: 600 <--> 1500 mV at 1137 mV normal
print_constraints: VDD3: 5000 mV
print_constraints: VDIG1: at 1800 mV
print_constraints: VDIG2: at 1800 mV
print_constraints: VPLL: at 1800 mV
print_constraints: VDAC: at 1800 mV
print_constraints: VAUX1: at 1800 mV
print_constraints: VAUX2: at 3300 mV
print_constraints: VAUX33: at 3300 mV
print_constraints: VMMC: at 3300 mV
tps65910 1-002d: No interrupt support, no core IRQ
omap_i2c omap_i2c.2: bus 2 rev2.4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource gp timer
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
musb-hdrc musb-hdrc.0: dma type: pio
musb-hdrc musb-hdrc.0: USB OTG mode controller at e081c000 using PIO, IRQ 18
musb-hdrc musb-hdrc.1: dma type: pio
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 3.2.0-EmbedSky musb-hcd
usb usb1: SerialNumber: musb-hdrc.1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at e081e800 using PIO, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
omap-gpmc omap-gpmc: GPMC revision 6.0
Registering NAND on CS0
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
yaffs: yaffs built Mar 21 2013 16:49:14 Installing.
msgmni has been set to 996
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found A70_TN92 panel
omap_uart.0: ttySAC0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttySAC1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttySAC2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
gjh123 发表于 2013-10-16 09:50:17 | 显示全部楼层
omap_uart.3: ttySAC3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttySAC4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttySAC5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
Register led successfully!
Register beep successfully!
brd: module loaded
loop: module loaded
i2c-core: driver [tsl2550] using legacy suspend method
i2c-core: driver [tsl2550] using legacy resume method
mtdoops: mtd device (mtddev=name/number) must be supplied
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
Creating 9 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "SPL"
0x000000020000-0x000000040000 : "SPL.backup1"
0x000000040000-0x000000060000 : "SPL.backup2"
0x000000060000-0x000000080000 : "SPL.backup3"
0x000000080000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x000000580000 : "LOGO"
0x000000580000-0x000000a80000 : "Kernel"
0x000000a80000-0x000010000000 : "File System"
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can.0: device registered (irq=52, irq_obj=53)
d_can d_can.1: device registered (irq=55, irq_obj=56)
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffe
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver SMSC LAN8710/LAN8720
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_subset
cdc_ncm: 04-Aug-2011
usbcore: registered new interface driver cdc_ncm
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usb 1-1: new high-speed USB device number 2 using musb-hdrc
usb 1-1: New USB device found, idVendor=1a40, idProduct=0101
usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1: Product: USB 2.0 Hub
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
gadget: Mass Storage Function, version: 2009/09/11
gadget: Number of LUNs=1
lun0: LUN: removable file: (no medium)
gadget: android_usb ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 3.2.0-EmbedSky musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
input: Resistance_ts as /devices/platform/omap/tsc/input/input0
using rtc device, omap_rtc, for alarms
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: already running
i2c /dev entries driver
Linux video capture interface: v2.00
i2c-core: driver [tuner] using legacy suspend method
i2c-core: driver [tuner] using legacy resume method
i2c-core: driver [msp3400] using legacy suspend method
i2c-core: driver [msp3400] using legacy resume method
usbcore: registered new interface driver usbvision
USBVision USB Video Device Driver for Linux : 0.9.11
usbcore: registered new interface driver zr364xx
zr364xx: Zoran 364xx
usbcore: registered new interface driver stkwebcam
sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.48
usbcore: registered new interface driver sn9c102
et61x251: V4L2 driver for ET61X[12]51 PC Camera Controllers v1.1.10
usbcore: registered new interface driver et61x251
pwc: Philips webcam module version 10.0.15 loaded.
pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
usbcore: registered new interface driver Philips webcam
gspca_main: v2.14.0 registered
usbcore: registered new interface driver benq
usbcore: registered new interface driver conex
usbcore: registered new interface driver cpia1
usbcore: registered new interface driver etoms
usbcore: registered new interface driver finepix
usbcore: registered new interface driver jeilinj
usbcore: registered new interface driver kinect
usbcore: registered new interface driver konica
usbcore: registered new interface driver mars
usbcore: registered new interface driver mr97310a
usbcore: registered new interface driver nw80x
usbcore: registered new interface driver ov519
usbcore: registered new interface driver ov534
usbcore: registered new interface driver ov534_9
usbcore: registered new interface driver pac207
usbcore: registered new interface driver pac7302
usbcore: registered new interface driver pac7311
usbcore: registered new interface driver se401
usbcore: registered new interface driver sn9c2028
usbcore: registered new interface driver sn9c20x
usbcore: registered new interface driver sonixb
usbcore: registered new interface driver sonixj
usbcore: registered new interface driver spca500
usbcore: registered new interface driver spca501
usbcore: registered new interface driver spca505
usbcore: registered new interface driver spca506
usbcore: registered new interface driver spca508
usbcore: registered new interface driver spca561
usbcore: registered new interface driver spca1528
usbcore: registered new interface driver sq905
usbcore: registered new interface driver sq905c
usbcore: registered new interface driver sq930x
usbcore: registered new interface driver sunplus
usbcore: registered new interface driver stk014
usbcore: registered new interface driver stv0680
usbcore: registered new interface driver t613
usbcore: registered new interface driver gspca_topro
usbcore: registered new interface driver tv8532
gjh123 发表于 2013-10-16 09:51:41 | 显示全部楼层
usbcore: registered new interface driver vc032x
usbcore: registered new interface driver vicam
usbcore: registered new interface driver xirlink-cit
usbcore: registered new interface driver zc3xx
usbcore: registered new interface driver ALi m5602
usbcore: registered new interface driver STV06xx
usbcore: registered new interface driver gspca_gl860
usbcore: registered new interface driver s2255
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
Linux telephony interface: v1.00
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCILL protocol initialized
Bluetooth: BlueFRITZ! USB driver ver 1.2
usbcore: registered new interface driver bfusb
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
_regulator_get: 1-0018 supply IOVDD not found, using dummy regulator
_regulator_get: 1-0018 supply DVDD not found, using dummy regulator
_regulator_get: 1-0018 supply AVDD not found, using dummy regulator
_regulator_get: 1-0018 supply DRVDD not found, using dummy regulator
asoc: tlv320aic3x-hifi <-> davinci-mcasp.1 mapping ok
ALSA device list:
  #0: AM335X EVM
oprofile: hardware counters not available
oprofile: using timer interrupt.
nf_conntrack version 0.5.0 (7968 buckets, 31872 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
mux: Failed to setup hwmod io irq -22
Power Management for AM33XX family
Trying to load am335x-pm-firmware.bin (60 secs timeout)
Copied the M3 firmware to UMEM
omap_hwmod: wkup_m3: wkup_m3: hwmod data error: OMAP4 does not support st_shift
clock: disabling unused clocks to save power
Detected MACID=bc:6a:29:84:f1:c6
input: gpio-keys as /devices/platform/gpio-keys/input/input1
Goodix-TS 2-005d: Install gt811 driver.
Goodix-TS 2-005d: Driver Release Date:2012-02-08
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 mmc 956 MiB
mmcblk0: p1
Goodix-TS 2-005d: GT811 Verion:0x2010
Goodix-TS 2-005d: chip_type=0x11
Goodix-TS 2-005d: version=0x1010
Goodix-TS 2-005d: rom_version=0x45
Goodix-TS 2-005d: start_addr=0x4100
Goodix-TS 2-005d: file_size=0x0ef0
Goodix-TS 2-005d: fw_checksum=0x0624ad
Goodix-TS 2-005d: gt811_downloader
Goodix-TS 2-005d: current version 0x2010, target verion 0x1010
Goodix-TS 2-005d: Rom version not match,exidownloader
Goodix-TS 2-005d: GT811 init info:X_MAX=800,Y_MAX=480,TRIG_MODE=RISING EDGE
input: Capacitance_ts as /devices/virtual/input/input2
Goodix-TS 2-005d: GT811 Verion:0x2010
Goodix-TS 2-005d: Create proc entry success!
Goodix-TS 2-005d: Start Capacitance_ts in interrupt mode,Driver Modify Date:2012-01-05
Failed to request GPIO:58, ERRNO:-16
gx801: probe of 2-0055 failed with error -16
omap_rtc omap_rtc: setting system clock to 2012-09-12 18:00:04 UTC (1347472804)
yaffs: dev is 32505864 name is "mtdblock8" rw
yaffs: yaffs: Attempting MTD mount of 31.8,"mtdblock8"
yaffs: yaffs_read_super: is_checkpointed 0
VFS: Mounted root (yaffs2 filesystem) on device 31:8.
Freeing init memory: 364K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot open '/initlogo.rle'
Disabling lock debugging due to kernel taint
rtusb init rt2870 --->
usbcore: registered new interface driver rt2870
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
android_usb: already disabled
adb_bind_config
adb_open
warning: `rild' uses 32-bit capabilities (legacy support in use)
root@android:/ # request_suspend_state: wakeup (3->0) at 16069383837 (2012-09-12 18:00:17.727128877 UTC)
init: untracked pid 85 exited
init: untracked pid 90 exited
request_suspend_state: wakeup (0->0) at 17532488671 (2012-09-12 18:00:19.190233961 UTC)
init: untracked pid 151 exited
init: untracked pid 152 exited
request_suspend_state: wakeup (0->0) at 22654777296 (2012-09-12 18:00:24.312521878 UTC)
init: untracked pid 179 exited
init: untracked pid 180 exited
request_suspend_state: wakeup (0->0) at 27766459047 (2012-09-12 18:00:29.424203920 UTC)
init: untracked pid 208 exited
init: untracked pid 209 exited
request_suspend_state: wakeup (0->0) at 32895057089 (2012-09-12 18:00:34.552802171 UTC)
init: untracked pid 236 exited
init: untracked pid 237 exited
request_suspend_state: wakeup (0->0) at 38019142548 (2012-09-12 18:00:39.676887088 UTC)
init: untracked pid 264 exited
init: untracked pid 265 exited
request_suspend_state: wakeup (0->0) at 42151571047 (2012-09-12 18:00:43.809316504 UTC)
init: untracked pid 292 exited
init: untracked pid 293 exited
到这里无限循环之后就手动关断板子电源了。请问怎样处理?谢谢
gjh123 发表于 2013-10-16 10:03:48 | 显示全部楼层
请帮忙啊小伙伴们
gjh123 发表于 2013-10-25 14:56:51 | 显示全部楼层
mmm命令之后生成的jar包里怎么没有dex文件呢?
gjh123 发表于 2013-11-5 23:16:55 | 显示全部楼层
楼主能不能上传分享一下这个app,不胜感激啊:handshake 一直在鼓捣这个,还是没有成功呢。
andrewgreat 发表于 2016-1-16 12:11:23 | 显示全部楼层
我不能下载啊。。。。。
liu402068552 发表于 2016-1-25 15:32:19 | 显示全部楼层
感谢楼主,下载学习了,我主要是不懂socket can的编程
andersr 发表于 2017-7-4 04:51:56 | 显示全部楼层
感谢楼主分享,要好好研究研究
您需要登录后才可以回帖 登录 | 注册

本版积分规则

关闭

i.MX8系列ARM cortex A53 M4 工控板上一条 /1 下一条

Archiver|手机版|小黑屋|天嵌 嵌入式开发社区 ( 粤ICP备11094220号 )

GMT+8, 2024-3-29 21:52 , Processed in 1.078125 second(s), 22 queries .

Powered by Discuz! X3.4

Copyright © 2001-2020, Tencent Cloud.

快速回复 返回顶部 返回列表