The following table summarizes the solutions available when doing embedded configuration and the relative advantages and disadvantages of each solution.
| Supported | |||
|---|---|---|---|
| Configuration Software | Configuration Mode | Advantage | Disadvantage |
| Jam STAPL Bytecode | JTAG | Multi-family, Multi-vendor support | Larger code size |
| JRunner | JTAG | Small code size | Recompile to add new device support |
| MicroBlaster | Passive-serial | Small code size | Recompile to add new device support |
There are two options when doing configuration via the JTAG port - Jam STAPL or JRunner. To program MAX devices, or another vendor's device, in addition to the Altera FPGA, then Jam STAPL Bytecode is the solution. However, to configure only Altera FPGAs while bypassing another vendor's device, then JRunner is a better solution, because it uses less memory (both code space and program memory). The relative disadvantage of JRunner is that recompilation of new source code is required in order to add new device support (once JRunner has been compiled for a particular device and embedded system, it will not need to be recompiled again).
MicroBlaster is the solution available for Passive-Serial configuration. The advantage of this solution is that it has the smallest code size of any solution Altera provides. The disdvantage is that code may need to be recompiled for new device support.
For more detailed information about each of these solutions, they can be downloaded from the Altera home page at: