TonyMac32

Hmm, I'd thought the connector was more for cameras since that's the whole strength of that SoC... But I won't argue with video. [emoji38] Sent from my Pixel using Tapatalk

I think SPI is your only real option, but I honestly haven't looked that close. So ili9341 or equivalent. The RPi 2 is the only one in the series I would consider using. The 3 was a waste of time, the 1/zero too slow to use, generally. Sent from my Pixel using Tapatalk

Assuming anyone wanted to make a profit I don't think that's feasible. Now, if the boards' literally a microSD card, USB port, and 40 pin header, it might be close, but my guess is even soldering down the camera connectors would make it tight. Sent from my Pixel using Tapatalk

OK, I'm adding the I2C for that to the device tree. For 4.19 I'll toss a set of overlays out so the various hardware can be configured at will. Install the deb attached into your 4.14 install and let me know if it works for you. Not complete, I need to add proper processor pin names for a few of these yet: linux-dtb-meson64_5.67_arm64.deb

Added Tinker Board, including the other pin functions not mentioned in ASUS documentation.

armbianmonitor -u please

Amazon was where I got them, however last I checked the heatsinks were no longer available for that seller. If you search a geometry that fits it shouldn't be hard to find something. Sent from my Pixel using Tapatalk

Right, that's why I was looking at the little board. I have some RPi style hats I've made for powering with SPI/I2C broken out, and another with a SPI NOR for booting the RK3288. Neither made it to "production quality", I need to share a few simple ones for people. Sent from my Pixel using Tapatalk

Interesting, I've been meaning to make some similar board afor the NanoPi Neo, their proto board is extremely limited due to size/etc.

There is no support for it in mainline as yet. I am planning on working on it (no guarantees) after the new year for possible integration with 4.19.

That stays cool forever, but won't fit in the pi-top I think. An alternative could be https://www.aliexpress.com/item/3D-Printer-Cooler-Fan-DC-12V-24V-Connector-Brushless-Cooling-Turbo-Blower-Fan-50x15mm-3D-Printer/32944813107.html Remember the Tinker Board is one of the highest performing boards you can buy, the RK3399 devices will do better due to way nicer interfaces (USB3, PCIe, etc), but the mainline support is not as good, and the Rockchip kernel is a bit of a mess, thankfully for 64-bit targets Ayufan has a nice fork. The Le Potato has 64-bits on it's side, and an active team working on the mainline support. Given the mobile nature (batteries, yes?) I'd look into a small circuit and a script to toggle the fan based on cooling state, so it's not just "on". If you are really adventurous, moving the debug UART to UART3 frees up 2 PWM pins. That reminds me I need to double check the vendor kernel and make sure we're matching it, there was some chaos this year... For Le Potato, 4.14.y from armbian download page does not have an easy way to be flashed to eMMC. 4.19.y works with the out of the box tools, but screen results may vary. I have not tried the amlogic downloader, my guess is it requires Android-looking images, which we do not create. I will be starting to test @Neil Armstrong's u-boot update as soon as I have a moment, look for it in January/February since that will be U-boot 2019.1. BTW, Neil, I love this README:

Now that I need to look at. Sent from my Pixel using Tapatalk

Nothing, I'm not sure the mention of "regression" was discussing the minor revision number, but more likely the 4.19 kernel itself. @rino can you confirm?

I've broken these things down (perhaps too far, but I will give a case for it, and we can all discuss), here are the overlays: - ds1307 - i2c1 - i2c4 - spi0 - spi2 - spidev0 - spidev2 - uart1 - uart2 - w1-gpio The DS1307 was simply pulled from ASUS as a simple test overlay while I was working through implementing the scripts. it can be jettisoned for all I care. These are all written with only the Tinker Board in mind, of course they are all SoC-centric other than the 1wire and ds1307 "Pi" ports: - i2c1 is the "Pi" I2C channel. Make it configurable in case you just want the GPIO - i2c4 is the "Pi" ID I2C channel. Make it configurable in case you just want the GPIO - spi2 is the "Pi" SPI channel. Makes it configurable in case you want just the GPIO - spidev2 enables the user space spidev driver with 2 chip selects for spi2 - uart1 is the "Pi" UART position. Tinker ports: - spi0 is the "extra" spi channel on Tinker, on pins 11/13/15/29/31. Disabled by default, it occupies the same pins as UART4 *Not Pi Compliant in location* - spidev0 enables the user space spidev driver with 2 chip selects for spi0 - uart2 is the debug port for Tinker. There are some interesting extra features exposed on some of the pins (PWM/etc) that I would like to experiment with, we'll see. I have pulled the spi out as an overlay separate from the peripheral attached to it, my thought is, there may be 2 unrelated devices tied into the board on each chipselect that the user has their own overlay for. (So up to 4 devices on hardware SPI)

I know exactly as much about this board's availability as you do. I accidentally happened across it the other day.

Right, I was looking at that one, petit_miner has a github with the design on it. Sent from my Pixel using Tapatalk

Yes, full install. I would only say for test, as the device tree/boot script may not be frozen just yet. Sent from my Pixel using Tapatalk

I haven't looked at 4.14 recently, let me see if there is an issue there. There are 4.19 beta images available in dl.armbian.com under tinkerboard, let me know if you are willing)able to try that out to see if the sound works. Sent from my Pixel using Tapatalk

Rockchip-dev kernel updated, now implements overlays for uarts 1-4, spi0, spi2, spidev0, spidev2. The default config for Tinker out of box is to have spi2/spidev2, and uarts 1 and 2 enabled. This puts the basic RPi configuration in place with the debug UART. Uart2, spi0/2 and spidev0/2 tested.

Yes, this is what I've been talking about in this thread for the last week or so. Sent from my Pixel using Tapatalk

Sorry, didn't read your posts, was curious as to the high shipping and noticed the smaller one. Sent from my Pixel using Tapatalk

armbianmonitor -u please, as posted in at least 2-3 things you had to click through.

Awesome! don't stress, any contribution is welcome, and in the time the contributor is willing to make it.

Everyone involved please post the armbianmonitor -u output as directed in the forum guidelines/banners so I can get some idea what we're all talking about. Sent from my Pixel using Tapatalk

I think you have to give up Wifi to have NVMe, or something like that on the 2.0 boards.