I am looking to attach a custom PCB to the RockPro64 board, a simple extension board with custom firmware that communicates over UART.
Up until now I have no luck getting even a basic two-way communication over UART2 working.
Steps taken:
* The RockPro64 runs on Armbian Ubuntu 18.04
* The RP64 is connected to a Ubuntu Laptop with the Pine64 UART-USB adapter. Due to voltage issues, we regulated the TXD and RTX pins to exactly 3.3V (see schematic attached). Bidirectional communication works fine for the serial login prompt.
* Serial console on ttyS2 is now disabled. We get some Uboot messages on boot, after that the port is silent
* picocom is running both on the RP64 (over SSH) and on the Ubuntu laptop
Expected result:
* Both machines should be able to communicate usint picocom, if started e.g. like `picocom -b 1500000 /dev/ttyS2`
Actual result:
* The RP64 is able to output some characters unreliably to the laptop
* The laptop cannot send any characaters to the RP64, instead mirroring some <?> characters despite local echo off
Some status logs:
Code:
$ dmesg | grep tty
[ 0.000000] Kernel command line: earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=4e0c7993-7cbb-46f7-acd0-2e3acdfa20ef rootwait rootfstype=ext4 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=350ce75a-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001397] console [tty1] enabled
[ 0.328959] Registered FIQ tty driver
[ 1.945780] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 36, base_baud = 1500000) is a 16550A
[ 1.946282] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 37, base_baud = 1500000) is a 16550A
[ 4.946846] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 15.681434] ttyS2 - failed to request DMA, use interrupt mode
The PineBook Pro is due to arrive Really Soon Now™, and I'm surely getting one. However, I find myself missing a lapdock-like solution. With the PineBook Pro and PineBook already equipped with screen, keyboard/touchpad, HDMI and battery, we're almost there. Add an input-board with signal converter for the onboard screen, an internal powered USB3 hub for external keyboard/touchpad/wifi and a dedicated port (USB-C?) to power an external SBC in a portable product, and you're there. I see several potential use-cases:
Portable KVM-machine for datacenter work
Troubleshooting SBCs that usually run headless
Pine64 SBC workstation
Super-portable video editing workstation (add a NUC or equivalent mITX computer)
A soberly priced (and available) alternative to PiTop
Convert a PinePhone (or really any phone) to a laptop
Are there any other users on this forum that would buy a product like that from Pine64?
Hi, I am using rockpro64 with Ubuntu18.04 LXDE image.
I made a project on rockpro64 that runs continously 24x7.
Sometimes when light goes or i do software restart, it does not reboot. I have to plug out the power jack and plug it again. SOmetime it reboots automatically after restart.
Is this common issue? Is it related to Hardware or Image? Any idea?
Thanks.
Hello,
I would like to use the PWM fan from Noctua (‘NF-A8 PWM’ - https://noctua.at/en/nf-a8-pwm) with my ROCKPro64. This fan requires PWM signal at 5 V and 25 kHz frequency.
As I understand, the only easily available PWM signal on ROCKPro64 board is PWM_1 (GPIO4C6) connected to board connector J8 (FAN). But it has 12 V at this connector. Somehow I do not like idea of shifting it back to 5 V.
Is there any place on the board, where I could obtain this signal before it gets shifted to 12 Volt? Maybe with little soldering...
Also, may I cause any problem, if I change frequency of this signal to 25 kHz?
Greetings to ROCKPro64 community at my first post!
Gienek.
PINE64 is making a commitment to financially support the community and PinePhone partner projects.
Moreover, a scheme will be put in place to aid closing the digital divide.
I've ported ayufan changes to lineage repo, I'm suspecting the av framework but I can't find my mistake, any ideas ?
By booting with ayufan native frameworks native the bootanimation appears but that's it, it's not going further, then processes are being killed with
Code:
[ 362.251756] init: Starting service 'zygote'...
[ 362.257818] init: Starting service 'audioserver'...
[ 362.265320] init: Starting service 'cameraserver'...
[ 362.272544] init: couldn't write 14298 to /dev/cpuset/camera-daemon/tasks: No such file or directory
[ 362.273294] init: Starting service 'media'...
[ 362.274808] init: Starting service 'netd'...
[ 364.871632] CPU Budget hotplug: cluster0 min:4 max:4
[ 364.877332] CPU Budget:update CPU 0 cpufreq max to 1152000 min to 480000
[ 364.886352] CPU Budget hotplug: cluster0 min:4 max:4
[ 364.891917] CPU Budget:update CPU 0 cpufreq max to 1152000 min to 816000
[ 366.918650] binder: 14483: binder_alloc_buf, no vma
[ 366.924122] binder: 1608:1637 transaction failed 29201, size 68-0
[ 366.944339] binder: undelivered transaction 32999
[ 366.949649] binder: undelivered transaction 32997
[ 366.970261] binder: 1608:1636 transaction failed 29189, size 68-0
[ 367.024959] init: Service 'zygote' (pid 14293) killed by signal 9
[ 367.031700] init: Service 'zygote' (pid 14293) killing any children in process group
[ 367.040363] init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory
[ 367.051115] init: write_file: Unable to write to '/sys/power/state': Invalid argument
[ 367.059725] init: Service 'audioserver' is being killed...
[ 367.065990] init: Service 'cameraserver' is being killed...
[ 367.072520] init: Service 'media' is being killed...
[ 367.078196] init: Service 'netd' is being killed...
[ 367.089154] init: Service 'audioserver' (pid 14294) killed by signal 9
[ 367.096496] init: Service 'audioserver' (pid 14294) killing any children in process group
