-
Notifications
You must be signed in to change notification settings - Fork 96
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
Not detecting any devices #56
Comments
We'll need way more information to be able to try and help you troubleshoot. Please review the entire FAQ and, if all that fails, provide the information as requested in FAQ item 8. |
The UART detection will only work on actively transmitting UART interfaces. Have you confirmed that the Wink UART interface is indeed sending data? You can try the UART Passthrough command with the JTAGulator connected to communicate directly with the Wink. See https://youtu.be/NWTNH1RgUZc?t=488 for UART functionality. You mention "We only get output while the device is starting up or in use." Can you clarify what you mean? I'm not clear if you're using the JTAGulator properly. Have you tried JTAG/SWD detection, as well? I don't see connectors soldered to those footprints. |
We have confirmed that the Wink UART interface is sending data. |
Since you know the UART pins of the Wink, have you tried the JTAGulator's UART passthrough mode to verify proper communication? Since you've tried with multiple JTAGulators, it's unlikely a hardware issue, but you can try to run through the test procedure to make sure: Test procedure and accompanying video Were these purchased directly from Parallax? Can you provide photos of the backsides?
OK, so are you saying the JTAGulator is working as expected, but just not with the Wink? Can you provide screenshots of the output? |
Closing due to no response. |
We have recently started using the JTAGULATOR to try to detect both UART and JTAG interfaces. We set up gnd pins to gnd on the JTAGULATOR and with both devices powered on it doesn't seem to ever detect anything. We are on version 1.11 and have tried connecting via screen command on kali and putty on windows. We only get output while the device is starting up or in use. This has also been an issue on multiple devices.
The text was updated successfully, but these errors were encountered: