Advanced Features

Experimental V1 firmware documentation. Koheron products currently ship with V0.x firmware by default. V1 firmware executables are not publicly available yet. Please contact us if you are interested in early access or would like to evaluate V1 on your device.

This page groups advanced V1 firmware features that are not required for normal terminal configuration. Detailed pages are provided for the largest features:

  • [User Modes](/support/firmware/v1/user-modes/)
  • [UART Multiplexing](/support/firmware/v1/uart-multiplexing/)
  • [Sequencer](/support/firmware/v1/sequencer/)
  • [Binary Status](/support/firmware/v1/binary-status/)

User EEPROM memory

memr and memw access user EEPROM pages. Each page is exactly 32 bytes. Page addresses are hexadecimal and range from 0x00 to 0x3F for the common user-memory command. Product firmware may relocate the user-memory base address, but the command still uses page numbers.

Read one page:

>> memr 0
<32 raw bytes>

The reply is exactly 32 raw bytes, not an ASCII line.

Write one page:

>> memw 0 <32 raw bytes>

memw requires advanced access. The payload must be exactly 32 bytes. The firmware detects this raw binary command and completes the command after the 32-byte payload; do not append text after the payload.

Because these commands are raw binary operations, use a dedicated script and verify data after writing.

EEPROM layout warning

User EEPROM pages share the same physical memory device as firmware configuration, device data, UART configuration and sequencer storage. Use only documented user pages and product-supported workflows. Do not write arbitrary EEPROM addresses from customer software.

Baud rate

brate reads or writes the UART baud rate:

>> brate
115200
>> brate 460800
460800

Writing requires advanced access. After changing the baud rate, host software must reconnect with the new baud rate.

Calibration and production commands

Some firmware commands are present for calibration, production or Koheron diagnostics. These operations can alter calibration data, serial number, model number or production configuration.

Do not use these commands in customer applications unless the product documentation explicitly says to do so.

Hidden does not mean unavailable

Hidden commands are not printed by help, but the command dispatcher can still execute them. The hidden flag is documentation and user-interface metadata, not an authentication mechanism. Access mode checks are implemented inside individual command handlers.

Integration checklist

Before using advanced features in a deployed application:

  • Confirm the installed firmware version with version.
  • Confirm the command set with help and the product command table.
  • Check access mode with usrmode.
  • Check error status with err before and after configuration.
  • Use byte-counted serial code for raw binary commands.
  • Keep a recovery path for muxon, brate and sequ changes.
[email protected]