TonyMac32

The last 4-5 posts very clearly say "we're close, please wait". Sent from my Pixel using Tapatalk

If you look at the datasheet for the SoC it will be in there, I'm cooking dinner at the moment. :-) Sent from my Pixel using Tapatalk

The eMMC bootloader is always installed a little differently on the eMMC than SD. The output Igor is seeing is the first stage loader in the SoC, it's not finding the bootloader where it wants to see it, it's probably just an offset. Sent from my Pixel using Tapatalk

Use kernel 4.4 and turn it on.

I would at least take a look at the H6 at this point, support is coming along quite nicely. Also, I own a CoCo 2 and a Model 100, so, tip of the hat to the name.

I haven't looked too deeply into the compatibility/resource footprint, but for some HMI environments I like tiling managers https://awesomewm.org/

I'm afraid I don't, I was actually trying to get some information about them the other day for a non-linux application before purchasing.

Moved to TV box topic, most likely more of the people following this subforum have interest/info about the topic.

I can take a look at this, my RPi keeps destroying its SD card and ruining my Volumio setup, so my hifiberry DAC Pro needs a new home. I keep trying to channel the "millions sold" they use as a defense of their design choices, but it just doesn't seem to matter...

Certainly, that would be great.

No need for hardware hacking, I will try to address this tonight, it is in my open items. :-) Sent from my Pixel using Tapatalk

Kernel module added for RK3288, all kernels, and if you have anything Amlogic, all Meson64's

Is inconsistent with And I'll disregard your caps yelling over a 20 minute first try using the information you provided and we'll move forward.lockquote widget. I'll give it another try and post the source later, but you need to do some different stuff to compile it.

I will be putting the overlay in the build system, it can be pulled out of the commit. This claims to be loading, but I'm not getting anything out on my display and haven't yet tried the touch. install the kernel package below, then change armbianEnv.txt to read "i2c1 i2c4 spi2 waveshare32b uart1 uart2" under overlays. Let me know if it works, if not I'll have to give it another go a little bit later. [ 15.027776] ads7846 spi2.1: spi2.1 supply vcc not found, using dummy regulator [ 15.027822] ads7846 spi2.1: Linked as a consumer to regulator.0 [ 15.031921] ads7846 spi2.1: touchscreen, irq 246 ... [ 15.029820] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [ 15.478839] graphics fb0: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 32 KiB buffer memory, fps=25, spi2.0 at 16 MHz linux-image-next-rockchip_5.87_armhf.deb

https://github.com/TinkerBoard/debian_kernel/blob/develop/arch/arm/boot/dts/overlays/waveshare32b-tinker-overlay.dts is an overlay by ASUS for the 4.4 kernel, I'll adapt it to Armbian and we'll see. [edit] the driver for the touchscreen is also not included with our kernel, that can be fixed momentarily once I give this overlay a shot.

I'm afraid I'm something of an electrician when it comes to Linux, I'm much more hardware oriented than software. This is something@JMCC works on, perhaps if he has time he can be of more use. Sent from my Pixel using Tapatalk

would this be similar to the waveshare model? Hmmm, kernel config and DT overlay I assume? I've not tried this. If you have the experience, review the kernel config in our github, and see if you can craft a device tree overlay for it. I have ILI9341 and XPT2046 (same interface) screens lying about for other projects, I may be able to give it a try as well. Were you planning on using the IRQ as well?

I'm afraid not really, this is a symptom of something we've been talking about a great deal, version control and releases being build system related, and not kernel related.

By "updated everything" do you mean ran the media script? Are you running the 4.4 kernel? Please see posting guidelines and add requisite information.

I will begin playing with mainline on it, and look to see if any mainline u-boot work has been done at the same time. If so the goal would be to just lump it in with Meson64 and keep the kernel count down. On Amlogic we have the luxury of Balbes's media box images, so we don't have to fight with the vendor kernels. Sent from my Pixel using Tapatalk

A realistic one performance wise I'm afraid. More (and faster) ram, more (and faster) processor cores, more bandwidth (anything with more than 1 USB port has more available bandwidth than an RPi), more GPU... I could go on. The RPi is a wonderful teaching tool and toy. Thankfully it was successful, the single board computers that existed before it we're a bit more expensive, and didn't get the press coverage, but we're also far more industrial in nature. Sent from my Pixel using Tapatalk

It is as Igor said, however Ethernet has been, and still is, problematic on RK3328 (performance is very slow), it would seem the TRM for the SoC is not as complete as it could be.

I'll try to work on this later today, as long as everything else works out... :-/

The rockchip repo will *mostly* work, but I've had issues with it being consistent as well.

I'm holding off until the DDR4 support is working in mainline, this board would be in the same unfortunate state as the RockPi 4/etc. once the u-boot is working properly we can get rk3399 all put into one happy family and get the support fixed.