Permalink
Browse files

EUSTM32F103RC - Delete legacy target.

1 parent 0bc7f51 commit 2dc546a481da00ca7d90da10c01b0b0ea98812d9 @hydra hydra committed with hydra Nov 19, 2016
Showing with 9 additions and 15 deletions.
  1. +4 −5 Makefile
  2. +1 −1 README.md
  3. +0 −1 docs/Boards.md
  4. +2 −6 docs/Spektrum bind.md
  5. +1 −1 src/main/drivers/pwm_mapping.c
  6. +1 −1 src/main/drivers/timer.c
View
@@ -38,7 +38,7 @@ FORKNAME = cleanflight
64K_TARGETS = CJMCU
128K_TARGETS = ALIENFLIGHTF1 CC3D NAZE RMDO SPRACINGF1OSD
-256K_TARGETS = ALIENFLIGHTF3 CHEBUZZF3 COLIBRI_RACE EUSTM32F103RC IRCFUSIONF3 LUX_RACE MOTOLAB PORT103R RCEXPLORERF3 SPARKY SPRACINGF3 SPRACINGF3EVO SPRACINGF3MINI STM32F3DISCOVERY SPRACINGF3OSD
+256K_TARGETS = ALIENFLIGHTF3 CHEBUZZF3 COLIBRI_RACE IRCFUSIONF3 LUX_RACE MOTOLAB PORT103R RCEXPLORERF3 SPARKY SPRACINGF3 SPRACINGF3EVO SPRACINGF3MINI STM32F3DISCOVERY SPRACINGF3OSD
F3_TARGETS = ALIENFLIGHTF3 CHEBUZZF3 COLIBRI_RACE IRCFUSIONF3 LUX_RACE MOTOLAB RCEXPLORERF3 RMDO SPARKY SPRACINGF3 SPRACINGF3EVO SPRACINGF3MINI STM32F3DISCOVERY SPRACINGF3OSD
@@ -122,8 +122,8 @@ ARCH_FLAGS = -mthumb -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingl
DEVICE_FLAGS = -DSTM32F303xC -DSTM32F303
TARGET_FLAGS = -D$(TARGET)
-else ifeq ($(TARGET),$(filter $(TARGET),EUSTM32F103RC PORT103R))
-# TARGETS: EUSTM32F103RC PORT103R
+else ifeq ($(TARGET),$(filter $(TARGET),PORT103R))
+# TARGETS: PORT103R
STDPERIPH_DIR = $(ROOT)/lib/main/STM32F10x_StdPeriph_Driver
@@ -428,7 +428,7 @@ NAZE_SRC = \
ALIENFLIGHTF1_SRC = $(NAZE_SRC)
-EUSTM32F103RC_SRC = \
+PORT103R_SRC = \
startup_stm32f10x_hd_gcc.S \
$(STM32F10x_COMMON_SRC) \
drivers/accgyro_adxl345.c \
@@ -464,7 +464,6 @@ EUSTM32F103RC_SRC = \
$(FC_COMMON_SRC) \
$(SYSTEM_SRC)
-PORT103R_SRC = $(EUSTM32F103RC_SRC)
CJMCU_SRC = \
startup_stm32f10x_md_gcc.S \
View
@@ -25,7 +25,7 @@ Cleanflight also has additional features not found in baseflight.
* Support for the TauLabs Sparky board (STM32F303, I2C sensors, based board with acc/gyro/compass and baro, ~$35).
* Support for the OpenPilot CC3D board (STM32F103, board, SPI acc/gyro, ~$20).
* Support for the CJMCU nano quadcopter board.
-* Support for developer breakout boards: (Port103R, EUSTM32F103RC, STM32F3Discovery).
+* Support for developer breakout boards: (Port103R, STM32F3Discovery).
* Support for more than 8 RC channels - (e.g. 16 Channels via FrSky X4RSB SBus).
* Support for N-Position switches via flexible channel ranges - not just 3 like baseflight or 3/6 in MultiWii.
* Lux's new PID (uses float values internally, resistant to looptime variation).
View
@@ -26,7 +26,6 @@ Cleanflight also runs on the following developer boards:
* STM32F3Discovery - Recommended for developers.
* Port103R - Recommended for F1 developers.
-* EUSTM32F103RB - Legacy.
There is also limited support for the following boards which may be removed due to lack of users or commercial availability.
@@ -2,7 +2,7 @@
Spektrum bind with hardware bind plug support.
-The Spektrum bind code is actually enabled for the NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY, CC3D, ALIENFLIGHTF1, ALIENFLIGHTF3 targets.
+The Spektrum bind code is enabled for most targets, some boards may not work due to SBus inverters. If you need Spektrum bind code ensure the board you are using specifically provides bind support.
## Configure the bind code
@@ -24,7 +24,7 @@ The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during bu
## Function
-The bind code will actually work for NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY targets (USART2) and CC3D target (USART3, flex port). The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Setting spektrum_sat_bind to zero will disable the bind mode in any case. The bind mode will only be activated after an power on or hard reset. Please refer to the table below for the different possible values.
+The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Setting spektrum_sat_bind to zero will disable the bind mode in any case. The bind mode will only be activated after an power on or hard reset. Please refer to the table below for the different possible values.
If the hardware bind plug is configured the bind mode will only be activated if the plug is set during the firmware start-up. The value of the spektrum_sat_bind parameter will be permanently preserved. The bind plug should be always removed for normal flying.
@@ -43,10 +43,6 @@ Please refer to the satellite receiver documentation for more details of the spe
| 9 | DSMX 2048bit/11ms | |
-### Supported Hardware
-
-NAZE, NAZE32PRO, CJMCU, SPARKY, EUSTM32F103RC, CC3D targets and ALIENWIIF1, ALIENWIIF3 targets with hardware bind plug
-
### Connecting a Spektrum-compatible satellite to a Flip32+ flight controller
The Flip32/Flip32+ is wired in a rather strange way, i.e. the dedicated connector for the satellite module uses the same UART pins as the USB adapter. This means that you can't use that connector as it maps to UART1 which you really shouldn't assign to SERIAL_RX as that will break USB functionality. (Looks this problem is fixed in later versions of the Flip32/Flip32+)
@@ -85,7 +85,7 @@ enum {
MAP_TO_SERVO_OUTPUT,
};
-#if defined(NAZE) || defined(NAZE32PRO) || defined(STM32F3DISCOVERY) || defined(EUSTM32F103RC) || defined(PORT103R) || defined(PORT103V)
+#if defined(NAZE) || defined(NAZE32PRO) || defined(STM32F3DISCOVERY) || defined(PORT103R) || defined(PORT103V)
static const uint16_t multiPPM[] = {
PWM1 | (MAP_TO_PPM_INPUT << 8), // PPM input
PWM9 | (MAP_TO_MOTOR_OUTPUT << 8), // Swap to servo if needed
@@ -42,7 +42,7 @@
TIM4 4 channels
*/
-#if defined(CJMCU) || defined(EUSTM32F103RC) || defined(NAZE) || defined(PORT103R)
+#if defined(CJMCU) || defined(NAZE) || defined(PORT103R)
const timerHardware_t timerHardware[USABLE_TIMER_CHANNEL_COUNT] = {
{ TIM2, GPIOA, Pin_0, TIM_Channel_1, TIM2_IRQn, 0, Mode_IPD}, // PWM1 - RC1
{ TIM2, GPIOA, Pin_1, TIM_Channel_2, TIM2_IRQn, 0, Mode_IPD}, // PWM2 - RC2

0 comments on commit 2dc546a

Please sign in to comment.