Differences between Disco and non-Disco version

[AussieMakerGeek]

Hi, I'm just wondering if there are any major differences between the versions? I know pin assignments are different and there is a limit on the AIN devices but is there any firm reason or preference for the non-disco version in terms of performance or features?

I have an STM32F407VGT6 'minimal' development board (Not actual discovery board) and I loaded the non-Disco version onto it, but it fails to detect via USB, I tried the disco version on a whim and it detects fine.

This is odd to me, since the USB pins should not change.

a) Is there any obvious/expected reason for this to happen?
b) if I just stick with the Disco version is this likely to cause issues later?

[Ultrawipf]

The disco version does not use the vbus detect pin while the normal one does to detect if it is connected via usb or not.
Many devboards do not use this feature so it is disabled in the disco version and if the normal one is flashed it will not connect via usb if the pin is not high.

[AussieMakerGeek]

Thanks for the reply. So that means, if I want to use the non-disco firmware, I just have to pull PA9 high, since my device will only ever be bus powered and it should work right?

Or, am I over complicating things needlessly and should just use the disco firmware? Which was point b of my question - is there any reason to favour one over the other?

[Ultrawipf]

In theory yes but check if the additionally used pins in the full firmware are actually fine to use on your board and not connected to existing hardware.
The disco version is supposed to be compatible with the discovery board which contains a bunch of extra parts that block pins.
The normal firmware is designed for the official FFBoard with its connectors and other integrated components like the CAN transceiver and leds.

[AussieMakerGeek]

Perfect. My dev board is very bare-bones. It has no other components like flash, SD card etc. There is only a button and a led, both of which I can disable if I have to, so i'll look at getting the general version going.

I'm only looking at doing a basic PWM wheel so the likes of CAN are not needed for my application but I feel like to future-proof it, staying away from the disco release is probably a better option.

[AussieMakerGeek]

Just to add for reference
I managed to get the non-disco firmware working fine on my board, which is a diymore STM32F407VGT6

Considerations
Remove the user LED on PE0 (and the associated resistor) - Not essential but this is shared with the OpenFFBoard firmware and is inverted logic
Wire PA9 to 3.3v as per above (just make sure the board is only powered from USB)
Boot0/1 pins are inverted logic from OpenFFBoard - Short BOOT1 and BOOT0 for normal mode, remove BOOT0 jumper to enter DFU mode.

I just used a NC momentary switch on BOOT0 and soldered a bridge on BOOT1

For a simple PWM wheel with no special features, it works fine.