S32KのトピックRe: S32K344 LPSPI cs is active too long

S32K344 LPSPI cs is active too long

esmax — Mon, 29 May 2023 11:35:44 GMT

Hello. I am trying to work with SPI but have a problem . SPI transmission is too long. CS stays in active state after data is transferred.

SPI configuration :

Has anyone encountered such behavior?

Re: S32K344 LPSPI cs is active too long

VaneB — Wed, 31 May 2023 17:32:21 GMT

Hi @esmax

Continuous Transfer configures to "keep PCS asserted between frames (as configured by FRAMESZ). A new command word is required to cause PCS to negate. Also supports changing the command word at the frame size boundaries."

If you disable continuous transfer you have the same behavior?

B.R.

VaneB

Re: S32K344 LPSPI cs is active too long

esmax — Thu, 01 Jun 2023 06:59:21 GMT

Hello @VaneB . Thank you for the reply.

When I disable continuous transfer I have this timings.

but I need CS to be active during transferring all 3 bytes.

I have similar project and SPI configuration is the same but another behavior of CS.

Re: S32K344 LPSPI cs is active too long

VaneB — Thu, 01 Jun 2023 17:44:29 GMT

Hi @esmax

The platform should behave similarly by having the same LPSPI configuration so that the problem may be due to the implementation.

Could you tell me the differences in your projects to verify if this is the reason?

Re: S32K344 LPSPI cs is active too long

esmax — Fri, 02 Jun 2023 05:57:13 GMT

Actually there are no differences. I read SPI registers during debug. They look correct.

LPSPI_2/SR, 0x40360014, 0x00000001
LPSPI_2/CFGR0, 0x40360020, 0x00000000
LPSPI_2/CFGR1, 0x40360024, 0x00000001
LPSPI_2/CCR, 0x40360040, 0x27270000
LPSPI_2/CCR1, 0x40360044, 0xFF800303

According to datasheet there are no any SPI registers that can affect SPI behavior. Am I right ?

It is written that write operation to CCR register overwrites CCR1 but there is no information how CCR1 can be calculated.

Re: S32K344 LPSPI cs is active too long

VaneB — Fri, 02 Jun 2023 21:07:39 GMT

Hi @esmax

As I mentioned before the platform should behave similarly if it used the same LPSPI configuration for both projects.

I would like to know if you are using an EVB or a custom board. If you are testing each project on a different board. I would like to discard all possible causes of the problem.

Re: S32K344 LPSPI cs is active too long

esmax — Sat, 03 Jun 2023 08:04:49 GMT

I am using the same hardware

Re: S32K344 LPSPI cs is active too long

VaneB — Mon, 05 Jun 2023 17:30:12 GMT

Hi @esmax

Since you are using the same hardware and the same LPSPI configuration in both projects, what must be generating this difference in CS behavior could be another module.

Could you help me with information regarding what other modules each project uses or if you want you can create a case in which you can share your projects with us so we can carry out tests.

Re: S32K344 LPSPI cs is active too long

esmax — Tue, 13 Jun 2023 09:31:55 GMT

Hello.

I use for the tests next code.

I do not change the code . Just size of buffers. As you can see I set up two buffers for transmission. They will be sent during one sequence.

When the size of buffers equal to 1 I have a delay between transferring data and disabling CS is around 15 uS

When the size of buffers is 2 bytes a delay between transferring data and disabling CS is around 12 uS

When the size of buffers is 3 bytes a delay between transferring data and disabling CS is around 1 uS

When the size of buffers is 4 bytes a delay between transferring data and disabling CS is around 11 uS

When the size of buffers is 5 bytes a delay between transferring data and disabling CS is around 2.5 uS

When size of buffers 6 and 7 bytes, delays are the same as for 5 bytes length buffers.

Could you please tell me what can be a reason of such weird behavior of SPI ?

Re: S32K344 LPSPI cs is active too long

VaneB — Thu, 15 Jun 2023 20:30:29 GMT

Hi @esmax

Could you verify if you have the same behavior with the example SPI_Transfer_S32K344 or Lpspi_Flexio_Ip_Transfer_S32K344?

Also, I notice that your clock is not symmetric, could you share an oscilloscope image of this?