Olimex A20-OLinuXino-Lime2

The A20 Olinuxino LIME2 is an OSHW board produced by Olimex.

The A20-OLinuXino-LIME2 is an upgrade of the Olimex A20-OLinuXino-Lime, but it comes with 1GiB RAM and gigabit ethernet. There are also two extra variants with onboard storage: A20-OLinuXIno-LIME2-4GB with 4GB NAND and A20-OLinuXino-LIME2-eMMC with 4GB eMMC.

= Identification =

The board is marked as A20-OLinuXino-Lime on both the top and bottom of the PCB.

Note that it is not marked as Lime2. The Lime2 variant can be distinguished by the presence of two dram chips on the top of the board between the SoC and the USB connectors, also the ethernet phy is on the bottom of the board instead of the top.

= Sunxi support =

Current status
Supported.
 * Mainline kernel patches posted to linux-arm-kernel mailing list 2014-09-28
 * Mainline u-boot patches posted to u-boot mailing list 2014-09-28

Manual build
You can build things for yourself by following our Manual build howto and by choosing from the configurations available below.

Sunxi/Legacy U-Boot
Use the A20-OLinuXino_Lime2 build target. _FEL version is also available for USB booting.

Mainline U-Boot
Use the A20-OLinuXino-Lime2_defconfig build target or A20-OLinuXino-Lime2-eMMC_defconfig if you have the eMMC version.

Sunxi/Legacy Kernel
Use the a20-olinuxino_lime2.fex file. (Please note that this fex file adopted DRAM clock setting from the Lime2's predecessor - only dram_tpr4 differs for unknown reasons. Using this fex file the DRAM is clocked with just 384 MHz, which costs some few percent performance depending on the application used.)

Mainline kernel
Use the sun7i-a20-olinuxino-lime2.dtb device-tree binary.

= Tips, Tricks, Caveats =

FEL mode
The Recovery button (under sata connector, nearest hdmi connector) triggers FEL mode.



GMAC quirks
Different ethernet PHY is used depending on board revision Each of those designs have quirks at gigabit speeds, with slightly different symptoms:
 * Rev. A-E with Realtek RTL8211CL PHY looses packets receiving at gigabit speed in slave mode
 * Rev. F-G2 with Realtek RTL8211E PHY looses packets transmitting at gigabit speed
 * Rev. H-L with Micrel KSZ9031 PHY looses packets transmitting at gigabit speed

Possible causes
A possible cause for packet loss only at gigabit speed is wrongly calibrated trace length compensation a.k.a. RGMII timing a.k.a. TX/RX skew: the sum of a) physical wiring length between MAC and PHY, b) compensations in MAC, and c) compensations in PHY, must result in a 1.5-2 ns delay from TX source clock in MAC and RX source clock in PHY.

A possible cause for packet loss only in master or slave mode is failure to seed or align with RGMII source-synchronous clock (this is newest suspected cause for rev. A-E boards but an older guess of the cause being clock calibration seems not ruled out).

A possible cause for packet loss only for Micrel PHY is a bug fixed since mainline linux v5.1 and unfixed in mainline u-boot (as of v2020.07).

slowdown
A simple general workaround is to avoid speeds showing package loss, either by advertising only lower speeds, or by turning off auto-negotiation and setting one specific lower speed, or doing similar advertising/fixation at the peer host. Mainline u-boot supports environment variable for Micrel 9031 PHY since v2017.09; i.e. setting  in u-boot environment should work for rev. H-L boards. Linux supports changing speed and auto-negotiation with ethtool or systemd (see option advertise in either  or  ). Beware: You may need additional changes with older linux or u-boot.

master mode
A workaround for rev. A-E boards is to force the device into master mode, either by fixating device to only offer master mode or by fixating peer device to only offer slave mode. Beware: This workaround has the adverse effect of complete network failure at any speed with a peer device in master mode! Mainline linux supports forcing master or slave mode since v5.7 which should be possible to control from ethtool v5.8 or newer. Mainline u-boot supports option for any Realtek RTL8211x PHY since v2016.05, and limited to Realtek RTL8211B/C PHYs since v2017.01 (i.e. it is ignored on newer revisions of LIME2); it is enabled by default for defconfig (since v2016.05 intermittently and) since v2020.04; it is not enabled for defconfig  (available since v2017.09). Beware: You may need additional changes with older linux or u-boot.

calibrate at MAC
A workaround for rev. F and newer (and maybe rev. A-E as well?) is to apply trace length compensation at the MAC. Mainline u-boot supports compensating at MAC since v2015.04 using option. Olimex fork of u-boot hardcodes the equivalent of  for rev. F-G2 boards, and the equivalent of  for rev. H-L boards. Some have alternatively had success with rev. K and u-boot option , also noting that the Micrel PHY gets significantly hotter than the older Realtek RTL8211CL/RTL8211E PHYs. Beware: A bugfix optimal for one board revision may adversely affect other board revisions! Beware: You may need additional changes with older linux or u-boot.

calibrate at PHY
A workaround (or proper fix?) for rev. F and newer (and maybe rev. A-E as well?) is to apply trace length compensation at the PHY.

Mainline linux always compensates at PHY for rev. F-G2 boards since v5.9 (and backported to v5.8.15) Mainline linux (and mainline u-boot?) supports compensating at PHY for rev. H-L boards when ethernet PHY is declared to as RGMII-ID (not RGMII) in device-tree (see fix for such issue with another PHY). Beware: Documentation for Micrel KSZ9031 PHY compensations where updated since v5.12.

Further testing
Current approach in mainline u-boot of unconditionally compensating at MAC require different values for rev. F-G2 as for rev. H-K.

Idea 1: Have u-boot probe and apply compensations conditional to i2c eeprom information about board revision (i.e. borrow from the implementation in Olimex fork of u-boot).

Idea 2: Change device-tree to use PHY-mode RGMII-ID (not RGMII) and rely on driver-specific default compensations - or adapt each driver if needed.

TODO:
 * test rev. A-E board with u-boot option  at various values and without
 * test rev. F-G2 board with u-boot option
 * test rev. F-G2 board with u-boot option  at various values (including 2 or 3 which some find optimal)
 * test rev. H-L board with u-boot option  and u-boot command
 * test rev. H-L board with u-boot options  and   with the latter at various values (including 3 or 4 which some find optimal)
 * test with u-boot and Linux device-tree option
 * inspect with ethtool 5.8 or newer if ethernet is in master or slave mode when conducting other tests, and try force the opposite mode to check if a calibration setup behaves same in both modes.

GMAC-related software bugs
Rev. A-E would fail to work in master mode, because workaround for a GMAC quirk was accidentally disabled since v2017.03). Fixed since mainline u-boot v2020.04.

Rev. H-L would fail to work or lose packets at 100 megabit or gigabit speeds, because Micrel PHY driver was not loaded by default. Fixed since mainline linux v5.5 and mainline u-boot v2021.01.

Expansion ports
The internal GPIO headers appear to be mirrored compared to the original Lime boards. Due to this there are specific A20-OLinuXino-Lime2-UEXT adapters, however as of 2014-09-28 these do not appear to be available directly from the Olimex shop.

Booting from SPI Flash
See the main Bootable_SPI_flash article for generic guides on how to boot from SPI flash. With SPI flash it is possible to use SATA or network boot without any need to use an SD card for storing the U-Boot bootloader.

Since rev. K all Lime2 boards are equipped with SPI NOR flash.

In case you have older revision, it is possible to add it yourself, as this requires soldering wires to 3 pads on the empty NAND socket in order to get access to the PC0,PC1,PC2 pins.

Using LiPo battery
Warning! Battery connector, JST, is exactly the same as SATA power connector!

PMIC AXP209 can charge LiPo battery and it has DC-DC bust-up converter to power the board from battery.

LED "CHGLED" (near battery connector): yellow — battery is charging.

If you connect the battery when the board is powered off, it will not power on automatically.

SATA power connector
Unlike other sunxi boards the Olimex boards don't use the JST XH 0.1"/2.5mm header for SATA power but the smaller JST PHR-2 header normally used for connecting LiPo batteries.

Hardware reliability
There are known cases where Lime2 boards are failing in the wild. The main suspects are DRAM clock speed and CPU core voltage. For more information see [Hardware Reliability Tests].

DRAM clock speed limit
DRAM is clocked at 480 MHz by the hardware vendor (in fact even 532Mhz is mentioned in the blog). The board uses somewhat non-standard resistors for ZQ calibration (ZQ = 330 Ohm, SZQ = 330 Ohm), but at least they seem to be the same in Lime2 revisions from Rev.B to Rev.E according to the board schematics. Still it's best to always mention the board revision in the results table in order to avoid any surprises.

DRAM test results
Having done runs on a larger set of boards, initial test results looked appalling. Machines that where known to have caused trouble in the past, failed within the hour. Others kept going for a few hours actually. We did notice temperature variation influences. On a Monday, the heating in the building was broken and the ambient temperature was only 20 degrees Celsius and 3 boards ran overnight without a problem. On Wednesday the heating was fixed and the ambient temperature rose to 23 degrees Celsius and all three boards had crashed. All of the initial 6 test subjects crashed and failed at their stock 480 DRAM frequency setting!

Expanding this test to influence ambient temperature, even more interesting results where found. For example, 456 Mhz seemed stable at 22 degrees Celsius, but with an ambient temperature of 50 degrees Celsius a few boards still crashed. Lowering the frequency even more, to 432 MHz stabilized that and thus the ambient temperature was increased to 70 degrees Celsius. Here the sunxi_tp_temp, which is very unreliable, reported core temperatures of about 77 degrees Celsius. The board however remained running stable at least one hour.

Lima-memtester was used for testing. The full tests results can be seen in this sheet, and can eventually be modified into table below.

= Adding a serial port =



There is a clearly marked UART0 connector on the edge of the board beside the ethernet connector. All you have to do is attach some leads according to our UART howto.

= Pictures =

= See also =


 * Olimex A10-OLinuXino-Lime
 * Olimex A20-OLinuXino-Lime
 * Lime2 schematics & CAD files

Manufacturer images
Olimex images for Lime2