Clarification of actual features on RT1062

Site Feedback
1

Hey OpenMV,

I’m feeling a little annoyed right now after trying to get SPI to work on an RT1062 board.

Although it’s a problem I am sure I will overcome, I feel this way because the way the board is advertised on the website is as a 60Mbp/s, highly SPI capable board (alongside UART and I2C etc), yet looking closer into the documentation, all but UART require Master mode only, and, all do not use the standard documentation and MicroPython implementation (pyb conflict), instead having to use the far less documented machine.SPI class instead.

Perhaps if the website could be updated to reflect some of these actual realities a little better, it might be clearer for customers. I can understand that many of these features are still being worked upon, but if they don’t work when I purchase the board it now requires more troubleshooting, debugging and time to the purchaser to fix later.

Overall though, the RT has been very effective at everything else and a lot of fun to work with, thank you!
Cheers.

2

Hi Class-ab,

So, the pyb module is only for the stm32 boards, and it’s deprecated. The machine module replaced it long ago.

For the mimxrt, we support CAN, I2C master/slave, UART, and SPI master. No micropython board except STM32 boards supports SPI slave mode right now. It’s a feature we have asked Damien to add upstream: OpenMV Features · GitHub

We hope that SPI slave support will be added soon. However, yes, at the moment it doesn’t exist. This has been an issue for a while.

The board docs are clear on every bus. I think you might have gotten tripped up with the pyb module as it’s deprecated… and has been for many years, but has yet to be deleted on STM32. After SPI slave mode is merged, maybe Damien should do this, as we’ve been pushing to get the machine module up to spec for a while now and it’s almost ready to replace pyb.

https://docs.openmv.io/v5.0.0/openmvcam/quickref/openmv-rt1062.html