标签归档:OMAP3530开发板

TI OMAP3530 数字媒体处理器

OMAP3530主要面向多媒体,此MCU片上集成了ARM9 Cortex-A8 600MHz内核、达芬奇C64X DSP 430MHz核、SX 2D/3D加速器,算是相当强悍的了,下面是一段来自TI官方的超声波扫面转换演示视频:

[flv]http://www.roboby.com/wp-content/uploads/2011/03/超声波扫描转换演示-OMAP3530-EVM-Basic-Small.flv[/flv]

TI还为此开发了DVSDK数字视频开发库,居然有500多兆,带源码,这对于那些基于此处理器开发DSP图像处理的人来说是相当宝贵的资源了!

从这里可以了解相关信息

http://www.ti.com

E文不好的还是从这里看中文的吧:

http://www.ti.com.cn

DevKit8000启动日志

周一到周五要上班,小孩子就我妈妈一个人照顾。老人家老了,不方便出去,所以小孩子很少能晒到太阳,哎,头疼的问题……

所以啊,周末得花多半时间陪陪孩子,带孩子出去走走,个人时间真是少啊……

今晚把玩了一下DevKit8000开发板,Linux的启动日志如下:

Texas Instruments X-Loader 1.41Starting OS Bootloader…

U-Boot 1.3.3-svn (Feb  6 2010 – 16:29:12)
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz

OMAP3 DevKit8000 Board + LPDDR/NAND

DRAM:  256 MB

NAND:  256 MiB

Using default environment
In:    serial

Out:   serial

Err:   serial

Hit any key to stop autoboot:  0
NAND read: device 0 offset 0x280000, size 0x240000 

2359296 bytes read: OK##

Booting kernel from Legacy Image at 80300000 …  

 Image Name:   Linux-2.6.28-rc9-omap1  

 Image Type:   ARM Linux Kernel Image (uncompressed)  

Data Size:    2165084

Texas Instruments X-Loader 1.41
Starting OS Bootloader…
U-Boot 1.3.3-svn (Feb  6 2010 – 16:29:12)

OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 DevKit8000 Board + LPDDR/NAND
DRAM:  256 MB
NAND:  256 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x280000, size 0x240000
 2359296 bytes read: OK
## Booting kernel from Legacy Image at 80300000 …
   Image Name:   Linux-2.6.28-rc9-omap1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2165084 Bytes =  2.1 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum … OK
   Loading Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux…………………………………………………….
…………………………………………………………………….
done, booting the kernel.
Linux version 2.6.28-rc9-omap1 (cyz@TIOP) (gcc version 4.2.1 (CodeSourcery Sourc
ery G++ Lite 2007q3-51)) #1 Wed Feb 24 15:49:35 CST 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 DevKit8000 Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 Unknown revision

SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstyp
e=ubifs video=omapfb:mode:4.3inch_LCD
Clocking rate (Crystal/DPLL/ARM core): 26.0/266/500 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 1024 (order: 10, 4096 bytes)
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80×30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255104KB available (3980K code, 355K data, 156K init)
Calibrating delay loop… 507.32 BogoMIPS (lpj=1982464)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
omap3evmdc: Driver registration complete
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
msgmni has been set to 498
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
dm9000 Ethernet Driver, V1.31
eth0: dm9000a at d08ae000,d08b2400 IRQ 185 MAC: 00:11:22:33:44:55 (chip)
Linux video capture interface: v2.00
tvp514x 2-005d: Registered to v4l2 master omap34xxcam!!
i2c /dev entries driver
Driver ‘sd’ needs updating – please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi
t)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on “omap2-nand”:
0x00000000-0x00080000 : “X-Loader”
0x00080000-0x00260000 : “U-Boot”
0x00260000-0x00280000 : “U-Boot Env”
0x00280000-0x00680000 : “Kernel”
0x00680000-0x10000000 : “File System”
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd4 to ubi0
UBI: MTD device name:            “File System”
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1996
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1996
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 2/0
usbmon: debugfs is not available
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
UBI: background thread “ubi_bgt0d” started, PID 396
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 6a:01:8d:f5:2a:30
usb0: HOST MAC 12:a5:ad:b2:c8:67
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
input: omap_twl4030keypad as /class/input/input0
input: gpio-keys as /class/input/input1
ads7846 spi2.0: touchscreen, irq 187
input: ADS784x Touchscreen as /class/input/input2
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
twl4030_rtc twl4030_rtc: Power up reset detected.
twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
Registered led device: led1
Registered led device: led2
Registered led device: ledB
Registered led device: led3
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
ASoC version 0.13.2
OMAP3 omap3devkit8000 SoC init
TWL4030 Audio Codec init
asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok
ALSA device list:
  #0: omap3devkit8000 (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
omapfb: using mode 4.3inch_LCD
Console: switching to colour frame buffer device 60×34
clock: clksel_round_rate_div: dpll4_m4_ck target_rate 28800000
clock: new_div = 15, new_rate = 28800000
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: chip id mismatch msb:0x87 lsb:0x87
tvp514x 2-005d: Unable to detect decoder
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: chip id mismatch msb:0x87 lsb:0x87
tvp514x 2-005d: Unable to detect decoder
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: chip id mismatch msb:0x87 lsb:0x87
tvp514x 2-005d: Unable to detect decoder
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: Write: retry … 0
tvp514x 2-005d: Write: retry … 1
tvp514x 2-005d: Write: retry … 2
tvp514x 2-005d: Write: retry … 3
tvp514x 2-005d: Write: retry … 4
tvp514x 2-005d: Write: retry … 5
tvp514x 2-005d: chip id mismatch msb:0x87 lsb:0x87
tvp514x 2-005d: Unable to detect decoder
Display already enabled
Display already enabled
Buffer Size = 3686400
omap_vout: registered and initialized                   video device 0 [v4l2]
Buffer Size = 3686400
omap_vout: registered and initialized                   video device 1 [v4l2]
display->updated
twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684
801)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name “rootfs”
UBIFS: file system size:   103348224 bytes (100926 KiB, 98 MiB, 801 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       4 (latest is 4)
UBIFS: default compressor: LZO
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem).
Freeing init memory: 156K
INIT: version 2.86 booting
eth0: link down
Starting udevuncorrectable error : <3>end_request: I/O error, dev mtdblock0, sec
tor 0
Buffer I/O error on device mtdblock0, logical block 0
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 8
Buffer I/O error on device mtdblock0, logical block 1
uncorrectable error : <3>uncorrectable error : <3>end_request: I/O error, dev mt
dblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
tar: removing leading ‘/’ from member names

Remounting root file system…
root: mount: mounting rootfs on / failed: No such file or directory
mknod: /dev/initctl: File exists
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces… udhcpc (v1.11.3) started
Sending discover…
Sending select for 192.168.0.103…
Lease of 192.168.0.103 obtained, lease time 604800
adding dns 202.112.176.2
done.
/sbin/ldconfig: /lib/libts-0.0.so.0 is not a symbolic link

Tue Jan 27 09:49:00 UTC 2009
INIT: Entering runlevel: 5
Starting syslogd/klogd: done

.——-.
|       |                  .-.
|   |   |—–.—–.—–.| |   .—-..—–.—–.
|       |     | __  |  —‘| ‘–.|  .-‘|     |     |
|   |   |  |  |     |—  ||  –‘|  |  |  ‘  | | | |
‘—‘—‘–‘–‘–.  |—–”—-”–‘  ‘—–‘-‘-‘-‘
                -‘  |
                ‘—‘

The Angstrom Distribution DevKit8000 ttyS2

Angstrom 2008.1-test-20090127 DevKit8000 ttyS2

DevKit8000 login: root
root@DevKit8000:~#
root@DevKit8000:~#
root@DevKit8000:~#
root@DevKit8000:~# shutdown now

Broadcast message from root (ttyS2) (Tue Jan 27 11:36:31 2009):

The system is going down to maintenance mode NOW!
INIT: Switching to runlevel: 1
INIT: Sending processes the TERM signal
INIT: Stopping syslogd/klogd: stopped syslogd (pid 1376)
stopped klogd (pid 1378)
done
Deconfiguring network interfaces… done.
INIT: no more processes left in this runlevel

对配置有些疑问,需要核实…

花了1680RMB拿下DevKit8000

今天终于拿到TI OMAP3530的开发板了,天漠的DevKit8000,花了1680人民币。

下一步,先熟悉熟悉Linux定制方面的知识。有了板子,也终于可以边看边实践了!

然后嘛,想做的东西就太多了,什么视觉系统啊、行走机构啊、蓝牙通讯啦……,每项都是重大课题,里面一点点东西都是好多公司花好多money在搞的东西,个人搞这个,有时候真觉得不现实。

但是,人不都得有点追求是不是?有追求,还得有点实现追求的实际行动是不是?搞就搞了,想这么多干嘛   :)~~~~~~~~~

 

 

最后决定购买DevKit8000及全部配件

最后决定购买DevKit8000评估套件完全配置,1680RMB,它具有强大的图形加速功能,如果能把OpenCV移植上去,那就太完美了!

http://www.broadon.cn/item.htm?id=4064505743

升级版套件:256MB SDRAM + 256MB NAND FLASH

– 基于OMAP3530处理器,板载256MByte DDR SDRAM及256MByte NAND Flash
– 支持DVI-D/S-Video/TFT-LCD三种显示输出,可输出高清信号
– 外扩USB OTG,串口,网口,摄像头,音频,SD/MMC,键盘等接口
– 支持WinCE 6.0及Linux2.6.28系统,完全兼容beagleboard

硬件特性

CPU单元:

OMAP3530应用处理器(Pin to Pin兼容OMAP3503,OMAP3515,OMAP3525处理器)
600-MHz ARM Cortex-A8 Core
430MHz TMS320C64x+ DSP Core
256MByte DDR SDRAM,32bit
256MByte NAND Flash
6层板设计
通讯接口:

1个S-VIDEO接口
1个音频输入接口
1个双声道音频输出接口
1个10/100M以太网(芯片:DM9000,RJ45接口)
1个高速USB2.0 OTG接口(芯片:TPS65930),速度达480Mbps
2个串口(1个3线RS232电平串口,1个5线TTL电平串口)
1个SD/MMC接口
1个6*6键盘接口
1个14针标准JTAG接口
1个CAMERA接口(可外接CCD和CMOS的摄像头)
4个按键(1个启动引导按键,1个复位按键及2个用户按键)
扩展接口(包含McSPI,McBSP,I2C,HDQ及SD/MMC接口)
显示单元:

1个HDMI接口(芯片:TFP410),可输出分辨率1280×720,码率30fps的DVI-D高清信号
24bit真彩色LCD接口(含4线触摸屏接口,分辨率可支持2048*2048)
电气参数:

工作温度:-40 ~ 85℃(芯片支持)
环境湿度:20% ~ 90% ,非冷凝
机械尺寸:110 mm * 95 mm
电气指标:+5V电源供电,电流150mA

订购信息

DevKit8000评估套件完全配置装箱清单:
一个DevKit8000单板  
一个4.3寸触摸屏
一个512MB SD卡
一条交叉网线
一条Mini USB A线转USB A型母头
一条Mini USB B线转USB A型公头
一个USB HUB(带电源)
一个HMDI转DVI-D转接线
一条S-Video线
一个5V 2A电源
一支触摸笔
一张光盘(使用文档、原理图、源代码及工具)

产品自需方购买日起质保半年,核心元器件除外,液晶屏不参与质保。长期提供免费的电话和Email技术支持。

DevKit8000开发板全部配件(12件)

OMAP3530 DSP Howto ( Really works by DSPLINK)

————–我转载它,主要是为了自己学习

2009/11/03 17:33

搞了一段很長的時間終於把DSP功能弄起來了,該是回頭紀錄一下”眉角”了.

1.Before touch anything

目前有兩種方式可以控制DSP,一個是

TI DVSDK

提供的DSPLINK,另一個則是DSPBRIDGE.

以我從google搜尋之後的了解DSPBRIDGE目前是沒有繼續maintain.

DSPLINK是

TI

比較建議的方式.

所搭配的media library為

DSPLINK + gstreamer

DSPBRIDGE + openmax + gstreamer
http://felipec.wordpress.com/2009/10/13/new-project-gst-dsp-with-beagleboard-demo-image/
http://felipec.wordpress.com/2008/12/12/gst-openmax-demo-on-the-beagleboard/

這邊我選擇DSPLINK控制DSP

2.Software

dvsdk_3_00_02_44

gst-

ti

-plugin-full-1.00.02

gst-omapfb

Build and install to target root file system (過程就省略了)

可參考以下作法
http://ossie.wireless.vt.edu/trac/wiki/BeagleBoard_CodecEngine

安裝目錄
DVSDK

: /opt/

dvsdk

gstreamer : /opt

3.Setup

DSPLINK 透過share memory的方式跟DSP交換資料所以有另一個driver叫cmemk.ko負責建立memory pool. 但這塊memory必須脫離kernel的掌控因此必須要空出一塊memory讓cmemk.ko使用.至於大小要看實際memory size跟DSP所需要的size來決定.

http://pixhawk.ethz.ch/wiki/tutorials/omap/dsplink/memorymap

依照以上說明修改以下檔案

dsplink_1_61_03/packages/dsplink/config/all/CFG_OMAP3530_SHMEM.c

dsplink_1_61_03/packages/dsplink/dsp/inc/DspBios/5.XX/

OMAP3530

/dsplink-

omap3530

-base.tci

dsplink_1_61_03/packages/dsplink/config/all/CFG_OMAP3530_SHMEM.c

我的target board有256MB DDR,因此記憶體配置如下

# 0x40200000    60 KB   CMEM (internal memory, see comment below)

# 0x80000000    200 MB   Linux

# 0x8C900000    16 MB   CMEM (external memory)

# 0x8D900000     2 MB   DSPLINK (MEM)

# 0x8DB00000     unused

kernel boot command 加上 mem=200M

For kernel 2.6.27

optargs=init=/init omapfb.video_mode=1280x1024MR-16@60 vram=12M omapfb.vram=4M,4M,4M omapfb.debug=1 omap-dss.def_disp=lcd omap-dss.debug=1 mem=200M

For kernel 2.6.29

setenv optargs ‘init=/init omapdss.def_disp=dvi omapfb.mode=dvi:1280x1024MR-16@60 vram=12M omapfb.vram=0:4M,1:4M,2:4M mem=200M’

memory pool配置如下

insmod cmemk.ko phys_start=0x8C900000 phys_end=0x8D900000 pools=20×4096,10×131072,2×1048576,1×5250000,4×829440,2×691200

gstreamer需要設定target上的環境變數好讓系統找的到執行檔及plug-in

export PATH=$PATH:/opt/gstreamer/bin

export GST_PLUGIN_PATH=/opt/gstreamer/lib/gstreamer-0.10

export LD_LIBRARY_PATH=/opt/gstreamer/lib

3.Get DSP work

載入drivers

#cd /opt/

dvsdk

#./loadmodules.sh

CMEMK module: built on Oct 30 2009 at 20:23:52

  Reference Linux version 2.6.28

  File /home/gigijoe/

OMAP3530

/dvsdk_3_00_02_44/linuxutils_2_24_02/packages/

ti

/sdo/linuxutils/cmem/src/module/cmemk.c

ioremap_nocache(0x8c900000, 16777216)=0xcf000000

allocated heap buffer 0xcf000000 of size 0x32c000

cmem initialized 6 pools between 0x8c900000 and 0x8d900000

DSPLINK Module (1.61.03) created on Date: Oct 30 2009 Time: 20:20:31

# lsmod

lpm_omap3530 8276 0 – Live 0xbf02c000

dsplinkk 114052 1 lpm_omap3530, Live 0xbf00b000

cmemk 24428 0 – Live 0xbf000000

測試omapfb, 應該會在畫面上看到彩色條紋.

gst-launch videotestsrc num-buffers=1000 ! omapfbsink

播放

TI

h.264 raw data sample

gst-launch –gst-debug-level=1 filesrc location=”/media/dcim/100andro/ntsc.264″ ! typefind ! TIViddec2 ! omapfbsink

Play avi file

gst-launch –gst-debug-no-color –gst-debug=

TI

*:2 filesrc location=/media/dcim/100andro/aris.mpeg ! typefind ! qtdemux name=demux demux.audio_00 ! queue max-size-buffers=8000 max-size-time=0 max-size-bytes=0 ! typefind ! TIAuddec1 ! audioconvert ! osssink demux.video_00 ! typefind ! TIViddec2 ! omapfbsink

Play mpeg4 file

gst-launch –gst-debug-no-color –gst-debug=

TI

*:2 filesrc location=/media/dcim/100andro/KenBlock-TopGear.mp4 ! typefind ! qtdemux name=demux demux.audio_00 ! queue max-size-buffers=8000 max-size-time=0 max-size-bytes=0 ! typefind ! TIAuddec1 ! audioconvert ! osssink demux.video_00 ! typefind ! TIViddec2 ! omapfbsink

Play H.264 mpeg4 file without mp3 audio

gst-launch filesrc location=/media/dcim/100andro/sany0014.mp4  ! typefind ! qtdemux name=demux  demux.video_00 ! typefind ! TIViddec2 ! omapfbsink

4.Debug

http://tiexpressdsp.com/wiki/index.php?title=Debugging_DSPLink_using_SET_FAILURE_REASON_prints

http://tiexpressdsp.com/index.php/Enabling_trace_in_DSPLink

一開始有一段時間kernel-2.6.29 DSP_init總是失敗

# ./messagegpp ./message.out 1000

========== Sample Application : Failure [0x8000800b] in [0x401] at line 522

MESSAGE ==========

Entered MESSFailure [0x8000802d] in [0x401] at line 544

AGE_Create ()

Failure [0x8000802d] in [0x401] at line 544

Failure [0x8000802d] in [0x401] at line 544

ISR_Install:445

request_irq 28

request_irq failed with error: -16

Failure [0x80008008] in [0x502] at line 459

Failure [0x80008008] in [0x80a] at line 824

Failure [0x80008008] in [0x80a] at line 1061

Failure [0x80008008] in [0x801] at line 597

Failure [0x80008008] in [0x701] at line 370

 DSP_init status [0x80008008]

Assertion failed ((isrObj!= NULL) && (ISR_InstalledIsrs [isrObj->dspId][isrObj->irq] == isrObj)). File : /home/gigijoe/

OMAP3530

/dvsdk_3_00_02_44/dsplink_1_61_03/packages/dsplink/gp

p/src/../../gpp/src/osal/Linux/2.6.18/isr.c Line : 507

Failure [0x80008000] in [0x502] at line 515

Failure [0x80008008] in [0x300] at line 476

Failure [0x80008008] in [0x300] at line 563

PROC_attach () failed. Status = [0x80008008]

PROC_setup () failed. Status = [0x80008008]

Leaving MESSAGE_Create ()

Entered MESSAGE_Delete ()

Assertion failed (IS_VALID_MSGQ (msgqQueue)). File : msgq.c Line : 484

MSGQ_release () failed. Status = [0x8000800b]

Assertion failed (IS_VALID_MSGQ (msgqQueue)). File : msgq.c Line : 335

Leaving MESSAGE_Delete ()

====================================================

Trace DSPLINK driver發現request_irq 28 居然失敗了.很明顯IRQ被佔據了.

看看到底是誰

cat /proc/interrupts

           CPU0

 11:          0        INTC  prcm

 12:          1        INTC  DMA

 18:          0        INTC  sr1

 19:          0        INTC  sr2

 24:          0        INTC  omap-iommu.1, Omap 3 Camera ISP

 25:          1        INTC  OMAP DSS

28:          0        INTC  omap-iommu.2

 56:        347        INTC  i2c_omap

 61:          0        INTC  i2c_omap

 72:          1        INTC  serial idle

 73:          1        INTC  serial idle

 74:         94        INTC  serial idle, serial

 77:          0        INTC  ehci_hcd:usb2

 83:          0        INTC  mmc0

 86:         14        INTC  mmc1

 92:          0        INTC  musb_hdrc

 93:          0        INTC  musb_hdrc

 95:        641        INTC  gp timer

160:          0        GPIO  mmc1

167:          0        GPIO  user

181:          8        GPIO  eth0

378:          0     twl4030  twl4030_usb

379:          0     twl4030  rtc0

384:          0     twl4030  mmc0

原來是iommu啊,OK,調整一下kernel config

Disable

Device Drivers->Multimedia Devices->Video Capture Adapters->OMAP 3 Camera Support

System Type->

TI

OMAP Implemenation->IOMMU Support

這樣就OK囉

其實還有一些疑慮沒有解決.

IOMMU 以 Shared IRQ 方式 request_irq而DSPLINK Driver request_irq 並不是.

因此造成問題,DSPLINK Driver是否應該以Shared IRQ方式request_irq呢?

看上TI 的 OMAP3530 开发板了

看上这块板子了:EVM3530-B3-1880-LUNC0

理由嘛:

1、CPU是TI的,TI OMAP3530 多核处理器,600MHz 的ARM Cortex-A8内核;430MHz TMS320C64x+ DSP POWERVR SG™2D/3D图形加速处理引擎。如果DSP资料开放,可以考虑移植OpenCV,利用DSP能力实现图像识别

2、一个10M/100M网卡、1个RS232、2个UART、4个USB2.0 Host、1个USB2.0 OTG

3、音频输入输出口、VGA口、视频输入输出口

4、SD卡槽

参数如下:
产品型号 技术参数 价格(RMB)
EVM3530-B3-1880-LUNC0 处理器:TI OMAP3530
内存:256M内存 + 256M Flash,
网络:采用LAN9221,10/100Mbps
USB接口:4个Host + 1个OTG
串口:1个RS232 + 2个串口插针
显示接口:标准DVI
1380

 

问题是1380大洋,还不带显示屏,如果加个4.3寸显示屏380,可就到1760了,nnd,喉贵!

选配表:

 
产品型号 技术参数 价格(RMB)
EVM3530-B3-1880-LUNC0 处理器:TI OMAP3530
内存:256M内存 + 256M Flash,
网络:采用LAN9221,10/100Mbps
USB接口:4个Host + 1个OTG
串口:1个RS232 + 2个串口插针
显示接口:标准DVI
1380
SOM-3530-B2-1880-C 1、处理器:TI OMAP3530
2、内存:256M内存 + 256M Flash
3、电源管理:高性能电源管理模块,支持USB
4、B2B接口:4x 0.5mm 60Pin B2B
600
SBC3530-A2-1880-LUAC0 处理器:TI OMAP3530
内存:256M内存 + 256M Flash,
网络:采用LAN9221,10/100Mbps
USB接口:4个Host + 1个OTG
串口:1个RS232 + 2个串口插针
显示接口:标准VGA
视频输入:四路模拟视频输入 + 1路数字摄像头
1580
DEV3530-128M 处理器:TI OMAP3530 ,内存:128M内存 + 128M Flash ,DVI视频接口:支持多种高分辨率,音频接口:2.1声道,网络:10/100Mbps 采用LAN9221,USB接口:1个OTG,串口:1个RS232 ,SD卡槽:最高支持32G容量 798
支持OMAP3530开发板的4.3寸群创液晶屏模块   380
支持OMAP3530开发板的7寸群创液晶屏模块   480
WIFI   250
 Camera   300
XDS100V2 仿真器   368
omap3530启动SD Card   55
适用于DEV3530系列   40

 

另两款:

DevKit8000评估套件+4.3触摸屏 OMAP3530开发板 256M

这个带了个4.3的屏幕,CPU与上一款一样,区别呢?

地址:http://item.taobao.com/item.htm?id=3781993929

报价¥1690,

256MB DevKit8000评估套件 配4.3寸屏 OMAP3530开发板

更上一款一样啊,报价多了9块钱 :)

地址:http://item.taobao.com/item.htm?id=3920551293

DevKit8000系列的参数及配置如下:

T1系列 主板型号 税前价 税后价 说明
OMAP3530 DevKit8000标准配置 888 1,050 单板+SD+电源+串口线
DevKit8000完全配置1 1,599 1,870 4.3”触摸屏及全部配件
DevKit8000完全配置2 1,799 2,100 7”触摸屏及全部配件
DevKit8000(2G)标准配置 988 1,160 单板+SD+电源+串口线
DevKit8000(2G)完全配置1 1,699 2,000 4.3”触摸屏及全部配件
DevKit8000(2G)完全配置2 1,899 2,220 7”触摸屏及全部配件
Mini8100 540 630 SBC8100核心板
SBC8100单板机 2,800 3,280 配512M SD卡、串口线、网线、5V/2A电源、USB转接线(Mini-B to A)、S-Video线。
SBC8100套件1 3,150 3,690 单板机配4.3寸触摸屏。
SBC8100套件2 3,300 3,860 单板机配7寸触摸屏。
Mini8100(2G) 640 750 SBC8100核心板
SBC8100(2G)单板机 2,900 3,400 配512M SD卡、串口线、网线、5V/2A电源、USB转接线(Mini-B to A)、S-Video线。
SBC8100(2G)套件1 3,250 3,800 单板机配4.3寸触摸屏。
SBC8100(2G)套件2 3,400 3,980 单板机配7寸触摸屏。
VSS3530(1G) 1299 1520 配12V/1.25A电源、串口线、串口转接板

 

配套模块型号 税前价 税后价 说明
CAM8000-A 250 290 模拟摄像头输入模块,配套DevKit8000和SBC8100
CAM8000-U 500 585 USB数字摄像头输入模块,配套DevKit8000和SBC8100
VGA8000-A 250 290 LCD转VGA输出模块,配套DevKit8000和SBC8100
模拟摄像头 250 290 提供配套电源,不带支架和连接线。
WF8000-U 250 290 USB WiFi模块,配套DevKit8000
GPRS8000-S 400 470 串口GPRS模块,配套DevKit8000
GPS8000-S 300 350 串口GPS模块,配套DevKit8000
CDMA8000-U 450 525 USB 3G模块,配套DevKit8000和SBC8100

 

仿真器 TDS560 Plus仿真器 4,800 4,800 适用于TI 公司C2000、C5000、C6000芯片及OMAP、DaVinci、ARM7、ARM9 
XDS100v2 380 445 支持多种处理器:TMS320C28x、TMS320C54x、TMS320C55x、TMS320C64x+、TMS320C674x、ARM 9、 ARM Cortex R4、ARM Cortex A8 

 

DevKit8000评估套件

 

– 基于TI OMAP3530处理器,板载256MByte DDR SDRAM、256MByte NAND Flash
– 支持DVI-D、VGA、TFT-LCD三种显示输出,可输出高清信号
– 支持摄像头输入、USB WiFi、GPS定位、GPRS通讯、CDMA
– 支持XDS100v2仿真器和TDS560 Puls仿真器调试
– 外扩USB OTG,串口,网口,摄像头,音频,SD/MMC,键盘等接口
– 支持WinCE 6.0及Linux2.6.28系统,完全兼容beagleboard
   

    DevKit8000评估主板为开发者使用TI OMAP35x系列处理器提供了完善的软件开发环境,支持linux-2.6.28操作系统及WinCE6.0操作系统,并包含完善的底层驱动程序,方便用户快速评估OMAP35x系列处理器、设计系统驱动及其定制应用软件,并提供有成熟的操作系统Google Android及Angstrom(GPE)的发布版本,方便用户快速体验OMAP35x处理器的强大的数据运算处理能力,也可降低产品开发周期,实现面向消费电子、医疗仪器、多媒体处理、视频监控、工业控制等领域的产品快速上市。
    DevKit8000评估套件是一个功能丰富的开发平台,为嵌入式设计人员提供快捷简单的实践方式来评估OMAP3530处理器。该套件提供了一个完整的实验评估平台,包括一个4.3″LCD屏、SD卡、电源及各种接口转接线(串口转接线,USB OTG转接线,S-Video转接线,HDMI转DVI-D转接线)等。该套件使设计者能够基于DevKit8000的板载系统快速开发出基于OMAP3530芯片的相关产品。

 
硬件特性
CPU单元: 

  • OMAP3530应用处理器(Pin to Pin兼容OMAP3503,OMAP3515,OMAP3525处理器)
  • 600-MHz ARM Cortex-A8 Core
  • 430MHz TMS320C64x+ DSP Core
  • 128MByte DDR SDRAM (可选配256MB DDR SDRAM)
  • 128MByte NAND Flash (可选配256MB NAND Flash)
  • 6层板

通讯接口: 

  • 1个S-VIDEO接口
  • 1个音频输入接口
  • 1个双声道音频输出接口
  • 1个10/100M以太网(芯片:DM9000,RJ45接口)
  • 1个高速USB2.0 OTG接口(芯片:TPS65930),速度达480Mbps
  • 1个高速USB2.0 Host接口
  • 2个串口(1个3线RS232电平串口,1个5线TTL电平串口)
  • 1个SD/MMC接口
  • 1个6*6键盘接口
  • 1个14针标准JTAG接口
  • 1个CAMERA接口(可外接CCD和CMOS的摄像头)
  • 4个按键(1个启动引导按键,1个复位按键及2个用户按键)
  • 扩展接口(包含McSPI,McBSP,I2C,HDQ及SD/MMC接口)

显示单元: 

  • 1个HDMI接口(芯片:TFP410),可输出分辨率1280×720,码率30fps的DVI-D高清信号
  • S-Video视频输出接口
  • 24bit真彩色LCD接口(含4线触摸屏接口,分辨率可支持2048*2048)

电气参数:

  • 工作温度:-40 ~ 85℃(芯片支持)
  • 环境湿度:20% ~ 90% ,非冷凝
  • 机械尺寸:110 mm * 95 mm
  • 电气指标:+5V电源供电,电流150mA
软件特性
Linux系统特性:

  • Linux版本:Linux2.6.28
  • 编译器版本:gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)
  • 启动方式:支持网络、SD卡或NAND Flash中启动引导Linux系统
  • 更新方式:支持网络或SD卡更新映像
  • 文件系统格式:Ramdisk文件系统、UBI文件系统
  • 文件系统支持:ROM/CRAM/EXT2/EXT3/FAT/NFS/JFFS2/UBIFS
  • 设备管理支持:udev设备管理
  • 驱动支持:Serial、RTC、NAND、DVI、LCD、 触摸屏、SD卡、USB、键盘、音频、网络、LED、CAMERA、WiFi、GPS、GPRS、CDMA

 

Wince系统特性:

  • Wince版本:Wince6.0
  • 启动方式:网络、SD卡或NAND Flash中启动引导Wince系统
  • 更新方式:网络或SD卡更新映像
  • 文件系统:支持HIVE注册表支持及ROM文件系统(可读写)
  • 支持微软的远程调试工具对目标板的文件、注册表、进程及线程的管理
  • 系统特性:支持.NET Compact Framework 3.5及KITL内核调试
  • 电源管理:背光管理、电池管理、休眠\唤醒功能
  • 驱动支持:DVI、LCD、SD卡、键盘、音频、网络、NLED、USB、RTC、Watchdog、WiFi、GPS、GPRS、CDMA

Demo演示:

  • Angstrom系统:嵌入式操作系统,支持音频播放,网络浏览,图形编辑及文档处理
  • Android系统:Google开发的基于Linux平台的开源手机操作系统
  • DVSDK软件包:支持MPEG4,MPEG2,H264,mp3,aac音/视频格式DSP硬解码及2D/3D特效

源码及工具:

  • 提供u-boot 1.3.3源码及linux2.6.28内核源码(包含驱动源码)
  • 提供gcc交叉编译工具
  • 提供Wince6.0 BSP源码包(包含驱动源码)及SDK安装包

 

订购信息

产品编号 T6010074
产品名称 DevKit8000评估套件
标准配件  1) Devkit8000评估版 *1
 2) SD卡(512MByte) *1
 3) 交叉串口线 *1
 4) 5V、2A电源适配器 *1
 5) CD光盘(包含用户手册、PDF原理图、外设驱动、源代码等)*1
完全配件  1) 4.3寸 LCD屏,分辨率(480*272)LCD8000-43T  *1
 2) SD卡(512MByte) *1
 3) 交叉串口线 *1
 4) 触摸笔 *1
 5) Mini USB A线转USB A型母头 *1
 6) Mini USB B线转USB A型公头 *1
 7) USB HUB(包括HUN电源、连接线) *1
 8) 网线 *1
 9) HMDI转DVI-D转接线 *1
 10) S-Video线 *1
 11) 5V、2A电源适配器 *1
 12) 光盘(包含用户手册、PDF原理图、外设驱动、源代码等) *1
可选配件  1)10.4寸LCD屏(LCD8000-104T,分辨率为800*600)(30套起订)一般不出货,
 2)7寸LCD屏(LCD8000-70T,分辨率为800*480),
 3)XDS100v2 仿真器(XDS100v2 仿真器
 4)560仿真器(TDS560 Plus仿真器
 5)VGA液晶显示(VGA8000,分辨率 1024*768)
 6)模拟摄像头模块(CAM8000-A,分辨率为720*576(PAL制式))
 7)数字摄像头模块(CAM8000-U
 8)USB WiFi模块(WF8000-U
 9)GPRS无线通讯模块(GPRS8000-S
 10)GPS定位系统模块(GPS8000-S
 11)CDMA8000-U 3G模块(CDMA8000-U
 
备注   CAM8000-A 摄像头模块现只支持Linux