Tido

Userlist access
  • Content Count

    1004
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Tido reacted to Werner in Improve 'Support over Forum' situation   
    I am torn about this. For various you may not be able to generate such a link. Like network issues (you still get the output but not the special link), I/O issues or boot issues.
     
     
  2. Like
    Tido reacted to Aurimas in Pine64+ on 4.19.13-sunxi64: rcu_sched self-detected stall on CPU   
    armbianmonitor -u output is here http://ix.io/1ytO
  3. Like
    Tido reacted to JMCC in [Development] RK3399 media script   
    It's baking in the oven... 
  4. Like
    Tido got a reaction from sfx2000 in Adafruit CircuitPython   
    35C3 - MicroPython – Python for Microcontrollers  https://www.youtube.com/watch?v=xCPnOxWxHIc 
    at min 5:30 you see also Adafruit, haven't seen it completely, but stumbled across it
     
  5. Like
    Tido got a reaction from sfx2000 in picocom login on MacOS   
    I use "screen"  instead of  picocom. Have you ever tried this software?
  6. Like
    Tido reacted to chwe in RockPi 4b 'board bring up'   
    As most of us were in the beginnings..
     
    I don't guarantee but I think it's not that easy to fry something with a wrong devicetree.. It's a way easier with connecting random crap to the pin-header.
     
    Since you want to get closer to group 1 let's give an example:
     
    That's the original DT for the RockPi4b (4.4.x kernel) spoiler cause it just messes up to show the whole one for everyone (https://github.com/radxa/kernel/blob/release-4.4-rockpi4/arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts):
     
    the first few lines after comment tell us which other DT files are included here e.g. (rk3399.dtsi):
    #include <dt-bindings/pwm/pwm.h> #include <dt-bindings/input/input.h> #include "rk3399.dtsi" #include "rk3399-linux.dtsi" #include "rk3399-opp.dtsi" basically just another 'layer' of describing hardware, since a lot of stuff is shared with all rk3399 based boards this stuff is usually described once there and the nodes are used again and again for every board.
     
    The nodes after it describe the hardware and how it is connected (also partly software e.g. there are multiple UARTs available, a node has to tell the kernel which one should be used to output the debug console).
     
    Now let's look at such a node:
    fiq_debugger: fiq-debugger { compatible = "rockchip,fiq-debugger"; rockchip,serial-id = <2>; rockchip,signal-irq = <182>; rockchip,wake-irq = <0>; rockchip,irq-mode-enable = <1>; /* If enable uart uses irq instead of fiq */ rockchip,baudrate = <1500000>; /* Only 115200 and 1500000 */ pinctrl-names = "default"; pinctrl-0 = <&uart2c_xfer>; }; the compatible part is the first one which is interesting cause it gives you some hints where you get further information. (https://github.com/radxa/kernel/blob/release-4.4-rockpi4/Documentation/devicetree/bindings/serial/rockchip_fiq_debugger.txt)
    From there you get most of the information out what this node does and how it can be configured.. E.g. for the fiq node, it could be worth to set baudrate to 115200 cause this is the common baudrate for all SBCs (except rockchips which often favor higher baudrates for whatever reasons ). So obviously when you connect an USB-UART you've to set it to 1500000 not the default 115200 (keep in mind, if it's patched in the kernel, it should also be patched in u-boot, otherwise things get messy).
     
    That's just a short introduction and you've to read a lot of stuff until all this stuff makes sense. Maybe I write something about the buildsystem tomorrow.
  7. Like
    Tido reacted to Neil Armstrong in Le Potato / C2 / K2 4.19 LTS testing thread   
    @TonyMac32I found a regression, can you test this fix ? https://github.com/superna9999/linux/commit/b9edb9c9eec654ba57f8da7966e4b1b81a6d7c7b
  8. Like
    Tido reacted to TonyMac32 in RK3288 Media Script (TinkerBoard)   
    Wait, what? Not much faster? If you say at burning energy during operation, I agree; otherwise, I think every benchmark on the planet is against you. I have 2 Pi3's, I can't use them because they are slower than very nearly every other board I possess, they collect dust. My Pi2 serves to play music for me.

    Sent from my Pixel using Tapatalk


  9. Like
    Tido reacted to vlad59 in when did you last donate to the armbian project ?   
    Just did right now, thanks for the reminder
  10. Like
    Tido reacted to zador.blood.stained in board support - general discussion / project aims   
    And also Terms of Use / Community guidelines should be linked somewhere in plain sight. Right now it can be accessed when registering, and even there it is not clearly shown as a link. IMO it should be on the top menu row as it is more important than i.e. Privacy policy that exists mostly for legal reasons.
     
    Edit: It's also on the bottom bar, but it will be hidden after you click "Accept", looks like by a specific cookie.
     
    Edit 2: Now that I'm looking at those (Registration Terms specifically) - they should be a numbered list instead of a bullet list, and we should probably add a new rule "Try to stay on topic defined by the starting post or developer posts in the thread. Off-topic posts that derail the discussion may be hidden, moved or deleted."
  11. Like
    Tido reacted to lanefu in board support - general discussion / project aims   
    Quick suggestion --- also add donate link  in plain site at top of forum....    

    I was further along in the thread, and I impulsively decided to donate, and so I scrolled to top of forum and no link so i had to work for it ;P
  12. Like
    Tido reacted to NicoD in who wants Flash Player on armbian?   
    That`s a joke. Learn to laugh
    Don`t joke about C, that`s serious stuff. (again...)
    Greetings
  13. Like
    Tido reacted to TonyMac32 in RK3288 device tree overlays   
    I've broken these things down (perhaps too far, but I will give a case for it, and we can all discuss), here are the overlays:
     
    - ds1307
    - i2c1
    - i2c4
    - spi0
    - spi2
    - spidev0
    - spidev2
    - uart1
    - uart2
    - w1-gpio
     
    The DS1307 was simply pulled from ASUS as a simple test overlay while I was working through implementing the scripts.  it can be jettisoned for all I care.
     
    These are all written with only the Tinker Board in mind, of course they are all SoC-centric other than the 1wire and ds1307
     
    "Pi" ports:
     
    - i2c1 is the "Pi" I2C channel.  Make it configurable in case you just want the GPIO
    - i2c4 is the "Pi" ID I2C channel.  Make it configurable in case you just want the GPIO
    - spi2 is the "Pi" SPI channel. Makes it configurable in case you want just the GPIO
    - spidev2 enables the user space spidev driver with 2 chip selects for spi2
    - uart1 is the "Pi" UART position. 
     
    Tinker ports:
     
    - spi0 is the "extra" spi channel on Tinker, on pins 11/13/15/29/31.  Disabled by default, it occupies the same pins as UART4  *Not Pi Compliant in location*
    - spidev0 enables the user space spidev driver with 2 chip selects for spi0
    - uart2 is the debug port for Tinker.
     
    There are some interesting extra features exposed on some of the pins (PWM/etc) that I would like to experiment with, we'll see. 
     
    I have pulled the spi out as an overlay separate from the peripheral attached to it, my thought is, there may be 2 unrelated devices tied into the board on each chipselect that the user has their own overlay for.  (So up to 4 devices on hardware SPI)
  14. Like
    Tido reacted to martinayotte in Lichee Pi zero   
    When I copy/pase links from AliExpress or eBay, I always shortening them manually to before the first "?" and check if link still relevant ...
  15. Like
    Tido reacted to balbes150 in [RFC WIP] Changes for boards and features implementing   
    Yes, this also happens to users (and quite often). When they run the update and as a result, some of the features they used are broken (you have to remove conflicting packages). They have to either write a bug report and wait for a fix, or roll back to previous, compatible versions of packages. When you manually update the system writes, if there are conflicts and the user decides what functions are important to him and how to do (what to remove and what to leave). In an automatic build, you cannot provide all the behaviors and always use the default.
    It is possible you that the online repositories used in the build are usually in a stable state (already updated or not yet updated) when you run the build. That is, the time of the build system is well synchronized with the work of updates in network repositories.
     
    IMHO I suggest for all versions of images where DE is used to use the standard approach from "adult" systems. The source image must use some kind of login Manager (for example, lightdm). This corresponds to the logic of safe operation and is a common (familiar) option for users moving from PC to ARM. The current state of Armbian and the hardware it runs on has already become quite Mature and capable of working on an equal footing with the PC. If the user wants to make a autologin or use "nodm" - he will do it yourself (good manuals for this is more than enough). In the server options of images, the default should not be any managers of the entrance.
     
    In addition. I would put the u-boot Assembly in a separate process, with mandatory testing for the correctness of the assembled version on the intended devices. And only after that place the packages in the repository for Assembly by others or for use by users. U-boot is an important element for the safe use of the device (this is especially true for devices with built-in memory, where it is very difficult to fix not correctly recorded in memory u-boot).
  16. Like
    Tido reacted to jock in Integrate WireGuard into kernel   
    Yeah you can integrate wireguard into the kernel, but you can also use DKMS framework to let it being recompiled each time a new kernel is installed.
    Wireguard already comes with a small configuration file for DKMS, just follow a tutorial on how to install and setup DKMS on your machine (which is quite easy, just few steps) and register wireguard module and you're done.
  17. Like
    Tido reacted to TonyMac32 in pyGPIO - A 'more general' python GPIO library   
    Bumped/Pinned like the others.  If I'm going to be in the trenches on these boards, may as well make it count.  I want to see this, circuitpython, Larry Bank's and sgjava's libraries all in a subforum (and any I'm missing, authors step forward and be counted.  ;-)
     
    Also @chwe tossed you a PR for Tritium H2+/H3 and your own Blinky example. 
     
  18. Like
    Tido reacted to chrisf in Reboot:system halted instead of proper shutdown   
    The manufacturer of the board isn't paying Armbian. Armbian is a group of volunteers making a Linux distribution.
    They're also not paying sunxi. sunxi is a group of volunteers making a Linux kernel for Allwinner SoC's.
     
    If you want to get mad at someone for the poor software support for your board, get made at Xunlong, the company you actually paid for a product you feel is inadequate.
    Don't get mad at the people spending their free time making things better for you, without you giving anything back to them.
  19. Like
    Tido reacted to sgjava in Adafruit CircuitPython   
    https://github.com/sgjava/userspaceio supports C, C++, Python and JVM (Java, Scala, Koltin, etc.). Do we really need another Python lib besides WiringPi and RPi.GPIO? Also, I have non-root access working for pretty much everything.
     
    Another thing, from looking at the CircuitPython site it appears to only support micro controllers at this point, not a full blown SBC. For this type of stuff I'm using NodeMCU with Lua which is mature and is hard to beat from a price/performance/usability perspective.
  20. Like
    Tido reacted to TonyMac32 in New official Raspberry Pi 3 Ubuntu 18.04.1 LTS (Bionic Beaver) Beta   
    Honestly that's the only Pi I use for anything.  It is more stable than the 3 for video in my opinion.
  21. Like
    Tido reacted to manuti in adafruit ♥ armbian = CircuitPython on Linux and Orange Pi Make hardware and interf   
    Nice to see adafruit recommending armbian in his projects:
     
    https://learn.adafruit.com/circuitpython-on-orangepi-linux/initial-setup
  22. Like
    Tido got a reaction from pazzoide in Banana PI - ghostly swap   
    RAM and compressed
  23. Like
    Tido got a reaction from NicoD in Kickstarter: Allwinner VPU support in the official Linux kernel   
    Both the API and our driver were merged in time for...  more over at: 
    https://bootlin.com/blog/allwinner-vpu-support-in-mainline-linux-november-status-update/
     
  24. Like
    Tido reacted to TonyMac32 in BananaPi R2 (.csc mt7623 as new boardfamily)   
    https://www.merriam-webster.com/dictionary/masochism
     
    (I would recommend sticking with definition 2.  Although it's tough these days to know for sure...) 
  25. Like
    Tido reacted to TonyMac32 in Daily (tech related) news diet   
    I try to eat organic when available and cost effective.  I also grow my own vegetables in the summer.  I also cut all the high-fructose corn syrup and a lot of sugar out of my diet, unless I need something to mix my rum or whisky with. 
     
    Playing with genetics seems a risky game, but then again scientists love diving into the unknown and the loud ones live lives of pure hubris, thinking their tiny addition to the sum of humanity's knowledge somehow makes them a god.