This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM385 with MT29F4G16ABAEAH4 "Starting kernel ..." hang issue

Other Parts Discussed in Thread: DM385

Hi All,

We are using CBB RDK 1.8 as reference for our development.

We have use MT29F4G16ABAEAH4 nand.

We are able to detect NAND as 512 MB.

 We have followed update.txt for flashing u-boot.min, u-boot.bin  and Kernel to nand.

//uboot-min
mmc rescan 0;fatload mmc 0 0x81000000 u-boot.min.nand;nand erase 0x0 0x20000;nand write.i 0x81000000 0x0 0x20000
 
// uboot
mmc rescan 0;fatload mmc 0 0x81000000 u-boot.bin;nand erase 0x20000 0x60000;nand write.i 0x81000000 0x20000 0x60000
 
// kernel
mmc rescan 0;fatload mmc 0 0x81000000 uImage;nand erase 0x00280000 0x00300000;nand write.i 0x81000000 0x00280000 0x300000;

- u-boot is able to boot from NAND successfully but when it reads Kernel by below command it hangs at "Starting kernel ...".

- We are able to boot the same kernel uImage from MMC.

=================================================================================================

// Write uImage

DM385:~#mmc rescan 0;fatload mmc 0 0x81000000 uImage;nand erase 0x00280000 0x00300000;nand write.i 0x81000000 0x00280000 0x300000;
reading uImage

2841232 bytes read

NAND erase: device 0 offset 0x280000, size 0x300000
Erasing at 0x560000 -- 100% complete.
OK

NAND write: device 0 offset 0x280000, size 0x300000
 3145728 bytes written: OK
DM385::~#nand read 0x81000000 0x00280000 0x280000;bootm

NAND read: device 0 offset 0x280000, size 0x280000
 2621440 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37_DM385_CBB_0.80.00
   Created:      2015-03-15   8:03:55 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2841168 Bytes = 2.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

===============================================================================

One more observation we found after enabling NAND debug in u-boot is that,

We are using Micron "MT29F4G16ABAEAH4" part but we are getting below below print

=================================

DM385-GP rev 1.1

ARM clk: 1000MHz
DDR clk: 533MHz
L3 clk: 200MHz
IVA clk: 297MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF

DRAM:  2 GiB
NAND:  HW ECC BCH8 Selected
NAND device: Manufacturer ID: 0x01, Chip ID: 0xcc (AMD NAND 512MiB 3,3V 16-bit)
512 MiB

===============================================================

For Micron Manufacturer ID should be "NAND device: Manufacturer ID: 0x2c, Chip ID: 0xcc (Micron NAND 512MiB 3,3V 16-bit)" .

1. Do we need to add any change in u-boot and  kernel to support MT29F4G16ABAEAH4 ?

2. Why Kernel hangs at  "Starting kernel ..." ?

Please advise

Thanks in advance,

Kalpesh

  • Hi Kalpesh,

    KALPESH PANCHAL said:
    1. Do we need to add any change in u-boot and  kernel to support MT29F4G16ABAEAH4 ?

    See the below e2e threads where the same NAND chip is used:

    KALPESH PANCHAL said:
    2. Why Kernel hangs at  "Starting kernel ..." ?

    See the below wiki page:

    Regards,
    Pavel