Skip to main content

Current Known Issues

All imps

  • Reconfiguring the pulse-counter with a different duration causes mis-counted pulses.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release.
  • 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.
  • 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.
  • 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).
  • 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.

imp003

  • 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 expected to be addressed in a future impOS release.

imp005

Ethernet

  • Ethernet interface data not present in net.info() if imp005 is disconnected.
    • Expected Fix This issue is scheduled to be addressed in a future impOS release.
  • Device-side persistent storage via the nv table is not present on the imp005.
  • On-device Real-Time Clock — Squirrel’s time() and date() are only correct after connecting to the server.

WPS

Agents

None