where is the QSPI CS# Pin is used QSPI library

[ykn]

hi,

this is the first time i have used QSPI library, I have to use external flash in QSPI mode.

In the data sheet it is given that, CS# pin should be low until command instruction 16bit data will pass. as shown ablove.

but when executing command the CS# Pin perform HIGH-LOW_HIGH and again did the same thing at the timing of writing. this should not happen. asper data it low at command insertion and data writing.

ihave check ON CRO.

my question where is the CS# micro, so that i can manage to write.

i know this could be stupid question.

thanking you.

 if (HAL_QSPI_Command(&QSPIHandle, &s_command, HAL_QPSI_TIMEOUT_DEFAULT_VALUE) != HAL_OK)
	 {
	 return QSPI_ERROR;
	 }

[Tesla DeLorean]

It's controlled properly/directly by the Peripheral, and via the AF setting of the associated pin.

The data sheet would list those pins usable for this.

The CS would be held low for Data transfer if you've got some DataMode and NbBytes set in the device instance (QSPIHandle), and you subsequently issue a HAL_QSPI_Receive()

Note that you can have a more open-ended/protracted transaction using the HAL_QSPI_AutoPolling() function, which waits for specific conditions in the read data to be met, and then dumps the CS

There's probably a section in the Reference Manual on this..

[ykn]

i have search all the code, but i dint see any CS# low micro.

and there is no such thing in reference manual.

please provide if you got this.

thanking you.

[Tesla DeLorean]

The questions lose something in translation

Some aspects controlled in configuration

 hQspi->Init.ChipSelectHighTime = QSPI_CS_HIGH_TIME_4_CYCLE; /* Min 50ns required after non Read command */

 hQspi->Init.ClockMode     = QSPI_CLOCK_MODE_0;

 hQspi->Init.FlashID      = QSPI_FLASH_ID_1;      /* Default value at start, can be changed dynamically using BSP_QSPI_SetFlashID() */

The peripheral owns the pin control

 /* QSPI BK1 CS GPIO pin configuration */

 gpio_init_structure.Pin    = QSPI_BK1_CS_PIN;

 gpio_init_structure.Pull   = GPIO_PULLUP;

 gpio_init_structure.Alternate = QSPI_BK1_CS_PIN_AF;

 HAL_GPIO_Init(QSPI_BK1_CS_GPIO_PORT, &gpio_init_structure);

These setting use by HAL_QSPI_Command and HAL_QSPI_Receive/Transmit ultimately determine how the peripheral holds the NCS signal. Normal behaviour is NCS drops at the beginning of the command dispatch, and then raises it at the end of the data transaction.

 s_command.AddressSize    = QSPI_ADDRESS_32_BITS;

 s_command.AlternateBytes = 4; 

s_command.DummyCycles   = 8;

s_command.NbData      = Size;

It is not a GPIO you can control manually, it is driven by the peripheral's state-machine, based on settings/parameters configured.