FMan functions implemented thru microcode are the following:
A- ‘’Independent Mode’’
Simplified FMan-to-Memory model, bypassing BMan/QMan for Boot/Debug purposes and simple Ethernet driver
B- Table Lookup Coarse Classification
To classify incoming packets thru some protocol headers exact match criteria
C- Advanced packet processing offloads
Header manipulation, IP-Fragmentation/Reassembly, IPSec pre-processing
D- Host Command interface
QMan based FMan control commands used by core/SW for updating some FMan global configuration during operation.
Can FMan provide Ethernet without loading microcode?
Overall answer is YES …
… as far as functions listed for Q1 (IM-Independent Mode, Host Interface, Table Lookup Coarse Classification, Advanced packet processing offloads) are not needed, none of them being strictly mandatory.
Software reference environment provided by FSL (Linux/SDK) or other suppliers require microcode to be loaded ..
What is FMan Independent Mode (IM), what is it used for?
IM is a simplified FMan mode of operation where Ethernet Rx and Tx are managed through simple BD rings as in PowerQUICC and non-DPAA QorIQ devices.
In IM mode, BMan and QMan are not used and thus do not need to be initialized.
IM mode is primarily intended for use during boot phase, before application performs full initialization of all DPAA resources (FMan/BMan/QMan …).
IM can also be used in operational mode (after boot phase) but due to simple BD ring model, the use of IM generally leads to lower Ethernet performance.