M-Labs
/
artiq-zynq
10
1
Fork 19
Code Issues 13 Pull Requests Releases Wiki Activity

satellite: I2C I/O expander #0 service failed and nested block_on nested panic! #262

New Issue
Closed
opened 2023-09-18 15:50:16 +08:00 by morgan · 4 comments
morgan commented 2023-09-18 15:50:16 +08:00
Owner
Copy Link

Using master jtag variant on kasli-soc and connect the SFP to kasli satellite relesae-7 result in the following error.

[     2.409684s]  INFO(runtime::rtio_mgt::drtio): [DEST#0] destination is up
Core 0 panic at runtime/src/main.rs:118:14: I2C I/O expander #0 service failed: "PCA954X failed to ack write address"
Backtrace: 
0x164128 0x16fbec 0x1716e8 0x123d68 0x11d0d4 0x119f28 0x119f98 0x153198 0x1699b4 0x1aa18c 0x1aa140 0x1a9fb4 0x1a9ee8 
End backtrace
[     2.544109s] ERROR(runtime::panic): panic at runtime/src/main.rs:118:14
[     2.550705s] ERROR(runtime::panic): panic message: I2C I/O expander #0 service failed: "PCA954X failed to ack write address"
[     0.007190s]  INFO(libboard_zynq::i2c): PCA9548 detected
[     0.038945s]  INFO(runtime::comms): network addresses: MAC=fc-0f-e7-07-58-bc IPv4=192.168.1.56 IPv6-LL=fe80::fe0f:e7ff:fe07:58bc IPv6: no configured address
Core 0 panic at /build/cargo-vendor-dir/libasync-0.0.0/src/executor.rs:67:17: nested `block_on`
nested panic!

For the satellite jtag variant, it works fine when connecting to a kasli-soc master release-7.

Tried commit

Using master jtag variant on `kasli-soc` and connect the SFP to `kasli` satellite relesae-7 result in the following error. ``` bash [ 2.409684s] INFO(runtime::rtio_mgt::drtio): [DEST#0] destination is up Core 0 panic at runtime/src/main.rs:118:14: I2C I/O expander #0 service failed: "PCA954X failed to ack write address" Backtrace: 0x164128 0x16fbec 0x1716e8 0x123d68 0x11d0d4 0x119f28 0x119f98 0x153198 0x1699b4 0x1aa18c 0x1aa140 0x1a9fb4 0x1a9ee8 End backtrace [ 2.544109s] ERROR(runtime::panic): panic at runtime/src/main.rs:118:14 [ 2.550705s] ERROR(runtime::panic): panic message: I2C I/O expander #0 service failed: "PCA954X failed to ack write address" [ 0.007190s] INFO(libboard_zynq::i2c): PCA9548 detected [ 0.038945s] INFO(runtime::comms): network addresses: MAC=fc-0f-e7-07-58-bc IPv4=192.168.1.56 IPv6-LL=fe80::fe0f:e7ff:fe07:58bc IPv6: no configured address Core 0 panic at /build/cargo-vendor-dir/libasync-0.0.0/src/executor.rs:67:17: nested `block_on` nested panic! ``` For the satellite jtag variant, it works fine when connecting to a `kasli-soc` master release-7. ### Tried commit - f3dcd53086ec569e326e5b57cd8ae074c9010153 (current master) - master: NG, Satellite: OK - b23c822ad2063d1ae10aa12d17151ac0c41df7b5 - master: NG, Satellite: OK - 85ecff2cc1b096e55b3c315e976b198da32fe9a4 - can't compile - 3a305c8cac1427231dd624e9c4568a754191d7d0 - Both OK
sb10q commented 2023-09-18 20:38:00 +08:00
Owner
Copy Link

Probably the zynq-rs update (85ecff2cc1). Try bisecting on the zynq-rs versions.

Probably the zynq-rs update (85ecff2cc1). Try bisecting on the zynq-rs versions.
sb10q commented 2023-09-18 20:38:51 +08:00
Owner
Copy Link

I suspect this is c15b54f92b

I suspect this is https://git.m-labs.hk/M-Labs/zynq-rs/commit/c15b54f92b3d4e125ae47a0dce7abe4b2bc9e054
sb10q commented 2023-09-18 20:39:06 +08:00
Owner
Copy Link

@jmatyas

@jmatyas
morgan commented 2023-10-27 11:53:14 +08:00
Author
Owner
Copy Link

issue is fixed as of a08a42c954

issue is fixed as of a08a42c954
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
release-7
release-8
release-6
Labels
Clear labels   
priority:critical

   
priority:high

   
priority:low

   
priority:medium
No Label
priority:critical
priority:high
priority:low
priority:medium
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/artiq-zynq#262
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?