[U-Boot] "Writing to MMC(%d)... failed"
"saveenv" won't write the environment out to disk. $ sudo dd if=/dev/zero of=/dev/sde seek=1 bs=512 count=3999 //wiping out area just to make sure no garbage is picked up.$ sudo dd if=bl1.HardKernel of=/dev/sde seek=1 iflag=dsync oflag=dsync$ sudo dd if=bl2.HardKernel of=/dev/sde seek=31 iflag=dsync oflag=dsync$ sudo dd if=u-boot-dtb.bin of=/dev/sde seek=63 iflag=dsync oflag=dsync$ sudo dd if=tzsw.HardKernel of=/dev/sde seek=2111 iflag=dsync oflag=dsync Fail: git://git.denx.de/u-boot.gitcommit 47d8ae4069b47ce966c0c5e0d8dd041e69ee1f86*****U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40) CPU: Exynos4412@1000MHzModel: Odroid based on Exynos4412DRAM: 2 GiBBoard PMIC initMMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1*** Warning - bad CRC, using default environment DFU alt info setting: doneNet: No ethernet found.Hit any key to stop autoboot: 0** Unrecognized filesystem type **** Unrecognized filesystem type **** Unrecognized filesystem type **Bad Linux ARM zImage magic!Odroid # saveenvSaving Environment to MMC...Writing to MMC(0)... failedOdroid # mmc infoDevice: SAMSUNG SDHCIManufacturer ID: 3OEM: 5344Name: SU08GTran Speed: 50000000Rd Block Len: 512SD version 3.0High Capacity: YesCapacity: 7.4 GiBBus Width: 4-bitErase Group Size: 512 BytesOdroid # mmc listSAMSUNG SDHCI: 0 (SD)EXYNOS DWMMC: 1Odroid # mmc part Partition Map for MMC device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type** Can't read partition table on 0:0 **Odroid # mmc hwpartition checkPartition configuration: No enhanced user data area No GP1 partition No GP2 partition No GP3 partition No GP4 partitioneMMC >= 4.4 required for enhanced user data areaFailed!Odroid # version U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40)armv7l-unknown-linux-gnueabihf-gcc (GCC) 5.0.0 20150221 (experimental)GNU ld (GNU Binutils) 2.25.51.20150221Odroid # fstype mmc 0:0 ** ext4fs_devread read error - blockFailed to mount ext2 filesystem...** Unrecognized filesystem type **Odroid # bdinfoarch_number = 0x000010C1boot_params = 0x40000100DRAM bank = 0x00000000-> start = 0x40000000-> size = 0x10000000DRAM bank = 0x00000001-> start = 0x50000000-> size = 0x10000000DRAM bank = 0x00000002-> start = 0x60000000-> size = 0x10000000DRAM bank = 0x00000003-> start = 0x70000000-> size = 0x10000000DRAM bank = 0x00000004-> start = 0x80000000-> size = 0x10000000DRAM bank = 0x00000005-> start = 0x90000000-> size = 0x10000000DRAM bank = 0x00000006-> start = 0xA0000000-> size = 0x10000000DRAM bank = 0x00000007-> start = 0xB0000000-> size = 0x0FF00000current eth = unknownip_addr = <NULL>baudrate = 115200 bpsTLB addr = 0xBFEF0000relocaddr = 0xBDE43000reloc off = 0x7A043000irq_sp = 0xB8E3D860sp start = 0xB8E3D850*****Ignore the "unrecognized filesystem type" stuff. I'm using ext4.mmc hwpartition only used for eMMC? Success:https://github.com/hardkernel/u-boot.gitcommit 33e05ffb159141b640571e91470172d83a2a1273*****U-Boot 2010.12-svn (May 12 2014 - 15:05:46) for Exynox4412
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]APLL = 1000MHz, MPLL = 880MHzDRAM: 2 GiB PMIC VERSION : 0x00, CHIP REV : 3TrustZone Enabled BSPBL1 version: 20121128 Checking Boot Mode ... SDMMCMMC Device 0: 7580 MBMMC Device 1 not found*** Warning - using default environmentUSB3503 NINT = OUTPUT LOW!ModeKey Check... run normal_bootNo ethernet found.Hit any key to stop autoboot: 0Exynos4412 # wipeenv 0spot on!0: wipeenv1:0MMC Device 1 not foundWiping u-boot env at MMC: 0Exynos4412 # mmcinfoDevice: S3C_HSMMC2Manufacturer ID: 3OEM: 5344Name: SU08G Tran Speed: 0Rd Block Len: 512SD version 2.0High Capacity: YesSize: 0MB (block: 7580)Bus Width: 4-bitBoot Partition Size: 0 KBExynos4412 # saveenvSaving Environment to SMDK bootable device...done*****
Wow, that came out as a real mess. I used Outlook.com to compose that message. Anyone experience that and can recommend how I can clean it up? I see that I composed using "Rich Text".
I'll try to redo it in my reply here using "Plain Text":
"saveenv" won't write the environment out to disk.
$ sudo dd if=/dev/zero of=/dev/sde seek=1 bs=512 count=3999 //wiping out area just to make sure no garbage is picked up. $ sudo dd if=bl1.HardKernel of=/dev/sde seek=1 iflag=dsync oflag=dsync $ sudo dd if=bl2.HardKernel of=/dev/sde seek=31 iflag=dsync oflag=dsync $ sudo dd if=u-boot-dtb.bin of=/dev/sde seek=63 iflag=dsync oflag=dsync $ sudo dd if=tzsw.HardKernel of=/dev/sde seek=2111 iflag=dsync oflag=dsync
Fail: git://git.denx.de/u-boot.git commit 47d8ae4069b47ce966c0c5e0d8dd041e69ee1f86 ***** U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40)
CPU: Exynos4412@1000MHz Model: Odroid based on Exynos4412 DRAM: 2 GiB Board PMIC init MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 *** Warning - bad CRC, using default environment
DFU alt info setting: done Net: No ethernet found. Hit any key to stop autoboot: 0 ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** Bad Linux ARM zImage magic! Odroid # saveenv Saving Environment to MMC... Writing to MMC(0)... failed Odroid # mmc info Device: SAMSUNG SDHCI Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Odroid # mmc list SAMSUNG SDHCI: 0 (SD) EXYNOS DWMMC: 1 Odroid # mmc part
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type ** Can't read partition table on 0:0 ** Odroid # mmc hwpartition check Partition configuration: No enhanced user data area No GP1 partition No GP2 partition No GP3 partition No GP4 partition eMMC >= 4.4 required for enhanced user data area Failed! Odroid # version
U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40) armv7l-unknown-linux-gnueabihf-gcc (GCC) 5.0.0 20150221 (experimental) GNU ld (GNU Binutils) 2.25.51.20150221 Odroid # fstype mmc 0:0 ** ext4fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Odroid # bdinfo arch_number = 0x000010C1 boot_params = 0x40000100 DRAM bank = 0x00000000 -> start = 0x40000000 -> size = 0x10000000 DRAM bank = 0x00000001 -> start = 0x50000000 -> size = 0x10000000 DRAM bank = 0x00000002 -> start = 0x60000000 -> size = 0x10000000 DRAM bank = 0x00000003 -> start = 0x70000000 -> size = 0x10000000 DRAM bank = 0x00000004 -> start = 0x80000000 -> size = 0x10000000 DRAM bank = 0x00000005 -> start = 0x90000000 -> size = 0x10000000 DRAM bank = 0x00000006 -> start = 0xA0000000 -> size = 0x10000000 DRAM bank = 0x00000007 -> start = 0xB0000000 -> size = 0x0FF00000 current eth = unknown ip_addr = <NULL> baudrate = 115200 bps TLB addr = 0xBFEF0000 relocaddr = 0xBDE43000 reloc off = 0x7A043000 irq_sp = 0xB8E3D860 sp start = 0xB8E3D850 ***** Ignore the "unrecognized filesystem type" stuff. I'm using ext4. mmc hwpartition only used for eMMC?
Success: https://github.com/hardkernel/u-boot.git commit 33e05ffb159141b640571e91470172d83a2a1273 ***** U-Boot 2010.12-svn (May 12 2014 - 15:05:46) for Exynox4412
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 2 GiB
PMIC VERSION : 0x00, CHIP REV : 3 TrustZone Enabled BSP BL1 version: 20121128
Checking Boot Mode ... SDMMC MMC Device 0: 7580 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 # wipeenv 0 spot on! 0: wipeenv 1:0 MMC Device 1 not found Wiping u-boot env at MMC: 0 Exynos4412 # mmcinfo Device: S3C_HSMMC2 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 0 Rd Block Len: 512 SD version 2.0 High Capacity: Yes Size: 0MB (block: 7580) Bus Width: 4-bit Boot Partition Size: 0 KB Exynos4412 # saveenv Saving Environment to SMDK bootable device... done *****
I think I've been able to narrow down, a bit, where the issue is coming from.
"mmc_set_blocklen" led me to "mmc_send_cmd" which showed that there is the "CONFIG_MMC_TRACE" I could use.
A notable difference between hardkernel's u-boot and mainline was the "uint flags;" was no longer in the "mmc_cmd" struct.
I did see that this removal was noted as being a problem back in 2012: http://lists.denx.de/pipermail/u-boot/2012-September/133409.html
The result from "saveenv":
Odroid # saveenv
Saving Environment to MMC...
Writing to MMC(0)... CMD_SEND:16
ARG 0x00000200
ret: -19
MMC_RSP_R1,5,6,7 0x00000000
I added the "printf" for "ret".
Hi,
On 02/27/2015 12:59 AM, Nathan wrote:
I think I've been able to narrow down, a bit, where the issue is coming from.
"mmc_set_blocklen" led me to "mmc_send_cmd" which showed that there is the "CONFIG_MMC_TRACE" I could use.
A notable difference between hardkernel's u-boot and mainline was the "uint flags;" was no longer in the "mmc_cmd" struct.
I did see that this removal was noted as being a problem back in 2012: http://lists.denx.de/pipermail/u-boot/2012-September/133409.html
The result from "saveenv":
This is too late for debug. The same result I can see when my card is not inserted.
Odroid # saveenv
Saving Environment to MMC...
Writing to MMC(0)... CMD_SEND:16
ARG 0x00000200ret: -19
MMC_RSP_R1,5,6,7 0x00000000I added the "printf" for "ret".
You should follow the card init sequence with the trace config, because it fails at init. This is the trace output from init sequence of my SD card:
MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:8 ARG 0x000001AA MMC_RSP_R1,5,6,7 0x000001AA CMD_SEND:55 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000120 CMD_SEND:41 ARG 0x40300000 MMC_RSP_R3,4 0x40FF8000 CMD_SEND:55 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000120 CMD_SEND:41 ARG 0x40300000 MMC_RSP_R3,4 0x40FF8000 CMD_SEND:55 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000120 CMD_SEND:41 ARG 0x40300000 MMC_RSP_R3,4 0xC0FF8000 CMD_SEND:2 ARG 0x00000000 MMC_RSP_R2 0x03534453 0x55303447 0x80273727 0x6900E700
DUMPING DATA 000 - 03 53 44 53 004 - 55 30 34 47 008 - 80 27 37 27 012 - 69 00 E7 00 CMD_SEND:3 ARG 0x00000000 MMC_RSP_R1,5,6,7 0xAAAA0520 CMD_SEND:9 ARG 0xAAAA0000 MMC_RSP_R2 0x400E0032 0x5B590000 0x1D8A7F80 0x0A404000
DUMPING DATA 000 - 40 0E 00 32 004 - 5B 59 00 00 008 - 1D 8A 7F 80 012 - 0A 40 40 00 CMD_SEND:13 ARG 0xAAAA0000 MMC_RSP_R1,5,6,7 0x00000700 CURR STATE:3 CMD_SEND:7 ARG 0xAAAA0000 MMC_RSP_R1,5,6,7 0x00000700 CMD_SEND:55 ARG 0xAAAA0000 MMC_RSP_R1,5,6,7 0x00000920 CMD_SEND:51 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000920 CMD_SEND:6 ARG 0x00FFFFF1 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:6 ARG 0x80FFFFF1 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:55 ARG 0xAAAA0000 MMC_RSP_R1,5,6,7 0x00000920 CMD_SEND:6 ARG 0x00000002 MMC_RSP_R1,5,6,7 0x00000920 CMD_SEND:16 ARG 0x00000200 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:17 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:16 ARG 0x00000200 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:17 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:16 ARG 0x00000200 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:18 ARG 0x00000A00 MMC_RSP_R1,5,6,7 0x00000900 CMD_SEND:12 ARG 0x00000000 MMC_RSP_R1b 0x00000900
I hope this will help you to solve this issue.
Best regards,
On Fri, Feb 27, 2015 at 7:16 AM, Przemyslaw Marczak p.marczak@samsung.com wrote:
This is too late for debug. The same result I can see when my card is not inserted.
Ugh, I meant to include the link to my post in the odroid forums which included the entire (very long) output: http://forum.odroid.com/viewtopic.php?f=13&t=2883#p76524
I'll inline compare my lines with yours, and prepend and append '*' to those that differ:
You should follow the card init sequence with the trace config, because it fails at init. This is the trace output from init sequence of my SD card:
MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
CMD_SEND:0
CMD_SEND:0
ARG 0x00000000
ARG 0x00000000
MMC_RSP_NONE
MMC_RSP_NONE
CMD_SEND:8
CMD_SEND:8
ARG 0x000001AA
ARG 0x000001AA
MMC_RSP_R1,5,6,7 0x000001AA
MMC_RSP_R1,5,6,7 0x000001AA
CMD_SEND:55
CMD_SEND:55
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000120
MMC_RSP_R1,5,6,7 0x00000120
CMD_SEND:41
CMD_SEND:41
ARG 0x40300000
ARG 0x40300000
MMC_RSP_R3,4 0x40FF8000
MMC_RSP_R3,4 0x40FF8000
CMD_SEND:55
CMD_SEND:55
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000120
MMC_RSP_R1,5,6,7 0x00000120
CMD_SEND:41
CMD_SEND:41
ARG 0x40300000
ARG 0x40300000
MMC_RSP_R3,4 0x40FF8000
* MMC_RSP_R3,4 0xC0FF8000* At the moment, I don't know what that command corresponds with, but I see the 55 and 41 are repeated 1 more time with yours before getting that 41 output that I have. Perhaps it's a timing/retry attempt on your system.
CMD_SEND:55 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000120
*retry attempt? Not on mine.*
CMD_SEND:41 ARG 0x40300000 MMC_RSP_R3,4 0xC0FF8000
*retry attempt? Not on mine.*
CMD_SEND:2
CMD_SEND:2
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R2 0x03534453
MMC_RSP_R2 0x03534453
0x55303447
* 0x55303847 *
0x80273727
* 0x8005FCD3*
0x6900E700
* 0x3000A400*
DUMPING DATA
DUMPING DATA
000 - 03 53 44 53
000 - 03 53 44 53
004 - 55 30 34 47
* 004 - 55 30 38 47*
008 - 80 27 37 27
* 008 - 80 05 FC D3*
012 - 69 00 E7 00
* 012 - 30 00 A4 00*
CMD_SEND:3
CMD_SEND:3
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0xAAAA0520
* MMC_RSP_R1,5,6,7 0xE6240520*
CMD_SEND:9
CMD_SEND:9
ARG 0xAAAA0000
* ARG 0xE6240000*
MMC_RSP_R2 0x400E0032
MMC_RSP_R2 0x400E0032
0x5B590000
0x5B590000
0x1D8A7F80
* 0x3B377F80*
0x0A404000
0x0A404000
DUMPING DATA
DUMPING DATA
000 - 40 0E 00 32
000 - 40 0E 00 32
004 - 5B 59 00 00
004 - 5B 59 00 00
008 - 1D 8A 7F 80
* 008 - 3B 37 7F 80*
012 - 0A 40 40 00
012 - 0A 40 40 00
CMD_SEND:13
CMD_SEND:13
ARG 0xAAAA0000
* ARG 0xE6240000*
MMC_RSP_R1,5,6,7 0x00000700
MMC_RSP_R1,5,6,7 0x00000700
CURR STATE:3
CURR STATE:3
CMD_SEND:7
CMD_SEND:7
ARG 0xAAAA0000
* ARG 0xE6240000*
MMC_RSP_R1,5,6,7 0x00000700
MMC_RSP_R1,5,6,7 0x00000700
CMD_SEND:55
CMD_SEND:55
ARG 0xAAAA0000
* ARG 0xE6240000*
MMC_RSP_R1,5,6,7 0x00000920
MMC_RSP_R1,5,6,7 0x00000920
CMD_SEND:51
CMD_SEND:51
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000920
MMC_RSP_R1,5,6,7 0x00000920
CMD_SEND:6
CMD_SEND:6
ARG 0x00FFFFF1
ARG 0x00FFFFF1
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:6
CMD_SEND:6
ARG 0x80FFFFF1
ARG 0x80FFFFF1
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:55
CMD_SEND:55
ARG 0xAAAA0000
* ARG 0xE6240000*
MMC_RSP_R1,5,6,7 0x00000920
MMC_RSP_R1,5,6,7 0x00000920
CMD_SEND:6
CMD_SEND:6
ARG 0x00000002
ARG 0x00000002
MMC_RSP_R1,5,6,7 0x00000920
MMC_RSP_R1,5,6,7 0x00000920
CMD_SEND:16
CMD_SEND:16
ARG 0x00000200
ARG 0x00000200
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
CMD_SEND:17
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:16
CMD_SEND:16
ARG 0x00000200
ARG 0x00000200
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
CMD_SEND:17
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:16
CMD_SEND:16
ARG 0x00000200
ARG 0x00000200
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:18
CMD_SEND:18
ARG 0x00000A00
ARG 0x00000A00
MMC_RSP_R1,5,6,7 0x00000900
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:12
CMD_SEND:12
ARG 0x00000000
ARG 0x00000000
MMC_RSP_R1b 0x00000900
MMC_RSP_R1b 0x00000900
I hope this will help you to solve this issue.
I searched my output for any "ret" value < 0 and it was only for "CMD_SEND:16" I should also add that I'm using odroid U2.
My output also doesn't stop at command 12. In fact I get an error right after it: "*** Warning - bad CRC, using default environment". But then that should be expected since I wipe blocks from 2560 to the start of my first partition. After that I get a bunch of 12, 16, 17, 18 commands (mostly 16, 17).
Thanks for taking the time to look into this issue.
I hope my last message didn't get lost during that outage last month.
In the mean time, I had to finagle the HardKernel code to work with GCC 5.0 which ended up being only 1 line change which I may end up encountering in mainline if I ever get far enough. After transferring the "CONFIG_MMC_TRACE" to the HardKernel mmc.c, I have a comparable output for the U2 with the "Samsung" mainline.
So the output comparison can be made more readable, I created a Google Drive Sheet, lining up the output when there were repeats, highlighting the differing output sections and changing the text color for the different values: https://docs.google.com/spreadsheets/d/1Gu10bG8wGJClorJjKoIMiAt4HR0nS22ugrL8...
Hello Nathan,
On 02/26/2015 01:30 AM, Nathan wrote:
Wow, that came out as a real mess. I used Outlook.com to compose that message. Anyone experience that and can recommend how I can clean it up? I see that I composed using "Rich Text".
I'll try to redo it in my reply here using "Plain Text":
Plain text is the right text formating.
"saveenv" won't write the environment out to disk.
$ sudo dd if=/dev/zero of=/dev/sde seek=1 bs=512 count=3999 //wiping out area just to make sure no garbage is picked up. $ sudo dd if=bl1.HardKernel of=/dev/sde seek=1 iflag=dsync oflag=dsync $ sudo dd if=bl2.HardKernel of=/dev/sde seek=31 iflag=dsync oflag=dsync $ sudo dd if=u-boot-dtb.bin of=/dev/sde seek=63 iflag=dsync oflag=dsync $ sudo dd if=tzsw.HardKernel of=/dev/sde seek=2111 iflag=dsync oflag=dsync
Fail: git://git.denx.de/u-boot.git commit 47d8ae4069b47ce966c0c5e0d8dd041e69ee1f86
U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40)
CPU: Exynos4412@1000MHz Model: Odroid based on Exynos4412 DRAM: 2 GiB Board PMIC init MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 *** Warning - bad CRC, using default environment
DFU alt info setting: done Net: No ethernet found. Hit any key to stop autoboot: 0 ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** Bad Linux ARM zImage magic! Odroid # saveenv Saving Environment to MMC... Writing to MMC(0)... failed Odroid # mmc info Device: SAMSUNG SDHCI Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Odroid # mmc list SAMSUNG SDHCI: 0 (SD) EXYNOS DWMMC: 1 Odroid # mmc part
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type ** Can't read partition table on 0:0 **
SD cards doesn't have hwpartitions.
Odroid # mmc hwpartition check Partition configuration: No enhanced user data area No GP1 partition No GP2 partition No GP3 partition No GP4 partition eMMC >= 4.4 required for enhanced user data area Failed! Odroid # version
U-Boot 2015.04-rc2-00081-g47d8ae4 (Feb 25 2015 - 12:12:40) armv7l-unknown-linux-gnueabihf-gcc (GCC) 5.0.0 20150221 (experimental) GNU ld (GNU Binutils) 2.25.51.20150221
Partition numbering starts from 1, so should use mmc 0:1
Odroid # fstype mmc 0:0 ** ext4fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Odroid # bdinfo arch_number = 0x000010C1 boot_params = 0x40000100 DRAM bank = 0x00000000 -> start = 0x40000000 -> size = 0x10000000 DRAM bank = 0x00000001 -> start = 0x50000000 -> size = 0x10000000 DRAM bank = 0x00000002 -> start = 0x60000000 -> size = 0x10000000 DRAM bank = 0x00000003 -> start = 0x70000000 -> size = 0x10000000 DRAM bank = 0x00000004 -> start = 0x80000000 -> size = 0x10000000 DRAM bank = 0x00000005 -> start = 0x90000000 -> size = 0x10000000 DRAM bank = 0x00000006 -> start = 0xA0000000 -> size = 0x10000000 DRAM bank = 0x00000007 -> start = 0xB0000000 -> size = 0x0FF00000 current eth = unknown ip_addr = <NULL> baudrate = 115200 bps TLB addr = 0xBFEF0000 relocaddr = 0xBDE43000 reloc off = 0x7A043000 irq_sp = 0xB8E3D860 sp start = 0xB8E3D850
Ignore the "unrecognized filesystem type" stuff. I'm using ext4. mmc hwpartition only used for eMMC?
Yes, only eMMC.
Success: https://github.com/hardkernel/u-boot.git commit 33e05ffb159141b640571e91470172d83a2a1273
U-Boot 2010.12-svn (May 12 2014 - 15:05:46) for Exynox4412
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 2 GiB
PMIC VERSION : 0x00, CHIP REV : 3 TrustZone Enabled BSP BL1 version: 20121128
Checking Boot Mode ... SDMMC MMC Device 0: 7580 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 # wipeenv 0 spot on! 0: wipeenv 1:0 MMC Device 1 not found Wiping u-boot env at MMC: 0 Exynos4412 # mmcinfo Device: S3C_HSMMC2 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 0 Rd Block Len: 512 SD version 2.0 High Capacity: Yes Size: 0MB (block: 7580) Bus Width: 4-bit Boot Partition Size: 0 KB Exynos4412 # saveenv Saving Environment to SMDK bootable device... done
I tested the latest mainline HEAD on U3, rev.0.2, on some two cheap Sandisk 4GB SD cards. It works fine for both Maybe your card is little tired and need some more timeout for some operations, this could be the reason of that issue. Can you test a different card?
Best regards,
participants (3)
-
Nathan -
Nathan Royce
-
Przemyslaw Marczak