Jump to content

Christos

Members
  • Posts

    306
  • Joined

  • Last visited

Posts posted by Christos

  1. Be careful, Armbian sun8i legacy is here: https://github.com/igorpecovnik/linux/tree/sun8i

     

    And 'history' of Allwinner's 3.4 BSP used for H3 boards (this latest version not including) can be found there: http://forum.armbian.com/index.php/topic/1351-h3-board-buyers-guide/?p=10144

     

    @jernej wanted to have a closer look into this new BSP variant -- he's away for a few days and might comment when he's back.

     

    I understand.

     

    From a first glimpse, it shows that in this latest BSP they do have added handling of the 24bit resolution, its obvious from the diffs in sound/soc/sunxi.

    If the modifications in sound/soc drivers involve and require major other changes in different modules (eg dma or clock/timing), then I do not think I'm gonna get the whole of it done, its above me, if on the other hand changes are compartmentalized only to the driver files without any other dependants, then I'll give it a try.

  2. I remember some linux-sunxi devs being pretty enthousiastic a few days ago when new HDMI drivers have been spotted in latest release of Allwinner's 3.4 BSP since this is the first time they got a proper license (and can now be used to implement HDMI in mainline kernel and u-boot). Maybe the same applies to Audio too (still no idea since enjoying the silence ;) )

     

     

    Seen some VERY INTERESTING diffs from orangepi's sourcetree there!!

     

    I will give it a try, make a little patch on the relevant device files and apply it to Igor's build..

     

    If that is for real and works.. then............  

  3. Yes, all audio drivers also have proper license now. We should see more H3 media related work now. I already informed Jean-Francois Moine about that, the guy who works on DRM and HDMI video & audio driver for H3 and A83T. He said it will take couple of weeks to upload the driver. BTW, from what I saw, SPDIF driver should already work on mainline. I'm not sure about I2S driver though. It would be best if you ask codekipper or someone else about I2S on H3 status on IRC. IIRC someone already started working on some audio drivers, apart from SPDIF and HDMI audio.

     

    Thanks for the info, really appreciated.

     

    If you happen to have the name of the relevant IRC (or a link) for me to keep an eye on would be great.

     

     

    Christos

  4. Ok Thomas, indeed needed the kernel clarification.

     

    It also eluded me that most likely the mainline devs couldnt care less for any legacy issues.

     

    On the other hand though, is there any way we can have audio in mainline for H3??

    I'm not able to have audio drivers at vanilla in either OPi or NPi

    login as: root
    root@192.168.1.12's password:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.7.6-sun8i
    System load:   0.44             Up time:       34 sec
    Memory usage:  8 % of 495Mb     IP:            192.168.1.12
    CPU temp:      26°C
    Usage of /:    7% of 15G
    
    Last login: Sat Oct 15 12:03:39 2016 from 192.168.1.6
    root@nanopineo:~# aplay -l
    aplay: device_list:268: no soundcards found...
    root@nanopineo:~# 
    
    

    Or is there any guide somewhere that we can enable even the onboard H3 audio?

     

     

    Christos

  5. Hi,

     

    Initially this started by trying to have proper capture and playback in PCM/I2S port, but it looks like that ALL H3 audio drivers got the same problem, they cannot capture at 24bits, they cannot do HiFi recording despite the Allwinner's datasheet that they do have 24bits in plain audio port and up to 32bits in PCM/I2S/HDMI.

     

    I made a very simple test in another thread here and anyone with any H3 board without anything else can do it too

    -> http://forum.armbian.com/index.php/topic/759-tutorial-i2s-on-orange-pi-h3/?p=17595

     

    Then it popped to my mind to do the most simple of the tests, in the included/onboard audio codec, wich according to datasheet it is working to 24bits, so not even a PCM/I2S enabled board is needed, just a stock one.

    login as: root
    root@192.168.1.10's password:
      ___                               ____  _    ___
     / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_)  / _ \ _ __   ___
    | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | | | | '_ \ / _ \
    | |_| | | | (_| | | | | (_| |  __/ |  __/| | | |_| | | | |  __/
     \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_|  \___/|_| |_|\___|
                           |___/
    
    Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i
    System load:   0.07             Up time:       2 hours
    Memory usage:  11 % of 494Mb    IP:            192.168.1.10
    CPU temp:      44°C
    Usage of /:    7% of 15G
    
    
    [ 2 updates to install: apt-get upgrade ]
    
    Last login: Sat Oct 15 08:21:07 2016 from 192.168.1.6
    root@orangepione:~# cat /etc/asound.conf
    pcm.!default  {
     type hw card 0
    }
    ctl.!default {
     type hw card 0
    }
    
    root@orangepione:~# aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 []
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 []
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    root@orangepione:~#
    root@orangepione:~# alsacap/alsacap
    *** Scanning for playback devices ***
    Card 0, ID `audiocodec', name `audiocodec'
      Device 0, ID `SUNXI-CODEC sndcodec-0', name `', 1 subdevices (1 available)
        1..2 channels, sampling rate 8000..192000 Hz
        Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE
          Subdevice 0, name `subdevice #0'
    Card 1, ID `sndhdmi', name `sndhdmi'
      Device 0, ID `SUNXI-HDMIAUDIO sndhdmi-0', name `', 1 subdevices (1 available)
        1..8 channels, sampling rate 8000..192000 Hz
        Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE
          Subdevice 0, name `subdevice #0'
    root@orangepione:~#
    
    
    

    As you see, this is a plain stock OrangePi One and got the onboard audio codec displayed.

    There is an error in the above system reporting, the codec according to datasheet is able to go up to 48KHz and not up to 192KHz, that is an indication that whoever did the driver implementation didnt do it properly..

     

    Next, I did the same test as in the PCM/I2S post above, this time with the onboard codec Card 0, ID `audiocodec', name `audiocodec'

    root@orangepione:~# arecord -t wav -c 2 -f S24_LE -r 48000 -d 10 testrec.wav
    Recording WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo
    root@orangepione:~#
    
    

    Requested a 10 seconds recording at 24bits.

    As previously, the system took 20 seconds of a recording..

    Then did the aplay of the recorded file

    root@orangepione:~# aplay testrec.wav
    Playing WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo
    root@orangepione:~#
    
    

    which again did squeeze the 20 seconds of initial recording into 10 seconds..

     

     

    Thus, if I look at it correctly, we have a more generic audio issue in H3 audio drivers and not only to PCM/I2S that initially thought.

    Could be the DMA implemetnation or timing, dont know.

     

     

    @Igor and admins, do you think we can report this to linux sunxi for rectification?

     

     

    Christos

  6. I use a PCM4222 EVM.

     

    From what I seen, the current driver (daudio), is working only with 16bits capture.

     

    Though the driver itself reports via alsacap that it can work at any ramplerate 8000..192000 and at 16/24/32bits as shown in Card 1, ID `snddaudio', name `snddaudio'

    login as: root
    root@192.168.1.131's password:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i
    System load:   0.18             Up time:       3 min
    Memory usage:  9 % of 494Mb     IP:            192.168.1.131
    CPU temp:      39°C
    Usage of /:    11% of 15G
    
    Last login: Fri Oct 14 17:25:47 2016 from 192.168.1.6
    root@nanopineo:~# alsacap/alsacap
    *** Scanning for playback devices ***
    Card 0, ID `audiocodec', name `audiocodec'
      Device 0, ID `SUNXI-CODEC sndcodec-0', name `', 1 subdevices (1 available)
        1..2 channels, sampling rate 8000..192000 Hz
        Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE
          Subdevice 0, name `subdevice #0'
    Card 1, ID `snddaudio', name `snddaudio'
      Device 0, ID `SUNXI-TDM0 snddaudio-0', name `', 1 subdevices (1 available)
        1..2 channels, sampling rate 8000..192000 Hz
        Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE
          Subdevice 0, name `subdevice #0'
    Card 2, ID `sndhdmi', name `sndhdmi'
      Device 0, ID `SUNXI-HDMIAUDIO sndhdmi-0', name `', 1 subdevices (1 available)
        1..8 channels, sampling rate 8000..192000 Hz
        Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE
          Subdevice 0, name `subdevice #0'
    root@nanopineo:~#
    
    

    There is an easy test to verify that the H3 PCM/I2S driver has a serious flaw/bug though.

     

    The PCM/I2S port as it is now setup in script.bin (working only in legacy.. still pending in vanilla..)

    is configuring the PCM/I2S port as master, thus it does not rely for any timing/control signal from the peripheral/codec/adc.

    That is good for our testing since no additional external hardware/codec/adc is required and everyone can do the test. Anyone that has any H3 board with a PCM/I2S enabled port.

     

    I do have setup the card1 as default

    root@nanopineo:~# cat /etc/asound.conf
    pcm.!default {
        type hw
        card 1
    }
    
    ctl.!default {
        type hw
        card 1
    }
    
    

    So, at first, do a 20sec capture

    root@nanopineo:~# arecord -t wav -c 2 -f S24_LE -r 48000 -d 20 testrec.wav
    Recording WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo
    root@nanopineo:~#
    
    

    You will notice, if you got a clock/timer on the other side of the screen, that this command it actually records for 40 sec!! not 20 as requested!!

    So, if you play the wav file you expect it to last for 40 sec..

     

    Then do play the recorded file

    root@nanopineo:~# aplay testrec.wav
    Playing WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo
    root@nanopineo:~#
    
    

    If you see the actual time passed, it will be 20 sec played, but the inital recording lasted for 40 sec..         (gotcha)

     

    In any samplerate you try, either 8K or 96K or 192K it will give the same results if you do a capture with more than 16bits resolution, eg S24_LE or S32_LE.

     

    Capturing with 16bits resolution eg with S16_LE everything is just fine.

     

     

    Obviously the H3 PCM/I2S driver has a problem with capture in anything higher than 16bits resolution and needs to be rectified.

     

     

    Christos

     

     

     

    P.S.

    Even if you do not rely on the -d <seconds> parameter, but you do it manualy by starting and stopping with ctrl-C and measuring the elapsed time yourself, you will notice the same thing, the recorded file lasts always half the time you recorded for, when having more than 16bits eg S24_LE.

  7. Hi Slawek,

     

    :)  There are no old guys, just some others are too young!! (I myself am a '65 model..)

     

    Not sure if that applies to you, but the two images in the armbian nanopineo specific download page are headless (no GUI) so they might lack some of the X11 features you require.

    Take a shot and try to build one for yourself via the https://github.com/igorpecovnik/lib in the page there are instructions for a custom build so you might have luck building a desktop build instead of a console/terminal only.

     

    Christos

  8. Hi,

     

    Got a bit of a strange situation here.

     

    Trying to get H3 I2S working in both playback and capture.

     

    Tweaked script.bin and got the I2S0 up and running.

     

    Playback in 96K and 192K tested and is ok.

     

    Capture though is giving me a headache.

     

    When I try to use arecord it does work and generates a wav file but upon playing the file with aplay and although the samplerate (96K or 192K) and channel numbers (Stereo) show ok on screen, the audio result from this recording is always mono and looks that the included samples numer is divided by 2 thus the playback time is shortened accordingly, eg if I record 10 sec, a 5 sec playing time happens.

     

    Verified the actual I2S HW lines with digital scope and they are ok with proper time periods/frequency and samplerate or bit depth.

     

    So, my question, has anyone any experience with a working I2S in H3 ? Is it actually working or the I2S driver is misbehaving? Is it tested in 96K and 192K capture?

     

    Can someone point me to where the pcm script.fex parameters are documented?

    The official sunxi does not show them..

    -> http://linux-sunxi.org/Fex_Guide

     

     

    Christos

     

     

    P.S.

    Boards tested/used are NanoPi NEO & OrangePi ONE

     

     

     

    To add a bit here, the problem happens when I capture/play with samplesizes more than 16bits, eg 24 or 32, S24_LE/S32_LE.

     

     

    Christos

  9. Hi

    Linux imbecile here.

    Do any of the Armbian distros have the USB port operational?

    I want to use my Neo as a NAA device for HQPlayer. I don't know if I have not installed HQPlayer NAA correctly onto my Neo or if the NAA is not seeing my DAC because the USB port is disabled.

    I am currently using ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i.

     

    Any help greatly appreciated.

    Regards

    Carl

     

    Hi Carl,

     

    Yes, if you build yourself a new image now, either legacy or vanilla, it will have USB working ok.

    See above posts 213 & 216

     

    Christos

  10. Only sources available. So unless someone knowledgeable reading through sources adds the stuff to linux-sunxi wiki nothing will change (I'm not kidding and I also lack both skills and interest... but this is really how it works. Documentation has to be written ;) )

     

    Ok Thomas, I understand your point and where you stand on this.

     

    I only hope that some knowledgable guys who have insight or experience on the issue I have stated on the initial post, come and lend a hand with some pointers at least on what to look for or where.

     

    Any help is welcome.

     

    Christos

  11. There are though after all pcm parameters in the script.fex for the H3

    [pcm0]
    daudio_used = 1
    daudio_master = 4
    daudio_select = 1
    audio_format = 1
    signal_inversion = 1
    mclk_fs = 128
    sample_resolution = 32
    slot_width_select = 32
    pcm_lrck_period = 32
    pcm_lrckr_period = 1
    msb_lsb_first = 0
    sign_extend = 0
    slot_index = 0
    slot_width = 32
    frame_width = 0
    tx_data_mode = 0
    rx_data_mode = 0
    i2s_mclk = port:PA18<2><1><default><default>
    i2s_bclk = port:PA19<2><1><default><default>
    i2s_dout0 = port:PA20<2><1><default><default>
    i2s_din = port:PA21<2><1><default><default>
    
    

    And they are sitting there since the first 3.x release from whoever did it (AllWinner itself or SinoVoip/Xunlong/FriendlyArm..)

    Yet there is zero info for most of them..

  12. Hi,

     

    Got a bit of a strange situation here.

     

    Trying to get H3 I2S working in both playback and capture.

     

    Tweaked script.bin and got the I2S0 up and running.

     

    Playback in 96K and 192K tested and is ok.

     

    Capture though is giving me a headache.

     

    When I try to use arecord it does work and generates a wav file but upon playing the file with aplay and although the samplerate (96K or 192K) and channel numbers (Stereo) show ok on screen, the audio result from this recording is always mono and looks that the included samples numer is divided by 2 thus the playback time is shortened accordingly, eg if I record 10 sec, a 5 sec playing time happens.

     

    Verified the actual I2S HW lines with digital scope and they are ok with proper time periods/frequency and samplerate or bit depth.

     

    So, my question, has anyone any experience with a working I2S in H3 ? Is it actually working or the I2S driver is misbehaving? Is it tested in 96K and 192K capture?

     

    Can someone point me to where the pcm script.fex parameters are documented?

    The official sunxi does not show them..

    -> http://linux-sunxi.org/Fex_Guide

     

     

    Christos

     

     

    P.S.

    Boards tested/used are NanoPi NEO & OrangePi ONE

     

     

     

     

  13. You can force older naming scheme by adding rule in /etc/udev/rules.d

    ..if I only knew  :lol:  how to do that.

     

    And as they say, if its not broken, dont try to fix it, I'll live with it.

    It works just fine as it is, it just has a ..strong character of its own!!

     

    Thanks for the hint though, appreciated and I might dive into udev rules someday to see how it can be done.

     

     

    Christos

  14. Good!

    Thanks Thomas,

     

    Fresh build, Armbian 5.21, Ubuntu 16.04.1 LTS, kernel 4.7.6

    C:\Christos>ssh christos@192.168.1.131
    christos@192.168.1.131's password:
    setsockopt IP_TOS 16: Invalid argument:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
    System load:   0.36             Up time:       1 min
    Memory usage:  5 % of 495Mb     IP:            192.168.1.131
    CPU temp:      35Β°C
    Usage of /:    8% of 15G
    
    Last login: Sun Oct  2 20:08:54 2016 from 192.168.1.6
    
    christos@nanopineo:~$ sudo ifconfig -a
    [sudo] password for christos:
    eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:1 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1
              RX bytes:49 (49.0   TX bytes:49 (49.0 
    
    wlxe84e0626ba70 Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
              inet addr:192.168.1.131  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::ea4e:6ff:fe26:ba70/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:139 errors:0 dropped:0 overruns:0 frame:0
              TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:16333 (16.3 KB)  TX bytes:20986 (20.9 KB)
    
    christos@nanopineo:~$ ping www.ubuntu.com -c 3
    PING www.ubuntu.com (91.189.89.118) 56(84) bytes of data.
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=1 ttl=
    52 time=70.2 ms
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=2 ttl=
    52 time=69.0 ms
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=3 ttl=
    52 time=67.9 ms
    
    --- www.ubuntu.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 67.914/69.075/70.291/1.017 ms
    christos@nanopineo:~$
    
    

    works like a charm, board USB connector enabled, WiFi up and running.

     

    Thanks again

    Christos

     

     

     

    P.S.

    The only strange thing is the wifi device with weird name wlxe84e0626ba70..

  15. Ok thanks,

     

    Just to confirm though, I've seen a few posts in armbian, eg -> http://forum.armbian.com/index.php/topic/993-ds18b20-temperature-sensor-in-lamobo-r1/

    where they modify BOTH the fex and the dts in order to achieve their goal.

    I guess that is redundant? only the dts needs change right?

     

    Christos

     

     

     

    P.S.

     

    BTW, these are some real case examples found in the forum here regarding dtc, so I sum them up just in case they are useful to someone that wants to have a look, together with Thomas's hints made me get an idea of what the dtc is

    http://forum.armbian.com/index.php/topic/382-armbian-on-pcduino3/?p=2444

    http://forum.armbian.com/index.php/topic/993-ds18b20-temperature-sensor-in-lamobo-r1/?p=16089

    http://forum.armbian.com/index.php/topic/385-banana-pi-usb-otg/?p=7773

    http://forum.armbian.com/index.php/topic/82-spi-on-olinuxino-a20-micro-with-device-tree-kernel/?p=827

     

     

    P.S. 2

    -> http://free-electrons.com/pub/conferences/2012/elce/arm-soc-checklist/arm-soc-checklist.pdf

    -> https://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf

    -> The purpose of the Device Tree is to move a significant part
    of the hardware description into a data structure that is no
    longer part of the kernel binary itself.
    -> This data structure, the Device Tree Source is compiled into
    a binary Device Tree Blob
    -> The Device Tree Blob is loaded into memory by the
    bootloader, and passed to the kernel.
    -> It replaces all the board-*.c files, and removes all the
    manual registration of platform_device. Also, no longer
    needed to have Kconfig options for each board.
    -> Usage of the Device Tree is mandatory for all new ARM
    SoCs. No way around it.
    
    
  16. Hi,

     

    Seen some posts where mentioning that depending of the version of kernel there is either FEX or DTS usage, old ones called Legacy, using FEX to define GPIOs and Peripherals pins.

    Wit Mainline Kernel, is using DTS.

     

    Yet in the recent kernel (dev) armbian builds, eg armbian 5.21, kernel 4.7.6 (on H3, NEO), seen the /boot containing all the FEX stuff script.bin etc.

    Is FEX still used in the mainline kernel builds?

    C:\Christos>ssh christos@192.168.1.131
    christos@192.168.1.131's password:
    setsockopt IP_TOS 16: Invalid argument:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.7.6-sun8i
    System load:   0.00             Up time:       37 min
    Memory usage:  9 % of 495Mb     IP:            192.168.1.131
    CPU temp:      34Β°C
    Usage of /:    8% of 15G
    
    Last login: Sun Oct  2 13:27:36 2016 from 192.168.1.6
    
    christos@nanopineo:~$ su root
    Password:
    root@nanopineo:/home/christos# cd /boot
    root@nanopineo:/boot# ls -l
    total 15788
    drwxr-xr-x 2 root root    4096 Oct  2 08:32 bin
    -rw-r--r-- 1 root root    6944 Oct  2 08:33 boot.bmp
    -rw-r--r-- 1 root root    2846 Oct  2 08:27 boot.cmd
    -rw-r--r-- 1 root root    2918 Oct  2 08:35 boot.scr
    -rw-r--r-- 1 root root  140522 Oct  2 08:22 config-4.7.6-sun8i
    lrwxrwxrwx 1 root root      15 Oct  2 08:32 dtb -> dtb-4.7.6-sun8i
    drwxr-xr-x 2 root root    4096 Oct  2 08:32 dtb-4.7.6-sun8i
    -rw-r--r-- 1 root root 3995879 Oct  2 08:33 initrd.img-4.7.6-sun8i
    lrwxrwxrwx 1 root root      17 Oct  2 08:32 script.bin -> bin/nanopineo.bin
    -rw-r--r-- 1 root root 2203811 Oct  2 08:22 System.map-4.7.6-sun8i
    -rw-r--r-- 1 root root 3995943 Oct  2 08:33 uInitrd
    -rwxr-xr-x 1 root root 5794016 Oct  2 08:22 vmlinuz-4.7.6-sun8i
    lrwxrwxrwx 1 root root      19 Oct  2 08:28 zImage -> vmlinuz-4.7.6-sun8i
    root@nanopineo:/boot#
    

    So if I change only the script.bin with bin2fex/fex2bin do these changes be effective in armbian latest kernel builds 4.x?

     

     

    Christos

     

  17. A question to the Armbian gurus here for the new armbian builds with 4.x kernel.

     

    Do these builds take into consideration the DDR frequency for the NanoPi-NEO RAM? or is that too from the OPi board and thus poses a risk factor for us with NEOs?

     

    Should we avoid making armbian builds with kernel 4.x on NEO?

  18. Ok,

     

    Finally I did a Debian latest kernel build and now it works just fine with WiFi

    C:\Christos>ssh christos@192.168.1.131
    christos@192.168.1.131's password:
    setsockopt IP_TOS 16: Invalid argument:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.7.6-sun8i
    System load:   0.94             Up time:       30 sec
    Memory usage:  9 % of 495Mb     IP:            192.168.1.131
    CPU temp:      33Β°C
    Usage of /:    8% of 15G
    
    Last login: Sun Oct  2 09:24:13 2016 from 192.168.1.6
    
    christos@nanopineo:~$ su root
    Password:
    root@nanopineo:/home/christos# iwconfig
    wlan0     IEEE 802.11  ESSID:"OTEf0b338"
              Mode:Managed  Frequency:2.442 GHz  Access Point: A4:7E:39:F0:B3:38
              Bit Rate=150 Mb/s   Tx-Power=20 dBm
              Retry short limit:7   RTS thr=2347 B   Fragment thr:off
              Encryption key:off
              Power Management:off
              Link Quality=64/70  Signal level=-46 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:7   Missed beacon:0
    
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    root@nanopineo:/home/christos# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:8 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1
              RX bytes:1104 (1.0 KiB)  TX bytes:1104 (1.0 KiB)
    
    wlan0     Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
              inet addr:192.168.1.131  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::ea4e:6ff:fe26:ba70/64 Scope:Link
              inet6 addr: 2a02:582:d2e:1100:ea4e:6ff:fe26:ba70/64 Scope:Global
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:150 errors:0 dropped:0 overruns:0 frame:0
              TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:15920 (15.5 KiB)  TX bytes:26776 (26.1 KiB)
    
    root@nanopineo:/home/christos#
    root@nanopineo:/home/christos# ping www.ubuntu.com -c 3
    PING www.ubuntu.com (91.189.90.59) 56(84) bytes of data.
    64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=1 ttl
    =52 time=71.5 ms
    64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=2 ttl
    =52 time=74.7 ms
    64 bytes from www-ubuntu-com.jujube.canonical.com (91.189.90.59): icmp_seq=3 ttl
    =52 time=72.7 ms
    
    --- www.ubuntu.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2001ms
    rtt min/avg/max/mdev = 71.594/73.046/74.773/1.312 ms
    root@nanopineo:/home/christos#
    

    This build, Armbian 5.21,  Debian jessie, kernel 4.7.6, has been build with armbian's build system choosing

    choose an option -> "Full OS image for writing to SD card"

    choose a board -> "nanopineo"

    choose a kernel -> "dev"

    choose a release -> "jessie"

    choose image type -> "Image with console interface"

    and all (NEW) prompts were answered as per their default value

     

    Used with the USB1 exported pins via the DIY board and connector shown above (until of course a proper USB3 image comes)

    Modifications to wifi related files are as described here -> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/.

     

    Hope that will be useful to anyone interested.

     

    Christos

  19. Ok,

     

    Did some 'cheating' here and instead of going into device tree and change the USB1 to USB3

    (I admit I got quite a few gaps still in the dtc/btb/bts thing..)

    I just connected the USB1 from the pinheader expansion on NEO and now the wifi device is visible

    C:\Christos>ssh christos@192.168.1.9
    christos@192.168.1.9's password:
    setsockopt IP_TOS 16: Invalid argument:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
    System load:   0.32             Up time:       27 sec
    Memory usage:  4 % of 495Mb     IP:            192.168.1.9
    CPU temp:      23Β°C
    Usage of /:    8% of 15G
    
    Last login: Sat Oct  1 12:38:33 2016 from 192.168.1.6
    
    christos@nanopineo:~$ lsmod      (Before plug-in of WiFi donlge)
    Module                  Size  Used by
    sun8i_ths               3668  0
    cpufreq_dt              3887  0
    uio_pdrv_genirq         3591  0
    uio                     8953  1 uio_pdrv_genirq
    thermal_sys            48267  2 sun8i_ths,cpufreq_dt
    christos@nanopineo:~$ lsmod      (After plug-in of WiFi donlge)
    Module                  Size  Used by
    rtl8192cu              60341  0
    rtl_usb                 9530  1 rtl8192cu
    rtl8192c_common        40018  1 rtl8192cu
    rtlwifi                58627  3 rtl_usb,rtl8192c_common,rtl8192cu
    mac80211              396612  3 rtl_usb,rtlwifi,rtl8192cu
    cfg80211              237274  2 mac80211,rtlwifi
    rfkill                 12189  2 cfg80211
    sun8i_ths               3668  0
    cpufreq_dt              3887  0
    uio_pdrv_genirq         3591  0
    uio                     8953  1 uio_pdrv_genirq
    thermal_sys            48267  2 sun8i_ths,cpufreq_dt
    christos@nanopineo:~$ sudo ifconfig -a
    [sudo] password for christos:
    eth0      Link encap:Ethernet  HWaddr 02:20:d2:9c:0b:2b
              inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: 2a02:582:d2e:1100:20:d2ff:fe9c:b2b/64 Scope:Global
              inet6 addr: fe80::20:d2ff:fe9c:b2b/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:254 errors:0 dropped:0 overruns:0 frame:0
              TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:28086 (28.0 KB)  TX bytes:28700 (28.7 KB)
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:1 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1
              RX bytes:49 (49.0   TX bytes:49 (49.0 
    
    wlxe84e0626ba70 Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    christos@nanopineo:~$
    

    There is a "wlxe84e0626ba70" wifi device now, but I could get some help here since I know how to set it up in Debian but I'm not so good in Ubuntu, so any hint on how to enable the wifi in this situation is welcome!

    so, how can I set this up? is there any how-to to read?

     

    Christos

     

     

    P.S.

    Here is attached the little patchwork

     

    post-2589-0-15305600-1475336377_thumb.jpg

  20. Ok,

     

    A new build has been done Ubuntu 16.04 with 4.7.6, it looks working.

    I answered the default answer to all the build (NEW) questions.

    C:\Documents and Settings\Christos>ssh christos@192.168.1.9
    christos@192.168.1.9's password:
    setsockopt IP_TOS 16: Invalid argument:
     _   _                   ____  _   _   _
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/
    
    
    Welcome to ARMBIAN Ubuntu 16.04.1 LTS 4.7.6-sun8i
    System load:   0.46             Up time:       3 min
    Memory usage:  4 % of 495Mb     IP:            192.168.1.9
    CPU temp:      31Β°C
    Usage of /:    8% of 15G
    
    Last login: Sat Oct  1 08:41:38 2016 from 192.168.1.6
    
    christos@nanopineo:~$
    
    

    As tk said, the USB obviously needs modification as the connector in NEO is not enabled in this build.

     

    Lets see now what can be done with dtc..

  21. Ok,

     

    To answer my own post, info found here

    -> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/

    due to being identical OPiOne<->NPi-NEO, WiFi RTL8192CU wlan0 its working now ok

    root@nanopineo:/home/christos# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 3a:b7:4e:c9:3a:51
              inet6 addr: fe80::38b7:4eff:fec9:3a51/64 Scope:Link
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0   TX bytes:580 (580.0 
              Interrupt:114
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:8 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:1104 (1.0 KiB)  TX bytes:1104 (1.0 KiB)
    
    tunl0     Link encap:IPIP Tunnel  HWaddr
              NOARP  MTU:1480  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    wlan0     Link encap:Ethernet  HWaddr e8:4e:06:26:ba:70
              inet addr:192.168.1.131  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: 2a02:582:d2e:1100:ea4e:6ff:fe26:ba70/64 Scope:Global
              inet6 addr: fe80::ea4e:6ff:fe26:ba70/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:119 errors:0 dropped:0 overruns:0 frame:0
              TX packets:102 errors:0 dropped:3 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:17160 (16.7 KiB)  TX bytes:16646 (16.2 KiB)
    
    root@nanopineo:/home/christos# ping www.ubuntu.com -c 3
    PING www.ubuntu.com (91.189.89.110) 56(84) bytes of data.
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.110): icmp_seq=1 ttl=
    52 time=69.8 ms
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.110): icmp_seq=2 ttl=
    52 time=71.7 ms
    64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.110): icmp_seq=3 ttl=
    52 time=73.8 ms
    
    --- www.ubuntu.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 69.805/71.794/73.829/1.671 ms
    root@nanopineo:/home/christos#
    

    P.S.

    Now lets see what can be done with recent kernel builds..

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines