When contacting us via email or the inquiry form regarding any issues or malfunctions,
please check and provide the information requested in items (1) to (5) below in
advance. This helps us identify the cause quickly and provide a prompt response.
Thank you for your cooperation.
Note: Please understand that providing only the error code often makes it difficult to
pinpoint the root cause. We may request confirmation of items (1) to (5) prior to
troubleshooting.
(1) Micom Pack Model Name
You can check this under the "MICOM PACK No." display at the top of the Remote Controller (SWX600) screen.
Example: `FRX830M02`
You must use the correct Micom Pack that matches your target MCU. Please note that
using an incorrect Micom Pack is not supported. If programming has never succeeded,
please verify that the target MCU part number matches the Micom Pack.
(2) Version Information
You can check these on the "Version" tab of the Remote Controller (SWX600):
- Firmware Version (FIRM Version): (e.g., `Ver 17.37`)
- FPGA Version (FPGA Version): (e.g., `Ver 28.87`)
- Definition Program Version: (e.g., `Ver 17.04`)
- Parameter Version: (e.g., `Ver 17.00`)
* If you are using an older version, updating to the latest versions may resolve the issue.
(3) Hardware Configuration
- Programmer Model Name: (e.g., `AFX100`, `AFX210`, etc.)
- Probe Hardware Model Name: (e.g., `PHX400`, `PHX401`, `PHX403`, `PHX410`, etc.)
Please check the probe model carefully: for specific low-voltage devices, PHX400
cannot be used and PHX401 or PHX403 is required.
If you are using previous generation models, please provide the programmer model
(e.g., `AF430`, `AF720`) and the adapter model (e.g., `AZ473`, `AZ442`).
(4) Error Code and Error Message
Please provide the complete error text displayed on the screen or in execution logs
without abbreviation.
In particular, the 2-digit or 4-digit code numbers (processing code / detail code) at the
end of the message are essential for identifying the cause.
Example: `1109:DEVICE ERR 02`, `1120:IDCODE MISMATCH 01`, etc.
(5) Detailed Error Symptoms and Conditions
・Frequency / Reproducibility:
(e.g., Occurred suddenly although it worked fine before / Occurs approximately 2 out of 100 times / Has never succeeded once, etc.)
・Executed Command / Operation, :
(e.g., Immediately after executing EPR / During Erase / During Verify / When loading an object file, etc.)
・Status of Target MCU:
(e.g., Programming succeeds with blank/new chips, but fails when reprogramming previously written chips, etc.)
・Other details:
(e.g., Changes in equipment, environment, or wiring before/after the error occurred)
[Important Notice for First-Time Programming (100% Error Rate)]
If programming has never completed successfully once, the primary causes are typically
incorrect wiring or improper programmer settings.
Please re-verify that the actual wiring (including pull-up/pull-down resistor settings)
matches the "Typical Connection Example" described in the user manual of your
Micom Pack, and check that there are no connection issues (such as broken wires,
loose connections, or contact failures on pin fixtures).
[Troubleshooting & FAQ]
Causes and countermeasures for common errors are available on our Support FAQ
page. Please check the following URL: