Green led blinking / UDOO won't boot [Official discussion]

Discussion in 'Troubleshooting' started by andcmp, Nov 6, 2013.

  1. andcmp

    andcmp New Member

    Joined:
    May 8, 2013
    Messages:
    161
    Likes Received:
    0
    Hi all!

    This topic gathers users with the following issues:
    - my UDOO shows a green led blinking (power led);
    - my UDOO is unstable and goes in reboot loop;
    - my UDOO won't boot

    If you experienced one of these issue, you probably have a problem with your power adapter, which doesn't deliver enough power to boot the board.

    UDOO works with a voltage range from 6 to 15 Volt with at least 1 Amp, we recommend to use a 12 Volt 2 Amps power adapter.

    If your power adapter delivers less that 1A, is possible that your UDOO won't boot or, if it boots, it will shoot down as soon as you start to use it.
    Sometimes cheap power adapters don't really deliver their declared value, so even a 1A power adapter could not be enough. Again, my suggestion is to get a 12V 2A power adapter.

    http://www.udoo.org/support/
     
  2. DracoLlasa

    DracoLlasa UDOOer

    Joined:
    Oct 15, 2013
    Messages:
    417
    Likes Received:
    3
    Re: Green led blinking / UDOO won't boot [Official discussio

    Just to share, this is a great power supply, and the one i have been using and it is not expensive
    The bonus adapter is wonderful to have around too
    http://www.amazon.com/gp/product/B006NTNGN0/
     
  3. Xykon

    Xykon Member

    Joined:
    Nov 1, 2013
    Messages:
    64
    Likes Received:
    20
    Re: Green led blinking / UDOO won't boot [Official discussio

    Well my udoo doesn't boot (no serial output) with several different mSD cards using several different methods to write the image. My power led is steady.

    Just to be sure I hooked up my udoo to my 0-15V/3A lab power supply and put my DMM into current mode in series with the power supply.

    At first the current stayed at a constant 75mA but is now ranging in the 95-110mA range. Still I don't see any output on the serial console and my monitor (Samsung SyncMaster P2770) stays black (it used to work fine with udoo before it died again).

    I think at least for myself I can safely say that the power supply isn't an issue. I'm just not sure what else I can try at this point...
     
  4. andcmp

    andcmp New Member

    Joined:
    May 8, 2013
    Messages:
    161
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    So your UDOO were working initially?
     
  5. Xykon

    Xykon Member

    Joined:
    Nov 1, 2013
    Messages:
    64
    Likes Received:
    20
    Re: Green led blinking / UDOO won't boot [Official discussio

    Yes it was working fine for the first four days. Then it "died" while I left it running during the day when I was at work. I wanted to do some tests remotely but didn't have a chance as it was a busy day... when I came home the computer monitor was in power save mode and no output on the serial console was seen. Even powering it down for 10 minutes (including disconnecting the serial console cable) didn't get it back to life.

    Now it seems to come to life every 24 hours but only for a few minutes, then it appears to be completely dead again. Is it possible that there is a fuse that has a 24h reset timer?

    What is the exact model number for the quad core cpu? I want to print the data sheet while I am at work but there are three versions:
    Automotive and Infotainment
    Consumer Products
    Industrial Products

    I don't want to print 166 pages just to find out I printed the wrong sheet, even though most of the info I'm interested in at this stage should be identical for all families.
     
  6. mkopack

    mkopack Member

    Joined:
    Jun 14, 2013
    Messages:
    451
    Likes Received:
    21
    Re: Green led blinking / UDOO won't boot [Official discussio

    I saw similar behavior with mine when I accidentally left it on overnight... Try unplugging any USB devices and see if that works, and then plug them back in one at a time (trying a reboot after each). I found that when I tried to boot with everything plugged in, it wouldn't load the rootfs (couldn't see my SATA drive). When I unplugged everything it would fail at a different stage of the uboot process, and then if I plugged in just my keyboard it would come up completely.

    Obviously YMMV... I'm wondering if it's more an issue with the PSU (I'm using the provided one) going flaky than the board, but who knows...
     
  7. Xykon

    Xykon Member

    Joined:
    Nov 1, 2013
    Messages:
    64
    Likes Received:
    20
    Re: Green led blinking / UDOO won't boot [Official discussio

    @mkopack Thanks for the tip. I tried this but my udoo keeps hanging at the same stage every time it actually manages to boot... the last few lines are:

    Code:
    [    2.219438] Bluetooth: Virtual HCI driver ver 1.3
    [    2.224371] Bluetooth: HCI UART driver ver 2.2
    [    2.228818] Bluetooth: HCIATH3K protocol initialized
    [    2.233797] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [    2.239503] usbcore: registered new interface driver btusb
    [    2.245155] sdhci: Secure Digital Host Controller Interface driver
    [    2.251351] sdhci: Copyright(c) Pierre Ossman
    [    2.256022] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
    [    2.263339] mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
    [    2.271379] VPU initialized
    [    2.275143] mxc_asrc registered
    
    I noticed the exact same behavior before when udoo wouldn't load the gui when no keyboard and mouse were connected (though other people say their udoo boots up fine without keyboard and mouse).

    However neither they num lock led goes on on the keyboard when pressing the num lock key (multiple times) nor does the led of the mouse turns on. So either there is a problem with the usb power (I'm about to prepare a cable that allows me to measure the voltages at the usb connector) or the udoo does not get to the point where to usb power gets turned on.

    But most of the time my udoo does nothing and the cpu seems to just reset constantly (see my other thread called udoo doesn't boot).

    I am 100% sure that this is not a power supply issue as I'm using a lab power supply PS1503SB rated for 0-15V and up to 3A. It has displays for power and current and shows my udoo using less than 1A when I'm feeding it 12V.

    [​IMG]
     
  8. Lifeboat_Jim

    Lifeboat_Jim New Member

    Joined:
    Sep 16, 2013
    Messages:
    399
    Likes Received:
    1
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi Xykon

    I suppose you ought to try just the board... no Bluetooth, no WiFi, no USB peripherals at all. Just monitor it from the USB Serial port (the one nearest the corner) from your PC/Mac/Whatever.
     
  9. Xykon

    Xykon Member

    Joined:
    Nov 1, 2013
    Messages:
    64
    Likes Received:
    20
    Re: Green led blinking / UDOO won't boot [Official discussio

    @Lifeboat_Jim,

    When I boot the board without anything attached (including removal of the Wifi module) then I get the same output on the serial console as when I connect keyboard and/or mouse and/or monitor:

    Code:
    
    
    U-Boot 2009.08-svn89 (Oct 29 2013 - 16:13:13)
    
    CPU: Freescale i.MX6 family TO1.2 at 792 MHz
    Thermal sensor with ratio = 185
    Temperature:   32 C, calibration data 0x59451a69
    mx6q pll1: 792MHz
    mx6q pll2: 528MHz
    mx6q pll3: 480MHz
    mx6q pll8: 50MHz
    ipg clock     : 66000000Hz
    ipg per clock : 66000000Hz
    uart clock    : 80000000Hz
    cspi clock    : 60000000Hz
    ahb clock     : 132000000Hz
    axi clock   : 264000000Hz
    emi_slow clock: 132000000Hz
    ddr clock     : 528000000Hz
    usdhc1 clock  : 198000000Hz
    usdhc2 clock  : 198000000Hz
    usdhc3 clock  : 198000000Hz
    usdhc4 clock  : 198000000Hz
    nfc clock     : 24000000Hz
    Board: i.MX6Q-UDOO: unknown-board Board: 0x63012 [POR]
    Boot Device: NOR
    I2C:   ready
    DRAM:   1 GB
    MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
    In:    serial
    Out:   serial
    Err:   serial
    Net:   got MAC address from IIM: 00:c0:08:88:17:f5
    FEC0
    Hit any key to stop autoboot:  0
    mmc2 is current device
    Loading file "/boot/uImage" from mmc device 2:1 (xxc1)
    4120200 bytes read
    ## Booting kernel from Legacy Image at 10800000 ...
       Image Name:   Linux-3.0.35
       Created:      2013-11-04  15:34:22 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    4120136 Bytes =  3.9 MB
       Load Address: 10008000
       Entry Point:  10008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK
    
    Starting kernel ...
    
    [    0.000000] Linux version 3.0.35 (udoo@ubuntu) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #3 SMP PREEMPT Mon Nov 4 16:34:14 CET 2013
    [    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
    [    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [    0.000000] Machine: SECO i.Mx6 UDOO Board
    [    0.000000] Kernel ver: v. 91
    [    0.000000] Ignoring unrecognised tag 0x41000901
    [    0.000000] Memory policy: ECC disabled, Data cache writealloc
    [    0.000000] CPU identified as i.MX6Q, silicon rev 1.2
    [    0.000000] PERCPU: Embedded 7 pages/cpu @8c008000 s5440 r8192 d15040 u32768
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 227328
    [    0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p1 rootwait rw fixrtc rootflags=barrier=1 mem=1024M arm_freq=996 video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32
    [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Memory: 640MB 256MB = 896MB total
    [    0.000000] Memory: 896376k/896376k available, 152200k reserved, 0K highmem
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    [    0.000000]     DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    [    0.000000]     vmalloc : 0xc0800000 - 0xf2000000   ( 792 MB)
    [    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
    [    0.000000]     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    [    0.000000]     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
    [    0.000000]       .init : 0x80008000 - 0x80038000   ( 192 kB)
    [    0.000000]       .text : 0x80038000 - 0x80b04ec4   (11060 kB)
    [    0.000000]       .data : 0x80b06000 - 0x80b65b40   ( 383 kB)
    [    0.000000]        .bss : 0x80b65b64 - 0x80bb44c0   ( 315 kB)
    [    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [    0.000000] Preemptible hierarchical RCU implementation.
    [    0.000000] NR_IRQS:624
    [    0.000000] MXC GPIO hardware
    [    0.000000] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
    [    0.000000] arm_max_freq=1GHz
    [    0.000000] MXC_Early serial console at MMIO 0x21e8000 (options '115200')
    [    0.000000] bootconsole [ttymxc1] enabled
    [    0.000000] Console: colour dummy device 80x30
    [    0.223082] Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
    [    0.311423] pid_max: default: 32768 minimum: 301
    [    0.316302] Mount-cache hash table entries: 512
    [    0.321507] CPU: Testing write buffer coherency: ok
    [    0.326661] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
    [    0.427190] CPU1: Booted secondary processor
    [    0.507187] CPU2: Booted secondary processor
    [    0.587200] CPU3: Booted secondary processor
    [    0.626695] Brought up 4 CPUs
    [    0.642521] SMP: Total of 4 processors activated (6324.22 BogoMIPS).
    [    0.649315] devtmpfs: initialized
    [    0.669485] print_constraints: dummy:
    [    0.673455] NET: Registered protocol family 16
    [    0.682161] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
    [    0.689652] print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
    [    0.697392] print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
    [    0.705068] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
    [    0.712834] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
    [    0.720485] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
    [    0.729499]
    [    0.729505] > UDOO quad
    [    0.733278] > rev C Called set_gpios_direction
    [    0.737953] Test and set gpios directions and values by Gionji feat. Ekirei test
    [    0.769185] Resetting ethernet physical layer.
    [    0.813256] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
    [    0.820091] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
    [    0.827451] hw-breakpoint: maximum watchpoint size is 4 bytes.
    [    0.833338] L310 cache controller enabled
    [    0.837380] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B
    [    0.870914] bio: create slab <bio-0> at 0
    [    0.878190] mxs-dma mxs-dma-apbh: initialized
    [    0.882877] print_constraints: vmmc: 3300 mV
    [    0.887973] vgaarb: loaded
    [    0.891513] SCSI subsystem initialized
    [    0.896377] usbcore: registered new interface driver usbfs
    [    0.902018] usbcore: registered new interface driver hub
    [    0.907522] usbcore: registered new device driver usb
    [    0.912591] Freescale USB OTG Driver loaded, $Revision: 1.55 $
    [    0.936693] imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    [    0.956686] imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    [    0.964577] MIPI CSI2 driver module loaded
    [    0.968915] Advanced Linux Sound Architecture Driver Version 1.0.24.
    [    0.976138] Bluetooth: Core ver 2.16
    [    0.979851] NET: Registered protocol family 31
    [    0.984309] Bluetooth: HCI device and connection manager initialized
    [    0.990693] Bluetooth: HCI socket layer initialized
    [    0.995586] Bluetooth: L2CAP socket layer initialized
    [    1.000728] Bluetooth: SCO socket layer initialized
    [    1.006039] cfg80211: Calling CRDA to update world regulatory domain
    [    1.013465] i2c-core: driver [max17135] using legacy suspend method
    [    1.019765] i2c-core: driver [max17135] using legacy resume method
    [    1.025982] Switching to clocksource mxc_timer1
    [    1.044989] NET: Registered protocol family 2
    [    1.049538] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    [    1.057453] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    [    1.066793] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
    [    1.074537] TCP: Hash tables configured (established 131072 bind 65536)
    [    1.081189] TCP reno registered
    [    1.084349] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [    1.090315] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [    1.097065] NET: Registered protocol family 1
    [    1.101744] RPC: Registered named UNIX socket transport module.
    [    1.107684] RPC: Registered udp transport module.
    [    1.112424] RPC: Registered tcp transport module.
    [    1.117144] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    1.124488] PMU: registered new PMU device of type 0
    [    1.129586] Static Power Management for Freescale i.MX6
    [    1.134850] wait mode is enabled for i.MX6
    [    1.139141] cpaddr = c0880000 suspend_iram_base=c08fc000
    [    1.144574] PM driver module loaded
    [    1.148451] IMX usb wakeup probe
    [    1.152191] add wake up source irq 75
    [    1.159463] IMX usb wakeup probe
    [    1.162987] cpu regulator mode:ldo_enable
    [    1.167258] i.MXC CPU frequency driver
    [    1.197545] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    [    1.204226] msgmni has been set to 1750
    [    1.209604] alg: No test for stdrng (krng)
    [    1.213870] io scheduler noop registered
    [    1.217807] io scheduler deadline registered
    [    1.222187] io scheduler cfq registered (default)
    [    1.227955] MIPI DSI driver module loaded
    [    1.232174] mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
    [    1.238673] mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
    [    1.245596] fbcvt: 1920x1080@60: CVT Name - 2.073M9
    [    1.262803] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines
    [    1.280639] imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
    [    1.313949] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines
    [    1.347343] Console: switching to colour frame buffer device 160x64
    [    1.395491] mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb
    [    1.401905] _regulator_get: get() with no identifier
    [    1.413727] mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb
    [    1.424957] imx-sdma imx-sdma: loaded firmware 1.1
    [    1.434378] imx-sdma imx-sdma: initialized
    [    1.567705] Serial: IMX driver
    [    1.570906] imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
    [    1.577765] imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
    [    1.584264] console [ttymxc1] enabled, bootconsole disabled
    [    1.584264] console [ttymxc1] enabled, bootconsole disabled
    [    1.595804] imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX
    [    1.607909] loop: module loaded
    [    1.611079] request BOSSA_CLK IRQ
    [    1.614396] registering IRQ 419 for BOSSAC Arduino erase/reset operation
    [    1.664770] No sata disk.
    [    1.668652] GPMI NAND driver registered. (IMX)
    [    1.677003] vcan: Virtual CAN interface driver
    [    1.681475] CAN device driver interface
    [    1.685312] flexcan netdevice driver
    [    1.689062] FEC Ethernet Driver
    [    1.694430] fec_enet_mii_bus: probed
    [    1.699152] usbcore: registered new interface driver rt2800usb
    [    1.705007] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    1.711683] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
    [    1.718314] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
    [    1.750599] fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
    [    1.770592] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
    [    1.776843] hub 1-0:1.0: USB hub found
    [    1.780621] hub 1-0:1.0: 1 port detected
    [    1.784720] add wake up source irq 72
    [    1.788420] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
    [    1.795063] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
    [    1.840586] fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
    [    1.870578] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
    [    1.876747] hub 2-0:1.0: USB hub found
    [    1.880511] hub 2-0:1.0: 1 port detected
    [    1.884801] Initializing USB Mass Storage driver...
    [    1.889835] usbcore: registered new interface driver usb-storage
    [    1.895899] USB Mass Storage support registered.
    [    1.900812] usbcore: registered new interface driver usbserial
    [    1.906749] USB Serial support registered for generic
    [    1.911940] usbcore: registered new interface driver usbserial_generic
    [    1.918470] usbserial: USB Serial Driver core
    [    1.922946] USB Serial support registered for debug
    [    1.927948] usbcore: registered new interface driver debug
    [    1.933453] ARC USBOTG Device Controller driver (1 August 2005)
    [    1.940214] mousedev: PS/2 mouse device common for all mice
    [    1.946759] i2c-core: driver [isl29023] using legacy suspend method
    [    1.953044] i2c-core: driver [isl29023] using legacy resume method
    [    1.959904] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
    [    1.966578] i2c /dev entries driver
    [    1.970840] Linux video capture interface: v2.00
    [    1.975832] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
    [    1.983459] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
    [    1.991126] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18
    [    1.998739] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19
    [    2.006378] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20
    [    2.014180] vivi-000: V4L2 device registered as video0
    [    2.019325] Video Technology Magazine Virtual Video Capture Board ver 0.8.0 successfully loaded.
    [    2.028474] i2c-core: driver [mag3110] using legacy suspend method
    [    2.034670] i2c-core: driver [mag3110] using legacy resume method
    [    2.041179] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
    [    2.049279] Bluetooth: Virtual HCI driver ver 1.3
    [    2.054209] Bluetooth: HCI UART driver ver 2.2
    [    2.058656] Bluetooth: HCIATH3K protocol initialized
    [    2.063636] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [    2.069343] usbcore: registered new interface driver btusb
    [    2.074990] sdhci: Secure Digital Host Controller Interface driver
    [    2.081188] sdhci: Copyright(c) Pierre Ossman
    [    2.085846] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
    [    2.093214] mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
    [    2.104419] VPU initialized
    [    2.108198] mxc_asrc registered
    
    I also checked the voltage on the usb ports and I get 5V so there doesn't seem to be a problem with the fuses either...

    I'm now compiling the latest kernel sources to see how that goes....

    UPDATE: I compiled the latest kernel from the git repository but I'm getting the same results as before...
     
  10. Xykon

    Xykon Member

    Joined:
    Nov 1, 2013
    Messages:
    64
    Likes Received:
    20
    Re: Green led blinking / UDOO won't boot [Official discussio

    I created another card with Android and it seems that it is hanging at the same step:

    Code:
    
    U-Boot 2009.08-svn24 (Oct 30 2013 - 08:53:42)
    
    CPU: Freescale i.MX6 family TO1.2 at 792 MHz
    Thermal sensor with ratio = 185
    Temperature:   37 C, calibration data 0x59451a69
    mx6q pll1: 792MHz
    mx6q pll2: 528MHz
    mx6q pll3: 480MHz
    mx6q pll8: 50MHz
    ipg clock     : 66000000Hz
    ipg per clock : 66000000Hz
    uart clock    : 80000000Hz
    cspi clock    : 60000000Hz
    ahb clock     : 132000000Hz
    axi clock   : 264000000Hz
    emi_slow clock: 132000000Hz
    ddr clock     : 528000000Hz
    usdhc1 clock  : 198000000Hz
    usdhc2 clock  : 198000000Hz
    usdhc3 clock  : 198000000Hz
    usdhc4 clock  : 198000000Hz
    nfc clock     : 24000000Hz
    Board: i.MX6Q-UDOO: unknown-board Board: 0x63012 [POR]
    Boot Device: NOR
    I2C:   ready
    DRAM:   1 GB
    MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
    *** Warning - bad CRC or MMC, using default environment
    
    In:    serial
    Out:   serial
    Err:   serial
    Net:   got MAC address from IIM: 00:c0:08:88:17:f5
    FEC0 [PRIME]
    Hit any key to stop autoboot:  0
    kernel   @ 10808000 (4275900)
    ramdisk  @ 11800000 (186957)
    kernel cmdline:
            use uboot command line:
            console=ttymxc1,115200 init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=28M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale mem=1024M
    
    Starting kernel ...
    
    Initializing cgroup subsys cpuset
    Initializing cgroup subsys cpu
    Linux version 3.0.35-svn24 (udoo@ubuntu) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #4 PREEMPT Wed Oct 30 09:16:17 PDT 2013
    CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: i.Mx6 UDOO Board
    Ignoring unrecognised tag 0x41000901
    Memory policy: ECC disabled, Data cache writeback
    CPU identified as i.MX6Q, silicon rev 1.2
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 223232
    Kernel command line: console=ttymxc1,115200 init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=28M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale mem=1024M
    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: 640MB 240MB = 880MB total
    Memory: 879220k/879220k available, 169356k reserved, 491520K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)
        vmalloc : 0xd9800000 - 0xf2000000   ( 392 MB)
        lowmem  : 0xc0000000 - 0xd9000000   ( 400 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .init : 0xc0008000 - 0xc0036000   ( 184 kB)
          .text : 0xc0036000 - 0xc0b46968   (11331 kB)
          .data : 0xc0b48000 - 0xc0b967e0   ( 314 kB)
           .bss : 0xc0b96804 - 0xc0cc3a28   (1205 kB)
    Preemptible hierarchical RCU implementation.
    NR_IRQS:624
    MXC GPIO hardware
    sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
    arm_max_freq=1GHz
    MXC_Early serial console at MMIO 0x21e8000 (options '115200')
    bootconsole [ttymxc1] enabled
    Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
    print_constraints: dummy:
    NET: Registered protocol family 16
    print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
    print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
    print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
    print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
    print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
    print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
    ####Called set_gpios_direction
    failed to get MX6_IO_MICRO: -16
    Resetting ethernet physical layer.
    hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
    hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
    hw-breakpoint: maximum watchpoint size is 4 bytes.
    L310 cache controller enabled
    l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B
    bio: create slab <bio-0> at 0
    print_constraints: vmmc: 3300 mV
    vgaarb: loaded
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    Freescale USB OTG Driver loaded, $Revision: 1.55 $
    imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
    MIPI CSI2 driver module loaded
    Advanced Linux Sound Architecture Driver Version 1.0.24.
    Bluetooth: Core ver 2.16
    NET: Registered protocol family 31
    Bluetooth: HCI device and connection manager initialized
    Bluetooth: HCI socket layer initialized
    Bluetooth: L2CAP socket layer initialized
    Bluetooth: SCO socket layer initialized
    cfg80211: Calling CRDA to update world regulatory domain
    i2c-core: driver [max17135] using legacy suspend method
    i2c-core: driver [max17135] using legacy resume method
    Switching to clocksource mxc_timer1
    NET: Registered protocol family 2
    IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
    TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
    TCP: Hash tables configured (established 65536 bind 65536)
    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 named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    Unpacking initramfs...
    Freeing initrd memory: 180K
    PMU: registered new PMU device of type 0
    Static Power Management for Freescale i.MX6
    wait mode is enabled for i.MX6
    cpaddr = d9880000 suspend_iram_base=d98f0000
    PM driver module loaded
    IMX usb wakeup probe
    add wake up source irq 75
    IMX usb wakeup probe
    cpu regulator mode:ldo_enable
    i.MXC CPU frequency driver
    highmem bounce pool size: 64 pages
    ashmem: initialized
    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    msgmni has been set to 757
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    MIPI DSI driver module loaded
    mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
    mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
    fbcvt: 1920x1080@60: CVT Name - 2.073M9
    imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines
    imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
    mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!
    mxc_sdc_fb mxc_sdc_fb.2: Can't get fb option for mxcfb2!
    imx-sdma imx-sdma: loaded firmware 1.1
    imx-sdma imx-sdma: initialized
    fbcvt: 1920x1080@60: CVT Name - 2.073M9
    Serial: IMX driver
    imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
    imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
    console [ttymxc1] enabled, bootconsole disabled
    console [ttymxc1] enabled, bootconsole disabled
    imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX
    loop: module loaded
    request BOSSA_CLK IRQ
    registering IRQ 419 for BOSSAC Arduino erase/reset operation
    vcan: Virtual CAN interface driver
    CAN device driver interface
    flexcan netdevice driver
    FEC Ethernet Driver
    fec_enet_mii_bus: probed
    PPP generic driver version 2.4.2
    PPP Deflate Compression module registered
    PPP BSD Compression module registered
    PPP MPPE Compression module registered
    NET: Registered protocol family 24
    PPTP driver version 0.8.5
    usbcore: registered new interface driver rt2800usb
    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 75, io base 0x02184000
    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
    add wake up source irq 72
    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 72, io base 0x02184200
    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: 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
    USB Serial support registered for GSM modem (1-port)
    usbcore: registered new interface driver option
    option: v0.7.2:USB Driver for GSM modems
    USB Serial support registered for Qualcomm USB modem
    usbcore: registered new interface driver qcserial
    ARC USBOTG Device Controller driver (1 August 2005)
    android_usb gadget: Mass Storage Function, version: 2009/09/11
    android_usb gadget: Number of LUNs=1
     lun0: LUN: removable file: (no medium)
    Gadget Android: controller 'fsl-usb2-udc' not recognized
    android_usb gadget: android_usb ready
    Suspend udc for OTG auto detect
    fsl-usb2-udc: bind to driver android_usb
    mousedev: PS/2 mouse device common for all mice
    i2c-core: driver [isl29023] using legacy suspend method
    i2c-core: driver [isl29023] using legacy resume method
    using rtc device, snvs_rtc, for alarms
    snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
    i2c /dev entries driver
    Linux video capture interface: v2.00
    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
    i2c-core: driver [mag3110] using legacy suspend method
    i2c-core: driver [mag3110] using legacy resume method
    imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
    Bluetooth: Virtual HCI driver ver 1.3
    Bluetooth: HCI UART driver ver 2.2
    Bluetooth: HCIATH3K protocol initialized
    Bluetooth: Generic Bluetooth USB driver ver 0.6
    usbcore: registered new interface driver btusb
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
    mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
    VPU initialized
    mxc_asrc registered
    
    It also seems as if my udoo does not freeze up like it used to if I keep it running and don't remove the power supply. So at least I could test several things instead of having my udoo become unresponsive after a few minutes.

    I also tried using the Ethernet port for the first time... I connected a cable to a switch but it never showed a link coming up... I was hoping to boot the kernel and rootfs via network but I'm not sure the hardware supports this... maybe the u-boot version supplied doesn't have network support built in?

    Where can I find the u-boot source code and/or configuration files used for this board?

    I also checked the Arduino CPU for the first time, simply uploading an empty sketch... after stopping u-boot autoboot and removing the jumper I was able to upload the sketch so it seems the SAM3 CPU is OK as well.

    Right now I'm running mtest from the u-boot console to see if any memory issues come up.

    Any other ideas of what I could try at this point?
     
  11. huseijn

    huseijn New Member

    Joined:
    Oct 25, 2013
    Messages:
    4
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    PLEASE Udoo ihave the same issue , im getting angry now. nothing works no boot . freeze , yust NOTHING. were can i send this back and get my money back .
     
  12. Lifeboat_Jim

    Lifeboat_Jim New Member

    Joined:
    Sep 16, 2013
    Messages:
    399
    Likes Received:
    1
    Re: Green led blinking / UDOO won't boot [Official discussio

    what issue exactly are you experiencing?

    This thread covers one of three possibilities, although all three are connected with not enough power.

    Are you powering the board with 12v 2A DC?
     
  13. micro

    micro New Member

    Joined:
    Nov 23, 2013
    Messages:
    3
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi everyone, UDOO team,

    I've been silently watching the forum for everything related to the boot problem, as I've got a problem there too. My dual doesn't have a problem at all at the moment, but my quad is pretty unstable. Here are some symptoms (only for the quad):
    * Stable green light, using the supplied 2A, 12V PSU. Same problems with other power supplies.
    * udoo doesn't seem to put anything out on HDMI or serial initially
    * heatsink very slowly warms up
    * after anything between 1 hour and multiple hours, the unit tries to boot up.
    * On android, it goes into a very slow boot loop: I can see the android flicker briefly, before it shuts down for like half an hour or longer, then tries again, then the cycle repeats
    * On linux, same extremely long delay with booting, but at least, once it boots, it doesn't seem to go into a boot loop, but it still randomly reboots (rarely), when browsing, for example.
    * Interestingly: it appears that the unit works fine when it's heated up, the heatsink being just too hot to touch for more than a few seconds. Once I get to start some heavy load on it, even on Android, then it's not rebooting at all anymore, and working very nicely.

    I suspect there's a bad solder joint somewhere, which somehow gets rectified with a bit of heat.

    Does anyone have hints on which power rails on the board I should start checking to further debug? Or is this unit broken?

    I've had this problem since I got the unit, and sent an email to support a week ago, but haven't received any response so far.

    Very happy with the dual so far. This could be an awesome platform, let's hope we can get these bugs sorted.

    I'm using Linux 1.3 and Android 1.1 versions from the download sections, and have tried 3 different sd cards, all the same problem.

    Regards,

    Michael
     
  14. MyUDOOQuestions

    MyUDOOQuestions New Member

    Joined:
    Nov 24, 2013
    Messages:
    5
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    I have the same problem with my Quad and the official UDOO Ubuntu image:

    1. Using supplied 12V 2A power supply.
    2. Green light is steady
    3. Black screen when connected to HDMI screen.
    4. Cannot see anything when connected via terminal and serial port.

    Basically, nothing works.
     
  15. jinu

    jinu New Member

    Joined:
    Nov 6, 2013
    Messages:
    10
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi,
    Im also facing the same issue with quad core. Board was working for few days, we build an image using the source and tried booting with same, but there was some error on boot-loader and it got struck on serial console with a message "USB Mode Suspended". Here after board shows below

    Green light is steady
    Black screen when connected to HDMI screen.
    Cannot see anything when connected via terminal and serial port.

    Using supplied 12V 2A power supply. Is something wrong with board?

    Regards
    Jinu
     
  16. epifanio

    epifanio New Member

    Joined:
    Oct 24, 2013
    Messages:
    4
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    Same symptoms here, i used the device for few hour per day without any problem (udoo quad) i tested several images and everything was working properly.
    To day i received my sata connector to plug the SSD (finally! i was so happy!) and ... after i plugged the sata and the power .. no boot at all. i removed all the cables usb dongle etc .. tried to boot .. nothing in the monitor and "screen" on linux is telling me no such file when i try to debug the device via serial usb.
    I also tried to boot a fresh udoo-quad image but nothing.

    green light fixed on
    power adapter 12V seems ok (same adaptor i was using when the device was working fine)

    Please help! my research is compromised without a working device! :(


    ### EDIT ###

    After one more day, i cam back at home .. i put the device on a piece of foam .. on the heating for half H (i don't know if this really helped)
    maybe it's just the time ... but in any case .. my UDOO is back alive!

    I'm happy!
     
  17. jinu

    jinu New Member

    Joined:
    Nov 6, 2013
    Messages:
    10
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi,
    I got to solve issue, i don't know the what was the issue. Below steps helped me..

    Created a new sd card with downloaded images and it started working. Note that another SD card which was not booting previously, that also started working.

    Jinu
     
  18. micro

    micro New Member

    Joined:
    Nov 23, 2013
    Messages:
    3
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi everyone,

    OK, maybe a small bit of progress tonight. After not hearing from the udoo team, I decided to take the heatsink off. I immediately noticed that the screws holding it down were tightened really hard.

    After taking off the heatsink, the unit booted within 2 minutes, on android, as that was the card I had in there. Trying the same thing a few times, and loosely putting the heatsink back on, the unit now boots up instantaneously, outputting information immediately on the serial port. Heatsink gets very hot very quickly now, rather than over a few hours before booting before.

    I'm now thinking the heatsink could have stressed the board, or components on it too much, creating a bad joint somewhere. Obviously, I'll need a lot more testing (I've only got to this point about half an hour ago, after weeks of trying different power supplies, SD cards, and images!)
    Let's hope it keeps working now.

    Will keep you updated when I find out more, or when I get to confirm more of this behaviour.

    Michael
     
  19. micro

    micro New Member

    Joined:
    Nov 23, 2013
    Messages:
    3
    Likes Received:
    0
    Re: Green led blinking / UDOO won't boot [Official discussio

    One day later, after letting the udoo quad cool down to room temperature, some more findings:
    * with heatsink removed:
    ** udoo boots up after about 3 minutes.
    ** after booting, and then putting the heatsink back, udoo fails to boot for at least 20 minutes (then I gave up waiting)
    ** removed the heat sink again, and the unit started booting again in about 2 minutes.
    (in all situations above, I only loosely placed the heatsink back on, without doing up the screws)

    Once the processor has heated up enough, booting and rebooting happens almost instantaneously (<3 seconds). The longer I let it cool down, the longer it takes to boot or reboot.

    In my last try for the evening, it booted "halfway": unit boots, but stops booting in the middle of the linux boot up sequence. Pressing the reset button doesn't do anything until I remove the heatsink.

    Come on, UDOO, what's happening?
    * How long can or should we run the quad without heatsink?
    * How quickly does a perfectly working board start up the boot sequence?
    * The wifi card seems to heat up too. Is that normal?
    * Is there a chance there's something wrong with the firmware that makes the boot-up process temperature dependent?

    Michael
     
  20. Lifeboat_Jim

    Lifeboat_Jim New Member

    Joined:
    Sep 16, 2013
    Messages:
    399
    Likes Received:
    1
    Re: Green led blinking / UDOO won't boot [Official discussio

    Hi Michael

    Sounds like you have a poorly mounted component(s) from your description.

    It only takes my Quad 45 seconds until Ubuntu desktop is fully loaded (after a proper shutdown).

    WiFi module is normally quite warm in use (see DracoLlasa's thermal test results).

    Firmware... it does keep an eye on temps but not in the way you mean, no impact on startup times unless its over its thermal max.

    Put in a support request for a replacement for a defective board is my advice.
     

Share This Page