Jump to content

martinayotte

Members
 View Profile  See their activity

  • Posts

    3892

  • Joined

  • Last visited

 Content Type 

Posts posted by martinayotte

    wrong access rights for dpkg-deb after U-Boot build

    in Armbian build framework

    Posted

    BTW, I've built a Armbian_5.27_Bananapim2ultra_Debian_jessie_dev_4.11.0-next-20170427.img image 2 days ago, and it is booting fine.

    The only thing is that the WiFi AP6212 isn't in good shape yet : wlan0 could be activated, but the issue is that it doesn't receive response from DHCP request.

    I think it is due to the fact that WL-WAKE is connected to AXP GPIO instead of PLx, and therefore the NMI is managed well.

     

    0

    3.95 inch display test

    in Allwinner sunxi

    Posted

    Your display is not with a SPI interface, all transfers are done with parallel GPIOs.

    So, don't expect been able to run it using frame buffer.

    You can use GPIO library to drive it, but you are on your own displaying something from your own application.

     

    0

    Cubieboard 2 w/ 3.4.108-cubietruck missing ttyUSB0

    in Allwinner sunxi

    Posted

    When the device is just connected, it will appear, for example, I've just attached a USB-TTL Serial adaptor on my OPi, and dmesg output is : 

    [  635.907660] usb 1-1.3: new full-speed USB device number 3 using ehci-platform
[  636.147607] usbcore: registered new interface driver usbserial
[  636.147692] usbcore: registered new interface driver usbserial_generic
[  636.147736] usbserial: USB Serial support registered for generic
[  636.153595] usbcore: registered new interface driver pl2303
[  636.153653] usbserial: USB Serial support registered for pl2303
[  636.153725] pl2303 1-1.3:1.0: pl2303 converter detected
[  636.155984] usb 1-1.3: pl2303 converter now attached to ttyUSB0

    What you battery monitor look like ? Are you sure it is appearing as serial device ?

    0

    [resolved] linux-sun50i-dev/sunxi64-4.11.y broken

    in Armbian build framework

    Posted

    For a reason I didn't figure out, the build is broken : 

      MKIMAGE
  CC [M]  fs/ecryptfs/read_write.o
  CC [M]  fs/ecryptfs/crypto.o
  CC      lib/kasprintf.o
  CC [M]  net/bluetooth/mgmt.o
  CC      kernel/compat.o
  CC [M]  sound/soc/soc-dapm.o
  CC [M]  fs/ecryptfs/keystore.o

Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k, sandbox
Usage: mkimage -l image
          -l ==> list image header information
       mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)   
          -n ==> set image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
       mkimage [-D dtc_options] [-f fit-image.its|-F] fit-image
          -D => set options for device tree compiler
          -f => input filename for FIT source
Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
       mkimage -V ==> print version information and exit
make[3]: *** [arch/arm64/boot/dts/allwinner/overlay/sun50i-a64-fixup.scr] Error 1
make[2]: *** [arch/arm64/boot/dts/allwinner/overlay] Error 2
make[1]: *** [arch/arm64/boot/dts/allwinner] Error 2
make: *** [dtbs] Error 2
make: *** Waiting for unfinished jobs....

    It looks like mkimage choking with some arguments, but, from what I know, we didn't changed anything on Armbian side. So, maybe something that Icenowy introduced in her branch ...

     

    EDIT : Oh ! I've found something on Armbian side : the *.scr are missing ...

    0

    AP6212 in Mainline

    in Advanced users - Development

    Posted

    I've done that for ZeroPlus-H3/ZeroPlus-H5/NanoPiM1Plus2-H5 Mainline with success !

    But still no success with OPiWin on Mainline ...

    Maybe I've done a mistake somewhere or there is a mistake on schematic ...

    Could you confirmed me what pins are used on Legacy FEX for WL-PWREN and WL-WAKE ?

     

    0

    How do I set up the time?

    in Beginners

    Posted

    Normally, there is a NTP service running on all Armbian.

    Check if it is running by doing "ps -ef | grep ntp", you should have something like : 

    ntp        720     1  0 May04 ?        00:01:28 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 105:110

    if not, try to run it manually to see if any errors ...

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept