OpenNetworkLinux
OpenNetworkLinux copied to clipboard
[Accton][as4625-30p] Add new platform
CPU: Intel Atom Processor C3508 1.6GHZ DDR4 SDRAM: 16GB 2400MHz with ECC(SO-DIMM) DDR4*1 SPI Flash(boot): 16Mb * 2 M.2 SSD: SATA 32GB MLC EC: IT8528E/VG-I TPM: SLB 9670XQ2.0 FW7.63 INFINEON Management: WGI210AT, INTEL, Out-band Mangement Ethernet port[RJ45], UART RS232 console port(RJ45) MAC: Broadcom Trident3 X2 BCM562771 PoE: STM32F100C8T6BTR1, PoE MCU, BCM59131 *4, PSE Controller Ethernet Ports: 24 x 1G Base-T + 6 x 10G SFP+ (Port1 ~ Port16 support PoE 30W; Port17 ~ Port24 support PoE 90W) Power Supply: AC 600W PSU, UMEC, 1+1 redundant load-sharing, hot-swappable Cooling: F2B fixed fan with 3 pcs of 40mmx40mmx28mm 12V Dimention:350.35mm(L: Depth) x 440mm(W: Width) x 44mm(H: Height)
Logical to Physical Port Mapping:
| Logical Port | Panel Port | Type | PoE Support |
|---|---|---|---|
| 0 | 1 | 1G Base-T | 30W |
| 1 | 2 | 1G Base-T | 30W |
| 2 | 3 | 1G Base-T | 30W |
| 3 | 4 | 1G Base-T | 30W |
| 4 | 5 | 1G Base-T | 30W |
| 5 | 6 | 1G Base-T | 30W |
| 6 | 7 | 1G Base-T | 30W |
| 7 | 8 | 1G Base-T | 30W |
| 8 | 9 | 1G Base-T | 30W |
| 9 | 10 | 1G Base-T | 30W |
| 10 | 11 | 1G Base-T | 30W |
| 11 | 12 | 1G Base-T | 30W |
| 12 | 13 | 1G Base-T | 30W |
| 13 | 14 | 1G Base-T | 30W |
| 14 | 15 | 1G Base-T | 30W |
| 15 | 16 | 1G Base-T | 30W |
| 16 | 17 | 1G Base-T | 90W |
| 17 | 18 | 1G Base-T | 90W |
| 18 | 19 | 1G Base-T | 90W |
| 19 | 20 | 1G Base-T | 90W |
| 20 | 21 | 1G Base-T | 90W |
| 21 | 22 | 1G Base-T | 90W |
| 22 | 23 | 1G Base-T | 90W |
| 23 | 24 | 1G Base-T | 90W |
| 24 | 25 | 10G SFP+ | N/A |
| 25 | 26 | 10G SFP+ | N/A |
| 26 | 27 | 10G SFP+ | N/A |
| 27 | 28 | 10G SFP+ | N/A |
| 28 | 29 | 10G SFP+ | N/A |
| 29 | 30 | 10G SFP+ | N/A |
Follow the steps below to build the Open Network Linux (ONL) image for this pull request (PR):
# Get the ONL master branch
ubuntu@ubuntu:~$ git clone https://github.com/opencomputeproject/OpenNetworkLinux.git
# Prepare and apply patch files (including build_workaround.patch and the patch from PR #1024)
ubuntu@ubuntu:~$ cp build_workaround.patch ./OpenNetworkLinux/
ubuntu@ubuntu:~$ cd OpenNetworkLinux/
ubuntu@ubuntu:~/OpenNetworkLinux$ wget https://patch-diff.githubusercontent.com/raw/opencomputeproject/OpenNetworkLinux/pull/1024.patch
ubuntu@ubuntu:~/OpenNetworkLinux$ git apply --whitespace=nowarn 1024.patch
ubuntu@ubuntu:~/OpenNetworkLinux$ git apply --whitespace=nowarn build_workaround.patch
# Build ONL using the default build steps
ubuntu@ubuntu:~/OpenNetworkLinux$ docker/tools/onlbuilder -10
ubuntu@ubuntu:~/OpenNetworkLinux$ source setup.env
ubuntu@ubuntu:~/OpenNetworkLinux$ make amd64
Follow the steps below to build the Open Network Linux (ONL) image for this pull request (PR):
# Get the ONL master branch ubuntu@ubuntu:~$ git clone https://github.com/opencomputeproject/OpenNetworkLinux.git # Prepare and apply patch files (including build_workaround.patch and the patch from PR #1024) ubuntu@ubuntu:~$ cp build_workaround.patch ./OpenNetworkLinux/ ubuntu@ubuntu:~$ cd OpenNetworkLinux/ ubuntu@ubuntu:~/OpenNetworkLinux$ wget https://patch-diff.githubusercontent.com/raw/opencomputeproject/OpenNetworkLinux/pull/1024.patch ubuntu@ubuntu:~/OpenNetworkLinux$ git apply --whitespace=nowarn 1024.patch ubuntu@ubuntu:~/OpenNetworkLinux$ git apply --whitespace=nowarn build_workaround.patch # Build ONL using the default build steps ubuntu@ubuntu:~/OpenNetworkLinux$ docker/tools/onlbuilder -10 ubuntu@ubuntu:~/OpenNetworkLinux$ source setup.env ubuntu@ubuntu:~/OpenNetworkLinux$ make amd64Thank you. Could you please paste the output of
ip land how you test the ports?
Thank you for providing these logs.
# onlpdump -S
Port Type Media Status Len Vendor Model S/N
---- -------------- ------ ------ ----- ---------------- ---------------- ----------------
24 25GBASE-CR Copper 1m Amphenol NDCCGF-0001 APF16270013KU0
25 25GBASE-CR Copper 1m Amphenol NDCCGF-0001 APF16270013KU0
26 NONE
27 NONE
28 NONE
29 NONE
Shouldn’t 30 ports be listed in there?
Thank you for providing these logs.
# onlpdump -S Port Type Media Status Len Vendor Model S/N ---- -------------- ------ ------ ----- ---------------- ---------------- ---------------- 24 25GBASE-CR Copper 1m Amphenol NDCCGF-0001 APF16270013KU0 25 25GBASE-CR Copper 1m Amphenol NDCCGF-0001 APF16270013KU0 26 NONE 27 NONE 28 NONE 29 NONEShouldn’t 30 ports be listed in there?
onlpdump only lists SFP ports, not TP ports. Presumably ports 0 to 23 are standard ethernet ports.
Thank you for the clarification.
Could you please list the ports 0 to 23 then?
Thank you for your comment.
I have added the following detailed port mapping table to the PR description for clarity:
Logical to Physical Port Mapping:
| Logical Port | Panel Port | Type | PoE Support |
|---|---|---|---|
| 0 | 1 | 1G Base-T | 30W |
| ... | ... | ... | ... |
| 23 | 24 | 1G Base-T | 90W |
| 24 | 25 | 10G SFP+ | N/A |
| ... | ... | ... | ... |
| 29 | 30 | 10G SFP+ | N/A |
Please let me know if this format meets your needs or if you would like the information presented elsewhere or in a different format.
Thank you for replying so quickly.
Please let me know if this format meets your needs or if you would like the information presented elsewhere or in a different format.
This table is very useful. Thank you.
Why I am asked the question regarding building and listing the ports is, that I thought you need some binaries from Broadcom to make full use of the device, and these binaries are not in the ONL archive, are they?
You are correct that, to fully utilize some advanced features—such as SDK-based management or advanced switching functions—proprietary Broadcom binaries are required. Due to licensing, these binaries are not included in the public ONL archive. For this PR, I have only ported the platform-related code and have not integrated or tested with the Broadcom SDK or any proprietary binaries.
You are correct that, to fully utilize some advanced features—such as SDK-based management or advanced switching functions—proprietary Broadcom binaries are required. Due to licensing, these binaries are not included in the public ONL archive. For this PR, I have only ported the platform-related code and have not integrated or tested with the Broadcom SDK or any proprietary binaries.
Thank you for clearing this up. It’d be great if you added this to the commit message.
You are correct that, to fully utilize some advanced features—such as SDK-based management or advanced switching functions—proprietary Broadcom binaries are required. Due to licensing, these binaries are not included in the public ONL archive. For this PR, I have only ported the platform-related code and have not integrated or tested with the Broadcom SDK or any proprietary binaries.
Thank you for clearing this up. It’d be great if you added this to the commit message.
I have updated the commit message to clarify the limitation as you recommended.