BLACK_F407ZET6 support

[uzi18]

Hi @fpistm
I want to add this board as PR, do You think it is enough to copy BLACK_F407VE and modify a little?
I think big difference is number of IOs.
On the market it is possible also to buy BLACK_F407ZG module (1MB of flash).

[fpistm]

Hi @uzi18
yes this could be enough.
making a diff btw PeripheralPins.c only some pins added:
https://github.com/stm32duino/Arduino_Tools/blob/master/src/genpinmap/Arduino/STM32F407V(E-G)Tx/PeripheralPins.c
https://github.com/stm32duino/Arduino_Tools/blob/master/src/genpinmap/Arduino/STM32F407Z(E-G)Tx/PeripheralPins.c

If the pin mapping is nearly the same, the variant could be updated using board define as differentiator.
I've made it for L496 and L496-P. Same for ldscript.

Arduino_Core_STM32/variants/NUCLEO_L496ZG/PeripheralPins.c

Line 111 in 7b48eff

#ifdef ARDUINO_NUCLEO_L496ZG

[uzi18]

thx, will check this out

[uzi18]

@fpistm ok looks like difference is very small but for STM32F407V(E-G)Tx/PeripherialPins.c vs variant Black_V407VG some lines are commented out, do you know why?

[fpistm]

Yes, this is commented in the header:

• Note: Commented lines are alternative possibilities which are not used per default.

•   If you change them, you will have to know what you do
  

To sum up, only one pin config is available. If you do not comment duplicated pins only the first occurence is used so second is never used and consume some space for nothing.

[BennehBoy]

@fpistm I have 2 of these boards on order so started to look at building a variant.

Although PeripheralPins.c could easily be done with defines, the actual pin layout on the board is very different to the BLACK407VET6.

The Variant.cpp file for BLACK407VET6 is laid out to represent the physical pin layout, accommodating the ZET6 here would necessitate either a) removing the physical layout altogether, or b) have a large ifdef section for each board.

Do you think it best to do one of the above, or break the ZET6 out into it's own unique variant folder?

[uzi18]

docs are here: https://github.com/mcauser/BLACK_F407ZE
BLACK_F407ZG is also available
in facts cpu is simmilar, but hardware onboard is different

[BennehBoy]

@uzi18 thanks - I think I have the hardware covered, my question is more about what is best practice for variants in STM core. The ZGT board looks identical other than the MCU used (with double the flash), so it ought to be pretty easy to include a variant.

[fpistm]

Do you think it best to do one of the above, or break the ZET6 out into it's own unique variant folder?

There is no specific rules. If thanks a switch it's simple to support it then update the current variant.
Else if too much diff a new variant can be created.

[uzi18]

@fpistm do you think it is possible to work with integrated sdcard slot, is sdio supported?

[fpistm]

Yes SDIO is supported thanks STM32SD and FatFs library. Works on Black F407VE.

[uzi18]

wow did not find any reference to STM32SD library, if also SPI will work, I will try W5500 ethernet ;)

[BennehBoy]

Yes SDIO is supported thanks STM32SD and FatFs library. Works on Black F407VE.

I've tested this.

SPI works just fine on the 407VET6, so no reason to think it won't on this.

I think for the sake of simplicity I'll remove the 'physical layout of the 407VET6, that way one variant should suffice for VET6/ZET6/ZGT6.

[uzi18]

It could be nice solution.
For fatfs did not find where to put files for STM32SD lib, it should be git submodule or something like that.

[fpistm]

@uzi18 those are libraries avalable thanks arduino library manager.
https://github.com/stm32duino/FatFs
https://github.com/stm32duino/STM32SD

@BennehBoy we talk about SD via SDIO not SPI ;)

[uzi18]

Have used to git clone libs, not manager itself ;)
I need also SPI for cheap W5500 ethernet module or maybe there is better alternative?