webbbn

Just to follow up. I was able to build an image. My problem previously was that my script was building a focal image, which, of course, would not work. A program of mine that uses libmpv is working very well. I have not been able to get the camera working. I'm pretty sure that I had /dev/video* device entries previously, but now I don't have anything, so maybe the camera died for some reason. It could also be that I don't know what I'm doing. :-) I wasn't able to a dts file that seemed like an exact fit for the camera, so that could be a problem as well. The camera that I have is this one: https://www.friendlyarm.com/index.php?route=product/product&path=78&product_id=247. It's not high priority, so, rather than thrash around some more, I'll just wait and see if anyone else gets it working.

Thanks. I build Armbian regularly, but, for some reason the image that I built did not have the media-buster-legacy-rk3399 package. I'll try again, and if it doesn't work I'll post my build options. Thanks! I'll take a look at the repo. That did fix it for me. I had to reboot (logging out/in might have been enough), but it is working now.

This is great! Unfortunately, I'm not having any luck so far. I built my own image (I know, that's not the standard method, but I assumed it would be the same), and it doesn't have the media-buster-legacy-rk3399 package available. Next I tried downloading the standard M4V2 image (Armbian_20.11.3_Nanopim4v2_buster_legacy_4.4.213_desktop.img.xz), and it gets stuck on bluetooth while booting and get's stuck there. I'm going to try the neo4 image now. I assume the Armbian_20.11.3_Nanopineo4_buster_legacy_4.4.213.img.xz image is a desktop image? In any case, I'm very excided about this. I have gone through the process of building a few systems with the script, but would much prefer to have the capability in the standard image without having to go through the extra steps. Is it possible to e.g. have MPV display directly on the framebuffer, accelerated with another app (OSD) running in another, overlying framebuffer on rk3399? I need/want to be able to build my own image, so is there some repo I need to add to the standard build, or should that have worked with a normal build? I may have some build option set incorrectly. Edit: The neo4 is getting stuck on starting bluetooth as well. Is there any way to skip it? Got past the bluetooth error on startup. It apparently had gotten far enough to allow network logins, so I was able to login, update, and install the multimedia packages, and it's looking good now. I was able to smoothly play a 1080p video that I had lying around with mpv. Time to start playing! Can you give a hint on how to enable the camera? I don't see any overlays that seem to relate to the camera. Is there another package that I have to install to install additional overlays? I'm trying to get libmpv to work, and I keep getting the error "EGL_NOT_INITIALIZED". I even get that when I install and run qtcreator. Does that make sense to anyone?

I ran a 12 hour stress run last night without issues, other than forcing me to put a better fan on the heatsink! :-) I've been running memtester for about 10 hours now without issue.

I haven't used it extensively yet, but I have worked on it a bit, and it has been up several days with no issues. Is there s stress test that I could run?

I'm building the latest version of current, so it is understandable that it doesn't work. Are there any RK3399 boards where USB-C works with Armbian mainline? It looks like the Firefly has a similar USB-C port, but I don't know if that works with Armbian either.

I can also confirm that NVME works perfectly, which I expected, since it works on the m4v2.

This may also be "human error", but the USB-C is not working, at least not the same as with the FA image. With the FA image, I can plug a USB C "hub" with HDMI, ethernet, USB, etc, and it powers up during boot and works as expected, which is very nice. With the armbian image it does power up at all. I believe the M4V2 only uses USB C for power, so I don't think think it has an equivalent of this, and I don't know where to look for how to enable it. Might there be a kernel configuration? The schematic shows a vbus detection line, power control, and some sort of interface IC (FUSB302MPX).

USB turned out to be a hardware issue. I booted a FA image, and USB didn't work there either, so I re-seated the module and USB is now working perfectly.

It appears that the USB ports are not working. Is there something in the device tree that enables them, or enables the power for them? It doesn't seem like anything happens when I insert a card, but I don't see anything in the schematic that would control power to them, other than the over current protection chip.

I forgot it had built-in emmc. That works perfectly as well.

Well, what do you know, it works! At the very least, ethernet, wifi, and hdmi work. I don't know what else to test on it ATM. I plan to try an NVME drive, but that's still in the mail, and I'm curious if USB-C display will work. One thing that interested me about this board/module was it's advertised ability to work with just a USB-C cable. It could be a really interesting board in that respect.

I am plenty familiar with the build tools, but not so much with bringing up a new board. To quote a Donald Rumsfeld phrase, there are alot of "unknown unknowns". I suppose I could try booting a similar image and see what happens...

Is there any way/plans to support the FrindlyArm RK3399 SOM in Armbian? Does anyone know the hardware well enough to know if another firmware could be loaded on it? It seems to be a very nice module, and the dev board has just about everything one might want on it. On a side note, possibly derailing my own topic, is there any plans to add any of the VPU patches for the RK3399 and associated software? It seems like support for that is getting pretty close, and it would be great if some of the patches that are floating around could get include in the official distro. I'm about to dive in an try getting at least accelerated ffmpeg working on my M4V2 and/or neo4, but have been hoping that it would get into the standard distro first. :-)

Do you need those exact baudrates? I don't remember where I saw it, but somewhere I read that the UART speed should be close to an even divisor of 1.5MHz. At least that's what I remember, and it seems to work for e.g. 115200. In any case, I'm currently running the UART on a Duo 2 at 500kbps with no problems. If you have control of the other end of the link you might try that. That said, I would also be interested in tweaking the clocks a bit because I would really like to be able to run at 400kbps and 420kbps if possible.

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.

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

That looks perfect.

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!

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).

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.

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.

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?

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!

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