![]() The datasheet that shows that PD14 is used for SPI CS not only contradicts what you are saying - twice - but also does not match the definitions in the stm32 peripherals.c file - they cannot both be correct! Why can you not understand or accept this? ![]() I don't see how quoting other datasheets that DON'T show something is justification for STILL arguing about the datasheet that DOES show the correct and working pinout. Honestly, I really don't know why this not work on your side. I remember your comment on an issue when you told: So, yes - "I guess to read the wrong datasheet" - but it is you that is reading the wrong datasheet, not me! I never told a regression can occur anyway this is not the case. Our answers were correct and when I said it has been tested since a while this is correct. Please, note that the PeripheralPins.c is generated automatically thanks the MCU XML description file from STM32CubeMX, as you can see below there is no CS capabilities.Īnyway those XML files can have an issue but is rare, in our case the Nucleo datasheet is not correct.Īnd here is a screenshot (again) that proves your answer wrong "SPI has been tested since a while and as mentioned by PD14 has no SPI capabilities" The fact it works with PD14 doesn't means this is an HW CS just it is used as an SW CS. I will raise an issue internally to fix the Nucleo datasheet. You can check by yourself:Ībout the Nucleo datasheet, you are right, this is mentioned anyway looking to the MCU datasheet, there is no SPI CS: My reference to it which clearly shows your answer to be incorrect seems to have been removed - is there any reason for that? I gave you the link to the datasheet I used. If you met an issue with SPI, I guess it could comes from the fact the PA7 is shared with Ethernet RMII so if you use Ethernet and SPI at the same time this would failed. SPI has been tested since a while and as mentioned by PD14 has no SPI capabilities. It seems strange you are able to get MOSI=21 or D22: where 21 would be PC1 and D22 is PB5 morover PB_5 is commented in the original file. The pinmap_pin() extracts the first one found. SSEL=15 or D20 -> pinName PA_15 is equal to 0x05 where GPIO port A (0x0) and GPIO pin (0x5) -> pinNumber PA15 = 20 SCLK=19 or D23 -> pinName PB_3 is equal to 0x13 where GPIO port B (0x1) and GPIO pin (0x3) -> pinNumber PB3 = 23 MISO=43 or D46 -> pinName PC_11 is equal to 0x21 where GPIO port C (0x2) and GPIO pin (0x1) -> pinNumber PC11 = 46 MOSI=21 or D22 -> pinName PC_12 is equal to 0x22 where GPIO port C (0x2) and GPIO pin (0x2) -> pinNumber PC12 = 21 SSEL=4 or D24 -> PinName PA_4 is equal to 0x04 where GPIO port A (0x0) and GPIO pin 4 (0x4) -> pinNumber PA4 = 24 SCLK=5 or D13 -> PinName PA_5 is equal to 0x05 where GPIO port A (0x0) and GPIO pin 5 (0x5) -> pinNumber PA5 = 13 MISO=6 or D12 -> PinName PA_6 is equal to 0x06 where GPIO port A (0x0) and GPIO pin 6 (0圆) -> pinNumber PA6 = 12 MOSI=7 or D11 -> pinName PA_7 is equal to 0x07 where GPIO port A (0x0) and GPIO pin 7 (0x7) -> pinNumber PA7 = 11 Thanks also check on my side and there is no issue with the default definition. With my defintions, the output is as follows: printf( " \nPIN assignments for SPI3 \n ") printf( " \nPIN assignments for SPI1 \n ") Open serial communications and wait for port to open: printf( "SSEL=%d or D%d \n ",x, pinNametoDigitalPin(x)) ![]() X= pinmap_pin(peripheral,PinMap_SPI_SSEL) printf( "SCLK=%d or D%d \n ",x, pinNametoDigitalPin(x)) X= pinmap_pin(peripheral,PinMap_SPI_SCLK) printf( "MISO=%d or D%d \n ",x, pinNametoDigitalPin(x)) X= pinmap_pin(peripheral,PinMap_SPI_MISO) printf( "MOSI=%d or D%d \n ",x, pinNametoDigitalPin(x)) X= pinmap_pin(peripheral,PinMap_SPI_MOSI) You don’t need to use/buy external debug probe.Īrduino Wiring-based Framework allows writing cross-platform software to control devices attached to a wide range of Arduino boards to create all kinds of creative coding, interactive objects, spaces or physical experiences.// If you omit these the results are total garbage const PinMap PinMap_SPI_MOSI = , ST Nucleo F429ZI has on-board debug probe and IS READY for debugging. You can switch between debugging Tools & Debug Probes usingĭebug_tool option in “platformio.ini” (Project Configuration File). Instructions and configuration information. Please click on compatible debug tool below for the further You will need to install debug tool drivers depending on your system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |