Hardware : Manufacturing

We don’t provide source code to these pre-built functional test applications, such as Rangetest, because they expose sensitive areas of the stack architecture. However, if you need to customize the test behavior of the Rangetest application, or you want similar functionality in a different interface, you can create your own application binary (or incorporate these test features into your existing application to avoid having to load a separate image during the manufacturing test process) by using Ember’s Manufacturing Test Library, known as “mfglib”.

Export controls for US-based products are regulated by the Bureau of Industry and Security (BIS), part of the United Stated Department of Commerce.

SIF_LOADB refers to the nSIF_LOAD line used for programming/debugging the EM2xx IC via the 10-pin InSight Port interface. As this line is active-low, it should typically be idling at a high logic level. If the programming utilities (em2xx_load or EM2UsbLoad) detect that the line is idling at a low level (not above the VDD_PADS threshold for high logic) before he programming mode is engaged, they will trigger an error to indicate that the line was in an unexpected state.

This kind of problem usually indicates a hardware issue.

With Ember’s EM260 images, the filenames usually reflect the EZSP serial style used. Depending on the release of EmberZNet you’re using, the firmware filenames may differ according to the significant pieces of functionality that are present/missing from the EM260 network coprocessor [NCP] images.

So, for example, in EmberZNet 3.3.0, there is only one SPI EZSP firmware image: em260-spi-with-standalone-bootloader.hex . This supports all features mentioned below, including debug capability and radio+SPI bootloader support.

On the subject of tokens (non-volatile settings used in the EmberZNet platform), although many customers use the EM2xx_Patch or EM2USBPatch utility to alter the manufacturing token data on each device at manufacturing time, it is possible, as explained in the EmberZNet Utilities Guide (document 120-4020-0000), to manually create an XDV file that can contain manufacturing token data. This XDV file can then be used with EM2xx_Load or EM2USBLoad to load this data into your devices in addition to any normal flash data (such as bootloader and/or application firmware).