Hello guys, I have an urgent question for you, may be you have a fastsolution and help me: I can download the ANDROID 5.0.2 FOR QUAD/LITE from http://www.udoo.org/bsp-download-page/ and install it to uSD card by follow the inctructions: Instructions To write Android image on uSD for SECOSBC-A62 QUAD or DUALLITE. From Linux machine: – Locate your uSD device $ sudo lsblk – Run make_sd script to flashes the android images on uSD card: $ sudo ./make_sd.sh /dev/sdX [ or /dev/mmcblkX ] [imx6q or imx6dl] But how to install Android to the internal eMMC? I would be very appresiate for any help!
Hi, First start the a62 with ubuntu os, Copy the android distro in USB, Mount the USB in a62 and then run the script with ./make_sd.sh /dev/mmcblk0p1 mmcblk0 ---> eMMC
Hi guys, I am new on the forum and udoo platforms. I just got my SBC-A62 Dual Lite. I flashed the UDOObuntu 2 For DUAL/LITE on a microSD Card and everything works fine. However, when I tried to burn the Android 5.0.2 for QUAD/LITE in the microSD, the make_sd.sh script returns error message during the partitionning pocedure. Hereafter the outcome of the script: Code: sudo bash ./make_sd.sh /dev/mmcblk0 imx6dl Trying to unmount partitions Disk /dev/mmcblk0 doesn't contain a valid partition table ./make_sd.sh: line 115: ((: boot_rom_sizeb = 16 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 116: ((: extend_size = 2068 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 117: ((: BOOT_ROM_SIZE = 8 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 118: ((: BOOTLOAD_RESERVE = 8 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 119: ((: SYSTEM_ROM_SIZE = 1500 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 120: ((: MISC_SIZE = 8 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 121: ((: CACHE_SIZE = 512 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 122: ((: VENDER_SIZE = 8 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 123: ((: RECOVERY_ROM_SIZE = 16 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ./make_sd.sh: line 124: ((: data_size = 5440 * 1024 * 1024 / = : syntax error: operand expected (error token is "= ") ############################################################################# ## ## ## Going to format /dev/mmcblk0 device. Everything on this device will be lost ## ## ## ############################################################################# Current partition table on /dev/mmcblk0: Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 4 heads, 16 sectors/track, 242560 cylinders, total 15523840 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mmcblk0 doesn't contain a valid partition table Continue with formatting ? (y/N)y Create android partition... 1+0 records in 1+0 records out 1024 bytes (1,0 kB) copied, 0,00421297 s, 243 kB/s Checking that no-one is using this disk right now ... OK Disk /dev/mmcblk0: 242560 cylinders, 4 heads, 16 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/mmcblk0: unrecognized partition table type Old situation: No partitions found Warning: given size (512) exceeds max allowable size (0) cannot build surrounding extended partition sfdisk: bad input Formatting partitions... mke2fs 1.42.9 (4-Feb-2014) mkfs.ext4: No such file or directory while trying to determine filesystem size mke2fs 1.42.9 (4-Feb-2014) Discarding device blocks: done Filesystem label=system OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 53648 inodes, 214216 blocks 10710 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=222298112 7 block groups 32768 blocks per group, 32768 fragments per group 7664 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done mke2fs 1.42.9 (4-Feb-2014) mkfs.ext4: No such file or directory while trying to determine filesystem size mke2fs 1.42.9 (4-Feb-2014) mkfs.ext4: No such file or directory while trying to determine filesystem size Flashing android images... 279+0 records in 279+0 records out 285696 bytes (286 kB) copied, 0,0760992 s, 3,8 MB/s 16+0 records in 16+0 records out 8192 bytes (8,2 kB) copied, 0,00416806 s, 2,0 MB/s 970+1 records in 970+1 records out 7950592 bytes (8,0 MB) copied, 0,00341947 s, 2,3 GB/s 1037+1 records in 1037+1 records out 8501504 bytes (8,5 MB) copied, 0,0043545 s, 2,0 GB/s 107108+0 records in 107108+0 records out 877428736 bytes (877 MB) copied, 0,346195 s, 2,5 GB/s 279+0 records in 279+0 records out 285696 bytes (286 kB) copied, 0,0771394 s, 3,7 MB/s imx6 DUALLITE Android 5.0 image created. I also tried to burn the Android 5.0.2 OS FOR QUAD/LITE into the eMMC (4 GB /dev/mmcblk3) as explained in this discussion but I got errors as you can see in the attached log. The device on /dev/mmcblk0 is a 32 GB microSD card on which I burned the UDOObuntu 2 For DUAL/LITE. and the system is running. Any help to burn the Android on microSD and both Android and UDOObuntu 2 on the eMMC will be appreciated! Thanks
Hi, For writing android on SD you don't need to use /dev/mmcblk0 this device is related to eMMC of A62,Once your card is inserted into host PC check for the command fdisk -l it will show your sd card device like /dev/sdb or /dev/sdc. To write the Android on SD use the command /make_sd.sh /dev/sdX imx6dl ---> this will write android to SD. For writing on Udoobuntu2 on eMMC Boot the A62 with SD then you are able to flash eMMC. For more information refer our wiki http://wikitech.seco.com/index.php/BSP_5.0_Flashing_eMMC. For writing Android on eMMC Boot the A62 with udoobuntu2 Copy the Android binaries to USB. Then Mount USB in A62. Now run the script at the path of your binaries ./make_sd.sh /dev/mmcblk0 imx6dl.
Hi Prakash.m, Thank you so much for your detailed and helpful answer! I am using the integrated SD card reader on my Laptop and the microSD was detected as eMMC device /dev/mmcblk0p1 Code: Partition table entries are not in disk order Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 81 heads, 10 sectors/track, 19165 cylinders, total 15523840 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/mmcblk0p1 8192 15523839 7757824 b W95 FAT32 I will try with an external USB SD Card reader. I hope this will fix the issue. When the system UDOObuntu 2 boots from a SD card, the eMMC flash of the SBC-A62 refers to the device /dev/mmcblk3 (lsblk -l or df -h) Running the make_sd.sh script with /dev/mmcblk0 will destroy the system on the SD card which is the device /dev/mmcblk0. Would you please confirm that I have to check first with lsblk command the list of devices (nodes) then pickup the internal eMMC flash device, in my case it is /dev/mmcblk3? Thanks for your help!
