`MCSMsg`

Start/stop messaging with MCs

MCSMsg

Shortest form: mcsm.

Start or stop messaging between the SDK and the embedded ARM cores (uCs) that run Broadcom firmware applications. Messaging with a core must be started before the other MCS commands can talk to it.

Forms: a core number starts messaging with that core; INIT starts messaging with all cores; HALT stops messaging with all cores; STOP <ucnum> stops messaging with one core. The words ignore case but cannot be abbreviated. The built-in help shows [ucnum|Start|Stop]; there is no Start keyword (it prints Error: Invalid parameter), the shell accepts INIT and HALT instead, and STOP needs a core number.

On a switch without embedded cores every MCS command fails without output. Whether a Trident 3 SONiC switch runs any firmware on these cores depends on the SAI configuration (see BCMSAI dump_eapp_config).

Warning

Stopping or halting messaging cuts off any SAI feature that runs on an embedded core. Do not use on a production switch.

Unvalidated — Start messaging with core 0

drivshell> mcsmsg 0

MCSMsg INIT

Start messaging with all cores.

Unvalidated

drivshell> mcsmsg init

MCSMsg HALT

Stop messaging with all cores.

Unvalidated

drivshell> mcsmsg halt

MCSMsg STOP <ucnum>

Stop messaging with one core. A non-numeric argument is read as 0.

Unvalidated

drivshell> mcsmsg stop 0

Built-in help

Parameters: [ucnum|Start|Stop]
    Control messaging with the UCs.
    ucnum = ucnum to start comminicating with (must start first).
    Init = Init messaging with all uCs.
    Halt = Halt messaging with all uCs.
    Stop = Stop messaging with uC.