Olimex Port Devices Driver

Posted By admin On 12/10/21
Olimex Teres-A64
ManufacturerOlimex
Release Date2017-10
WebsiteOlimex
Specifications
SoCA64 @ 1.2Ghz
DRAM2GiB DDR3L @ 672 MHz
NAND16GB eMMC
PowerDC 5V @ 3A, 9500mAh 3.7V Li-Ion battery
Features
LCD157.5x168 (11')
VideoHDMI (mini)
Audio3.5mm headphone plug HDMI, internal stereo speakers, internal microphone
NetworkWiFi 802.11 b/g/n ([RTL8723BS])
StorageµSD, NAND
USB2 USB2.0 Host, X USB2.0 OTG
CameraVGA (640x480) front

This page needs to be properly filled according to the New Device Howto and the New Device Page guide.

Do it yourself laptop, hacker friendly.

By OLIMEX Ltd in Learning, linux, olinuxino, open source, OSHW Tags: device, GSM, linux, usb, wifi Sometimes devices connected to USB ports need to be re-set. It’s not unusual GSM modems and WiFi dongles to freeze and the only way to bring them back to life is to remove and re-attach. Please note that the examples above are intended for ARM CrossConnects, which have a USB vendor ID of 0x131B and a USB product ID of 0x0003 and 0x0004. If you are using a different device you will need to modify the files so they contain the correct USB vendor and product IDs for your device.

  • 2Sunxi support
    • 2.2Manual build
      • 2.2.1U-Boot
      • 2.2.2Linux Kernel
  • 3Tips, Tricks, Caveats
  • 7See also

The PCB has the following silkscreened on it:

Along with the availability in the olimex web shop mid-2017, PCB1 Rev.C was released.

Current status

Olimex Port Devices Driver

Give a brief overview of the current status of support under sunxi here.

Generally works with mainline kernel since release 4.19and mainline u-boot since [504bf79] targeted release 2019.07.

Debian buster image (including linux 4.19, and u-boot 2019.04 with above patch backported) is at http://box.redpill.dk/

Manual build

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

U-Boot

Sunxi/Legacy U-Boot

Use the MANUFACTURER_DEVICE build target.

Mainline U-Boot

The board is [expected to be] fully supported since v2019.07.Use the teres_i_defconfig target to build a U-Boot image.You need an ARM Trusted Firmware build (bl31.bin), which will be included in the FIT image.

Booting from MicroSD card or USB works, as does use of an externally plugged in USB keyboard.Builtin USB keyboard fails to register with U-boot - possibly due to special quirks needed. [See also this bug in debian BTS]

Linux Kernel

Sunxi/Legacy Kernel

Use the MANUFACTURER_DEVICE.fex file.

Olimex Port Devices Driver Updater

Mainline kernel

DriverOlimex Port Devices driver

Olimex Port Devices Driver

Use the FAMILY-CHIP-DEVICE.dtb device-tree binary. (no 'final' device tree yet)

Olimex Port Devices Drivers

Linux-4.19 has most of the relevant drivers included. If U-Boot has provided an appropriate frame buffer it can be re-used for a display;otherwise screen still stays dark. Drivers for the eDP bridge anx6345 mainly responsible for this are being discussed [[1]].Audio drivers are to appear in 4.20.

Add MANUFACTURER DEVICE specific tips, tricks, Caveats and nice to have changes here.

FEL mode

The main PCB has a solder jumper labeled 'UBOOT1', next to the internal expansion connector 'CON3'.A drop of solder will pull A64's ball F17 low and should activate FEL mode. The correspondingUSB OTG however is only available on the internal extension connectors, so an appropriate breakout PCBseems to be the bigger task.

Olimex Port Devices Driver Vga

Device specific topic

If there are no further device specific topics to add, remove these sections.

...

DEVICE UART pads

PCB1 has solder pads for a 3-pin header. A horizontal pin header would however bump into the battery, once assembled.

On Revision C boards, a serial port is provided through the audio jack. It can be enabled via an analog switch controlled bybit 9 on Port L, which has to be pulled low. Otherwise it will be a plain audio jack, as on Rev.B boards.You can find more information on [Olimex github repo].Olimex sell a specific cable: [Teres usb debug].The Pinebook debug cable also works.

If you decide to build your adapter cable, connect the tx to the tip of the jack, rx to central ring, and ground to the sleeve. They must be 3.3V compatible.The board's RX is protected with a diode ('D4'), so 5V should work as well. Never connect to a rs232 serial port directly.Usually usb serial adapters with 1/10' pin headers are 5v or 3.3v level compatible, but if in doubt, double check it.

Take some pictures of your device, upload them, and add them here. DO NOT UPLOAD PICTURES WHICH YOU PLUCKED OFF THE INTERNET.

List rebadged devices here.

Manufacturer images

Olimex Port Devices Driver

The Olimex image of Ubuntu Mate can be downloaded, using torrent. It uses allwinner provided linux kernel 3.10 and u-boot.

[[2]]

Retrieved from 'http://linux-sunxi.org/index.php?title=Olimex_Teres-A64&oldid=22992'

This tutorial shows how to use the inexpensive Olimex ARM-USB-OCD-H adapter to debug ESP8266 firmware using VisualGDB and Visual Studio. Before you begin, install VisualGDB 5.0 or later.

Olimex Port Devices Driver Device

Update: our latest ESP8266 toolchain includes an improved OpenOCD port for ESP8266 that is more stable than the xt-ocd tool described here. Please follow this tutorial for detailed instructions on using it.

  1. Setup your JTAG connection as described in the basic ESP8266 tutorial, however leave the reset pin unconnected:If you connect the reset pin, the ESP8266 GDB stub will not be able to recognize the core correctly and the debugging won’t work. In order to work around this bug, the reset should be left unconnected and the device should be reset manually (e.g. by plugging it out and back in) before each debugging session.
  2. Start Visual Studio and launch the VisualGDB Embedded Project Wizard:
  3. Uncheck the “bin” checkbox to avoid generating an extra .bin file (ESP8266 debugging plugin will generate a set of .bin files automatically):
  4. Select the ESP8266 toolchain and the device from the list:
  5. In order to keep things simple while testing the JTAG functionality we will use the basic LEDBlink sample that does not involve any WiFi functionality:
  6. On the last page of the wizard select the FT2232-based interface and pick the olimex-tiny-h layout:
  7. The Xtensa OCD Daemon does not support the ARM-USB-OCD-H programmer, however it supports a similar olimex-tiny-h programmer, that has identical hardware, but a different ID. We will now show how to change the ID of the ARM-USB-OCD-H programmer to make it compatible with the Xtensa OCD Daemon. Download and launch USBDriverTool, connect your Olimex programmer and install the FTDI CDM driver for both interfaces:
  8. Ensure that the driver is installed successfully for both interface 00 and 01:
  9. Download, install and launch FT_Prog. Then select “Scan and Parse” to populate the device list:
  10. We will now use FT_Prog to change the product ID of the Olimex USB-OCD-H device. Ensure that the vendor ID is set to 15BA and set the product ID to 002A:
  11. Click the “Program Devices” button:
  12. Finally press the “Program” button to apply the changes:
  13. Once the programming is complete, reconnect the device. As the ID has been changed, the drivers won’t be installed anymore:
  14. Install the FTDI CDM driver for both interfaces and use the FT_Prog tool to find the serial number of the device:
  15. Go back to VisualGDB Embedded Project Wizard and enter the serial number observed in FT_Prog. Also lower the speed to 3MHz:
  16. Press “Finish” to generate the project. Build it with Ctrl-Shift-B:
  17. Now you can start debugging by pressing F5. Observe how VisualGDB programs the SPI FLASH:
  18. Now you can try setting breakpoints in your code. If the debugging does not work, observe the xt-ocd output for information about the encountered problems. Note that the “Error opening probe … trying with ‘A’ suffix” message is normal:
  19. If you have connected the serial port on the ESP8266 device to the serial port of the Olimex ARM-USB-OCD-H like described in this tutorial, you need to install the USB serial port driver in order to view the output from the COM port. Locate the serial port in Device Manager:
  20. Check device properties to find the serial port corresponding to interface 01 (it will have &MI_01 at the end of the last hardware ID):
  21. Start updating the drivers for that COM port and select “Let me pick a list of device drivers”:
  22. Click “Have disk” and specify the FTDI CDM driver directory under the directory where you have extracted USBDriverTool:
  23. Select the USB Serial Port driver from the list:
  24. Finally go to VisualGDB Project Properties and enable the Raw Terminal on the newly installed COM port. Ensure you specify the correct baud rate:
  25. Once the Raw Terminal is enabled, you will see the output from the COM port inside Visual Studio once you start debugging. See this tutorial for an example of reading the output from the COM port.