Encode Demo hangs up??

Are you getting any error messages on the console either when you run the demo or when the board is booting? For a failure like this I would expect some sort of console feedback as to where it is going wrong.

Another thought would be if this is a filesystem level issue, are you able to create a new file in your filesystem?

Other things to consider:

   - space left on file system

   - since encodedecode does not store anything but still fails, myabe it is a compatibility problem with the encode codec.  What DVSDK version are you using?

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

## Booting image at 80700000 ...

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

OK

 

Starting kernel ...

 

Linux version 2.6.10_mvl401 (a0270758@gtmatrix) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 EDT 2007

CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)

CPU0: D VIVT write-back cache

CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: DaVinci DM355 EVM

Memory policy: ECC disabled, Data cache writeback

DM0350

Built 1 zonelists

Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.9:/home/koa/workdir/filesys,nolock video=dm64xxfb:output=pal mem=116M

PID hash table entries: 512 (order: 9, 8192 bytes)

Console: colour dummy device 80x30

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 116MB = 116MB total

Memory: 114176KB available (2762K code, 585K data, 164K init)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

CPU: Testing write buffer coherency: ok

spawn_desched_task(00000000)

desched cpu_callback 3/00000000

ksoftirqd started up.

desched cpu_callback 2/00000000

desched thread 0 started up.

NET: Registered protocol family 16

Registering platform device 'serial8250.0'. Parent at platform

Registering platform device 'nand_davinci.0'. Parent at platform

Registering platform device 'dm9000.0'. Parent at platform

Registering platform device 'mmc.0'. Parent at platform

Registering platform device 'mmc.1'. Parent at platform

DaVinci I2C DEBUG: 15:42:09 Oct 17 2007

Registering platform device 'i2c'. Parent at platform

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]

Registering platform device 'musb_hdrc'. Parent at platform

musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12

musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD ret 0

Registering platform device 'dm_spi.0'. Parent at platform

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0

NetWinder Floating Point Emulator V0.97 (double precision)

JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.

yaffs Oct 17 2007 15:41:45 Installing.

Initializing Cryptographic API

Registering platform device 'dm355fb.0'. Parent at platform

Console: switching to colour frame buffer device 90x36

watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec

Registering platform device 'davinci_pwm0.0'. Parent at platform

Registering platform device 'davinci_pwm1.1'. Parent at platform

Registering platform device 'davinci_pwm2.2'. Parent at platform

Registering platform device 'davinci_pwm3.3'. Parent at platform

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled

Registering platform device 'serial8250'. Parent at platform

ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A

ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A

ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A

io scheduler noop registered

io scheduler anticipatory registered

RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize

loop: loaded (max 8 devices)

dm9000 Ethernet Driver

eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c2:5b

i2c /dev entries driver

Linux video capture interface: v1.00

Registering platform device 'vpfe.1'. Parent at platform

vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded

ipipe major#: 253, minor# 0

Registering platform device 'dm355_ipipe.2'. Parent at platform

ipipe driver registered

af major#: 252, minor# 0

Registering platform device 'dm355_af.2'. Parent at platform

aew major#: 251, minor# 0

Registering platform device 'dm355_aew.2'. Parent at platform

elevator: using anticipatory as default io scheduler

at25xxA_spi_eeprom init

nand_davinci nand_davinci.0: Using 4-bit hardware ECC

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

2 NAND chips detected

nand_bbt: ECC error while reading bad block table

nand_bbt: ECC error while reading bad block table

Creating 5 MTD partitions on "nand_davinci.0":

0x00000000-0x003c0000 : "bootloader"

0x003c0000-0x00400000 : "params"

0x00400000-0x00800000 : "kernel"

0x00800000-0x20800000 : "filesystem1"

0x20800000-0x80000000 : "filesystem2"

nand_davinci nand_davinci.0: hardware revision: 2.3

scan_boardinfo:<NULL>:-1067850772

modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824

drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded

dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)

Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage

USB Mass Storage support registered.

usbcore: registered new driver usbhid

drivers/usb/input/hid-core.c: v2.0:USB HID core driver

mice: PS/2 mouse device common for all mice

mmc mmc.0: Supporting 4-bit mode

mmc mmc.0: Using DMA mode

mmc mmc.1: Supporting 4-bit mode

mmc mmc.1: Using DMA mode

Registering platform device 'davinci-audio.0'. Parent at platform

NET: Registered protocol family 2

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 8192 bind 16384)

Initializing XFRM netlink socket

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

eth0: link down

Sending DHCP requests ., OK

IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.1.10

IP-Config: Complete:

device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=255.255.255.255,

host=192.168.1.10, domain=lan, nis-domain=(none),

bootserver=0.0.0.0, rootserver=192.168.1.9, rootpath=

Looking up port of RPC 100003/2 on 192.168.1.9

Looking up port of RPC 100005/1 on 192.168.1.9

VFS: Mounted root (nfs filesystem).

Freeing init memory: 164K

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

INIT: version 2.85 booting

Mounting a tmpfs over /dev...done.

Creating initial device nodes...done.

Activating swap...done.

Remounting root filesystem...done.

Calculating module dependencies

WARNING: Couldn't open directory /lib/modules/2.6.10_mvl401: No such file or directory

FATAL: Could not open /lib/modules/2.6.10_mvl401/modules.dep.temp for writing: No such file or directory

Loading modules:

Checking all file systems: fsck

fsck 1.35 (28-Feb-2004)

Mounting local filesystems: mount nothing was mounted

Cleaning: /tmp /var/lock /var/run done.

Setting up networking (ifupdown) ..

Cleaning: /etc/network/run/ifstate done.

Starting network interfaces: done.

Starting hotplug subsystem:

pci

pci [success]

usb

usb [success]

isapnp

isapnp [success]

ide

ide [success]

input

input [success]

scsi

scsi [success]

done.

Starting portmap daemon: portmap.

done.

Setting pseudo-terminal access permissions...done.

Updating /etc/motd...done.

INIT: Entering runlevel: 3

Starting NFS common utilities: statd lockd.

Starting internet superserver: inetd.

Starting MontaVista target tools daemon: mvltdmvltd version 2.1 MontaVista Software,Inc.

mvltd[1059]: can't send broadcast message: Network is unreachable

mvltd[1059]: can't send broadcast message: Network is unreachable

mvltd[1060]: started on port 34577

.

MontaVista(R) Linux(R) Professional Edition 4.0.1 (0600980)

 

192.168.1.10 login:

This is the Log File from Booting, during Encode Demo there is no error at the console.

Creating a new file is possible, if "mkdir foo" is ok.. i created this directory at the nfs over the console of the board.

Juan Gonzales said:

Other things to consider:

   - space left on file system

   - since encodedecode does not store anything but still fails, myabe it is a compatibility problem with the encode codec.  What DVSDK version are you using?

Space is left i think 13GB should be enough.

the DVSDK Version is... 1_30_00_23

I just tried this using the pre-built binaries (uImage and u-boot) from DVSDK 1_30_00_40 (what I had readily available); I was able to run both encodedecode and encode (per instructions above) without any issues (Log below)

root@156.117.95.19:/opt/dvsdk/dm355# ./encode -v video1.mpeg4 -t 20
Encode demo started.
Capturing 720x480 video (cropped to 720x480)
root@156.117.95.19:/opt/dvsdk/dm355# ls -al
total 8608
drwxr-xr-x  5 root root    4096 Sep 23  2008 .
drwxr-xr-x  3 root root    4096 Jun 22  2008 ..
-rw-rw-rw-  1 root root   17988 Jun 22  2008 cmemk.ko
drwxr-xr-x  6 root root    4096 Jun 22  2008 data
-rwxr-xr-x  1 root root  567502 Jun 22  2008 decode
-r--r--r--  1 root root    4710 Jun 22  2008 decode.txt
-rw-rw-rw-  1 root root    7068 Jun 22  2008 dm350mmap.ko
-rwxr-xr-x  1 root root     381 Mar 20  2008 dvevmdemo
-rwxr-xr-x  1 root root  569594 Jun 22  2008 encode
-r--r--r--  1 root root    5318 Jun 22  2008 encode.txt
-rwxr-xr-x  1 root root  561215 Jun 22  2008 encodedecode
-r--r--r--  1 root root    4905 Jun 22  2008 encodedecode.txt
-rwxr-xr-x  1 root root   58931 Jun 22  2008 interface
-rwxrwxrwx  1 root root     284 Jun 22  2008 loadmodules.sh
-rwxrwxrwx  1 root root    7680 Jun 22  2008 mapdmaq
drwxr-xr-x  2 root root    4096 Jun 22  2008 thirdpartydemos
-rw-r--r--  1 root root 6850869 Sep 23  2008 video1.mpeg4
drwxrwxr-x  3 root root    4096 Apr 30  2008 web
root@156.117.95.19:/opt/dvsdk/dm355#

Are you using pre-built binaries?  If so, I would suggest you try DVSDK 1.30.00.40 just to be sure; if you still have problems, this may point to an issue on the hardware itself, in which case you may need to exchange it.

yes i'm using these pre built ones at the demo folder. But it didnt work...

i copied them manually to the workdir, cause i get an error if i want to rebuild the demo folder, you can look at this error in my other thread...

https://community.ti.com/forums/p/1005/3229.aspx#3229

Maybe its the same problem???

I will install dvsdk 1_30_00_23 just to make sure there are no issues (although I am pretty sure I have installed it in the past).  What Linux host OS are you using?  FYI, I am using RHEL4

I am using Fedore Core 9 some sort of free RedHat. Now i am waiting for dvsdk 1_30_00_40 since i've got my mail from registration.

I have another Question: is there anywhere a tutorial or some demo source code for using the LEDs and push Buttons at the Board? Cause i need something to do while i am waiting :)

Alex,

1) I could not find DVSDK 1.30.00.23 in the software update site as I had expected; I am trying to get it thru internal channels but this may take some time. 

2) You mentioned you got your e-mail from registration; I believe this e-mail has instructions on how to set-up your PIN so you can get access to our software update site.  Have you tried this, it may be faster if you just upgrade to the latest version so that we are both using the same release.

3) With regards to using LEDs; if you refer to the technical reference manual on Spectrum digital site ( http://c6000.spectrumdigital.com/evmdm355/revd/files/EVMDM355_TechRef_RevD.pdf ), you will find information with regards to which LEDs are under user control as well as I2C address of MSP430 that controls those LEDs.  You can use this information to write a simple user space application that writes to MSP430 to toggle LEDs on and off (I did one for DM644X a long time ago; unfortunately, I have deleted since).

Hi i solved this problem or maybe i think it.

1) I think i had a bad video source for capturing, now i am using a cam at s-video port and everything runs fine :)

2) i didnt get the email with the pin yet, i am still waiting!

3) i will have a look next week on it.

Best regards Alex!

Alex,

This is good news.  With regards to your registration, if I can have your e-mail and EVM S/N used during registration, I can look into it.  However, I would suggest you send me this sensitive information via private message as you do not want to post this for everyone to see.

If you click on my name, you should see options for sending me private e-mail message.

hi,

I have the same problem with yours. Must the camera be the S-video port.  The  camera that I used is the composite camera.

The dm355 board support the interface of the composite video input.

If I need a transform which transform the S-video into composite form.

Best regars!

Allen Wang

Is the camera you tried connecting (to the composite port) color or black and white?  I had trouble where the EVM wouldn't capture from a black and white camera.  It worked fine once the camera was swapped out for a color one.

-c.

the camera that i used is color. when I run encode demo it hangs up, do you have the same problem and how did you resolve it ?

Allen Wang

how are you running the demo?  if you look at the encode.txt file which accompanies the demo, it will give you a good idea of what the defaults are.

For example, by default the demo assumes NTSC and composite input, if you want to input s-video, then you need to specify '-x' option.  Let us know if this helps.

thanks, I have read the encode.txt. The problem is the software that I modify has something wrong. When I return to the original version, it works well .

Allen Wang 

Maybe if you can give us on overview of the general chages you made, we can offer some key areas you need to double check to ensure all necessary changes were done.  You can always start from the working version and change small pieces at a time until you find what broke it.