Jump to content

Igor

Administrators
  • Posts

    14418
  • Joined

  • Last visited

Posts posted by Igor

  1. 49 minutes ago, spottyrover said:

    I assume there is no other menu program to choose which boot option is available?


    You mean to select / boot into different systems at boot start like in GRUB? I don't know if  this is possible with some menus and even it is, it would be limited to some boards, which can use modern u-boot. It can be done from user space + reboot.

    Not all boards are at the level, you started playing with - Orange Pi Plus 2e ...

  2. No change ... the problem is also that, even I have connected power, I experience SD media problems - next step is manual charge :)
     

    Spoiler
    
    [mmc]: mmc 0 data timeout 80
    [mmc]: smc 0 err, cmd 18,  DCE
    [mmc]: mmc 0 close bus gating and reset
    [mmc]: mmc 0 mmc cmd 18 err 0x00000080
    [mmc]: read block failed, mmc_read_blocks 271
    [mmc]: block read failed, mmc_bread 324
     ** ext4fs_devread read error - block
    [mmc]: mmc 0 cmd 16 timeout, err 100
    [mmc]: smc 0 err, cmd 16,  RTO
    [mmc]: mmc 0 close bus gating and reset
    [mmc]: mmc 0 mmc cmd 16 err 0x00000100
    [mmc]: Set block len failed
    ** Can't read partition table on 0:0 **
    ** Invalid partition 1 **
    Bad Linux ARM64 Image magic!
    Booting with defaults ...
    [mmc]: mmc 0 cmd 16 timeout, err 100
    [mmc]: smc 0 err, cmd 16,  RTO
    [mmc]: mmc 0 close bus gating and reset
    [mmc]: mmc 0 mmc cmd 16 err 0x00000100
    [mmc]: Set block len failed
    ** Can't read partition table on 0:0 **
    ** Invalid partition 1 **
    [mmc]: mmc 0 cmd 16 timeout, err 100
    [mmc]: smc 0 err, cmd 16,  RTO
    [mmc]: mmc 0 close bus gating and reset
    [mmc]: mmc 0 mmc cmd 16 err 0x00000100
    [mmc]: Set block len failed
    ** Can't read partition table on 0:0 **
    ** Invalid partition 1 **

     


    Boot log: sopine legacy image with this patch

     

    Spoiler
    
    HELLO! BOOT0 is starting!
    boot0 commit : 43e77041d17badbf8be959b8db97232c5e3a0a75
     
    boot0 version : 4.0.0
    set pll start
    set pll end
    rtc[0] value = 0x00000000
    rtc[1] value = 0x00000000
    rtc[2] value = 0x00000000
    rtc[3] value = 0x0000a102
    rtc[4] value = 0x00000000
    rtc[5] value = 0x00000000
    DRAM driver version: V1.1
    rsb_send_initseq: rsb clk 400Khz -> 3Mhz
    PMU: AXP81X
    ddr voltage = 1280 mv
    DRAM Type = 7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
    DRAM clk = 552 MHz
    DRAM zq value: 003b3bdd
    DRAM dual rank full DQ gate training OK
    DRAM size = 2048 MB
    DRAM init ok
    dram size =2048
    card boot number = 0, boot0 copy = 0
    card no is 0
    sdcard 0 line count 4
    [mmc]: mmc driver ver 2015-05-08 20:06
    [mmc]: sdc0 spd mode error, 2
    [mmc]: Wrong media type 0x00000000
    [mmc]: ***Try SD card 0***
    [mmc]: HSSDR52/SDR25 4 bit
    [mmc]: 50000000 Hz
    [mmc]: 122623 MB
    [mmc]: ***SD/MMC 0 init OK!!!***
    sdcard 0 init ok
    The size of uboot is 000e8000.
    sum=17816203
    src_sum=17816203
    Succeed in loading uboot from sdmmc flash.
    boot0: start load other image
    boot0: Loading BL3-1
    Loading file 0 at address 0x40000000,size 0x0000a200 success
    boot0: Loading scp
    Loading file 2 at address 0x00040000,size 0x00019a00 success
    set arisc reset to de-assert state
    Ready to disable icache.
    
    onfiguring SPC Controller
    NOTICE:  BL3-1: v1.0(debug):3cdc5c3
    NOTICE:  BL3-1: Built : 20:14:26, May 18 2017
    INFO:    BL3-1: Initializing runtime services
    INFO:    BL3-1: Preparing for EL3 exit to normal world
    INFO:    BL3-1: Next image address = 0x4a000000
    INFO:    BL3-1: Next image spsr = 0x1d3
    
    
    U-Boot 2014.07-g6f37e5c-dirty (May 18 2017 - 20:14:27) Allwinner Technology 
    
    uboot commit : 6f37e5cf6a65b0b10455d12dbd631effabe765ec
     
    rsb: secure monitor exist
    [      0.381]pmbus:   ready
    [      0.383][ARISC] :arisc initialize
    [      0.756][ARISC] :arisc_dvfs_cfg_vf_table: support only one vf_table
    [SCP] :sunxi-arisc driver begin startup 2
    [SCP] :arisc_para size:1a8
    [SCP] :arisc version: [v0.1.76]
    [SCP] :sunxi-arisc driver v1.10 is starting
    [      0.899][ARISC] :sunxi-arisc driver startup succeeded
    [      0.936]PMU: AXP81X
    [      0.938]PMU: AXP81X found
    bat_vol=3229, ratio=0
    [      0.945]PMU: dcdc2 1100
    [      0.948]PMU: cpux 1008 Mhz,AXI=336 Mhz
    PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhz
    device_type = 3253, onoff=1
    dcdc1_vol = 3300, onoff=1
    dcdc2_vol = 1100, onoff=1
    dcdc6_vol = 1100, onoff=1
    aldo1_vol = 2800, onoff=0
    aldo2_vol = 1800, onoff=1
    aldo3_vol = 3000, onoff=1
    dldo1_vol = 3300, onoff=0
    dldo2_vol = 3300, onoff=0
    dldo3_vol = 2800, onoff=0
    dldo4_vol = 3300, onoff=1
    eldo1_vol = 1800, onoff=1
    eldo2_vol = 1800, onoff=0
    eldo3_vol = 1800, onoff=0
    fldo1_vol = 1200, onoff=0
    fldo2_vol = 1100, onoff=1
    gpio0_vol = 3100, onoff=0
    vbus not exist
    normal dc exist, limit to dc
    run key detect
    no key found
    no uart input
    DRAM:  2 GiB
    fdt addr: 0xb6ebcf40
    Relocation Offset is: 75f0f000
    In:    serial
    Out:   serial
    Err:   serial
    gic: sec monitor mode
    [      1.266]start
    drv_disp_init
    init_clocks: finish init_clocks.
    enable power vcc-hdmi-33, ret=0
    drv_disp_init finish
    boot_disp.output_disp=0
    boot_disp.output_type=3
    boot_disp.output_mode=10
    fetch script data boot_disp.auto_hpd fail
    disp0 device type(4) enable
    attched ok, mgr0<-->device1, type=4, mode=10
    [      1.673]end
    workmode = 0,storage type = 1
    [      1.677]MMC:        0
    [mmc]: mmc driver ver 2015-06-03 13:50:00
    SUNXI SD/MMC: 0
    [mmc]: start mmc_calibrate_delay_unit, don't access device...
    [mmc]: delay chain cal done, sample: 185(ps)
    [mmc]: media type 0x0
    [mmc]: Wrong media type 0x0
    [mmc]: ************Try SD card 0************
    [mmc]: host caps: 0x27
    [mmc]: MID 1b PSN db1b0226
    [mmc]: PNM 00000 -- 0x30-30-30-30-30
    [mmc]: PRV 1.0
    [mmc]: MDT m-11 y-2015
    [mmc]: speed mode     : HSSDR52/SDR25 
    [mmc]: clock          : 50000000 Hz
    [mmc]: bus_width      : 4 bit
    [mmc]: user capacity  : 122623 MB
    [mmc]: ************SD/MMC 0 init OK!!!************
    [mmc]: erase_grp_size      : 0x1WrBlk*0x200=0x200 Byte
    [mmc]: secure_feature      : 0x0
    [mmc]: secure_removal_type : 0x0
    [      1.883]sunxi flash init ok
    
    ** Unable to use mmc 0:1 for loading the env **
    Using default environment
    
    --------fastboot partitions--------
    mbr not exist
    base bootcmd=run mmcbootcmd
    bootcmd set setargs_mmc
    key 0
    recovery key high 12, low 10
    fastboot key high 6, low 4
    no misc partition is found
    to be run cmd=run mmcbootcmd
    update dtb dram start
    update dtb dram  end
    serial is: 841050344318440e088e
    check for ANX9807
    get Pine64 model from DRAM size
    DRAM >512M
    Pine64 model: pine64-plus
    PowerBus = 2(0: not exist 1:vBus 2:acBus 3:vBus&acBus)
    pre sys mode
    Battery Voltage=3229, Ratio=0
    key trigger
    sunxi bmp: unable to open file \boot\bootlogo.bmp
    [      2.283]inter uboot shell
    autoboot in 3 seconds, Press s or <Esc><Esc> to abort

     

     

  3. 2 hours ago, tomp said:

    But, changing the timestamp creates another problem,

    the compile reports that it cannot update due to the change.


    That's correct behaviour. You don't alter main script - and if you do, warning is issued.

     

    2 hours ago, tomp said:

    Can I ignore the errors about ending in middle of line?


    Yes.

     

    2 hours ago, tomp said:

    Which preempt model did you succeed with?

     

    IIRC all works but full preempt.

  4. 15 minutes ago, bozden said:

    Do you have any plans to publish new legacy versions? 3.4.113 is almost EOL...


    No, legacy kernels won't get much if any updates and also no more recent kernel (Allwinner boards). But mainline support is already very good, on A10-20-A31 is perfectly fine, while H3 needs some and H5 some more work to become ready for production usage. For server case scenarios, while video acceleration and 3D drivers won't get (if at all) here anytime soon.

  5. Those two chips are similar, document is correct and approach universal.

     

    On H5 board this part of /boot/armbianEnv.txt

    overlay_prefix=sun8i-h3

    is different, the rest is the same

    overlay_prefix=sun50i-h5

     

    Unfortunately it's not working out of the box. I try to add few and some fixing (wrong directory name - overlay vs overlays) is needed, but overlays exits:

    Spoiler
    
    ** File not found /boot/dtb/allwinner/overlay/sun50i-h5-w1-gpio.dtbo **
    ** File not found /boot/dtb/allwinner/overlay/sun50i-h5-uart1.dtbo **
    ** File not found /boot/dtb/allwinner/overlay/sun50i-h5-i2c0.dtbo **
    ** File not found /boot/dtb/allwinner/overlay/sun50i-h5-fixup.scr **

     

    Spoiler
    
    root@orangepizeroplus2:/boot/dtb/allwinner/overlays# ls -l
    total 40
    -rw-r--r-- 1 root root 374 May 16 14:53 sun50i-h5-i2c0.dtbo
    -rw-r--r-- 1 root root 374 May 16 14:53 sun50i-h5-i2c1.dtbo
    -rw-r--r-- 1 root root 374 May 16 14:53 sun50i-h5-i2c2.dtbo
    -rw-r--r-- 1 root root 837 May 16 14:53 sun50i-h5-spi0-jedec-nor.dtbo
    -rw-r--r-- 1 root root 527 May 16 14:53 sun50i-h5-spi0-spidev.dtbo
    -rw-r--r-- 1 root root 837 May 16 14:53 sun50i-h5-spi1-jedec-nor.dtbo
    -rw-r--r-- 1 root root 527 May 16 14:53 sun50i-h5-spi1-spidev.dtbo
    -rw-r--r-- 1 root root 506 May 16 14:53 sun50i-h5-uart1.dtbo
    -rw-r--r-- 1 root root 506 May 16 14:53 sun50i-h5-uart2.dtbo
    -rw-r--r-- 1 root root 506 May 16 14:53 sun50i-h5-uart3.dtbo

     

     

  6. Yes, we promote Ubuntu with a reason - Ubuntu Xenial has more recent and polished package base with less troubles than Debian Jessie. In desktop area we ran into enough troubles which lead to abandoning support for Debian desktop versions, while server remain fully supported. If there are no download options, you need to build it on your own.

     

    When Debian moves to Stretch, we plan to follow and situation will most likely turn in favour of Debian.

  7. 8 hours ago, Xalius said:

    Question, how did it run dry?


    I don't know, I assume I left it on ... I got it with full battery and after few hours here and there I lost few 10% and charge it back to 100% .. than after a day or two when I wanted to proceed with porting Armbian I could only boot into empty red battery followed by power off. Beside stock boot from eMMC I used one of Ayufan builds.

  8. My suspicions were similar - AXP does not start charging for some reason. Yesterday I screwed my Pinebook back together, since we are getting late with general update and this will have to wait ... I already did many tricks including plug / unplug ... but perhaps not enough? ASAP I'll try to charge it manually and dig back in. 

     

    Thanks for the tips!

  9. Wonderful. We have broken Firefox in arm64 (but solvable) and broken Chromium in armhf :(. In this case is better to have Firefox which at least works. We would need extensive research and patching for which we don't have time ATM so rolling back to Firefox seems to be the only viable solution?

     

    If you do some quick search, you can see lot's of problems with Chromium on Rpi, Odroids, ... 

  10. It works with SoPine default 3.10.105 image ... but battery remains dead.


    Battery connected:

    /sys/class/power_supply/battery/voltage_now

    3267000 DC

    3225000 Battery

    /sys/class/power_supply/battery/capacity

    0

    /sys/class/power_supply/battery/present

    1

    Without:

    /sys/class/power_supply/battery/voltage_now

    0

    /sys/class/power_supply/battery/capacity

    100

    /sys/class/power_supply/battery/present

    0

     

    "Charging" for 25 minutes, capacity remains 0, voltage idling at 3247-8, current draw at socket 0.3A at 5.00V

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines