February 24, 2020, 12:01:13 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 - vinifr

Hi guys,

i'm trying to boot mainline sunxi-next taken from https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-next, but hangs here:
Starting kernel ...
Hi guys, here is the link to new video with right commands:


Here is the link to my .config: https://dl.dropboxusercontent.com/u/22273442/a13/configs/config_sunxi_mainline3

I enabled a lot of things, but there is still a lot of thing to enable.
List of videos showing every step of the configuration and building of Linux kernel for A13. But also works to A10!  ;)

Part 1 (Installing Toolchain): https://www.youtube.com/watch?v=3xNdH9SquL4

Part 2 (Compiling linux sunxi): https://www.youtube.com/watch?v=ilDhOzmkORY

Part 3 (Copying Modules): https://www.youtube.com/watch?v=LWJ11nJ_0-k

I'm also having problems with OpenCV. I cannot build/cross-compile OpenCV with libucil2-dev because i am using debian7, there is only libucil2-dev for debian6. :'(

If you intend to use webcam must enable UniCap: http://indranilsinharoy.com/2012/11/01/installing-opencv-on-linux/
As I said, you can not use .tx_buf and .rx_buf at same time. What software do you use to test SPI0. Is SPI0 available?

Also look for pins conflicting into script.fex. ;)
Wow, sorry for long time.  :o I was using ubuntu, but now I'm using debian7.

IMG means file system? Kernel image?

In order to compile vlc I copied it to the card and follow the instructions.
Without the patch, you must set .tx_buf=0 when reading and .rx_buf=0 when writing! You can not use .tx_buf and .rx_buf at same time, as spidev does.

.tx_buf = (unsigned long)tx,
.rx_buf = (unsigned long)rx,

This way, it is necessary to transfer two messages, one for reading and one for writing.

// for writing
struct spi_ioc_transfer tx = {
.tx_buf = (unsigned long)tx,
.rx_buf = 0,
.len = ARRAY_SIZE(tx),
.delay_usecs = delay,
.speed_hz = speed,
.bits_per_word = bits,
// for reading
struct spi_ioc_transfer rx = {
.tx_buf = 0,
.rx_buf = (unsigned long)rx,
.len = ARRAY_SIZE(tx),
.delay_usecs = delay,
.speed_hz = speed,
.bits_per_word = bits,

// writing
ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tx);
// reading
ret = ioctl(fd, SPI_IOC_MESSAGE(1), &rx);

Have you already searched the driver specific to this ADC?
Unfortunately spi_sunxi have no support for full-duplex, this way spidev0.0 doesn't work. But a patch was submitted: https://groups.google.com/forum/?fromgroups=#!topic/linux-sunxi/yEmBiaJ3LAI
Cubieboard v1 Hardware (A10 Based) / Re: using PWM
July 15, 2013, 08:56:19 am
Do you applied the patch yourself? Which pins are you using? Look for conflicts: http://linux-sunxi.org/A10/PIO
Basically interrupts can be used only by device drivers. But there is mechanisms available to the user space like 'egde' for gpio.

For timers, you can use function alarm(): http://linux.die.net/man/3/alarm
You need to select a pin and then configure the correct multiplexer: http://linux-sunxi.org/A10/PIO

Example: PB02 or PI03: both use MUX2

Note: This patch has not been applied, would be better to wait! ;)