-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wio-terminal Wi-Fi examples broken by #542 #628
Comments
Hello @pabigot, |
@lokiodin I haven't had a chance to get back to this yet. |
@pabigot Ok thanks. I will try to do something but as I a new in the embedded world ... |
I encountered the same bug. I used the debugger, and found that the reason was atsamd/boards/wio_terminal/src/wifi.rs Line 172 in 18cf7e9
But I'm not sure why this error happened since I don't know much knowledge about how this module works. |
@garasubo Awesome; thanks! That inspired me to try again, and I found a fix that's in #644. Could you point me to any information you can cite or provide on how to use a debugger on these boards? Ideally without having to modify the hardware to enable SWD, but if that's necessary I might be able to find somebody to do it. |
The SWD connector is available inside Wio Terminal case. I connected my Wio Terminal to Seeduino Xiao using FPC cable. You also need DAPLink for Xiao and openocd from here: https://github.com/ciniml/debug-tools-builder/releases |
@garasubo There are a couple things that might be going wrong. First, the Second, have you applied the Wi-Fi core firmware update? I happen to have some in-the-box Wio Terminals; if I take a fresh one and with the #647 branch run:
nothing happens. But if I go through the FWIW I'm using 2.1.2, which is the
|
Thanks. The FPC+various converters approach looks a little too fragile for me. I already have multiple SWD/JTAG-capable debuggers; the problem is accessing the signals. I'm going to try to find somebody who can short the jumpers as described here to bring the signals out to the Grove port. |
That was the reason. Thanks.
I agree with this, but it is relatively inexpensive and not super hard. Using SWD/J-TAG-capable debbuggers will be ideal if possible. |
Hmm, it seems still broken in debug build. Is it better to open a new issue for it? |
I think so, yes. |
@garasubo I don't think this is a bug. The connection to the RTL8720 has no flow control, so the Overflow error that causes a panic is legitimate. The example works if |
As noted in #604 (comment) the Wi-Fi examples for this target don't work; bisect narrows it down to 34ad122. Observable behavior is that as soon as interrupts are re-enabled after
wifi.enable()
everything goes dark.Between the board not supporting debugging without hardware modifications, and Rust blocking my normal dirty tricks to toggle LEDs without regard to safety, I don't expect to be able to solve this, but if somebody has suggestions I can test them.
The text was updated successfully, but these errors were encountered: