Comments (8)
The problem is that the given package is not even a WHD event.
So trying to read the EventHeader fails...
Seems like WHD events in reality are Broadcom brcmf events.
#3 should fix this issue.
from cyw43.
The issue appears to be related to EventHeader
deserializing improperly such that evt_data.datalen
is far larger than the real data buffer. I've not identified what the proper offset is for this header. Documentation on what BcdHeader
can contain and where EventHeader
's format is defined would be appreciated.
from cyw43.
Some addition trace logging:
0.645521 TRACE tx SdpcmHeader { len: 1072, len_inv: 64463, sequence: 0, channel_and_flags: 0, next_length: 0, header_length: 12, wireless_flow_control: 0, bus_d
ata_credit: 0, reserved: [0, 0] }
0.645598 TRACE CdcHeader { cmd: 263, len: 1044, flags: 2, id: 1, status: 0 }
0.645733 TRACE [30, 04, cf, fb, 00, 00, 00, 0c, 00, 00, 00, 00, 07, 01, 00, 00, 14, 04, 00, 00, 02, 00, 01, 00, 00, 00, 00, 00, 63, 6c, 6d, 6c, 6f, 61, 64,
00, 02, 10, 02, 00, 00, 04, 00, 00, 00, 00, 00, 00]
0.647205 TRACE rx [00, 01, ff, fe, 00, 01, 00, 0c, 00, 00, 00, 00, 5c, 14, 04, 1a, 0c, 42, 88, 1d, 04, 4e, 1a, 01, 4c, 50, 02, a5, 2e, 59, 68, c2, 6c, 83, 23, 1
8, 2b, 48, d2, 20, 13, 58, c6, 24, f0, 55, 46, 14]
0.647370 TRACE rx SdpcmHeader { len: 256, len_inv: 65279, sequence: 0, channel_and_flags: 1, next_length: 0, header_length: 12, wireless_flow_control: 0, bus_da
ta_credit: 0, reserved: [0, 0] }
0.647448 TRACE BcdHeader { flags: 92, priority: 20, flags2: 4, data_offset: 26 }
0.647500 TRACE [c1, 54, 30, dc, 41, 00, 40, 00, 04, 10, 02, b0, 00, 21, 50, 10, 14, c0, 88, c7, ee, 90, 70, 08, 7f, 10, 02, a0, 0a, 04, a1, 54, 00, 22, 84,
91]
0.647686 TRACE rx EventHeader { version: 32528, flags: 672, event_type: 168075604, status: 2262161, reason: 1045727236, auth_type: 138448032, datalen: 347347
8656, addr: [65, 145, 17, 225, 51, 5], ifname: [0, 139, 32, 1, 8, 0, 64, 68, 114, 53, 2, 132, 136, 5, 113, 76], ifidx: 32, bsscfgidx: 1 }
0.647905 ERROR panicked at 'range end index 3473478656 out of range for slice of length 64', library/core/src/slice/index.rs:73:5
Something is up with the deserialization of the EventHeader
, none of these values look correct. Note, this trace!
was added after evt.byteswap()
, but putting it before yields similar, definitely wrong, results.
from cyw43.
It makes it further from your fork, but I still get some sort of failure (though it's cryptic and possibly related to my probe)
from cyw43.
@chiefnoah, is it still panicing in the event handling?
If you provide the output I can try to understand what the problem is.
from cyw43.
No, it gets further. There's a bunch of IOCTL Response messages, but it ultimately fails with some sort of probe error that I've never seen before:
0.891802 INFO get clmload_status
0.892006 TRACE tx SdpcmHeader { len: 43, len_inv: 65492, sequence: 5, channel_and_flags: 0, next_length: 0, header_length: 12, wireless_flow_control: 0, bus_data_credit: 0, reserved: [0, 0] }
0.892048 TRACE CdcHeader { cmd: 262, len: 15, flags: 0, id: 6, status: 0 }
0.892097 TRACE [2b, 00, d4, ff, 05, 00, 00, 0c, 00, 00, 00, 00, 06, 01, 00, 00, 0f, 00, 00, 00, 00, 00, 06, 00, 00, 00, 00, 00, 63, 6c, 6d, 6c, 6f, 61, 64, 5f, 73, 74, 61, 74, 75, 73, 00, 00]
0.892967 TRACE rx [03, 01, fc, fe, 07, 00, 00, e4, 00, 16, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
0.893054 TRACE rx SdpcmHeader { len: 259, len_inv: 65276, sequence: 7, channel_and_flags: 0, next_length: 0, header_length: 228, wireless_flow_control: 0, bus_data_credit: 22, reserved: [0, 0] }
0.893104 TRACE CdcHeader { cmd: 262, len: 15, flags: 0, id: 6, status: 0 }
0.893145 INFO IOCTL Response: [00, 00, 00, 00, 6f, 61, 64, 5f, 73, 74, 61, 74, 75, 73, 00]
0.893261 INFO Configuring misc stuff...
0.897747 INFO set bus:txglom = [00, 00, 00, 00]
0.897916 TRACE tx SdpcmHeader { len: 92, len_inv: 65443, sequence: 6, channel_and_flags: 0, next_length: 0, header_length: 12, wireless_flow_control: 0, bus_data_credit: 0, reserved: [0, 0] }
0.897959 TRACE CdcHeader { cmd: 263, len: 64, flags: 2, id: 7, status: 0 }
0.898023 TRACE [5c, 00, a3, ff, 06, 00, 00, 0c, 00, 00, 00, 00, 07, 01, 00, 00, 40, 00, 00, 00, 02, 00, 07, 00, 00, 00, 00, 00, 62, 75, 73, 3a, 74, 78, 67, 6c, 6f, 6d, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
0.898621 TRACE rx [00, 01, ff, fe, 08, 00, 00, b0, 00, 17, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
0.898706 TRACE rx SdpcmHeader { len: 256, len_inv: 65279, sequence: 8, channel_and_flags: 0, next_length: 0, header_length: 176, wireless_flow_control: 0, bus_data_credit: 23, reserved: [0, 0] }
RTT error: Error communicating with probe: A core architecture specific error occured
────────────────────────────────────────────────────────────────────────────────
Error: A core architecture specific error occured
Caused by:
0: Failed to read register DRW at address 0x0000000c
1: An error specific to the selected architecture occured
2: Target device did not respond to request
```
from cyw43.
Could it be a power issue?
See rp-rs/rp2040-project-template#23
from cyw43.
"Error communicating with probe" is an error from probe-rs , not a panic from the firmware. I'm going to close this (also due to inactivity). If you see a panic please feel free to open a new issue with the stack trace.
from cyw43.
Related Issues (13)
- flip-link fails HOT 2
- Fail to initialize HT (High Throughput) PLL after embassy update HOT 3
- Any project related to MQTT or HTTP protocal? HOT 1
- Why spawner.spawn needed when wifi runner.run()? HOT 2
- No route to host HOT 2
- Support Bluetooth HOT 4
- Stuck on "Downloading CLM" HOT 1
- cyw43 fails to compile
- Missing `Default` implementation HOT 1
- Failing to connect (Pico W) HOT 7
- Issue since commit HOT 4
- fix README.md HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cyw43.