It is possible that after programming your programmable token you may find that the token displays an error state where instead of displaying a 6 digit OTP code the token displays six dashes (see example below);
This issue is generally caused when you attempt to burn a programmable hardware token with a seed that is hex encoded rather than base32 encoded
In the example above the hexadecimal version of the seed was pasted into the seed field. After attempting to burn the seed the token was placed in the error state (with dashes displayed).
This issue can easily be resolved by first replacing the seed data with the same seed data, but in base32 form (you can use this tool to convert the seed: hex to base32 conversion);
If we now reburn the token we will find that the error state is removed, and the token will produce the expected OTP codes.