April 05, 2020, 03:40:48 pm


Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - GeorgeIoak

Looking at this a little more and in order to use the internal RTC of the A10 you would need to provide not only the 1.25V power but also a 32.768kHz crystal to balls Y13 and W13.

Looking at the Cubie schematic I see that W13 is tied to VCC-3V3 and Y13 is used for LCD/LVDS.

What's a bit curious to me is that when looking at the A10 datasheet the pin multiplexing tables make no mention of the RTC function and in fact only list W13 as a power pin (page 35 of http://dl.linux-sunxi.org/A10/A10%20Datasheet%20-%20v1.00%20%282011-08-22%29.pdf) but yet it's defined as the clock input on page 46 of that spec.

Not quite sure how you define a pin as AO on one page and then as a power pin on another page. I guess this is just another wonderful example of confusing documentation available to us!

Based on this I only see adding an external RTC chip as a viable option to getting RTC.

I think I'll add this to the next design of the baseboard...
Looking at your option #2 I don't think that's going to be an easy task for most people. If I'm seeing the Cubie schematic correctly. On page 2 it shows the A10 ball K8 as the RTC_VDD signal.

That pin is "routed" to net name RTCVDD and on page 7 is connected to the LDO1 output of the AXP209. So if you apply an external voltage to the RTCVDD it will be connected to the output of the AX209 which could cause the AXP209 to fail.

I haven't read through the AXP209 datasheet recently but I see that it has BAT1, BAT2 and a BATSENSE signas but none of them are routed so I don't see an easy way to take advantage of the RTC of the A10 which is a real shame.

You could add a RTC to one of the I2C buses and enable that in the kernel though.
I have about 10 boards completely built up but now I need to make the modification in order for VGA to work. What's missing is the female headers that the Cubie plugs into. The ones that I have are about 1mm too short so when the Cubie is plugged in the bottom of the Cubie hits the electrolytic caps. The boards that I have built up use a taller Samtec connector which I was planning on using but the cost of that connector is over $10 so not a good option for us!
Sorry, I mis-read Lawrence's post about the pin change. i should be good now that i know to use the other set of sync signals
Looks like some good work. What Linaro image are you using? Does your kernel have the Mali drivers loaded? I'm using the same VGA circuit and have not been able to get an image
Development / Re: Default NAND layout as seen from fdisk.
February 07, 2013, 06:07:23 pm
I've wondered why there are so many partitions in the NAND??
Quote from: Andre on February 02, 2013, 07:54:11 pm

@GeorgeIoak: My exams are done, and so I had some time and make a little board to try to interface the VGA.  I have built it according to the schematic posted by lawrence http://www.cubieforums.com/index.php/topic,6.msg10.html#msg10

That link was for CVBS, this is the design that most people are referring to when implementing VGA:
Cubieboard v1 Hardware (A10 Based) / Re: CVBS Output GPIO
February 02, 2013, 03:20:17 am
pretty much any scotky diod will work, try a BAT85S

Why are you using -j4 on your compile line and the first steps is using -j5, what's the difference?

In your steps you don't show compiling the modules but if you have a new config and changed anything don't you need to compile the modules and then also copy them over to your rootfs?
@castalla I prefer to run a Vm using VirtualBox on my Win7 x64 machine. Some of the instructions say that you need a Ubuntu x64 version so that is what I installed. My daily PC is the Win7 x64 so I prefer the VM since I can treat it like a window and let it run without tying up a machine. I have a fastmachine with 16GB of memory so the VM runs almost as fast as a normal machine.
when I ran this step:

Quote#create a partition 64M in size at 1M, then another partition at 66M till end of the disk
sfdisk -uM /dev/[yourcard]

I get an error at the 67,,L line saying that it has to start at 68 or greater. If I did that I ran into some other problems. I switched to fdisk and it worked OK.
tried downloading http://dl.cubieforums.com/loz/rootfs/Linaro-ALIP-with_MALI_and_X.tar.bz2 several times and different ways and it's always corrupt.
use this guide, http://linux-sunxi.org/Mali400 read the whole page but start at:

Mali-400 X11 DRI2 drivers
Development / Re: Unfinished notes on video side on x11
January 30, 2013, 08:08:33 pm
I hope I'm not spamming your thread too much but just trying to add info in case anyone else follows this and has the same problem.

Checking what's installed I find the following that I extracted (just based on what looked like it was relevant):

dpkg --get-selections

libegl1-mesa install
libegl1-mesa-dev install
libegl1-mesa-drivers install
libgl1-mesa-dev install
libgl1-mesa-dri install
libgl1-mesa-glx install
libglapi-mesa install
libgles2-mesa install
libgles2-mesa-dev install
xserver-xorg-video-ati install
xserver-xorg-video-fbdev install
xserver-xorg-video-mach64 install
xserver-xorg-video-nouveau install
xserver-xorg-video-r128 install
xserver-xorg-video-radeon install
Development / Re: Unfinished notes on video side on x11
January 30, 2013, 07:26:51 pm
Going to hunt to see why I'm getting this DRI2 error

linaro@linaro-ubuntu-desktop:~/gfx/xf86-video-mali$ es2_info
libEGL warning: DRI2: failed to authenticate
EGL_VENDOR = Mesa Project
EGL_EXTENSIONS = EGL_KHR_surfaceless_gles1 EGL_KHR_surfaceless_gles2 EGL_KHR_surfaceless_opengl
GL_VERSION: OpenGL ES 2.0 Mesa 8.0.2
GL_RENDERER: Software Rasterizer
    GL_EXT_blend_minmax, GL_EXT_multi_draw_arrays,
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_format_BGRA8888,
    GL_OES_depth24, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,
    GL_OES_mapbuffer, GL_OES_rgb8_rgba8, GL_OES_standard_derivatives,
    GL_OES_stencil8, GL_OES_texture_3D, GL_OES_texture_npot,
    GL_OES_depth_texture, GL_OES_packed_depth_stencil,
    GL_EXT_texture_type_2_10_10_10_REV, GL_NV_fbo_color_attachments,