No data after firmware update -> chipKIT core issue

CJPCJP
edited March 2018 in Cyton
Hi all,

We have a OpenBCI 32bit board which we bought in 2015. Yesterday we updated the firmware following the steps given in tutorials. First Device->host->board. But after the update board is not streaming data. We then downgraded to the old firmware, but the problem remains the same. I am attaching a screen shots of the Openbci python screen when I start the stream with the 1.XX firmware. The error was same for the new firmware too.  
 

Anyone know whats happening here?

Really appreciate your help. 

Thank you,
Chamika. 
«1

Comments

  • wjcroftwjcroft Mount Shasta, CA
    Chamika, is there any difference when running the Cyton with the OpenBCI_GUI? Have you made sure that dongle and Cyton are on the same radio channel? The GUI has user interface buttons to control the radio channels,


    Mentioning AJ @pushtheworld.

    William

  • Hi William,

    Thank you very much for your replay.

    OpenBCI GUI seems to have a problem of connecting with the board. It outputs a error saying "Error reading from the serial port, Try different one" . I am attaching a screenshot of the terminal and gui window when this happens. The story was same for the new firmware too.

    https://ibb.co/gu6EOH

    Chamika.
  • wjcroftwjcroft Mount Shasta, CA
    Are the latest FTDI drivers installed? Have you tried another laptop, to eliminate the possibility of an OS serial port issue?

  • CJPCJP
    edited February 2018
    FTDI driver is up to date, I will check the board with a another computer ASAP. But I tried it with my windows and Linux OSs but the result is same. 
  • I flashed the latest firmware again and now the serial connection is ok in GUI. But still no data from the sensors or the accelerometers.
  • wjcroftwjcroft Mount Shasta, CA
    AJ @pushtheworld, do you have any suggestions?
  • KCDTylerKCDTyler Melbourne, Australia
    edited February 2018
    Hi,

    I tried to update firmware earlier today, and now also find the same problem. 

    The serial connection seems to be ok, and the radio configuration reports 'Success:System is up', but there is absolutely no data streaming: the .txt files that are saved are just a bunch of zeros. 

    Any help much appreciated.

    Cheers,




  • wjcroftwjcroft Mount Shasta, CA
    AJ @pushtheworld, two Cyton owners are now reporting no data streaming after upgrading to the latest firmware. And @KCDTyler mentions the .txt file output is being written by the GUI, but contains all zeros. Does that mean a stream is being received, but is all zeros?

    KCD, do you see the dongle lights flickering (radio data coming in) when you try your test? That might say that the Cyton IS streaming data, but that the data is all zeros.

    William

  • KCDTylerKCDTyler Melbourne, Australia
    Hi William,

    When streaming, the dongle shows both a blue led, and a red led light. Neither are flickering. I am pretty sure that the red was not showing, when streaming prior to this attempted firmware upgrade. 

    Also, when doing the firmware upgrade and selecting serial port on the Arduino IDE, tools>port>dev/etc there was only the dev/cu.usb serial option, no dev/tty.usb serial option. Could this have anything to do with it?

    I noticed that the tutorial stated to use stated to use dev/tty.usbserial-DN00nnnn  serial port for firmware upgrades, however the picture in the tutorial showed use of the dev/cu.usb ## port. I was hoping that this was ok. 

    Cheers,
    Kaelasha
  • wjcroftwjcroft Mount Shasta, CA
    edited February 2018
    The cu and tty devices on Mac are 'almost' the same thing; commented on that other thread. 'tty' just blocks on the open call until device is online. 'cu' will open if when no serial device is present. I guess the GUI was switched over to cu recently.

  • As I remember, There was a solid red on TX led when streaming. Its same after the firmware update. Solid red on TX LED when I start the stream. 
  • edited February 2018
    Same thing here.
    Yesterday, I carefully followed the instructions to update the firmware to the latest version, and now I don't get any signal from the sensors anymore.
    I checked the radio channel on the OpenBCI GUI ("Success: Host and Device on Channel number: 1"), tried both dev/tty.usbserial and dev/cu/usb.serial.
    The GUI doesn't initialize if I select 16 channels ("unable to attach daisy"), even though the Daisy is correctly plugged in. I have to select only 8 channels for the UI to be rendered.
    When I start streaming, the TXD led is solid red. Data is recorded, but all values are 0.
    Everything was working fine just before the update.
  • After discussing the issue with AJ @pushtheworld, he suggested that I should retry and issue a soft reset. There was no error during upload, but the output of the v command (from the Arduino serial console) is as follow:

    OpenBCI V3 8-16 channel
    On Board ADS1299 Device ID: 0x00
    LIS3DH Device ID: 0x00
    Firmware: v3.1.0
    $$$
    No ID can be found for the board or the accelerometer. No electric shock happened during the upload. I reverted to the 2.x firmware, but still no luck:

    OpenBCI V3 8-16 channel
    On Board ADS1299 Device ID: 0x0
    LIS3DH Device ID: 0x00
    Firmware: v2.0.1
    $$$
    @CJP, @KCDTyler, do you experience the same?
  • @wjcroft

    The user still has the choice of in regards to "I guess the GUI was switched over to cu recently."
  • Hey I'm tracking this issue with @mesca over in the NeurotechX slack, seems like some problem with the SPI comms happened to the board because we can see the no ID. I'm not fimilar with this issue.

    @KCDTyler do you think you could try using the serial terminal in the arduino to send a v (just a single 'v') and report back here with what the result is?
  • @mesca


    yes its the same. 

    ⸮I V3 8-16 channel
    On Board ADS1299 Device ID: 0x00
    LIS3DH Device ID: 0x00
    Firmware: v3.1.0
    $$$


    I went back to the 1.xx firmware earlier but the output was all zeros.But  I can't remember about the IDs in 1.XX firmware
  • @CJP is having the same issue as @mesca as i can see from the screen shots.... what the heck is going on with these
  • edited February 2018
    As far as i know, people have been using the latest firmware with no issue, i wonder what version of arduino this subset of people are using to upload the code. Maybe there is a problem with either the latest chipkit and arduino?

    @CJP, @mesca, @KCDTyler what version of arduino did you use to upload the code? I use 1.8.5.
  • Latest version of Arduino (1.8.5).
  • Which chip kit core did you download? I see a major update of the chip kit core was released on 11 Feb 2018, that is a biggg red flag for me!

    Why don't y'all try using the 1.3.1 version of the chipkit core instead of the 2.0.1 version.

    https://chipkit.net/wiki/index.php?title=ChipKIT_core#1.29_Auto_install_via_URL_from_within_Arduino_IDE_.28latest_version_chipKIT-core_v1.3.1.29
  • I had no idea a new major version of the chip kit core was released so I have a feeling this is where the problem is coming from, expecially because the firmware that you re-uploaded (v2.0.1) does not work when you uploaded it again.
  • WoooHooooo yeeeeeee I see DATA :D 

    used chipkit 1.3.1

    Thank you very much @pushtheworld @mesca and @KDCTyler .. 

    May be the firmware update wiki should be updated. Anyone know how to suggest the edit to admins ?
  • Yeah! Can't try right now, but will confirm tonight.
  • edited February 2018
    @CJP you can make edits on github!

    https://github.com/OpenBCI/Docs/edit/master/Hardware/05-Cyton_Board_Programming_Tutorial.md

    All you need to do is make the change and I can approve it!
  • @pushtheworld ;

    I suggested a edit via github, Check whether I did the right thing . .
  • @CJP I am not seeing the pull request, did you change the text and then suggest a pull request?

    Thanks so much for your help!
  • @pushtheworld 

    I'm sorry. I'm new to github apart from downloading the .zip files :D .. 
    i think I sent you the pull request now. 
  • edited February 2018
    Downgrading to chipkit 1.3.1 worked! Thank you @pushtheworld
  • KCDTylerKCDTyler Melbourne, Australia
    Hallelujah! I see data! Downgrading to chipkit 1.3.1 appears to have solved the problem. Thanks so much for the help!
Sign In or Register to comment.