| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,454
» Latest member: Pattienner
» Forum threads: 16,190
» Forum posts: 116,850
Full Statistics
|
|
|
| [Solved] Boot Issues |
|
Posted by: dedseason - 05-30-2017, 12:43 AM - Forum: General Discussion on PINE A64(+)
- Replies (9)
|
 |
Recently, I'm having boot issues with my pine64 1GB model.
I normally run the board as a headless server and the uptime was almost 3 months. I run transmission-daemon, plexmediaserver, and ssh-server on the board. For OS, I was using Debian Jesse (I think kernel version 3.10, but not 100% sure).
Additional information:
- SSH runs on a non-standard (not 22) port (no VPN)
- Normally I have external HDDs plugged into the board via an externally powered USB hub
- Board does not boot with or without Ethernet
- Board does not boot with HDMI plugged in
- Board does not boot with or without external USB hub plugged in
- I've been using the OnePlus One charger as a power supply for over a year without an problem (I believe it's 5V 2A)
- I have tried other phone chargers as well to no avail
- When power is supplied, board light turns red but I cannot ssh into the board nor does it power an external display via HDMI
- My SD card is G.Skill 32GB Class 10 MicroSDHC
Any ideas as to what could be the issue?
|
|
|
|
| SOPINE A64 DRAM init error |
|
Posted by: vicb - 05-29-2017, 02:49 AM - Forum: General Discussion on PINE A64-LTS / SOPINE
- Replies (2)
|
|
Hi!
I received the SOPINE A64 with motherboard.
The problem is that the initializing SDRAM Fail
The log from serial console:
Code: HELLO! BOOT0 is starting!
boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f
boot0 version : 4.0.0
set pll start
set pll end
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
DRAM driver version: V1.1
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1500 mv
DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 672 MHz
DRAM zq value: 003b3bbb
DRAM error status 0
DRAM init error!
initializing SDRAM Fail.
It's a hardware problem or can I solve it?
Thank you!
Mod edit: wrapped terminal output in code tags - heaps with long code, and also prevents 'smilies' randomly popping up
|
|
|
|
How to go about setting up your own Jenkins build system for pine64 / pinebook images |
|
Posted by: pfeerick - 05-28-2017, 11:05 PM - Forum: General Discussion on PINE A64(+)
- Replies (2)
|
 |
This is basically a place to try and document what I have done, and find out what I need do in order to get this working. I've flagged it as pine64 and pinebook related as ayufan's builds support both at this point in time.
So, what am I trying to do? Basically, I have crappy internet, and come computers around which are more than capable of grunting their way through compiling and building images for the pine64 / pinebook. This would also let me look into customising the images, and doing some work on them myself... maybe.  I've played with docker a little bit, and have used Travis CI in the past, so thought how hard could this be? Famous last words. 
I decided one of my pine64 servers could be the jenkins boss, so loaded jenkins 2.46 (as it's the LTS version) on that that. Easy peasy, had everything up and running in under 20 minutes. Set up a build node or two on the ubuntu x64 boxes, so that they could be responsible for the actual builds, so the pine64 only had to manage them from afar. Since the Jenkins file in the repo wanted a node with both the docker and linux-build tags, I made sure one of them had that, was running LTS 16.04, and had docker on it, and had actually also manually build the build-environment docker on it also (but that was more to test if it was working than actually configure anything, and I did end up deleting it at one point just in cause it was the cause of the issue).
I then setup the new pipeline, configured it as a pipeline script from SCM -> Git -> https://github.com/ayufan-pine64/linux-build and left pretty much everything else as defaults. Tried running the pipeline, had to double back and install the AnsiColor plugin, and then the build ran. It downloaded the repo file, logged into the build node, and started building the docker container without any dramas. So it gets to the end of the docker build, and promptly and consistently dies. I'll include some logs below, but does anyone (especially ayufan or tkaiser) have any ideas what I'm doing wrong? Am I missing some blindingly obvious configuration step that I should have known about before attempting any of this?
I even setup jenkins on the same machine that was doing the build, and set it as the docker/build node, tried playing with docker plugins with no luck, and installed blue ocean just incase it was related to a plugin it added.
I *think* the issue is related to this entry in the log, but I'm not sure, and I don't know how to correct it, hence this post. asus-h55d is the host-name of the node which the build was slaved out to, and it's this line that stands out as different from the logs from ayufan's builds.
Code: [Pipeline] withDockerContainer
15:33:39 asus-h55d does not seem to be running inside a container
This is the plain text build log: http://sprunge.us/LaPW
This is the log that blue ocean shows, which rather helpfully doesn't actually show why the environment stage failed: http://sprunge.us/IiVU
Can anyone help?
|
|
|
|
|
Remix OS 2.0 [20170105] Waaaa??? |
|
Posted by: veronicasmithen03 - 05-26-2017, 02:58 PM - Forum: Remix OS
- Replies (1)
|
|
So I haven't seen it mentioned in this section that on the Wiki page there is a newer Remix OS release dated 2017/01/05. What exactly is the difference/advantage to running that version over the latest version discussed here? I don't see any mention of it here, so I am unsure whether there is any difference/advantage?
It's getting a bid odd having multiple versions of the same OS, in different places. Some of the OS's on the Wiki page seem to be the "wrong" version. Example - people are being told to use the Android 6 img that's from ayufan on the forum/github, but there are three android v6 builds there - two of them being newer than ayufan's builds.
Cheers
|
|
|
|
| Enabling wolfson wm8960 i2c/i2s sound codec |
|
Posted by: saro - 05-26-2017, 07:23 AM - Forum: Pine A64 Hardware, Accessories and POT
- Replies (5)
|
|
Hi,
I'm trying to use the chip wolfosn wm8960, that is connected with I2C interface and I2S bus.
Polling it on the I2C bus, the peripheral is recognized with address 0x1a on i2c-1, but nothing related to this device like sound card found.
Another preliminary step follewed is the kernel compilation, making by activation the driver wm8960 found in sound/soc/devices/ like built-in and enabling all voices found in "--- ASoC support for SUNXI" of menuconfig.
At this step, applying the new kernel, I don't found any peripheral with arecord -l or aplay -l or with pactl command and there isn't any row in the syslog/kernlog that show me that the wm8960 device is found.
There are few references for this codec, but I'm trying to follow the guide posted for another soc (i.MX6) in which the device driver already built-in inside the kernel source tree, showed at: https://community.nxp.com/docs/DOC-106295
Another link (for i-MX6) report also that:
Code: WM8960
Driver location: linux/sound/soc/codecs/wm8960.c
Machine driver location: linux/sound/soc/imx/imx-wm8960.c
1.In Kernel Configuration, go to
Device Drivers --> Sound card support --> Advanced Linux Sound Architecture --> ALSA for SoC audio support --> SoC Audio for Freescale i.MX CPUs -->
2.Select <*> SoC Audio support for IMX boards with WM8960
In this case, I found
Code: linux/sound/soc/codecs/wm8960.c
Code: Machine driver location: linux/sound/soc/imx/imx-wm8960.c
I have to specify, for example, some configuration in the dts device tree?
Is impossible to see the peripheral because there isn't the imx-wm8960.c machine based driver file matching the pine64 board?
Can someone help me, please?
Thanks in advance.
|
|
|
|
|
)