TonyMac32

Oh my. In other news the Tinkerboard will power up and operate normally via the GPIO (Pins 2,4,6) My above-board idea is a little closer to my heat sink modification than I like, but if I make a proper board I want to include a USB charge port for powering external HDD's assuming they won't spin up on the USB alone (I tested with an old 2.5" USB-PATA enclosure, worked like a charm) Supply used: Odroid XU4 5.0 V 4 Amp, I stuck a capacitor on there, will probably include an overvoltage protection diode as well. I wasn't too worried, all of the really sensitive stuff goes through the RK808, which is fairly forgiving.

For USB contact rating in micro USB: 1.8 Amps is cited along with a 500 mA current on all other pins simultaneously. An odd way to write the requirement, however if only pins 1 and 5 are involved, assuming heat dissipation is the primary concern, then you could, in theory (after performing adequate testing *TO FAILURE* on multiple devices), pull a known current more without risking a "thermal event". I'm sure some less-than-brilliant soul simply added 1.8 and 1.5 and decided they had plenty of headroom... In any situation, you can only assume 1.8 Amps, but I would not break into cold sweats or lose sleep over using 2A intermittantly.

Dev (4.12-rc1) will build now. Note that I changed only what was needed to make it build, so some of the patches may not be needed/may not help/etc. @Myy I had to take out the post-mali UMP patch, UMP is failing to build for some reason or another on 4.12 using this build system. Otherwise it appears to be at the same level of functionality as 4.11, although I did notice a marked improvement in USB audio (external cards, not the built-in codec), even though it does still try to blow my eardrums out of my head using the browser with certain source materials. (I haven't tried to mess with PA yet). I am building a "Hat" or "Shield" or (more likely) "tombstone" for the board to see if I can power it via the gpio pins and avoid the micro USB. If it powers on with a smaller supply, I'll build to suit the Odroid XU4 4A adapter. (Obviously this board is going to be trouble power wise, however, since I've already got one I'm going to make it work for me) OK, back to the job that pays me. ;-)

Same here, I just mentioned it in the other thread, Chromium is "Aw Snap!" on Tinker Board as well.

I think so. Will need to revert the 1 commit I had for the MiQi LED fix that's already in 4.12. ;-) Ah, forgot, Chromium won't show anything but the "aw, snap" screen, I had to install firefox to get online. I'm not sure what Chromium is doing.

I still have to get the patches submitted, but: |_ _(_)_ __ | | _____ _ __| |__ ___ __ _ _ __ __| | | | | | '_ \| |/ / _ \ '__| '_ \ / _ \ / _` | '__/ _` | | | | | | | | < __/ | | |_) | (_) | (_| | | | (_| | |_| |_|_| |_|_|\_\___|_| |_.__/ \___/ \__,_|_| \__,_| Welcome to ARMBIAN 5.27 stable Ubuntu 16.04.2 LTS 4.12.0-rockchip System load: 0.48 0.14 0.05 Up time: 0 min Memory usage: 2 % of 2007MB IP: 10.0.0.46,10.0.0.54 CPU temp: 32°C Usage of /: 8% of 29G

@cyberk What kernel are you running? I have 4.4.66 with 1.8 GHz enabled, a larger heat sink and a small (25mm square) fan attached to the 5V: sysbench 0.4.12: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 4 Doing CPU performance benchmark Threads started! Done. Maximum prime number checked in CPU test: 20000 Test execution summary: total time: 64.4817s total number of events: 10000 total time taken by event execution: 257.8760 per-request statistics: min: 25.37ms avg: 25.79ms max: 66.93ms approx. 95 percentile: 26.48ms Threads fairness: events (avg/stddev): 2500.0000/43.31 execution time (avg/stddev): 64.4690/0.01

Cool @mcerveny, I replied on Tinkerboarding since that's the OP, would you be willing to run the same tests using Armbian kernel 4.4.66? In other news, I am building a 4.12 image as I type this, fingers crossed.

There are a few 5.3 Volt 2 Amp supplies available cheaply on Amazon (for Samsung Cell Phones), which would work for most people working with a streaming media player type setup or with a solid-state USB storage option. How much is that 80mm fan pulling at 5V? The USB attached peripherals will be the first thing to fail, nothing else on the board actually uses 5V directly, and all of the regulators are buck or LDO to 3.3 V or lower. Otherwise this adapter, or one like it (notice the cabling reads "20 AWG" and it is 5.25 Volts, 3 Amp) would be ideal. This way, it takes a 500 mV drop before you start really digging yourself a hole.

Anything targeting the mainline will be getting 4.12 tonight, I can confirm some patch failures for Tinker Board/MiQi NEXT, Specifically: 0002-Adaptation-ARM-dts-rockchip-fix-the-MiQi-board-s-LED Was patched in the kernel. 9002_dts_rk3288_updates - Fixed and the packaging postinstall-scripts patch specific chunk: scripts/package/builddeb There is no "Provides:" statement.

I confess, I have no idea what to do with the contents of this repository. Any help would be great, as I've said before, my Linux experience is lacking on things, the work I do is usually in hardware with kiB of RAM... I'm working on the assumption that this would be the best lib to install, if I'm wrong, let me know. https://github.com/rockchip-linux/libmali

@cyberk, it's not it's power needs, it's the power connector. Micro USB is not up to the task of supplying large currents without significant voltage drops. I use AWG 20 cables for my setup, and still get a voltage drop. My 400 mV drop was measured with a fixed cable 5.25 V 2.4 amp supply. That is the issue. The cooling is also sub-par, that tiny heat sink is not good enough, I've done what you see below (I'm sorry tkaiser, I know little fans anger and sicken you. It is at least optional. ;-) ). I also noticed the RK808 getting hot, so it got a tiny little heatsink out of habit (I work on automotive manufacturing and test equipment professionally)

@Peba, is there any insight you could/would give on developing an image for the rk3288 UGOOS boxes? It looks straightforward enough, and is a nifty little container (But why oh why is the OTG a full size USB port?) Flashed it to the newest firmware, after making an absolutely idiotic Male-A to Male-A cable out of some old printer cables I had lying around... I want to see what the RK3288 is actually capable of, since nobody's linux is there yet I'm having a hard time gauging whether or not our performance is reasonable.

For the purpose of the device, I'd second (or third) the recommendation for some ECC RAM.

That is exactly the test I performed and mentioned in the other thread, I saw significant voltage drops on the 5V directly related to CPU load. Now, I have a 5.25 Volt 2.4 amp usb supply, so I think that is adequate. ("Adequate", not "optimal"). The USB codec was a mistake, the hub was a judgement error, the micro-usb power is obviously not a great call, and the documentation kind of stinks.

The mechanism used to get the reboot working on 4.4 does not work on 4.11. I haven't dug into why exactly that is (it is a hack), however I saw some soft reset patches to the 4.12 kernel that may resolve the issue, rock chip has been pretty active with improving kernel support, although the RK-wifi system interface isn't present for wifi, etc.

http://ugoos.net/blog/RK3288-update-v309-ugoos-settings

That's nice. If you widened the box just a tiny bit and used something like *these* I think all would be well. I could use the USB3 to drive my existing 4-bay RAID as well...

Did you change the cpu governor before running the test? I'd be curious your experience changing it to "interactive".

The default governor needs to be changed as well, the powersave setting seems to impact USB transfers pretty significantly.

Thanks tkaiser, I hadn't been too worried about it, sounds easy to experiment for those who want to without changing anything in the defaults. Along other lines, I tested a USB soundcard with the Tinker Board and can confirm that "as-built" the performance is terrible, as was mentioned earlier. The default cpu governor is set to Powersave.

I'm reading the voltage at the GPIO 5V pins (Pins 4 and 6), which, according to what ASUS would call a "schematic", is directly connected to the same rail that sources the RK808. This goes through a surge suppressor and a USB charge monitor, but it is the main 5V rail for the device. The voltage was measured at that point with the CPU at idle and running minerd just to put some (albeit unrealistic) load on it (1.8 GHz). The VCC_SYS can be observed to drop significantly. I used a 5.0 Vsupply and the initial voltage, same test point, at idle, is 4.85 V. For the 3.3 V components it's just fine, but USB peripherals will be less than amused.

You're right, but I am using a pretty solid supply and cable, anyone using even an "ok" one is going to have some trouble. (For instance, if it was a 5.0 or 5.1V supply, or the cable had any more inline resistance).

I am going to review powering the board through the GPIO, I am using a 2.4 Amp power supply to power it through micro-USB and am still getting a 400 mV voltage drop when the processor clocks up to 1.8 GHz. (The supply is powering at 5.25V, I'm droping to just shy of 4.9)

My testing has shown it never going below 600 MHz, despite having op points for as low as 126 MHz. I have only seen it go to 1.8 when trying to play video, since none of that hardware has userspace drivers yet to my knowledge (and I admit I don't know how to install them) Rockchip has a repo for Mali and their MPP, but I'm not sure how to go about using them. I think it is set to conservative/powersave, that question needs posed to a larger audience however, the kernel config affects both Tinker Board and MiQi.