Versions Compared

Old Version 11

changes.mady.by.user Tracy W

Saved on

compared with

New Version Current

changes.mady.by.user Tracy W

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Uploading NodeTest Application


In order to facilitate RF testing, you will need to upload the NodeTest application onto your Module using a RapidConnect Programming Fixture and ISA3 Adapter.


Note

NodeTest is included in the EmberZNet PRO Stack installation directory, available with the EM35X-DEV Development Kit. If you only purchase the ISA3 Debugger, you will need to contact Silicon Labs support for the NodeTest files.


After installing and configuring the ISA3, you can upload the NodeTest .hex file on the Module.
To load NodeTest:
  • Place your Module into a RapidConnect Programming Fixture. If your module has already been mounted on another board, you will need to use a 10-pin ISA3 header on that other board to communicate with the module
  • Connect your ISA3 to the fixture using the JTAG programming header
  • Use the em3xx_load.exe utility that comes with the ISA3 to load the NodeTest .hex file
    • em3xx_load.exe EM357-nodetest-with-bootloader.hex
Note

em3xx_load.exe can also be found under the install directory for SiLabs's Simplicity Studio. Typically in the install path of "C:\SiliconLabs\SimplicityStudio\<version>\developer\adapter_packs\em3xx\utils"

Running NodeTest


After NodeTest has been loaded, you can run NodeTest:
  • You can interact with NodeTest via the hardware UART or the Virtual UART.
  • Using the Virtual UART requires telnetting to a Debug Adapter (ISA3), port 4900, with the Packet Trace Port cable connected to the chip.
  • You can use the hardware UART in any of these methods:
    • Using a direct UART connection.
    • Using a USB-to-serial connection.
    • Using the passthrough UART mode.
    • Using the passthrough UART mode and opening the “Serial 0” tab of the Console view (opened through the “Launch Console” action of the Adapters view) in Ember Desktop for the device’s connected ISA3.
  • Press Enter in the telnet window or com port window to start the NodeTest application.
  • Note: If using the hardware UART without the Debug Adapter (ISA3), you must configure your comm port program to 115,200 bps, no parity bits, 1 stop bit. If using the hardware UART via the passthrough mode of the Debug Adapter (ISA3), port 4901, configure the Debug Adapter (ISA3) to 115,200 bps by executing the command ember> port 1 115200. Execute the Debug Adapter (ISA3) configuration command by telnetting to the Debug Adapter (ISA3) administration interface at TCP port 4902.
  • Note: Every time NodeTest resets, it will not automatically print any characters. Instead, NodeTest will listen on both the hardware UART and the Virtual UART looking for a carriage return (Enter key). Whichever port NodeTest finds a carriage return on first will become the port that NodeTest uses for all serial interaction until NodeTest resets again.
  • A Return key initiates the NodeTest application on reset. This displays the power-up prompt, ending in the > (greater than) symbol. Pressing the Return key at the prompt will always cause another prompt to be displayed. Executing the help command causes NodeTest to print a list of all available commands with a brief description of the commands.
  • The following setting should be used to configure the GPIOs for our Z357PA20 or Z357PA40 modules with chip antenna: settxpowmode 0 1
  • The following settings should be used to configure the GPIOs for our Z357PA20 or Z357PA40 modules with U.FL connector and external whip antenna: settxpowmode 0 1
    gpioclear c 80

Resources

You can also watch a video that goes over the NodeTest basics here: https://www.youtube.com/watch?v=wxoUHXGRZLA


Info

Please contact Silicon Labs support for any files that you may be missing.



Panel
borderStylesolid
titleOn This Page

Table of Contents
maxLevel1


Panel
borderStylesolid
titleIn This Space

Page Tree
rootApplication Notes
spacesSKB
searchBoxtrue


Panel
borderStylesolid
titleRelated Content

Filter by label (Content by label)
showLabelsfalse
max4
showSpacefalse
cqllabel = "hardware" and parent = "113312124"



Style
{style}
.wiki-content h1 { 
font-family: 'Helvetica Neue', sans-serif; font-size: 30px; font-weight: bold; color: #20b6e1; letter-spacing: 1px; line-height: 1; text-align: left;
#border-bottom: 1px solid #98bddd !important; 
}
.wiki-content h2 { 
font-family: 'Helvetica Neue', sans-serif; font-size: 20px; font-weight: normal; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
.wiki-content h3 { 
font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: bold; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
.wiki-content h4 { 
font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; font-style:italic; color:#00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
#title-text{
font-family: 'Helvetica Neue', sans-serif; font-size: 40px; font-weight: 500; letter-spacing: 1px; line-height: 1; text-align: left;
}

.panel, #content .panel {
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}

.panel .panelHeader {
text-align: left;
color: #FFFFFF;
line-height: 1em;
padding: 10px 10px 5px;
margin-bottom: 0;
background-color: #00517f;
-moz-border-radius-topleft: 5px;
-moz-border-radius-topright: 5px;
-webkit-border-top-right-radius: 5px;
-webkit-border-top-left-radius: 5px;
border-top-right-radius: 5px;
border-top-left-radius: 5px;
color:#FFFFFF
}

{style}