Update README for DPAA2 commands used to manage MC - Upldate details - Added example

Signed-off-by: Prabhakar Kushwaha prabhakar@freescale.com --- Based upon u-boot-fsl-qoriq.git branch next

arch/arm/cpu/armv8/fsl-layerscape/README.lsch3 | 88 +++++++++++++++++--------- 1 file changed, 59 insertions(+), 29 deletions(-)

diff --git a/arch/arm/cpu/armv8/fsl-layerscape/README.lsch3 b/arch/arm/cpu/armv8/fsl-layerscape/README.lsch3 index b924134..f9323c1 100644 --- a/arch/arm/cpu/armv8/fsl-layerscape/README.lsch3 +++ b/arch/arm/cpu/armv8/fsl-layerscape/README.lsch3 @@ -244,35 +244,65 @@ MMU Translation Tables ... ...

-DPAA2 commands to manage Management complex -------------------------------------------- -Management complex Firmware, DPL and DPC are depolyed during u-boot boot -sequence. - -New DPAA2 commands has been added to manage Management Complex (MC) i.e. -start mc, aiop and apply DPL from command prompt. - -a) fsl_mc start mc [FW_addr] [DPC_addr] - Start Management Complex -b) fsl_mc apply DPL [DPL_addr] - Apply DPL file -c) fsl_mc start aiop [FW_addr] - Start AIOP - -u-boot etherenet support sequence :- -a) fsl_mc start mc [FW_addr] [DPC_addr] - Start Management Complex -b) DPMACs device will be available now for use - -Linux boot sequence :- -a) fsl_mc start mc [FW_addr] [DPC_addr] - Start Management Complex -b) fsl_mc apply DPL [DPL_addr] - Apply DPL file -c) No DPMACs availabe for use in u-boot -c) boot Linux - -AIOP boot sequence :- -a) fsl_mc start mc [FW_addr] [DPC_addr] - Start Management Complex -b) fsl_mc start aiop [FW_addr] - Start AIOP -c) fsl_mc apply DPL [DPL_addr] - Apply DPL file -d) No DPMACs availabe for use in u-boot -Please note actual AIOP start will happen during DPL parsing of Management complex - +DPAA2 commands to manage Management Complex (MC) +------------------------------------------------ +DPAA2 commands has been introduced to manage Management Complex +(MC). These commands are used to start mc, aiop and apply DPL +from u-boot command prompt. + +Please note Management complex Firmware(MC), DPL and DPC are no +more deployed during u-boot boot-sequence. + +Commands: +a) fsl_mc start mc <FW_addr> <DPC_addr> - Start Management Complex +b) fsl_mc apply DPL <DPL_addr> - Apply DPL file +c) fsl_mc start aiop <FW_addr> - Start AIOP + +How to use commands :- +1. Command sequence for u-boot ethernet: + a) fsl_mc start mc <FW_addr> <DPC_addr> - Start Management Complex + b) DPMAC net-devices are now available for use + + Example- + Assumption: MC firmware, DPL and DPC dtb is already programmed + on NOR flash. + + => fsl_mc start mc 580300000 580800000 + => setenv ethact DPMAC1@xgmii + => ping $serverip + +2. Command sequence for Linux boot: + a) fsl_mc start mc <FW_addr> <DPC_addr> - Start Management Complex + b) fsl_mc apply DPL <DPL_addr> - Apply DPL file + c) No DPMAC net-devices are available for use in u-boot + d) boot Linux + + Example- + Assumption: MC firmware, DPL and DPC dtb is already programmed + on NOR flash. + + => fsl_mc start mc 580300000 580800000 + => setenv ethact DPMAC1@xgmii + => tftp a0000000 kernel.itb + => fsl_mc apply dpl 580700000 + => bootm a0000000 + +3. Command sequence for AIOP boot: + a) fsl_mc start mc <FW_addr> <DPC_addr> - Start Management Complex + b) fsl_mc start aiop <FW_addr> - Start AIOP + c) fsl_mc apply DPL <DPL_addr> - Apply DPL file + d) No DPMAC net-devices are availabe for use in u-boot + Please note actual AIOP start will happen during DPL parsing of + Management complex + + Example- + Assumption: MC firmware, DPL, DPC dtb and AIOP firmware is already + programmed on NOR flash. + + => fsl_mc start mc 580300000 580800000 + => fsl_mc start aiop 0x580900000 + => setenv ethact DPMAC1@xgmii + => fsl_mc apply dpl 580700000

Errata A009635 ---------------