Still no joy, this time the error shows the following. did a clean installation of Arduino v1.5.8 and copied the OpenBCI RFduino folder into the package contents as instructed on the Radios programming page. Tested flashing to RFDuino on Sierra MacOsx as well. If you can provide a Gdrive link or email me at: t3kn0mage gmail (dot) com, that would be most appreciated, thanks! I'd like to request if anyone here could provide me with a pre-compiled firmware hex (for RFduino) that I can try burning to my board using RFDLoader directly (i.e., via Command/Terminal), instead of doing it through Arduino's Compile/Upload process. I can only hope I havent bricked its radio section somehow.Īnyway, I'm curious to know if anyone here has experienced something similar to the issues I've described above?Īlso.
Rf toolbox bci code#
But after I uploaded the test code to my RFduino, its radio operations have stopped working and I am unable to detect using any scanner now.
Rf toolbox bci android#
and I was able to detect the RFduino using a BLE device scanner on Android (you can do the same with NRF's Connect/Toolbox as well). Once that line is executed, it's like the RFduino goes into a hang/loop and any successive operations are ignored or not executed, irrespective of whether they are non-BLE or not.ītw, this can't be a problem with the device itself because when I first tested it out with the stock firmware it arrived with, the LED lit up successfully and blinked during its initial advertising on startup. For e.g., during the RFDuino's initialization, I can get the LED on pin 3 to light up in setup() but only before RFduinoBLE.begin() is called. Now, what I mean by my partial success here is this: any non-BLE section of the code works absolutely fine UNTIL the function RFduinoBLE.begin() is called inside setup(). but thanks to Roman's modified RFDLoader.exe which he has graciously provided, I replaced the original exe and when I attempted to upload the code to the RFduino via FTDI, I was able to do so (somewhat) successfully.
Rf toolbox bci windows#
Much thanks to for his windows solution above! Initially, I did face the very same fail error on Win as well. I'm sure it's not an issue with the wires being loose or incorrectly connected in any way, because surprise surprise! On Windows, I am able to upload the same code successfully to the RFduino from my PC. Despite all the detailed instructions and precautions, I still get this error on Mac, which is a bit surprising to me: RFduino device required for RFduino hex fileĪn error occurred while uploading the sketch Besides that, I paid caution to all the wire connections from the FTDI board to the corresponding RFduino's pins (FT-Tx to RF-Rx, FT-Rx to RF-Tx, FT-DTR to RF-RST through a 0.1uF cap) as described on the Cyton Radio Programming page, as well as other RFduino project pages scattered across the net.
the only modification I made was to add an LED to the RFduino's GPIO3, so that I can see if there's any response from the RFDuino on startup.
The arduino test code I used is from one of the RFduinoBLE examples. I've followed all the instructions on installing the RFDuino board into Arduino, as well as the required libraries into the respective locations for both OSs. Currently, I'm testing out the RFduinos standalone before I commit them to the Cyton & Dongle boards I got printed.
and this is happening on MacOSx, and partially on Win8.1 as well (and I'll explain what I mean by the partial issue further below). I'm experiencing a similar issue with uploading the compiled hex to my RFDuino too.
0 kommentar(er)
