Hi,
If I don't want the multibuffer feature for SPI1/3/5 I now can check a seperate checkbox in HalCoGen. But if I do this the bit0 (=MSPIENA) in MIBSPIE register stays set.
I'm not sure if this is a bug or a feature?
Thanks
BR
Christian
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
If I don't want the multibuffer feature for SPI1/3/5 I now can check a seperate checkbox in HalCoGen. But if I do this the bit0 (=MSPIENA) in MIBSPIE register stays set.
I'm not sure if this is a bug or a feature?
Thanks
BR
Christian
Christian,
Your question has been forwarded to Halcogen team. They will reply you shortly.
Thanks and regards,
Zhaohong
Hi
Sorry for the confusion. It's a Bug in HALCogen, MIBSPIE register is used during startup where we initialize the MIBSPI RAM, and was not reverted back.
Please do not select the "Memory Built in self test / Memory parity Self check" for MIBSPI 1 / 2/ 3 in SAFETY INIT tab if MIBSPI driver is not selected.
Regards
Prathap
Hello Oliver,
I think this is not possible with HALCoGen 3.03. I've found the checkboxes to choose compatibility mode only in version 3.04 (but then with the bug explained in my first post).
Currently I'm using version 3.04 and activate the compatibilty mode manually after the call to spiInit(). This works for me. Here is my function to do this (in file spi.c):
/* USER CODE BEGIN (27) */
void spiDisableMultiBufferMode(mibspiBASE_t *spi)
{
spi->MIBSPIE &= ~0x00000001;
}
/* USER CODE END */
Best Regards
Christian