apollon77 Posted February 24, 2017 Author Posted February 24, 2017 3.) tpm8 384-DCDC3 (384 DRAM speed, modified DCDC3) freeze with limatester 100MB root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050506 active_windowing = 0
apollon77 Posted February 24, 2017 Author Posted February 24, 2017 3.) tpm8 432-DCDC3 (432 DRAM speed, modified DCDC3) stable with limatester 100MB root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x06060605 active_windowing = 0 And now ?! How to go further on the topic? Or are the affected devices simply "strange somehow" and can't use the default u-boot?!
ssvb Posted February 24, 2017 Posted February 24, 2017 First, it looks like the calibrated ZQ value is the same in all tests (reported as 0x5294a00). We can try to force dqs_gating_delay to 0x06060606 instead of autodetection and check if this improves anything. This can be done via the CONFIG_DRAM_DQS_GATING_DELAY option in U-boot defconfig, see http://git.denx.de/?p=u-boot.git;a=blob;f=board/sunxi/Kconfig;h=e1d4ab148f0838d746889775cfbab5bed57838bf;hb=a705ebc81b7f91bbd0ef7c634284208342901149#l196 Also it may be a very good idea to add CONFIG_DRAM_TIMINGS_DDR3_800E_1066G_1333J=y or CONFIG_DRAM_TIMINGS_DDR3_1066F_1333H=y to the defconfig too.
ssvb Posted February 24, 2017 Posted February 24, 2017 Welcome everyone and glad to find this great forum I have two boards and one of them has similar problem. With the old debian-server-ct-nand-v1.0.img it is rock stable but with Armbian Debian Jessie mainline it is throwing exceptions during the boot (and freeze). I compiled u-boot from Armbian source with various memory clocks (360-432mhz) without any differences (clock changed but no success boot). Also tried to set ZQ (from 7B to 7D as it is the only "visible" difference between the original Debian and Armbian memory settings) but i isn't changing (according to a10-meminfo). Any idea what could be the problem or what should be my next step? "Good" board (which is working with Armbian) has GT8UB512V memory ICs while the "bad" one has SKHynix. For the ZQ settings to have a meaningful effect, ODT needs to be enabled. This can be enabled by adding CONFIG_DRAM_ODT_EN=y to the U-Boot defconfig. Also at least for the boards with GT DRAM chips, these settings can result in a much improved reliability and higher DRAM clock speed ceiling: https://linux-sunxi.org/User:Ssvb/Cubietruck_DRAM_Calibration Basically, you could try the following: CONFIG_DRAM_TIMINGS_DDR3_1066F_1333H=y CONFIG_DRAM_EMR1=66 CONFIG_DRAM_ZQ=17643776 CONFIG_DRAM_ODT_EN=y CONFIG_DRAM_TPR3=528657 I'm not sure if these settings are also good for SKHynix but somebody could give them a try too. CONFIG_DRAM_DQS_GATING_DELAY option may be also added if necessary.
apollon77 Posted March 4, 2017 Author Posted March 4, 2017 Further infos on my problematicdevice: RAM-chips are from SKhynix I will start further testing with a mainly well working device today and will also send the RAM chips used there later on
apollon77 Posted March 5, 2017 Author Posted March 5, 2017 So results for another device (cubietruck2) ... limatester worked in all tested configs. Same u-boots as tested before to be compatible in the results ... (so latest ideas from ssvb not included) tpm8-u-boot-sunxi-with-spl_20170219_432_DCDC3_13v root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050605 active_windowing = 0 --> stable 3 u-boot armbian 5.20 root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050605 active_windowing = 0 -> stable u-boot armbian 5.25 root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050506 active_windowing = 0 -> stable I will post the RAM-chip-name from that device later on
andrei_l Posted April 24, 2017 Posted April 24, 2017 Any news on this? I have the same stability issues on my CT (hynix mems).
Recommended Posts