Digging through another Android Linux source I found one for the Marsboard
version 3.3 and it too has the same strange mV value for the
voltage_min_design and uV value for voltage_max_design.
I dug through both code and there is no multiplier added to
voltage_min_design when it is used. At one
I am running Android sunxi-linux 3.4 and on boot up, with battery power
only, I see the following in the debug output.
[0.148] boot1 version : 2.0.0
[0.149] script installed early ok
[0.149] pmu type = 3
[0.253] bat vol = 3894 mv
This corresponds pretty much with what I am reading with a
Hi Bruno,
The battery voltages I assume are set internally to the AXP209 as I don't
see any way to set these. I did find a listing for these.
Yes, this is the Android Linux 3.4 kernel.
When I get the likes of 18% showing on the Android status bar and check the
actual voltage of the battery it
On Saturday, 20 September 2014 22:40:04 UTC+7, Bruno Prémont wrote:
Hi Dave,
Does it happen for each suspend oder just sporadically? If sporadically
it
might be a race condition where some AXP data got read before suspend,
the
rest after resume - ending up with incoherent data and
With an A20 board I have found that if I power up with external DC
connected, the battery shows the correct charge percentage. If I run on
batter and make sure it never sleeps (through the app I am developing) it
discharges as expected.
If I disconnect DC and run on the battery and *put it
Looking at the FEX file for an Olimex-A20 and a Cubieboard this entry looks
like this.
pmu_adpdet = port:PH020defaultdefaultdefault
But on the Olimex-A20 this pin is connected to a notification LED. It is
not used in the schematic of the Cubieboard that I found.
Looking at the AXP209 I found
I think this is very possible from a suitably written custom SD boot option
but you are going to have to write your own drivers to do this.
From what I can tell, the A20 looks on the SD for a boot partition so if
you can create your own boot you could do this. Trouble is, I don't know if
I have followed the instructions on how to create a new initlogo file but
the size does not match when init tries to use it.
I used the following on a png file that is 800 x 480 and the file size is
119,306 bytes.
After I run *convert -depth 8 initlogo.png rgb:initlogo.raw* the .raw file
is
I got it working by changing the name as below.
static struct i2c_board_info __initdata ds1307_i2c_board_info[] = {
{
.type = ds1307,
.addr = 0x68,
},
};
The bit that got this working was the change of the name to ds1307 instead
of rtc-ds1307 which was the name of the
I've ported a touch driver to my system and each time the interrupt handler
fires I am seeing this in the debug output.
gpio_irq_hdl: handler failed
I've checked the handler and it is passing back IRQ_HANDLED to this
function so it appears to be a bug in the code here.
if
Hi Oliver,
I finally got it working this weekend and posted the results on my blog.
I had to add some code to the Fusion driver to pass back detection state
and also make changes to use the AllWinner GPIO drivers and read the
sysconfig.fex during init.
There was also a bug in the eint driver
I am trying to get an interrupt input to but I get an error when I try to
set PC19 as an interrupt input.
According to the datasheet on page 243 it can be EINT12 but elsewhere in
the doc, EINT12 is shown for PH12.
It looks like the document is wrong.
--
You received this message because you
I am trying to port a touchscreen driver to my system and I have the module
building and installing.
I have added it to the auto detect code in device.c and I can see in dmesg
that the driver from i2c-core gets detected and the init function is
called.
What never gets called is the probe
Hi Alejandro, I ran a diff and ended up with a 384MB patch file. My first
time using this so I need to see how to filter the input so that only
source files are compared. :)
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe
Check with your hardware guy on the voltage of the TX line as you do not
want to be putting anything near 5V into the A20. It is not 5V tolerant on
the GPIO pins and will most likely damage the A20 IO.
The datasheet quotes the max input as 3.6V.
On Sunday, 16 February 2014 19:01:53 UTC+7,
You say it works with a USB to Serial cable? Is that adapter at RS232 levels or
TTL?
That's important as the GPIO would be at 3.3V which is commonly called TTL even
though most still refer to this as 5V the term is often used to mean processor
voltage levels.
If your custom board is an
Hi Emilio,
My kernel build seems to be OK. I look at what you said and using
imgRePacker I replaced the working Android image with my faulty Android
image and this way I would be using the working Linux kernel and it gives
the same error.
I then tried the other way around and used my Linux
I think I may have tracked the problem down or at least found out why it is
failing to load the display drivers.
I added some debug to the hardware.c file to show which modules where being
loaded and looked up. This is what happened with the display module
W/HAL ( 1160): Loading module
Hi all, I am new to the group.
I have an Olinuxino-A20 board that I have been trying to get Android
working on. The source builds but surfaceflinger crashes during the boot
cycle. Something I am still working on in trying to get Olimex to supply
ALL of the files as some configuration are
19 matches
Mail list logo
