The G400S System on Module (SoM) is the surface mount version of the G400D. The G400D can be programmed in .NET C# and Visual Basic using .NET Micro Framework.
Not recommended for new designs, consider SITCore System on Chip.
Ordering Part Number
- G400S SoM: G400S-SM-480
|Atmel AT91SAM9X35 ARM 926
|32 KByte (SRAM)
|128 MByte (DDR2 SDRAM)
|4 MByte (SPI)
|48.3 x 33.1 x 4.6 mm
|-40 C to +85 C
Note: Not all memory will be available for your application.
Note: Many peripherals share I/O pins. Not all peripherals will be available to your application.
- .NET Micro Framework
- RoHS Lead Free
- 400 MHz ARM 9 Atmel SAM9X35
- 64 MBytes available RAM
- 1.4 MBytes available flash
- Embedded LCD controller
- 89 interrupt capable GPIO
- 2 SPI
- 1 I2C
- 6 UART
- 2 CAN
- 4 PWM
- 12 10-bit analog output
- 4-bit SD/MMC memory card interface
- Low power modes
- USB host
- USB client
- SQLite database
- TCP/IP with SSL
- Full .NET socket interface
- File System
- Full .NET file interface
- SD cards
- USB drives
- Native extensions
- Runtime Loadable Procedures
- Device register access
- Signal controls
- Pulse measurement
Many signals on the G400 are multiplexed to offer multiple functions on a single pin. Developers can decide on the pin functionality to be used through the provided libraries. Any pin with no name, function, or note must be left unconnected.
G400S Recommended Footprint
The G400 is held in reset when the reset pin is low. Releasing it will begin the system startup process. It is pulled high internally
There are four different components of the device firmware:
- GHI Electronics Bootloader: initializes the system, updates TinyBooter when needed, and executes TinyBooter.
- TinyBooter: executes NETMF, updates NETMF when needed, and updates the system configuration.
- NETMF: loads, debugs, and executes the managed application.
- Managed application: the program developed by the customer.
Which components get executed on startup can be control by manipulating the LDR0 and LDR1 pins. LDR0 and LDR1 are pulled high on startup.
|Execute the managed application
|Wait in TinyBooter
|Wait in GHI Electronics Bootloader
Additionally, the communications interface between the host PC and the G400 is selected on startup through the MODE pin, which is pulled high on startup. The USB interface is selected when MODE is high and UART1 is selected when MODE is low.
The above discussed functions of LDR0, LDR1, and MODE are only during startup. After startup, they return to the default GPIO state and are available to use as GPIO in the user application.
.NET Micro Framework (NETMF)
The NETMF software on G400 is mature and complete. For more information on NETMF you can go to the NETMF Introduction page. The NETMF Getting Started page covers NETMF from setup of the host computer to program deployment on both an emulator and target device.
Bootloader v1 is needed for G400 to work with NETMF. It is available in the NETMF SDK.
To set the chip in SAM-BA mode, hold down the dedicated button on your board (SYS A on UCM Dev and Breakout boards) while the system powers up (or during reset). If there is no such button, connect G400S pin SPI1_MISO to ground. Keep the button pressed (pin grounded) for three seconds after power up or reset, then release the pin. The device manager will show a COM port similar to "Bossa Program Port" or "GPS Detect".
- If it is not already installed, download and install the SAM-BA tool from Microchip. The latest version we have tested is 2.18 for Windows. (The tool may not show correctly. Try to make the window larger to see all hidden buttons!)
- Open the SAM-BA program then select the COM port for your device in the connection box and your board type below it (at91sam9x35-ek for G400), then click connect.
- Near the middle of the window, go to the
Enable Dataflash (SPI0 CS0)then click the
Erase Allthen click
Execute. This will take some time to complete. It seems that if SAM-BA loses focus during the erase procedure it can seem to lock up. We recommend that once you click the
Executebutton you leave the computer alone until the erase procedure is completed.
Send Boot File, click execute, then browse to and select the bootloader for the device.
- Once the transfer finishes, go to
Quitand then reset the board. Make sure to properly quit the program or connection errors may result on subsequent uses.
- Now reset the board. Congratulations, your board is now running the loaded program!
Loading the Firmware
- Activate the bootloader, hold the LDR0 signal low while resetting the board.
- Open FEZ Config tool and follow the instructions.
You can also update the firmware manually. See GHI Electronics Bootloader page.
Now that you have installed the bootloader and firmware, you can setup your host computer and start programming. Go to the NETMF Getting Started page for instructions.
This documentation page replaced the legacy datasheet PDF but it is here for reference.
CAN Bit Timing Settings
The following CAN bit timing parameters were calculated for a G400 driving the SN65HVD230 CAN driver chip. See the CAN Tutorial for more information.
|Synchronization Jump Width
|Use Multi Bit Sampling
|Max Osc. Tolerance
|Max Cable Length
Note: Maximum Oscillator Tolerance and Maximum Cable Length are theoretical maximums and must be tested to ensure reliability.
Exposing the following pins is required in every design to enable device programming, updates, and recovery:
- Desired debug interface(s)
- MODE if required to select a debug interface
- SPI1 MISO to update TinyBooter in SDK 2015 R1 and earlier and to install the GHI Electronics Bootloader once for SDK 2016 R1 and later
A typical clean power source, suited for digital circuitry, is needed to power the G400. Voltages should be within at least 10% of the needed voltage. Decoupling capacitors of 0.1 μF are needed near every power pin. Additionally, a large capacitor, typically 47 μF, should be near the G400 if the power supply is more than few inches away. Additionally, the G400 requires additional voltages beyond the typical 3.3 V to function properly. See the pinout table for details.
The G400 includes the needed system and RTC crystals and their associated circuitry.
SPI1 is shared internally with the flash memory on the G400. Use of a chip select with devices on this channel is required or the G400 will not function properly. The use of another SPI channel is recommended.
The built in Ethernet available on the G400D includes all needed Ethernet circuitry internally. However, an appropriate magnet and connector, like the J0011D or similar, are required.
Soldering the G400S
The G400S is designed to be easily machine-placed or hand-soldered. Static sensitive precautions should be taken when handling the module.
The G400S is not sealed for moisture. Baking the module before reflow is recommended and required in a humid environment. The process of reflow can damage the G400 if the temperature is too high or exposure is too long.
The lead-free reflow profiles used by GHI Electronics are shown below. The profiles are based on AIM SAC 305 solder (3% silver, 0.5% copper). The thermal mass of the assembled board and the sensitivity of the components on it affect the total dwell time. Differences in the two profiles are where they reach their respective peak temperatures as well as the time above liquids (TAL). The shorter profile applies to smaller assemblies, whereas the longer profile applies to larger assemblies such as back-planes or high-density boards. The process window is described by the shaded area. These profiles are only starting-points and general guidance. The particulars of an oven and the assembly will determine the final process.