Archive

Posts Tagged ‘olimex’

Linux 4.14 Release – Main Changes, ARM & MIPS Architecture

November 13th, 2017 7 comments

Linus Torvalds has announced the release of Linux 4.14:

No surprises this week, although it is probably worth pointing out how the 0day robot has been getting even better (it was very useful before, but Fengguang has been working on making it even better, and reporting the problems it has found).

Sure, some of the new reports turned out to be just 0day doing things that just don’t work (ie KASAN with old gcc versions, but also doing things like loading old ISA drivers in situations that just don’t make sense – remember when you couldn’t even ask if the hardware existed or not, and just had to know), but even then it’s been all good.

The appended shortlog is obviously only for the (small) haul since rc8, and it really is tiny. Not very many commits, and they are small. The biggest thing that stands out in the diffstat is the “leaking_addresses” perl script, which is actually under active development, but I put the first version in for 4.14 just so that people could see that initial state and start looking at the end result and perhaps ask themselves “should my code make these kernel addresses visible to user space”.

The actual changes will hopefully start percolating into 4.15, with one notable likely early change (which has been discussed extensively on the list) being to just hash any “%p” addresses by default. We used to have strict modes that just zeroed the address out, but that was actually counter-productive, in that often people use the address as a “kernel object identity” for debugging (or for cross-correlation -think network sockets), and so just clearing the pointer value makes those kinds of uses pointless. But using a secure hash allows for those kinds of identity uses, while not actually leaking the address itself.

(Other situations where the actual address is relevant then need other approaches – we’ll be restricting /proc/kallsyms only to entities that actually need them etc etc).

Anyway, apart from that one script, the rest of it really is one-liners or “few-liners”.

The most noticeable last-minute change is probably that we had to revert the code that showed a good MHz value in /proc/cpuinfo even for the modern “CPU picks frequency dynamically” case. It worked fine, but it was much too expensive on machines with tens or hundreds of CPU cores. There’s a cunning plan, but it didn’t make 4.14, so we’ll get it working and then back-port.

Anything else is pretty esoteric, you can just read the changelog..

And with this, the merge window for 4.15 is obviously open. As mentioned in the late rc announcements, the extra week for rc8 means that now Thanksgiving week ends up happening during the second half of the merge window, and I’ll be off on a family vacation.

We’ll see how that goes.

I might decide that I’ll extend the merge window if I feel that I can’t be responsive enough.

Or maybe you guys won’t even notice, because I _will_ have my laptop and Internet access.

Or maybe I will just decide that 4.14 was a painful release, and any late stragglers for 4.15 are not worth _another_ painful release, and I’ll just say “tough luck, you were late to the merge window, and I felt more like being out in the sun than taking your second-week pull request”.

Because it really would be lovely to have a smaller and calmer release for 4.15.

Anyway, go out and test the new 4.14 release, that is slated to be the next LTS kernel – and start sending me pull request for the 4.15 merge window.

Linux 4.13 brought us new features such as support for non-blocking buffered I/O operations at the block level, AppArmor security module’s “domain labeling” code, kernel-based TLS implementation for better performance, and CIFS/SAMBA default change to v3.0 for better security, among many other changes.

Some newsworthy changes in Linux 4.14 include:

  • Bigger memory limits – x86-64 used to be limited by 4-level paging to 256 TiB of virtual address space and 64 TiB of physical address space. Some vendors already reached the limit with servers equipped with 64 TiB of memory, so support for 5-level paging has been introduced, increasing the limits to 128 PiB of virtual address space and 4 PiB of physical address space.
  • Added AMD Secure Memory Encryption – Secure Memory Encryption can be used to protect the contents of DRAM from physical attacks on the system. Read LWN article or AMD whitepaper for details.
  • Better kernel traces with the ORC unwinder – An “unwinder” is what prints the list of functions (aka. stack trace, callgraph, call stack…) that have been executed before reaching a determinate point of the code. The new unwinder is called ORC (Oops Rewind Capability), works more reliably than the current unwinder, and does not require adding code anywhere, hence having not effect on text size or runtime performance
  • Compression in Btrfs and Squashfszstd compresses at speeds close to lz4 at compression ratio comparable to lzma. Support for zstd compression had been added to both Btrfs and Squash. See benchmarks in commit messages for Btrsfs and Squashfs.
  • Zero-copy from user memory to sockets – The MSG_ZEROCOPY socket flag enables zero copy mechanism to common socket send calls. It is generally only effective at writes over around 10 KB. Checkout the documentation for more details.

Linux 4.14 will be a long term support kernel with 6-years of support, so it will be found in devices for the years to come. [Update: While Linux 4.4 will be supported for 6 years until February 2022, the plan is to support Linux 4.14 until January 2020, right from the horse’s mouth]

The ARM architecture has gone through many changes as per usual. Here’s a non-exhaustive list of changes:

  • Allwinner:
    • Allwinner A10s – HDMI DDC I2C Adapter,HDMI CEC support
    • Allwinner A10/A20 – CCU Clock-ng support
    • Allwinner A64 – SRAM controller driver
    • Allwinner A83T –  SD/MMC support, AXP813 PMIC,USB support
    • Allwinner H3 – I2S support
    • Allwinner R40 –  CCU sunxi-ng style clock driver support,pinctrl support
  • Rockchip
    • Clock driver – Fixes for RK3128, added RK3126 support within RK3128 driver
    • Pinctrl – Rockchip RK3128 subdriver
    • Power domains for Rockchip RK3366
    • New power key driver for Rockchip RK805 PMIC
    • PCI driver – Added Rockchip per-lane PHY support for better power management
    • SPI driver – Explicit support for Rockchip RV1108
    • DRM driver – Added dw_hdmi support for RK3399
    • Added ROCK64 board, RK3399 Sapphire module on Excavator carrier-board, and Theobroma Systems RK3399-Q7 SoM
    • Device tree changes:
      • pinctrl typos
      • keep-power-in-suspend in non-sdio nodes
      • removal of the deprecated num-slots property from dwmmc nodes.
      • RK3328 – support for spdif, io-domains and usb (including enablement of usb on the evaluation board)
      • RK3368 – support for spdif.
      • RK3399 – pcie changes, support for the mali gpu, a new power-domain, sdmmc support on the firefly board and dynamic-power-coefficients.
      • Removal of the deprectated num-slots property from all Rockchip dw-mmc nodes
      • RV1108 – support for sd-cards on the evaluation board
      • RK3288 – EVB gains support saradc and the adc-key, mali gpu enabled in some boards (fennec, evb, tinker).
      • RK3228/RK3229 – Support for efuse, sdmmc, sdio, io-domans and spdif; separate rk3229.dtsi;  The evaluation board also gets regulators, io-domains, emmc, tsadc keys
  • Amlogic
    • Clock driver – Added gxbb CEC32 and sd_emmc clocks, meson8b reset controller
    • SoC info driver – “Amlogic SoCs have a SoC information register for SoC type, package type and revision information. This patchs adds support for this register decoding and exposing with the SoC bus infrastructure”
    • Added Amlogic Meson AO CEC Controller driver
    • Device tree changes:
      • Updates for new MMC driver features/fixes, support for high-speed modes
      • Clock updates
      • Add GPIO line names to a few boards
      • Update clock controler for use as reset controller
  • Samsung
    • Clock driver – suspend fix for Samsung Exynos SoCs where we need to keep clks on across suspend
    • Samsung Exynos5420/5422/5800 audio fixes
    • S3C24xx platform – Cleanup from non-existent CONFIG entries, fix unmet NET dependency when H1940 bluetooth chip is selected
    • Pinctrl driver – Fix NULL pointer dereference on S3C24XX, fix invalid register offset used for external interrupts on Exynos5433, consolidate between drivers and bindings the defines for pin mux functions, minor code improvements
    • Samsung DTS ARM64 changes
      • Remove deprecated and unneeded properties from Exynos boards.
      • Implement proper (working) support for USB On-The-Go on Exynos5433 TM2/TM2E boards.
    • Samsung defconfig changes
      • Enable some drivers useful on our boards (communication: Bluetooth, WiFi, NFC, USB; codepages and crypto algorithms).
      • Enable debugging and lock testing options.
  • Qualcomm
    • IPQ8074 – Added SoC & HK01 board support, PCI driver
    • APQ8016 – Force USB host mode; jack detection support in ASoC
    • MSM8916 – Updated coresight nodes, added GPU, IOMMU, Venus video codec, and CEC clock nodes
    • MSM8996 – Add  support for USB, PCIE phy, RPM/GLink, and modem SMP2P; SMMU clks
    • Pinctrl driver – Qualcomm APQ8064 can handle general purpose clock muxing
    • NAND driver – Various fixes
    • Qualcomm GLINK SMEM driver – Fix memory leak, and unlock  on error
    • V4l – Update the Qualcomm Camera Subsystem driver document with a media controller pipeline graph diagram, VFE scale and crop modules support, and PIX interface and format conversion support.
    • Added DB820c PM8994 regulator node
    • Add PMI8994 gpios
    • Device tree changes:
      • Fixup XO, timer nodes, and pinctrl on IPQ4019
      • Add IPQ4019 RNG and wifi blocks
      • Update MSM8974 coresight node
      • Add IPQ8074 bindings
  • Mediatek
    • Pinctrl driver – Mediatek MT7623 PCIe mux data fixed up.
    • PCI Driver – Added MediaTek MT2712 and MT7622 support
    • Thermal driver – Added Mediatek thermal driver for mt2712
    • Added support for MediaTek MT2712 SoC and avaluation board
    • New board – Mediatek mt7623-based Banana Pi R2
  • Other new ARM hardware platforms and SoCs:
    • Broadcom – Stingray communication processor, Raspberry Pi Zero W
    • Marvell – ARMADA 8080 SoC
    • Microchip/Atmel – SAMA5D28 SoM1 EK
    • NXP – Toradex Apalis module + Apalis and Ixora carrier boards, Engicam GEAM6UL Starter Kit, Beckhoff CX9020 Embedded PC (i.MX53)
    • Renesas – R-Car D3 board (R8A77995)
    • Storlink/Cortina –
    • Texas Instruments – TI DT76x, TI AM335x Moxa UC-8100-ME-T open platform, TI AM57xx Beaglebone X15 Rev C
    • Uniphier – PXs3 STB SoC and development board
    • ZTE – ZX296718 PCBOX Board

MIPS had a huge changelog this time, summarized below:

  • CM – Rename mips_cm_base to mips_gcr_base; Specify register size when generating accessors; Use BIT/GENMASK for register fields, order & drop shifts; Add cluster & block args to mips_cm_lock_other()
  • CPC – Use common CPS accessor generation macros; Use BIT/GENMASK for register fields, order & drop shifts; Introduce register modify (set/clear/change) ; Use change_*, set_* & clear_* where appropriate, etc…
  • CPS – Read GIC_VL_IDENT directly, not via irqchip driver
  • DMA – Consolidate coherent and non-coherent dma_alloc code, Don’t use dma_cache_sync to implement fd_cacheflush
  • FPU emulation / FP assist code – Corner cases fixes such as NaN propagation and other special input values; Zero bits 32-63 of the result for a CLASS.D instruction; enhanced statics via debugfs; do not use bools for arithmetic. GCC 7.1 moans about this; correct user fault_addr type
  • Generic MIPS
    • Enhancement of stack backtraces
    • Cleanup from non-existing options
    • Handle non word sized instructions when examining frame
    • Fix detection and decoding of ADDIUSP instruction
    • Fix decoding of SWSP16 instruction
    • Refactor handling of stack pointer in get_frame_info
    • Remove unreachable code from force_fcr31_sig()
    • Many more fixes and cleanups
  • GIC – Introduce asm/mips-gic.h with accessor functions; Use new GIC accessor functions in mips-gic-timer; Remove counter access functions from irq-mips-gic.c; Remove gic_read_local_vp_id() from irq-mips-gic.c, etc…
  • microMIPS – Fix microMIPS stack unwinding on big endian systems
  • MIPS-GIC – SYNC after enabling GIC region
  • NUMA – Remove the unused parent_node() macro
  • R6 – Constify r2_decoder_tables; add accessor & bit definitions for GlobalNumber
  • SMP – Constify smp ops, allow boot_secondary SMP op to return errors
  • VDSO – Drop gic_get_usm_range() usage, avoid use of linux/irqchip/mips-gic.h
  • Platform changes
    • Alchemy – Add devboard machine type to cpuinfo, update cpu feature overrides,threaded carddetect irqs for devboards
    • AR7 – allow NULL clock for clk_get_rate
    • BCM63xx – Fix ENETDMA_6345_MAXBURST_REG offset, allow NULL clock for clk_get_rate
    • CI20 – Enable GPIO and RTC drivers in defconfig; add ethernet and fixed-regulator nodes to DTS
    • Generic platform
      • Move Boston and NI 169445 FIT image source to their own files
      • Include asm/bootinfo.h for plat_fdt_relocated()
      • Include asm/time.h for get_c0_*_int()
      • Include asm/bootinfo.h for plat_fdt_relocated()
      • Include asm/time.h for get_c0_*_int()
      • Allow filtering enabled boards by requirements
      • Don’t explicitly disable CONFIG_USB_SUPPORT
      • Bump default NR_CPUS to 16
    • JZ4700 – Probe the jz4740-rtc driver from devicetree
    • Lantiq – Drop check of boot select from the spi-falcon and lantiq-flash MTD drivers, access boot cause register in the watchdog driver through regmap, add device tree binding documentation for the watchdog driver, add docs for the RCU DT bindings, etc…
    • Loongson 2F – Allow NULL clock for clk_get_rate
    • Malta – Use new GIC accessor functions
    • NI 169445 – Add support for NI 169445 board; only include in 32r2el kernels
    • Octeon – Add support for watchdog of 78XX SOCs, add support for watchdog of CN68XX SOCs, expose support for mips32r1, mips32r2 and mips64r1, enable more drivers in config file, etc…
    • Omega2+ – New board, add support and defconfig
    • Pistachio – Enable Root FS on NFS in defconfig
    • Mediatek/Ralink – Add Mediatek MT7628A SoC, allow NULL clock for clk_get_rate, explicitly request exclusive reset control in the pci-mt7620 PCI driver.
    • SEAD3 – Only include in 32 bit kernels by default
    • VoCore board – Add VoCore as a vendor t0 dt-bindings, add defconfig file

For the complete details, you could check out the full Linux 4.14 changelog – with comments only – generated using git log v4.13..v4.14 --stat, or – kinder to your eyes – read kernelnewsbies’s Linux 4.14 changelog.

Olimex TERES-I DIY OSHW Laptop Now Up for Sale for 240 Euros

October 12th, 2017 14 comments

Olimex has been working on their open source hardware TERES-I DIY laptop since last year. The laptop is supposed to come in kit form, so that you can build it yourself. Every board and most parts are open source to let your easily repair it, or improve it by adapting the part to your own needs.

The company has now launched the laptop kit for 240 Euros in black or white.

Olimex TERES-I laptop updated specifications:

  • SoC – Allwinner A64 quad core ARM Cortex-A53 processor @ 1.2 GHz with Mali-400MP2 GPU
  • System Memory – 2GB DDR3L
  • Storage – 16 GB eMMC Flash, micro SD slot
  • Display – 11.6″ LCD display with 1366×768 resolution
  • Video Output – 1x HDMI 1.4 port
  • Audio – Via mini HDMI, 3.5mm audio jack, 2x speakers, microphone
  • Connectivity – 802.11 b/g/n WiFi up to 150Mbps, Bluetooth 4.0 LE
  • USB – 2x USB port ports
  • Front camera
  • QWERTY keyboard + touchpad with 2 buttons
  • Debugging – Serial debug via header or 3.5mm audio jack
  • Power Supply – 5V/3A
  • Battery – 9,500mAh capacity
  • Weight – ~1 kg

The laptop will ship with Ubuntu 16.04 LTS with Mate, Firefox browser, Video player, Open Office, Arduino IDE and IceStorm for FPGA development (an FPGA add-on board is planned).

Mainboard

The build instructions can be downloaded here. Hardware design files for all 5 boards for the laptop, and software will soon be all found on Github. Note that the laptop is intended for engineering development and evaluation only, should not be considered a finished product, and may not comply with FCC, CE or UL directives. Olimex had quite a lot of people registered their interests before, so they only expect to be able to fulfill new order within 2 or 3 weeks.

Olimex Introduces 40 Euros iCE40HX8K-EVB Board with Lattice ICE40 FPGA

June 23rd, 2017 No comments

Last year, Olimex launched their first FPGA board with iCE40HX1K-EVB. The board is very cheap at 22 Euros, but what you can do with it is limited since it only comes with 1280 logic cells. The company has now introduced an upgraded model called iCE40HX8K-EVB with 7680 logic cells, and more I/O headers.

Olimex iCE40HX8K-EVB specifications:

  • FPGA – Lattice Semi iCE40HX8K-CT256 FPGA with 7680 logic gates, 960 Logic Array Blocks, and 128 Kbit memory
  • System Memory – 256Kx16 SRAM (512KB SRAM)
  • Storage – 2MB serial flash
  • Expansion
    • 34-pin connector to access FPGA I/Os
    • 4x 40 pin connectors for GPIOs
  • Debugging / Programming – 10-pin “PGM” connector
  • Misc – 2x user buttons, reset button, 2x user LEDs, power & programming status LEDs
  • Power Supply – 5V via power jack
  • Dimensions – 67×65 cm

The board is open source hardware with the KiCAD schematics and PCB layout, BoM, and Gerber files available on Github. Lattice IceCube2 or Project IceStorm can be used to program the board. So that means we have an open source FPGA board designed with an open source CAD software (KiCAD), and programmable in Verilog with an open source tool (Project IceStorm).

iCE0-ADC Board

You can use the 34-pin connector to connect add-on boards such as:

  • iCE40-ADC with 100Mhz ADC
  • iCE40-DAC with 100Mhz DAC
  • iCE40-IO with VGA, PS2 and IrDA transceiver
  • MOD-DIO with logic analyzer level shifter with programmable 1.5-5.5V threshold.

The modules can be daisy chained with up to 4x DAC and 4x ADC modules.

Olimex iCE40HX8K-EVB can be purchased for 39.95 Euros on Olimex store, where you’ll also find the aforementioned add-on boards for 9.95 to 15.95 Euros.

Olimex Launches 22 Euros ESP32-GATEWAY Board with Ethernet, WiFi and Bluetooth LE

June 21st, 2017 13 comments

Olimex has just launched ESP32-GATEWAY board, as cost-down version of their ESP32-EVB board, still with Ethernet, WiFi, and Bleutooth LE, but without any relays, CAN bus, nor IR control, less I/Os, and a smaller footprint.

Olimex ESP32-GATEWAY specifications:

  • Wireless Module – ESP32-WROOM32 module with 802.11 b/g/n WiFi and Bluetooth LE
  • Wired Connectivity – 10/100M Ethernet with RJ45 jack (via LAN8710A)
  • External Storage – micro SD slot
  • Expansion – 20-pin GPIO connector
  • USB – 1x micro USB port for debugging (CH340T) and power
  • Misc – Reset and user buttons
  • Power Supply – 5V via micro USB port
  • Dimensions – 62 x 50 mm

Another change is the lack of a LiPo charger to run the board from batteries. Just like most Olimex boards, ESP32-GATEWAY is open source hardware with KiCAD design files available on Github. The software directory is still empty, but Ethernet demo code using ESP32-IDF has been pushed for for ESP32-EVB board, and is likely to run with minor or even no modifications on ESP32-GATEWAY board.

You’ll save 4 Euros over ESP32-EVB board, as Olimex is selling ESP32-GATEWAY board for 22 Euros.

A64-OLinuXino Open Source Hardware Allwinner A64 Development Board Launched for 50 Euros

June 6th, 2017 24 comments

Several boards based on Allwinner A64 quad core 64-bit ARM processor have been available on the market for a while, with products such as Pine A64(+), NanoPi A64, or Banana Pi BPI-M64. Olimex also has been working on A64-OLinuXino since late 2015, and the company has now formally launched the board for 50 Euros, which also happens to be the very first open source hardware board based on Allwinner A64.

A64-OLinuXino Rev. C board specifications:

  • SoC – Allwinner A64 quad core Cortex-A53 processor with Mali-400MP2 GPU
  • System Memory – 1 or 2GB DDR3L @ 672 MHz
  • Storage – micro SD slot, Optional 4 or 16GB industrial grade eMMC flash, optional SPI Flash
  • Video Output & Display I/F – HDMI, 20-pin MIPI & 40-pin LCD display connectors
  • Audio – Via HDMI, 3.5mm Audio In and Out jacks (Headphone output and microphone input can be changed to Line-in and Line-out via jumpers)
  • Connectivity – Gigabit Ethernet, optional BLE/WiFi module
  • USB – 1x micro USB OTG port, 1x USB host port, 1x unpopulated HSIC header
  • Expansion Headers
    • Unpopulated 40-pin GPIO header
    • Unpopulated UEXT header for compatible Olimex modules
  • Debugging – Debug header for serial console
  • Misc – Power, battery charging, and user LEDs; UBOOT, RESET and POWER buttons; RTC battery expansion
  • Power Supply – 5V power jack;  battery connector for 3.7 Li-Po battery; AXP803 PMU with Lipo charger and step-up
  • Dimensions – 90×62.5 mm

Three models will be available with only the second one for sale right now:

  • A64-OLinuXino-1G0G with 1GB RAM, no Flash, no WiFi/BLE
  • A64-OLinuXino-1G4GW with 1GB RAM, 4GB eMMC and WiFi/BLE
  • A64-OLinuXino-2G16G-IND with 2GB RAM, 16GB eMMC with industrial grade components (-40 to +85°C temperature range)

You can also request to have the SPI flash and/or header soldered for an additional fee.

The hardware design files for the latest revision of the board – with schematics designed with KiCAD – should soon be pushed to Github, as currently only Rev. A and Rev. B board files are accessible. The board is said to run Linux and Android, but I have not been able to located firmware images and source code specific to the board yet.

You can purchase A64-OLinuXino-1G4GW board now for 50 Euros plus shipping.

Olimex ESP32-EVB Board with Ethernet, CAN Bus, and Relays up for Sale for 26 Euros

May 30th, 2017 3 comments

One of the new feature of Espressif ESP32 SoC over ESP8266 is the inclusion of an Ethernet MAC interface, but so far few boards come with an RJ45 jacks. ESP32 Monster board is an option, also including an OLED Display and CAN Bus, and sold on Tindie for $35, but Olimex has now stocked their ESP32-EVB board with Ethernet, CAN Bus, and two relays, and you can purchase it for 26 Euros per unit, and less in larger quantities.

Olimex ESP32-EVB Rev. B specifications:

  • Wireless Module – ESP32-WROOM32 module with 802.11 b/g/n WiFi and Bluetooth LE
  • Wired Connectivity – 10/100M Ethernet with RJ45 jack (via LAN8710A)
  • External Storage – micro SD slot
  • Relays – 2x 10A/250VAC relays with LED status
  • Expansion
    • 40-pin GPIO female header (2.54mm pitch)
    • UEXT connector for sensors and modules
    • CAN Bus
  • USB – 1x micro USB port for debugging (CH340T) and power
  • Misc – Reset and user buttons, IR receiver and transmitter with up to 5 meter range
  • Power Supply
    • 5V via power jack or micro USB port
    • LiPo charger and step up converter allowing ESP32-EVB to run from LiPo battery
  • Dimensions – 75 x 75 mm

The specifications are a little different compared to the Rev. A prototype shown in February, as they added IR transmitter and receiver, a CAN bus, and a micro USB port for debugging, which increases the size of the PCB, and also explains why the price went up from an expected 22 Euros to 26 Euros for the final board.

The board is open source hardware, and you’ll find hardware design files on Github. The software directory is empty for now, but the Tindie page about ESP32 Monster board indicates that “Ether and CAN programming requires ESP-IDF environment and still not by Arduino IDE”, so if you want to use the latter you may have wait a little longer. Olimex is also planning for a color 2.8″ LCD 320×240 pixel display board connected through UEXT header.

22€ Olimex ESP32-EVB ESP32 Development Board Features an Ethernet Port and Relays

February 10th, 2017 3 comments

We already have a good choice of ESP32 development boards, but none of the ones I’ve seen make use of the Ethernet MAC interface found in Espressif ESP32 SoC. Olimex has changed that with their ESP32-EVB featuring ESP32-WROOM32 module as well as one Fast Ethernet port and two relays.

Olimex ESP32-EVB specifications:

  • Wireless Module – ESP32-WROOM32 module with 802.11 b/g/n WiFi and Bluetooth LE
  • Wired Connectivity – 10/100M Ethernet RJ45 port
  • External Storage – micro SD slot
  • Relays – 2x 10A/250VAC relays
  • Expansion
    • 40-pin GPIO female header (2.54mm pitch)
    • UEXT connector for sensors and modules
  • Misc – 2x user buttons
  • Power Supply
    • 5V power jack
    • LiPo charger and step up converter allowing ESP32-EVB to run from LiPo battery

The company still have to write software samples, and do some testing to make sure the board work before going into mass production. Once everything is cleared, the board will be sold for 22 Euros.

ESP32-WROVER-KIT Devkit Supports Espressif ESP32 Modules, Includes a 3.2″ LCD Display

December 30th, 2016 5 comments

Yesterday Olimex wrote a blog post informing us that ESP32-CoreBoard was back in stock, one the many ESP32 boards launched late this year, but still hard to get. The company also mentioned they’d have limited quantity of the new ESP32-WROVER with JTAG and LCD display together with the picture below.

esp32-wrover-esp32-lcd-kit

ESP32 is quite more powerful than ESP8266 so it makes sense to have an ESP32 development kit with an LCD display. A quick DuckDuckGo search led me to ESP-WROVER-KIT Getting Started Guide, where we can find more details including the overall specifications:

  • Compatible with ESP-WROOM-32 and ESP32-WROVER modules based on ESP32 dual core Tensilica L108 processor clocked at up to 240 MHz with WiFi and Bluetooth LE connectivity
  • Storage – Micro SD slot
  • Display – 3.2″ LCD display connected via SPI
  • USB – 1x micro USB port
  • Expansion
    • 8-pin UART header
    • 6-pin SPI header
    • 48-pin header for I/Os and camera interface (standard OV7670 camera module supported)
  • Debugging – JTAG through USB interface (FTDI FT2232HL) or 14-pin header
  • Misc – CTS/RTS jumper; power selection (EXT or USB); RGB LED; boot & reset (EN) buttons
  • Power Supply – 5V DC input; 5V to 3.3V LDO chip
  • Dimensions – 85.2 x 79.0 mm
ESP-WROVER-KIT Block Diagram - Click to Enlarge

ESP-WROVER-KIT Block Diagram – Click to Enlarge

The rest of the getting started guide explains how to configure jumpers to set the power source, serial flow control, and JTAG. It also shows how to access the serial console with a typical 115200 8N1 connection, as well as compile and load a simple hello program with ESP-IDF SDK in Windows and Linux.

Image Source: HackerBoads

Image Source: HackerBoards

Beside the development kit itself, I also discovered the new ESP32-WROVER module with the same feature as ESP-WROOM-32 plus an extra 32Mbit pSRAM chip and an external antenna connector.

esp32-wrover

ESP32-WROVER Photo via ESP32 Twitter Account

The kit should be available in January based on Olimex’ blog post, but we don’t have any pricing info yet.