You just have to copy the pin definitions inside the file, inside this definitionheretop wrote: ↑Thu Jul 01, 2021 4:19 pmMay I confirm that you just overwrite the 2.0.0 core (PeripheralPins.c) with STM 1.9.0 core (PeripheralPins.c)? I did that but I got ...TFTLCDCyg wrote: ↑Thu Jul 01, 2021 4:06 pm I did a little exercise with the Nucleo F767ZI board, I copied all the pin definitions from the STM 1.9.0 core (PeripheralPins.c) and substituted it in the pin definitions from the STM 2.0.0 core (PeripheralPins.c), the NHD screen FT813 of 3.5 " now is answered without problems en el kernel 2.0.0 !!!!
Don't overwrite the whole file.#if! defined (CUSTOM_PERIPHERAL_PINS)
#include "Arduino.h"
#include "PeripheralPins.h"
/ * =====
* Notes:
* - The pins mentioned Px_y_ALTz are alternative possibilities which use other
* HW peripheral instances. You can use them the same way as any other "normal"
* pin (i.e. analogWrite (PA7_ALT1, 128);).
*
* - Commented lines are alternative possibilities which are not used per default.
* If you change them, you will have to know what you do
* =====
* /
// here is the field of replacement of pinout
#endif / *! CUSTOM_PERIPHERAL_PINS * /
With this I confirm my initial suspicion that the new 2.0.0 kernel has a different pin mapping than the 1.9.0 kernel.