How can I capture the entire flash contents of my device (including manufacturing and stack token data)?

EM250/EM260
Flash data from an EM2xx chip can be captured using em2xx_read.exe, which is part of the SIF Toolkit installed by xIDE For EM250 or by the EmberZNet EM260 installer.

To capture the contents of a device in a standard Intel HEX record (HEX file format), use a command like:

em2xx_read -id 10.0.0.1 -includeSIMEE -outfile foo.hex

…replacing the IP address with that of the InSight Adapter you have attached to the target EM2xx device or with the USBLink device ID of the USBLink attached to your target.

Note that older versions of the SIF Toolkit may not work with USBLink devices (such that EM2USBRead.exe from the USBLink toolkit is required instead), and these versions require the “-id” flag to be replaced with “-sid” for InSight Adapter targets.

See http://en.wikipedia.org/wiki/Intel_HEX for more information about how to interpret Intel HEX file contents. Note that Simulated EEPROM (in the last 8KB of main flash contents) is specially wear-leveled for token data usage and therefore is not straightforward to interpret. If you need assistance interpreting your token data from a HEX file, please contact Ember customer support.

EM35x
Flash data from an EM35x chip can be captured using em3xx_load.exe, which is part of the ISA3 Utilities installer. (See http://portal.ember.com/em35x for links to latest EM35x software installations.)

To capture the contents of the main flash block (MFB, which includes application firmware, bootloader firmware, and SimEEPROM token data) from a device in a standard Motorola S-Record (S37 file format), use a command like:

 em3xx_load --ip 10.0.0.1 --read @mfb foo.s37

…replacing the IP address with that of the ISA3 you have attached to the target EM35x device (or the —ip argument can be omitted if the target’s ISA3 is attached via USB).

If the Flash Information Block (Ember-programmed manufacturing tokens) or Customer Information Block (customer-programmed manufacturing tokens) are desired in the captured data, the “@fib” and “@cib” arguments can be added to the command line.

See http://en.wikipedia.org/wiki/SREC_%28file_format%29 for more information about how to interpret Motorola S-Record file contents. Note that Simulated EEPROM (usually the last 8KB of main flash contents) is specially wear-leveled for token data usage and therefore is not straightforward to interpret. If you need assistance interpreting your token data from an S37 file, please contact Ember customer support.