| Welcome, Guest |
You have to register before you can post on our site.
|
|
|
| Pine64 and MQTT |
|
Posted by: Grootkonijntje - 09-22-2016, 03:15 AM - Forum: openHAB
- Replies (2)
|
 |
Are there any options for integrating Mosquitto support on the Pine ?
Which Linux distributions will work with it ?
I'm a newbie at Linux, so have a little patience with me please
|
|
|
|
| A little whinge Some simple questions I hope |
|
Posted by: MobileFusion - 09-22-2016, 02:59 AM - Forum: Getting Started
- Replies (3)
|
|
I have tried asking these questions direct to Pine with no reply. Come on guys you have a good product but a product is only as good as the support.
Anyway whinge over and now the questions...
1. I am going to buy a LCD screen in the next few weeks, but want to know is there is any operating system which would allow me to run dual screen one HDMI connected to the port and also the lcd?
2. Is there any list of PI hats that will work o the pine if not any tutorials and what would be needed?
3. When will the be (as promised) European distributer(must say the shipping is improving things are taking a little over a week)?
|
|
|
|
| Pine64 2gb + stuff for sale or trade |
|
Posted by: Caleb420 - 09-22-2016, 01:46 AM - Forum: Shipment Related Discussion
- No Replies
|
|
Hey everybody. Well iv lost my patience with this pine board. And I don't want spend any more money to get their wifi module ete.
I have a pine64 2gb with lcd, and the play case.
I would like to get a orange pi 2 plus or pi3 with accessories. I would also consder a cpu upgrade to my I5 4670 in same 4th gen 1150. I live in us
|
|
|
|
| RPI2-GPIO |
|
Posted by: mus1c - 09-21-2016, 02:40 PM - Forum: Pi2, Euler and Exp GPIO Ports
- Replies (6)
|
|
I want to set up a serial connection from raspberry pi 2 bus but don't know what the device would be called in regards to /dev/tty*. It is wired correctly but because the raspberry pi is different to pine64 system the tutorial stopped there.
|
|
|
|
| Pine64+Ubuntu+Tvheadend+DVBT Dongle |
|
Posted by: Shai - 09-21-2016, 04:13 AM - Forum: Linux on Pine A64(+)
- Replies (3)
|
|
Hello
I am trying to run Tvheadend over Ubuntu 16.04 LTS (GNU/Linux 3.10.102-3-pine64-longsleep aarch64)
with dongle Bus 001 Device 002: ID 0572:c688 Conexant Systems (Rockwell), Inc. Geniatech T230 DVB-T2 TV Stick
I couldn't make the compile of tvheadend so i have used a prepared .deb file and the service is working just fine. the thing is that the DVB dongle is not recognised on the Tvheadend.
some1 can help?
|
|
|
|
| Etcher, the superior burning choice! |
|
Posted by: Ghost - 09-21-2016, 02:14 AM - Forum: General
- Replies (42)
|
 |
Hi
Many of the threads here on the forums, when talking about burning operating system images mention the use of Win32DiskImager. But there is a better alternative called Etcher.
It's user-friendly, open source, cross-platform, and most importantly, it verifies that a burn has been completed successfully.
You can download it here.
|
|
|
|
| Surround Sound Possible on Any OS? |
|
Posted by: methvenc - 09-20-2016, 07:53 PM - Forum: General Discussion on PINE A64(+)
- Replies (1)
|
|
Hello,
My end goal is to use this with a plex media client connected to my TV and audio receiver via HDMI and get surround sound.
I have tested Android 5.1 which as far as I know is not capable of surround sound, I assumed that it would because my nexus player running the same software did support surround sound, I was wrong. I thought that perhaps the nexus was running Android TV OS, so that could be the issue. I have tested Android TV, that also does not produce surround sound, only stero sound via my receiver.
My question is, is there any software (remix, Linux) that can supports surround sound via HDMI? If so, is it possible to run plex from that OS?
Not sure why the nexus player is capable of playing surround sound but this is not, from what I understand it is more complicated than them sharing similair OS.
If anyone could point me in any direction it would be appreciated. I checked the forums in each OS but couldn't find anything to confirm this works.
|
|
|
|
| LCD Monitor resolution problem |
|
Posted by: S265 - 09-20-2016, 02:52 PM - Forum: Debian
- Replies (2)
|
|
Hi all. The Pine64 Debian Xfce image does not detect my LCD monitor resolution correctly. For some reason it is using 1280 x 760 or such. The correct resolution is 1920 x 1080. The Pine64 Ubuntu mate image does not suffer from this problem - It works at the correct resolution. My OpenSuse Desktop also uses this monitor at 1920 x 1080. Any ideas on how to address this?
|
|
|
|
Howto: Getting Bluetooth (serial console) working on Debian |
|
Posted by: pfeerick - 09-20-2016, 03:18 AM - Forum: Wifi/BT Module
- Replies (14)
|
 |
Tested on a Pine64+ 1GB running Debian 8 “jessie” (3.10.102-3) using the official WIFI 802.11BGN/BLUETOOTH 4.0 Module.
What's it all about? These were the steps I followed to be able to view the text output of a bluetooth-enabled USB power meter, and most of these steps apply to getting bluetooth working at all if it isn't already configured in your chosen image. If it is already enabled, you can probably jump straight to step 5. Regardless, steps 1-5 should get your bluetooth working and a device paired with your pine64, but what you do after that if you don't want the text output (ie. you instead want a bluetooth mouse, audio) like I did I wouldn't know! ;)
Step 1: Make sure you have the bluetooth stack and utilities installed! If you want to all make sure you have all of the stuff this guide uses in one hit, you can add "rfkill git screen minicom" to the list of stuff to install.
sudo apt-get install bluez
Step 2: Get the firmware binaries for the BT from https://github.com/lwfinger/rtl8723bs_bt
This repo contains the programs and firmware to operate the Bluetooth section of the RTL8723BS. This basically loads the firmware into the module, which makes it a bluetooth module! if you don't have git, install it by running "sudo apt-get install git".
Quote:git clone https://github.com/lwfinger/rtl8723bs_bt.git
Step 3: Compile and load the firmware.
Change into the newly cloned repo, and run "make", which will compile the main program needed, rtk_hciattach. Then run "sudo make install" to install the firmware.
You’ll then want the following command to run at bootup, so perhaps put it in /etc/rc.local. For the moment though, you can run it as shown below.
Quote:sudo ./start_bt.sh
This is the command that does real magic… it configures the BT module and makes it available for use.
Step 4: Remove soft block, scan for devices
For some reason or another, the device is "soft blocked" (meaning it is blocked by software), which is easy to fix when you know how. Run
Quote:sudo rfkill list
and you should see something like this (if you don’t, something has gone horribly, horribly wrong already). If you get a message saying rfkill can’t be found, thats ok… just run "sudo apt-get install rfkill" to install it, and try again.
Quote:0: sunxi-bt: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
The entry of interest is the last one (the one for hci0: Bluetooth). That is the bluetooth adapter we’re trying to use, and as you can see, it is currently soft blocked. To fix that, just run (if yours is listed as 3 also)
Quote:sudo rfkill unblock 3
and it will be unblocked. You sould then see if you run "sudo rfkill list" again that this is the case, and if you run hcitool dev, you should also have something like this as the ouput, listing the MAC address of the pine64’s BT adapter.
Quote:Devices:
hci0 34:C3:D2:71:BE:ED
Step 5: Power on bluetooth module and pair your device
You can then run bluetoothctl (as sudo) in order tha manage the bluetooth connection. Install via ‘sudo apt-get install bluez-utils’ if it is missing. You should get an immediate message about a new bluetooth controller… this is a good sign… everything is working so far if you get that message. If you get a message about no default controller, something is wrong. Assuming you don’t have any issues, run the following commands, which power on the BT module and sets it as the default BT agent.
Quote:power on
agent on
default-agent
If all has gone well, you should be seeing something like this.
Quote:[NEW] Controller 34:C3:D2:71:BE:ED pine64 [default]
[NEW] Device 00:BA:55:56:D8:7E SPP-CA
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
You can then then enter "scan on" to start discovery of BT devices, and if you have any devices available for pairing, you should see messages about them appear (prefixed by [NEW]). If they’re not ready for pairing, this is the time to make them ready.
Once your device appears, you can run "scan off" to make the system a bit more responsive again, as it seems pretty laggy at times whilst the scan process is running.
To pair the device you’re trying to pair the pine64 with, enter the command "pair <your-bluetooth-deviceaddress>" . For example, my USB power meter with BT serial had an address of “00:BA:55:56:D8:7E”, so I entered “pair 00:BA:55:56:D8:7E” and entered the device pin when prompted. Once you see a message about the pair being successful (I had to do it a couple of times, it didn’t seem to take the first time) you can exit the bluetoothctl program with the quit command.
Step 6: Bind bluetooth device for usage
This step is what makes the bluetooth device available for you to access. It’s really simple.. just run "sudo rfcomm bind hci0 <your-bluetooth-device-address>"
For example,
Quote:sudo rfcomm bind hci0 00:BA:55:56:D8:7E
This binds hci0 (which you might remember from the rfkill list output from earlier) to the bluetooth device you specificied (usb power meter in my case).
Step 7: Do something with it!
Since I simply wanted to view the serial output from the meter, and I prefer using screen I ran
Quote:sudo screen /dev/rfcomm0 9600
in order to connect to the bluetooth device (made available at /dev/rfcomm0) at 9600 baud. (run "sudo apt-get install screen" to use screen as it’s not installed by default). For those of you who prefer minicom, you could do the same thing by running
Quote:sudo minicom -D /dev/rfcomm0 -b 9600
And then try figuring out how to exit it – hint: it’s Ctrl+a, z, q, enter).I then get a line like this every 5 seconds (the update rate I have the meter set to) telling me the voltage and amperage being measured by the meter. Success!
Quote:052496,005516
052496,005420
All it needs then is some simple decoding to change the interger values sent to their decimal equivalents (ie. the second line is 5.2496v and 0.5420A).
Assuming you were working with a device that didn’t work one way (the meter only ouputs the data, it doesn’t have any configuration or anything over the BT link), you sould then have proper two-way communication via your device and the pine64 over bluetooth!
Acknowledgements:
This information/guide would not be possible without the following sources:
Errata:
2016-09-25 - removed redundant part of step 3
2016-10-10 - removed reference to bluez-utils as isn't needed (or available!) for jessie
|
|
|
|
|
