webbbn

Members
  • Content Count

    34
  • Joined

  • Last visited

About webbbn

  • Rank
    Advanced Member

Recent Profile Visitors

405 profile views
  1. That's what I thought you would say. I don't expect to do too much with them, so I'll probably just continue to fight with the old Yacto build, but they're really nice boards that you just can't find anywhere else for this purpose, at least not that I'm aware of, other than hacking together a bunch of parts on a raspberry pi zero. FWIW, it's the control/video transmission boards out of the 3DR Solo quadcopter and controller. They were recently resurected by the OpenSolo project to get them where they are, but I've just gotten used to just apt-getting this and apt-getting that, and building on-board.
  2. I am developing on an imx6 board that is no longer in production. It has a full Yacto-based build system that works, based on an old 3.17?) kernel, but its a pain to develop for. It's not worth spending too much time on refactoring the image, but I'm wondering how big of a job it might be to build an Armbian image for it, given that I already have a working uboot and kernel. The hardware just uses a couple of usbs and uarts, and a pcie wifi card. One wersion also has an hdmi encoder, another has hdmi display. Those might be the hardest to support, but driver support is in the kernel. Thoughts? Sent from my LM-G710 using Tapatalk
  3. As far as I can tell, there is currently no hook to allow patching the out of tree wifi drivers, since they're merged into the kernel source after patching. I was able to add the ability to patch these drivers with just a one line change: Would it be possible to add that (or something similar) to the build scripts, or let me know how I can currently add the patches if it's already possible? Thanks!
  4. That's a fair question. It must be one of my added packages that's pulling it in. I built a stock version without an issue. Thanks for the link to the bug report. For now I'll try to find the package that's the root of the problem and see if I can get by without it (likely).
  5. I've been trying to build a nanopiduo2 firmware for the last couple of days, and I keep getting an error on the 048-humanity-icon-theme_0.6.15_all.deb. It says corrupted filesystem tarball. I don't know where to report this. Is this a packaging error in Armbian or Ubuntu? I'm trying to build the bionic firmware. Any suggestions on getting around this error would be much appreciated.
  6. It turns out that buildroot has exactly what I'm looking for. They call it KCONFIG_FRAGMENT_FILES. Essentially it allows one to just say that I want to use the default configuration, but change these specific options. I'm sure it wouldn't work 100% of the time, but it seems like it could be better in some circumstances than just replacing the current default configuration with an old, possibly now non-functional configuration just to change a couple of options.
  7. I have a Jenkins server that builds kernels/images for several boards that I own, and, for the most part it works very well. The biggest problem that I currently have is the kernel configuration. I need to add a few patches, which generally works well, and change a couple of configuration options, which sometimes fails. The problem is that I go through a process of creating a modified kernel configuration by first building a stock configuration. I then go into the kernel source directory under cache, make my changes, do a "make oldconfig", grab the new config file and add it to my userpaches directory. That works for a while, but eventually the kernel configuration changes enough that I get non-bootable images and have to go through the process again, potentially for each board. Is there a better way of doing this? Is there a way to build the kernel using the default configuration with just a few options changed?
  8. Do you have more information on this? I've been trying to setup my nanopi neo4 as an access point without success, and I believe the hardware is very similar, so it's likely a similar problem. FWIW, I got farther with the FriendlyArm distribution, but it still has issues that I haven't resolved yet. I would much rather use Armbian anyways. It's much more polished, and the support is top notch!
  9. I finally got it working. I don't know what the problem was, but I switched back to the default config and started from there again. This is a diff between the original script.fex and the one that enables composite video out: 314c314 < disp_mode = 1 --- > disp_mode = 0 317,318c317,318 < screen1_output_type = 2 < screen1_output_mode = 14 --- > screen1_output_type = 3 > screen1_output_mode = 5 327c327 < hdmi_used = 0 --- > hdmi_used = 1 331c331 < tv_used = 1 --- > tv_used = 0 419c419 < tvout_used = 1 --- > tvout_used = 0
  10. I should add that this is the H3 version of the board.
  11. I am trying to get composite video fully working on an Orange Pi Zero Plus 2. I installed the legacy kernel image, and I've been able to turn on composite out, but I just get a blank screen on boot and there is no /dev/fb0. Is there anything else I have to do to enable the framebuffer. This is the (I believe) relevant portions of the script.fex file: [boot_disp] advert_disp = 0 auto_hpd = 1 output_type = 4 hdmi_channel = 0 hdmi_mode = 4 cvbs_channel = 1 cvbs_mode = 11 output_full = 1 hdmi_mode_check = 1 [disp_init] disp_init = 1 disp_mode = 1 screen0_output_type = 3 screen0_output_mode = 5 screen1_output_type = 2 screen1_output_mode = 14 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 1 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 1 [hdmi_para] hdmi_used = 0 hdpc_enable = 0 [tv_para] tv_used = 1 tv_dac_used = 1 tv_dac_src0 = 0 these are some possible relevant lines from boot. [ 0.000000] Kernel command line: root=UUID=ab03f9a3-0ba3-4236-8857-33f3229b7a85 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 monitor=composite-ntsc panic=10 consoleblank=0 loglevel=1 ubootpart=75ceecdb-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1 [ 0.614087] [DISP]disp_module_init [ 0.614413] cmdline,init_disp= [ 0.614448] cmdline,disp= [ 0.615200] [DISP]disp_module_init finish [ 1.029299] cmdline,disp= [ 1.029629] [DISP] disp_init_tv,line:539:screen 0 do not support TV TYPE! [ 1.029647] [DISP] bsp_disp_tv_register,line:998:'ptv is null [ 1.029710] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr1<-->device1, type=2, mode=14
  12. I installed the experimental version of the NanoPi Neo Air distribution on my Air a month or two ago. At the time I believe Bluetooth was not working on that version. I don't see any indication that it is not working now, but it doesn't seem to be working on my install. Is Bluetooth working on the experimental kernel? If so, should I just re-install, or is it not hard to get it working on an existing install? I just installed the latest updates and rebooted, and that didn't fix it. The symptom that I'm seeing is that if I run bluetoothctl it prints a prompt, but seems to lock up.
  13. The heatsink is just bolted on, so it's easy to remove, but it doesn't interfere with the pins, so it's possible to solder pins on even with the heatsink installed.
  14. It doesn't look to me like that comes with a power supply, and I don't know why you would want to use that anyway if you just want to power it. Why not use something like this: https://www.amazon.com/Raspberry-Power-Supply-KuGi-Adapter/dp/B01E6YLFAO