Jump to content

darethehair

Members
  • Posts

    20
  • Joined

  • Last visited

Reputation Activity

  1. Like
    darethehair reacted to gounthar in Very Small Platforms - Rockchip 3308 and Allwinner V3s   
    http://www.tuxmachines.org/node/125008
    https://www.cnx-software.com/2019/06/19/rock-pi-s-tiny-sbc-rockchip-rk3308-processor/
  2. Like
    darethehair reacted to schwar3kat in Orange Pi Zero NTP Stratum 1 PPS GPS Server with Armbian OS, Hardware and Software Tutorial   
    Orange Pi Zero NTP Stratum 1 PPS GPS Server with Armbian OS.
    Link to the Tutorial - http://schwartzel.eu3.org/ntp-stratum1.html

    This tutorial uses a 3.3V capable GPS module with PPS output - TOPGNSS GN-701 (u-blox 7) but other similar modules should work.

     
    This tutorial is for the Orange Pi Zero, but will probably work for other boards.

     

    I couldn't easily do a comprehensive hardware and software tutorial on this forum, so I've published it on my web server and linked from here and attached a PDF.
    Link to the Tutorial - http://schwartzel.eu3.org/ntp-stratum1.html

    Tutorial PDF
    ntp-stratum1.pdf

    If you spot any typo's or errors please let me know.
     
  3. Like
    darethehair reacted to Strontium in Debian Stretch Main: Questions   
    I don't know the exact answer to your question, but i do know that stretch will only build with the Mainline kernel or the Dev one.  If you choose "legacy" and then try and build a stretch image it will object.  At least for Allwinner H2/H3.
  4. Like
    darethehair reacted to mantouboji in OPi Zero GPS ntpserver   
    I use the OrangePi Zero.  But it is similar to other model.
     
    It's very simple:
     
    1) use the mainline 4.11.x kernel 
    2) enable the uart1 and pps-gpio in /boot/armbianEnv.txt  like this :
      
    overlays=uart1 pps-gpio param_pps_pin=PA7  
    3) edit /etc/default/gpsd  to use ttyS1 as gps device
    # Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyS1" # Other options you want to pass to gpsd GPSD_OPTIONS="-G -n "  
    4) If you use ntpd,  edit /etc/ntpd.conf like this:
    # GPS Serial data reference server 127.127.28.0 minpoll 4 maxpoll 4 prefer fudge 127.127.28.0 time1 0.135 refid GPS server 127.127.22.0 maxpoll 4 # ATOM(PPS) fudge 127.127.22.0 flag3 1 # enable PPS API  
    5) Or if you prefer crony rather than ntp, install chrony instead of ntp, edit /etc/chrony/chrony.conf , add this to end of it:
    refclock SHM 0 refid GPS precision 1e-1 offset 0.134 delay 0.2 noselect refclock PPS /dev/pps0 lock GPS 6) connect GPS module to UART1 
        GPS      Zero
    ---------------------
       TXD        UART1_RX PIN10
       RXD        UART1_TX  PIN8
      PPS          IO-1  PIN12
     
    7)  use ntpq -p  or chrony sources. to check it.
     

  5. Like
    darethehair reacted to James Kingdon in What's your favorite board(s) and why?   
    Re heatsinks on PC+, I guess depends on your use case - all of mine do, plus a fan It's probably overkill, but I had the parts to hand for the higher power boards and I prefer the simplicity of not getting into thermal throttling (I mostly run benchmarks looking for performance improvements or regressions). I also run overclocked, which perhaps isn't very smart.
     
    With heatsinks but the fan turned off it will gradually climb into the 60 to 70C range, which would be fine.
     
    1.54 GHz 0.000V 69.0C fan off
    1.54 GHz 0.000V 68.0C fan off
    1.54 GHz 0.000V 70.0C fan off
    1.54 GHz 0.000V 70.0C fan off
    1.54 GHz 0.000V 71.0C fan off
     
    Without the heatsinks it will certainly be into throttling with this workload (scalar, mostly integer, no gpu).
     
    Putting the fan back on holds the temperature in the 40s (it's a 12v fan running on the 5v line, so only very light flow and little noise. I use 12v supplies for the fans on the bigger boards)
     
    1.54 GHz 0.000V 47.0C fan on
    1.54 GHz 0.000V 46.0C fan on
    1.54 GHz 0.000V 47.0C fan on
    1.54 GHz 0.000V 48.0C fan on
    1.54 GHz 0.000V 47.0C fan on
     
    Idle temperature (with the fan off) is typically in the low 30s (depending on ambient of course). The fan comes on and off automatically at a threshold I pick to be a bit above idle temp for each board.
     
  6. Like
    darethehair reacted to martinayotte in What's your favorite board(s) and why?   
    Nonne of my OPiPC+ has one ...
     
  7. Like
    darethehair got a reaction from TonyMac32 in What's your favorite board(s) and why?   
    Wow!  I remember while working a co-op job in computer science in 1983, that one of my senior co-workers brought in one of those -- totally impressed me at the time
  8. Like
    darethehair reacted to lanefu in What's your favorite board(s) and why?   
    The CHIP is a cool little board.   Ive got a pocketCHIP which is always surprisingly fun to use as a SSH remote control.
     
    i gotta give nextthing credit for completeness.
  9. Like
    darethehair reacted to martinayotte in What's your favorite board(s) and why?   
    OrangePiPC+ is way much better than CHIP. One of the reason is that CHIP doesn't use eMMC but plain NAND.
     
  10. Like
    darethehair reacted to zador.blood.stained in Kernel Option Requests?   
    We are trying to keep the config balanced for different use cases (server, desktop, multimedia, IoT), and if a kernel option has a recommended value it would be best to use it.
    config NO_HZ_IDLE bool "Idle dynticks system (tickless idle)" depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS select NO_HZ_COMMON help This option enables a tickless idle system: timer interrupts will only trigger on an as-needed basis when the system is idle. This is usually interesting for energy saving. Most of the time you want to say Y here.  
    Usually if there is a patch foir the mainline kernel, then somebody needs to maintain this patch, adopting to kernel changes, otherwise this patch will be thrown out if it doesn't apply cleanly or breaks the compilation.
     
    The most reasonable solution in my opinion for this rather unusual use case would be to compile the kernel with required changes and patches, put the kernel packages on hold and forget about it unless you require a newer kernel for some reason.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines