my Pine doesn't boot as soon as I connect the Wifi/BT module.
Linux does a cold reboot when starting the kernel module for Wifi/BT (~15..20 after power on).
I tested different Images (Arch, Debian, Android) with different Pine A64 (1GB and 2GB).
Did I miss something or is the Wifi/BT module defective?
06-05-2016, 04:14 PM (This post was last modified: 06-05-2016, 07:23 PM by CHeitkamp.)
I'm somewhat disappointed about the PineA64 support, but maybe they are completely overstressed at the moment....
I wrote them a mail for this issue (and something missing from the order) about 1 month ago, but I never got an answer from them.
So I end up with an useless/defective Wifi/BT board and an incomplete acrylic case for now.
06-05-2016, 05:32 PM (This post was last modified: 06-05-2016, 05:50 PM by CHeitkamp.)
I tried different SD cards and power supplies, too.
The attached logs were done with the debian-mate-jessie-20160501-lenny.raposo-longsleep-pine64-8GB.img image on an Samsung EVO+ 32GB µSD card.
Only power, the SD card and the serial console were connected to the Pina A64 1GB.
I attached the serial console logs without (OK.txt) and with (FAIL.txt) Wifi/BT module attached.
06-05-2016, 07:00 PM (This post was last modified: 06-05-2016, 07:00 PM by pfeerick.
Edit Reason: typos
)
(06-05-2016, 05:32 PM)CHeitkamp Wrote: I tried different SD cards and power supplies, too.
The attached logs were done with the debian-mate-jessie-20160501-lenny.raposo-longsleep-pine64-8GB.img image on an Samsung EVO+ 32GB µSD card.
Only power, the SD card and the serial console were connected to the Pina A64 1GB.
I attached the serial console logs without (OK.txt) and with (FAIL.txt) Wifi/BT module attached.
Very first thing I'd do is update the kernel... you're running a very old version - 3.10.65-7-pine64-longsleep, when the current version is 3.10.101-4-pine64-longsleep, IIRC. You probably need up update uboot also. The easiest way to update these (if you have an ethernet connection you can use to get the pine64 on the internet) are:
and then reboot your pine64, and then try again. There is also a resize_rootfs.sh script in that folder you'll want to run if/when you do get the wifi working, as you'll only have access to 8GB of your 32GB card.
Also, just a dumb question... you are plugging in the wifi/bt module before powering up the pine64, aren't you... not while it's starting up... just checking!
If you still aren't getting any where, and longsleep doesn't have any tips or pointers... try and get hold tllim via a PM... seems to be more responsive that way at the moment.
In the meantime I got the help from Lukasz in the irc chat, but with the same result.
The uboot was already up-to-date and I posted another log with the most recent kernel,
a few minutes before your post.
About your not to dumb question:
I only (dis)connect the module, if the power cable is detached from the board.
I noticed 2 things about the wifi/bt module:
1. The APX803 gets quite warm, if the wifi/bt module is attached - usaly it stays cold
2. There are some unpopulated smd parts on the wifi/bt module - is this intended?
(06-05-2016, 07:37 PM)CHeitkamp Wrote: About your not too dumb question:
I only (dis)connect the module, if the power cable is detached from the board.
I noticed 2 things about the wifi/bt module:
1. The APX803 gets quite warm, if the wifi/bt module is attached - usaly it stays cold
2. There are some unpopulated smd parts on the wifi/bt module - is this intended?
Thanks for that... had to ask!
Ok, I was writing my reply when you posted that... so didn't see that till just now...
So, I can't comment on the APX803 atm, other than to say that with the module plugged it, it was certainly warm to touch, but I havn't run the pine64 without it, so don't know what different that makes to it's temperature in my case.
As far as populated components, on my module, there appear to be spaces for components (SMD resistors/capacitors) but not populated. Here is a pic of mine if that helps... which is working btw before you ask!
I just got my Board today (the 2gig Ram Variety) Downloaded the 5.1 Android DD (non-rooted) and plugged in the WIFI and same crap. Constant reboot, the board getting pretty toasty.. I am using my pi3 power supply. I can get things running but with this, doesn't seem like it's a software related issue at all since it reboots at the Pine64 screen and never even makes it to Lollipop...
(06-05-2016, 07:37 PM)CHeitkamp Wrote: 1. The APX803 gets quite warm, if the wifi/bt module is attached - usaly it stays cold
Further the APX803 being warm, I ran my pine64 for about 30 minutes without the wifi modules, powered it down, removed the module, waiting about five minutes for the temperatures to settle, and then ran it up again, with a couple other tests along the way. It would seem from the results that if the wifi module isn't really doing much, the AMX chip stays cool, if the wifi is active, it starts warming up a bit, but gets the hottest when the CPU is maxed out.
All measurements taken at an ambient temperature of 22*C, and an input voltage of 5.2v. First three measurements are temperatures of the chips (taken with a IR temp sensor - probably not the most accurate one around, but passable for comparison stats), final measurement is the avg power consumption @ 5.2v. Measurements were taken around the end of each run.
If you think the APX803 is getting hotter than say around 40*C at start up, or the power consumption of the pine64 is significantly more than 300-350ma whilst starting up, then I think there is something major wrong with the wifi board.
no wifi module
APX = 35/36
CPU = 45
MEM = 31/32
pwr = ~245mA
wifi module connected
APX = 36/37
CPU = 45
MEM = 31/32
pwr = ~251mA (no SSH connected)
pwr = ~317mA (SSH terminal active)
wifi module connected - playing internet radio over headphones via wifi \w SSH terminal active
APX = 40
CPU = 46
MEM = 32
pwr = ~321-326mA
wifi module connected - 5 mins stress (stress -c 4 -i 1 -m 1 -t 300)
APX = 52
CPU = 81/85
MEM = 41/42
pwr = ~680-720mA
