Skip to main content

Current Known Issues

All imps

Pulse Counter

Server Connections

  • If server.connect() returns a code 4 (NO_SERVER) to indicate an error, this same code may be repeated if subsequent connection attempts fail, even if they fail for a different reason.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release.

Squirrel Strings

  • Device-side Squirrel does not deal correctly with strings longer than 65,535 bytes. No warnings or errors are currently generated, either at compile-time (for literals) or run-time (for constructed strings), but oversize strings behave as if their lengths were reduced modulo 65,536.
    • Workaround Check the lengths of strings likely to contain 65,535 Ascii characters (fewer if you use unicode) and segment into multiple strings as necessary.

SPI Flash Timings

  • From impOS 34, the value passed into spiflash.setspeed() will survive a Squirrel reload (eg. after waking from deep sleep), so that the speed set on the first call to spiflash.enable() (made in the the first Squirrel run after a cold boot, ie. a power cycle) will be retained if the application attempts to alter the speed following a warm boot (ie. a Squirrel restart).

UART FIFO

  • Custom UART FIFO sizes, as set by uart.settxfifosize() and/or uart.setrxfifosize(), are not set back to their defaults when Squirrel is reloaded (eg. when using the Build and Force Restart button in impCentral™). The sizes are only reset to their defaults when the imp reboots in some way: either a cold boot (power-cycle) or a warm boot (eg. wake from server.sleepfor()).
    • Expected Fix This issue is scheduled to be addressed in a future impOS release, under which any Squirrel reload will also cause UART FIFOs to be reset to their default sizes.

impC001

  • Not all imp API methods are implemented on the impC001 (as of impOS 38).

imp003

Sampler

  • The imp003 has ten ADC-capable pins but can currently only sample from no more than eight of these at a time.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release.

imp005

Ethernet

  • Ethernet interface data not present in net.info() if imp005 is disconnected.
    • Under impOS 36, the Ethernet interface is not present in net.info() output when the Ethernet is not powered up. Ethernet is not powered up when the imp is disconnected.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release.

nv

  • Device-side persistent storage via the nv table is not present on the imp005.

RTC

  • On-device Real-Time Clock — Squirrel’s time() and date() are only correct after connecting to the server.

UART FIFO

  • Calling uart.disable() does reset the FIFO sizes back to the defaults. This behavior does not occur on any other imp.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release, under which this effect will be removed from the imp005 to ensure consistent behavior across all imps (uart.disable() does not reset the FIFO sizes).

USB

  • USB isochronous endpoints are not supported.
  • impOS 36 adds interrupt-in endpoints.
  • In impOS 34, only bulk and control endpoints are supported.

Wake Reason

  • The imp API method hardware.wakereason() is not available on the imp005.
    • This behavior is not now expected to change.

WPS

  • BlinkUp™ can transmit a WPS (WiFi Protected Setup) code to a device. This mode of configuration is not supported on imp005-based devices. For this reason, imp.net.configurewps() is not available on the imp005.
    • This behavior is not expected to change.
    • Workaround For WiFi access, provide the device with the network’s SSID and password, not a WPS code.

Agent

Crypto

  • RESOLVED While the crypto object methods are now supported in agent code, this is only the case with agents paired to development devices. Agents paired with production devices cannot yet make use of these methods.

General Issues

Please see the Knowledgebase.