Found out that our issues were caused just by bad timings. Default ones fitted stm32f4 168 MHz, but were not good for stm32f7 216 MHz.
For some reason I wrongly thought that NuttX CAN driver calculate best Phase_Seg1 and Phase_Seg2 itself, like for example it is done in libuavcan https://github.com/PX4/libuavcan/blob/52e7ce09907bcec8a0b93e7a15d5fbd121c686dc/libuavcan_drivers/stm32/driver/src/uc_stm32_can.cpp#L195 ср, 22 июл. 2020 г. в 11:29, Oleg Evseev <ev.m...@gmail.com>: > Hi Ben, > > Yes, I mean native internal stm32f7 CAN controller RX, TX connected to CAN > phy chip (SN65HVD230 in our case). > We have no problems with stm32f4, but can't get it working with stm32f7 > yet - mcu sends something to TX, but CAN analyzers do not see any messages > on CAN bus. > > ср, 22 июл. 2020 г. в 10:54, Disruptive Solutions < > disruptivesolution...@gmail.com>: > >> Oleg do you mean the SPI version (mcp) or native with a say tja1050? The >> SPI version I use on different platforms. The stm32f7 I have to try >> though... >> >> Ben >> >> Op di 21 jul. 2020 23:06 schreef Oleg Evseev <ev.m...@gmail.com>: >> >> > Hi all, >> > >> > Did anybody use the NuttX CAN driver with stm32f7 mcu? Does it work ok? >> > >> > --- >> > With regards, Oleg. >> > >> >
