Can the TL3238C achieve coexistence of BLE and Thread on the Matter over Thre...

we_6875975083

We are developing a Matter over Thread product on the TL3238 and have encountered an issue where BLE and 802.15.4 RF cannot operate concurrently. We would like to consult whether there is an officially supported RF library for concurrency or a recommended time-sharing scheme. Software stack: * Zephyr: Telink Zephyr branch tl3238x\_zephyr\_v1.0.3.0 (99b1ab86) * 802.15.4: Zephyr OpenThread driver * BLE controller: closed-source library lib\_zephyr\_tl323x.a (from tl\_ble\_sdk v4.0.4.5) Observed behavior: 1. When Thread is already joined and online, calls to the BLE advertising API return normally, but no BLE advertising packets can be captured over the air; advertising is not actually transmitted. 2. When a BLE connection has been established, restoring/restarting the Thread stack directly interrupts the BLE connection, and BLE cannot be maintained. Preliminary conclusion: the two protocol stacks share the same RF hardware. Under the current combination, once 802.15.4 occupies the RF, the BLE side is suppressed, and there is no arbitration/time-sharing mechanism. Questions: 1. Do the TL323x hardware and the existing SDK support RF-level concurrency between BLE and 802.15.4/Thread (similar to the scheduling mechanism in the legacy platform Zigbee/BLE Concurrent solution)? Is there a corresponding combined RF library or patch? 2. If concurrency is not supported, does the official side have a recommended time-division switching scheme (e.g., scheduling RF ownership based on connection events/Thread events) or a reference example? 3. Are future SDK versions planning to provide BLE/Thread coexistence support? Thank you!