SPI issues that will be fixed in next JP release

This is extended topic from this one: Cannot process SPI Slave Communication In JP 6.0 - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums.
We decided to use our custom board as SPI Master, but there is minimum speed issue in JP 6.0 as I understand this topic: Jetson AGX Orin: Issues with minimum SPI speed and byte send order after update to Jetpack 6. It actually did on our Jetson AGX Orin, too.
May I ask if this minimum speed issue will be solved in next JP release, as slave issue does? Also, May I ask is there approximate schedule for release? Thanks.

Kind regards,
bi.min

Hi bi.min,

We are still working on the clock issue in SPI driver of JP6.

May I know what’s your requirement for SPI frequency?
Have you tried to configured it in device tree directly?

Hello KevinFFF.

We currently expect our peripheral device requires over 5 Mhz, so at now It couldn’t be problem.
But we also have possibility to communicate in lower speed (lower than 3 Mhz) so just wanted to know.

How can I configure it in device tree? I need to apply it as built image, so want to modify it in source as far as possible. Should this field needs to be configured?

spi-max-frequency = <50000000>;

Thanks.

This is 50MHz rather than 5MHz.

Do you mean that you want to use different SPI frequency on the same SPI interface?
It seems not the expected use case to me.

Since we function of best clock selection is removed since JP6, have you also verified with the latest JP5.1.3(R35.5.0)?

Do you mean that you want to use different SPI frequency on the same SPI interface?
It seems not the expected use case to me.

We didn’t exactly specified our peripheral to use, so we have another scenarios. If we choose other peripheral, we need to comunicate lower than 3 Mhz clock, so we apply lower communication speed in our software. In that case, JP6 SPI speed issue becomes problem - which it is not at this time though.

Since we function of best clock selection is removed since JP6, have you also verified with the latest JP5.1.3(R35.5.0)?

Yes, we verified at JP5.1.3. In that version, lower clock communication and slave function were all good. But we prefer JP6.0 due to some other reason.

This is 50MHz rather than 5MHz.

I actually thought this is a maximum frequency, so all freq lower than this value can be used by configuration. I’ll try it when I receive devkit (I don’t have it right now).

Thanks.

Is this still an issue to support? Any result can be shared?

We decided to use AGX Orin as 5 Mhz clock SPI master device, so I consider this issue solved at now. I’ll open another topic if we face this issue as problem again.
Thank you for your support.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.