TI DM816x/AM389x EVM board hangs while booting

Maynard Cabiente

Other Parts Discussed in Thread: PMP

Hello,

We purchased 2 TI DM816x EVM boards for evaluation 2 months ago. I have been working with the first board for 2 months now without any issue. Today, we just opened the second board but found out that it hangs when trying to boot linux. The board just came out of the box and it has all the default jumper settings. I also tried the SD card I am using on the first board into this problematic 2nd board but the issue is still the same.

Here's the output of the serial console when it hangs:

## Booting kernel from Legacy Image at 80009000 ...
   Image Name:   Arago/2.6.37-psp04.00.00.10/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2362080 Bytes = 2.3 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.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Jun 1 12:18:59 I
ST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168evm
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 1.1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224
Kernel command line: console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprink vram=50M ti816xfb.v
ram=0:16M,1:16M,2:6M ip=off noinitrd
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 206MB = 206MB total
Memory: 203604k/203604k available, 58540k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    lowmem : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0035000   ( 180 kB)
      .text : 0xc0035000 - 0xc0478000   (4364 kB)
      .data : 0xc0478000 - 0xc04b91e0   ( 261 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
NOR: Can't request GPMC CS
registered ti816x_vpss device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
ti816x_pcie: Invoking PCI BIOS...
ti816x_pcie: Setting up Host Controller...
ti816x_pcie: Register base mapped @0xd0820000
ti816x_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19
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
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
sr1_fck HVT rate = 125000000
sr2_fck SVT rate = 125000000
SR NTarget value for HVT 0xa9fd95
SR NTarget value for SVT 0xaab3d5
SmartReflex Driver initialized
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) �� 2001-2006 Red Hat, Inc.
msgmni has been set to 397
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
m25p80 spi1.0: found w25q32, expected w25x32
m25p80 spi1.0: w25q32 (4096 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000042000 : "U-Boot Env"
0x000000042000-0x0000002c2000 : "Kernel"
0x0000002c2000-0x000000400000 : "File System"
omap2-nand driver initializing

This is where it hangs forever. Does anyone knows what is causing the issue? Do we have a defective board in our hands?

Any help is appreciated.

Regards,
Maynard

over 13 years ago

0 Anil over 13 years ago

TI__Expert 6655 points

Hi Maynard,

From the log I can see that you are using"psp04.00.00.10"

Better use the latest PSP release

http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DM816x_04_00/04_00_02_14/index_FDS.html

Regards

AnilKumar

0 Maynard Cabiente over 13 years ago in reply to Anil

Intellectual 460 points

Hi Anil,

How can updating to the latest PSP resolve the issue? The same SDK release (EZSDK 5.01) is working on our first EVM board. I am actually using 5.02 of the EZSDK in my first board. I tried the 5.02 release on the problematic board and it still did not resolve the issue.

As I have done much work on the 5.02 release for our demo, I am hesitant to go to the latest release unless this will solve the issue on the 2nd board. I will update to the latest release once we have completed the demo. I don't have time to waste right now porting all our stuff to the new release that may or may not work on the 2nd board.

Isn't this more of a hardware issue or jumper related settings?

Regards,
Maynard

0 pathfinder over 13 years ago in reply to Maynard Cabiente

TI__Genius 12790 points

EVM#2 does NOT boot with Micron NAND that came with board but WILL boot when NAND from EVM#2 is used, although it boots, it says'No NAND device found". See below. I ran the Spectrum digital NAND test code on both EVMs and they both PASS! We tried booting both EVMs with 3 different SD cards that came in the box - Linux 2.6.37 and it did not work unless we swapped NAND devices.

If moving to a new EZSDK or PSP release fixes the issue, i need to know why.

** EVM#1 - boot attempt w/ NAND that came with it. Gets stuck @ 'omap2-nand driver initializing'

m25p80 spi1.0: w25q32 (4096 Kbytes)
Creating 4 MTD partitions on "spi_flash":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000042000 : "U-Boot Env"
0x000000042000-0x0000002c2000 : "Kernel"
0x0000002c2000-0x000000400000 : "File System"
omap2-nand driver initializing

** EVM#1 - boot attempt w/ NO NAND in the socket - does NOT boot.

** EVM#1 with NAND from EVM#2 - now it boots but says 'No NAND device found'

0 Parth Saxena over 13 years ago in reply to pathfinder

TI__Intellectual 1265 points

Marc,

From what I understand, it does not look like a software (Nand driver) issue to me. Also, I don’t think moving to the next release will help because the same release seems to be working fine on the other board.

I can suggest you to cross check the following switch settings on the board:

1) NAND switch must be turned on

2) NAND buswidth swich should be set appropriately according to 8/16 bit NAND used (for this setting, you can refer to the corresponding Release Notes’ “Read this first” section)

3) Boot mode pins should be set appropriately

Regards,

Parth

0 pathfinder over 13 years ago in reply to Parth Saxena

TI__Genius 12790 points

Both EVMs have identical bootmode settings per the GSG. One EVM is being RMA'd. Otherone still in hand boots but continues to give the 'No NAND device found'. I will let you know what happens. Thanks.

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

EVM#1 (S/N 1108279) – boots but halfway down Linux bootlog – says ‘No NAND device found’.

Creating 4 MTD partitions on "spi_flash":

0x000000000000-0x000000040000 : "U-Boot"

0x000000040000-0x000000042000 : "U-Boot Env"

0x000000042000-0x0000002c2000 : "Kernel"

0x0000002c2000-0x000000400000 : "File System"

omap2-nand driver initializing

No NAND device found.

davinci_mdio davinci_mdio.0: davinci mdio revision 1.6

davinci_mdio davinci_mdio.0: detected phy mask fffffff9

davinci_mdio.0: probed

EVM#2 (S/N 1108260) – does not boot w/ provided SD card. Gets stuck midway down bootlog. Same place except this board doesn’t go past it.

m25p80 spi1.0: found w25q32, expected w25x32

m25p80 spi1.0: w25q32 (4096 Kbytes)