So despite being the color code for "Microcontrollers Port" the rgb is not on stm32 pin labels A8 C7 D7 (I assume those are arduino pin numbers?) They are actually on PK5 PK6 PK7 . Frustrating but ok. After getting the USBhs and external ram working in libopencm3 I started on spi but could get no response on the pins. Many hours spent. The gd pinout labels the spi pins as SPI1....But one of the schematic labels them as SPI2!(confirmed by datasheet, this info I coulda/shoulda checked) Also when showing the headers saying spi miso goes to spi miso..thats not helpful. The second schematic was even worse because next to all the pins on main mcu instead of it being "pin label / function" its just "pin label / pin label" why bother with the second column of same info? So just to make sure spi device/port was working I used a sketch with the stm pin names....it didnt work, I switched the pin defs to the arduino pin names and it did...Uhg this makes me think that possibly that one of the pins is mislabeled as well but its def from stm names to arduino is correct so im gonna go find that sumwhere hopefully easily in the variant folder. Just checked and variant seems to match pinout, The schematic shows clock at 27mhz, the variant 25mhz (my god why), ive been using clock settings based on 25mhz, I assume thats correct? The only place I could find the ulpi pinout was in cores/arduino/mbed/targets/TARGET_STM/TARGET_STM32H7/TARGET_STM32H747xI/TARGET_PORTENTA_H7/PinNames.h it states
USB_OTG_HS_ULPI_DIR = PC_2,
USB_OTG_HS_ULPI_NXT = PC_3,
But this is incorrect (or at least doesnt work for me) I use PH4 PI11 which does work, So where is arduino culling the real ulpi pin names? I see the USBHOST file has correct names, despite the name maybe it uses that for the usb device pinout? Anyway This has been very frustrating. The cynic in me wonders if this and the multiyear struggle to get bootloader code/info was done as a sorta vendor lockin making it harder to use non-arduino approved liibs/sdk's. But im tired, frustrated, and venting.
Hi @bm16ton. Thanks for reporting these errors.
The best way to get corrections made to content you find under the docs.arduino.cc domain, including the pinout diagrams and schematics, is to submit an issue or pull request to the repository where the content is maintained:
Please make sure to submit a separate issue for each of the distinct problem you found as this will make it easier for the project maintainers to ensure all the problems are resolved.
If you find an error in the core code such as the file you mention here, that should instead be reported or fix submitted to the repository where the core is maintained:
Give consideration to the philosophy of the wise man named Hanlon.
Ha you turned my horrible mood into a good one my good man with the hanlon link! Truely thank you my friend it was exactly what i needed! I was posting mostly to point it out to others who fall into it, and of course i apparently wanted to act like a middle school child, but i will send the appropriate info to the correct repos, thank you for finding those for me! Wish everyone online was like you. This was def the best/correct way to respond. Ill learn from how you responded, and hopefuly be better at responding to people because of it.