| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,677
» Latest member: Charlotten
» Forum threads: 16,252
» Forum posts: 117,166
Full Statistics
|
| Latest Threads |
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: zetabeta
Yesterday, 04:14 PM
» Replies: 1
» Views: 192
|
black cursos background
Forum: General Discussion on PineTab
Last Post: polrus
Yesterday, 04:07 PM
» Replies: 0
» Views: 34
|
slight bumps causing phon...
Forum: PinePhone Pro Hardware
Last Post: JadenSki
Yesterday, 02:05 PM
» Replies: 2
» Views: 64
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
Yesterday, 02:01 PM
» Replies: 10
» Views: 12,457
|
Switching cameras on PPpr...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 10:44 AM
» Replies: 0
» Views: 32
|
Battery connector dead
Forum: PinePhone Hardware
Last Post: mdk
Yesterday, 10:05 AM
» Replies: 3
» Views: 2,360
|
No touch KB after update(...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 09:45 AM
» Replies: 3
» Views: 145
|
compass pdf link expired:...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-10-2025, 12:39 PM
» Replies: 4
» Views: 257
|
Running Pinebook (non-Pro...
Forum: Pinebook Hardware and Accessories
Last Post: guidol
11-09-2025, 04:19 AM
» Replies: 0
» Views: 85
|
Pinebook Pro for sale
Forum: General Discussion on Pinebook Pro
Last Post: rfm83
11-08-2025, 09:22 AM
» Replies: 0
» Views: 146
|
|
|
| unable to deploy my application to the Pine using Visual Studio 2017 |
|
Posted by: Matthew - 10-05-2017, 01:59 AM - Forum: Windows 10 IoT
- Replies (9)
|
 |
Hello all,
A customer of ours is trying to deploy their application, see below his email:
"I'm unable to deploy my application to the Pine using Visual Studio 2017.
I remember that I had my the application running on when we received the boards a while back but I was using Visual Studio 2015 then.
"The application we have developed is a UWP project and not a native Win32 project.
I've followed the steps you pointed to but it did not fix the problem.
It compiles and deploy successfully to a Raspberry Pi running Windows Core."
Please assist?
Thanks.
|
|
|
|
| Looking for the Mali support... |
|
Posted by: rondoor - 10-05-2017, 01:20 AM - Forum: Linux on Pinebook
- Replies (1)
|
|
Recently, I know there is a way to enable Mali-400 support from here.
https://github.com/ayufan-pine64/linux-build/releases
I did same things as the introduction said, such as installing xserver-xorg-video-armsoc-sunxi and libmali-sunxi-utgard0-r6p0, Updating a kernel, a u-boot and packages. And I executed the script by typing pine64_enable_sunxidrm.sh . Then, it told me to reboot my pinebook. After rebooting, I checked whether the Mali works correctly or not by glmark2. Unfortunately, it said..
GL_VENDOR: VMware, Inc.
GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)
GL_VERSION: 3.0 Mesa 12.0.6
I thought this meant I failed to enable it. So I tried many times but the results are always same . 
How can I enable it? And, did you success to have the Mali work on your pinebook?
I need your advice. And I apologize for my poor english.
|
|
|
|
| Debian Stretch and Kodi Krypton on Rock64 |
|
Posted by: zarusz - 10-04-2017, 11:59 PM - Forum: Linux on Rock64
- Replies (28)
|
|
Hi All,
I bought a ROCK64 and I am trying to move from my existing RaspberryPi2.
I would like to go with Debian Stretch and install all my required services (Samba, Kodi, Java 8, openHAB 2.2, mosquitto ...).
The only thing that does not work for me is Kodi.
During start it screams with some errors (low level C++ free() memory exceptions). Right now I installed the LibreELEC by @Raybuntu, however I would like to stick with Debian Stretch for my other services. I will install Debian once more and try to capture the exact errors.
Did anyone manage to install Kodi on Debian Stretch and could post an instruction?
Thanks!
|
|
|
|
| Xorg & Mali |
|
Posted by: stuartiannaylor - 10-04-2017, 10:58 PM - Forum: Linux on Rock64
- Replies (5)
|
|
Code: [ 11.482] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so: $
[ 11.483] (EE) AIGLX: reverting to software rendering
[ 11.485] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 11.488] (II) AIGLX: Loaded and initialized swrast
[ 11.488] (II) GLX: Initialized DRISWRAST GL provider for screen 0
Has anyone managed to get xorg to use the mali yet, its supported just not in the main kernel but struggling with the community images.
Always end up reverting to software rendering and it sucks.
Been through practically all the community images and it seems the same but its really hard to tell if we are running distro xorg or the rockchip xorg.
http://opensource.rock-chips.com/wiki_Status_Matrix
Its supposedly supported but with what we have it doesn't seem to be.
rockchip_dri.so doesn't even exist
|
|
|
|
| Some helpful tips! |
|
Posted by: dudemo - 10-04-2017, 02:28 PM - Forum: Android on Rock64
- Replies (10)
|
|
After disliking how Android appeared on the Rock64, I decided I'd had enough and began searching for a new launcher. I wasn't too surprised when I fired up Google Play and saw that basically no launchers are supported. So I started searching out specific launchers (ADW Launcher, Nova Launcher, etc...) and I was able to find a few launchers that actually work! GO Launcher EX works amazingly well and is highly customizable. I won't go into an advertisement for the software, just letting you know that it is a fast way to change the look of Android. One feature I will tout is the ability to force screen orientation in landscape, so you shouldn't be turning your head 90 degrees to navigate anymore hopefully.
Play store link: https://play.google.com/store/apps/detai...erex&hl=en
An alternative that I found works just as well but doesn't have as many options: https://play.google.com/store/apps/detai...cher&hl=en
Next, if your like me... You don't use the on-screen keyboard because you have a USB mouse/keyboard hooked up. I found it to be annoyingly large and it also required that I push the "search" button on the on-screen keyboard and not just pushing "enter" on the keyboard. I searched around and found that others have had the same problem. And came up with a solution! Null Input Method is an IME that basically is not a keyboard. It just hides the on-screen keyboard and re-enables "enter" on a USB keyboard.
Play store link: https://play.google.com/store/apps/detai...free&hl=en
Some of you may not be aware that Android actually does have provisions built-in for a wired keyboard. Unfortunately, documentation for this is very hard to find. Here are the key bindings I've found to be working. I'm also looking into a way to remap these so we can use more comfortable keyboard combinations. Sadly, the "Home", "Num Lock", etc... buttons do not work on any keyboard I've tried, so just pushing "Home" to go home doesn't work.
Home: Alt+Escape
Back: Escape/Right-Click
Menu: Control+Escape
Reboot (NO WARNING!) Control+Alt+Delete
Caps Lock: Shift, Shift (Twice in quick succession!)
App Switcher: Alt+Tab
When I find a free way to remap these buttons, I will let you all know. Likewise, I'll let you know if more shortcuts are found. Fee free to add to the list!
Edit: Aptoide has a pretty good app for downloading apps you cannot get from the Play Store. For example, I really wanted virtual soft keys (back, home, menu) but I was having a hard time finding any compatible ones in the Play Store. Aptoide let me download the one I wanted and installed it. Which brings me to my next point...
Virtual Soft Keys (no root) works pretty fine for getting navigation keys on screen. Follow the directions, it works great. Added benefit is that it let's you hide the keys when you won't need them (RetroArch, Kodi, etc...) by swiping them down, and then reenable them by swiping up from the bottom.
Now, I've had several apps tell me I'm rooted. Am I? Because no root manager seems to work at all.
|
|
|
|
| What is name of gpio hardware on a rock64? |
|
Posted by: gene83 - 10-04-2017, 12:04 PM - Forum: Linux on Rock64
- Replies (6)
|
|
The driver code checks for it, and will return a valid answer if its a bcm2709, bcm2835, bcm2836, or a bcm2837. Code is:
Code: #define CPUINFO_BUFSIZE (16*1024) // Should be large enough for now
static platform_t check_platform(void)
{
FILE *fp;
char *buf;
size_t fsize;
platform_t rv = RPI_UNSUPPORTED;
if(!(buf = rtapi_kmalloc(CPUINFO_BUFSIZE, RTAPI_GFP_KERNEL))) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: No dynamic memory\n");
return RPI_UNSUPPORTED;
}
if(!(fp = fopen("/proc/cpuinfo", "r"))) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: Failed to open /proc/cpuinfo\n");
goto check_exit;
}
fsize = fread(buf, 1, CPUINFO_BUFSIZE - 1, fp);
fclose(fp);
// we have truncated cpuinfo return unsupported
if(!fsize || fsize == CPUINFO_BUFSIZE - 1) {
rtapi_print_msg(RPSPI_ERR, "hm2_rpspi: Platform detection memory buffer too small\n");
goto check_exit;
}
/* NUL terminate the buffer */
buf[fsize] = '\0';
if(strstr(buf, "BCM2708")) {
rv = RPI_1;
} else if(strstr(buf, "BCM2709")) {
rv = RPI_2; //for RPI 3 too
} else if(strstr(buf, "BCM2835")) { // starting with 4.8 kernels revision tag has board details
char *rev_val = strstr(buf, "Revision");
if(rev_val) {
char *rev_start = strstr(rev_val, ": ");
unsigned long rev = strtol(rev_start + 2, NULL, 16);
if(rev <= 0xffff)
rv = RPI_1; // pre pi2 revision scheme
else {
switch((rev & 0xf000) >> 12) {
case 0: //bcm2835
rv = RPI_1;
break;
case 1: //bcm2836
case 2: //bcm2837
rv = RPI_2; // peripheral base is same on pi2/3
break;
default:
break;
}
}
}
}
check_exit:
rtapi_kfree(buf);
return rv;
}
And all the c style indenting has been stripped, so how do I post code? This sucks.
Thanks everybody.
Cheers, Gene83
|
|
|
|
not able to flash u-boot onto SD Card |
|
Posted by: consoleadam - 10-04-2017, 03:44 AM - Forum: General Discussion on ROCK64
- Replies (2)
|
|
greetings,
I have manged to build u-boot as per http://opensource.rock-chips.com/wiki_U-Boot . However, after burning the images to SD card, booting stops before starting my built version of u-boot, i.e., no u-boot prompt!
Serial console output below, also, further down build details.
Can anyone please shed light whats wrong in the process ?
thanks
consoleadam
serial output
========
DDR version 1.06 20170424
In
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7587MB
FwPartOffset=2000 , 0
StorageInit ok = 48039
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x7b5f4
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 09:28:45, May 31 2017
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initiapteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: platng runtime services
WARNING: No OPTEE provided by BL2 boot loadTEE will return SMC_UNK
ERROR: Error initializing runtime sernormal world
INFO: Entry point address = 0x200000
INFO:
-------------------
Build and Flashing in details:
==================
consoleadam@barbarian:~/rock64$ git clone https://github.com/rockchip-linux/u-boot.git
consoleadam@barbarian:~/rock64/u-boot$ make ARCH=arm -j4 CROSS_COMPILE=aarch64-linux-gnu- distclean
consoleadam@barbarian:~/rock64/u-boot$ make ARCH=arm -j4 CROSS_COMPILE=aarch64-linux-gnu- evb-rk3328_defconfig all
BL2 ddr.bin & idbloader.img
-----------------------------
consoleadam@barbarian:~/rock64/u-boot$ dd if=../rkbin/rk33/rk3328_ddr_786MHz_v1.06.bin of=ddr.bin bs=4 skip=1
consoleadam@barbarian:~/rock64/u-boot$ tools/mkimage -n rk3328 -T rksd -d ddr.bin idbloader.img
consoleadam@barbarian:~/rock64/u-boot$ cat ../rkbin/rk33/rk3328_miniloader_v2.43.bin >> idbloader.img
BL3 trust.img & u-boot.img
----------------------------
consoleadam@barbarian:~/rock64/u-boot$ ../rkbin/tools/loaderimage --pack --uboot ./u-boot-dtb.bin uboot.img 0x200000
consoleadam@barbarian:~/rock64/u-boot$ cp ../rkbin/rk33/rk3328_loader_ddr786_v1.06.243.bin ./
consoleadam@barbarian:~/rock64/u-boot$ cat >trust.ini <<EOF
[VERSION]
MAJOR=1
MINOR=2
[BL30_OPTION]
SEC=0
[BL31_OPTION]
SEC=1
PATH=../rkbin/rk33/rk3328_bl31_v1.34.bin
ADDR=0x10000
[BL32_OPTION]
SEC=0
[BL33_OPTION]
SEC=0
[OUTPUT]
PATH=trust.img
EOF
consoleadam@barbarian:~/rock64/u-boot$ ../rkbin/tools/trust_merger trust.ini
flashing
---------
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=idbloader.img of=/dev/sdb seek=64 bs=512
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=uboot.img of=/dev/sdb seek=16384 bs=512
consoleadam@barbarian:~/rock64/u-boot$ sudo dd if=trust.img of=/dev/sdb seek=24576 bs=512
|
|
|
|
| eMMC Boots to Recovery Menu |
|
Posted by: Farley56 - 10-03-2017, 01:16 PM - Forum: Android on Rock64
- Replies (3)
|
|
Had a working Android 7.1.2 eMMC. Not sure what I did to it but now it boots to the Recovery Menu but there's no keyboard or mouse response. Can't move to any selection in the menu. Reload the eMMC? Boot to an SD Card linux image and fix it from there somehow? Thanks for any tips.
|
|
|
|
|
