DIY Cyton firmware upload: "No target found"

edited January 2022 in Build-it-yourself

I played the board according to the official PCB, but when I burned and uploaded the firmware, Copyright: (C) 2011-2015 Serge Vakulenko appeared
No target found.
2016-2017 Majenko Technologies
Programmer for Microchip PIC32 microcontrollers, Version 2.1.46
This is what questions are looking forward to answering

Comments

  • wjcroftwjcroft Mount Shasta, CA

    Have you loaded the firmware for the RFduino's (dongle and mainboard), before attempting to flash the PIC32?

  • @wjcrof
    No, I don't have one, so what I want to ask is how to upload the firmware to the board based on the original board, my dongle came with the Cyton board, I assembled this new cyton board myself, this board uses It is cyton's official PCB and bill of materials

  • @wjcrof
    I will add that the dongle is included with the Cyton board, I just made the cyton board according to the official PCB file, so the RFduino based on the dongle has firmware, and my own board does not have any firmware, how to put The original firmware is flashed, the traditional upload is through the serial port, should I use the serial port for burning?

  • wjcroftwjcroft Mount Shasta, CA

    You may want to examine other threads discussing the (Arduino oriented) serial port driven 'bootloader', which is pre-installed on the PIC32 during manufacturing.

    https://openbci.com/forum/index.php?p=/discussion/383/bootloader-issue-on-my-diy-32bit-clone-board
    https://www.google.com/search?as_q=pic32+bootloader&as_sitesearch=openbci.com

    I don't understand what hardware you have? You have built a DIY Cyton, but it has no RFduino on the mainboard, nor a dongle. But you have a separate Cyton+dongle purchased from the OpenBCI Store?? That dongle won't do you any good, since your DIY Cyton has no RFduino.

    During data streaming, the byte stream from the PIC32 is slightly manipulated by the two RFduino's. So if you are trying to talk to the PIC32 over direct serial port wires, you need to modify some aspects, such as the end byte / start byte. Additionally, the OpenBCI GUI assumes that certain command strings are supported directly by the RFduino's, such as to change the radio channels, status, etc.

  • @wjcrof
    I don't quite understand what you mean, two explanations:
    1. The problem of the dongle, the dongle was purchased from the OpenBCI mall together with the cyton board. Now I just want to make a cyton board by myself. I want to communicate with the original dongle because the dongle is in The dongle purchased in the mall is normal and has firmware. This cyton board is completely made according to the files provided by BCI. I guess the board can also communicate with the dongle.
    2. As shown
    I have RFD22301 on my board

  • wjcroftwjcroft Mount Shasta, CA

    OK, your original comments were unclear about what was OpenBCI store bought hardware, and what was your own build.

    You need to follow the exact sequencing given in this document to flash first the mainboard RFduino, then the dongle (which needs re-flashing after the pass-through firmware), then the PIC32:

    https://github.com/OpenBCI/OpenBCI_Cyton_Library/blob/master/UPGRADE_GUIDE.md#upgrading-to-200

    https://docs.openbci.com/Cyton/CytonRadios/
    https://docs.openbci.com/Cyton/CytonProgram/

  • wjcroftwjcroft Mount Shasta, CA
    edited January 2022

    @wjcroft said:
    You may want to examine other threads discussing the (Arduino oriented) serial port driven 'bootloader', which is pre-installed on the PIC32 during manufacturing.
    ...

    This bootloader IS NOT present on the PIC32 you have, but must be installed by yourself. By my earlier comment: "...pre-installed during manufacturing...", I was referring to OpenBCI manufacturing, not PIC32 Microchip manufacturing.

    https://www.google.com/search?q=PIC32+bootloader+chipkit

  • @wjcroft
    Thank you very much, if I have any questions I will keep in touch with you. Thanks again for sharing

  • @wjcroft
    Hi, can you please send me all the firmware codes I need, preferably with tutorials, because I'm a newbie and I'm feeling a little bit hard to get started now and I'm getting an error when uploading the RadioDevice32bit of the RFduino
    Here is the error code:
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp: In member function 'void OpenBCI_Radios_Class::configure(uint8_t, uint32_t)':
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp:101:17: error: 'class RFduinoGZLLClass' has no member named 'channel'
    RFduinoGZLL.channel = getChannelNumber();
    ^
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp: In member function 'void OpenBCI_Radios_Class::revertToPreviousChannelNumber()':
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp:254:15: error: 'class RFduinoGZLLClass' has no member named 'channel'
    RFduinoGZLL.channel = previousRadioChannel;
    ^
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp: In member function 'void OpenBCI_Radios_Class::printMessageToDriver(uint8_t)':
    C:\Users\uHear\Documents\Arduino\libraries\OpenBCI_Radios\OpenBCI_Radios.cpp:532:17: error: 'class RFduinoGZLLClass' has no member named 'channel'
    RFduinoGZLL.channel = getChannelNumber();

    My email is [email protected]

Sign In or Register to comment.