pfeerick

Moderators
  • Content Count

    146
  • Joined

  • Last visited


Reputation Activity

  1. Like
    pfeerick reacted to Igor in H6 boards: Orange Pi One Plus, Orange Pi 3 Plus and Pine H64   
    True, I notice that USB3 port was not working. I was happy that it booted in the first place. I already merged into our main sunxi DEV branch (attached back to upstream master) and will try to remake this with a working USB3.
  2. Like
    pfeerick reacted to Igor in Next major upgrade v5.60   
    You need to be an expert to see this  Add EXPERT="yes" to the configuration.
  3. Like
    pfeerick reacted to chwe in board support - general discussion / project aims   
    Let's try it with an example and lock what happens/if it works...   Such a 'project manager' needs a background in the topic otherwise it's similar to marketing monkey writes product description for *random device*. I suggest we take @zador.blood.stained proposal as a test:
    Is it possible to write a proposal what should be done out of it?
     
     
    IMHO, it can't be a goal that you have to test all images on your own, otherwise armbian has to reduce the supported boards to much less boards. If you look into DL statistic, there are enough people downloading our images, there must be some interest from the community to report bugs (update or fresh download). Can we start with a 'testgroup lite'? IMHO most important (cause most annoying) is to avoid that the device is not bootable after update. As long as you have SSH access via ETH to the device, broken things can be fixed or at least, a backup of the data can made (I agree you should backup your system before the update - but to be honest, we have to accept that people don't do it). To avoid flooding the forum with a lot of junk from the testers group a small webservice might help:
    With a clear statement that we don't suggest that you're test without having a serial console at hand (seems that a lot of user don't think it is necessary to have a usb serial device at home when playing with SBCs - maybe we should 'educate' our 'customers' also in this field....  ). 
     
    Is it possible to have a 'board specific' update mechanism? E.g apt-update/upgrade only updates kernel/u-boot only if it's somehow on a 'positive list'? 
     
    Internet of shitty Things is the 'new' buzzword...  Since people like @Larry Bank and @sgjava strongly push the GPIO issue, we might have a good solution in 2018.  To avoid  more load for the maintainers and keep Armbian as general as possible, I suggest to solve it similar to the OMV project. Means that we can provide a post installation script for a 'ArmbianIoT' but IMO we should avoid providing it in 'standard Armbian'.
     
    A few questions:
    Do we have a nightly desktop policy? Why do we provide desktop in nightly images? Does it make sense to provide such images as long as we can't provide 'basic stability'?
  4. Like
    pfeerick reacted to jernej in Kickstarter: Allwinner VPU support in the official Linux kernel   
    While they still don't cooperate with open source community as good as Rockchip, they at least are more cooperative. I asked for HDMI/DE2/DE3 documents and received all of them. Someone else asked about AC200 doc and also receive it. Or better said, they were uploaded to linux-sunxi.org. I would say that is a very good improvement.
  5. Like
    pfeerick reacted to Tido in Kickstarter: Allwinner VPU support in the official Linux kernel   
    beating a dead horse is not going to get you anywhere.
    I rather support Amlogic or Rockchip
  6. Like
    pfeerick got a reaction from Tido in IoT with an OrangePi Zero: Node-Red + Mosquitto + ESP8266/NRF24l01   
    Right, why did you post to this topic while I had it open? I think I need to go check my network security now!   
     
    Anyway, indeed... if this is node red and MQTT running, there is nothing to stop an ESP8266 with screen... say a 1.3" OLED or a 2.2" TFT, etc, from also polling the orange pi / etc and showing the data. 
     
     
  7. Like
    pfeerick reacted to Tido in IoT with an OrangePi Zero: Node-Red + Mosquitto + ESP8266/NRF24l01   
    and what does stop you of doing so ?
  8. Like
    pfeerick reacted to chwe in IoT with an OrangePi Zero: Node-Red + Mosquitto + ESP8266/NRF24l01   
    I finally gave up playing arround with the MySensors lib.  Main reasons are:
    For every example they use predefined libs (DS18b20, DHT etc.) sometimes no support for updates of these libs.  Things like "This example uses a modified version of the external DTH library, which is included in the MySensors external examples." indicates to me, that this lib has some 'problems', otherwise this should work with the standard DHT lib.  The hole project seems a little bit predefined to me: Use the nodes we think you need, and since I'm not interessted in their nodes it does not make sense for me.  They presented so many examples of nodes, but I never found a example like: how to build your one node (for IoT stuff, where every one, including me, thinks that he would have a better idea how his node should look like, this is IMO the most important tutorial that you should have on your webpage).  I tried to get a DHT11/DS18b20 working on an arduino nano just to give you an example that this setup works, but I failed several times.  Since im not really interessted in the MySensors stuff anymore I would not waste my time for this. If someone tries it and it works, please add it to this thread, it would be cool for others which are interessted in the MySensors stuff!
     
    @pfeerick the finally made it! (ok, not for the toilett, but would not be hard to adapt this..  )
     
    Found on CNXSoft that  BLE is now able to implement mesh networking.  If this will be implemented on the cheap BLE modules (e.g. CC2541) this would be a game changer for IoT thingies... 
  9. Like
    pfeerick got a reaction from Naguissa in Armbian configuration utility   
    Yup, that's what it says at the bottom of the login banner...
     

  10. Like
    pfeerick reacted to Naguissa in Armbian configuration utility   
    armbian-config
     
    Maybe...
     
    Enviado desde mi Jolla mediante Tapatalk
     
     
     
     
  11. Like
    pfeerick reacted to mikemoy in Armbian configuration utility   
    I was informed about Armbian today, and so far from what I am reading it looks very promising.
    I was on the Armbian configuration utility doc page:
    https://docs.armbian.com/User-Guide_Armbian-Config/
     
    But it says nothing on how to start it. whats the command for it ?
     
  12. Like
    pfeerick reacted to ZupoLlask in Pine64 wont boot after update   
    I've just tried to reproduce the problem with a 15cm cable... It still happens easily.
     
    In my case, I don't think it's related with power supply but I'll try to clear that out in the lab.
     
    If it was,  it should happen consistently with several USB devices overloading the power supply with the 4 CPU cores at 100% each, which never occurs.
  13. Like
    pfeerick reacted to ZupoLlask in Pine64 wont boot after update   
    I brought a TTL adaptor from my company's lab and now I can confirm I'm having precisely the same problem described in the OP.
     
    I also found out this thread, which can be useful for other to better understand this issue: https://github.com/longsleep/build-pine64-image/issues/51
     
    As I doubt I have a problem with the power supply I'm using, for now I decided to test another USB cable.
    After that, I'll make proper testings of all the components involved if I need it...
  14. Like
    pfeerick reacted to Владимир Титаренко in Supporting smb2.1 or smb3 protocols for mount.cifs   
    I found one simple way, that helps me
    I use armbian-config utiility, System -> Switch -> next
    root@orangepipc:/media# uname -a Linux orangepipc 4.13.16-sunxi #20 SMP Fri Nov 24 19:50:07 CET 2017 armv7l armv7l armv7l GNU/Linux root@orangepipc:/media# mount -t cifs //192.168.1.5/D /media/share_test/ --verbose -o user=user,pass=verystrongpassword,vers=2.1 mount.cifs kernel mount options: ip=192.168.1.5,unc=\\192.168.1.5\D,vers=2.1,user=user,pass=******** root@orangepipc:/media# ll /media/share_test/ total 16196 /* List of files was ok */ Interesting moment: MAC address of ethernet card changed after change kernel
  15. Like
    pfeerick reacted to reptile in orange pi zero led   
    I was wondering about the same and i answered it here:
     
    For anyone landing here and can't find answer..
     
  16. Like
    pfeerick reacted to reptile in Trigger LED on Orange PI Zero Plus   
    ok, 2nd day and starting to better understand this, will explain it loudly for myself and anyone else:
     
    Though the answer was there from the beginning, too bad that it wasn't clear for meL
    http://linux-sunxi.org/GPIO
     
    First we need to "create" or "attach" the GPIO port using this command:
     
    sudo echo XX > /sys/class/gpio/export The XX is a complex calculation of the GPIO:
     
     
    so for Orange PI Zero plus 2 H5 (should be same for h3/h2) the RED led would on GPIO PA17 and GREEN LED on GPIO PL10  (Info from here: http://linux-sunxi.org/Xunlong_Orange_Pi_Zero_Plus_2 )
    The calculation would be (Letter A is 1, the "P" not counted): (1 -0) * 32 + 17 =  17  (For RED LED) while for Green LED: (12 - 1) * 32 + 10 = 362
     
    sudo echo 362 > /sys/class/gpio/export sudo echo 17 > /sys/class/gpio/export  
    Now lets check the status of the GPIOs:
     
    cat /sys/kernel/debug/gpio gpiochip1: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-9 ( |reset ) out hi gpio-14 ( |sysfs ) out hi gpio-17 ( |sysfs ) in lo gpio-110 ( |sysfs ) in lo gpio-166 ( |cd ) in hi IRQ gpio-204 ( |usb0_id_det ) in lo IRQ gpiochip0: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-358 ( |? ) out lo gpio-362 ( |sysfs ) in lo  
    The GPIOs should be "out" direction (i guess because we are outputting to it), so lets fix them:
    sudo echo out > /sys/class/gpio/gpio362/direction sudo echo out > /sys/class/gpio/gpio17/direction  
    Now that the direction is correct, lets try to switch them on or off:
    sudo echo 1 > /sys/class/gpio/gpio362/value sudo echo 0 > /sys/class/gpio/gpio362/value sudo echo 1 > /sys/class/gpio/gpio17/value sudo echo 0 > /sys/class/gpio/gpio17/value  
    Now that the LEDs are controllable, The  next challenge would be adding some rhythm to the led per hardware occasions such as heart beet, read/write..  i hope it will be easier than above
  17. Like
    pfeerick reacted to TonyMac32 in Info: Rockchip are phasing out sales of the RK3288   
    Better hope a certain world leader doesn't get wind of this:  "CNX is fake news!! SAD!!"  
  18. Like
    pfeerick reacted to TonyMac32 in Info: Rockchip are phasing out sales of the RK3288   
    That makes me feel so much better... 
     
    It just seemed a rather extreme jump, given the usual context of this board ("I bought an $8 thingy and it's not as powerful as my laptop... WHY?!?!?!")
  19. Like
    pfeerick reacted to TonyMac32 in Info: Rockchip are phasing out sales of the RK3288   
    Oh my, have they fixed all the reboot hackery?  Also see:  Giant Heatsink.  
     
    And no, even in automotive where last time buys are common, no one is stocking to support "up to" 2 million pieces without guarantees that the parts will be used.  I wonder if that vendor had a falling out with Rockchip.
  20. Like
    pfeerick reacted to botfap in Info: Rockchip are phasing out sales of the RK3288   
    You sure about this?
     
    One of our clients ordered 85K rk3288 boards to be designed and manufactured to rk-miniarm spec in August and they have contractual availability to buy upto 500K per year through till July 2021. Their OEM would have to hold a lot of rk3288 SoC stock to meet those obligations for a discontinued chip over 5 years.
  21. Like
    pfeerick reacted to chwe in Orange Pi One is not booting from SD Card....   
    https://www.ubuntu.com/download/server
     
    if you only need console... The ISO is ~750mb, don't know how much space it needs on an SD-Card but I think it's less than 8GB...  maybe you need to resize the FS by hand after its (don't have such sticks)... 
  22. Like
    pfeerick reacted to guidol in ESPTerm - a nice Idea fore the Debug-Port   
    Yesterday I came across the following - for me - fine project (Demo-Page):
    ESPTERM Release 2.3.0 Cricket
    https://espterm.github.io/term.html
     
    GitHub-Page:
    https://github.com/espterm/espterm-firmware
     
    Downloads:
    https://github.com/espterm/espterm-firmware/releases
     
    Its a VT100-Webpage-Terminal on a ESP8266-Microcontroller which opens a Accesspoint.
    You could connect via this VT100-Webpage-Terminal to the TTL-Port of the ESP8266.
     
    TTL-Connection is done (like allways in TTL-Connections) with RX,TX and GND
     
    I connected my Orange Pi R1 via TTL and 115200 Baud and could "work" at a (max.) Terminal-Size of 80x25
    (80x25 is max. in the downloadable binary - if you do compile by yourself mor is possible.... 132x50 would be fine )
     
    So if you have a misconfigured Network-Connection (missed the /24 in the IP of the server in nmtui) and you dont want to use a USB-serial-Dongle because every Dongle wats its own driver  - here a second solution


  23. Like
    pfeerick reacted to vlad59 in 5.35/5.36 bug / questions collection   
    I also have the problem. I tried some quick debugging and watched some kernel logs about network / a20 but found nothing so far.
  24. Like
    pfeerick reacted to Igor in Pine64+ & Pine64so - uboot - no ethernet   
    A network was working in 4.13.y and we don't have another kernel for this board/chip. If you refer to recent Allwinner 4.4.y ... waste of time. There is no instant solution except the already mentioned legacy kernel.

    Edit: btw this - what you ask - is u-boot related and I don't know if we have network support there yet.
  25. Like
    pfeerick got a reaction from alexparser in How to replace the welcome message at login?   
    Login/welcome messages come from the scripts in /etc/update-motd.d, so you can remove/change them as you wish.  If you didn't want the sysinfo, tips,update nofications and armbian-config messages, you can just remove the executable bit (i.e. chmod -x) from the four scripts responsible for those messages (30-sysinfo 35-tips 40-updates 41-armbian-config), and then you'd be left with just the board name. You can also turn that off by disabling the 10-header script. You can also make your own, and have them run and display on login (if properly written and the executable bit is set). 
     
    The easiest way to run something before login is to use crontab. i.e. run crontab -e, and then add a new @reboot command for a script that will run after the device has rebooted, and before login.  See this page for some more information and examples.