Twiddler

User Tools

Site Tools

Trace:
t4_errorcodes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
t4_errorcodes [2024/10/25 20:00] – tonyt4_errorcodes [2024/10/25 21:13] (current) – [Error Example] eric
Line 1: Line 1:
 ====== Twiddler 4 Error Codes ====== ====== Twiddler 4 Error Codes ======
  
-In the event of product damage, part failure or code issue, the Twiddler will go into an Error state and blink red.  Decoding the blinks will allow you to pinpoint the issue.+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 first set of blinks are rapid blinks to get your attention.  Take note of which LEDs are blinking red, they indicate the type of error that is occuring.+The LEDs are named when looking at the Twiddler 4 in an upright position. 
  
-**1st pattern – Rapid Flashing indicating type of failure** +[LED 1] [LED 2] [LED 3]
-^ L1 ^ L2 ^ L3 ^ Error ^ +
-| | | RED | Hardware | +
-| | RED | | Software | +
-| | RED | RED | Bluetooth | +
-| RED | | | Initialization | +
-| RED | RED | RED |Debug (Developer Only)|+
  
-So, if the Twiddler is rapidly blinking L3 (the right most LED) then it is a Hardware Error.  +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 – Error Type ===== 
 + 
 + 
 +^ LED 1 ^ LED 2 ^ LED 3 ^ Error Type ^ 
 +| | | RED | 1: Hardware | 
 +| | RED | | 2: Software | 
 +| | RED | RED | 3: Bluetooth | 
 +| RED | | | 4: Initialization | 
 + 
 + 
 + 
 +===== 2nd pattern – Error Code =====
  
 After the type of failure has been indicated, the Twiddler will slowly blink to indicate the 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
 +
  
-2nd pattern – Slow Flashing indicating failure point+==== Error Example====
  
-**Hardware (L3)** +**Test Case**: Power up device WITHOUT connecting U3 (PAW OFN) to J4
-^ L1 ^ L2 ^ L3 ^ Failure Point ^ +
-| | | R | ERR_HW_I2SINIT | +
-| | | R-R | ERR_HW_I2SINIT | +
-| | | R-R-R | ERR_HW_I2SINIT | +
-| | | R-R-R-R | ERR_HW_I2SINIT |+
  
-**Software (L2)** +Expected Blink Pattern: 
-^ L1 ^ L2 ^ L3 ^ Failure Point ^ +  * R,G,B then, 
-| | | R | ERR_HW_I2SINIT |+  * LED 3 blinking rapidly indicating a hardware fault, 
 +  * then LED1 and LED 2 not blinking, LED3 blinking slowly 4 times indicating Error: Hardware Code=004
  
-**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 | 
  
t4_errorcodes.1729886411.txt.gz · Last modified: by tony

Page Tools