Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 28,531
» Latest member: lavabrilliant
» Forum threads: 15,853
» Forum posts: 115,343

Full Statistics

Latest Threads
No HDMI Video - Anything ...
Forum: General Discussion on ROCKPRO64
Last Post: KC9UDX
6 hours ago
» Replies: 2
» Views: 72
Pinetab 2 Not Powering On...
Forum: General
Last Post: tllim
Yesterday, 12:25 PM
» Replies: 3
» Views: 177
Some Suspense.... Camerra...
Forum: Mobian on PinePhone
Last Post: biketool
09-28-2024, 10:32 PM
» Replies: 3
» Views: 114
July 1 upgrade of Mobian ...
Forum: PinePhone Pro Software
Last Post: mburns
09-26-2024, 09:56 AM
» Replies: 3
» Views: 763
desktop and lockscreen
Forum: Mobian on PinePhone
Last Post: biketool
09-25-2024, 05:11 AM
» Replies: 0
» Views: 75
2024 Sep 21 - PinePhonePr...
Forum: General Discussion of PinePhone Pro
Last Post: biketool
09-25-2024, 04:16 AM
» Replies: 8
» Views: 2,444
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: zetabeta
09-25-2024, 12:41 AM
» Replies: 36
» Views: 6,673
Can't install some softwa...
Forum: General Discussion on PineTab
Last Post: mikehenson
09-24-2024, 07:49 AM
» Replies: 2
» Views: 166
Testing Some More Games o...
Forum: General Discussion on Pinebook Pro
Last Post: pigkang
09-24-2024, 01:43 AM
» Replies: 5
» Views: 3,457
Developing on Mac (M3)
Forum: Development Discussion on PineTime
Last Post: oksalahti
09-23-2024, 01:27 AM
» Replies: 1
» Views: 93

 
Sad No update on shipping for Backer number #245
Posted by: seven77j - 06-18-2016, 06:22 AM - Forum: Shipment Related Discussion - Replies (14)

Backer number #245. 7 weeks after the 4/28 CN tracking number was sent. Nothing received. The tracking numbers has show only up to 23rd of April. No response to my mails also.


  AXP803 Battery Charger Support
Posted by: xalius - 06-18-2016, 03:28 AM - Forum: Linux on Pine A64(+) - Replies (14)

I am currently investigating how the battery charger in the PMIC (AXP803) is supported by the software. Being a hardware guy I was working my way up from the bottom side of things, starting with the physical connection and the PMIC:

The battery seems to be connected to the PMIC via a load sensing (current sensing) shunt and the PMIC has a switch that connects the battery to the inputs of the voltage
regulators once certain conditions are met. There is also an input on the battery connector to attach a 10k NTC for monitoring the battery temperature. The PMIC contains a battery charger that charges the battery depending on what DC power source is available (USB/DC IN).

From the AXP803 Datasheet:

- Vbat charge target voltage = 4.2V typical
- Charge current can be set between 200 and 2800mA, 1200mA typical
- Trickle charge current is 10% of normal charge current

- There are two safety timers which can be programmed to limit regular/trickle charging after x minutes (480 min / 50min typical)
- Charging stops in CV mode if the normal charge current drops below 10% of the set charge current
- The NTC monitor has different trip points like cold fault, hot fault for operation and charging which can be programmed in the PMIC
- Battery isolation current is 40uA


- Turning on the PMIC happens by either applying USB/DC_IN or pushing the power button
- Turning off the PMIC happens by undervoltage lockout, fault condition, power button or software writes to a register
- The charger starts working once the voltage input from USB/DC_IN is between 4.1V and 7V

- Input to the regulators is automatically selected from Battery, DC_IN or USB
- USB/DC_IN are preferred over Battery
- If USB and DC_IN are not connected together, DC_IN is preferred over USB
- If USB/DC_IN drops below certain thresholds, Battery takes over
- Input can be controlled by registers

- The function of the charge LED can be controlled via registers

- The PMIC is connected to the A64 via a I2C interface

I have looked at the device tree file and it seems to contain some default setting for the PMIC (and the charger):


Code:
pmu0@0 {
           compatible = "allwinner,pmu0";
           device_type = "pmu0";
           pmu_batdeten = <0x00000001>;
           pmu_init_chgend_rate = <0x00000014>;
           pmu_init_chg_enabled = <0x00000001>;
           pmu_init_adc_freq = <0x00000320>;
           pmu_init_adcts_freq = <0x00000320>;
           pmu_init_chg_pretime = <0x00000046>;
           pmu_init_chg_csttime = <0x000002d0>;
           pmu_batt_cap_correct = <0x00000001>;
           pmu_chg_end_on_en = <0x00000000>;
           pmu_pwroff_vol = <0x00000ce4>;
           pmu_pwron_vol = <0x00000a28>;
           pmu_powkey_off_delay_time = <0x00000000>;
           pmu_pwrok_time = <0x00000040>;
           pmu_reset_shutdown_en = <0x00000001>;
           pmu_restvol_adjust_time = <0x0000003c>;
           pmu_ocv_cou_adjust_time = <0x0000003c>;
           pmu_vbusen_func = <0x00000001>;
           pmu_reset = <0x00000000>;
           pmu_IRQ_wakeup = <0x00000001>;
           pmu_hot_shutdowm = <0x00000001>;
           pmu_inshort = <0x00000000>;
           pmu_bat_shutdown_ltf = <0x00000c80>;
           pmu_bat_shutdown_htf = <0x000000ed>;
           status = "okay";
           pmu_id = <0x00000006>;
           pmu_twi_addr = <0x00000034>;
           pmu_twi_id = <0x00000001>;
           pmu_irq_id = <0x00000040>;
           pmu_chg_ic_temp = <0x00000000>;
           pmu_battery_rdc = <0x00000058>;
           pmu_battery_cap = <0x000012c0>;
           pmu_runtime_chgcur = <0x000001c2>;
           pmu_suspend_chgcur = <0x000005dc>;
           pmu_shutdown_chgcur = <0x000005dc>;
           pmu_init_chgvol = <0x00001068>;
           pmu_ac_vol = <0x00000fa0>;
           pmu_ac_cur = <0x00000dac>;
           pmu_usbpc_vol = <0x00001130>;
           pmu_usbpc_cur = <0x000001f4>;
           pmu_battery_warning_level1 = <0x0000000f>;
           pmu_battery_warning_level2 = <0x00000000>;
           pmu_chgled_func = <0x00000000>;
           pmu_chgled_type = <0x00000000>;
           pmu_bat_para1 = <0x00000000>;
           pmu_bat_para2 = <0x00000000>;
           pmu_bat_para3 = <0x00000000>;
           pmu_bat_para4 = <0x00000000>;
           pmu_bat_para5 = <0x00000000>;
           pmu_bat_para6 = <0x00000000>;
           pmu_bat_para7 = <0x00000001>;
           pmu_bat_para8 = <0x00000001>;
           pmu_bat_para9 = <0x00000002>;
           pmu_bat_para10 = <0x00000003>;
           pmu_bat_para11 = <0x00000004>;
           pmu_bat_para12 = <0x0000000a>;
           pmu_bat_para13 = <0x00000011>;
           pmu_bat_para14 = <0x0000001a>;
           pmu_bat_para15 = <0x00000029>;
           pmu_bat_para16 = <0x0000002e>;
           pmu_bat_para17 = <0x00000033>;
           pmu_bat_para18 = <0x00000038>;
           pmu_bat_para19 = <0x0000003b>;
           pmu_bat_para20 = <0x00000041>;
           pmu_bat_para21 = <0x00000045>;
           pmu_bat_para22 = <0x0000004b>;
           pmu_bat_para23 = <0x0000004f>;
           pmu_bat_para24 = <0x00000053>;
           pmu_bat_para25 = <0x00000059>;
           pmu_bat_para26 = <0x0000005f>;
           pmu_bat_para27 = <0x00000062>;
           pmu_bat_para28 = <0x00000064>;
           pmu_bat_para29 = <0x00000064>;
           pmu_bat_para30 = <0x00000064>;
           pmu_bat_para31 = <0x00000064>;
           pmu_bat_para32 = <0x00000064>;
           pmu_bat_temp_enable = <0x00000001>;
           pmu_bat_charge_ltf = <0x000008d5>;
           pmu_bat_charge_htf = <0x00000184>;
           pmu_bat_temp_para1 = <0x00001d2a>;
           pmu_bat_temp_para2 = <0x00001180>;
           pmu_bat_temp_para3 = <0x00000dbe>;
           pmu_bat_temp_para4 = <0x00000ae2>;
           pmu_bat_temp_para5 = <0x000008af>;
           pmu_bat_temp_para6 = <0x000006fc>;
           pmu_bat_temp_para7 = <0x000005a8>;
           pmu_bat_temp_para8 = <0x000003c9>;
           pmu_bat_temp_para9 = <0x00000298>;
           pmu_bat_temp_para10 = <0x000001d2>;
           pmu_bat_temp_para11 = <0x00000189>;
           pmu_bat_temp_para12 = <0x0000014d>;
           pmu_bat_temp_para13 = <0x0000011b>;
           pmu_bat_temp_para14 = <0x000000f2>;
           pmu_bat_temp_para15 = <0x000000b3>;
           pmu_bat_temp_para16 = <0x00000086>;
           pmu_powkey_off_time = <0x00001770>;
           pmu_powkey_off_func = <0x00000000>;
           pmu_powkey_off_en = <0x00000001>;
           pmu_powkey_long_time = <0x000005dc>;
           pmu_powkey_on_time = <0x000003e8>;
           power_start = <0x00000000>;
};


There seems to be a driver for the PMIC in the Linux kernel (drivers/power/axp_power/) that interfaces with the PMIC and is used for register access, controlling the various output voltages (CPU frequency scaling etc...) and the battery charger operation. Some of  the information is also exported via sysfs and can be read from /sys/class/power_supply/ , /sys/class/regulator and other places.

My question is now, what would be the correct way to handle battery charging, what would be a good way to set the charger defaults and are there any userspace tools available already that can use the subsystems for monitoring etc... ?


Photo Recycled Clear Modem case
Posted by: jjmgryphon - 06-18-2016, 02:47 AM - Forum: Enclosures - Replies (2)

On receiving my battery today, I decided it was time to put the old cardboard case I made from the shipping box (great for initial testing) and move up to something with more space and stability.  Found my old Clear modem and decided it would work great.  Had to dremmel, sand, eyeball and tape but eventually I ended up with the following:
[Image: 13423756_10208416506024661_8127703958426...e=57D9C397]
Due to not being able to find any right angle audio plugs I had to cut a hole for it to extend out of the case and back into where the speaker is housed.  After thinking about it I liked this idea as it allows me to still plug in headphones when I'm on the go.

I salvaged the old Clear antenna and used it instead of the provided one with the wifi/bt hat.  What do you know, I can now receive wifi from down the street.

Here are images of the other sides minus back as it is just a lot of clear info.  Will have to put a nice print out of something back there to finish out the mod.
[Image: 13495665_10208416506384670_5180447306309731828_o.jpg][Image: 13418441_10208416506224666_3486499833463613513_o.jpg]
[Image: 13475110_10208416506184665_8291963304572830887_o.jpg][Image: 13443311_10208416576786430_250911135047268314_o.jpg]

Biggest problem I ran into is the 30 pin ribbon cable for the display was about an inch too short to have the display exactly centered so it is sitting lower then expected (and the black piece of tape covers the origonal slot the cable used).  After readjusting it several times everything fits and works.  

In the last pic you can see where I cut out part of the grill of what used to be the bottom of the modem so I can get easy access to the SD card for ease of changing.

Hope this gives some people ideas to work with.


  Still not shipped...
Posted by: Cyrel - 06-17-2016, 09:35 PM - Forum: Shipment Related Discussion - Replies (1)

I got my Pine from the official shop, it was to be shipped in Late May - June and I've been waiting since 5th of April..

102285870 this is my order number and I've seen that most of the orders that start with #102 has been already shipped..


  Actual voltages, amperage
Posted by: NexusDude - 06-17-2016, 03:12 PM - Forum: USB 2.0 Ports - Replies (13)

This is not a complaint, but just FYI for anyone who wants to know. I've had zero issues with the Pine's USB ports.

According to my USB meter, I've seen the voltages of the USB 2 ports vary between 4.77 - 4.94V. Typically, 4.89 - 4.92V.

The amperage is 0.07 - 0.08A for the flash drives I've tested. 
For keyboard, mouse, or powered hard drive, it's 0.00A.
I don't have a working wifi dongle, yet...


  Android + battery
Posted by: dulasu - 06-17-2016, 12:53 PM - Forum: Android on Pine A64(+) - Replies (2)

Hi there,

Is it possible to configure Pine's behavior when it's powered with a battery?
Mine board turns off a usb port (maybe it even turns off ethernet can't check it exactly without working mouse Smile ).

Dzmitry


  Slow boot on Remix os and Debian
Posted by: djkatpt - 06-17-2016, 12:32 PM - Forum: General Discussion on PINE A64(+) - Replies (5)

Hello there,

I have a pine64 with 2Gb Ram.
Also have two images from the latest build for Remix OS and Debian OS
My SD card is class 10 with 64Gb.

using win32diskimager i uploaded the remix os image to the Sd card.
I took more or less 10 minutes for the system to boot into remix with very slow operation if i tried to make something like open google play or something.

The same appened in Debian.
I even tried to update the system to see if there was something needing update, but this task when it doesn't give error takes ages.

What can I do to correct this?
is it a Pine64 error?

David


  Basic IR Support
Posted by: xalius - 06-17-2016, 10:07 AM - Forum: Linux on Pine A64(+) - Replies (2)

Hi, I just mounted the IR receiver that came with the basic Pine Remote on my board. After reading the User Manual and checking the schematics, I know now that the A64 has a dedicated IR receiver block that does low level decoding. According to http://linux-sunxi.org/IR there was legacy support for that for the other sunxi SoCs as a keyboard device and there is a newer driver for 4.x Linux. I had a look at the devicetree entries and it's there with the correct base address... Is this something we could enable in the 3.10.x kernel ?


  I2C
Posted by: igna09 - 06-17-2016, 09:55 AM - Forum: Pi2, Euler and Exp GPIO Ports - Replies (4)

Hi, is possible to enable i2c?


  What am I doing wrong?
Posted by: Gauloises - 06-17-2016, 09:05 AM - Forum: Getting Started - Replies (3)

Howdy folks

I've tried for 3 days now to get my Pine64 up and running but it just refuses to work properly.

First I installed the 64gb remix OS version on my 64gb class 10 sandisk, this worked... almost, whenever i ran an application it would crash to a black screen
I tried reinstalling, reformatting etc.. 5 or so times but still fared no better.
Next I attempted to install the more compact phoenix version which didn't even get past the keyboard language option.

Giving up on Remix I tried out Android 
doing the exact same thing but never getting past the 'verifying apps' load screen

My SD card is legit and works with other boards, my cable is perfectly fine and again works with other boards. Even my power supply is rated correctly, having tried 2 that didn't work at all. 

What am I doing wrong? Every time I start up without usb attachments, follow all available online instructions, tried 4 different sd cards and can't get the damn thing to work!


Info:

SD: Sandisk Ultra Class 10 64gb and Samsung Memory 32 GB Evo
Power type: micro usb to usb, connected to a 5v 2.1a UK adapter | UPDATE - also tried NorthPada Mains Charger 5V 2000mA / 2A

OS types tried:

8gb Remix OS (latest) - Written to sd card via Win32DiskManager after being formatted with SDFormatter
64gb Remix OS (latest) - Written to sd card via Win32DiskManager after being formatted with SDFormatter
Phoenix type Remix OS - Written to sd card via Phoenixcard after being formatted with SDFormatter

64gb Android non-rooted (latest) - Written to sd card via Win32DiskManager after being formatted with SDFormatter
64gb Android rooted (latest) - Written to sd card via Win32DiskManager after being formatted with SDFormatter
Phoenix type android - Written to sd card via Phoenixcard after being formatted with SDFormatter

None of the above worked, either giving me black screens or failing to fully boot.