User Tools

Site Tools


openmicro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
openmicro [2018/01/13 00:01]
sirdomsen
openmicro [2020/02/24 17:03] (current)
fenrisulven
Line 1: Line 1:
  
  
-**CG023 firmware** (or OpenMicro which is the folder name Silver13 used) is going to have support for multiple different hardware platforms. Each copter has slightly different pin-outs, but with the right settings in the hardware.h file, it should be able to support some.+**Silverware** is going to have support for multiple different hardware platforms. Each copter has slightly different pin-outs, but with the right settings in the hardware.h file, it should be able to support some.
  
 For instructions on flashing a board with the STM32F0xx series processor, look at the bottom of this page. For instructions on flashing a board with the STM32F0xx series processor, look at the bottom of this page.
Line 7: Line 7:
 === Hardware support === === Hardware support ===
  
-If a copter uses supported chips, adding it to OpenMicro should really easy. <sortable>+If a copter uses supported chips, adding it to Silverware should really easy. 
 + 
 +<sortable>
  
 ^MCU^Supported| ^MCU^Supported|
Line 16: Line 18:
  
 </sortable> </sortable>
 +
 +<sortable>
  
 ^MPU^Supported| ^MPU^Supported|
Line 24: Line 28:
 |MPU-6052C|Yes| |MPU-6052C|Yes|
  
-</sortable> <sortable>+</sortable> 
 + 
 +<sortable>
  
 ^RX^Supported| ^RX^Supported|
Line 32: Line 38:
 |BK2453|Only syma x5c protocol, tested with devo only| |BK2453|Only syma x5c protocol, tested with devo only|
  
-</sortable> <sortable>+</sortable> 
 + 
 +<sortable>
  
 ^Protocols^Supported| ^Protocols^Supported|
Line 42: Line 50:
 |Bayang + telemetry|Yes - devo and multimodule| |Bayang + telemetry|Yes - devo and multimodule|
 |Q282|Yes| |Q282|Yes|
 +
 +</sortable>
  
 <sortable> <sortable>
  
-^Quad^H8 acro/dual^H101 acro/dual^CG023^Other^Notes| +^Copter^H8 acro/dual^H101 acro/dual^CG023^Other^Notes| 
-|Eachine/JJRC H8, green board|yes| | | | |+|Eachine/JJRC H8, green board|yes| | | |[[:h8mini|See the dedicated page]]|
 |Eachine H8 3D mini| | | |yes 3D([[https://github.com/silver13/H8_3D|code]])| | |Eachine H8 3D mini| | | |yes 3D([[https://github.com/silver13/H8_3D|code]])| |
 |Floureon H101| |yes| | | | |Floureon H101| |yes| | | |
 |Eachine H8S| |yes| | | | |Eachine H8S| |yes| | | |
 |Eachine CG023| | |yes| | | |Eachine CG023| | |yes| | |
-|Eachine/JJRC H8, blue board| | |yes|[[https://github.com/silver13/H8mini_blue_board|[1]]]|Keil Bug, solve it [[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|that way, ]]CLK/DAT swapped|+|Eachine/JJRC H8, blue board| | |yes|[[https://github.com/silver13/H8mini_blue_board|[1]]]| \\ Keil Bug, solve it [[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|that way, ]]CLK/DAT swapped \\  \\ [[:h8mini|See the dedicated page]] \\ |
 |GW008 Skull Quad| | | |yes, forum post| | |GW008 Skull Quad| | | |yes, forum post| |
 |DHD D1| | |[[https://www.rcgroups.com/forums/showpost.php?p=36580830&postcount=1756|info]]|[[https://github.com/silver13/d1|acro only]]| | |DHD D1| | |[[https://www.rcgroups.com/forums/showpost.php?p=36580830&postcount=1756|info]]|[[https://github.com/silver13/d1|acro only]]| |
Line 58: Line 68:
 |FQ777-124|yes ([[https://www.rcgroups.com/forums/showpost.php?p=36558530&postcount=7259|post]])| | | |[[https://github.com/bikemike/h8mini-testing/tree/fq777-124|bikemike's fork]]| |FQ777-124|yes ([[https://www.rcgroups.com/forums/showpost.php?p=36558530&postcount=7259|post]])| | | |[[https://github.com/bikemike/h8mini-testing/tree/fq777-124|bikemike's fork]]|
 |CX Model CX023|yes ([[https://www.rcgroups.com/forums/showthread.php?2512604-Eachine-H8-mini-acro-firmware/page545#post37060692|post)]] \\  and following| | | |[[https://github.com/bikemike/h8mini-testing/tree/fq777-124|bikemike's fork]] {{:wiki:hardware_cx023.h..zip|:wiki:hardware_cx023.h..zip}} | |CX Model CX023|yes ([[https://www.rcgroups.com/forums/showthread.php?2512604-Eachine-H8-mini-acro-firmware/page545#post37060692|post)]] \\  and following| | | |[[https://github.com/bikemike/h8mini-testing/tree/fq777-124|bikemike's fork]] {{:wiki:hardware_cx023.h..zip|:wiki:hardware_cx023.h..zip}} |
-|[[:bwhoop|Boldclash Bwhoop B-03]]| | | |[[https://github.com/silver13/BoldClash-BWHOOP-B-03/|Github]]|No alt holdKeil Bug, solve it [[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|that way,]]|+|[[:bwhoop|Boldclash Bwhoop B-03+B03 pro]]| | | |[[https://github.com/silver13/BoldClash-BWHOOP-B-03/|Github]]|[[:bwhoop_ah|Alt hold supported]] using [[https://github.com/silver13/BoldClash-BWHOOP-B-03/tree/AH|this branch]]. \\  Keil Bug, solve it [[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|that way]]|
 |[[http://sirdomsen.diskstation.me/dokuwiki/doku.php?id=e011|Eachine E011]]| | | |[[https://github.com/silver13/Eachine-E011|Github]]|[[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|flashing instructions]]| |[[http://sirdomsen.diskstation.me/dokuwiki/doku.php?id=e011|Eachine E011]]| | | |[[https://github.com/silver13/Eachine-E011|Github]]|[[https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995|flashing instructions]]|
 +|Furibee H801|yes| | |[[https://github.com/silver13/BoldClash-BWHOOP-B-03/|Github]]|same as BWHOOP, identical boards|
  
 </sortable> </sortable>
Line 68: Line 79:
  
 ^Copter^MCU^MPU^RX^Pinout^Supported^Notes| ^Copter^MCU^MPU^RX^Pinout^Supported^Notes|
- +^DHD D1^STM32F031K4^M540^XN297^-^[[https://github.com/silver13/d1|https://github.com/silver13/]][[https://github.com/silver13/d1|d1]][[https://www.rcgroups.com/forums/showpost.php?p=36580830&postcount=1756|info]]^onboard vreg turned on by cpu|
-]]| +
- +
-|DHD D1|STM32F031K4|M540|XN297|-|[[https://github.com/silver13/d1|Beta]][[https://www.rcgroups.com/forums/showpost.php?p=36580830&postcount=1756|info]]|onboard vreg turned on by cpu|+
 |Eachine H8 (Blue board)|STM32F030F4P6|M688|XN297LBW| |Yes ([[https://github.com/silver13/H8mini_blue_board|*]])|unusual radio ic, 3wire spi (bi-directional)| |Eachine H8 (Blue board)|STM32F030F4P6|M688|XN297LBW| |Yes ([[https://github.com/silver13/H8mini_blue_board|*]])|unusual radio ic, 3wire spi (bi-directional)|
 |M9912|STM32F031K4| |XN297|[[http://static.rcgroups.net/forums/attachments/4/7/0/8/6/1/a9255237-208-9912.JPG|Here]]|[[https://github.com/stawel/CG023/commit/4549a1e76ed24513d88a580df774b8c51c2039d9|Maybe]][[http://www.rcgroups.com/forums/showpost.php?p=35485543&postcount=889|Yes]]|[[:mt9912|MT9912]]| |M9912|STM32F031K4| |XN297|[[http://static.rcgroups.net/forums/attachments/4/7/0/8/6/1/a9255237-208-9912.JPG|Here]]|[[https://github.com/stawel/CG023/commit/4549a1e76ed24513d88a580df774b8c51c2039d9|Maybe]][[http://www.rcgroups.com/forums/showpost.php?p=35485543&postcount=889|Yes]]|[[:mt9912|MT9912]]|
Line 83: Line 91:
 |FQ777-124 (Red)|GD32F130G6| | | |[[https://www.rcgroups.com/forums/showpost.php?p=36558530&postcount=7259|Forum Post]]|PCB 'SF123R2.4 V1.2| |FQ777-124 (Red)|GD32F130G6| | | |[[https://www.rcgroups.com/forums/showpost.php?p=36558530&postcount=7259|Forum Post]]|PCB 'SF123R2.4 V1.2|
 |Fayee FY804|STM32F031K4| |XN297| |May be same as D1|see D1 link above| |Fayee FY804|STM32F031K4| |XN297| |May be same as D1|see D1 link above|
-|Fayee FY805|STM32F031K4| |XN297| |Yes|[[https://www.rcgroups.com/forums/showthread.php?2512604-Eachine-H8-mini-acro-firmware/page805#post38540867|Forum Post]]|+|Fayee FY805|GD32F130K6| |XN297| |Yes|[[https://www.rcgroups.com/forums/showthread.php?2512604-Eachine-H8-mini-acro-firmware/page805#post38540867|Forum Post]]hexa board|
 |DM003|STM32F031K4| |XN297|[[http://static.rcgroups.net/forums/attachments/4/7/0/8/6/1/a9209496-248-DM003%20pinouts.JPG|Here]]|Yes|[[https://www.rcgroups.com/forums/showthread.php?t=2634611&page=46#post35358892|Forum Post]]| |DM003|STM32F031K4| |XN297|[[http://static.rcgroups.net/forums/attachments/4/7/0/8/6/1/a9209496-248-DM003%20pinouts.JPG|Here]]|Yes|[[https://www.rcgroups.com/forums/showthread.php?t=2634611&page=46#post35358892|Forum Post]]|
 |DM007|STM32F031K4| |XN297| |Yes|[[https://github.com/silver13/H8mini_blue_board|Forum Post ]]| |DM007|STM32F031K4| |XN297| |Yes|[[https://github.com/silver13/H8mini_blue_board|Forum Post ]]|
Line 129: Line 137:
 Before flashing, the hardware.h file must be configured to assign the correct pins to the processor for the board you are going to flash. There are instructions at the top of the hardware.h file. For an example of how to set up the LED's, read [[http://www.rcgroups.com/forums/showpost.php?p=35509671&postcount=916|this post.]] Before flashing, the hardware.h file must be configured to assign the correct pins to the processor for the board you are going to flash. There are instructions at the top of the hardware.h file. For an example of how to set up the LED's, read [[http://www.rcgroups.com/forums/showpost.php?p=35509671&postcount=916|this post.]]
  
-Since different quads have different pins of the main processor assigned to different functions (motors, LED's, gyro), silvverxxx made the code configurable. Of course, the default settings are for a CG023 and nothing has to be done for a CG023. This is only for if you want to flash a quad that uses an STM32F031 processor and it isn't a CG023.+Since different quads have different pins of the main processor assigned to different functions (motors, LED's, gyro), silvverxxx made the code configurable. Of course, the default settings are for another Copter and nothing has to be done for a natively supported copter. This is only for if you want to flash a quad that uses an STM32F031 processor and it isn't a natively supported one.
  
 First you need to trace the pcb and find out what pins of the processor go to the gyro, the LED's and the motors. This is not easy on some pcb's as the traces can go from the top side to the bottom side through tiny copper tubes called vias. Other boards are easier and can sometimes be traced just from close-up pics on the internet. First you need to trace the pcb and find out what pins of the processor go to the gyro, the LED's and the motors. This is not easy on some pcb's as the traces can go from the top side to the bottom side through tiny copper tubes called vias. Other boards are easier and can sometimes be traced just from close-up pics on the internet.
openmicro.1515798063.txt.gz · Last modified: 2018/01/13 00:01 by sirdomsen