[U-Boot] Odroid n1- booting hangs if we add memtest=4 to kernel command line.

[Kever Yang]

Hi Anand,


On 2019/9/16 下午7:03, Anand Moon wrote:
> Hi Jagan / Kever,
>
> I have with me Odroid - N1 per-released development board,
> It's almost same form factor to "Firefly-RK3399 Board" with
> rk3399-sdram-ddr3-1600.dtsi ram configuration.
>
> I have configure Odroid - N1 board to boot using TPL / SPL configuration
> using latest kernel and latest u-boot, but I am facing some issue with not
> able to upgrade my distro packages, It's literally hangs on heavy I/O
> operations.
>
> So I would like to check if the memory is working correctly, but below
> command failed.
>
> # sudo memtester 1024 5
> memtester version 4.3.0 (64-bit)
> Copyright (C) 2001-2012 Charles Cazabon.
> Licensed under the GNU General Public License version 2 (only).
>
> pagesize is 4096
> pagesizemask is 0xfffffffffffff000
> want 1024MB (1073741824 bytes)
> got  1024MB (1073741824 bytes), trying mlock ...
>
> Then I would like to enable *memtest=4* via bootargs ie kernel command
> line and it failed to boot up.


I'm not able to understand well about your issue, does it:
- boots fine with odroid-N1 but hang at memtester ?
- hang at "Starting kernel..." with kernel command like update
Since it boots OK, the DRAM should works OK, you can replace the TPL 
with rockchip binary ddr[0]
to double check if they have the same output.
I have no idea about the bootargs "memtest=4", but I suppose this should 
not affect the kernel
boot process, maybe you have do something wrong and not update the 
bootargs as what you
expect, you can print it in U-Boot to check the actually bootargs.

Thanks,
- Kever
[0] 
https://github.com/rockchip-linux/rkbin/blob/master/bin/rk33/rk3399_ddr_800MHz_v1.23.bin 

> below is the logs.
> -------------------
> U-Boot TPL 2019.10-rc3-00320-g23b93e33ad-dirty (Sep 16 2019 - 18:17:38)
> con reg
> cru , cic , grf , sgrf , pmucru , pmu
> Starting SDRAM initialization...
> sdram_init: data trained for rank 2, ch 0
> sdram_init: data trained for rank 2, ch 1
> Channel 0: sdram_init: data train failed for channel 0
> Channel 1: sdram_init: data train failed for channel 0
> 256B stride
> cic: ctr10      : (0xff620000 - 0x14)
> cic: status0    : (0xff620010 - 0x101)
> grf: ddrc0_con0 : (0xff77e380 - 0x1f81)
> grf: ddrc1_con0 : (0xff77e388 - 0x1f81)
> grf: soc_con0   : (0xff77e200 - 0x0)
> pmu: noc_auto_ena : (0xff3100d8 - 0x0)
> pmu: bus_idle_req : (0xff310060 - 0x0)
> pmu: bus_idle_st : (0xff310064 - 0x0)
> pmugrf: os_reg2 : (0xff320308 - 0x3aa17aa1)
> pmugrf: os_reg3 : (0xff32030c - 0x20000005)
> pmusgrf: soc_con4 : (0xff33e010 - 0x3600)
> Finish SDRAM initialization...
> Trying to boot from BOOTROM
> Returning to boot ROM...
>
> U-Boot SPL 2019.10-rc3-00320-g23b93e33ad-dirty (Sep 16 2019 - 18:17:38 +0530)
> Trying to boot from MMC1
> NOTICE:  BL31: v2.1(release):v2.1-705-g42cdeb93
> NOTICE:  BL31: Built : 18:17:28, Sep 16 2019
>
>
> U-Boot 2019.10-rc3-00320-g23b93e33ad-dirty (Sep 16 2019 - 18:19:19 +0530)
>
> Model: Hardkernel ODROID-N1
> DRAM:  rk3399_dmc_probe: pmugrf = 00000000ff320000
> 3.9 GiB
> MMC:   dwmmc at fe320000: 1, sdhci at fe330000: 0
> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>
> In:    serial at ff1a0000
> Out:   serial at ff1a0000
> Err:   serial at ff1a0000
> Model: Hardkernel ODROID-N1
> rockchip_dnl_key_pressed: adc_channel_single_shot fail!
> Net:
> Warning: ethernet at fe300000 (eth0) using random MAC address - f2:12:d7:dd:0e:72
> eth0: ethernet at fe300000
> Hit any key to stop autoboot:  0
> Card did not respond to voltage select!
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found U-Boot script /boot/boot.scr
> 871 bytes read in 5 ms (169.9 KiB/s)
> ## Executing script at 00500000
> 24838656 bytes read in 1049 ms (22.6 MiB/s)
> 56286 bytes read in 10 ms (5.4 MiB/s)
> 7326472 bytes read in 314 ms (22.3 MiB/s)
> ## Flattened Device Tree blob at 01f00000
>     Booting using the fdt blob at 0x1f00000
>     Loading Ramdisk to f5818000, end f5f14b08 ... OK
>     Loading Device Tree to 00000000f5807000, end 00000000f5817fff ... OK
>
> Starting kernel ...
>
> ---------
> Can you share some input on how to resolve this issue?
> or is it I am missing some configuration.
>
> Here is the normal boot log of the
> [0] https://pastebin.com/AxmqxeuU
>
> Best Regards
> -Anand