my touch device rebooting continuously i think it is in a boot loop could any one please help me

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

my touch device rebooting continuously i think it is in a boot loop could any one please help me

786 Views
subramanikandas
Contributor I

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

Booting from root partition 1

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

 

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

Booting from app partition 1

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

 

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

Booting from kernel partition 1

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

 

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

=== Loading kernel and booting up ===

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

 

NAND read: device 0 offset 0x500000, size 0x800000

 8388608 bytes read: OK

 

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

=== Enabling WatchDog, 64sec timeout ===

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

 

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

=== Booting ===

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

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

   Image Name:   Linux-2.6.35.3-0

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2572068 Bytes =  2.5 MB

   Load Address: 70008000

   Entry Point:  70008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

 

Starting kernel ...

 

Linux version 2.6.35.3-0 (tsdop@precompiled-21.0.0-dbg-02a-KSP858-BR-container-build) (gcc version 5

4.0 (Buildroot 2016.08-00002-gbbebe28-dirty) ) #1 PREEMPT Fri Feb 15 17:57:26 UTC 2019

CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7d

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

Machine: Freescale MX53 LOCO Board

Memory policy: ECC disabled, Data cache writeback

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

Kernel command line: console=ttymxc0,115200n8 consoleblank=0 video=mxcdi0fb:RGB24,KONE_1024_768 back

ight=15000,255,140,0 ubi.mtd=8 ubi.mtd=4 ubi.mtd=5 ubi.mtd=6 ubi.mtd=7 root=ubi1:root rootfstype=ubi

s up

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

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

Memory: 480MB = 480MB total

Memory: 482396k/482396k available, 9124k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xf8e00000 - 0xffe00000   ( 112 MB)

    vmalloc : 0x9e800000 - 0xf4000000   (1368 MB)

    lowmem  : 0x80000000 - 0x9e000000   ( 480 MB)

    modules : 0x7f000000 - 0x80000000   (  16 MB)

      .init : 0x80008000 - 0x80027000   ( 124 kB)

      .text : 0x80027000 - 0x8043c000   (4180 kB)

      .data : 0x80456000 - 0x80498f00   ( 268 kB)

SLUB: Genslabs=9, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

09 RCU-based detection of stalled CPUs is disabled.

09 Verbose stalled-CPUs detection is disabled.

NR_IRQS:368

MXC GPIO hardware

MXC IRQ initialized

MX5: PLL1 rate: 800000000

MX5: AEC 800MHz

MXC_Early serial console at MMIO 0x53fbc000 (options '115200n8')

bootconsole [ttymxc0] enabled

Console: colour dummy device 80x30

Calibrating delay loop... 532.48 BogoMIPS (lpj=2662400)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

regulator: core version 0.5

NET: Registered protocol family 16

i.MX IRAM pool: 128 KB@0x9e840000

IRAM READY

CPU is i.MX53 Revision 2.1

Using SDMA I.API

MXC DMA API initialized

IMX usb wakeup probe

IMX usb wakeup probe

bio: create slab <bio-0> at 0

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

Advanced Linux Sound Architecture Driver Version 1.0.23.

mc34708 Rev 2.4 FinVer 0 detected

PMIC MC34708 ID:0x14

regulator: SW1: 650 <--> 1437 mV at 1250 mV

regulator: SW1B: 650 <--> 1437 mV at 1100 mV

regulator: SW2: 650 <--> 1437 mV at 1300 mV

regulator: SW3: 650 <--> 1425 mV at 1200 mV

regulator: SW4A: 1200 <--> 3300 mV at 1500 mV

regulator: SW4B: 1200 <--> 3300 mV at 1500 mV

regulator: SW5: 1200 <--> 1975 mV at 1800 mV

regulator: SWBST:

regulator: VPLL: 1200 <--> 1800 mV at 1800 mV

regulator: VREFDDR:

regulator: VDAC: 2500 <--> 2775 mV at 2775 mV

regulator: VUSB:

regulator: VUSB2: 2500 <--> 3000 mV at 2500 mV

regulator: VGEN1: 1200 <--> 1550 mV at 1300 mV

regulator: VGEN2: 2500 <--> 3300 mV at 2500 mV

pmic 0-0008: Loaded

Switching to clocksource mxc_timer1

NET: Registered protocol family 2

IP route cache hash table entries: 4096 (order: 2, 16384 bytes)

TCP established hash table entries: 16384 (order: 5, 131072 bytes)

TCP bind hash table entries: 16384 (order: 4, 65536 bytes)

TCP: Hash tables configured (established 16384 bind 16384)

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.

LPMode driver module loaded

Static Power Management for Freescale i.MX5

PM driver module loaded

sdram autogating driver module loaded

Bus freq driver module loaded

DI0 is primary

mxc_dvfs_core_probe

DVFS driver module loaded

i.MXC CPU frequency driver

DVFS PER driver module loaded

JFFS2 version 2.2. (NAND) c2 a9  2001-2006 Red Hat, Inc.

msgmni has been set to 942

alg: No test for stdrng (krng)

cryptodev: driver loaded.

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

pwm-backlight pwm-backlight.0: PWM backlight frequency set to 15000Hz

pwm-backlight pwm-backlight.0: off duty cycle 255

pwm-backlight pwm-backlight.0: middle brightness duty cycle 140

pwm-backlight pwm-backlight.0: full brightness duty cycle 0

regulator: get() with no identifier

mxc_ldb mxc_ldb: default di0 single mode

IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

Console: switching to colour frame buffer device 128x48

Serial: MXC Internal UART driver

mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX

console [ttymxc0] enabled, bootconsole disabled

console [ttymxc0] enabled, bootconsole disabled

mxcintuart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a Freescale i.MX

mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale i.MX

mxcintuart.3: ttymxc3 at MMIO 0x53ff0000 (irq = 13) is a Freescale i.MX

mxcintuart.4: ttymxc4 at MMIO 0x63f90000 (irq = 86) is a Freescale i.MX

loop: module loaded

at24 2-0050: 65536 byte 24c64 EEPROM (writable)

MXC MTD nand Driver 3.0

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

RedBoot partition parsing not available

Creating 9 MTD partitions on "NAND 1GiB 3,3V 8-bit":

0x000000000000-0x000000400000 : "bootloader"

0x000000400000-0x000000500000 : "bootscript"

0x000000500000-0x000000d00000 : "kernel1"

0x000000d00000-0x000001500000 : "kernel2"

0x000001500000-0x000014100000 : "root1"

0x000014100000-0x000026d00000 : "root2"

0x000026d00000-0x00002ad00000 : "app1"

0x00002ad00000-0x00002ed00000 : "app2"

0x00002ed00000-0x000040000000 : "data"

UBI: attaching mtd8 to ubi0

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: attached mtd8 to ubi0

UBI: MTD device name:            "data"

UBI: MTD device size:            275 MiB

UBI: number of good PEBs:        2196

UBI: number of bad PEBs:         4

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 2196

UBI: number of PEBs reserved for bad PEB handling: 21

UBI: max/mean erase counter: 13/5

UBI: image sequence number: 690230599

UBI: background thread "ubi_bgt0d" started, PID 1056

UBI: attaching mtd4 to ubi1

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: attached mtd4 to ubi1

UBI: MTD device name:            "root1"

UBI: MTD device size:            300 MiB

UBI: number of good PEBs:        2400

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 2400

UBI: number of PEBs reserved for bad PEB handling: 24

UBI: max/mean erase counter: 19/18

UBI: image sequence number: 1760829427

UBI: background thread "ubi_bgt1d" started, PID 1059

UBI: attaching mtd5 to ubi2

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: attached mtd5 to ubi2

UBI: MTD device name:            "root2"

UBI: MTD device size:            300 MiB

UBI: number of good PEBs:        2400

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 2400

UBI: number of PEBs reserved for bad PEB handling: 24

UBI: max/mean erase counter: 18/17

UBI: image sequence number: 793385032

UBI: background thread "ubi_bgt2d" started, PID 1062

UBI: attaching mtd6 to ubi3

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: attached mtd6 to ubi3

UBI: MTD device name:            "app1"

UBI: MTD device size:            64 MiB

UBI: number of good PEBs:        512

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 512

UBI: number of PEBs reserved for bad PEB handling: 5

UBI: max/mean erase counter: 4/3

UBI: image sequence number: 631428060

UBI: background thread "ubi_bgt3d" started, PID 1065

UBI: attaching mtd7 to ubi4

UBI: physical eraseblock size:   131072 bytes (128 KiB)

UBI: logical eraseblock size:    129024 bytes

UBI: smallest flash I/O unit:    2048

UBI: sub-page size:              512

UBI: VID header offset:          512 (aligned 512)

UBI: data offset:                2048

UBI: attached mtd7 to ubi4

UBI: MTD device name:            "app2"

UBI: MTD device size:            64 MiB

UBI: number of good PEBs:        512

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 512

UBI: number of PEBs reserved for bad PEB handling: 5

UBI: max/mean erase counter: 1/0

UBI: image sequence number: 519897797

UBI: background thread "ubi_bgt4d" started, PID 1068

FEC Ethernet Driver

fec_enet_mii_bus: probed

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200

usb 1-1: new high speed USB device using fsl-ehci and address 2

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

usbcore: registered new interface driver cdc_acm

cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

usbserial: USB Serial Driver core

MXC keypad loaded

input: mxckpd as /devices/virtual/input/input0

scsi0 : usb-storage 1-1:1.0

egalax_ts 2-0004: egalax_ts: failed to read firmware version                 

egalax_ts: probe of 2-0004 failed with error -5

atmel_mxt_ts 2-004a: Error -19 getting vdd regulator

atmel_mxt_ts 2-004a: Family: 164 Variant: 11 Firmware V1.2.AA Objects: 41

atmel_mxt_ts 2-004a: T100 Touchscreen size X1023Y767

atmel_mxt_ts 2-004a: Invalid object type T107

input: atmel_mxt_ts T100 touchscreen as /devices/platform/imx-i2c.2/i2c-2/2-004a/input/input1

i2c /dev entries driver

Linux video capture interface: v2.00

mxc_v4l2_output mxc_v4l2_output.0: Registered device video0

gspca: main v2.9.0 registered

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v0.1.0)

Driver for 1-wire Dallas network protocol.

1-wire driver for the DS2438 smart battery monitor

MXC WatchDog Driver 2.0

MXC Watchdog # 0 Timer: initial timeout 60 sec

cpuidle: using governor ladder

cpuidle: using governor menu

PMIC ADC start probe

VPU initialized

mxc_asrc registered

gpu mmu enabled

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

No device for DAI imx-ssi-1-0

No device for DAI imx-ssi-1-1

No device for DAI imx-ssi-2-0

No device for DAI imx-ssi-2-1

DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=0 buf->addr=f8016000 buf->area=9e856000 size=

4576

asoc: tlv320dac3100 <-> imx-ssi-2-0 mapping ok

Control name 'Beep generator Volume Control(0 = -61 dbdB, 63 = 2 dB)' truncated to 'Beep generator V

lume Control(0 = -61 dbdB,'

Control name 'SP Class - D driver Volume(0 = 6 dB, 4 = 24 dB)' truncated to 'SP Class - D driver Vol

me(0 = 6 dB, 4 = 24'

Control name 'HP Analog Gain Volume(0 = 0 dB, 127 = -78.3 dB)' truncated to 'HP Analog Gain Volume(0

= 0 dB, 127 = -78.3'

Control name 'SP Analog Gain Volume(0 = 0 dB, 127 = -78.3 dB)' truncated to 'SP Analog Gain Volume(0

= 0 dB, 127 = -78.3'

Control name 'Right Output Mixer DAC_R To Right Mixer Amp switch' truncated to 'Right Output Mixer D

C_R To Right Mixer Amp'

Control name 'Right Output Mixer DAC_R To HPR Driver switch' truncated to 'Right Output Mixer DAC_R

o HPR Driver swit'

Control name 'Left Output Mixer DAC_L To Left Mixer Amp switch' truncated to 'Left Output Mixer DAC_

 To Left Mixer Amp s'

Control name 'Left Output Mixer DAC_L To HPL Driver switch' truncated to 'Left Output Mixer DAC_L To

HPL Driver switc'

ALSA device list:

  #0: imx-3stack (TLV320DAC3100)

TCP cubic registered

NET: Registered protocol family 17

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2

UBIFS: recovery needed

UBIFS: recovery completed

UBIFS: mounted UBI device 1, volume 0, name "root"

UBIFS: file system size:   304496640 bytes (297360 KiB, 290 MiB, 2360 LEBs)

UBIFS: journal size:       15224832 bytes (14868 KiB, 14 MiB, 118 LEBs)

UBIFS: media format:       w4/r0 (latest is w4/r0)

UBIFS: default compressor: lzo

UBIFS: reserved for root:  4952683 bytes (4836 KiB)

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

devtmpfs: mounted

Freeing init memory: 124K

init: upstart-dbus-bridge main process (1178) terminated with status 1

init: upstart-dbus-bridge main process ended, respawning

Starting logging: OK

scsi 0:0:0:0: Direct-Access     JetFlash Transcend 4GB    8.07 PQ: 0 ANSI: 4

sd 0:0:0:0: [sda] 7864320 512-byte logical blocks: (4.02 GB/3.75 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Assuming drive cache: write through

Populating /dev using udev: sd 0:0:0:0: [sda] Assuming drive cache: write through

 sda: sda1

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] Attached SCSI removable disk

UBIFS: recovery needed

UBIFS: recovery completed

UBIFS: mounted UBI device 0, volume 0, name "data"

UBIFS: file system size:   278562816 bytes (272034 KiB, 265 MiB, 2159 LEBs)

UBIFS: journal size:       13934592 bytes (13608 KiB, 13 MiB, 108 LEBs)

UBIFS: media format:       w4/r0 (latest is w4/r0)

UBIFS: default compressor: lzo

UBIFS: reserved for root:  4952683 bytes (4836 KiB)

<30>udevd[1197]: starting version 3.2.5

<27>udevd[1197]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it fro

 /etc/udev/rules.d/usb.rules:1

<30>udevd[1204]: starting eudev-3.2.5                                             

Checking partition consistency

done

Initializing random number generator... done.

Starting system message bus: done

Starting rpcbind: OK

Starting network: eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)

udhcpc: started, v1.27.2

udhcpc: sending discover

PHY: 0:00 - Link is Up - 100/Full

udhcpc: sending discover

udhcpc: sending select for 192.168.80.1

udhcpc: lease of 192.168.80.1 obtained, lease time 1601

/usr/share/udhcpc/default.script: Adding NTP server 192.168.66.11

restart: Unknown instance:

OK

Starting nginx...

Starting sshd: OK

i don't know what is the problem here i'm using MCIMX537CVV8C  the Touch scree is rebooting continuously. Could any one please help

Tags (2)
0 Kudos
1 Reply

613 Views
igorpadykov
NXP Employee
NXP Employee

Hi Subramani

for i.MX53 touchscreen one can look at below threads

and use Mfg Tool for reflashing image

MX53 MC34708 touchscreen 

https://community.nxp.com/docs/DOC-1302 

i.MX Manufacturing Toolkit

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos