Cyton 'Failed to initialize board' error
Hello,
After successfully recording multiple sessions of data concurrently, I was not able to reconnect to the Cyton board, receiving the 'Failed to initialize board' error from the GUI. I noticed that the blue LED light was not consistently flashing ON (flickering in brightness depending on the orientation of the battery holder) when the board was switched to 'PC' mode. I replaced the batteries and that seemed to fix the issue with the LED, as it now flashed at full brightness as expected.
After attempting to reconnect the Cyton board, I received the same 'Failed to initialize board' error. I tried all of the following to no avail:
- Pressed RST pin to reset the Cyton board
- Used DMM to check input voltage from battery pack, which was suitable, at 5.8V within the 3-12V range. I assumed that the issue could have been due to the connection between the battery holder and the board being compromised, but the voltage was stable at 5.8V.
- Tried to set the Cyton board in bootloader mode by pressing RST+PROG, switching board ON, releasing RST then PROG. The board's blue LED did not flash as expected.
After attempting to diagnose the issue, I am simply unsure what the problem could be. Any suggestions are much appreciated!
Comments
I also wanted to note that I tried the 'manual' serial connect feature on OpenBCI GUI. Auto-scan fetched a message that reads, "Success. Cyton and Dongle are paired. Ready to start session!". After pressing 'Start session' shortly afterwards, I again received the 'Failed to initialize board' error.
After booting up the board this morning, the same issue occurred. But the blue on-board LED was fluctuating in brightness. I checked the input voltage at the JST pin and it was fluctuating along with the LED brightness. Eventually, the LED stabilizes at its typical brightness, and seemingly starts receiving a stable input voltage as well, around 5.8V. I am assuming there is an issue with the battery holder or connection between the holder and the board, which is causing the issues, and also preventing me from setting the board to bootloader mode.
For reference, here is the console log output where I launch the GUI, use the autoscan feature, connect to Cyton via COM3, then attempt to start session.
I have ruled out a battery issue for the time being, since I have attached a new JST connector and battery pack which I soldered which is providing the Cyton board with sufficient power, while the board still fetches a BOARD_NOT_READY_ERROR.
Upon looking into the Github repositories, I noticed that an issue was raised last year outlining the same error being seen in the console log. (https://github.com/OpenBCI/brainflow/issues/166)
The issue was closed without any detailed explanation as to what the reason behind the issue was though.
Nushaab, hi.
Sorry you are having this issue. Have you tried the AUTO-SCAN or SYSTEM STATUS buttons in the GUI Radio Configuration dialog? This would at least confirm that the two RFduino's (dongle and mainboard), are seeing each other consistently.
Also would suggest trying to use another computer, to eliminate any potential issues with USB interface or OS drivers. Be sure you have installed the FTDI drivers.
https://ftdichip.com/drivers/vcp-drivers/
If this still persists, I'd suggest emailing customer support at contact at openbci.com. They might have further tests or procedures you could try.
William
Thanks William, I've gone ahead and reached out to customer supports. Thanks for your suggestions.
I think we have same issue. Should we also call to customer support?
I would advise in doing so if you have tried the tips William had previously mentioned.
Thank you! I will.
I'm having this same problem with two different Cyton boards, a new one and one that I previously was able to connect to the GUI and get data (a month or so ago). Autoscan works fine for both, but I get a Failed to Initialize board error when I attempt to start a session. For both boards, I have tried (or successfully have) flashed my own firmware to record to the SD card using the PROG button. Could my firmware have changed something? Or do I have to update the GUI in some way?
If this is still running your modified firmware, it seems prudent to restore the default firmware to verify that the failure is not firmware related.
If your firmware worked with the GUI previously, you may also want to try another computer / different usb connection to rule out issues with the computer hardware.
William