Jump to content

martinayotte

Members
  • Posts

    3892
  • Joined

  • Last visited

Posts posted by martinayotte

  1. 6 hours ago, pfeerick said:

    android eEMMC install might die a sudden death now and be reborn with linux... after a backup, of course

    I didn't take care of backuping mine ... ;)

     

    6 hours ago, pfeerick said:

    I usually use the eMMC jumpter to boot from the SD

    It is what I did but removed the jumper only 1 or 2 secs after bootloader started.

  2. Strange ...

    On your, when boot succeed, the sdcard is really at mmcblk0 ?

    Why even by removing the eMMC module, my SDCard wasn't seen as mmcblk0 ?

    Anyway, I've edited /boot/extlinux/extlinux.conf to point to mmcblk1, but it still try to access mmcblk0.

    But greping the whole /boot, some binary still have mmcblk0 ...

    I don't understand this whole boot process ...:wacko:

  3. When shorting the eMMC jumper, it start booting, but it produce a lot of mmcblk0 errors, and finally quit by not having mount rootfs.

    I've then remove eMMC module, but it does the same thing ...

    I think I will have to edit some configs to change it to mmcblk1 or mmcblk2.

     

     


    Warning: fsck not present, so skipping root file system
    [   33.619161] mmcblk0: error -5 transferring data, sector 262152, nr 8, cmd response 0x900, card status 0xb00
    [   33.647386] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
    [   33.699107] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
    [   33.718354] mmc0: tried to reset card
    [   33.737397] mmcblk0: error -5 transferring data, sector 262152, nr 8, cmd response 0x900, card status 0xb00
    [   33.750745] mmcblk0: retrying using single block read
    [   33.764169] mmcblk0: error -110 sending status command, retrying
    [   33.771975] mmcblk0: error -84 transferring data, sector 262152, nr 8, cmd response 0x900, card status 0x0
    [   33.780141] blk_update_request: I/O error, dev mmcblk0, sector 262152
    [   33.791800] EXT4-fs (mmcblk0p7): can't read group descriptor 0
    mount: mounting /dev/mmcblk0p7 on /root failed: Invalid argument
    done.
    Begin: Running /scripts/local-bottom ... done.
    Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
    done.
    mount: mounting /run on /root/run failed: No such file or directory
    run-init: current directory on the same filesystem as the root: error 0
    Target filesystem doesn't have requested /sbin/init.
    run-init: current directory on the same filesystem as the root: error 0
    run-init: current directory on the same filesystem as the root: error 0
    run-init: current directory on the same filesystem as the root: error 0
    run-init: current directory on the same filesystem as the root: error 0
    run-init: current directory on the same filesystem as the root: error 0
    No init found. Try passing init= bootarg.


    BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    (initramfs)

     
     

     

     

  4. Just now, Xalius said:

    I have removed the eMMC module from the board atm

    Do you mean it is trying to boot the eMMC even if I have SD inserted ?

     

  5. It failed to find boot partition. Looking at partition schemes, strangely it has 7 GPT partitions and the Boot one seems to be the 7th.



    In
    LPDDR3
    786MHz
    Bus Width=32 Col=11 Bank=8 Row=14/14 CS=2 Die Bus-Width=32 Size=2048MB
    ddrconfig:7
    OUT
    Boot1 Release Time: 2017-02-23, version: 2.39
    ChipType = 0x11, 127
    WR_REL_SET is 0 4
    SdmmcInit=2 0
    BootCapSize=2000
    UserCapSize=1ce8000
    FwPartOffset=2000 , 2000
    StorageInit ok = 26281
    SecureMode : SBOOT_MODE_NS
    LoadTrustBL
    Trust version:102
    BL2: Loading BL3-0
    No find bl30.bin
    BL2: Loading BL3-1
    image_size:0x124
    image_base:0x10000
    image_size:0x10
    image_base:0xff091000
    BL2: Loading BL3-2
    image_size:0x1dc
    image_base:0x8400000
    Load uboot, ReadLba = 2000
    Load OK, addr=0x200000, size=0x57bcc
    sha_hw_verify
    RunBL31 0x10000
    NOTICE:  BL31: v1.3(debug):3cb76c2
    NOTICE:  BL31: Built : 21:10:34, Feb 23 2017
    NOTICE:  BL31: Release version: v1.1
    INFO:    ARM GICv2 driver initialized
    INFO:    boot cpu mask: 1
    INFO:    plat_rockchip_pmu_init: pd status 0xe
    INFO:    BL31: Initializing runtime services
    INFO:    BL31: Preparing for EL3 exit to normal world
    INFO:    Entry point address = 0x200000
    INFO:    SPSR = 0x3c9


    U-Boot 2017.02-RK3328-06-02273-g84e0a7b-dirty (Apr 12 2017 - 23:42:46)

    CPU: rk3328
    cpu version = 1
    CPU's clock information:
        arm pll = 600000000HZ
        general pll = 800000000HZ
        ddr pll = 1572000000HZ
        codec pll = 594000000HZ
        new pll = 594000000HZ
    Board:  Rockchip platform Board
    Uboot as second level loader
    DRAM:  Found dram banks: 1
    Adding bank:0000000000200000(000000007fe00000)
    128 MiB
    GIC CPU mask = 0x00000001
    SdmmcInit = 0 0
    SDCard Update.
    storage init OK!
    Using default environment

    GetParam
    W: Invalid Parameter's tag (0x00000000)!
    Invalid parameter
    remotectl v0.1
    pwm freq=0x11b3dc
    pwm_freq_nstime=0x35d
    No pmic detect.
    CPU's clock information:
        arm pll = 1200000000HZ
        general pll = 800000000HZ
        ddr pll = 1572000000HZ
        codec pll = 594000000HZ
        new pll = 594000000HZ
    SecureBootEn = 0, SecureBootLock = 0

    #Boot ver: 0000-00-00#0.00
    empty serial no.
    normal boot.
    no fuel gauge found
    no fuel gauge found
    read logo on state from dts [0]
    no fuel gauge found
    'recovery' does not seem to be a partition nor an address
    Unable to boot:recovery
    try to start backup
    'backup' does not seem to be a partition nor an address
    Unable to boot:backup
    try to start rockusb

  6. Dooohhh !

    None of my USB-Serial are supporting this rate ... :wacko:

    What kind are you using ?

     

    EDIT : Oupps ! it is picocom that doesn't support it, minicom did ...

  7. @Xalius, do you know if the debug serial on those Rock64 should be UART2 (pin 8 and 10) on header ?

    Using either mate or minimal 0.2.1 images, I've only got few garbage characters and nothing else. I presumed it should be at 115200.

    Maybe the board I've received doesn't work at all ...:(

  8. Hi folks !

     

    I'm overwelmed with daily job as well as looking at this thread ...

    Not even been able to do diagnonal reading ...

     

    "Time is the missing indredient"  !

     

    BTW,  I' ve received today my Rock64 (Thanks @TLLim, but don't expect upcoming work/effort until my  overwelmed situation is cleared out)

     

  9. 2 hours ago, blaster_56 said:

    Which sd card problems ? I never had sd card problem.

    Of course you had some problems, otherwise, you would not posted that Chinese Android screenshot !
     

    2 hours ago, blaster_56 said:

    Today i will ask my network enginer to make a report

    Does he have a USB Serial to debug ? :lol:

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines