| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,687
» Latest member: ouglastam
» Forum threads: 16,256
» Forum posts: 117,177
Full Statistics
|
| Latest Threads |
Battery Life on Latest In...
Forum: General
Last Post: ouglastam
3 hours ago
» Replies: 1
» Views: 1,884
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
4 hours ago
» Replies: 0
» Views: 25
|
Second screen mirroring
Forum: General
Last Post: andrekyler
10 hours ago
» Replies: 3
» Views: 1,872
|
7 inch touch panel patche...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: mkjmkj
11 hours ago
» Replies: 0
» Views: 33
|
Pine64 LTS v1.2 not turni...
Forum: P64-LTS / SOPINE Hardware, Accessories and POT
Last Post: in_sympathy
Yesterday, 08:09 PM
» Replies: 0
» Views: 30
|
I think you can try compi...
Forum: General Discussion on Pinebook Pro
Last Post: wangyukunshan
11-14-2025, 05:27 AM
» Replies: 1
» Views: 254
|
Are you interested in a n...
Forum: General Discussion on Pinebook Pro
Last Post: WEF
11-12-2025, 02:33 PM
» Replies: 2
» Views: 3,020
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-12-2025, 11:18 AM
» Replies: 3
» Views: 414
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
11-12-2025, 07:29 AM
» Replies: 0
» Views: 121
|
black cursos background
Forum: General Discussion on PineTab
Last Post: polrus
11-11-2025, 04:07 PM
» Replies: 0
» Views: 113
|
|
|
| RFE for next ROCK64 |
|
Posted by: mcerveny - 07-06-2018, 04:19 PM - Forum: General Discussion on ROCK64
- Replies (4)
|
 |
Hello.
I have some enhancement suggestion for next update of ROCK64:
- connector for RTC battery for RK805
- connector for RESET and POWERON
- needed for external control (power on by event)
- connector for true PoE/PoE+/4PPoE (802.3af/802.3at/802.3bt with mode a,b,a+b over 1gbit) with 1GBit connector+magnetics for example "EDAC A70-112-331N126" or "LINK-PP LPJG0926HENL" (must be carefully routed with operating up to 600mA@57V and with PoE isolation requirements)
- connector between barrel power connector and board power (both pins, with installed jumpers from factory) that can be used for:
- internal (in case) DC/DC converter (also isolated variant) from higher voltage (12V)
- combined DC from embedded UPS battery with cooperation with external DC
- combined DC from PoE DC/DC with cooperation with external DC (also possibility to supply any DC to external component back over DC connector (available power +-10W reserved for ROCK64 from 12.95W(PoE)/25.50W(PoE+)/51W(4PPoE) (for external powered usb hub, speakers, small lcd panel, camera, positioning motors, ...)))
- power distribution over mounting holes connected to barrel power connector selectable with pinheaders/jumpers (probably with additional internal DC/DC converter from previous point to compensate voltage drop for massive stacking) - see Paralella
- connector (with installed jumper from factory) to unselect internal SPI (SPI_CSN0_M2) (but with possibility to boot from external SPI flash directly from embedded ROM over PI-2 connector)
- larger internal SPI to accommodate boot+stripped_down_kernel+ramdisk miniroot with something like NOOBS (New Out Of the Box Software) distribution download from internet and etcher flash to local SDCARD/eMMC
- maybe connector with PMEB+VCC33_LAN+GND (or embed this to board - 1xLDO + 3xdiode? (untested)) from RTL8211F to implement Wake-on-LAN (WoL) with external logic but VCC33_LAN must be reworked to supply RTL8211F chip externally too. Example scenario (untested):
1) new attach of PoE (ethernet connector) or external DC must start rk3328+rk805 to setup/config RTL82211F for WoL (actual behavior due to C736)
2) PoE or external DC still available (eg. VCC_SYS==5V) but rk3328+rk805 is down (eg. no BUCK4 VCC_IO->VCC33_LAN) and VCC33_LAN externally over pin or with own LDO from VCC_SYS (combined power with diodes?)
3) PMEB should signal WoL to pin or to POWERON (over diode or transistor)
- Colored connector like TinkerBoard or adafruit
- USB and power test pads from bottom to stack USB peripherals like RPI ZERO USB hub
- Add some programmable peripheral co-processor like 8-bit (AVR) or 32-bit (ARM M0+) or other hw peripheral rich chip (connected with i2c+interrupt to RK3328, connected to RESET/POWERON to RK805, serial firmware programming with external connection, maybe "alway-on" (not RK805) powered also on vBAT...) for programmable hw tasks like true PWM (motor or fan speed control), A/D (also for independent voltage/current board monitor), programmable sw logic, WoL monitor, external watchdog, oneWire bridge, IR transmitter ... with connection on PI2 unusable pins (11,12,13,24(SPI CSN0),29,31 and maybe 32-40)
- Add some simple undervoltage detector (op-amp comparator) to driver green led (LED705) (bicolor led (green/red) may be better)
I estimate material expenses about $1 (~14 pinheaders, ~3 diodes, ~1 LDO and replace "HANRUN HR911130A" to "LINK-PP LPJG0926HENL") + $0.5-$2 for coprocessor.
Something like this:
|
|
|
|
| Purchase Cart Interface on Quanitity |
|
Posted by: eaterofpis - 07-06-2018, 02:39 PM - Forum: General
- Replies (1)
|
 |
So it seems people are limited to 5x amount of any particular type of board on each order. Example, one is restricted to only adding 5x Rock64 (2GB). One minor workaround is adding 5x of a different type such as Rock64 (4GB) or 5x Pine64.
It becomes a problem if those are not the type of board you want or if you're looking to buy larger quantities of a specific soc.
I think one can break larger purchase into multiple orders but it can feel like an inconvenience from a shopper pov.
On the flip side, i do understand that there's a flat shipping rate. And for instance, shipping say 50 boards order under a fixed flat rate $8 as opposed to shipping 5 boards, would not be ideal from a business and cost perspective.
Is there a middle ground to this? Like flat rates when quantity of each type in the cart does not exceed 5, but system cart switches to a variable rate when a quantity type is greater than 5?
|
|
|
|
| Display limited to 800x600 [SOLVED] |
|
Posted by: Averell - 07-06-2018, 08:04 AM - Forum: Linux on Rock64
- Replies (16)
|
 |
Hello,
I used the Pine64 installer to install a "Community Debian Stretch Mate". Indicated version, in July 2018 is : 0.5.15
Beautiful installer, everything fine but the display : it is locked to 800x600, and somewhere a message indicates that the display card is not recognised. I thought I would find a solution and set up the Linux, and used it for some time. But nothing was found to fix the display problem.
Further tests showed that only the 0.6.x versions give me the normal resolution of the display (1280 x 1024 DVI). I tried with :
- Community Debian Stretch Mate (0.5 : Bad)
- Community Debian Stretch Minimal (0.6 : OK)
- Community Bionic Lxde (0.6 : OK)
- Community Xenial Mate (0.5 : Bad)
I found later that Ayufan builds really work from 0.6 versions. It is regretful that the 0.5 versions are not yet replaced in the Pine64 installer.
A good desktop experience
Question : is it possible to fix the problem in the installed 0.5 version, or is it necessary to start all over from scratch ?
A strange phenomenon : The defective Debian runs on the eMMC. I tried to flash a SD card with a Bionic 0.6 version. Tested on a second Rock64 : fine. I put the SD card in the first Rock64 : The Bionic is launched, but the display is 800x600. At first, I thought the Rock64 was defective. Then I tried to remove the eMMC card : then the Bionic starts with the 1280,1024 resolution. What can be the reason ? Are some files read first on the eMMC card, when a SD card is present ?
Thanks if someone has a suggestion. I would hate to reinstall everything.
But what I really like with this little thing is the perfect silence.
|
|
|
|
Help! My parcel is stuck in Shenzen |
|
Posted by: notthebee - 07-06-2018, 07:41 AM - Forum: Shipment Related Discussion
- Replies (2)
|
 |
Hi! I live in the EU and i ordered a Rock64 on 14th of June. On the 20th my order was shipped. However, since 27th of June, there is no progress regarding the shipping, the tracking is stuck on Shenzhen, leave Shenzhen to Shenzhen Postal Courier Company (Hong Kong) Business Department
As far as i know, most shipments take 6-15 business days to arrive, but mine has been en route for 16 days now, with no chance of it being delivered anytime soon. I have sent an e-mail to the sales department, but got no reply. Can anyone help me?
Order: #62235
Tracking number: LZ479139910CN
Any feedback is appreciated!
|
|
|
|
| Non-Flash SPI |
|
Posted by: RichCrewe - 07-06-2018, 07:35 AM - Forum: P64-LTS / SOPINE Hardware, Accessories and POT
- Replies (1)
|
 |
Has anyone had any experience using SPI channel 1 for connecting to things other than flash?
I've set-up my system to use the Armbian distro for Pine64SO.
There's a driver for spi compiled into the kernel, but it looks as if the hardware is disabled in the Device-Tree file (/boot/dtb/sun50iw1p1-pine64so.dtb) so that the pins can be used for UARTs 3 and 4.
I've modified the dtb file to disable these UARTs an enable SPI-1 (spi@01C69000), but when I reboot with this modified dtb file. The system fails to bring-up Ethernet. After modifying the logging system to store the logs somewhere persistent, it appears that there's a crash somewhere in sunxi_mdio_reset(), probably at the first time it accesses hardware. This seems a bit weird as the pins used by SPI channel-1 are not used by any of the Ethernet hardware. I'm wondering if there's some kind of interrupt or clock-speed conflict.
At the moment I'm trying to find a UART so that I can watch the console as it boots, but I wondered if anyone else had been down this road before.
--
Richard Crewe
|
|
|
|
| Search Compatible 10.1" touchscreen |
|
Posted by: alfredo78 - 07-06-2018, 03:48 AM - Forum: LCD and Touch Panel
- No Replies
|
 |
Hi, I would like to know if there are compatible 10.1" touchscreen displays with the PINE64-LTS or ROCKPro64 boards (unfortunately, this is a constraint for my project)..
Do you help me ?
Thanks, L.A.
|
|
|
|
|