Repository navigation
IPRO SDK V2.3.0
IPRO7 / IPRO7AI and IPRO6S release: one OTA component for every transport, an open example for the IPRO7AI Sensor Tag with flashing over the board's own USB, and the IPRO6S build line. Use it with IPRO Workbench 0.2.0 (https://github.com/INTELPRO-INC/ipro-workbench/releases/tag/v0.2.0) and IntelProCube 0.7.0.1 or later.
| Download | Size | SHA-256 |
|---|---|---|
IPRO-SDK-V2.3.0.tar.gz |
163.4 MB | 0f39c1d2551be0aa748bfee6613ec3c8cb5cfa6b1cea310780f9d58ce216574b |
New:
- OTA component
components/sys/ipro_ota(CONFIG_IPRO_OTA): one package
check for every transport. It reads the 512-byte OTA header, checks the
SHA-256 of the image written to flash before the board switches to it, and
erases each flash sector just before it is written. Two transports use it:- OTA over the console UART: the shell command
ota_uart <bytes> [noapply]
(CONFIG_IPRO_OTA_UART). IPRO Workbench 0.2.0 sends a package to the board
with it (OTA Package → Send to Board). - BLE OTA service (UUID 0xFF60,
CONFIG_IPRO_OTA_BLE): the service
ipro_ble_remotehad, now in the component.ipro_ble_remote
(defconfig_reef) refuses a package whose SHA-256 does not match, and
starts receiving in under half a second instead of about four (it no longer
erases the whole slot first).
Seecomponents/sys/ipro_ota/README.md.
- OTA over the console UART: the shell command
ipro7ai_sensor_tag_demofor the IPRO7AI Sensor Tag board: IMU (ISM330BX:
acceleration, rotation, temperature), fuel gauge (CW2015), button, two LEDs
and buzzer. It prints 20 lines a second ofname:valuepairs over the board's
own USB, which IPRO Workbench 0.2.0's Sensor Dashboard lays out with the
application'sdashboard.yaml; shell commandsstream,rate,led,beep.tools/ipro_dl.py: flashes a board through boot2's USB downloader
(Python standard library only, macOS and Linux). The Sensor Tag example is flashed
with it; IPRO Workbench 0.2.0 on macOS uses it when Flash targets the board's own USB port.- IPRO6S: the boot prints a
Build:line with the build date and time, as
IPRO7 does, so IPRO Workbench can tell which firmware the board runs. - IPRO6S Wi-Fi:
wifi_ap_start -b 1 -o 1keeps a 2.4 GHz access point on
its 40 MHz channel even when neighbouring networks overlap it (-b 1alone
still falls back to 20 MHz, as before). - Fixed: with DTIM power save, an access point whose beacon is sometimes late
behind a neighbour's made the IPRO6S open its receiver too late and miss
beacons; the receive window now stays on the on-time beacon. ipro6_demoships the configurations its prebuilt archives build:
defconfig_ipro6_lpwifianddefconfig_ipro6_lp.defconfig_ipro6_lpwifi_ping
(in V2.2.x) is no longer in the package: it needs the Wi-Fi library sources.- README: IPRO6S is described as Wi-Fi.
Upgrading from V2.2.x: unpack the new package and rebuild your applications.
Validation:
- The package's own build check: 37 FreeRTOS applications build from this
package (ipro_agora_sentinoonce AOSL is fetched), every shipped IPRO6S
defconfig (7) builds, and the Zephyr sample matrix andtwister --build-only
build foripro7_evbandipro7ai_evk. - On an IPRO6S EVK, with IPRO Workbench 0.2.0:
ipro6_demo
(defconfig_ipro6_lpwifi) built from this package, flashed with IntelProCube
0.7.0.1 (partition_cfg_fw_direct.toml), booted with itsBuild:line, and
scanned the access points around it. - On an IPRO7AI Reef EVK V4.0:
ipro7ai_reef_demobuilt from this package and
flashed with IntelProCube 0.7.0.1 passedreef selftest. - On an IPRO7AI Sensor Tag:
ipro7ai_sensor_tag_demobuilt from this package and
flashed over the board's own USB, from the board's USB console and from boot2's
downloader, withtools/ipro_dl.pyand with IPRO Workbench 0.2.0; it streams
its sensors at 20 lines a second.
Documentation: https://intelpro-inc.github.io/ipro-sdk-docs/