User Tools

Site Tools


t4_errorcodes

This is an old revision of the document!


Twiddler 4 Error Codes

In the event of product damage, part failure or firmware issue, the Twiddler will go into an Error state and blink red. Decoding the blinks will allow you to pinpoint the issue.

The LEDs are named when looking at the Twiddler 4 in an upright position.

[LED 1] [LED 2] [LED 3]

First, there is a rapidly flashing LED pattern; followed by a slow-blinking numbered code. Take note of which LEDs are blinking red, they indicate the type of error that is occurring.

1st pattern – Rapid Flashing indicating type of failure

LED 1 LED 2 LED 3 Error Type
RED 1: Hardware
RED 2: Software
RED RED 3: Bluetooth
RED 4: Initialization

2nd pattern – Slow Flashing indicating failure point

After the type of failure has been indicated, the Twiddler will slowly blink to indicate the failure point. Each LED will flash 0 to 5 times times representing a digit value of the code number. 1 flash = 1, 2 flashes = 2, and so on. No flashes on a LED is value of zero.

e.g. LED 1: 2 flashes LED 2: 1 flash LED 3: 3 flashes This represents error code #213

LED 1: 0 flashes LED 2: 0 flashes LED 3: 4 flashes This represents error code #004

Hardware (L3)

L1 L2 L3 Failure Point
R ERR_HW_I2SINIT
R-R ERR_HW_I2C_WR
R-R-R ERR_HW_I2C_RDS
R-R-R-R ERR_HW_PAW_INIT

Software (L2)

L1 L2 L3 Failure Point
R ERR_SW_APPHANDLER

Bluetooth (L2 & L3)

L1 L2 L3 Failure Point
R ERR_BLE_ADV_START
R-R ERR_BLE_ADV_PEER_ADDR_REPLY
R-R-R ERR_BLE_ADV_WHITELIST_REPLY
R ERR_BLE_PM_ID_LIST
R R ERR_BLE_PM_WHITELIST_GET
R R-R ERR_BLE_PM_WHITELIST_SET
R R-R-R ERR_BLE_PM_DATA_BONDING_LOAD
R R-R-R-R ERR_BLE_PM_DEVICE_IDENTITIES_SET
R R-R-R-R-R ERR_BLE_PM_PEERS_DELETE
R-R ERR_BLE_EVT_GAPCONNECTED_QWR_CONN_HANDLE_ASSIGN
R-R R ERR_BLE_EVT_GAP_PHY_REQ_PHY_UPDATE
R-R R-R ERR_BLE_EVT_GATTC_TIMEOUT_DISCONNECT
R-R R-R-R ERR_BLE_EVT_GATTS_TIMEOUT_DISCONNECT
R-R R-R-R-R ERR_BLE_EVT_HIDS_OUTP_REP_GET
R-R-R ERR_BLE_ERRORHANDLER_HIDS
R-R-R R ERR_BLE_ERRORHANDLER_PARAMS
R-R-R R-R ERR_BLE_ERRORHANDLER_NRF_QWR
R-R-R R-R-R ERR_BLE_ERRORHANDLER_ADV

Initialization (L1)

L1 L2 L3 Failure Point
R ERR_INIT_I2C_INIT
R-R ERR_INIT_NRF_DRV_CLK_INIT
R-R-R ERR_INIT_NRF_PWR_MGMT_INIT
R ERR_INIT_BLE_GAP_NAME_SET
R R ERR_INIT_BLE_GAP_APPEARANCE_SET
R R-R ERR_INIT_BLE_GAP_PCCP_SET
R R-R-R ERR_INIT_BLE_DIS_INIT
R R-R-R-R ERR_INIT_BLE_BAS_INIT
R R-R-R-R-R ERR_INIT_BLE_QWR_INIT
R R ERR_INIT_BLE_GAP_PARAMS
R R R ERR_INIT_BLE_GATT
R R R-R ERR_INIT_BLE_CONN_PARAMS_INIT
R R R-R-R ERR_INIT_BLE_HIDS
R R R-R-R-R ERR_INIT_BLE_ADV_INIT
R R R-R-R-R-R ERR_INIT_BLE_NRF_SDH_EN_REQ
R R-R ERR_INIT_BLE_NRF_SDH_BLE_DEFAULT_CFG_SET
R R-R R ERR_INIT_BLE_NRF_SDH_BLE_EN
R R-R R-R ERR_INIT_BLE_PM_INIT
R R-R R-R-R ERR_INIT_BLE_PM_SEC_PARAMS_SET
R R-R R-R-R-R ERR_INIT_BLE_PM_REGISTER
R-R ERR_INIT_APP_USBD_INIT
R-R R ERR_INIT_APP_USBD_CLASS_APPEND_MOUSE
R-R R-R ERR_INIT_APP_USBD_CLASS_APPEND_KB
R-R R-R-R ERR_INIT_APP_USBD_CLASS_APPEND_MSD
R-R R-R-R-R ERR_INIT_APP_USBD_CLASS_APPEND_CONSUMER
R-R R-R-R-R-R ERR_INIT_APP_USBD_POWER_EVTS_EN
R-R-R ERR_INIT_APP_TIMER_INIT
R-R-R R ERR_INIT_APP_TIMER_CREATE
R-R-R R-R ERR_INIT_APP_TIMER_START

Error Example

Test Case: Power up device WITHOUT connecting U3 (PAW OFN) to J4

Expected Blink Pattern:

  • R,G,B then,
  • L3 blinking rapidly indicating a hardware fault,
  • then L3 blinking Slowly 4 times indicating ERR_HW_PAW_INIT.
t4_errorcodes.1729890415.txt.gz · Last modified: by eric