I did a layout for an STM32F405RG that I was going to flash with SilF4ware, an F4 port of SilverWare. I ended up with a mixture of an FC suitable for the AlienFlight F4 target in BetaFlight and Silf4ware that can be custom configured to an extent in Cube MX. This is what happens with a little knowledge
The way that I connected the gyro was exactly the same as the AlienFlight F4 and as far as I am aware there is no way of re configuring these actual hardware connections in Cube to match my PCB’s. Some Pins I could move in Cube as the code is bit banged so I have quite a bit of flexibility to move about half the pins but the others forget it. To complicate thing this FC uses the MPU-6000 whereas the AFF4 uses the noisy MPU-6500 but I have been told that the code should work for both gyros as long as I am not using any Mag or Baro functions which I am not, plus I do not think that my 6000 has that capability anyway.
On this SilverF4 layout , I have the motors on PC6 - PC9 (Pins 37 - 40) which are CH’s 1 - 4 on TIMER4
My question is can I remap these in the CLI in BetaFlight so I can at least use this board as a derivative design of the AlienFlight F4 that has three UART’s and SP13 (four pins) broken out to pads on the board.
To double complicate thing I am having very sporadic connection via serial and when trying to put into DFU. It has connected, accepted a few different firmwares and gone into DFU but not reliably so I think that I need to rework the STM.