Leopardboard 355 - Recent Threads

Couldnt find valid RAM disk image

jatinpasrija — Thu, 18 Mar 2010 14:35:24 GMT

I am trying to reload the filesystem for leopard board dm355 by following the readme given on the support page

http://designsomething.org/leopardboard/uploads/readme.txt

When I download the uimage and ramdisk.gz using tftp, and then try to boot, it is giving the following error:

RAMDISK: Couldn't find valid RAM disk image starting at 0.
yaffs: dev is 1048576 name is "ram0"
yaffs: Attempting MTD mount on 1.0, "ram0"
yaffs: dev is 1048576 name is "ram0"
yaffs: Attempting MTD mount on 1.0, "ram0"
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

Can anyone please help me on this issue. Thank you.

Ramdisk Source for leopard board dm355

venkatasubramanian — Tue, 19 Jun 2012 06:25:34 GMT

Hi,

Where i can get the Ramdisk Source code of the leopard board dm355.

Which is version of the dvsdk for leopard board dm355.

venkatasubramanian — Mon, 18 Jun 2012 06:17:09 GMT

Hi,

Can any one tell me which is the version of the dvsdk for leopard board dm355 and where i can download the source code of the application belong to the leopard board dm355.

VPFE_CMD_CONFIG_CCDC_RAW error in dm355 while running mt9p031_demo application

venkatasubramanian — Thu, 14 Jun 2012 08:38:33 GMT

Hi, We are using Leopardboard DM355 it is working fine and we can able to see the video through MPEG4 Streaming Demo on Web Browser.But if i try to run the capture application manually inside of /opt/ipnc .The application is MT9P031_demo.It is showing the below error can any one help in this issue. The error is

VPFE_CMD_CONFIG_CCDC_RAW

3) Installing the UBL and the Uboot.

richardg — Sat, 23 Apr 2011 14:31:22 GMT

Having make the RR SDK for leopardboard,

I am now trying to deploy the system to target board.

The FAQ says to make sure uboot is running on /dev/ttyUSB0, I presume this is on the leopardboard.

Presently the leopardboard boots int the IP Cam demo as factory installed.

The minicom repeatedly shows "SetAlarmResetTrigger".

How do I put the leopardboard into the "Uboot" state?

Do I login to the board and run some command like "uboot xxxx" and quit minicom or

do I try the dip switches and reboot with the correct dip switch boot setting?

Appreciate any tips from experts here.

Thanks

Richard

Is 5vdc power supply module center positive with 5.5x2.1mm barrel connector?

mazx — Sat, 10 Oct 2009 18:10:05 GMT

Is 5vdc power supply module center positive with 5.5x2.1mm barrel connector?

I currently have one extra so I was wondering if it's similar to the one DM355 LEOPARD BOARD uses.

Thanks in advance.

Andre

defconfig file for dm355 leopard board

shiny — Mon, 30 Apr 2012 08:29:55 GMT

some can help me to get defconfig file for dm355 leopard board? I want to compile linux 3.3 kernel and load it to leopard board dm355. when i gave the command "make davinci_dm355_leopard_defconfig" its showing some error and not compiling..

Leopard Board 355 and USB (not discovered)

gentlemich — Mon, 03 May 2010 20:55:50 GMT

Hello,

I am trying to connect various USB devices to the USB port of Leopard Board DM355 (thus in Host mode) but I don't get anything:

For example, I've tried to plug in the Keyspan USA-19HS serial to USB adapter and nothing happened. I know that it is being powered successfully (5.4V) by the LB but it is not being discovered... while I'm sure the drivers are available in the kernel. NO message, NO new device is appearing in the Ridge Run SDK Linux I am using. What could go wrong?

When compiling the Kernel, most of the options are checked in Kernel Configuration > Device Drivers > USB support: support for host-side USB, USB verbose debug messages, USB announce new devices, USB device filesystem, USB device class-devices, dyn. USB minor allocation, USB monitor, enable wireless USB extensions and some USB serial converter.

Any idea? Should probably be simple no?

Thanks,

Mike

PS: the J15 jumpers are connected (i.e. USB Host is at 5V) and J14 is between pin2 and pin3 (GND level)

dm365 mt9v113 vga camera support

kailash — Wed, 07 Dec 2011 14:44:08 GMT

hi all

i m trying to modify the rr kernel to support aptina vga sensor i have succeeded to insert it as a module but

i think the problem is coming when try to modify the "board-leopard-dm365.c"

as i m giving value to .platform_data=&mt9v113_pdata

here is the stucture which ive modifiedn in "board-leopard-dm365.c"

static struct i2c_board_info i2c_info[] = {
#if defined(CONFIG_VIDEO_MT9V113) || defined(CONFIG_VIDEO_MT9V113_MODULE)
{

    I2C_BOARD_INFO("mt9v113", MT9V113_I2C_ADDR),
         .platform_data =&mt9v113_pdata,

},

#endif

    {
        I2C_BOARD_INFO("tlv320aic3x", 0x18),
    },
    {
        I2C_BOARD_INFO("ths7303", 0x2c),
    }
};

i ve attached three files to the system

1.mt9v113.c in <kernel>drivers/media/video

2.mt9v113_regs.h in same location

3.mt9v113.h in <kernel>include/media

pls tell me the right step if i m missing something

this is the kernel loading in leopard board

## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   "RR Linux Kernel"
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4445856 Bytes = 4.2 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.32-rc2-ridgerun (dm365@dm365-desktop) (gcc version 4.2.4) #271
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DM365 Leopard
Memory policy: ECC disabled, Data cache writeback
DaVinci dm365_rev1.2 variant 0x8
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 13716
Kernel command line: davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0)
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 54MB = 54MB total
Memory: 50100KB available (3996K code, 387K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 147.86 BogoMIPS (lpj=739328)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 8 gpio irqs
NET: Registered protocol family 16
davinci_serial_init:97: failed to get UART2 clock
bio: create slab <bio-0> at 0
DM365 IPIPE initialized in Single Shot mode
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
vpss vpss: dm365_vpss vpss probed
vpss vpss: dm365_vpss vpss probe success
dm365_afew_hw_init
ch0 default output "COMPOSITE", mode "720P-60"
Invalid id...
Setmode failed, reset to encoder default...
VPBE Encoder Initialized
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
LogicPD encoder initialized
Leopard DVI encoder initialized
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi-dma, host, debug=0
musb_hdrc: USB Host mode controller at fec64000 using DMA, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 97
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
davincifb davincifb.0: dm_osd0_fb: 720x480x16@0,0 with framebuffer size 675KB
davincifb davincifb.0: dm_osd1_fb: 720x480x4@0,0 with framebuffer size 675KB
davinci_interrupt 368: VBUS error workaround (delay coming)
DM365 IPIPEIF probed
imp serializer initialized
davinci_previewer initialized
davinci_resizer initialized
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
console [ttyS0] enabled
brd: module loaded
console [netcon0] enabled
netconsole: network logging started
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
i2c /dev entries driver
Linux video capture interface: v2.00
ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT
Modules linked in:
CPU: 0    Not tainted (2.6.32-rc2-ridgerun #27)
PC is at strcpy+0x10/0x24
LR is at mt9v113_probe+0x90/0x130
pc : [<c017a064>]    lr : [<c0227a78>]    psr: a0000013
sp : c2029e48 ip : c2029e58 fp : c2029e54
r10: 00000000 r9 : 00000001 r8 : c04392c0
r7 : c2023a20 r6 : c043b2ac r5 : c2023a00 r4 : c043b2f8
r3 : c043950c r2 : c043b8c4 r1 : 00000000 r0 : c043b8c4
Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 0005317f Table: 80004000 DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc2028270)
Stack: (0xc2029e48 to 0xc202a000)
9e40:                   c2029e7c c2029e58 c0227a78 c017a064 c2029e7c c2029e68
9e60: c02279e8 c2023a20 c2023a00 c043b268 c2029e9c c2029e80 c02116e8 c02279f8
9e80: c00e9f2c c2023a20 c2023a54 c043b268 c2029ebc c2029ea0 c01be8ac c0211658
9ea0: c2023a20 c2023a54 c043b268 c043b268 c2029edc c2029ec0 c01be9cc c01be80c
9ec0: c2029edc 00000000 c2029ee0 c01be960 c2029f04 c2029ee0 c01bdcb4 c01be970
9ee0: c205d0b8 c2054c30 c043b244 c043b268 c23c4b40 00000000 c2029f14 c2029f08
9f00: c01be708 c01bdc6c c2029f44 c2029f18 c01be280 c01be6f8 c03e06fc c043b244
9f20: c043b244 c043b268 c04392c0 00000000 00000000 c001cac4 c2029f6c c2029f48
9f40: c01bedc4 c01be1ec c043b244 c0025040 c04392c0 00000000 00000000 c001cac4
9f60: c2029f8c c2029f70 c02102bc c01bed24 00000000 c0024f84 c0025040 c04456ac
9f80: c2029f9c c2029f90 c001cadc c0210250 c2029fdc c2029fa0 c002d340 c001cad4
9fa0: 00000000 00000000 000000f5 c041df40 00000000 c0024f84 c0025040 00000000
9fc0: 00000000 00000000 00000000 00000000 c2029ff4 c2029fe0 c0008798 c002d2f0
9fe0: 00000000 00000000 00000000 c2029ff8 c0045738 c000870c e59f004c e1a01005
Backtrace:
[<c017a054>] (strcpy+0x0/0x24) from [<c0227a78>] (mt9v113_probe+0x90/0x130)
[<c02279e8>] (mt9v113_probe+0x0/0x130) from [<c02116e8>] (i2c_device_probe+0xa0)
r7:c043b268 r6:c2023a00 r5:c2023a20 r4:c02279e8
[<c0211648>] (i2c_device_probe+0x0/0xc4) from [<c01be8ac>] (driver_probe_device)
r6:c043b268 r5:c2023a54 r4:c2023a20
[<c01be7fc>] (driver_probe_device+0x0/0x164) from [<c01be9cc>] (__driver_attach)
r7:c043b268 r6:c043b268 r5:c2023a54 r4:c2023a20
[<c01be960>] (__driver_attach+0x0/0x90) from [<c01bdcb4>] (bus_for_each_dev+0x5)
r6:c01be960 r5:c2029ee0 r4:00000000
[<c01bdc5c>] (bus_for_each_dev+0x0/0x8c) from [<c01be708>] (driver_attach+0x20/)
r7:00000000 r6:c23c4b40 r5:c043b268 r4:c043b244
[<c01be6e8>] (driver_attach+0x0/0x28) from [<c01be280>] (bus_add_driver+0xa4/0x)
[<c01be1dc>] (bus_add_driver+0x0/0x228) from [<c01bedc4>] (driver_register+0xb0)
[<c01bed14>] (driver_register+0x0/0x13c) from [<c02102bc>] (i2c_register_driver)
[<c0210240>] (i2c_register_driver+0x0/0xa0) from [<c001cadc>] (mt9v113_init+0x1)
r6:c04456ac r5:c0025040 r4:c0024f84
[<c001cac4>] (mt9v113_init+0x0/0x20) from [<c002d340>] (do_one_initcall+0x60/0x)
[<c002d2e0>] (do_one_initcall+0x0/0x1ac) from [<c0008798>] (kernel_init+0x9c/0x)
[<c00086fc>] (kernel_init+0x0/0x110) from [<c0045738>] (do_exit+0x0/0x654)
r5:00000000 r4:00000000
Code: e1a0c00d e92dd800 e24cb004 e1a02000 (e4d13001)
---[ end trace 2fb026f5e56724ab ]---
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0031730>] (dump_backtrace+0x0/0x110) from [<c0031874>] (dump_stack+0x18/0x1c)
r6:0000000b r5:c0445e24 r4:c041d6f8
[<c003185c>] (dump_stack+0x0/0x1c) from [<c00424f8>] (panic+0x54/0x134)
[<c00424a4>] (panic+0x0/0x134) from [<c004579c>] (do_exit+0x64/0x654)
r3:c041d6f8 r2:c2028000 r1:00000001 r0:c03adbcc
[<c0045738>] (do_exit+0x0/0x654) from [<c00319f4>] (die+0x15c/0x17c)
[<c0031898>] (die+0x0/0x17c) from [<c0033640>] (__do_kernel_fault+0x6c/0x7c)
[<c00335d4>] (__do_kernel_fault+0x0/0x7c) from [<c003381c>] (do_page_fault+0x1c)
r7:00000000 r6:00000000 r5:c2024000 r4:ffffffff
[<c0033650>] (do_page_fault+0x0/0x1e4) from [<c00338d4>] (do_translation_fault+)
[<c00338b8>] (do_translation_fault+0x0/0x84) from [<c002d27c>] (do_DataAbort+0x)
r4:ffffffff
[<c002d23c>] (do_DataAbort+0x0/0xa4) from [<c002da2c>] (__dabt_svc+0x4c/0x60)
Exception stack(0xc2029e00 to 0xc2029e48)
9e00: c043b8c4 00000000 c043b8c4 c043950c c043b2f8 c2023a00 c043b2ac c2023a20
9e20: c04392c0 00000001 00000000 c2029e54 c2029e58 c2029e48 c0227a78 c017a064
9e40: a0000013 ffffffff
r8:c04392c0 r7:c2023a20 r6:c043b2ac r5:c2029e34 r4:ffffffff
[<c017a054>] (strcpy+0x0/0x24) from [<c0227a78>] (mt9v113_probe+0x90/0x130)
[<c02279e8>] (mt9v113_probe+0x0/0x130) from [<c02116e8>] (i2c_device_probe+0xa0)
r7:c043b268 r6:c2023a00 r5:c2023a20 r4:c02279e8
[<c0211648>] (i2c_device_probe+0x0/0xc4) from [<c01be8ac>] (driver_probe_device)
r6:c043b268 r5:c2023a54 r4:c2023a20
[<c01be7fc>] (driver_probe_device+0x0/0x164)
davinci_interrupt 368: VBUS error workaround (delay coming)
from [<c01be9cc>] (__driver_attach+0x6c/0x90)
r7:c043b268 r6:c043b268 r5:c2023a54 r4:c2023a20
[<c01be960>] (__driver_attach+0x0/0x90) from [<c01bdcb4>] (bus_for_each_dev+0x5)
r6:c01be960 r5:c2029ee0 r4:00000000
[<c01bdc5c>] (bus_for_each_dev+0x0/0x8c) from [<c01be708>] (driver_attach+0x20/)
r7:00000000 r6:c23c4b40 r5:c043b268 r4:c043b244
[<c01be6e8>] (driver_attach+0x0/0x28) from [<c01be280>] (bus_add_driver+0xa4/0x)
[<c01be1dc>] (bus_add_driver+0x0/0x228) from [<c01bedc4>] (driver_register+0xb0)
[<c01bed14>] (driver_register+0x0/0x13c) from [<c02102bc>] (i2c_register_driver)
[<c0210240>] (i2c_register_driver+0x0/0xa0) from [<c001cadc>] (mt9v113_init+0x1)
r6:c04456ac r5:c0025040 r4:c0024f84
[<c001cac4>] (mt9v113_init+0x0/0x20) from [<c002d340>] (do_one_initcall+0x60/0x)
[<c002d2e0>] (do_one_initcall+0x0/0x1ac) from [<c0008798>] (kernel_init+0x9c/0x)
[<c00086fc>] (kernel_init+0x0/0x110) from [<c0045738>] (do_exit+0x0/0x654)
r5:00000000 r4:00000000
davinci_interrupt 368: VBUS error workaround (delay coming)
davinci_interrupt 368: VBUS error workaround (delay coming)

i thhink error is coming becoz kernel is enable to handle address given in ".platform_data=&mt9v113_pdata"

<kernel>=home/dm365/work/leo/kernel/linux-2.6.32

waiting for reply

kailash

NAND Boot failed.

steffi — Thu, 24 Nov 2011 12:17:21 GMT

Hi,

When i on the minicom for the leopard boarddm355 the following things are showing?? i reset the board then also it showing like this.What should i do?? can anyone help me??

BOOTUBLChip initialization passed!
TI UBL Version: 1.30
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
NAND Boot failed.
Starting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBL BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME B!
TI UBL Version: 1.30
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
NAND Boot failed.
Starting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...
BOOTUBLStarting UART Boot...

Thanks

Fail to boot NAND

steffi — Thu, 24 Nov 2011 10:03:51 GMT

Hi,

I was trying to copy the uimage from the NAND flash of leopard boarddm355. I tried the commamd <nand read 0x80700000 0x200000 0x200000> then it was showing message as some 2972152 bytes read.. after that again i gave command as <nand write 0x82000000 0x400000 0x900000> ...and i restarted the board, then on the minicom it was showing that

I don know what to do? Please can anyone help me??

Thanks

CMEMK Error: ALLOC: invalid pool (0) passed. Why ?

Taylor — Sun, 09 Oct 2011 04:21:54 GMT

Hello everyone,

when I excute "./capture_prev_rsz_onthe_fly_bayer_mew" on the target , why does it export the folowning Error

input_std_paramsCMEMK Error: ALLOC: invalid pool (0) passed.

: name = V4L2_STD_MT9T001_VGA_30FPS

input_std_params: output size = 640 * 480

calling cmem utilities for allocating frame buffers

CMEM Error: allocPool: ioctl CMEM_IOCALLOC failed from pool 0: -1

Failed to allocate cmem pool

Unable to Allocate user buffers

why ?

My boot messege is :

U-Boot 2010.12-rc2 (Aug 29 2011 - 17:30:18)

Cores: ARM 297 MHz

DDR: 243 MHz

I2C: ready

DRAM: 128 MiB

NAND: 256 MiB

MMC: davinci: 0, davinci: 1

Net: Ethernet PHY: GENERIC @ 0x00

DaVinci-EMAC

Hit any key to stop autoboot: 0

Loading from nand0, offset 0x400000

Image Name: "RR Linux Kernel"

Created: 2011-10-09 2:04:55 UTC

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 4013504 Bytes = 3.8 MiB

Load Address: 80008000

Entry Point: 80008000

Automatic boot of image at addr 0x82000000 ...

## Booting kernel from Legacy Image at 82000000 ...

Image Name: "RR Linux Kernel"

Created: 2011-10-09 2:04:55 UTC

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 4013504 Bytes = 3.8 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

Starting kernel ...

Linux version 2.6.32-17-ridgerun (root@davicwxc-desktop) (gcc version 4.3.3 (So1

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: DM365 Leopard

Memory policy: ECC disabled, Data cache writeback

DaVinci dm36x_rev1.2 variant 0x8

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 25146

Kernel command line: davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0)

PID hash table entries: 512 (order: -1, 2048 bytes)

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

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

Memory: 99MB = 99MB total

Memory: 96184KB available (3592K code, 285K data, 140K init, 0K highmem)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

NR_IRQS:245

Console: colour dummy device 80x30

Calibrating delay loop... 147.86 BogoMIPS (lpj=739328)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

DaVinci: 8 gpio irqs

NET: Registered protocol family 16

davinci_serial_init:97: failed to get UART2 clock

bio: create slab <bio-0> at 0

DM365 IPIPE initialized in Continuous mode

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

vpss vpss: dm365_vpss vpss probed

vpss vpss: dm365_vpss vpss probe success

dm365_afew_hw_init

ch0 default output "COMPOSITE", mode "NTSC"

VPBE Encoder Initialized

LogicPD encoder initialized

Switching to clocksource timer0_1

musb_hdrc: version 6.0, cppi-dma, host, debug=0

musb_hdrc: USB Host mode controller at fec64000 using DMA, IRQ 12

musb_hdrc musb_hdrc: MUSB HDRC host driver

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

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

TCP reno registered

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

msgmni has been set to 188

alg: No test for stdrng (krng)

io scheduler noop registered

io scheduler anticipatory registered (default)

davincifb davincifb.0: dm_osd0_fb: 720x480x16@0,0 with framebuffer size 1350KB

davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 1020KB

davincifb davincifb.0: dm_osd1_fb: 0x0x8@0,0 with framebuffer size 675KB

davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 1020KB

DM365 IPIPEIF probed

imp serializer initialized

davinci_previewer initialized

davinci_resizer initialized

Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled

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

console [ttyS0] enabled

brd: module loaded

loop: module loaded

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bi)

Scanning device for bad blocks

3 cmdlinepart partitions found on MTD device davinci_nand.0

Creating 3 MTD partitions on "davinci_nand.0":

0x000000000000-0x000000400000 : "UBOOT"

0x000000400000-0x000000840000 : "KERNEL"

0x000000840000-0x00000d040000 : "FS"

davinci_nand davinci_nand.0: controller rev. 2.3

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbtest

i2c /dev entries driver

Linux video capture interface: v2.00

ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)

vpfe_init

vpfe-capture: vpss clock vpss_master enabled

vpfe-capture vpfe-capture: v4l2 device registered

vpfe-capture vpfe-capture: video device registered

mt9p031 1-0048: Detected a MT9P031 chip ID 1801

mt9p031 1-0048: mt9p031 1-0048 decoder driver registered !!

vpfe-capture vpfe-capture: v4l2 sub device mt9p031 registered

vpfe_register_ccdc_device: DM365 ISIF

DM365 ISIF is registered with vpfe.

af major#: 252, minor# 0

AF Driver initialized

aew major#: 251, minor# 0

AEW Driver initialized

Trying to register davinci display video device.

layer=c5061000,layer->video_dev=c5061164

Trying to register davinci display video device.

layer=c5061400,layer->video_dev=c5061564

davinci_init:DaVinci V4L2 Display Driver V1.0 loaded

watchdog watchdog: heartbeat 60 sec

davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

TCP cubic registered

NET: Registered protocol family 17

Clocks: disable unused mmcsd1

Clocks: disable unused spi0

Clocks: disable unused spi1

Clocks: disable unused spi2

Clocks: disable unused spi3

Clocks: disable unused spi4

Clocks: disable unused pwm0

Clocks: disable unused pwm1

Clocks: disable unused pwm2

Clocks: disable unused pwm3

Clocks: disable unused timer1

Clocks: disable unused timer3

Clocks: disable unused emac

Clocks: disable unused voice_codec

Clocks: disable unused asp0

Clocks: disable unused rto

Clocks: disable unused mjcp

davinci_emac_probe: using random MAC addr: 1e:a3:8e:a1:38:a0

emac-mii: probed

Sending DHCP requests ., OK

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

IP-Config: Complete:

device=eth0, addr=192.168.1.132, mask=255.255.255.0, gw=192.168.1.1,

host=192.168.1.132, domain=, nis-domain=(none),

bootserver=0.0.0.0, rootserver=192.168.1.109, rootpath=, mtu=576

Looking up port of RPC 100003/2 on 192.168.1.109

Looking up port of RPC 100005/1 on 192.168.1.109

VFS: Mounted root (nfs filesystem) on device 0:13.

Freeing init memory: 140K

init started: BusyBox v1.18.2 (2011-08-29 15:41:56 CST)

starting pid 967, tty '': '/etc/rcS'

Starting System

done.

Welcome to

__________ .__ .___ __________

\______ \|__| __| _/ ____ ____ \______ \ __ __ ____

| _/| | / __ | / ___\ _/ __ \ | _/| | \ / \

| | \| |/ /_/ | / /_/ >\ ___/ | | \| | /| | \

|____|_ /|__|\____ | \___ / \___ >|____|_ /|____/ |___| /

\/ \//_____/ \/ \/ \/

Embedded Linux Solutions

EVALUATION VERSION FOR NON COMMERCIAL USE ONLY!

"Educational institutions, students, and hobbyists use is encouraged"

For further information see:

http://www.ridgerun.com

Build host: davicwxc-desktop

Built by: root

Build date: Sun, 09 Oct 2011 10:04:54 +0800

Build tag: leopard

Configuring network interfaces

Starting D-Bus message bus system

Starting Ipipe daemon

Loading coprocessors modules...

Loading cmem from 0x86500000 to 0x87400000

CMEMK module: built on Aug 29 2011 at 17:19:42

Reference Linux version 2.6.32

File /usr/local/dvsdk/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/cmem/sc

allocated heap buffer 0xca000000 of size 0xf00000

heap fallback enabled - will try heap if pool buffer is not available

CMEM Range Overlaps Kernel Physical - allowing overlap

CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x86300000)

cmemk initialized

EDMAK module: built on Aug 29 2011 at 17:19:59

Reference Linux version 2.6.32

File /usr/local/dvsdk/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/edma/sc

IRQK module: built on Aug 29 2011 at 17:19:55

Reference Linux version 2.6.32

File /usr/local/dvsdk/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/irq/src

irqk initialized

Starting Dropbear SSH server: dropbear.

I also think there is some wrong with the above bold place ,but I am not sure.

Why does CMEM phys_start (0x1000) overlap kernel (0x80000000 -> 0x86300000) ? Does it lead to the above Error?

Somebody can hep me ?

Thanks for your suggest in advance !

Looking forward to your reply !

Can't build RR..

nikhil@avench — Sat, 17 Sep 2011 14:47:04 GMT

hi,

I am using RR version DM355SDK701905 which is the only available version now. and dvsdk 2_00_00_22.

1 while giving make VERBOSE=1 i am getting the following error. Please help me to fix this error..

2 when will u release your latest SDK version for DM355..?

Thank you..

mv dvsdk_2_00_00_18/Rules.make dvsdk_2_00_00_18/Rules.make.orig
echo PLATFORM=dm355 > dvsdk_2_00_00_18/Rules.make
cat Rules.make >> dvsdk_2_00_00_18/Rules.make
quilt push -a
Applying patch dvsdk.patch
patching file dvsdk_2_00_00_18/dsplink-1_60-prebuilt/packages/dsplink/make/Linux/davinci_mvlpro5.0.mk

7 out of 7 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dsplink-1_60-prebuilt/packages/dsplink/make/Linux/davinci_mvlpro5.0.mk
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/decode/Makefile

3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/decode/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/encode/Makefile

3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/encode/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/encodedecode/Makefile

3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm6446/encodedecode/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/jpegdec/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/jpegenc/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/vdec/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/venc/Makefile
patching file dvsdk_2_00_00_18/dmai_1_20_00_06/packages/ti/sdo/dmai/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/decode/Makefile
Hunk #1 FAILED at 13.
Hunk #2 FAILED at 39.
Hunk #3 FAILED at 82.
3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/decode/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encode/Makefile

3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encode/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encodedecode/Makefile

3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encodedecode/Makefile
patching file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/interface/Makefile
Hunk #1 FAILED at 13.
Hunk #2 FAILED at 39.
Hunk #3 FAILED at 81.
3 out of 3 hunks FAILED -- rejects in file dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/interface/Makefile
patching file dvsdk_2_00_00_18/dmai_1_20_00_06/packages/ti/sdo/dmai/apps/Makefile.app
patching file dvsdk_2_00_00_18/dvtb_4_00_04/packages/ti/sdo/dvtb/dm355/Makefile
Hunk #1 FAILED at 29.
1 out of 1 hunk FAILED -- rejects in file dvsdk_2_00_00_18/dvtb_4_00_04/packages/ti/sdo/dvtb/dm355/Makefile
Patch dvsdk.patch does not apply (enforce with -f)
make[3]: *** [patched] Error 1
make[3]: Leaving directory `/opt/DM355SDK701905/proprietary/dvsdk_2_00_00'
Error building dvsdk_2_00_00
make[2]: *** [dependency_build] Error 1
make[2]: Leaving directory `/opt/DM355SDK701905/proprietary'
make[1]: *** [proprietary_src_build] Error 1
make[1]: Leaving directory `/opt/DM355SDK701905/fs'
make: *** [fs_build] Error 2

Using Gstreamer for simultaneous

Kacie — Mon, 22 Mar 2010 05:33:21 GMT

Hi,

I am attempting to construct a pipeline that uses a tee element so that I can run a few different threads from my Leopard board. So far, I have tried to record and live preview simultaneously but I have not been successful.

Taking a stab, I would have thought that the following would be an appropriate pipeline to do this:

/ # gst-launch v4l2src always-copy=false ! dmaiaccel ! \

> tee name=tee .src0,src1 tee.src0 ! \

> queue ! TIDmaiVideoSink sync=false displayStd=v4l2 displayDevice=/dev/video2 tee.src1 !\

> queue ! dmaienc_mpeg4 ! qtmux ! filesink location=test.mp4

This piepline results in a live image on the screen for about a second which freezes, and a file is created with nothing in it - the terminal window loom like this:

/ # gst-launch v4l2src always-copy=false ! dmaiaccel ! tee name=tee .src0,src1 t
ee.src0 ! queue ! TIDmaiVideoSink sync=false displayStd=v4l2 displayDevice=/dev/
video2 tee.src1 ! queue ! dmaiaccel ! dmaienc_mpeg4 ! qtmux ! filesink location=
test.mp4
<7>mt9v113 1-003c: mt9v113_write_reg reg=0x98c, val=0x2739
Setting pipeline to PAUSED ...
[ 3060.700000] mt9v113 1-003c: invalid control id 9963781
[ 3060.710000] mt9v113 1-003c: invalid control id 9963782
[ 3060.710000] mt9v113 1-003c: invalid control id 9963783
[ 3060.720000] mt9v113 1-003c: invalid control id 9963784
[ 3060.720000] mt9v113 1-003c: invalid control id 9963785
[ 3060.730000] mt9v113 1-003c: invalid control id 9963786
[ 3060.730000] mt9v113 1-003c: invalid control id 9963787
[ 3060.740000] mt9v113 1-003c: invalid control id 9963788
[ 3060.740000] mt9v113 1-003c: invalid control id 9963789
[ 3060.750000] mt9v113 1-003c: invalid control id 9963790
[ 3060.750000] mt9v113 1-003c: invalid control id 9963791
[ 3060.760000] mt9v113 1-003c: invalid control id 9963792
[ 3060.760000] mt9v113 1-003c: invalid control id 9963793
[ 3060.770000] mt9v113 1-003c: invalid control id 9963796
[ 3060.780000] mt9v113 1-003c: invalid control id 9963797
[ 3060.780000] mt9v113 1-003c: invalid control id 9963798
[ 3060.790000] mt9v113 1-003c: invalid control id 9963799
[ 3060.790000] mt9v113 1-003c: invalid control id 9963800
[ 3060.800000] mt9v113 1-003c: invalid control id 9963801
[ 3060.800000] mt9v113 1-003c: invalid control id 9963802
[ 3060.810000] mt9v113 1-003c: invalid control id 9963803
[ 3060.810000] mt9v113 1-003c: invalid control id 9963804
[ 3060.820000] mt9v113 1-003c: invalid control id 9963805
[ 3060.820000] mt9v113 1-003c: invalid control id 9963806
[ 3060.840000] vpfe-capture: hpitch = 640, vpitch = 480, bpp = 2
[ 3060.850000] vpfe-capture: adjusted hpitch = 640, vpitch = 480, bpp = 2
[ 3060.870000] vpfe-capture vpfe-capture: calling ccdc_config_raw()
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

The pipeline does not stop until I press ctrl C.

I have played around a little with the elements and theire order and from what I can gather it appears that the dmaienc_mpeg4 element (I think) that causes the freeze.

I was wondering if anybody could help

Kacie

SD Card boot not working

prongs — Thu, 04 Aug 2011 19:25:00 GMT

I was following the getting started guide for leopard board and I successfully completed make, make install commands and after that in minicom, boot works just fine. But from what I guess it is booting from nand flash. I want to boot it from SD card. I was following this guide :

http://processors.wiki.ti.com/index.php/SD_card_boot_and_flashing_tool_for_DM355_and_DM365

I created two partitions mmcblk0p1(fat32) and mmcblk0p2(linux) on the sd card. After inserting it into the board, I switched to sd boot mode of the board. After that I pressed the reset button but that does not work. Basically, nothing happens. After switching back to nand mode, I am able to reset and boot but sd mode does not work. While booting in nand mode, I can see /dev/mmcblk0p1 and p2. When we set bootargs_root environment variable to /dev/mmcblk0p1 in nand mode, then it does something but gets stuck at

"starting kernel"

I would appreciate any kind of help. Feel free to ask for more info.

--prongs

How do I go about returning this worthless board?

coolcorey13755 — Tue, 02 Aug 2011 00:17:18 GMT

I have been trying to get this DM355 to boot for about 2 weeks now. I have received no answers to questions, using your SD boot tool does nothing, the RR SDK refuses to build, the EVM kernel and rootfs will not boot, and I don't have a JTAG so I do not feel safe flashing U-Boot, which may be the issue since the version that came in flash memory is about 4 years old and lacks support for most things useful.

So how do I get my money back for this expensive paperweight?

At least with a GumStix board I can get some help.

Can't build RR,

coolcorey13755 — Mon, 25 Jul 2011 03:29:02 GMT

It seems to me that support for the DM355 is waning. I have, in a meticulous way, gone through each step of http://processors.wiki.ti.com/index.php/Installing_RR_free_SDK_for_Leopard_Board.

1.) DM355SDK-840402-Linux-x86-Install.bin doesn't even exist.
2.) The only OS support for RR is 9.04 with the extremely old version that is available via the link on this page. Ubuntu is currently in the elevens...?
3.) so you can hack that by adding to the $DEVDIR/bsp/oscheck the version of Ubuntu you are using, fine.
4.) After running make, assuming you can even get this far, I am plagued with this:
"
patching file dvsdk_2_00_00_18/examples/dm355/jpegdec/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/jpegenc/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/vdec/Makefile
patching file dvsdk_2_00_00_18/examples/dm355/venc/Makefile
patching file dvsdk_2_00_00_18/dmai_1_20_00_06/packages/ti/sdo/dmai/Makefile
can't find file to patch at input line 315
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/decode/Makefile
|===================================================================
|--- dvsdk_2_00_00.orig/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/decode/Makefile    2009-05-11 08:58:49.000000000 -0600
|+++ dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/decode/Makefile2009-05-12 08:03:07.000000000 -0600
--------------------------
No file to patch. Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 356
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encode/Makefile
|===================================================================
|--- dvsdk_2_00_00.orig/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encode/Makefile    2009-05-11 08:58:49.000000000 -0600
|+++ dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encode/Makefile2009-05-12 08:03:07.000000000 -0600
--------------------------
No file to patch. Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 397
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encodedecode/Makefile
|===================================================================
|--- dvsdk_2_00_00.orig/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encodedecode/Makefile    2009-05-11 08:58:49.000000000 -0600
|+++ dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/encodedecode/Makefile    2009-05-12 08:03:07.000000000 -0600
--------------------------
No file to patch. Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 438
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/interface/Makefile
|===================================================================
|--- dvsdk_2_00_00.orig/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/interface/Makefile    2009-05-11 08:58:49.000000000 -0600
|+++ dvsdk_2_00_00/dvsdk_2_00_00_18/dvsdk_demos_2_00_00_04/dm355/interface/Makefile    2009-05-12 08:03:07.000000000 -0600
--------------------------
No file to patch. Skipping patch.
3 out of 3 hunks ignored
patching file dvsdk_2_00_00_18/dmai_1_20_00_06/packages/ti/sdo/dmai/apps/Makefile.app
can't find file to patch at input line 520
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: dvsdk_2_00_00/dvsdk_2_00_00_18/dvtb_4_00_04/packages/ti/sdo/dvtb/dm355/Makefile
|===================================================================
|--- dvsdk_2_00_00.orig/dvsdk_2_00_00_18/dvtb_4_00_04/packages/ti/sdo/dvtb/dm355/Makefile    2009-05-12 10:11:31.000000000 -0600
|+++ dvsdk_2_00_00/dvsdk_2_00_00_18/dvtb_4_00_04/packages/ti/sdo/dvtb/dm355/Makefile    2009-05-12 10:12:42.000000000 -0600
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
Patch dvsdk.patch does not apply (enforce with -f)
make[3]: *** [patched] Error 1
make[3]: Leaving directory `/opt/DM355SDK701905/proprietary/dvsdk_2_00_00'
Error building dvsdk_2_00_00
make[2]: *** [dependency_build] Error 1
make[2]: Leaving directory `/opt/DM355SDK701905/proprietary'
make[1]: *** [proprietary_src_build] Error 1
make[1]: Leaving directory `/opt/DM355SDK701905/fs'
make: *** [fs_build] Error 2
corey@corey-desktop:/opt/DM355SDK701905$

"

Now, people have used soime sort of magical patch to fix the issue, but of course that only works on a version of RR that is no longer available for download.

The only question I have, since I am beginning to realize how futile this path is, is this: Are there ANY working sets of instructions that can instruct one to create a usable DM355 board? OR! does anyone have an SD image that works?!

1.3 mege pixel MT9M112 Driver

kpjobanputra — Tue, 19 Jul 2011 05:07:50 GMT

Dear Friends,

I have buillded the RidgeRun SDK(DM355SDK840402) for Leopard Board. Now I want to capture the Image from the camera.

I am using camera 1.3 mega pixel(Sensor: Aptina 1/4“ CMOS Sensor MT9M112). Does the RidgeRun provide a driver of MT9M112 driver.

As i have search on sdk i find there is no driver for MT9M112.

Can any body help me, from where i will get a driver and how to integrate with this sdk?

Regards

Kiran Thakkar

error showing-configuring usb otg

vigneshs@adeptte.com — Mon, 27 Jun 2011 06:53:47 GMT

hi all,

i triy to cinfigure usb otg in leo365,configured as per procedure given in below :

https://www.ridgerun.com/developer/wiki/index.php/How_to_configure_DM365_for_USB_host,_device_and_OTG_support

but it showing following error while try to recompile and install,

any suggesstion???

dm365@dm365-desktop:~/work/leo365$ make
Ridgerun Linux SDK
Board configuration: Leopard Board DM365

Processing toolchain...
Build complete
Processing kernel...
<stdin>:1351:2: warning: #warning syscall migrate_pages not implemented
drivers/usb/gadget/r8a66597-udc.c: In function ‘r8a66597_probe’:
drivers/usb/gadget/r8a66597-udc.c:1585: error: implicit declaration of function ‘IS_ERR’
drivers/usb/gadget/r8a66597-udc.c:1588: error: implicit declaration of function ‘PTR_ERR’
make[4]: *** [drivers/usb/gadget/r8a66597-udc.o] Error 1
make[3]: *** [drivers/usb/gadget] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [build] Error 2
make: *** [kernel_build] Error 2
dm365@dm365-desktop:~/work/leo365$

Using UART1 with Leoparboard 355 to interface with another device

Billy — Sun, 08 May 2011 08:36:02 GMT

Hi,

I am trying to use the UART1 port to communicate with a camera. I am using the RR SDK.

I really don't know where to start when it comes to coding. I've checked out all the code I can on how the UART is configured:

kernel/linux-2.6.29/arch/arm/mach-davinci/board-dm355-leopard.c
kernel/linux-2.6.29/arch/arm/mach-davinci/serial.c
kernel/linux-2.6.29/arch/arm/mach-davinci/include/mach/serial.h

I tried linking to the serial.h header file above, but my code won't compile because it can't find the file when I try to include it with the line:

#include <mach/serial.h>

As of now, I'm just trying to get something that can transmit data across this protocol using the uart drivers that the RR SDK claims to support. The code (that doesn't compile) is as follows. It should just write a bunch of 1's and 0's to the ttyS1 device.

*****************************************

#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>

#include <sys/ioctl.h>

#include <linux/serial.h>
#include <mach/serial.h>

#define UART1_DEV "/dev/ttyS1"

static struct davinci_uart_config uart_config = {
    .enabled_uarts = (1 << 1), /* I think this enables UART1 */
}

int main(int argc, char *argv[]) {
    int out_value = 1;
    int uart1_fd;  /* UART1 file descriptor */

    /* initialize the serial port */
    davinci_serial_init(&uart_config);

    uart1_fd = open(UART1_DEV, O_RDWR);
    if (uart1_fd == -1) {
        /* error opening serial port */
        perror("open");
        return 1;
    }

    if ( ioctl(uart1_fd, DAVINCI_UART1_BASE, uHwAddress) < 0) {
        /* error assigning uart1_fd to the UART1 hardware
         * address */
        perror("ioctl");
        return -1;
    }

    while (1) {

        if ( -1 == write(uart1_fd, out_value, 2) ) {
            perror("write");
            return 1;
        }
        sleep(1);

        out_value ^= 1; /* toggle the out value */

        /*if ( -1 == write(uart1_fd, "hello", 6) ) {
            perror("write");
            return 1;
        }*/
    }

    return 0;
}

************************

Any help would be great!  Some examples would even be greater!

Thanks,

Billy

How to configure DM365 for USB host

vigneshs@adeptte.com — Fri, 17 Jun 2011 11:24:07 GMT

hi my dear friends,

im presently working in leopard dm365

i need to stream the video file through usb for that

can any one suggest me ,How to configure DM365 for USB host

nand flash as storing device

vigneshs@adeptte.com — Wed, 15 Jun 2011 11:34:20 GMT

hi everybody,

is it is possible to store the video(+audio) streaming data in nand flash through usb ?

if it is ,then can u help me ?

suggest the method .

regards vs.,

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

Justin — Tue, 17 May 2011 12:49:16 GMT

Hi there.

I'm having trouble getting started with my LeopardBoard DM355.
I get the following error once I have flashed the leopardboard:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

I have attached what thought to be relevant.
Has anyone encountered this before? Any ideas of where I what went wrong?

*********************************************************************
            DM355 LEOPARD:
*********************************************************************
DM35x
initialization passed!
Customized by RidgeRun
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000002.
   DONE
Jumping to entry point at 0x81080000.

U-Boot customized by RidgeRun
U-Boot 2009.11 (May 13 2011 - 19:59:55)

Cores: ARM 216 MHz
DDR:   171 MHz
I2C:   ready
DRAM: 128 MB
NAND: 256 MiB
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x000000020000
nand_read_bbt: Bad block at 0x000000040000
nand_read_bbt: Bad block at 0x000000060000
nand_read_bbt: Bad block at 0x000000080000
nand_read_bbt: Bad block at 0x0000000a0000
nand_read_bbt: Bad block at 0x0000000c0000
Net:   dm9000
Hit any key to stop autoboot: 0

Loading from nand0, offset 0xc0000
Skipping bad block 0x000c0000
   Image Name:   "RR Linux Kernel"
   Created:      2011-05-16 12:55:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3376616 Bytes = 3.2 MB
   Load Address: 80008000
   Entry Point: 80008000
Skipping bad block 0x000c0000
Automatic boot of image at addr 0x80700000 ...
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   "RR Linux Kernel"
   Created:      2011-05-16 12:55:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3376616 Bytes = 3.2 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Linux version 2.6.29-ridgerun-davinci1 (justin@ubuntu) (gcc version 4.2.4) #1 PREEMPT Fri May 13 19:31:29 SAST 2011
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: DaVinci DM355 leopard
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] DaVinci DM0355 variant 0x0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 29464
[    0.000000] Kernel command line: console=ttyS0,115200n8 video=davincifb:osd1=0x0x8 root=/dev/mtdblock3 rw mem=116M rootfstype=jffs2 mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[42949372.960000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[42949372.960000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[42949372.980000] Memory: 116MB = 116MB total
[42949372.980000] Memory: 114076KB available (3056K code, 208K data, 116K init)
[42949372.980000] Calibrating delay loop... 107.72 BogoMIPS (lpj=538624)
[42949373.210000] Mount-cache hash table entries: 512
[42949373.210000] CPU: Testing write buffer coherency: ok
[42949373.210000] net_namespace: 520 bytes
[42949373.220000] NET: Registered protocol family 16
[42949373.220000] MUX: initialized INT_EDMA_CC
[42949373.220000] MUX: initialized VIN_CINL_EN
[42949373.250000] DaVinci: 104 gpio irqs
[42949373.330000] bio: create slab <bio-0> at 0
[42949373.340000] vpss vpss: dm355_vpss vpss probed
[42949373.340000] vpss vpss: dm355_vpss vpss probe success
[42949373.340000] ch0 default output "COMPOSITE", mode "NTSC"
[42949373.340000] VPBE Encoder Initialized
[42949373.350000] SCSI subsystem initialized
[42949373.350000] usbcore: registered new interface driver usbfs
[42949373.350000] usbcore: registered new interface driver hub
[42949373.360000] usbcore: registered new device driver usb
[42949373.370000] Avnetlcd encoder initialized
[42949373.380000] musb_hdrc: version 6.0, pio, host, debug=0
[42949373.400000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[42949373.400000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[42949373.400000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[42949373.400000] usb usb1: configuration #1 chosen from 1 choice
[42949373.400000] hub 1-0:1.0: USB hub found
[42949373.400000] hub 1-0:1.0: 1 port detected
[42949373.410000] NET: Registered protocol family 2
[42949373.410000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[42949373.410000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[42949373.410000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[42949373.410000] TCP: Hash tables configured (established 4096 bind 4096)
[42949373.410000] TCP reno registered
[42949373.410000] NET: Registered protocol family 1
[42949373.420000] JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
[42949373.430000] msgmni has been set to 223
[42949373.430000] io scheduler noop registered (default)
[42949373.440000] davincifb davincifb.0: dm_osd0_fb: 720x480x16@0,0 with framebuffer size 1350KB
[42949373.450000] davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 675KB
[42949373.460000] davincifb davincifb.0: dm_osd1_fb: 0x0x8@0,0 with framebuffer size 1350KB
[42949373.470000] davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 675KB
[42949373.480000] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
[42949373.480000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[42949373.480000] console [ttyS0] enabled
[42949373.810000] brd: module loaded
[42949373.840000] loop: module loaded
[42949373.840000] dm9000 Ethernet Driver, V1.31
[42949373.970000] Unable to read MAC address: Generating random value ...
[42949373.970000] The random generated MAC address: 56:53:ba:ae:bf:c6 will be assigned to your device
[42949373.980000] eth0 (dm9000): not using net_device_ops yet
[42949373.990000] eth0: dm9000e at c785c000,c7860016 IRQ 73 MAC: 56:53:ba:ae:bf:c6 (chip)
[42949374.000000] Linux video capture interface: v2.00
[42949374.010000] vpfe-capture vpfe-capture: video device registered
[42949374.010000] vpfe-capture vpfe-capture: v4l2 int master registered
[42949374.020000] vpfe_capture: init successful
[42949374.030000] Trying to register davinci display video device.
[42949374.030000] layer=c65f7200,layer->video_dev=c65f7364
[42949374.040000] Trying to register davinci display video device.
[42949374.050000] layer=c65f7000,layer->video_dev=c65f7164
[42949374.050000] davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
[42949374.060000] vpfe-capture vpfe-capture: register slave mt9v113
[42949374.070000] mt9v113 1-003c: chip id mismatch read 0x0, expecting 0x2280
[42949374.070000] mt9v113 1-003c: Unable to detect decoder
[42949374.080000] mt9v113 1-003c: Registered to v4l2 master vpfe-capture!!
[42949374.090000] Driver 'sd' needs updating - please use bus_type methods
[42949374.100000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[42949374.110000] 2 NAND chips detected
[42949374.110000] Scanning device for bad blocks
[42949374.120000] Bad eraseblock 3 at 0x000000060000
[42949374.120000] Bad eraseblock 4 at 0x000000080000
[42949374.130000] Bad eraseblock 5 at 0x0000000a0000
[42949374.130000] Bad eraseblock 6 at 0x0000000c0000
[42949374.220000] Bad eraseblock 2051 at 0x000010060000
[42949374.220000] Bad eraseblock 2052 at 0x000010080000
[42949374.230000] Bad eraseblock 2053 at 0x0000100a0000
[42949374.230000] Bad eraseblock 2054 at 0x0000100c0000
[42949374.320000] 4 cmdlinepart partitions found on MTD device davinci_nand.0
[42949374.330000] Creating 4 MTD partitions on "davinci_nand.0":
[42949374.340000] 0x000000000000-0x0000000a0000 : "UBOOT"
[42949374.350000] 0x0000000a0000-0x0000000c0000 : "UBOOT_ENV"
[42949374.360000] 0x0000000c0000-0x000000480000 : "KERNEL"
[42949374.360000] 0x000000480000-0x0000019e0000 : "FS"
[42949374.370000] davinci_nand davinci_nand.0: controller rev. 2.3
[42949374.380000] Initializing USB Mass Storage driver...
[42949374.390000] usbcore: registered new interface driver usb-storage
[42949374.390000] USB Mass Storage support registered.
[42949374.400000] i2c /dev entries driver
[42949374.410000] watchdog watchdog: heartbeat 60 sec
[42949374.420000] davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
[42949374.430000] davinci_mmc davinci_mmc.1: Using DMA, 4-bit mode
[42949374.450000] Advanced Linux Sound Architecture Driver Version 1.0.18a.
[42949374.460000] No device for DAI tlv320aic3x
[42949374.470000] No device for DAI davinci-i2s
[42949374.470000] AIC3X Audio Codec 0.2
[42949374.480000] asoc: tlv320aic3x <-> davinci-i2s mapping ok
[42949374.510000] ALSA device list:
[42949374.510000]   #0: Leopard Board (tlv320aic3x)
[42949374.520000] TCP cubic registered
[42949374.520000] NET: Registered protocol family 17
[42949374.530000] RPC: Registered udp transport module.
[42949374.530000] RPC: Registered tcp transport module.
[42949374.540000] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[42949387.490000] Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
[42949387.500000] empty_blocks 0, bad_blocks 0, c->nr_blocks 171
[42949387.500000] VFS: Cannot open root device "mtdblock3" or unknown-block(31,3)
[42949387.510000] Please append a correct "root=" boot option; here are the available partitions:
[42949387.520000] 1f00             640 mtdblock0 (driver?)
[42949387.520000] 1f01             128 mtdblock1 (driver?)
[42949387.530000] 1f02            3840 mtdblock2 (driver?)
[42949387.530000] 1f03           21888 mtdblock3 (driver?)
[42949387.540000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

***************************************************************************

***************************************************************
            IFCONFIG
***************************************************************
justin@ubuntu:~$ ifconfig

eth0      Link encap:Ethernet HWaddr 48:5b:39:b7:84:02
          inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::4a5b:39ff:feb7:974f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:3693 (3.6 KB)
          Interrupt:29 Base address:0x2000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10660 (10.6 KB) TX bytes:10660 (10.6 KB)
***************************************************************

***************************************************************
            PRINTENV
***************************************************************

DM355 LEOPARD # printenv
bootdelay=3
baudrate=115200
ethaddr="00:0e:99:00:05:2e"
bootfile="uImage"
ethact=dm9000
mtdparts=mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
mtdids=nand0=davinci_nand.0
filesize=338628
kernelloadaddr=0x82000000
kernelsaveaddr=0xC0000
kerneloffset=0xC0000
ksize=0x340000
kernelmd5sum=23c2767fb1fc9a9fbd2d732674843890
ipaddr=192.168.1.100
partition=nand0,0
mtddevnum=0
mtddevname=UBOOT
fssize=0x15537D4
fssaveaddr=0x480000
fsoffset=0x480000
bootargs=console=ttyS0,115200n8 video=davincifb:osd1=0x0x8 root=/dev/mtdblock3 rw mem=116M rootfstype=jffs2 mtdparts=davinci_nand.0:640k(UBOOT),128k(UBOOT_ENV),3840k(KERNEL),21888k(FS)
serverip=192.168.1.50
bootcmd=nboot KERNEL
autostart=yes
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.11 (May 13 2011 - 19:59:55)

Environment size: 799/131068 bytes
*******************************************************

***************************************************************
        MAKE CONFIG
***************************************************************

Make Config -> Architecture configurations:

     (192.168.1.50) Linux network IP address (eth0)
     (255.255.255.0) Linux network mask address for interface (eth0)
     (48:5b:39:b7:84:02)Linux network ethernet address (eth0)

Make Config -> Installer Configuration:

      (0x82000000) RAM address to load components
       Communication method with the target board (Serial port) --->
       (/dev/ttyS0) Serial port for target communication
        Protocol for transfering images to the target (TFTP) --->
      Flashing method for the bootloader (U-boot Commands) --->
         *** Network options for installation ***
      (eth0) Interface on your host machine connected to your target hardware
      U-boot IP address (Static IP address) --->
      (192.168.1.100) Static IP
     (255.255.255.0) Static mask
      *** NAND Flash memory map (Partitions sizes are given in blocks number) ***
     (5) Uboot partition size
     (1) Uboot environment partition size
     (30) Minimum kernel partition size
     (160) Mininum file system partition size
      *** MTD Integration options ***
    [*] Configure Kernel MTD partitions with U-boot information
   (davinci_nand.0) MTD device name
      MTD extra partitions

********************************************************

********************************************************
        WHEN I CONNCT TO WIFI
********************************************************
justin@ubuntu:~$ ifconfig
eth0      Link encap:Ethernet HWaddr 48:5b:39:b7:84:02
          inet6 addr: fe80::4a5b:39ff:feb7:974f/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:11856 (11.8 KB)
          Interrupt:29 Base address:0x2000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14212 (14.2 KB) TX bytes:14212 (14.2 KB)

wlan0     Link encap:Ethernet HWaddr 00:0c:f6:85:d9:01
          inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::20c:f6ff:fe85:d901/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:7250 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2969 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3766299 (3.7 MB) TX bytes:657390 (657.3 KB)

Leopard board SDK Stable Version

kpjobanputra — Wed, 08 Jun 2011 10:43:25 GMT

Dear Friends,

I have beagle board and trying to build rootfs and uImage with gStremer.

Can you please tell me which is stable version of SDK which will build without any error.

I have tried with DM355SDK840402 and DM355SDK789311 with

dvsdk_2_00_00_22

xdctools_3_10_05

But It is giving me building error.

Regards

Kiran Thakkar

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

Justin — Mon, 16 May 2011 16:07:50 GMT