Results 1 to 3 of 3

Thread: Cubieboard1: Timeout initialising DRAM

  1. #1
    Join Date
    2016-Jul
    Posts
    4

    Cubieboard1: Timeout initialising DRAM

    Greetings, friends!

    I have a problem with the installation of Kali Linux on Cubieboard (first version).
    Since the difference between Cubieboard and Cubieboard2 are practically no, I use the image for Cubieboard2.

    When you try to boot, the board wrote to the console
    Code:
    U-Boot SPL 2016.01-rc3-ge7d6aa0 (Mar 16 2016 - 21:45:53)
    DRAM:Timeout initialising DRAM
    
    resetting ...
    
    U-Boot SPL 2016.01-rc3-ge7d6aa0 (Mar 16 2016 - 21:45:53)
    DRAM:Timeout initialising DRAM
    
    resetting ...
    
    U-Boot SPL 2016.01-rc3-ge7d6aa0 (Mar 16 2016 - 21:45:53)
    DRAM:Timeout initialising DRAM
    
    resetting ...
    
    U-Boot SPL 2016.01-rc3-ge7d6aa0 (Mar 16 2016 - 21:45:53)
    DRAM:Timeout initialising DRAM
    
    resetting ...
    And so on. At the same time, if you remove the SD card, then recorded on the Cubieboard Android loaded properly.
    Even with the boot loader of Kali.
    Code:
    U-Boot SPL 2016.01-rc3-ge7d6aa0 (Mar 16 2016 - 21:45:53)
    DRAM:HELLO! BOOT0 is starting!
    boot0 version : 1.5.1
    dram size =1024
    Succeed in opening nand flash.
    Succeed in reading Boot1 file head.
    The size of Boot1 is 0x0003c000.
    The file stored in 0X00000000 of block 2 is perfect.
    Check is correct.
    Ready to disable icache.
    Succeed in loading Boot1.
    Jump to Boot1.
    [       0.133] boot1 version : 1.4.0
    [       0.133] pmu type = 3
    [       0.135] bat vol = 0
    [       0.161] axi:ahb:apb=3:2:2
    [       0.161] set dcdc2=1400, clock=1008 successed
    [       0.163] key
    [       0.175] no key found
    [       0.175] flash init start
    [       4.055] flash init finish
    [       4.055] fs init ok
    [       4.056] fattype FAT16
    [       4.057] fs mount ok
    [       4.064] script finish
    [       4.065] power finish
    [       4.073] BootMain start
    [       4.073] 0
    [       4.092] key value = 0
    [       4.092] recovery key high 6, low 4
    [       4.093] unable to find fastboot_key key_max value
    [       4.101] test for multi os boot with display
    [       4.103] show pic finish
    [       4.106] load kernel start
    [       4.130] load kernel successed
    [       4.130] start address = 0x4a00000
    
    U-Boot 2011.09-rc1 (Nov 26 2012 - 14:01:52) Allwinner Technology
    
    CPU:   SUNXI Family
    Board: A10-EVB
    DRAM:  512 MiB
    NAND:  3776 MiB
    In:    serial
    Out:   serial
    Err:   serial
    --------fastboot partitions--------
    -total partitions:11-
    -name-        -start-       -size-
    bootloader  : 1000000       1000000
    env         : 2000000       1000000
    boot        : 3000000       2000000
    system      : 5000000       14000000
    data        : 19000000      20000000
    misc        : 39000000      1000000
    recovery    : 3a000000      2000000
    cache       : 3c000000      8000000
    private     : 44000000      1000000
    sysrecovery : 45000000      14000000
    UDISK       : 59000000      93000000
    -----------------------------------
    Hit any key to stop autoboot:  0
    
    NAND read: device 0 offset 0x3000000, size 0x2000000
     33554432 bytes read: OK
    
    Starting kernel ...
    
    [    0.181304] cryptomgr_test used greatest stack depth: 6672 bytes left
    [    0.181692] cryptomgr_test used greatest stack depth: 6480 bytes left
    [    0.183592] cryptomgr_test used greatest stack depth: 6388 bytes left
    [    0.184541] cryptomgr_test used greatest stack depth: 6280 bytes left
    [    0.217476] sw_ahci sw_ahci.0: forcing PORTS_IMPL to 0x1
    [    0.520709] [LCD] lcd_module_init
    [    0.587363] regulator_init_complete: axp20_buck3: incomplete constraints, leaving on
    [    0.595400] regulator_init_complete: axp20_buck2: incomplete constraints, leaving on
    [    0.603433] regulator_init_complete: axp20_ldo4: incomplete constraints, leaving on
    [    0.611377] regulator_init_complete: axp20_ldo3: incomplete constraints, leaving on
    [    0.619292] regulator_init_complete: axp20_ldo2: incomplete constraints, leaving on
    [    0.627278] regulator_init_complete: axp20_ldo1: incomplete constraints, leaving on
    [    0.635012] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock
    [    0.696762] init: to sleep 1 seconds.
    [    1.700693] init: has waken up.
    [    1.703873] init: [william] hdmistatus = 0!
    [    1.708059] init: [william] tvstatus = 0!
    [    1.712447] init: width = 1280
    [    1.715519] init: height = 720
    [    1.718588] init: s.st_size = 3686400
    [    2.683986] init: do_umount: /data
    [    2.813297] e2fsck used greatest stack depth: 5696 bytes left
    [    2.819376] logwrapper used greatest stack depth: 5616 bytes left
    [    2.971170] init: do_umount: /cache
    [    3.011807] init: dont need format /dev/block/nandk
    [    3.018021] init: dont need format /dev/block/nandi
    [    3.084217] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
    [    3.098237] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    [    4.090658] android_usb: already disabled
    [   12.802358] sunxi-rtc sunxi-rtc: rtc only supports 63£¨2010¡«2073£© years
    [   17.321757] wemac wemac.0: WARNING: no IRQ resource flags set.
    [   18.990233] netd used greatest stack depth: 5456 bytes left
    [   19.000310] netd used greatest stack depth: 5416 bytes left
    HELLO! BOOT0 is starting!
    boot0 version : 1.5.1
    dram size =1024
    Succeed in opening nand flash.
    Succeed in reading Boot1 file head.
    The size of Boot1 is 0x0003c000.
    The file stored in 0X00000000 of block 2 is perfect.
    Check is correct.
    Ready to disable icache.
    Succeed in loading Boot1.
    Jump to Boot1.
    [       0.133] boot1 version : 1.4.0
    [       0.133] pmu type = 3
    [       0.134] bat vol = 0
    [       0.161] axi:ahb:apb=3:2:2
    [       0.161] set dcdc2=1400, clock=1008 successed
    [       0.163] key
    Is it possible to to install Kali Linux on Cubieboard1?

    Kluge.

  2. #2
    Join Date
    2014-Feb
    Posts
    309
    You would need to modify the cubieboard2 script to point to cubieboard1's script.bin (it's the fex file) in order to boot it. Each allwinner device requires its own script.bin file that describes the hardware so unfortunately, the cubieboard2 script.bin won't work with the cubieboard1.

  3. #3
    Join Date
    2016-Jul
    Posts
    4
    Quote Originally Posted by steev View Post
    You would need to modify the cubieboard2 script to point to cubieboard1's script.bin (it's the fex file) in order to boot it. Each allwinner device requires its own script.bin file that describes the hardware so unfortunately, the cubieboard2 script.bin won't work with the cubieboard1.
    And where I can take correct script.bin file for Cubieboard1 and how to install it?

    Kluge.

Similar Threads

  1. Reaver timeout occurred
    By suresher in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2020-06-22, 13:38
  2. Using SSH with VPN = Timeout
    By Flauschi in forum General Archive
    Replies: 0
    Last Post: 2017-02-25, 02:05

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •