Issue flashing to FED3

79 views
Skip to first unread message

Tim Sainburg

unread,
Dec 17, 2022, 4:42:17 PM12/17/22
to FEDforum
Hello,

I'm having trouble flashing to the FED3. I purchased my FED3 from OpenEphys a few weeks ago. 

The FED3 came with ClassicFed3 installed, and everything works nicely. I followed the instructions here to write a custom script, which is where I'm having trouble. 

When I plug the micro USB into the PCB, my computer does not see the USB, but it powers the board. When I plug the USB directly into the Adafruit Feather, my computer does see it. The board "Adafruit Feather M0 (SAMD21)" is recognized in port "/dev/tty/AMCM0 Serial Port USB". However, the board is only seen in certain modes. 
Specifically, the board is seen be the computer while in the "Select Program" screen, but if I let the selector go to "FR1", the Arduino IDE immediately switches over to "NO PORTS DISCOVERED" and `lsusb` no longer registers the device. If, instead, I choose "Free feeding" there is no such issue. So, while free feeding is selected, I tried flashing to the board. However, even with the board seen by the computer/Arduino IDE, I get the following message when I try to upload a script (here SetClock) "No device found on ttyACM0". 

I've tried this in both Arduino IDE 2.0.4 and 1.8.x. Same result in both cases. I am using Ubuntu 20.04

Can anyone assist? 

Thanks,
Tim

Tim Sainburg

unread,
Dec 17, 2022, 4:44:33 PM12/17/22
to FEDforum
You can ignore this, I just forgot to go into bootloader. 

Tim Sainburg

unread,
Dec 17, 2022, 5:09:55 PM12/17/22
to FEDforum
For posterity, if anyone comes across the following issue:

`error touching serial port /dev/ttyacm0 permission denied`

This seems to be some sort of default permissions error with ubuntu. This is the fix:

`sudo chmod a+rw /dev/ttyACM0`

Lex Kravitz

unread,
Dec 17, 2022, 5:15:59 PM12/17/22
to FEDforum
Thanks for posting back Tim!  I like to think that you wouldn't have figured that out if you hadn't posted here :) 

For anyone else who has this issue, you have to "double-click" the reset button the Adalogger to enter the bootloader mode to accept new code. See a video on common connectivity troubleshooting including how to do the "double-click" here.
Reply all
Reply to author
Forward
0 new messages