[device/accton]: Update Accton-AS7326-56X

[pollyhsu2git]

• Update Accton-AS7326-56X to adapt xxx.config.bcm based on the latest update of Device-Specific File Directory Structure
• Update Accton-AS7326-56X upon the port link / led test / PING out / SCP upon self-bringing up the new SAI version, 3.4.0.2

Signed-off-by: polly_hsu@edge-core.com

- What I did
Update Accton-AS7326-56X upon the port link / led test / PING out / SCP upon self-bringing up the new SAI version, 3.4.0.2

- How I did it

1. Update Accton-AS7326-56X to adapt xxx.config.bcm based on the latest update of Device-Specific File Directory Structure the SONiC Porting Guide.
2. Update Accton-AS7326-56X against the latest update of the SONiC Porting Guide (https://github.com/Azure/SONiC/wiki/Porting-Guide).

- How to verify it

1. Target-verified the port mapping of 48x25G+8x100G as expected.
2. Target-verified the port link of -48x25G+8x100G as expected.
3. Target-verified the port led of -48x25G+8x100G as expected, however, we off-loaded the TD3 LED BINs to our self-brought up SAI libraries due to SONiC NOT supporting them currently.
4. Ran config_checker passed on our config.bcm, however, we off-loaded the needed TD3 SDK config setting to our self-brought up SAI libraries due to SONiC NOT supporting them currently (config_check ERRORs them).
   [-] help_cli_enable=1
   [-] ifp_inports_support_enable=1
   [-] memlist_enable=1
   [-] port_flex_enable=1
   [-] reglist_enable=1

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

[lguohan]

except for ifp_inports_support_enable, all others can be added to permitted list. what is the use case for ifp_inports_support_enable? We can help to white list it.

[lguohan]

what is the problem of port led? Can you describe the problem what is not supported by current SAI?

[pollyhsu2git]

@lguohan
For ifp_inports_support_enable, brcm_sai_dm_init needs to set up the SDK config, ifp_inports_support_enable=1 based on the TD3 model brought-up tests.

Jan 1 00:21:02.890487 sonic ERR syncd/syncd: _brcm_sai_create_trap_resource:3983 field group create failed with error Feature unavailable (0xfffffff0).
Jan 1 00:21:02.890487 sonic CRIT syncd/syncd: _brcm_sai_dm_init:8597 initializing hostif state failed with error -2.
Jan 1 00:21:02.890487 sonic CRIT syncd/syncd: brcm_sai_create_switch:449 initializing modules data failed with error -2.
Jan 1 00:21:02.890487 sonic ERR syncd/syncd: :- processEvent: attr: SAI_SWITCH_ATTR_INIT_SWITCH: true
Jan 1 00:21:02.890487 sonic ERR syncd/syncd: :- processEvent: attr: SAI_SWITCH_ATTR_FDB_EVENT_NOTIFY: 0x421130
Jan 1 00:21:02.890487 sonic ERR syncd/syncd: :- processEvent: attr: SAI_SWITCH_ATTR_PORT_STATE_CHANGE_NOTIFY: 0x421140
Jan 1 00:21:02.890487 sonic ERR syncd/syncd: :- processEvent: attr: SAI_SWITCH_ATTR_SWITCH_SHUTDOWN_REQUEST_NOTIFY: 0x421150
Jan 1 00:21:02.890487 sonic ERR syncd/syncd: :- processEvent: attr: SAI_SWITCH_ATTR_SRC_MAC_ADDRESS: 3C:2C:99:CF:72:20
Jan 1 00:21:02.890531 sonic ERR syncd/syncd: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_SWITCH:oid:0x21000000000000, status: SAI_STATUS_NOT_SUPPORTED

[pollyhsu2git]

@lguohan
For the TD3 model,

• It needs the CANCUN firmware to do the initialization. The CACUN firmware is not supported on your SAI. We've reported it via Is the branch, 201811 (Broadcom SAI 3.3 GA release) supporting the Broadcom TD3 chip yet? #2370 wit the detailed debug messages
• For the latest Broadcom chip design, the LED work is off-loaded to the LED micro processor with its LED BIN firmware (Binary). We've see another vendor trying to PR, but rejected due to its binary format. Plus, the LED BIN firmware (Binary) MUST be executed in the specific step within its CANCUN firmware initialization.