Good old autocorrect strikes again!.. yes Newbies, not bewbies... (although it IS breast cancer awareness month.... )
Of course the problem could be several things, but yes, this sounds very similar to the issues with the Raspberry Pi HDMI. On one of my monitors HDMI would work fine, but on another one I had to add "hdmi_force_hotplug=1" to the config.txt configuration file to assert the hotplug signal in order to get it to work. Many other users have also came across this issue and fix, as well as other fixes by adding various parameters to the config file as noted below: Here are the more common HDMI related parameters for the Pi: http://elinux.org/R-Pi_Troubleshooting# ... put_at_all Here is the full list of all available parameters: http://elinux.org/RPiconfig
Right, the question is, are there similar types of tweaks that can be made on the Udoo to do the same sorts of adjustments to get things working for folks? In fact, I saw this very sort of problem happen to Eben Upton during his presentation at NYC Maker Faire this year... He was trying to demo the new stuff they've done for desktop acceleration and the signal to the projector wasn't working right so he had to bail on it.
I'm up and running now. Long story short, when I recreated the quad ubuntu image from Windows it worked (initially I had made multiple attempts from my Mac Book to no avail). My familiarity with the OSX tools for partitioning/formatting/imaging drives is low but I wasn't able to get a working image by following the Mac instructions given in the tutorial. I went through the process of debugging via the microusb port. The FAQ on boot issues and the appendix of the getting started guide http://www.udoo.org/faq-items/why-my-udoo-wont-boot/ were very helpful but there were a lot of details I had to filter through to get things working. Here's a short recap of my problem/solution in case it's helpful for anyone else: 1. Created image on microUSB following Mac instructions (repeated for Quad Ubuntu and Quad Android with no reported errors) but no HDMI output when powering up the UDOO and waiting several minutes (note that when working properly it takes around a minute for anything to appear on the HDMI output). 2. Installed Tera Term freeware tool for Windows http://logmett.com/index.php?/download/tera-term-479-freeware.html 3. Installed Windows drivers for the serial/USB bridge http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx 4. Plugged in micro USB cable (borrowed from my Kindle - thought I was going to have to order one ) to powered down UDOO, started TeraTerm, selected serial port (mine appeared as COM7: Silicon Labs CP210X) and changed the baud rate to 115200 (all other default port settings matched appendix instructions). 5. Powered on UDOO with 12V adapter. Still nothing from HDMI output or output to Tera Term windows. After some careful re-reading of the Getting started guide, it says if you still don't see output to COM port from debug console then your image is bad. 6. At this point, I decided to try creating the micoSD image from Windows instead of OSX. I plugged in my card reader with the microSD and used Windows Disk Management to format the 8GB card as FAT32 and followed the rest of the image creation instructions here: http://www.udoo.org/getting-started/creating-a-bootable-micro-sd-card-from-image/ 7. Writing the image took a couple hours. Plugged the microSD back into the UDOO, reconnected the debug port using Tera Term (note: that the factory default state had Jumper 18 already installed so I didn't need to swap any jumper settings to console debug), and plugged in the 12V power. 8. Immediately, I had console output and after 30 seconds or so a login prompt. After about 1 minute, the HDMI output came on and Ubuntu was ready to go. Now I'm ready to play with the Arduino.
Sorry - I just saw your reply, I need to turn on notifications or something... Anyways - I download the U-boot binary for the Quad here: http://udoo.org/download/files/UDOO_Unico/u-Boot_Quad/u-boot-q.bin These are Linux instructions: Insert SD card into your host; be careful it doesn't automount, if it does, unmount the mounted partitions. Use dmesg to verify a card has been inserted, and note where the device enumerates, in my case, /dev/sde: Code: [593177.632226] sd 10:0:0:0: [sde] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [593177.633985] sd 10:0:0:0: [sde] No Caching mode page present [593177.633998] sd 10:0:0:0: [sde] Assuming drive cache: write through [593177.636605] sd 10:0:0:0: [sde] No Caching mode page present [593177.636618] sd 10:0:0:0: [sde] Assuming drive cache: write through [593177.639097] sde: sde1 sde2 Next you can dd the binary to the card: $ sudo dd if=/path/to/u-boot-q.bin of=/dev/sde bs=512 seek=2 skip=2; sync This should overwrite the U-boot present - I've not tested with the Dual, as I don't have one, but I expect this would be the same process. I *think* I experienced the same issue with the Yocto build - but I will flash and attempt to boot test and validate.
Re: Booting Udoo? HDMI monitor compatibility When booting Ubuntu, I have black screen. It doesn't help to wait. I am able to connect to Udoo with ssh over ethernet connection. Also, I can connect with USB/serial cable. Only HDMI output does not work with my ASUS monitor. Raspberry Pi works with this monitor in 1080p (using same HDMI cable). Udoo works with HDMI on my Sharp TV (but has screen sizing issues, similar to other devices connected to same TV). So, it seems there is a mismatch between Udoo and my HDMI monitor (and monitor works with other devices). When I switch inputs on monitor, Udoo recognizes the monitor being switched on/off (see end of dmesg file) I am attaching a copy of my dmesg file: gn=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.222732] Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280) [ 0.311067] pid_max: default: 32768 minimum: 301 [ 0.315949] Mount-cache hash table entries: 512 [ 0.321165] CPU: Testing write buffer coherency: ok [ 0.326313] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.426836] CPU1: Booted secondary processor [ 0.506840] CPU2: Booted secondary processor [ 0.586846] CPU3: Booted secondary processor [ 0.626348] Brought up 4 CPUs [ 0.642173] SMP: Total of 4 processors activated (6324.22 BogoMIPS). [ 0.665759] print_constraints: dummy: [ 0.669750] NET: Registered protocol family 16 [ 0.678485] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal [ 0.685934] print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal [ 0.693677] print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal [ 0.701367] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal [ 0.709131] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal [ 0.716783] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal [ 0.725771] [ 0.725777] > UDOO quad [ 0.729569] > rev C Called set_gpios_direction [ 0.734228] Test and set gpios directions and values by Gionji feat. Ekirei test [ 0.765268] Resetting ethernet physical layer. [ 0.812877] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers. [ 0.819713] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step. [ 0.827072] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.832956] L310 cache controller enabled [ 0.836998] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B [ 0.870537] bio: create slab <bio-0> at 0 [ 0.877834] mxs-dma mxs-dma-apbh: initialized [ 0.882519] print_constraints: vmmc: 3300 mV [ 0.887602] vgaarb: loaded [ 0.891151] SCSI subsystem initialized [ 0.895276] libata version 3.00 loaded. [ 0.896017] usbcore: registered new interface driver usbfs [ 0.901669] usbcore: registered new interface driver hub [ 0.907164] usbcore: registered new device driver usb [ 0.912234] Freescale USB OTG Driver loaded, $Revision: 1.55 $ [ 0.936344] imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) [ 0.956344] imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) [ 0.964232] MIPI CSI2 driver module loaded [ 0.968573] Advanced Linux Sound Architecture Driver Version 1.0.24. [ 0.975784] Bluetooth: Core ver 2.16 [ 0.979501] NET: Registered protocol family 31 [ 0.983959] Bluetooth: HCI device and connection manager initialized [ 0.990343] Bluetooth: HCI socket layer initialized [ 0.995236] Bluetooth: L2CAP socket layer initialized [ 1.000386] Bluetooth: SCO socket layer initialized [ 1.005708] cfg80211: Calling CRDA to update world regulatory domain [ 1.013130] i2c-core: driver [max17135] using legacy suspend method [ 1.019429] i2c-core: driver [max17135] using legacy resume method [ 1.025645] Switching to clocksource mxc_timer1 [ 1.042677] NET: Registered protocol family 2 [ 1.047243] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) [ 1.055213] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) [ 1.064546] TCP bind hash table entries: 65536 (order: 7, 786432 bytes) [ 1.072282] TCP: Hash tables configured (established 131072 bind 65536) [ 1.078918] TCP reno registered [ 1.082091] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 1.088057] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 1.094814] NET: Registered protocol family 1 [ 1.099470] RPC: Registered named UNIX socket transport module. [ 1.105430] RPC: Registered udp transport module. [ 1.110150] RPC: Registered tcp transport module. [ 1.114879] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.121353] PCI: CLS 0 bytes, default 32 [ 1.122191] PMU: registered new PMU device of type 0 [ 1.127300] Static Power Management for Freescale i.MX6 [ 1.132562] wait mode is enabled for i.MX6 [ 1.136848] cpaddr = b0880000 suspend_iram_base=b08fc000 [ 1.142277] PM driver module loaded [ 1.146181] IMX usb wakeup probe [ 1.149500] the wakeup pdata is 0xa416de40 [ 1.149871] add wake up source irq 75 [ 1.157173] IMX usb wakeup probe [ 1.160505] the wakeup pdata is 0xa416d980 [ 1.160693] cpu regulator mode:ldo_enable [ 1.164967] i.MXC CPU frequency driver [ 1.192906] JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc. [ 1.199566] msgmni has been set to 1242 [ 1.204975] alg: No test for stdrng (krng) [ 1.209233] io scheduler noop registered [ 1.213190] io scheduler deadline registered [ 1.217556] io scheduler cfq registered (default) [ 1.223356] MIPI DSI driver module loaded [ 1.227566] mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi [ 1.234085] mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1 [ 1.241010] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 1.252561] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines [ 1.270300] imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) [ 1.303611] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines [ 1.329049] Console: switching to colour frame buffer device 160x64 [ 1.377667] mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb [ 1.384081] _regulator_get: get() with no identifier [ 1.397485] mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb [ 1.407809] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 1.413962] imx-sdma imx-sdma: loaded firmware 1.1 [ 1.418059] imx-sdma imx-sdma: initialized [ 1.598060] Serial: IMX driver [ 1.598171] imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX [ 1.598536] imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX [ 1.683016] console [ttymxc1] enabled, bootconsole disabled [ 1.694731] imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX [ 1.706507] loop: module loaded [ 1.709658] request BOSSA_CLK IRQ [ 1.712985] registering IRQ 419 for BOSSAC Arduino erase/reset operation [ 1.763316] No sata disk. [ 1.767190] GPMI NAND driver registered. (IMX) [ 1.772573] vcan: Virtual CAN interface driver [ 1.777022] CAN device driver interface [ 1.780869] flexcan netdevice driver [ 1.784593] FEC Ethernet Driver [ 1.789934] fec_enet_mii_bus: probed [ 1.794716] usbcore: registered new interface driver rt2800usb [ 1.800570] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.807226] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller [ 1.813874] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 [ 1.850254] fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000 [ 1.870245] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 [ 1.876432] hub 1-0:1.0: USB hub found [ 1.880195] hub 1-0:1.0: 1 port detected [ 1.884315] add wake up source irq 72 [ 1.888017] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller [ 1.894688] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 [ 1.930255] fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200 [ 1.950244] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 [ 1.956383] hub 2-0:1.0: USB hub found [ 1.960146] hub 2-0:1.0: 1 port detected [ 1.964438] Initializing USB Mass Storage driver... [ 1.969472] usbcore: registered new interface driver usb-storage [ 1.975496] USB Mass Storage support registered. [ 1.980404] usbcore: registered new interface driver usbserial [ 1.986350] USB Serial support registered for generic [ 1.991540] usbcore: registered new interface driver usbserial_generic [ 1.998070] usbserial: USB Serial Driver core [ 2.002542] USB Serial support registered for debug [ 2.007540] usbcore: registered new interface driver debug [ 2.013042] ARC USBOTG Device Controller driver (1 August 2005) [ 2.019706] mousedev: PS/2 mouse device common for all mice [ 2.026295] i2c-core: driver [isl29023] using legacy suspend method [ 2.032580] i2c-core: driver [isl29023] using legacy resume method [ 2.039424] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0 [ 2.046107] i2c /dev entries driver [ 2.050359] Linux video capture interface: v2.00 [ 2.055327] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16 [ 2.062949] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17 [ 2.070566] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18 [ 2.078184] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19 [ 2.085794] mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20 [ 2.093577] vivi-000: V4L2 device registered as video0 [ 2.098720] Video Technology Magazine Virtual Video Capture Board ver 0.8.0 successfully loaded. [ 2.107889] i2c-core: driver [mag3110] using legacy suspend method [ 2.114086] i2c-core: driver [mag3110] using legacy resume method [ 2.120582] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1) [ 2.128694] Bluetooth: Virtual HCI driver ver 1.3 [ 2.133636] Bluetooth: HCI UART driver ver 2.2 [ 2.138083] Bluetooth: HCIATH3K protocol initialized [ 2.143063] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 2.148771] usbcore: registered new interface driver btusb [ 2.154426] sdhci: Secure Digital Host Controller Interface driver [ 2.160623] sdhci: Copyright(c) Pierre Ossman [ 2.165291] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA [ 2.172624] mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed [ 2.183859] VPU initialized [ 2.187651] mxc_asrc registered [ 2.207910] Thermal calibration data is 0x57850369 [ 2.212732] Thermal sensor with ratio = 181 [ 2.230273] Anatop Thermal registered as thermal_zone0 [ 2.235598] anatop_thermal_probe: default cooling device is cpufreq! [ 2.251767] usbcore: registered new interface driver usbhid [ 2.257342] usbhid: USB HID core driver [ 2.261604] usbcore: registered new interface driver snd-usb-audio [ 2.268329] mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio [ 2.273799] Cirrus Logic CS42888 ALSA SoC Codec Driver [ 2.279039] i2c-core: driver [cs42888] using legacy suspend method [ 2.280264] usb 2-1: new high speed USB device number 2 using fsl-ehci [ 2.291763] i2c-core: driver [cs42888] using legacy resume method [ 2.346972] mmc0: new high speed SDHC card at address aaaa [ 2.352863] mmcblk0: mmc0:aaaa SU08G 7.40 GiB [ 2.358971] mmcblk0: p1 [ 2.380379] audio_codec_ac97_cold_reset [ 2.461588] hub 2-1:1.0: USB hub found [ 2.462822] Found Audio codec AC97 vt1613, [ID = 5649 - 4123] [ 2.471285] hub 2-1:1.0: 4 ports detected [ 2.481053] asoc: vt1613 <-> imx-ssi.0 mapping ok [ 2.487238] imx_3stack asoc driver [ 2.492212] asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok [ 2.498810] ALSA device list: [ 2.501801] #0: vt1613-audio [ 2.504856] #1: imx-hdmi-soc [ 2.508118] NET: Registered protocol family 26 [ 2.513168] TCP cubic registered [ 2.516400] NET: Registered protocol family 17 [ 2.520874] can: controller area network core (rev 20090105 abi 8) [ 2.527129] NET: Registered protocol family 29 [ 2.531585] can: raw protocol (rev 20090105) [ 2.535857] can: broadcast manager protocol (rev 20090105 t) [ 2.541600] Bluetooth: RFCOMM TTY layer initialized [ 2.546486] Bluetooth: RFCOMM socket layer initialized [ 2.551662] Bluetooth: RFCOMM ver 1.11 [ 2.555415] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.560736] Bluetooth: BNEP filters: protocol multicast [ 2.565963] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.572034] lib80211: common routines for IEEE802.11 drivers [ 2.577697] lib80211_crypt: registered algorithm 'NULL' [ 2.577704] lib80211_crypt: registered algorithm 'WEP' [ 2.577711] lib80211_crypt: registered algorithm 'CCMP' [ 2.577716] lib80211_crypt: registered algorithm 'TKIP' [ 2.577731] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 2.585784] Bus freq driver module loaded [ 2.589801] Bus freq driver Enabled [ 2.595058] mxc_dvfs_core_probe [ 2.598403] DVFS driver module loaded [ 2.603595] snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:01:01 UTC (61) [ 2.760476] usb 2-1.2: new full speed USB device number 3 using fsl-ehci [ 2.800288] USB Host suspend begins [ 2.800297] will suspend roothub and its children [ 2.800318] ehci_fsl_bus_suspend begins, DR [ 2.801110] ehci_fsl_bus_suspend ends, DR [ 2.801124] host suspend ends [ 2.891972] hub 2-1.2:1.0: USB hub found [ 2.896040] hub 2-1.2:1.0: 4 ports detected [ 2.980434] usb 2-1.3: new high speed USB device number 4 using fsl-ehci [ 3.145374] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 3.147059] Registered led device: rt2800usb-phy0::radio [ 3.147203] Registered led device: rt2800usb-phy0::assoc [ 3.147330] Registered led device: rt2800usb-phy0::quality [ 3.220415] usb 2-1.2.1: new low speed USB device number 5 using fsl-ehci [ 3.333266] kjournald starting. Commit interval 5 seconds [ 3.338765] EXT3-fs (mmcblk0p1): using internal journal [ 3.344003] EXT3-fs (mmcblk0p1): recovery complete [ 3.350931] EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode [ 3.358013] VFS: Mounted root (ext3 filesystem) on device 179:1. [ 3.364085] Freeing init memory: 192K [ 3.395503] input: CHICONY USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.0/input/input0 [ 3.407189] generic-usb 0003:04F2:0833.0001: input,hidraw0: USB HID v1.11 Keyboard [CHICONY USB Keyboard] on usb-fsl-ehci0 [ 3.452546] input: CHICONY USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.1/input/input1 [ 3.464240] generic-usb 0003:04F2:0833.0002: input,hidraw1: USB HID v1.11 Device [CHICONY USB Keyboard] on usb-fsl-ehci.11 [ 16.891674] udevd[5056]: renamed network interface wlan0 to wlan6 [ 17.585543] eth2: Freescale FEC PHY driver [Generic PHY] (mii_bushy_addr=1:06, irq=-1) [ 17.585580] Activating ethernet physical layer Micrel KSZ9031 Gigabit PHY. [ 17.736962] init: failsafe main process (5520) killed by TERM signal [ 17.782688] init: gdm main process (5621) killed by TERM signal [ 18.703242] [drm] Initialized drm 1.1.0 20060810 [ 18.718217] [drm] Initialized vivante 1.0.0 20120216 on minor 0 [ 21.590598] PHY: 1:06 - Link is Up - 1000/Full [ 28.275255] ehci_fsl_bus_resume begins, DR [ 28.735836] warning: process `colord' used the deprecated sysctl system call with 8.1.2. [ 29.452843] mxc_hdmi mxc_hdmi: same edid [ 52.782241] mxc_hdmi mxc_hdmi: same edid [ 69.964030] mxc_hdmi mxc_hdmi: same edid [ 132.203917] mxc_hdmi mxc_hdmi: same edid [ 166.553846] mxc_hdmi mxc_hdmi: same edid
I had the same issues as PSJ. After reading his post above I went and redid the SD card. The first time I made it on my MacBook and it took hours for it to write to the SD card using DD. This time I used the Windows instruction and win32imager. It only took 20 minutes to write the image to the SD card. I though even if their was something wrong with the SD card, I would still see some kind of output on the Serial Connection or on the HDMI out.
Still cant get Android running. I took the advice to buy an SD card reader and i bought a Kingston 8GB Class 4 micro SD with an adapter to fit the reader. The card was instantly recognized by the O/W (Win7) and auto assigned drive=G:. I downloaded and unzipped the .img file for my dual. I downloaded, unzipped and ran WIN32 Disk Imager. I got past the death warning and received the following error: Write Error: Not enough space on disk: Size 15508990 sectors. Available: 15278080 sectors Sector size: 512. The drive (SDCARD) shows up as empty and formatted with FAT32. Its showing 32,768 Used space and 7,813,955,584 bytes 7.27 GB as Free space. The properties pie shows 100% free space. I should mention that the unzipped image file is 7,754,495 KB. Any help here would be greatly appreciated.
Solardave1, I have the same issue with my Kingston 8GB - it seems all 8GB cards are not created alike? I think Udoo support needs to make a slightly smaller image for us.
Ubuntu's image files have already been downsized to match even "smaller" 8GB micro SD card, today we should be able to upload downsized file images for Android too.
Thank you for responding quickly to the issue. Looking forward to trying Android with your product. Glenn
I wasn't able to see anything on my HDMI monitor booting off of either the Android or Linux SD card that were provided, with my UDOO Quad. Yes, I pushed the reset button! Then I set up the serial debug on Mac OS X - again nothing on either SD card. I then downloaded and reimaged the provided Android card using Mac OS X. Again nothing on the serial debug. I tried creating a Raspberry Pi image on the Android card - it worked fine. So it doesn't look like the media itself is an issue. What is my next step?
I used a class 4 MicroSD card to boot the linux image. There is no indication anything is going on during the boot which takes 2 minutes and 35 seconds. Now that I know, i have no problem waiting. For future configurations it might be good to show some boot progress for eager newbies like myself. Just a suggestion. Glenn
Will someone post when the downsized Android image is uploaded. Also, my Linux boots up in 30 seconds tops.
That is good to know as my quad core is definitely taking 2.5 minutes. I only have a mouse plugged in no keyboard, We are using the same MicroSD card. Strange? Glenn
That's seems like a really long time. When I first got my udoo (dual) I tried and failed at booting Android which is what I bough the thing for anyway. To test if it was the card or the board, I swapped out with the Linux card and it outed right up - certainly not 2:30. I'm patiently waiting for an android build that will fit on my 8Gb card so unless I take a crash course in Linux , I'm dead in the water.
Its been a week and dozens of attempts and I have yet to be able to uzip and flash an sd using ubuntu. unzip never actually unzips the image for some reason. when I hard kill unzip I have an img file? I tried putting this on the card and dd takes literally hours. Weird. I got a rasperrypi running in the time I was waiting for dd to run. no problem.
