MitchD

Members
  • Content Count

    35
  • Joined

  • Last visited


Reputation Activity

  1. Like
    MitchD reacted to Igor in Testers wanted Real Time Kernel image builds for H3 boards   
    https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.11/

    No idea if it works.
  2. Like
    MitchD got a reaction from StuxNet in Testers wanted Real Time Kernel image builds for H3 boards   
    You can find a 4.11.9 rt patch here: https://www.kernel.org/pub/linux/kernel/projects/rt/4.11/older/
     
    I have a vanilla mainline kernel with that patch applied and it works for me. I think armbian uses a separate github directory, so you might need to tweak the patch. 
  3. Like
    MitchD reacted to StuxNet in Need help for Orange Pi Zero OS Installation   
    Ummm?... because Q4OS only supports Pinebook, Pine64 and Raspberry Pi as per their downloads page. Unless I'm missing something. Even if I am, that would mean their "ARM port" download is trying to do something similar to Armbian by being compatible with multiple devices. Aside from chromebooks, tablets, etc... I think you'd be hard pressed to find an argument for using Q4OS over Armbian especially for OPiZero. Maybe that's just me though.
     
    https://q4os.org/downloads1.html

    So what's your reasoning as to why you opt for Q4OS over Armbian?
  4. Like
    MitchD got a reaction from StuxNet in Buildroot realtime image for nanopi neo   
    It looks like your patches applied correctly, comparing your images to my make menuconfig shows its the same. I'm not sure why you're not getting ethernet. Once your board boots up, if you type "ifup eth0" it should come up. Also check the /etc/network/interfaces file to make sure eth0 is define, like this:
     
    auto eth0
    iface eth0 inet dhcp
           wait-delay 15
     
    I tested my mainline image on an orangepi zero and it booted right away with ethernet, so I'm not sure what is wrong. If you change out your SD card and power supply or USB cable you may have luck.
     
     
  5. Like
    MitchD reacted to zador.blood.stained in Anyone know the type of ribbon cable used for OPi Camera modules?   
    Orange Pi schematics list this connector as "FPC24-05PH-BOT", so I would assume it is FPC 24 pin 0.5mm pitch bottom contacts.
  6. Like
    MitchD reacted to martinayotte in backing up SD to filename.img   
    Using "truncate" with the "endsect" number shown by fdisk after gparted shrinking.
    Here is the sequence :
    sudo modprobe loop sudo losetup -f sudo losetup /dev/loop0 myimage.img sudo partprobe /dev/loop0 sudo gparted /dev/loop0 sudo losetup -d /dev/loop0 fdisk -l myimage.img sudo truncate --size=$[(endsect+1)*512] myimage.img  
  7. Like
    MitchD got a reaction from gatinho in Buildroot realtime image for nanopi neo   
    Ethernet drivers exist in my image. I tested it before I uploaded it.  Your image uses a mainline image, and I provided ethernet patches for that in a post above.  Apply the patches and enable them in the defconfig and your own kernel should have them. 
     
    You set the ethernet driver by doing `make linux-menuconfig`, going to Device Drivers,  Network Device Support, Ethernet Driver Support, and selecting "SUNXI Platform Network device drivers", and the three options below that.
     
    The only way I know to add drivers to a linux kernel is to build them when you build the kernel. There is no need to download my github and try it, because I gave you the compiled kernel with the drivers in it. If you meant wifi drivers, then you would download mine and patch the kernel to add the drivers, and select those drivers from the `make linux-menuconfig` command, and build the kernel that way. 
     
    When I put the project together initially, I had a working mainline vanilla boot for the nanopi neo, and I modified armbian's sources to create a legacy buildroot image with realtime capabilities for the nanopi neo. Any use outside of that is up to the end user.
     
    I'm not familiar with wireless drivers and I really don't want to spend the time to get them working.  The only way I would get them working is if  @Igor decided there should be a minimal buildroot image for every board Armbian supports, and I don't think that is likely.  
     
    If you can't find your device on your subnet, you can try Wake Me On Lan for windows.  It will show you every device your computer can ping. If you use linux, nmap and arp should do just fine. 
     
     
     
  8. Like
    MitchD reacted to zador.blood.stained in Please repair RT-KERNEL patches   
    What kernel are we talking about (since this is posted in the "mainline" section)?
     
    For the legacy - pull requests with fixes are welcome, at this point it's unlikely that the legacy kernel will receive any significant changes/patches.
    For the mainline - you have to find RT patches that match the available mainline kernel version (currently it's 4.11.5).
  9. Like
    MitchD reacted to Igor in Please repair RT-KERNEL patches   
    From a current perspective, all I can do is to remove this partially working / invalid patch ... to suppress questions  I am tired to write excuses - we are just a few, so don't expect this to be solved anytime soon / up on your needs  Our lists are full of such "just this" cases and basic functionality is our core interest in the first place. Perhaps somebody already fixed those patches and they "only" need to find a way to our sources?
  10. Like
    MitchD reacted to StuxNet in Buildroot realtime image for nanopi neo   
    This guy is experiencing the same exact detailed issue as you.
    Attempted to create kernel. Kernel doesn't boot. Kernel complains of Ethernet missing. End user wrote image with `dd` command.   
    The only difference is that OP is using OPi Zero Plus, not OPi Zero.... big woop. Simply try with Etcher, report back. That might be hard though without a UART adapter... get MitchD to do it for ya xD

    Sup MitchD? Keep up the good work.
  11. Like
    MitchD reacted to StuxNet in I made an email/SMS IOT thing. What does the Armbian forum think?   
    Tinkering with API's is fun. Always wanted to allocate the scripts and tools made over time and allow quick access to the data they can provide. Never liked the idea of leaving a power hungry Desktop running to have access to it and am too paranoid to leave any SBC (FTP/WebServer) connected to the World Wild West for too long. As seen with the Mirai Botnet/DYN attacks. So my answer was to have something low power (SBC and armbian) that was at least 'secure enough' for me to let it interface with the world.

    So this was made: https://github.com/BiTinerary/PersonalAPI


    In a nutshell this is how it works:
    Scripts on an OPi Zero that make API calls, scrape web data or w/e. I want to collect this data, check a sensor, trigger... from my phone. SMS/MMS an email to users inbox containing a keyword. Weather, Beer, Water plants, etc... The script uses a dictionary.txt file to constantly check the inbox for keywords. When one is found, it executes the key's respective value. ie: Key = Forecast. Value = Weather API call. Any returned value or echoed statement is passed as a string and sent as a reply, back to my phone.  
    The only security concern is that anyone can fire off one of these scripts by sending a spoofed message, as a specific address, containing a predefined keyword. This might be a big security concern for some but personally, it's negligible. Not only do you need to know the address to spoof, keyword to send, parameter to pass, syntax to use, etc... but you would only succeed in entering a sandbox that I control.

    Not to mention, SMS two factor authentication can be implemented later on and message content can be obfuscated to oblivion.
    The sky is periwinkle but the grass is still green.

    Anyways... Maybe someone can use the source code. Hopefully someone can use the source code. What are the thoughts of the community? Am I off my rocker? Suggestions on what you'd like to be add? Always looking for new ideas and projects.
  12. Like
    MitchD reacted to StuxNet in Armbian fails to boot after build   
    cyclic redundancy check
     
    I've never built my own kernel (I let Igor do that for me) but I know a bad 'hard drive' when I see one, from my computer repair days.

    BAD CRC = cyclic redundancy check error

    Make sure your SD card image writing software is 'approved' to work with armbian. ie: Etcher
    This is (as far as I know) the only Armbian 'approved' method. Likely because Etcher verifies the image after writing, by default. Whereas dd and Win32Disk Imager (uses dd) don't require verification, of what it just wrote.

    So..... bad SD card? Prove it is/isn't then come back asking for help.
     
    Otherwise, I've received bad CRC errors due to power cables going bad at pain points. I think. Might of been that I was writing using Win32 at the time xD IDK for sure because I immediately tried fixing both birds with one stone as opposed to troubleshooting individually.
    So double check that Power Supply if you haven't already. If you haven't already, see 0, 1 and 2 links in my signature. ;D
  13. Like
    MitchD reacted to gatinho in Buildroot realtime image for nanopi neo   
    Thanks @MitchD, I will surely try what you sayd. Did you plug a monitor through the TV out?.
    For copying the SD card, I am using this command: sudo dd.
    The eth0 might be, beause I changed the etc/network/interfaces, to get an static ip, I will change it back and see what happends.
     
    I will try what you say tomorrow, and comment back.
    Thanks
  14. Like
    MitchD got a reaction from StuxNet in Buildroot realtime image for nanopi neo   
    The kernel you supplied has no drivers, so I'm willing to bet there will be nothing in the TV out. 
     
    The ethernet doesn't exist in the dtb, so it will not load it in the kernel. 
     
    I have created a legacy image for you, which has basically everything working but the wifi. It has python and ssh like you wanted. The login is root,  password is root. 
     
    For TV output, you'll want to change the fex file, as described here. Since there is no xserver, I'm not sure what you're going to be displaying on the TV. 
     
    I hope this helps. 
     
    https://drive.google.com/file/d/0B42tAZ6A-UbDV3dFTHhlQnVsdVE/view?usp=sharing
  15. Like
    MitchD got a reaction from gatinho in Buildroot realtime image for nanopi neo   
    I'm using puredata with alsa, and i have a latency of about 8ms. I haven't dug down and messed with drivers yet, but I hope to reduce that. I may add Jack in the future. 
     
    I'm gonna guess you built it from linux 3.4 sources, right? In your boot partition, there is no script.bin. You'll need that instead of the dtb for the legacy images. I would also suggest getting a USB to serial device and plugging directly into the board via the headers to get boot output. It is extremely useful in cases like these. 
     
    I will try with my orange pi zero tonight. 
  16. Like
    MitchD got a reaction from StuxNet in Buildroot realtime image for nanopi neo   
    I'm using puredata with alsa, and i have a latency of about 8ms. I haven't dug down and messed with drivers yet, but I hope to reduce that. I may add Jack in the future. 
     
    I'm gonna guess you built it from linux 3.4 sources, right? In your boot partition, there is no script.bin. You'll need that instead of the dtb for the legacy images. I would also suggest getting a USB to serial device and plugging directly into the board via the headers to get boot output. It is extremely useful in cases like these. 
     
    I will try with my orange pi zero tonight. 
  17. Like
    MitchD reacted to giri@nwrk.biz in [Program] Move Composite AV Video Output to fix Overscanning   
    Hey folks!
     
    On monday I was able to fix the overscanning issue of my Orange Pi zero (read here).
    Because fiddling around with the register values can be pretty harsh some times I decided to created a small programm to move the picture of the composite video output. You can find the project page here: https://projects.nwrk.biz/projects/allwinner-tvout
     
    With this tool you can easily move the picture relative to its actual position by just calling :
    $ sudo tvout -m -x <value in px> -y <value in px>  
    To reset the position you can use:
    $ sudo tvout -r  
    I hope some of you may find this useful.
    If I have enough spare time i will add more features to this project (like changing the resolution, etc.). If you have any questions or ideas please feel free to tell me in this thread!

     
  18. Like
    MitchD got a reaction from bzfrp in Buildroot realtime image for nanopi neo   
    I'm not sure if anyone is interested in a very small distro without gcc, but I spent some time the last week using buildroot and armbian's source files to create a 3.4.112-rt image for the nanopi neo. It is going to be part of a realtime audio project (think synth or guitar pedal) that I'm working on and it demands a quick boot, among other things. 
     
    There is also a mainline version, but it doesn't have all the fixings you folks like, so I don't know if you'd want to use that. 
     
    You can find the build scripts and config files on my github. I'll be posting the legacy image in a zip file tonight, once I verify everything is reproducible. 
     
    I would like to thank the Armbian developers for all their time and energy doing what they do. Their code and guides have helped me understand how one would even attempt something like this, and I'm very grateful. If you ever use my image, please donate to the Armbian community. 
     
    The screenshot is proof that the system works, and how much ram it uses while forwarding a puredata session over X-forwarding. 
     
    I'm open to any questions. Thanks. 

  19. Like
    MitchD got a reaction from op1tjaap in Buildroot realtime image for nanopi neo   
    I'm not sure if anyone is interested in a very small distro without gcc, but I spent some time the last week using buildroot and armbian's source files to create a 3.4.112-rt image for the nanopi neo. It is going to be part of a realtime audio project (think synth or guitar pedal) that I'm working on and it demands a quick boot, among other things. 
     
    There is also a mainline version, but it doesn't have all the fixings you folks like, so I don't know if you'd want to use that. 
     
    You can find the build scripts and config files on my github. I'll be posting the legacy image in a zip file tonight, once I verify everything is reproducible. 
     
    I would like to thank the Armbian developers for all their time and energy doing what they do. Their code and guides have helped me understand how one would even attempt something like this, and I'm very grateful. If you ever use my image, please donate to the Armbian community. 
     
    The screenshot is proof that the system works, and how much ram it uses while forwarding a puredata session over X-forwarding. 
     
    I'm open to any questions. Thanks. 

  20. Like
    MitchD got a reaction from Naguissa in Buildroot realtime image for nanopi neo   
    I'm not sure if anyone is interested in a very small distro without gcc, but I spent some time the last week using buildroot and armbian's source files to create a 3.4.112-rt image for the nanopi neo. It is going to be part of a realtime audio project (think synth or guitar pedal) that I'm working on and it demands a quick boot, among other things. 
     
    There is also a mainline version, but it doesn't have all the fixings you folks like, so I don't know if you'd want to use that. 
     
    You can find the build scripts and config files on my github. I'll be posting the legacy image in a zip file tonight, once I verify everything is reproducible. 
     
    I would like to thank the Armbian developers for all their time and energy doing what they do. Their code and guides have helped me understand how one would even attempt something like this, and I'm very grateful. If you ever use my image, please donate to the Armbian community. 
     
    The screenshot is proof that the system works, and how much ram it uses while forwarding a puredata session over X-forwarding. 
     
    I'm open to any questions. Thanks.