letsdudiss

Hey Martin, I'll check if it can see both mmcblk. If that's what "nand-sata-install", is there a script to do the reverse? Copy from eMMC back to sdcard. This is so that I can clone boards Hey Zador, By "this kernel" you mean the current Armbian legacy kernel? I guess the kernel would be zImage. How do I build another uInitrd? I know another bloke asked this question in previous posts but it's still not clear to me how I could build uInitrd. EDIT: I read the posts again. There is the "update initramfs" thingo. I'll guess I'll try it.

Hi, I have a Chinese board that has H3 on it. Earlier versions of this board works with this tool. However, there has been a change in the eMMC chip and the tool failed to mount the eMMC. It goes into kernel panic as it could not find mmcblk0 or 1. I replaced the zImage of the tool with a zImage from a fresh Armbian build, the board doesnt go into kernel panic anymore, in fact, it can now see the mmc chip (cat /proc/partitions shows 8GB on mmcblk0). The console shows that its exporting MMC 0 but then on Windows, it says the USB device malfunction :/ Console log below: U-Boot 2016.09-armbian-fel-mass-storage-dirty (Sep 28 2016 - 12:21:11 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 1 GiB Using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 (FEL boot) ## Executing script at 43100000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2229486 Bytes = 2.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 1024MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2004620! ion_reserve_common: ion reserve: [0x50000000, 0x60000000]! Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... Starting g_mass_storage script https://github.com/zador-blood-stained/fel-mass-storage Exporting MMC 0 (SD) (/dev/mmcblk0) Done # cat /proc/partitions major minor #blocks name 179 0 7634944 mmcblk0 179 1 5173248 mmcblk0p1 179 2 16384 mmcblk0p2 179 3 1 mmcblk0p3 179 5 16384 mmcblk0p5 179 6 16384 mmcblk0p6 179 7 786432 mmcblk0p7 179 8 16384 mmcblk0p8 179 9 32768 mmcblk0p9 179 10 786432 mmcblk0p10 179 11 16384 mmcblk0p11 179 12 16384 mmcblk0p12 179 13 16384 mmcblk0p13 179 14 32768 mmcblk0p14 179 15 16384 mmcblk0p15 259 0 655360 mmcblk0p16 179 32 4096 mmcblk0boot1 179 16 4096 mmcblk0boot0 # The supplier has given me source code for u-boot, kernel mmc driver and kernel nand driver. I have verified these source code works as I updated an Android SDK with these code and the Android image can be now flashed with PheonixSuit (previously it would fail) Where should I start to make this tool work again? Funnily enough, if I use the "sdcard method" to write Armbian image into mmc, Armbian boots without a problem. I wouldve thought the Armbian image would need to be updated to work with new mmc chip. Not sure if I am understanding things correctly here. This is really out of my depth. Thanks for help