Hello,

Our config.:- Linux Kernel 2.6.35, Android 4.0.3

U-Boot 1.3.4 (Feb 21 2012 - 16:28:41) for HKDKC110 D Type
CPU: S5PC110@800MHz(OK)
APLL = 800MHz, HclkMsys = 200MHz, PclkMsys = 100MHz
MPLL = 667MHz, EPLL = 80MHz
HclkDsys = 166MHz, PclkDsys = 83MHz
HclkPsys = 133MHz, PclkPsys = 66MHz
SCLKA2M = 200MHz
Serial = CLKUART
Board: HKDKC110
I2C: pres(1), div(3)
ready
DRAM: 256 MB
Flash: 1 MB
SD/MMC: 7580MB
*** Warning - using default environment
pres(1), div(3)
In: serial
Out: serial
Err: serial
checking mode for fastboot ...
Hit any key to stop autoboot: 0
reading kernel.. 1081, 8192
MMC read: dev # 0, block # 1081, count 8192 ...8192 blocks read: OK
completed
reading RFS.. 9273, 3072
MMC read: dev # 0, block # 9273, count 3072 ...3072 blocks read: OK
completed
Boot with zImage
get_format
-------- 1 --------
## Loading init Ramdisk from Legacy Image at 30b00000 ...
Image Name: ramdisk
Created: 2012-02-17 7:46:49 UTC
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 164478 Bytes = 160.6 kB
Load Address: 30800000
Entry Point: 30800000
Verifying Checksum ... OK
## Transferring control to Linux (at address 30008000) ...
Starting kernel... <--------- stop

What is the problem when stop booting in "Starting Kernel...."?

We need more explanation what you did.

Did you compile and put the kernel you built?
What you changed?
Did you try .odt recovery image?

.odt recovery image can run on the Odroid7.
The uboot is built by ourself. Kernel is the same as yours, and we have not make any changes. Will the uboot recognize the machine ID then stop at starting kernel?

You can find a .odt image of ICS on ODROID-7 in this link.
http://com.odroid.com/sigong/nf_file_board/nfile_board_view.php?keyword=&bid=81

Are you following blow article?
http://www.hardkernel.com/?b114

Yes, there should be a checking routine of machine id.

Would the machine ID be the same for S5PC110 N type and D type?

I think it should be same. But, I can't guarantee.
Do you use N type?

yes, we use the N-type. D-type is 4Gnand+1GDram+3Gddr, N-type is 4Gnand+4Gddr. Can we use the same uboot for N-type? Would the bootup init be the same as D-type? When we use the same uboot, the board will be hanged on "Starting Kernel.....". What is the problem?

U-Boot 1.3.4 (Feb 22 2012 - 10:44:34) for HKDKC110 D Type
CPU: S5PC110@800MHz(OK)
APLL = 800MHz, HclkMsys = 200MHz, PclkMsys = 100MHz
MPLL = 667MHz, EPLL = 80MHz
HclkDsys = 166MHz, PclkDsys = 83MHz
HclkPsys = 133MHz, PclkPsys = 66MHz
SCLKA2M = 200MHz
Serial = CLKUART
Board: HKDKC110
I2C: pres(1), div(3)
ready
DRAM: 256 MB
Flash: 1 MB
SD/MMC: 7580MB
pres(1), div(3)
In: serial
Out: serial
Err: serial
checking mode for fastboot ...
Hit any key to stop autoboot: 0
reading kernel.. 1081, 8192
MMC read: dev # 0, block # 1081, count 8192 ...8192 blocks Read: OK
completed
reading RFS.. 9273, 3072
MMC read: dev # 0, block # 9273, count 3072 ...3072 blocks read: OK
completed
Boot with zImage
get_format
-------- 1 --------
## Loading init Ramdisk from Legacy Image at 30b00000 ...
Image Name: ramdisk
Created: 2012-02-17 7:46:49 UTC
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 164478 Bytes = 160.6 kB
Load Address: 30800000
Entry Point: 30800000
Verifying Checksum ... OK
## Transferring control to Linux (at address 30008000) ...
## Ramdisk Start address at 30b00040 to address at 30b282be
commandline: root=/dev/mmcblk0p2 rootfstype=ext3 rw init=/init console=ttySAC2,115200 androidboot.console=s3c2410_serial2 rootdelay=1
Starting kernel ... <------ STOP

You may need to check the DRAM initialisation routine of Kernel because N-type has different DRAM configuration.
Contact Samsung or distributor to get a different kernel source for N-type.
We can't help you any more.

Kernel can run then boot recently, but it hangs at the end of init string. dmesg shows that some files cannot be created in the memory and stop. Are some of the memorys block write protected? Is it possible to bypass the Secure Booting? How to do that?