olimex / olinuxino Goto Github PK

I have just updated the firmware of my rt5350f to the last release of chaos calmer
https://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/rt305x/openwrt-15.05.1-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin
After having finished the installation via tftp I noticed that the free space is now just 232 KB, while it was 2 MB with the previous version. Is there any module or packet that has been added and that I can remove. Do you think I did something wrong?

On the current version of chaos calmer 15.05.1 when I type df -h I obtain:

root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 448.0K 216.0K 232.0K 48% /
/dev/root 2.3M 2.3M 0 100% /rom
tmpfs 14.2M 624.0K 13.6M 4% /tmp
tmpfs 14.2M 48.0K 14.2M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock6 448.0K 216.0K 232.0K 48% /overlay
overlayfs:/overlay 448.0K 216.0K 232.0K 48% /

On the previous version instead:

root@OpenWrt:/# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 4.2M 2.1M 2.1M 50% /
/dev/root 2.5M 2.5M 0 100% /rom
tmpfs 14.3M 432.0K 13.8M 3% /tmp
/dev/mtdblock6 4.2M 2.1M 2.1M 50% /overlay
overlayfs:/overlay 4.2M 2.1M 2.1M 50% /
tmpfs 512.0K 0 512.0K 0% /dev

iMX233-OLINUXINO uses processor on 454Mhz and have less memory and will not allow fancy graphics, but this is not our intention.

Wait, the site says it's an A20 dual core Cortex-A7 processor. Does this description still apply? I would think it was more powerful than a raspberry pi now.

Is this process on "Step 5"?

The summary sheet A20_LIME2_GPIOs.pdf mentions GPIO2 and GPIO3 on connector GPIO-4 but that is actually wrong. It should be labled as PA9 and PA14.

GPIO2 and GPIO3 yield the intention that they are pins from the AXP209.

I was able to get it to boot Debian successfully using the Sunxi bootloader and the Debian ARM64 port, however I get the following kernel errors (below).

Does anyone have any clues as to how to resolve these problems?

[    1.186363] Freeing unused kernel memory: 448K
[    1.892064] systemd[1]: System time before build time, advancing clock.
[    1.973534] x_tables: version magic '4.13.13 SMP preempt mod_unload modversions aarch64' should be '4.13.13 SMP mod_unload aarch64'
[    1.985513] systemd[1]: Failed to insert module 'ip_tables': Exec format error
[    2.031000] systemd[1]: systemd 236 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid)
[    2.052054] systemd[1]: Detected architecture arm64.

Welcome to Debian GNU/Linux buster/sid!

[    2.069222] systemd[1]: Set hostname to <olimex>.
[    2.274027] BUG: Bad page state in process systemd-cryptse  pfn:7dd29UG: Bad page state in process systemd-cryptse  pfn:7dd29
[    2.280474] page:ffffffbf00f74a40 count:1 mapcount:0 mapping:          (null) index:0x1
[    2.288468] flags: 0x0()
[    2.291003] raw: 0000000000000000 0000000000000000 0000000000000001 00000001ffffffff
[    2.298735] raw: dead000000000100 dead000000000200 0000000000000000 0000000000000000
[    2.306463] page dumped because: nonzero _refcount
[    2.311244] Modules linked in:
[    2.314300] CPU: 0 PID: 119 Comm: systemd-cryptse Not tainted 4.13.13 #13
[    2.321076] Hardware name: Olimex A64-Olinuxino (DT)
[    2.326031] Call trace:
[    2.328485] [<ffffff8008086f68>] dump_backtrace+0x0/0x210
[    2.333879] [<ffffff8008087254>] show_stack+0x14/0x20
[    2.338926] [<ffffff80085c4360>] dump_stack+0x98/0xb8
[    2.343972] [<ffffff800813fc30>] bad_page+0xe0/0x140
[    2.348931] [<ffffff800813fce4>] free_pages_check_bad+0x54/0xb8
[    2.354842] [<ffffff8008140008>] free_pcppages_bulk+0x218/0x2f0
[    2.360754] [<ffffff8008141bf0>] free_hot_cold_page+0x1a8/0x1f0
[    2.366665] [<ffffff8008141f54>] free_hot_cold_page_list+0x34/0x60
[    2.372837] [<ffffff800814939c>] release_pages+0x27c/0x338
[    2.378319] [<ffffff800817ab18>] free_pages_and_swap_cache+0xb0/0xc8
[    2.384666] [<ffffff8008164c00>] tlb_flush_mmu_free+0x40/0x60
[    2.390404] [<ffffff8008165a98>] arch_tlb_finish_mmu+0x48/0x78
[    2.396229] [<ffffff8008165cb4>] tlb_finish_mmu+0x24/0x50
[    2.401622] [<ffffff800816dbf0>] exit_mmap+0xb0/0xf8
[    2.406582] [<ffffff800809f2ec>] mmput+0x44/0xf8
[    2.411194] [<ffffff80080a522c>] do_exit+0x26c/0x990
[    2.416152] [<ffffff80080a59b4>] do_group_exit+0x34/0xa0
[    2.421456] [<ffffff80080a5a30>] __wake_up_parent+0x0/0x28
[    2.426934] [<ffffff8008082ca0>] __sys_trace_return+0x0/0x4
[    2.432496] Disabling lock debugging due to kernel taint

Armbian 5.35 , python 3.5 :
SPII.open("/dev/spidev0.0", mode=0, bits_per_word=8, speed=500000)
AttributeError: module 'pyA20.spi' has no attribute 'open'

GPIO works fine.

I am not able to open any of the schematics with eeschema v4.0.6. I keep getting error about the file not being a vaild eeschema file. How can I open the schematics with kicad?

I recently ordered some linuxino Lime2 boards (with eMMC) which are marked as revision K, but currently no information about the changes in these boards is present in the user manual.

Device: OLIMEX-A20-SOM
Image: Armbian_5.65_Olinuxino-a20_Debian_stretch_next_4.19.9.img
(SD Card)
Boot log:

U-Boot SPL 2018.07-armbian (Dec 14 2018 - 10:13:25 +0200)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
EEPROM: Error
Trying to boot from MMC1


U-Boot 2018.07-armbian (Dec 14 2018 - 10:13:25 +0200) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Unknown
I2C:   ready
DRAM:  1 GiB
NAND:  0 MiB
MMC:   mmc@01c0f000: 0, mmc@01c12000: 1
Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3716 bytes read in 1 ms (3.5 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 1 ms (149.4 KiB/s)
5215328 bytes read in 289 ms (17.2 MiB/s)
7263112 bytes read in 403 ms (17.2 MiB/s)
Found mainline kernel configuration
** File not found /boot/dtb/ **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
** File not found /boot/dtb/overlay/sun7i-a20-fixup.scr **
## Loading init Ramdisk from Legacy Image at 43200000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5215264 Bytes = 5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
Card did not respond to voltage select!
## Error: "bootcmd_nand" not defined
scanning bus for devices...
Found 0 device(s).

Device 0: unknown device

Device 0: unknown device
ethernet@01c50000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@01c50000
=>

This folder has one build file and it is for "jessie":
BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt

The Debian "jessie" release does not work out so well. I think it is time to update this, we can see in the directions it then tries to add a "squeeze" repository to the apt sources saying "if you use debian".

I have been unable to get a proper build with this file using various versions of Debian and using Ubuntu 16.04. So, I recommend to pick one disto and test it well. Use something like Docker and be sure it builds.

To get you started, this is how this might easily be done. I'll set it up as documented with the inconstancy but you may take the opportunity to change to ubuntu and use a better tag for emdebian.org:

./Dockerfile

FROM debian:jessie
RUN echo deb http://www.emdebian.org/debian squeeze main >> /etc/apt/sources.list &&\
    apt-get update &&\
    apt-get install -y ca-certificates wget &&\
    wget https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt
CMD bash

Then build the environment and get everything working:

docker build -t olimex .
mkdir -p ~/opt/a20-olimex

# --rm just removes dockers image of the "run" session (those take a lot of disk space)
docker run --rm -v ~/opt/a20-olimex:/a20-olimex -it olimex

# "run" runs the CMD in the docker file, that is "bash" .. so we get a bash shell in the docker
root@97554b8228ff:/# cd /a20-olimex/
root@97554b8228ff:/a20-olimex# apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git
...
# build everything ..

# save all the hard work and use it to update the Dockerfile above
history -a && cp ~/.bash_history /a20-olimex
exit

I have explored several avenues to try and get everything to build. This is time consuming because the toolchain and code is picky and I'm not familiar with this process. I can respect that you may only want to have 1 build file to maintain, but it really should work especially since there is a product for sale depending on this. Using Docker opens the door to publishing an environments that work well and should cut down on your support issues. If you have any questions about docker I'm happy to help.

Hi,
in which software is sch and pcb drawn?
I need to know exact position of mounting holes relatively to GPIO connectors. Would it be possible to upload pick&place and update Kicad shield template to contain mounting holes position? Thank you.
Best regards, Samuel

Is it possible to get this updated as the number of GPIO's in [gpio_para] is only 64 not 75 so I don't know what to put in script.fex for 65 - 75.

Thanks

Andy.

I have downloaded the brd file for A20 Lime2 "https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/A20-OLinuXino-Lime2_Rev_B.brd" and opened it in Eagle 6.6.0 Pro version.

I haven't changed any settings. Just opened it and ran the DRC. The reported error count does not match the error count embedded on the brd file.

See attached image.

AP1231-2.5V is mentioned but I need to get the datasheet or complete part number

As in the example, if I type:

>>> from pyA10Lime.gpio import gpio
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name gpio

I'm following this guide:

https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt

These packages are not in apt-get in debian stretch (my typical selection) or debian squeeze:
gcc-4.7-arm-linux-gnueabihf ncurses-dev

What distro do you recommend for the build environment? I'm using Docker so it is not a big deal to change it. It is just tricky to find the distro that will both find the old version of gcc (gcc-4.7 gnueabihf) even when I try adding this repository:

deb http://www.emdebian.org/debian squeeze main
in the file below:
/etc/apt/sources.list

Please consider using something like docker, it will help to re-create the environment and builds..

The 4.3 LCD display seems to be a true 24bit screen according to the datasheet (GFT043HA480272Y).

Yet we enable 6 colors per pixel dithering here:
https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103/script_change_display_3.4.103/change_display.sh#L556

Why is that? We should be able to set frm to 0 indicating a 24 bit, rather then an 18 bit display and thus disable color dithering.

Hello!
I am trying to use Ethernet over usb on my olimex a33, but it isn't working.

I am using a official image from this github section.
Version of kernel is 3.4.39.1

Can somebody help me?

I plan to make one pcb prototype based on A20 Micro board. Can i use k4b4g1646g-bck0 instead of k4b1g1646b-bck0,

Do I need to change the fex file for this?

Step 5 says to write Uboot and u-boot-sunxi-with-spl.bin to the SD card. I am however working with the LIME2 (not the LIME) so I did not build u-boot-sunxi-with-spl.bin. This file is build in the 2.4 A20-OLinuXino-LIME board section. I ran the make in 2.1 A20-OLinuXino-LIME2 board instead.

https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt

Should I run the LIME build too?

Latest image torrent

flashed using etcher (so verified write), retried using several microSD cards. Unsure what the issue is.

Previous image torrent (which looks like the image in this git repo) works

https://www.olimex.com/Products/OLinuXino/A64/A64-OLinuXino/open-source-hardware

Using the 1GB a64 board with onboard storage

Does not output anything via USB TTL connected as-per Quick Start Guide

When gigabit ethernet is enabled by default on Debian images from Olimex, Debian images from the official Debian website and Arch Linux, ethernet performance is terrible. Maximum download speed is 15 KB/s and sometimes drops as low as 5 KB/s. Forcing 100 Mb/s ethernet via software (# mii-tool eth0 -F 100baseTx-FD) or connecting the board to a 100 Mb/s switch is a workaround, though I have bought the board specifically for the gigabit capability. The problem is mentioned here: http://forum.armbian.com/index.php/topic/31-problems-with-gigabit/ and here: https://www.olimex.com/forum/index.php?topic=4615.0 . The problem is very easy to reproduce: just hook up the board to a 1000 Gb/s network switch and try to download something from the Internet.

I am adding additional boot parameters to my kernel, I can do this through a script below:

setenv console 'ttyS0,115200'
setenv root '/dev/sda2'
setenv panicarg 'panic=10'
setenv extra 'my_sextra_options=123'
setenv loglevel '8'
setenv setargs 'setenv bootargs console=${console} root=${root} loglevel=${loglevel} ${panicarg} ${extra}'
setenv kernel 'uImage'
setenv boot_mmc 'fatload mmc 0 0x40008000 script.bin; fatload mmc 0 0x40008000 ${kernel}; bootm 0x40008000'
setenv bootcmd 'run setargs boot_mmc'

But its that setenv boot_mmc that I am unsure of, what address should script.bit be loaded to?

Another option is to simpily add the extas to uEnv.txt:

setenv extra 'my_sextra_options=123'

But will uBoot still load the script.bin and keep the extra variables?

Hi,

Can you put official debian image without X. Just the minimal environment: only ssh enabled by default.

Thinking of olinuxino as a server without having to download very large image and remove packages.

Thanks,

The GPIO Cheat Sheet for the A20 LIME2 uses a strange pagelayout where GPIO_3 is split over 2 pages and GPIO_4 is lonley on the 2nd page.

Since we do not have the PDF source files I cannot submit a patch for this ;) But my suggestion is to do a hard enter after GPIO_2 so that GPIO_3 and GPIO_4 are on the 2nd page (like Lime1 GPIO)

Default SPI speed is much too slow !

I've an SPI LCD that was working fine in kernel 4.4.5, and suddenly was way too slow when I've upgraded to 4.5.x or 4.6.x. After some debugging, I've figured out that kernel was now using "transfer-speed" instead of "spi-device-max-speed", the first been set during ioctrl, but ignored/not-used in older kernels.

Here is the commit merge in Mainline 9 months ago :

https://github.com/megous/linux/commit/47284e3e0f3c427c93f8583549b6c938e8a18015

I've finally figured out that guilty code was in pyA20 providing a wrong default ioctrl value for the "transfer-speed" of 100kHz, while we all know that SPI default should be 10MHz :

diff pyA20-0.2.1/pyA20/spi/spi.c~ pyA20-0.2.1/pyA20/spi/spi.c
238c238
<     config.speed = 100000;

---
>     config.speed = 10000000;

Hello,

Is there no USB ESD protection on any of the olinuxino boards? I have looked at a few schematics and I could not find it. Is it usually built into the Allwinner soc?

I'm trying to make some trivial changes to the Eagle files for the iMX233 Mini and I'm admittedly some what of a novice at Eagle, but when I open the files in version 6.2 I get hundreds of errors.

Do I need to downgrade to 4.16? I noticed from http://olimex.wordpress.com/2012/01/11/why-we-will-not-upgrade-to-eagle-6/ that you guys are not upgrading.

Hi, everybody!
I am working on my personal project using allwinner A13 SoC. Thank you very much for your work and for sharing the schematics!
Right now I'm trying to use AXP209 PMIC, and I have a question about its usage:
I have noticed that wherever you use AXP209, you also use other parts, like SY8009AAAC and MP1584EN (or MP1482DS) and others. But in some cases, like in A13-SOM512 version you use only SY8009AAAC without AXP209, and also in A10S-OLinuXino-MICRO use only AXP152 without any additional parts. As I can deduce, one reason for this is that you don't have battary in these cases. My question is: why can't we use AXP209 without additional parts? As much as I can understand from AXP209 datasheet, they are not so necessary.
Thanks in advance!

found this : https://www.olimex.com/forum/index.php?topic=4580.0 , is this fixed?

When the lastest official prebuilded image https://www.olimex.com/wiki/images/4/45/A20_OLinuxino_Micro_debian_Jessie_34_103_2G_eMMC_release_18.torrent is used, no IPv6 support is built in. According which build instructions/sources was this image built?

The custom build described in https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt uses https://www.olimex.com/wiki/images/b/b5/Debian_FS_34_103_Jessy_8.1_A20-olimex_rel_4.torrent as a rootfs. What is the origin of this image and what are the modifications?

Can you put this link to github or any other static server? Google has concurrent user limitation

Better if you put in torrent,

Thanks,

hi,I have 3 questions.

1. what software u used for pcb design (A13-OLinuXino revision C)?
2. how many layers pcb design (A13-OLinuXino revision C)?
3. and,can i design it in two layers (pcb -A13-OLinuXino revision C)?
   Thanks, I'll give you the answer

https://github.com/OLIMEX/OLINUXINO/blob/b757e3c9be92cbd05854d68da52c639057d005ff/SOFTWARE/A64/emmc.sh

olimex@a64:/$ curl -sSL http://bit.ly/2Hbw9zi | sudo bash
Checking permissions...
Checking MMC device...
Checking eMMC device...
Reading partition table..
Erasing eMMC partition table...
Copying bootloader...
Creating partition: 1
Formating partition 1 to vfat...
Copying files...
          8.24M  40%   15.22MB/s    0:00:00 (xfr#7, to-chk=4/11) 
rsync: chown "/emmc/a64" failed: Operation not permitted (1)
         20.35M  99%   16.06MB/s    0:00:01 (xfr#9, to-chk=1/11)
rsync: chown "/emmc/.bootlogo.bak.OaVi1V" failed: Operation not permitted (1)
rsync: chown "/emmc/.bootlogo.bmp.sZrVrZ" failed: Operation not permitted (1)
         20.43M 100%   16.06MB/s    0:00:01 (xfr#10, to-chk=0/11)
rsync: chown "/emmc/.font24.sft.J9j474" failed: Operation not permitted (1)
rsync: chown "/emmc/.font32.sft.ACoFXd" failed: Operation not permitted (1)
rsync: chown "/emmc/.initrd.gz.dqNlOo" failed: Operation not permitted (1)
rsync: chown "/emmc/.uEnv.txt.YF6K8A" failed: Operation not permitted (1)
rsync: chown "/emmc/.uboot.env.drIPzN" failed: Operation not permitted (1)
         20.43M 100%   16.06MB/s    0:00:01 (xfr#10, to-chk=0/11)
rsync: chown "/emmc/a64/.Image.uvTdu3" failed: Operation not permitted (1)
rsync: chown "/emmc/a64/.a64-olinuxino.dtb.vtLr25" failed: Operation not permitted (1)
rsync: chown "/emmc/a64/.a64-olinuxino.dts.UvvJp9" failed: Operation not permitted (1)
         20.43M 100%   16.01MB/s    0:00:01 (xfr#10, to-chk=0/11)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1]
Creating partition: 2
Formating partition 2 to ext4...
Copying files...
          1.92G  99%    7.51MB/s    0:04:03 (xfr#63820, to-chk=0/100669)   
Finished!
olimex@a64:/$

I was looking for the H3-OLinuXino-NANO files, but was unable to find them.
As I understand it was discontinued due to thermal issues, however, I am already using a cooling system so that's not an issue. If they are not in a condition that matches the other designs on here, would it still be possible to obtain the files?
Thanks,
Nathan

I can't build python packages using buildroot. In the building process the following message is received:

>>> python-olimex 0.2.1 Patching
>>> python-olimex 0.2.1 Configuring
>>> python-olimex 0.2.1 Building
(cd /home/crudo/modduo-build/ROOT/build/python-olimex-0.2.1//; PATH="/home/crudo/modduo-build/ROOT/host/bin:/home/crudo/modduo-build/ROOT/host/sbin:/home/crudo/modduo-build/ROOT/host/usr/bin:/home/crudo/modduo-build/ROOT/host/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" PYTHONPATH="/home/crudo/modduo-build/ROOT/target/usr/lib/python3.4/sysconfigdata/:/home/crudo/modduo-build/ROOT/target/usr/lib/python3.4/site-packages/" _python_sysroot=/home/crudo/modduo-build/ROOT/host/usr/arm-buildroot-linux-gnueabihf/sysroot _python_prefix=/usr _python_exec_prefix=/usr  /home/crudo/modduo-build/ROOT/host/usr/bin/python setup.py build  )
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.4
creating build/lib.linux-x86_64-3.4/pyA20
copying pyA20/__init__.py -> build/lib.linux-x86_64-3.4/pyA20
creating build/lib.linux-x86_64-3.4/pyA20/gpio
copying pyA20/gpio/__init__.py -> build/lib.linux-x86_64-3.4/pyA20/gpio
running build_ext
No processor detected
Warning! Detected and target processor mismatch. 
Do you want to continue [Y/n]?

Is it possible to include this flag to get snapd support on Lime2 board?

CONFIG_SQUASHFS_XZ=y

I am using this image for syncloud.org project:
https://www.olimex.com/wiki/A20-OLinuXino-LIME2#Linux_images

If you actually follow these commands on the wiki, they don't work.

# wget https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build/spi-sun7i.c

This is because wget will retrieve the html version of the page, whereas you actually want the raw version, like so:

# wget https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build/spi-sun7i.c

The other changes required are:

# wget https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build/SPI.patch

to

# wget https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build/SPI.patch

and

# wget https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build/a20_olimex_defconfig

to

# wget https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build/a20_olimex_defconfig

Other parts of the build may also be affected, I'm yet to get down to those instructions but the same fix will apply.

Thanks for hosting this project by the way, it's really awesome that this exists!

When i try install kmod-mmc-over-gpio I get this error:

Installing kmod-mmc-over-gpio (3.18.17-4) to root...
Downloading http://downloads.openwrt.org/chaos_calmer/15.05-rc3/ramips/rt305x/packages/base/kmod-mmc-over-gpio_3.18.17-4_ramips_24kec.ipk.
Multiple packages (kmod-lib-crc-itu-t and kmod-lib-crc-itu-t) providing same name marked HOLD or PREFER. Using latest.
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-mmc-over-gpio:
 *  kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) *     kernel (= 3.18.17-1-73d2b013e81727fe0664fd1b78bd291e) * 
 * opkg_install_cmd: Cannot install package kmod-mmc-over-gpio.

Any idea what is wrong?

I believe somebody lost it there, 640 Mbs of dead weight. Link: https://www.olimex.com/wiki/images/2/29/Debian_FS_34_90_camera_A20-olimex.torrent

root@a20-olimex:~# du -sh *
24K     change_display_olimex_A20.sh
4.0K    Desktop
634M    FFmpeg
4.0K    minicom.log

Hello, is there a possibility of have never kernel on A20 devices (A20-SOM), or best, the main-line?

Thank you

when the board is powered on it displays this message on the debug uart continuously!

U-Boot SPL 2014.04-10706-g36080eb (Aug 19 2014 - 16:42:16)
Board: A20-OLinuXino_MICRO
DRAM:Timeout initialising DRAM

Please help how can I debug this

https://www.olimex.com/wiki/RT5350F-OLinuXino says release 3 was made in April. Where is it available?

Currently, Lime2 shield is missing the mounting hole locations on the shield. It would be nice to have the centers marked on the shield.

Also, it would be nice if the Eagle board/schematic files could be re-saved to newer XML-based format that KiCAD can import.

It would have saved me quite a bit of time to have usbnet drivers enabled in the olinuxino a13 debian micro sd card that I bought. Just a few bits more, and a lot of convenience.

Can you do that for future shipments?

I am unable to load the brd file for H3-OLinuXino in any program that I can find. Is it possible that the format is old?
The error message that comes up in kicad is XML parsing error: 'not well formed (Invalid token)' at line one.
The easyeda error message is something about an invalid utf character at line 1.
openboardview.org has same issue.

Any help appreciated.

Hi,

when I build u-boot for A20 OLinuXino Micro from the mainline u-boot repo I get a warning as shown below

# make A20-OLinuXino_MICRO_defconfig
# make
...
  LD      spl/fs/built-in.o
  LDS     spl/u-boot-spl.lds
  LD      spl/u-boot-spl
  OBJCOPY spl/u-boot-spl-nodtb.bin
  COPY    spl/u-boot-spl.bin
  MKSUNXI spl/sunxi-spl.bin
  MKIMAGE u-boot.img
  COPY    u-boot.dtb
  MKIMAGE u-boot-dtb.img
  BINMAN  u-boot-sunxi-with-spl.bin
===================== WARNING ======================
This board does not use CONFIG_DM_VIDEO Please update
the board to use CONFIG_DM_VIDEO before the v2019.07 release.
Failure to update by the deadline may result in board removal.
See doc/driver-model/MIGRATION.txt for more info.
====================================================

If this warning does not apply to you, please close this ticket.

hello.
i use altium designer for pcb design and i can't open .brd in this software.
how can i convert .brd format to .pcb without problem? Or how can i open it with altium designer or allegro software?

also i have two problems else:
1)which version A13-OLinuXino of your design is the latest one?
2)what is the difference between A13-OLinuXino versions?
sorry for my bad english and thank you for your answers in advance.

Hi there,

the A20-OLinuXino-Lime2-Rev_*.pdf files list pins F19 and E18 as VCC_CSI0 and VCC_CSI1, respectively. This is a bit misleading as these are the generic power inputs for ports E & G (VCC-PE and VCC-PG) Someone may wrongly disable them if they don't use a CSI, which will disable the ports.

This was discovered by Iain Paton on the linux-sunxi mailing list:

On the lime2 schematic we see the pins labeled as follows:

F19 : VCC_CSI0
E18 : VCC_CSI1

However the A20 datasheet doesn't label them this way, instead using:

F19 : VCC-PE : Port E Power Supply
E18 : VCC-PG : Port G Power Supply

no mention at all of CSI. CSI just happens to be a function that can be
multiplexed onto ports E & G.

So lets assume for a moment we don't have a CSI device, or a CSI driver
and are not using those pins for CSI functions but are instead using
their default GPIO purpose, or in the case of PG perhaps for UART3
or UART4.

What happens when you disable the regulator? Hopefully from the above
you'll already have worked out that you lose ports E & G when you turn
their I/O power supply off and anything multiplexed onto those ports
becomes unuseable.

I haven't checked other schematics, but all of the Olimex A10/A20
boards along with Cubieboard & CubieTruck label these pins as VCC_CSIn
It would be my guess that there's a reference design being given to
manufacturers, perhaps the original Cubieboard even, that makes this
mistake and everyone else has blindly copied it.

Full message and thread context: https://www.mail-archive.com/[email protected]/msg17042.html