This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLP LightCrafter powers off after boot

Other Parts Discussed in Thread: DLPC300

Hello.

I am having the following problem with my DLP LightCrafter (LC).

The LC correctly boots from the NAND but it fails when running the "command handler application".

Before that point the LEDs on both boards are green. After the error, the board on top the LC switches off (the green LEDs disappear) and a red LED starts blinking in the bottom board.

The strange thing is that I was able (only once) to connect to the LC with the DLP LightCrafter GUI. After I disconnected that very first time, I am having this problem, that is the LC powers off after booting.

I have access to the UART console. The log from the console is attached at the end of this post.

Any idea what is causing the error and how to solve it?

Thanks in advance.
Fred M.

Here is the log from the UART.

-----------------------------------------------
         LightCrafter - NAND Boot
-----------------------------------------------
nand_size=134217728
 u-boot  src=0x00320800
nand_read block_idx=0x00000019 page_idx=0x00000001 len=0x0002D000
block=0000001A
 kernel  src=0x00400000
nand_read block_idx=0x00000020 page_idx=0x00000000 len=0x00300000
block=00000038
 file-system  src=0x00800000
nand_read block_idx=0x00000040 page_idx=0x00000000 len=0x00300000
block=00000058
Jummping to nand bootloader


U-Boot 2010.12-rc2 (Sep 16 2013 - 13:35:08)

Cores: ARM 297 MHz
DDR:   243 MHz
I2C:   ready
DRAM:  128 MiB
GPIO Config NAND-WP : GPIO76 as output (1)
GPIO Config DVI-I2C-EN : GPIO73 as output (0)
GPIO Config DVI-ENA : GPIO74 as output (0)
GPIO Config CAM-RESETZ : GPIO102 as output (0)
GPIO Config CAM-RESETZ : GPIO102 as output (1)
GPIO Config CAM-DENABLE : GPIO93 as output (1)
MMC:   davinci: 0
Using default environment

Net:   No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2013-09-20  10:44:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1603744 Bytes = 1.5 MiB
   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.32.17-davinci1 (sanjeev@sanjeev-VirtualBox) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #5

PREEMPT Fri Sep 20 16:14:26 IST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DM365 LCr
Memory policy: ECC disabled, Data cache writeback
DaVinci dm36x_rev1.2 variant 0x8
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 29464
Kernel command line: mem=116M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,5M ramdisk_size=15360 ip=off

video=davincifb:vid0=1216x684x16,4050K:vid1=off:osd0=0x0x8,0K:osd1=0x0x8,0K dm365_imp.oper_mode=0

davinci_enc_mngr.ch0_output=LCD davinci_enc_mngr.ch0_mode=1216x684YUV vpfe_capture.interface=1
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: 116MB = 116MB total
Memory: 108956KB available (3024K code, 243K data, 124K 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
vpss vpss: dm365_vpss vpss probed
vpss vpss: dm365_vpss vpss probe success
dm365_afew_hw_init
ch0 default output "LCD", mode "1216x684YUV"
VPBE Encoder Initialized
LogicPD encoder initialized
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi-dma, peripheral, debug=0
musb_hdrc: USB Peripheral mode controller at fec64000 using DMA, IRQ 12
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
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 5120K
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 223
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
davincifb davincifb.0: dm_vid0_fb: 1216x684x16@0,0 with framebuffer size 4050KB
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
serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Creating 4 MTD partitions on "davinci_nand.0":
0x000000000000-0x000000400000 : "bootloader"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000000c00000 : "rootfs"
0x000000c00000-0x000008000000 : "data"
davinci_nand davinci_nand.0: controller rev. 2.3
spi_davinci spi_davinci.0: Controller at 0xfec66000
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 06:14:76:56:4b:7d
usb0: HOST MAC d2:eb:83:8c:7c:e1
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
i2c /dev entries driver
Linux video capture interface: v2.00
vpfe_init
vpfe-capture: vpss clock vpss_master enabled
vpfe-capture vpfe-capture: v4l2 device registered
vpfe-capture vpfe-capture: video device registered
IndPico : switch to HD imager-MT9P031 video input
Sanjeev::MT9P031-> Probing for the camera device...
Sanjeev::MT9P031-> Camera device not detected!!!
vpfe-capture vpfe-capture: v4l2 sub device mt9p031 register fails
suresh:mt9m112_probe()
Sanjeev::MT9M112-> Probing for the camera device...
suresh:mt9m112 : f0 <= 0
mt9m112 : page reg write failed !!!!!!!
mt9m112 1-0048: No MT9M11x chip detected, register read ffffff87
Sanjeev::MT9M112-> Camera device not detected!!!
vpfe-capture vpfe-capture: v4l2 sub device mt9m112 register fails
mt9v113 1-003c: No MT9V113 chip detected, register read ffffff87
vpfe-capture vpfe-capture: v4l2 sub device mt9v113 register fails
No sub devices registered
vpfe_register_ccdc_device: DM365 ISIF
dm365_isif: probe of dm365_isif failed with error -22
af major#: 252, minor# 0
AF Driver initialized
aew major#: 251, minor# 0
AEW Driver initialized
Trying to register davinci display video device.
layer=c669c000,layer->video_dev=c669c164
Trying to register davinci display video device.
layer=c669c400,layer->video_dev=c669c564
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
watchdog watchdog: heartbeat 60 sec
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
TCP cubic registered
NET: Registered protocol family 17
Clocks: disable unused mmcsd1
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_mmc davinci_mmc.0: powerup timeout
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 124K
init started: BusyBox v1.14.2 (2013-09-17 12:10:50 IST)
starting pid 927, tty '': '/etc/rcS'
Starting System
done.
Welcome to
 _     _       _     _    ____            __ _
| |   (_) __ _| |__ | |_ / ___|_ __ __ _ / _| |_ ___ _ __
| |   | |/ _` | '_ \| __| |   | '__/ _` | |_| __/ _ \ '__|
| |___| | (_| | | | | |_| |___| | | (_| |  _| ||  __/ |
|_____|_|\__, |_| |_|\__|\____|_|  \__,_|_|  \__\___|_|
         |___/

                DLP(R) Pico Development Platform
Build host: ubuntu
Built by: a0876512
Build date: Fri, 24 Jun 2011 14:23:15 +0530
Build tag: leopard
Skipping Network Config ...
Starting IndPico Command Handler ....
Running LightCrafter command handler application.... build date Sep 17 2013 12:10:28

Please press Enter to activate this console. I2CRegister.c:154 >> Error = ERR_DEVICE_FAIL
DLPC300.c:198 >> FAIL
API.c:181 >> DPP_Init() Failed
API_Init() FailedDatabase.c:146 >> Error = FAIL
API.c:1694 >> Error = FAIL
API.c:413 >> Error = FAIL
I2CRegister.c:154 >> Error = ERR_DEVICE_FAIL
DLPC300.c:453 >> FAIL
API.c:261 >> Error = FAIL
API.c:226 >> FAIL
API.c:311 >> Error = FAIL
I2CRegister.c:154 >> Error = ERR_DEVICE_FAIL
DLPC300.c:453 >> FAIL
API.c:261 >> Error = FAIL
API.c:226 >> FAIL

  • Hello Fred,

    You mentioned it is booting, therefore I am assuming, the four logo images shown as part of boot sequence, please confirm if it is not.

    Why the command handler application failing?

    It appears to be issue with DM365 not able to communicate with DLPC300, if you refer to the schematics or the hardware, there is J8 (80-pin) interface connector going between, top board (System Board) and bottom board (Driver Board), the I2C lines from DM365 goes to DLPC300 from here. Unless there is no damage to the board, the poor contacts in the connector could be one reason. Please remove and reconnect the boards via the J8 connector firmly or just press the boards firmly, see if you are now able to make interface working.

    Regards,

    Sanjeev

  • Hi Sanjeev,

    The splash screen or four logo images are not shown during the boot sequence. It seems that the LEDs are NOT switched on in my board.

    Removing and reconnecting the board firmly did not solve the problem.

    According to the UART log, it appears to be a problem with I2C, as you pointed out in your previous post.
    The DM365 in the System Board (top) is connected to the Driver Board (bottom) via I2C through the J8 80-pin board connector.

    In the Driver Board there is an I2C connector just next to the MSP430 or DLPC300 flash programming interface.
    Does this I2C output refer to the same I2C connection that might be broken between the top and bottom boards?
    Is this connector what is referred to as "I2C Switch" in the schematics?
    If yes, then I should be able to see what the problem is by probing it. Is this correct/do you agree?

    Thanks for your time.

  • Hello Fred,

    There is seems to problem on the driver board itself.

    Just remove the the top board (System Board), apply power, you should see that the LOGO displayed on the DMD, the MSP430 via I2C issues commands to DLPC300 to load the logo from its flash. If it is not happening, the DLPC300 flash may be corrupt or fault on the driver board causing no i2c communication b/w MSP430 & DLPC300. Unless this part is fixed, it is not possible to recover the hardware.

    Now, the I2C switch U21 part on the Driver Board is activated when MSP430 completes sending commands to DLPC300. After this only, with U21 enabled the I2C link b/w DM365 I2C from system board is established. 

    So I suggest, to concentrate on driver board to figure out why MSP430 to DLPC300 communication not working.

    Regards,

    Sanjeev

  • Hi Sanjeev,

    I can't see the LOGO displayed on the DMD.

    In order to ensure it is not the flash of the DLPC300, is there a way to reflash it?
    Can you provide with relevant information on this topic?

    Regards,
    Fred