Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    14420

  • Joined

  • Last visited

 Content Type 

Posts posted by Igor

    Quick Pinebook Preview / Review

    in Allwinner sunxi

    Posted

    1 hour ago, zador.blood.stained said:

    Desolder (or cut) the battery wire(s)? It should reset the AXP and allow starting from DC IN power.

     

    I only get this, looping.

    Spoiler 
    
INFO:    Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):0bc348a
NOTICE:  BL3-1: Built : 01:16:30, Jan  4 2017
NOTICE:  BL3-1 commit: 0bc348ab272ad81a4faf128ef38f4724f36fded6

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-4-pine64-gaa53f12-dirty (Apr 17 2017 - 10:12:30) Allwinner Technology 

uboot commit : aa53f12d5033bf3ba525d52d0a83d5115b8d662d
 
rsb: secure monitor exist
[      0.254]pmbus:   ready
[      0.257][ARISC] :arisc initialize
[      0.729][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.904][ARISC] :sunxi-arisc driver startup succeeded
[      0.951]PMU: AXP81X
[      0.953]PMU: AXP81X found
bat_vol=0, ratio=100
[      0.960]PMU: dcdc2 1100
[      0.963]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 = 2500, 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=1

     

     

    SD card boot:

     

    Spoiler 
    
HELLO! BOOT0 is starting!
boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f
 
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 = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
DRAM driver version: V1.1
start ddr type auto scan mode
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1280 mv
DRAM init OK 
lpddr3 try success
DRAM Type = 7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 408 MHz
DRAM zq value: 003939b9
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]: 7620 MB
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
The size of uboot is 000f8000.
[mmc]: mmc 0 data timeout, err 00000080
[mmc]: mmc 0 cmd 18 err 00000080
[mmc]: mmc 0  read blcok failed
[mmc]: mmc 0 block read failed
Fail in reading uboot head.
Ready to disable icache.

     

     

    0

    Quick Pinebook Preview / Review

    in Allwinner sunxi

    Posted

    On 14. 5. 2017 at 10:51 AM, tkaiser said:

    Same observation here, I tried it again after 5 minutes (red 'emtpy battery' logo shown and powered off again) but after 15 min Pinebook started and is now at


    My Pinebook is officially dead - it does not charge the battery - with stock system, latest build or Android image. Any known workarounds?

    0

    Changing to Chromium

    in Advanced users - Development

    Posted

    I can implement this later if we agree @zador.blood.stained @tkaiser

    /usr/sbin/logram # changed #11

    Spoiler 
    
#!/bin/sh

# Source: https://github.com/azlux/log2ram
# License: MIT
# License file: /usr/share/log2ram/LICENSE

SIZE=40M
USE_RSYNC=false
ENABLED=false
ME="${0##*/}"
DIRNAME="$(echo ${ME} | sed 's/2ram$//')"

[ -f /etc/default/${ME} ] && . /etc/default/${ME}

[ "$ENABLED" != true ] && exit 0

# don't touch anything below here.

HDD_LOG=/var/${DIRNAME}.hdd/
RAM_LOG=/var/${DIRNAME}/
LOG2RAM_LOG="${HDD_LOG}${ME}.log"
LOG_OUTPUT="tee -a $LOG2RAM_LOG"

isSafe () {
    [ -d $HDD_LOG ] || echo "ERROR: $HDD_LOG doesn't exist!  Can't sync."
    [ -d $HDD_LOG ] || exit 1
}

syncToDisk () {
    isSafe

    if [ "$USE_RSYNC" = true ]; then
        rsync -aXWv --delete --exclude ${ME}.log --links $RAM_LOG $HDD_LOG 2>&1 | $LOG_OUTPUT
    else
        cp -rfup $RAM_LOG -T $HDD_LOG 2>&1 | $LOG_OUTPUT
    fi
}

syncFromDisk () {
    isSafe

    if [ "$USE_RSYNC" = true ]; then
        rsync -aXWv --delete --exclude ${ME}.log --links $HDD_LOG $RAM_LOG 2>&1 | $LOG_OUTPUT
    else
        cp -rfup $HDD_LOG -T $RAM_LOG 2>&1 | $LOG_OUTPUT
    fi
}


case "$1" in
  start)
      [ -d $HDD_LOG ] || mkdir $HDD_LOG
      rm -f $LOG2RAM_LOG
      mount --bind $RAM_LOG $HDD_LOG
      mount --make-private $HDD_LOG
      mount -t tmpfs -o nosuid,noexec,nodev,mode=0755,size=$SIZE ${ME} $RAM_LOG
      syncFromDisk
      ;;

  stop)
      syncToDisk
      umount -l $RAM_LOG
      umount -l $HDD_LOG
      ;;

  write)
      syncToDisk
      ;;
  *)
      echo "Usage: ${ME} {start|stop|write}" >&2
      exit 1
      ;;
esac

     

     

    0

    I2C - Orangepi Zero Plus H5

    in Allwinner sunxi

    Posted

    36 minutes ago, moonki123 said:

    sudo nano /etc/modules -> add - i2c-dev, i2c-bcm2708

     

    and i refer https://github.com/longsleep/linux-pine64/pull/17/commits/d915860a9c57a9a3ab3df7775c942ca205c8e16d this site

     

    Wrong, this way:

     

    1. I2C, SPI, UART -> https://docs.armbian.com/User-Guide_Allwinner_overlays/ (I only test enabling UARTS)

    2. Images are experimental. We put them out because basic things work, you at least have connectivity ... This is checked, the rest ... no idea.

    0

    Ping too high(OrangePi Zero)

    in Allwinner sunxi

    Posted

    Wireless connection? Yes, it's normal - all initiatives that this is fixed to some normal state were failed, documentation does not exits and investing more time solo into this problem is long gone. New Zero comes with AP6212 which is working O.K.

    This is written at download page:

    • Onboard wireless chip (XR819) has poor software support so wireless connection issues are expected

    And if you do some forum search, you will get even more information about this problem.

    0

    Changing to Chromium

    in Advanced users - Development

    Posted

    I just committed package change :)

     

    What about adding to armhwinfo? 

    # create chromium cache directory
[[ ! -d /var/log/.cache ]] && mkdir /var/log/.cache && chgrp netdev /var/log/.cache && chmod g+w /var/log/.cache

    You can add scripts to:

    /etc/chromium-browser/customizations 

    export XDG_CACHE_HOME="/var/log/.cache"

    works.

    0

    Changing to Chromium

    in Advanced users - Development

    Posted

    I did few tests on Odroid C2 since my Pinebook is still dead and have nothing against to switch to Chromium. Firefox can't match. 

    There are still some writing to SD but minimal.
     

    6 hours ago, tkaiser said:

    Will we follow or waste our time trying to find out why seccomp/sandboxing is not working on arm64?


    Follow, waste later. We know about this problem and eventually will be fixed.

    0

    Changing to Chromium

    in Advanced users - Development

    Posted

    11 minutes ago, tkaiser said:

    Will we follow or waste our time trying to find out why seccomp/sandboxing is not working on arm64?


    I haven't done any research in this area but I suspect this is digging into the mud. What about http://midori-browser.org/ ? But I don't have much experiences neither ... Let's stick to Firefox for now and check little more about this and / or provide both browsers for now?

     

    BTW. After few hours, no change with my battery. Still not powering on.

    0

    Quick Pinebook Preview / Review

    in Allwinner sunxi

    Posted

    Problem? Battery was discharged down to null and when attaching a charger, current remains at 120 mA ... shouldn't this be little higher? I'll leave it for the day ...

    This is last log I got:

    Spoiler 
    
--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
bootcmd set setargs_mmc
key 0
recovery key high 10, low 10
fastboot key high 4, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
serial is: 841050344318440e088e
get Pine64 model from DRAM size and used storage
Pinebook: has ANX9807 chip
Pine64 model: pine64-pinebook
PowerBus = 2(0: not exist 1:vBus 2:acBus 3:vBus&acBus)
Battery Voltage=3286, Ratio=0
power trigger
battery low power and vol with dc or ac, should charge longer
[mmc]: Has init
[      4.041]---drivers/mmc/mmc.c 2733 mmc_init
reading bat\bempty.bmp
120056 bytes read in 5 ms (22.9 MiB/s)
bmp file buffer: 0x41000000, bmp_info.buffer: 47400000
fetch script data boot_disp.output_full fail
screen_id =0, screen_width =1366, screen_height =768
frame buffer address 47400036
set next system normal
drv_disp_exit
[mmc]: mmc exit start
[mmc]: start mmc_calibrate_delay_unit, don't access device...
[mmc]: delay chain cal done, sample: 178(ps)
[mmc]: delay chain cal done, ds: 185(ps)
[mmc]: mmc 2 exit ok
[      7.293]power off
set power off vol to default

     

     

    0

    Tinkerboard DVB drivers

    in Tinkerboard

    Posted

    If those drivers are part of a kernel, tell me which should be enabled in kernel configuration:

     

    4.4.x: https://github.com/armbian/build/blob/master/config/kernel/linux-rockchip-default.config

    4.11.x: https://github.com/armbian/build/blob/master/config/kernel/linux-rockchip-next.config

     

    or provide a patch / submit PR to our repository.

     

    If they are not part of the kernel source, then you need to obtain source (and possible firmware) and proceed this way: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver

    0

    Odroid XU4, Mainline Xenial, and Logitech Webcam Help

    in Odroid XU4

    Posted

    Armbian Legacy works, while on recent mainline 4.9.27 (from Hardkernel) my camera also doesn't work. I am getting this error: 

    [   62.977891] usb 3-1.1: USB disconnect, device number 3
[   65.246039] usb 3-1.1: new high-speed USB device number 5 using xhci-hcd
[   65.611019] usb 3-1.1: New USB device found, idVendor=046d, idProduct=0826
[   65.611037] usb 3-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[   65.611048] usb 3-1.1: Product: HD Webcam C525
[   65.611059] usb 3-1.1: SerialNumber: 0A035EE0
[   66.028076] usb 3-1.1: set resolution quirk: cval->res = 384
[   66.029876] uvcvideo: Found UVC 1.00 device HD Webcam C525 (046d:0826)
[   66.042387] uvcvideo 3-1.1:1.2: Entity type for entity Extension 5 was not initialized!
[   66.042428] uvcvideo 3-1.1:1.2: Entity type for entity Camera 1 was not initialized!
[   66.042444] uvcvideo 3-1.1:1.2: Entity type for entity Extension 6 was not initialized!
[   66.042459] uvcvideo 3-1.1:1.2: Entity type for entity Extension 7 was not initialized!
[   66.042474] uvcvideo 3-1.1:1.2: Entity type for entity Extension 8 was not initialized!
[   66.043261] input: HD Webcam C525 as /devices/platform/soc:/soc:usb3-0:/12000000.dwc3:/xhci-hcd.2.auto/usb3/3-1/3-1.1/3-1.1:1.2/input/input5

    I'll keep looking if there are any fixes for this problem.

    0

    need help install usb wifi

    in Allwinner sunxi

    Posted

    1 hour ago, Armnlegs said:

    Are they Retro script or Armbian? 


    Retro is based on Armbian but I am not familiar with what they changed. /boot/script.bin is (blob) board configuration for Allwinner boards on kernels older than 3.10. You can use bin2fex and fex2bin tools to convert this blob to text, edit and convert back to bin. But you have to understand what you are doing there ...

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept