ASUS 90MB0QY1-M0EAY0 Tinker Board
image source: Asus Tinker Board is designed to trump the Raspberry Pi 3 - Gadgets - News - HEXUS.net
image source: Asus Tinker Board is designed to trump the Raspberry Pi 3 - Gadgets - News - HEXUS.net
Kodi 14.2 Linux Ported to Rockchip RK3288 with VPU Hardware Decoding
something to play with in the meantime?
Mike
ASUS Tinker Board’s Debian & Kodi Linux Images, Schematics and Documentation
Did you look there as well?
Mike
mconners 2 days and more THANK YOU!!! I had tried searching Asus but didn't find anything and CPC were supposed to be sending me the link when it became available.
Just running the debian distro... it's fast
Thanks again,
Brian
Michael Conners wrote:
Just running the debian distro... it's fast
It must have been fast to setup as well, that didn't take you long.
Mike
Fast D/L on Virginmedia Broadband 
Quick to write on a 16G Sandisk Ultra uSD using USB3.0 adapter. (2.1Gbyte image)
Plugged in powered up and around 18 seconds to full boot into gui.
Brian
The (C) GPIO looks like very crude hack from Pi based stuff.
Have you found any I2C examples/library yet ?
I need to test something with I2C and I thought this might be a good way to kill multiple birds with one Rock !
MK
For I2C, I expect that there is a kernel driver, and that you can use the standard I2C tools like i2cdetect.
Thanks Roger, I've never used any of these tiny Linux thingies so I'm not sure where to look for stuff.
MK
Hi Michael,
The problem is, most documentation/tutorials online are often written just for one SBC, e.g. Raspberry Pi or BBB, and do not mention that its likely the code will work on all platforms. It is particularly
irritating when APIs even have the word 'pi' in the function names, when in reality they may work on other platforms too. Maybe it is information hiding, or maybe the developers of the documentation/tutorials didn't know.
Anyway, for I2C, the easiest way is to check in the /dev folder, if there is an entry called i2c-1 or i2c-2 or something. If so, then one of these will provide driver based access to the I2C pins on the connector, and the
access should work in any language with any library provided it uses the driver (which isn't often mentioned anywhere in the documentation but could be visible in the source code).
I don't know which language you wished to use, but (for example) for C programming the access is via the 'ioctl' function. Just to make it slightly higher-level (but still fairly low-level) I wrote some wrapper functions to
have an easier-to-understand API for I2C. It is available here, in the files i2cfunc.h and i2cfunc.c :
https://github.com/shabaz123/lcd3
(to see how it is used, the file lcd3-test.c could be examined). In short, to use I2C with this wrapper library, these are some of the functions that are available:
i2c_open
i2c_write
i2c_read
i2c_close
(the full list and short documentation is in the i2cfunc.h file, it is mostly self-explanatory to be honest).
It doesn't handle everything but handles things like the repeated start which some online tutorials etc miss.
Thanks for the info - I've just ordered a board but it'll be a while until I can play with it.
I'm keen on the 1GB Ethernet done properly on this board so I have some hope of it being useful.
MK
Roger Wolff wrote:
For I2C, I expect that there is a kernel driver, and that you can use the standard I2C tools like i2cdetect.
Yep the i2c is all working as far as I can tell. I tried the RPi camera (latest version) and got that working.
I also tried the RPi Touchscreen display but that isn't working ... yet to determine why but it does show up on the i2c bus.