Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Pinebuds volume in each e...
Forum: General
Last Post: CaptSpify
7 hours ago
» Replies: 0
» Views: 10
|
Unable to switch from Was...
Forum: General Discussion on PineTime
Last Post: Bruce Kissinger
9 hours ago
» Replies: 0
» Views: 7
|
Searching for a PinePhone...
Forum: PinePhone Accessories
Last Post: RubiksCube
Yesterday, 12:35 PM
» Replies: 0
» Views: 30
|
PinePhone Beta Edition wi...
Forum: Manjaro on PinePhone
Last Post: spazz
Yesterday, 05:55 AM
» Replies: 9
» Views: 8,323
|
Unable to use umlaut key ...
Forum: General Discussion on Pinebook Pro
Last Post: ili
10-01-2024, 01:36 PM
» Replies: 2
» Views: 89
|
Shipping Update and Stock...
Forum: News
Last Post: tllim
10-01-2024, 11:05 AM
» Replies: 89
» Views: 105,514
|
Ethical sourcing practice...
Forum: General
Last Post: cinnabarwinner
09-30-2024, 07:19 PM
» Replies: 2
» Views: 419
|
FIXED-Newer ver of EC25 M...
Forum: PinePhone Hardware
Last Post: DarciFoxe
09-30-2024, 02:08 PM
» Replies: 3
» Views: 293
|
Star64: GPU firmware load...
Forum: Getting Started
Last Post: Marco2024
09-30-2024, 02:49 AM
» Replies: 14
» Views: 6,647
|
Troubleshooting Pinedio L...
Forum: PinePhone Accessories
Last Post: lavabrilliant
09-29-2024, 09:17 PM
» Replies: 2
» Views: 519
|
|
|
Pine64 and Nexdoc |
Posted by: mcf - 09-18-2016, 12:42 AM - Forum: POT modules
- Replies (11)
|
|
I have a nexdoc. The pine64 will drive the display but not well, it is not crisp like it should be.
The display resolution of the nexdoc is 1366*768, but I can't select this under ubuntu on the pine (in fact I an only select one resolution (I can't remember what). Is there some way around this?
..mcf
|
|
|
1Gbps clock sync |
Posted by: stepw - 09-17-2016, 11:54 AM - Forum: Ethernet Port
- Replies (3)
|
|
I have a 'bad' PINE64+ board, running armbian with legacy kernel, powered via micro-USB AC adapter. NIC and UART0 serial are the only active peripherals. 100Mbps is perfectly fine, but there's a major packet loss at 1Gbps, no need for iperf to tell there's an issue.
VDD33 voltage is between 3.26V and 3.27V, regardless of
- 1Gbps or 100Mbps or 10Mbps link speed
- CPU idle (/sys/class/thermal/thermal_zone0/temp @ 42 degrees) or busy (/sys/class/thermal/thermal_zone0/temp @ 65 degrees)
- 3 different microUSB AC 5V adapters and cables
That voltage is within tolerance range of 2.97V to 3.63V for PHY VDD33 (per PHY DS). PMIC AC input tolerance range is 3.5V to 7V (per PMIC DS), so PHY should be getting conditioned ~3.3V consistently, even when microUSB AC source is used. Unfortunately I don't have a scope to monitor continuously, but if AC-IN voltage drops were affecting 1Gbps communications, I'd expect them to equally affect 100Mbps communications and that is not the case. So the issue with my board doesn't seem to be caused by PHY input voltage fluctuations.
However, there is a noticeable difference in the amount of packet loss with different power sources:
1. laptop USB, so <500mA, 2 feet USB cable
PC -> SBC: 30% loss
SBC -> PC: 36% loss
2. AC 5V/2A adapter, 6 feet USB cable
PC -> SBC: 5% loss
SBC -> PC: 11% loss
3. AC 5V/3A adapter, 3 feet USB cable
PC -> SBC: 15% loss
SBC -> PC: 31% loss
I'd speculate that there's possibly another element sensitive to AC input inconsistencies that might not be conditioned by the PMIC or that may have a narrow tolerance range. Alternatively, PINE64+ PCB layout might not be strictly following guidelines for RTL8211E IC as set forth in PHY DS, resulting in EMI affecting its operation or VDD10 conditioned input being outside of a narrow 0.95V to 1.06V tolerance range.
References:
PHY DS - http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf
PMIC DS - http://files.pine64.org/doc/datasheet/pi...t_V1.0.pdf
So I've fiddled around with EMAC IC and its RGMII interface to PHY IC.
Some findings:
1. MII RXERC = 0 in mii-tool reg dump, supposedly that indicates PHY is not receiving erroneous frames
#mii-tool -vvv
registers for MII PHY 0:
1140 796d 001c c915 01e1 cde1 000d 2001
6801 0300 7800 0000 0000 0000 0000 3000
016e acc2 9f01 0000 8040 1006 4100 2100
0000 8c00 0040 0106 21fc 8038 0123 0000
2. EMAC reports RGMII speed/duplex and clock is consistent with PHY link type
1Gbps/full:
EMAC BASIC_CTL_0:
#devmem2 0x1c30000 w
0x1 = 1Gbps/full
EMAC RGMII_STA:
#devmem2 0x1c300d0 w
0xD = 0b1101 - 1Gbps, 125MHz clock
MII PHY:
#mii-tool -vvv
registers for MII PHY 0:
1140 796d 001c c915 0001 cde1 000f 2001
6801 0200 7800 0000 0000 0000 0000 3000
016e acc2 9f01 6c52 8040 1006 4100 2100
0000 8c00 0040 0106 21fc 8038 0123 0000
100Mbps/full:
EMAC BASIC_CTL_0:
#devmem2 0x1c30000 w
0xD = 100Mbps/full
EMAC RGMII_STA:
#devmem2 0x1c300d0 w
0xB = 0b1011 - 100Mbps, 25MHz clock
MII PHY:
#mii-tool -vvv
registers for MII PHY 0:
1140 796d 001c c915 01e1 cde1 000d 2001
6801 0300 7800 0000 0000 0000 0000 3000
016e acc2 9f01 0000 8040 1006 4100 2100
0000 8c00 0040 0106 21fc 8038 0123 0000
3. EMAC is using internal clock for 1Gbps/125MHz
A64 EMAC_CLK_REG:
#devmem2 0x1c00030 w
clock 0b01 = GMII/RGMII external
clock 0b10 = GMII/RGMII internal (default)
This said, there could be a problem with 125MHz clock sync, required for proper RGMII communication between EMAC and PHY at 1Gbps rate. Judging by latest PCB diagrams, PHY CLK125 is attached to EMAC, presumably to supply 125MHz clock to EMAC, however EMAC's internal clock is enabled (by the EMAC driver?), so EMAC and PHY clocks are not synchronized. However, switching to external clock (supplied by PHY?) results in even higher packet loss, upwards of 80%
I was trying to dump EMAC DMA TX/RX descriptors and buffers to get an idea of whether frames received by PHY make it to EMAC over RGMII and vice versa, but so far didn't manage to access them from userland. I guess it would take to debug EMAC driver to monitor them and accumulate TX/RX frames and errors statistics.
Above is a re-post from my earlier post at armbian forum.
I don't know if my findings are conclusive, but I'd be interested to know if EMAC internal vs. external clock makes a difference on other boards.
Could someone who has a Pine64+ board with working 1Gbps NIC
1. Confirm if EMAC clock is internal on their board?
2. Try switching EMAC clock to external to confirm if that cripples 1Gbps performance?
Clock source change is volatile, can be reverted manuually or by reloading the board, so there's no permanent effect.
It would take to:
a). install devmem2
Code: # sudo apt-get install devmem2
b). read EMAC register EMAC_CLK_REG at 0x1c00030
Code: # devmem2 0x1c00030 w
Sample output:
/dev/mem opened.
Memory mapped at address 0x7f88009000.
Value at address 0x1C00030 (0x7f88009030): 0x10C06
c). test ping to default gateway
Code: # ping `ip route show 0.0.0.0/0 | awk '{print $3}'`
Sample output:
PING 192.168.137.1 (192.168.137.1) 56(84) bytes of data.
64 bytes from 192.168.137.1: icmp_seq=2 ttl=128 time=0.725 ms
64 bytes from 192.168.137.1: icmp_seq=3 ttl=128 time=0.397 ms
64 bytes from 192.168.137.1: icmp_seq=5 ttl=128 time=0.366 ms
64 bytes from 192.168.137.1: icmp_seq=6 ttl=128 time=0.436 ms
64 bytes from 192.168.137.1: icmp_seq=7 ttl=128 time=0.303 ms
^C
--- 192.168.137.1 ping statistics ---
7 packets transmitted, 5 received, 28% packet loss, time 6004ms
d). write EMAC register EMAC_CLK_REG at 0x1c00030
Code: # devmem2 0x1c00030 w 0x10C05
Sample output:
/dev/mem opened.
Memory mapped at address 0x7f911c2000.
Value at address 0x1C00030 (0x7f911c2030): 0x10C06
Written 0x10C05; readback 0x10C05
e). test ping to default gateway
Code: # ping `ip route show 0.0.0.0/0 | awk '{print $3}'`
Sample output:
PING 192.168.137.1 (192.168.137.1) 56(84) bytes of data.
64 bytes from 192.168.137.1: icmp_seq=3 ttl=128 time=0.479 ms
64 bytes from 192.168.137.1: icmp_seq=7 ttl=128 time=0.398 ms
64 bytes from 192.168.137.1: icmp_seq=12 ttl=128 time=0.504 ms
^C
--- 192.168.137.1 ping statistics ---
14 packets transmitted, 3 received, 78% packet loss, time 13004ms
f). revert to internal clock
Code: # devmem2 0x1c00030 w 0x10C06
Sample output:
/dev/mem opened.
Memory mapped at address 0x7f911c2000.
Value at address 0x1C00030 (0x7f911c2030): 0x10C05
Written 0x10C06; readback 0x10C06
Reference:
page 158 of http://files.pine64.org/doc/datasheet/pi...l_V1.0.pdf
|
|
|
Android USB camera support - Android 7.0 |
Posted by: mikey0000 - 09-17-2016, 03:25 AM - Forum: Android on Pine A64(+)
- Replies (24)
|
|
Hi all,
Been working on getting the camera module up a firing. Tonight I had success and got my logitech 615 webcam opening in a camera app. However it probably means that the himax 5mp camera won't work with these changes. Just out of curiosity how many people here have the himax 5mp camera? It should be possible to support both but as I don't have one I can't test it.
Will post a link to the module when its a bit more ready flag that here it is and eventually it will end up in Ayufan's Android builds.
To use the module ALPHA
https://drive.google.com/open?id=0B3jDRH...UtmcmVVckE
run adb remount
adb push 32bit/camera.tulip.so /system/lib/hw/
adb push 64bit/camera.tulip.so /system/lib64/hw/
and also everytime you start
lsmod and look for uvcvideo or ls /dev/ and look for video0
if they are not there do the following
adb shell insmod /system/vendor/modules/videobuf2-vmalloc.ko sorted in latest build, uvcvideo too
adb shell insmod /system/vendor/modules/uvcvideo.ko (assuming kernel support)
---> these two last steps should be fixed eventually in a new os build latest Ayufan has fixed this
You should at least get a video feed with this module.
Bug Reports:
- app your using ( e.g skype, camera app)
- Device your using (camera not pine)
- adb logcat with errors
- steps to reproduce
as always I will not be held accountable if your pine melts down because you followed these instructions!
|
|
|
Best way to set up ubuntu |
Posted by: pharris430 - 09-16-2016, 09:33 AM - Forum: Ubuntu
- Replies (5)
|
|
So I've been working with my pine for a few months now, trying to get a hadoop server running to support my work as an integration architect. My plan is to use the pine as a linux server, running multiple hadoop clusters, a postgres db and proprietary integration software from my employer. As an experiment I simply installed everything on the micro sd card, but that is not sustainable as far as size, so I experimented with using a usb thumbdrive as a pic. That only worked somewhat since I had to muck around with disk mounts etc, and ultimately as soon as I had it all working a bad shutdown corrupted the thumbdrive sending me back to square one.
I have since invested in a 1tb usb hdd, a powered usb hub, and now need to the optimal way of setting it all up. My first question is is it best to reformat the external hdd to a linux partition or leave it as ntfs. I know that ntfs has limitations with setting privileges, which is a issue with postgres. How would the linux gurus approach this?
|
|
|
Wrong items received |
Posted by: lukebamar - 09-16-2016, 07:11 AM - Forum: Shipment Related Discussion
- Replies (1)
|
|
Hi,
I received shipment in july but without things i ordered from backerkit.
I got:
1x Pine54 2GB with Wifi module
Air mouse
Acrylic case
Keyboard
ABS case
Power supply
RTC Backup Battery - CR
HDMI to VGA Adapter
2x MicroSD cards 64GB
Micro USB to USB
HDMI to DVI adapter
POE Splitter
Instead of:
2x 2gb board
PINE64 Acrylic Open Enclosure
3x 5 Way 12C Cables
3x 4 Way 12C Cables
3x 5-Way to 4-Way I2C Cables
2x PINE64 5V 2A Power Supply - International
PINE64 ABS Enclosure
PINE64 12C Multiport POT
PINE64 Wifi Remote Module
USB Serial Programmer for PINE64
PINE64 Ambient Light Sensor
2x PINE64 Humidity Temperature Sensor
HDMI to VGA Adapter With Audio
RTC Backup Battery - AAA
2x RTC Backup Battery - CR
Wifi 802.11BGN/ Bluetooth 4.0 Module
I tried to contact Pine support but they are ignoring me.
I also tried to politely contact tllim. He informed shipping facility two times, now he ignoring me as well.
Is there any other way how to get my paid things? Or get overpaid money back?
|
|
|
|