Closed wesmat closed 3 years ago
If you have a different data-capable USB cable, could you try that? Also, you have the USB cable connected from the Raspberry Pi to the 32U4 right?
I have tried 3 cables, all work for other data transfer situations. I have tried all 4 USB ports on the Pi with no luck.
On Mon, Jan 18, 2021 at 4:05 PM Zhiquan Yeo notifications@github.com wrote:
If you have a different data-capable USB cable, could you try that? Also, you have the USB cable connected from the Raspberry Pi to the 32U4 right?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wpilibsuite/frc-docs/issues/1110#issuecomment-762470276, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXMRFCBVRNQ4O6YIGM7DQ3S2SPC7ANCNFSM4WH2MWKA .
--
Wes Matchett
Database Administrator / FIRST Robotics
603-569-7181
www.brewsteracademy.org Celebrate 200 https://200.brewsteracademy.org Years With Us!
Couple of troubleshooting steps:
If this doesn't work, SSH into the pi (ssh pi@10.0.0.2
) and do ls -l /dev/tty*
to see if /dev/ttyACM0
is listed there.
Couple of worst case options:
pio run -t upload
from the firmware
folderInitially this did not work. I noticed that the Roma power switch was off. It was lit up and led 13 was flashing. I powered everything off, turned on the pi. The Romi has lights when the Pi is powered on. I SSH'd to the pi. The ttyACM0 dev was flipping from being there to not and the 'Update Firmware' button was also flipping. I turned the Romi power switch on. The tty dev stabilized. I was able to update.
Thanks for your help. I think the issue was the Romi power switch.
On Mon, Jan 18, 2021 at 4:49 PM Zhiquan Yeo notifications@github.com wrote:
Couple of troubleshooting steps:
- Unplug all USB cables from the Pi, and restart the Pi.
- Once it starts up again, verify that the Update Firmware button is NOT enabled
- Plug in the 32U4 to the Pi, and verify that the Update Firmware button is now enabled
If this doesn't work, SSH into the pi (ssh pi@10.0.0.2) and do ls -l /dev/tty* to see if /dev/ttyACM0 is listed there.
Couple of worst case options:
- Reimage the Pi and try it again
- Install PlatformIO on your computer, clone https://github.com/wpilibsuite/wpilib-ws-robot-romi and run pio run -t upload from the firmware folder
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wpilibsuite/frc-docs/issues/1110#issuecomment-762484883, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXMRFDE4XFTJ6R4T25FM5TS2SUFBANCNFSM4WH2MWKA .
--
Wes Matchett
Database Administrator / FIRST Robotics
603-569-7181
www.brewsteracademy.org Celebrate 200 https://200.brewsteracademy.org Years With Us!
Glad it's all worked out
When I attempt to image the 32U4 I get the following...
The cable is not the issue, I can access the board with the arduino API with no problems using the same cable.
Any ideas?