SDK Initialization failing on cold boot

Shantanu Shrivastava

unread,

Nov 10, 2021, 11:11:34 PM11/10/21

to sonicproject

We are porting sonic on a TD3 based platform. SDK initialisation is failing and also we see bcm knet driver crash.

Steps to reproduce the issue:

Do a cold boot.

Describe the results you received:

syslog:6330:Nov 10 14:48:11.316302 tb63-host2-cimc NOTICE syncd#syncd: :- processOidCreate: creating switch number 1
syslog:6331:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#syncd: [none] SAI_API_SWITCH:board_id_default:601 Failed to obtain switch ID.
syslog:6332:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#/supervisord: syncd :ngknet_dev_ver_check: IOCTL failed on /dev/linux_ngknet#15
syslog:6333:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#/supervisord: syncd :bcma_sys_probe_ngbde: Unable to attach KNET driver#15
syslog:6334:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#/supervisord: syncd Found 0 devices.#15
syslog:6335:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#/supervisord: syncd DMA pool size: 33554432#15
syslog:6336:Nov 10 14:48:11.358965 tb63-host2-cimc INFO syncd#/supervisord: syncd Error : Unknow bus type 0x0 !!#15
syslog:6337:Nov 10 14:48:11.360131 tb63-host2-cimc INFO syncd#syncd: message repeated 11 times: [ [none] SAI_API_SWITCH:board_id_default:601 Failed to obtain switch ID.]
syslog:6338:Nov 10 14:48:11.360131 tb63-host2-cimc CRIT syncd#syncd: [none] SAI_API_SWITCH:platformInit:2042 No attached units.
syslog:6339:Nov 10 14:48:11.360163 tb63-host2-cimc CRIT syncd#syncd: [none] SAI_API_SWITCH:sai_driver_init:443 Error initializing driver, rc = -1.

Describe the results you expected:Output of show version:

SONiC Software Version: SONiC.202012.0-dirty-20211110.093615 Distribution: Debian 10.11 Kernel: 4.19.0-12-2-amd64 Build commit: 1fc4968cd Build date: Wed Nov 10 11:51:37 UTC 2021 Built by: sonic Platform: x86_64-pensando_taormina-r0 HwSKU: Pensando-Taormina ASIC: broadcom ASIC Count: 1 Serial Number: Uptime: 15:04:34 up 37 min, 1 user, load average: 0.00, 0.06, 0.15 Docker images: REPOSITORY TAG IMAGE ID SIZE docker-syncd-brcm 202012.0-dirty-20211110.093615 8a92de26b8b0 702MB docker-syncd-brcm latest 8a92de26b8b0 702MB docker-teamd 202012.0-dirty-20211110.093615 aa6da1826763 420MB docker-teamd latest aa6da1826763 420MB docker-nat 202012.0-dirty-20211110.093615 7b95cce8b607 423MB docker-nat latest 7b95cce8b607 423MB docker-router-advertiser 202012.0-dirty-20211110.093615 82009f25f7a8 410MB docker-router-advertiser latest 82009f25f7a8 410MB docker-platform-monitor 202012.0-dirty-20211110.093615 29e30216a7fb 621MB docker-platform-monitor latest 29e30216a7fb 621MB docker-lldp 202012.0-dirty-20211110.093615 5e1d3d6bc8dd 450MB docker-lldp latest 5e1d3d6bc8dd 450MB docker-snmp 202012.0-dirty-20211110.093615 8ffb957aa767 452MB docker-snmp latest 8ffb957aa767 452MB docker-orchagent 202012.0-dirty-20211110.093615 f3ee84fe159c 439MB docker-orchagent latest f3ee84fe159c 439MB docker-dhcp-relay 202012.0-dirty-20211110.093615 ece1cdb9e7a9 423MB docker-dhcp-relay latest ece1cdb9e7a9 423MB docker-database 202012.0-dirty-20211110.093615 6f5779dbc6cb 410MB docker-database latest 6f5779dbc6cb 410MB docker-sonic-telemetry 202012.0-dirty-20211110.093615 32ef85c34561 499MB docker-sonic-telemetry latest 32ef85c34561 499MB docker-sonic-mgmt-framework 202012.0-dirty-20211110.093615 ab2358e79c79 823MB docker-sonic-mgmt-framework latest ab2358e79c79 823MB docker-fpm-frr 202012.0-dirty-20211110.093615 65e9d58a5a44 438MB docker-fpm-frr latest 65e9d58a5a44 438MB docker-sflow 202012.0-dirty-20211110.093615 fda4385fb43b 421MB docker-sflow latest fda4385fb43b 421MB

Output of show techsupport:

timeout --foreground 5m cat /pro[ 2366.063290] BUG: unable to handle kernel NULL pointer dereference at 0000000000000298 [ 2366.072517] PGD 0 P4D 0 [ 2366.075346] Oops: 0000 [#1] SMP PTI [ 2366.079241] CPU: 4 PID: 13756 Comm: cat Tainted: G IOE 4.19.0-12-2-amd64 #1 Debian 4.19.152-1 [ 2366.090031] Hardware name: HPE Grangeville-NS/Type2 - Board Product Name1, BIOS DL-01-0003 07/01/2021 [ 2366.100350] RIP: 0010:bkn_seq_dma_next_pos+0x2f/0x76 [linux_bcm_knet] [ 2366.107545] Code: e8 fd fc ff ff 48 85 f6 74 60 8b 7a 0c 83 7a 04 00 8d 4f 01 74 37 83 f9 40 7e 37 8b 4a 08 c7 42 0c ff ff ff ff ff c1 89 4a 08 <3b> 88 98 02 00 00 7c 33 8b 02 48 c7 42 04 00 00 00 00 8d 78 01 89 [ 2366.128535] RSP: 0018:ffff9ea6c4abfe48 EFLAGS: 00010202 [ 2366.134372] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001 [ 2366.142345] RDX: ffff8dab4e011520 RSI: 0000000000000001 RDI: 0000000000000040 [ 2366.150317] RBP: ffff8dab7c473aa8 R08: ffff8dab4e011520 R09: ffff8dab7c473aa8 [ 2366.158288] R10: ffff8daba2e08600 R11: 0000000000000000 R12: 00000000ffffffff [ 2366.166261] R13: ffff8dab4e011520 R14: ffff8dab4df7f800 R15: ffff8dab7c473a80 [ 2366.174235] FS: 00007f5f41ac6540(0000) GS:ffff8dabdfb00000(0000) knlGS:0000000000000000 [ 2366.183276] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2366.189694] CR2: 0000000000000298 CR3: 00000007cb9ea003 CR4: 00000000003606e0 [ 2366.197668] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 2366.205641] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 2366.213613] Call Trace: [ 2366.216349] ? bkn_seq_dma_next+0x13/0x23 [linux_bcm_knet] [ 2366.222483] ? seq_read+0x17f/0x410 [ 2366.226370] ? proc_reg_read+0x39/0x60 [ 2366.230557] ? vfs_read+0x91/0x140 [ 2366.234354] ? ksys_read+0x57/0xd0 [ 2366.238154] ? do_syscall_64+0x53/0x110 [ 2366.242439] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9

Regards

Shantanu Shrivastava

unread,

Nov 13, 2021, 5:08:11 AM11/13/21

to sonicproject

Can anyone please reply why is the sdk not recognising the soc unit.

I can see the in lspci the broadcom asic TD3 has been enumerated.

Regards,

Shantanu

Masaru OKI

unread,

Nov 14, 2021, 9:43:16 PM11/14/21

to Shantanu Shrivastava, sonicproject

Me too. I tried with Delta AG9032v2A.

It was caused by a knet driver, I guess.

> Nov 15 10:50:31.436762 sonic INFO syncd#/supervisord: syncd <nounit>:ngknet_dev_ver_check: IOCTL failed on /dev/linux_ngknet#015
> Nov 15 10:50:31.436762 sonic INFO syncd#/supervisord: syncd <nounit>:bcma_sys_probe_ngbde: Unable to attach KNET driver#015
> Nov 15 10:50:31.449683 sonic INFO syncd#/supervisord: syncd Found 0 devices.#015

2021年11月13日(土) 19:08 Shantanu Shrivastava <shan...@pensando.io>:

--
You received this message because you are subscribed to the Google Groups "sonicproject" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonicproject...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/9ffaf833-ffce-4a8d-995c-8339b0eac5e7n%40googlegroups.com.

Shantanu Shrivastava

unread,

Nov 15, 2021, 10:35:21 AM11/15/21

to sonicproject

Hi Masaru,

Are you also trying to bring up td3.

Please let me know if you are able to resolve.

Regards,

Shantanu

Dante Su

unread,

Nov 15, 2021, 9:43:43 PM11/15/21

to Shantanu Shrivastava, sonicproject

Hi Masaru, Shantanu,

Could you please double-check if the TD3 is correctly recognized by the Linux PCI subsystem?

The following message implies a SAI failure that the Broadcom switch silicon is not found when creating the SAI switch object.

Please use the instructions below to check the failures, you may want to reach out to the ODM for a BIOS update to correctly reset the TD3 upon cold-reboot

sudo dmesg | grep 'bde'
sudo lspci -d 14e4: -v

Best Wishes,

Dante (Kuo-Jung) Su

To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/21a59ccf-b942-44e2-98c5-268e1b795176n%40googlegroups.com.

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

Shantanu Shrivastava

unread,

Nov 16, 2021, 4:28:20 PM11/16/21

to sonicproject

Hi Dante,

Thanks for your reply.

The Broadcom device is getting recognised by the linux pci subsystem.

Yet i still see an errors.

syslog:2861:Nov 16 20:06:47.872662 tb63-host2-cimc INFO syncd#syncd: [none] SAI_API_SWITCH:board_id_default:601 Failed to obtain switch ID.

syslog:2862:Nov 16 20:06:47.872662 tb63-host2-cimc INFO syncd#/supervisord: syncd Error : Unknow bus type 0x0 !!#015

syslog:2863:Nov 16 20:06:47.882235 tb63-host2-cimc INFO syncd#syncd: message repeated 11 times: [ [none] SAI_API_SWITCH:board_id_default:601 Failed to obtain switch ID.]

syslog:2864:Nov 16 20:06:47.882235 tb63-host2-cimc CRIT syncd#syncd: [none] SAI_API_SWITCH:platformInit:2042 No attached units.

syslog:2865:Nov 16 20:06:47.882235 tb63-host2-cimc CRIT syncd#syncd: [none] SAI_API_SWITCH:sai_driver_init:447 Error initializing driver, rc = -1.

syslog:2866:Nov 16 20:06:47.882235 tb63-host2-cimc CRIT syncd#syncd: [none] SAI_API_SWITCH:brcm_sai_create_switch:1016 initializing SDK failed with error Operation failed (0xfffffff5).

syslog:2867:Nov 16 20:06:47.882235 tb63-host2-cimc ERR syncd#syncd: :- sendApiResponse: api SAI_COMMON_API_CREATE failed in syncd mode: SAI_STATUS_FAILURE

admin@tb63-host2-cimc:/etc/sonic$ sudo dmesg | grep 'bde'

[ 6.296656] linux_kernel_bde: loading out-of-tree module taints kernel.

[ 7.146193] linux-kernel-bde (542): _init(3115):use_msi = 0

[ 7.147355] linux-kernel-bde (542): Not find vendor(0x184e) device(0x1004) bus

[ 7.147359] linux-kernel-bde (542): Not find vendor(0x184e) device(0x1004) bus

[ 7.147360] linux-kernel-bde (542): Not find vendor(0x184e) device(0x1004) bus

[ 7.176229] linux-kernel-bde (610): Allocating DMA memory using method dmaalloc=0

[ 7.177988] linux-kernel-bde (610): _use_dma_mapping:0 _dma_vbase:000000000a7a9ae8 _dma_pbase:2e000000 _cpu_pbase:2e000000 allocated:1000000 dmaalloc:0, dma64_support:0

[ 62.517118] linux-kernel-bde (118): probing: vendor_id=0x14e4, device_id=0xb870

[ 62.517123] linux-kernel-bde (118): Enabling PCI device : vendor_id=0x14e4, device_id=0xb870

[ 62.517133] linux-kernel-bde 0000:01:00.0: enabling device (0000 -> 0002)

[ 62.517470] linux-kernel-bde (118): found irq 24

[ 62.517473] linux-kernel-bde (118): _pci_probe:irq = 24

[ 62.517493] linux-kernel-bde (118): Set max payload size (128)

[ 62.517495] linux-kernel-bde (118): Set max payload val (0)

[ 62.517517] linux-kernel-bde (118): Found VSEC (4276494)

[ 62.517691] linux-kernel-bde (118): BAR 2: kernel addr:0xffffac0745000000 phys addr:0x183ffc000000 length:800000

[ 62.517786] linux-kernel-bde (118): BAR 0: kernel addr:0xffffac0743c60000 phys addr:0x183ffc800000 length:8000

[ 62.517790] linux-kernel-bde (118): config_pci_intr_type: msi = 0

[ 62.517808] linux-kernel-bde (118): Found VSEC (4276494)

[ 62.517812] linux-kernel-bde (118): iproc version = e dma_hi_bits = 0

[ 62.517822] linux-kernel-bde (118): enable PCI resources 0x6 (PCI_COMMAND)

[ 62.517825] linux-kernel-bde (118): PCI resource len 8MB

[ 62.517833] linux-kernel-bde (118): _pci_probe: configured dev:0xb870 rev:0x1 with base_addresses: 0xffffac0745000000 0xffffac0743c60000

[ 62.517844] linux-kernel-bde (118): Allocating DMA memory using method dmaalloc=0

[ 62.519776] linux-kernel-bde (118): _use_dma_mapping:1 _dma_vbase:0000000028619174 _dma_pbase:4f000000 _cpu_pbase:4f000000 allocated:2000000 dmaalloc:0, dma64_s

root@tb63-host2-cimc:/var/log# sudo lspci -d 14e4:b870 -v

01:00.0 Ethernet controller: Broadcom Limited Device b870 (rev 01)

Subsystem: Broadcom Limited Device b870

Flags: bus master, fast devsel, latency 0, IRQ 24, NUMA node 0

Memory at 183ffc800000 (64-bit, prefetchable) [size=32K]

Memory at 183ffc000000 (64-bit, prefetchable) [size=8M]

Capabilities: [48] Power Management version 3

Capabilities: [50] Vital Product Data

Capabilities: [58] MSI: Enable- Count=1/32 Maskable+ 64bit+

Capabilities: [a0] MSI-X: Enable- Count=64 Masked-

Capabilities: [ac] Express Endpoint, MSI 00

Capabilities: [100] Advanced Error Reporting

Capabilities: [13c] Device Serial Number 00-00-00-00-00-00-00-00

Capabilities: [150] Power Budgeting <?>

Capabilities: [160] Virtual Channel

Capabilities: [180] Vendor Specific Information: ID=0000 Rev=0 Len=028 <?>

Capabilities: [1b0] Latency Tolerance Reporting

Capabilities: [240] L1 PM Substates

Capabilities: [300] #19

Capabilities: [250] #12

Kernel driver in use: linux-kernel-bde

Kernel modules: linux_kernel_bde

Can you please help?

Regards,

Shantanu

Shantanu Shrivastava

unread,

Nov 21, 2021, 10:33:56 PM11/21/21

to sonicproject

Hi Dante,

I have made some changes in the sequence of td3 powerup so it is loading fine but failing durig soc_init with below message.

Seems unlikely as i thought the pcie firmware should be loaded by default when the chip is powered up.

Do i need to configure anything duing powerup? What am i missing?

"PCIe firmware was not loaded on unit 0"

Regards,

Shantanu

Dante Su

unread,

Nov 25, 2021, 8:42:52 PM11/25/21

to Shantanu Shrivastava, sonicproject

Hi Shantanu,

In the case of TD3, the PCIe firmware is fetched from the EEPROM on the card upon POR, and please be sure to have the PCIe firmware upgraded to 2.5 onwards.

For more details, please reach out to the Broadcom SDK team for this issue (you may need to contact the ODM for this). Thanks

Here are the example instructions to check your PCIe firmware revision

e.g.

admin@Leaf-1:~$ bcmcmd 'show unit'
show unit
Unit 0 chip BCM56873_A0 (current)
drivshell>
admin@Leaf-1:~$ bcmcmd 'pciephy fw version'
pciephy fw version
        PCIe FW loader version: 2.5
        PCIe FW version: D102_08
drivshell>

Best Wishes,

Dante (Kuo-Jung) Su

To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/d75e3790-0551-49f5-a907-59ca0bcaef78n%40googlegroups.com.

Hui Li

unread,

Nov 28, 2021, 7:35:10 PM11/28/21

to Shantanu Shrivastava, sonicproject

趙麗穎是穴頭，管北京艾滋病

	Hui Li
邮箱：li7...@gmail.com

签名由网易邮箱大师定制

To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/d75e3790-0551-49f5-a907-59ca0bcaef78n%40googlegroups.com.

Peter Metljak

unread,

Feb 15, 2022, 7:35:35 AM2/15/22

to sonicproject

Hi,

I've come accross simular issue on with device as7316-27xb.

Feb 15 12:20:34 sonic kernel: [ 6.274246] linux_kernel_bde: loading out-of-tree module taints kernel.
Feb 15 12:20:34 sonic kernel: [ 6.274246] linux_kernel_bde: loading out-of-tree module taints kernel.
Feb 15 12:20:38 sonic kernel: [ 10.642942] linux-kernel-bde (504): Allocating DMA memory using method dmaalloc=0
Feb 15 12:20:38 sonic kernel: [ 10.642942] linux-kernel-bde (504): Allocating DMA memory using method dmaalloc=0
Feb 15 12:20:38 sonic kernel: [ 10.659918] linux-kernel-bde (504): DMA buffer pool before mapping kernel_virt:0xffff9c9901000000 physical:0x1000000 size:0x2000000 dmaalloc:0
Feb 15 12:20:38 sonic kernel: [ 10.659925] linux-kernel-bde (504): _init(3157):use_msi = 0
Feb 15 12:20:38 sonic kernel: [ 10.662066] linux-kernel-bde (504): Not find vendor(0x184e) device(0x1004) bus
Feb 15 12:20:38 sonic kernel: [ 10.662070] linux-kernel-bde (504): Not find vendor(0x184e) device(0x1004) bus
Feb 15 12:20:38 sonic kernel: [ 10.662072] linux-kernel-bde (504): Not find vendor(0x184e) device(0x1004) bus
Feb 15 12:20:38 sonic kernel: [ 10.662074] linux-kernel-bde (504): Not find vendor(0x184e) device(0x1004) bus
Feb 15 12:20:38 sonic kernel: [ 10.659918] linux-kernel-bde (504): DMA buffer pool before mapping kernel_virt:0xffff9c9901000000 physical:0x1000000 size:0x2000000 dmaalloc:0
Feb 15 12:20:38 sonic kernel: [ 10.659925] linux-kernel-bde (504): _init(3157):use_msi = 0

Feb 15 13:24:32.197562 sonic NOTICE syncd#syncd: :- processOidCreate: creating switch number 1
Feb 15 13:24:32.253050 sonic INFO syncd#syncd: [none] SAI_API_SWITCH:board_id_default:611 Failed to obtain switch ID.
Feb 15 13:24:32.254636 sonic INFO syncd#syncd: message repeated 12 times: [ [none] SAI_API_SWITCH:board_id_default:611 Failed to obtain switch ID.]
Feb 15 13:24:32.254732 sonic CRIT syncd#syncd: [none] SAI_API_SWITCH:platformInit:2120 No attached units.
Feb 15 13:24:32.254824 sonic CRIT syncd#syncd: [none] SAI_API_SWITCH:sai_driver_init:536 Error initializing driver, rc = -1.
Feb 15 13:24:32.254912 sonic CRIT syncd#syncd: [none] SAI_API_SWITCH:brcm_sai_create_switch:1127 initializing SDK failed with error Operation failed (0xfffffff5).

SONiC Software Version: SONiC.master.72202-486e9b0c7
Distribution: Debian 11.2
Kernel: 5.10.0-8-2-amd64
Build commit: 486e9b0c7
Build date: Sun Feb 13 19:45:57 UTC 2022
Built by: AzDevOps@sonic-build-workers-00162R

Platform: x86_64-accton_as7315_27xb-r0
HwSKU: Accton-AS7315-27XB

ASIC: broadcom
ASIC Count: 1

Serial Number: N/A
Model Number: N/A
Hardware Revision: N/A
Uptime: 13:34:06 up 1:13, 1 user, load average: 0.29, 0.28, 0.25

Docker images:
REPOSITORY TAG IMAGE ID SIZE

docker-dhcp-relay latest 8de2d8e614ed 448MB
docker-sonic-telemetry latest 3301e963d33c 527MB
docker-sonic-telemetry master.72202-486e9b0c7 3301e963d33c 527MB
docker-orchagent latest ff7e0b0bd0d3 461MB
docker-orchagent master.72202-486e9b0c7 ff7e0b0bd0d3 461MB
docker-sflow latest 267e22a739a0 441MB
docker-sflow master.72202-486e9b0c7 267e22a739a0 441MB
docker-teamd latest 1c6cee53c601 440MB
docker-teamd master.72202-486e9b0c7 1c6cee53c601 440MB
docker-nat latest 118556e3c1d8 443MB
docker-nat master.72202-486e9b0c7 118556e3c1d8 443MB
docker-fpm-frr latest b30c9e421576 459MB
docker-fpm-frr master.72202-486e9b0c7 b30c9e421576 459MB
docker-macsec latest ab2dc3e0ac96 443MB
docker-macsec master.72202-486e9b0c7 ab2dc3e0ac96 443MB
docker-gbsyncd-credo latest 07666fddeae3 443MB
docker-gbsyncd-credo master.72202-486e9b0c7 07666fddeae3 443MB
docker-snmp latest 708bf4ec596f 469MB
docker-snmp master.72202-486e9b0c7 708bf4ec596f 469MB
docker-syncd-brcm latest 3616e0c46044 804MB
docker-syncd-brcm master.72202-486e9b0c7 3616e0c46044 804MB
docker-platform-monitor latest 2d980db8a97d 539MB
docker-platform-monitor master.72202-486e9b0c7 2d980db8a97d 539MB
docker-lldp latest 5a3b2e34694b 466MB
docker-lldp master.72202-486e9b0c7 5a3b2e34694b 466MB
docker-router-advertiser latest 77cfc2e5afbf 426MB
docker-router-advertiser master.72202-486e9b0c7 77cfc2e5afbf 426MB
docker-mux latest a2c9e8eaeb83 478MB
docker-mux master.72202-486e9b0c7 a2c9e8eaeb83 478MB
docker-sonic-mgmt-framework latest c5496a0b6f70 581MB
docker-sonic-mgmt-framework master.72202-486e9b0c7 c5496a0b6f70 581MB
docker-database latest 08c3dadac17b 426MB
docker-database master.72202-486e9b0c7 08c3dadac17b 426MB

Maybe somebody have an idea of how to solve this issue ?

Regards,

Peter

ponedeljek, 22. november 2021 ob 04:33:56 UTC+1 je oseba Shantanu Shrivastava napisala:

Shantanu Shrivastava

unread,

Feb 15, 2022, 11:20:11 AM2/15/22

to Peter Metljak, sonicproject

You need to make sure that you have brought broadcom chip out of reset and it is detected in Pcie.

Regards,

Shantanu

You received this message because you are subscribed to a topic in the Google Groups "sonicproject" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonicproject/W_0yVT17pM4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonicproject...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/de876dce-94b5-4058-ad29-9ebb190b0ab1n%40googlegroups.com.

Abdelmuhaimen Seaudi

unread,

Sep 11, 2022, 9:03:45 AM9/11/22

to sonicproject

Hello Shantanu

I have similar issue with BCM56864, could you tell me how you change the startup sequence ?

Thanks

A. Seaudi

Reply all

Reply to author

Forward

Message has been deleted