webbbn

Members
  • Content Count

    43
  • Joined

  • Last visited

About webbbn

  • Rank
    Advanced Member

Recent Profile Visitors

510 profile views
  1. I can also confirm that NVME works perfectly, which I expected, since it works on the m4v2.
  2. 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).
  3. 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.
  4. 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.
  5. I forgot it had built-in emmc. That works perfectly as well.
  6. 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.
  7. 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...
  8. 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. :-)
  9. 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.
  10. 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.
  11. 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
  12. 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!
  13. 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).
  14. 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.