MitchD

Members
  • Content count

    21
  • Joined

  • Last visited

  1. This isn't a feature with the H2/H3 device trees because those CPUs don't have a DPI interface. You could try to use notro's fbtft library using the parallel option to drive your display, but I don't think he has support for RGB24.
  2. Cool, I didn't know RT patches for 4.13 were out already! Thats great news, I should bump up my version. Are you building your kernel using the armbian toolset or your own? Another point is that mine is specifically for the nanopi neo, which doesn't involve any HDMI setup or clocking. I'm not sure if that affects the results of cyclictest, but it might, as the HDMI subsystem must involve interrupts to the kernel. Armbian also ships with irqutils, which balances the irqs over the 4 cores (or 3, as you have one isolated). I have no idea if that matters either. I'm using my stuff for audio, and having the full RT kernel helps with audio dropouts on my USB device. Using alsa (no jack) I can get it down to ~10ms round trip. Without RT it was more like ~30ms. I've found the best test of any RT system is how it responds with your application.
  3. Sure thing! Here are my results: # cyclictest -p 80 -t5 -n -a # /dev/cpu_dma_latency set to 0us policy: fifo: loadavg: 0.12 0.17 0.08 1/93 193 T: 0 ( 186) P:80 I:1000 C: 551057 Min: 5 Act: 8 Avg: 8 Max: 29 T: 1 ( 187) P:80 I:1500 C: 367371 Min: 5 Act: 8 Avg: 7 Max: 44 T: 2 ( 188) P:80 I:2000 C: 275529 Min: 7 Act: 8 Avg: 7 Max: 13 T: 3 ( 189) P:80 I:2500 C: 220423 Min: 7 Act: 8 Avg: 7 Max: 11 T: 4 ( 190) P:80 I:3000 C: 183685 Min: 5 Act: 8 Avg: 7 Max: 24 I have isolcpus=2,3 running, and I'm running a mainline 4.11 kernel with the rt patch, as well as an ethernet patch and usb otg patch. It is also a buildroot environment, so I'm not sure how much that is skewing these results in my favor. # uname -a Linux nanopi-neo 4.11.9-rt7 #1 SMP PREEMPT RT Fri Sep 22 10:38:22 CDT 2017 armv7l GNU/Linux
  4. You can find discussion about this in another post on this forum: I find you don't get great latency in the legacy kernel, whereas my post with the mainline kernel has a max latency of 42 us.
  5. Looks like g_hid is broken on this build of armbian. Not sure why this hasn't been patched yet.
  6. Sorry, put sudo before those commands and run them again. It must be run as root. I'll try with a legacy stable image tonight and see if I can get it operational.
  7. Which kernel are you using? If you are using mainline, I understand than the OTG options aren't there yet. If on legacy, you can try: modprobe -r g_serial followed by: modprobe g_hid From there, see if any new devices are created. Full documentation is here: https://www.kernel.org/doc/Documentation/usb/gadget_hid.txt
  8. If you want the cyclictest results from a mainline kernel, here are mine: Linux nanopi-neo 4.11.9-rt7 #2 SMP PREEMPT RT Mon Aug 7 21:41:13 CDT 2017 armv7l GNU/Linux # cyclictest -p 80 -t5 -n # /dev/cpu_dma_latency set to 0us policy: fifo: loadavg: 0.05 0.05 0.01 1/96 220 T: 0 ( 208) P:80 I:1000 C: 572399 Min: 5 Act: 6 Avg: 8 Max: 42 T: 1 ( 209) P:80 I:1500 C: 381600 Min: 6 Act: 9 Avg: 8 Max: 34 T: 2 ( 210) P:80 I:2000 C: 286200 Min: 5 Act: 9 Avg: 7 Max: 25 T: 3 ( 211) P:80 I:2500 C: 228960 Min: 6 Act: 9 Avg: 8 Max: 29 T: 4 ( 212) P:80 I:3000 C: 190800 Min: 5 Act: 11 Avg: 8 Max: 30
  9. 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.
  10. 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.
  11. Replicating an existing release?

    There is a way to roll back changes, and its almost straightforward. I successfully did it by manually going back through the git commits in armbian/build until I found the date that matched the uname output, and cloned it from that point. Then you have to add an empty file on the same directory as compile.sh with: touch .ignore_changes From there, you have to change how it grabs the sources, and make sure that repo is from the same date. Here is the build repo commit for Feb 2: https://github.com/armbian/build/tree/813cfaa16cb3164acb3f8feade5f269a218121c9 And here is the linux repo from January 20th: https://github.com/armbian/linux/tree/e0a8ecfd409ffb14fe382804fdc180e6c52413e0 From there you have to dig around in armbian/build and change which git repo it clones, and don't allow cleaning the directory before it compiles. With enough perseverance you should be able to get it to work.
  12. 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.
  13. Buildroot realtime image for nanopi neo

    I think you would have to copy directly to the filesystem, but I'm not sure. I've never added drivers after the kernel is compiled. You're going to need to look under /lib/modules and figure out what do there.
  14. Buildroot realtime image for nanopi neo

    It is set up to a dynamic IP right now. If you try `nmap -sP 192.0.2.0/24` on your laptop before `arp -a` you might be able to find it. If at all possible, find another ethernet cable, and plug the orange pi directly into the router. Its the easiest method. You should be able to bridge the wireless and ethernet connections, but this is outside the scope of the help I'm able to provide. Its different for every system. The kernel I provided does not have any wifi support, so a cable is going to be the easiest thing to manage.
  15. 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