TonyMac32

Oh my, have they fixed all the reboot hackery? Also see: Giant Heatsink. And no, even in automotive where last time buys are common, no one is stocking to support "up to" 2 million pieces without guarantees that the parts will be used. I wonder if that vendor had a falling out with Rockchip.

In terms of "Le Potato" yes, Libre Computer is supporting development actively through the same team Amlogic is using to get their SoC's mainlined. It has been nice seeing the improvement from kernel to kernel, and they've been responsive to issues/feedback. If that's the rule for how they proceed, then I have some confidence in the boards barring any hardware mistakes. I think it would be best to verify the voltage situation, as I saw a few oddities on that portion of the schematic concerning layout and labelling. (Nothing "wrong" that I remember , but some labels and such) Sent from my Pixel using Tapatalk

I'm an old dusty FriendlyARM user, it's actually what brought me here. I did initially avoid these because of unknown SoC support, going with their H3 boards instead because Armbian supported them. The boards look interesting, and yes, no micro-USB

There is an H5 one as well, correct?

I have thrown myself out of the forums at least 6 times today by clicking on the "Armbian" banner image.

Hmmm, considering this is at least second-hand info from the maker of a game console I'm not sure anyone has heard of (personal biases there), I'd take it with a grain of salt. I'd also caution that "phasing out" is not typically the same as "EOL". Phasing out involves "not for new design" but continuing to sell to existing customers on a per-customer basis. I'd be surprised if there aren't a lot of other reasons for changing processor, or if these guys don't have enough volume to negotiate to keep the older chip in a new design and want more power, for instance the people making the claim are going to an entirely different manufacturer and performance and cost tier on their processors.

Well crap.

I use a chassis supply to power most boards that come equipped with micro-USB. To accomplish that I use a voltmeter to set the supply voltage to 5.25 volts, and apply the power through the GPIO header on the RPi clones, making sure to get both 5V and 2 gnd pins. With a quality supply there wouldn't be a huge difference between plugging straight into GPIO or adding filtering/over voltage protection. I would recommend a 0.1 uF ceramic capacitor tied between the 5V and ground to reduce power supply related noise. The Tinkerboard filters all of the important voltages through a PMIC's various regulators, so it is a bit more resilient than some other boards, however USB and HDMI are not as well protected. I can provide some more info later, at the day job currently.

I didn't catch that the first time. That's actually what brought me across them, I'm building a power distribution panel for my router/server cabinet to get rid of some power adapters... I was looking at the old-school HDD connectors and saw the mini version.

Working in automotive I'm continuously trying to find harnesses and connectors, I'll look around, but usually something like that is a special order situation. I'll see how I do building some. Also, anyone searching may come across floppy drive power connectors. These are Berg connectors, not mini-SPOX, no matter what Amazon may tell you.

Unless my eyes are deceiving me, that appears to be a Molex Mini-SPOX 2.5mm connector, I have seen some questions here and there about what that thing was, I'll order a couple connectors and verify (once I see if I have a usable crimper), since it would be nice to have a few more laying around.

That is my understanding as well.

@Andro I don't have a patch to correct the ethernet issue on mainline as yet.

That will be a Balbes150 Image, for the ones I work with see https://www.armbian.com/nanopi-k2/, however, the current WIP is not yet a nightly image. With the new kernel 4.14 NEXT images you'll have something to look at. The currently available 4.13 image has a RAM bug involving the location of the ARM trusted Firmware.

Hi @kicker22004, if you have the Armbian build system set up, you can build a 4.14 desktop image and try it out. I currently don't have the wifi up and running, this hasn't been my priority board. At this point really it's just board support for peripherals and testing.

if you change the dtb it will be to "rk3288-miniarm.dtb" as that was the original name of the board. I've stuck with it because of consistency to the 4.4 kernel. But to be clear, I'm not sure how that would be the issue, I admit I haven't built an image in a couple days, but...

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/diff/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi?id=v4.14.3&id2=v4.14.2 4.14.3 has the memory fix built in for s905x

It will need built at the moment, it doesn't look like Tinker Board is in the nightly build list. That isn't something I've toyed with, so I will defer to @Igor

Now I know.

I don't know of any other way to boot a VideoCore.

Cost, power, throughput. I just saw this beastie, could you imagine if it were powered by something even with proper ethernet?

That is the driver that made it into mainline (4.12+). The legacy kernel is a different driver.

I think how to categorize the boards is a separate discussion, I'd link it in closely with the matrix of kernel support I've mentioned elsewhere, then that could be searchable via a specific function (like a filter: "I want a mainline supported USB3 Gb Eth 64-bit quad core")

No. Now, I built a 4.14 Stretch and did not have the same issue, however Chromium graphics performance seems choppy somehow. This goes for tinker and potato at 4.14. Sent from my Pixel using Tapatalk

Was certain I'd brought this up, but couldn't find it quickly (google search claims it's in the 7" touchscreen thread but it is not). The legacy Tinkerboard image hangs for a period of time launching large apps in Debian Stretch. The machine is not locked up, as the uart console is still responsive. Nothing is showing up in logs. The x-server simply becomes unresponsive, the "please wait" circle spins and it takes 3-4 minutes to "get over it" and move on. Does not accept mouse or keyboard input through the GUI, behaves normally through the console.