eMMC 장착 안하고 해서 그런가..?
U-Boot 2010.12-00000-g9777ca6-dirty (Nov 26 2015 - 10:10:11) for Exynox4412 CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 800MHz DRAM: 2 GiB PMIC VERSION : 0x00, CHIP REV : 2 TrustZone Enabled BSP BL1 version: 20121128 Checking Boot Mode ... SDMMC MMC Device 0: 15193 MB MMC Device 1 not found *** Warning - using default environment USB3503 NINT = OUTPUT LOW! ModeKey Check... run normal_boot No ethernet found. Hit any key to stop autoboot: 0 Exynos4412 # Exynos4412 # movi init 1 emmc reset... REVISION: 2.0 [ERROR] response timeout error : 00000104 cmd 1 Card NOT detected or Init Failed!! Exynos4412 # movi init 1 emmc reset... REVISION: 2.0 |
껐다 켜고 하니 잘되네..
일단 위의 경우에는 eMMC 안꼽고 movi init 1을 해서 그런건가 싶긴한데.. 다시 해보긴 귀찮네
U-Boot 2010.12-00000-g9777ca6-dirty (Nov 26 2015 - 10:10:11) for Exynox4412 CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 800MHz DRAM: 2 GiB PMIC VERSION : 0x00, CHIP REV : 2 TrustZone Enabled BSP BL1 version: 20121128 Checking Boot Mode ... SDMMC MMC Device 0: 15193 MB MMC Device 1 not found *** Warning - using default environment USB3503 NINT = OUTPUT LOW! ModeKey Check... run normal_boot No ethernet found. Hit any key to stop autoboot: 0 Exynos4412 # Exynos4412 # movi init 1 emmc reset... REVISION: 2.0 Manufacture ID 0x11 [ 7456MB ] NAME: S5P_MSHC4 Device: S5P_MSHC4 Manufacturer ID: 11 OEM: 100 Name: 008G9 Tran Speed: 0 Rd Block Len: 512 MMC version 4.0 High Capacity: Yes Size: 0MB (block: 7456) Bus Width: 8-bit DDR Boot Partition Size: 4096 KB Exynos4412 # run copy_uboot_sd2emmc reading FWBL1 ..device 0 Start 1, Count 30 MMC read: dev # 0, block # 1, count 30 ... 30 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing FWBL1 ..device 1 Start 0, Count 30 MMC write: dev # 1, block # 0, count 30 ... 30 blocks written: OK completed eMMC CLOSE Success.!! reading BL2 ..device 0 Start 31, Count 32 MMC read: dev # 0, block # 31, count 32 ... 32 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing BL2 ..device 1 Start 30, Count 32 MMC write: dev # 1, block # 30, count 32 ... 32 blocks written: OK completed eMMC CLOSE Success.!! reading bootloader..device 0 Start 63, Count 2048 MMC read: dev # 0, block # 63, count 2048 ... 2048 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing bootloader..device 1 Start 62, Count 2048 MMC write: dev # 1, block # 62, count 2048 ... 2048 blocks written: OK completed eMMC CLOSE Success.!! reading 0 TrustZone S/W.. Start 2111, Count 312 MMC read: dev # 0, block # 2111, count 312 ... 312 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing 1 TrustZone S/W.. Start 2110, Count 312 MMC write: dev # 1, block # 2110, count 312 ... 312 blocks written: OK completed eMMC CLOSE Success.!! MMC write: dev # 1, block # 2423, count 32 ... 32 blocks written: OK |
[링크 : https://wiki.odroid.com/old_product/accessory/emmc/emmc_recovery_u3]
2018/09/24 - [embeded/odroid] - odroid U3/XU4 eMMC 복구 방법
아무튼 eMMC에 미리 쓰고 나서 SD 메모리에 하나더 쓰고
그걸 이용해서 eMMC에 부트로더 넣어주면 끝!
'embeded > odroid' 카테고리의 다른 글
odroid U3 18.03 업데이트 (6) | 2018.09.29 |
---|---|
odroid U3 방열판/쿨러 (0) | 2018.09.26 |
odroid 고민.. (2) | 2018.09.26 |
odroid XU4 팬 컨트롤 (0) | 2018.09.24 |
odroid U3/XU4 eMMC 복구 방법 (0) | 2018.09.24 |