cancel
Showing results for 
Search instead for 
Did you mean: 

FDCAN H7 BRS failure with Kvaser Leaf 3

LCE
Principal II

Heyho,

after some *** CAN beginner mistakes on my side, I got the FDCAN BRS 8 Mbit working.

Or so I thought. It's only working between my custom boards, as I found out after connecting a Kvaser Leaf v3.

With the Kvaser (directly connected to the board's D-sub, termination on, signals on the scope look good (enough)) and BRS on, it only works with max 2 Mbit, and only if the Kvaser's bit timing is set below 70% sampling point.

So far I played with changes to TDC, sampling point, SJW, and all bit timings (checked the Kvaser timing website).

Any ideas welcome!

8 REPLIES 8
mƎALLEm
ST Employee

So it's a "Kvaser" issue as FDCAN BRS 8 Mbit is working between your custom boards.

Did you remove the terminating resistor inside that Kvaser device? you need only two terminating resistors on the CAN lines.

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
LCE
Principal II

Thanks for the quick answer!

I only have the Kvaser connected to one of my boards.
The termination resistor is switchable on my boards (with an isolated low capacitance opto relay).

 

Do you confirm FDCAN is working well between the boards without that kvaser device?

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
LCE
Principal II

Do you confirm FDCAN is working well between the boards without that kvaser device?

Yes, at all bit rates.

Scope confirms bit timings.

I thought that the Kvaser stuff - coming from the market leader (I think) - is the impeccable reference.

So maybe I got something wrong?

Here's the CAN register settings for 8M (hex):

(for the segment times below the complete register, e.g. DTSEG1, the "+1" is already included)

FDCAN 1->
Clock = 80.000 MHz - PLL 1 Q
CREL = 32141218
ENDN = 87654321
DBTP = 00800521
        TDC = 1
        DBRP   = 1
        DTSEG1 = 6
        DTSEG2 = 3
        DSJW   = 2
NBTP = 24008A13
        NBRP   = 1
        NTSEG1 = 139
        NTSEG2 = 20
        NSJW   = 19
TEST = 00000080
RWD  = 00000000
CCCR = 00004300
        INIT = 0
        CCE  = 0
        ASM  = 0
        CSA  = 0
        CSR  = 0
        MON  = 0
        DAR  = 0
        TEST = 0
        FDOE = 1
        BRSE = 1
        PXHD = 0
        EFBI = 0
        TXP  = 1
        NISO = 0
TSCC = 00000001
TSCV = 0000BA51
TOCC = 0000FFFF
TOCV = 0000FFFF
ECR  = 00000000
PSR  = 0000070F
GFC  = 00000007

 


@LCE wrote:

Do you confirm FDCAN is working well between the boards without that kvaser device?

Yes, at all bit rates.


So that's not a STM32 issue, that's "kvaser" related one which I cannot help you on that.

Check again your kvaser device config, your wiring etc ..

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
mƎALLEm
ST Employee

A question: What is the clock source of PLL1Q? HSE?

Are you using a crystal?

If not, please use HSE as source clock for PLL1Q and use crystal (XTAL) or crystal oscillator (XO).

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
LCE
Principal II

HSE, ultra stable 10 ppm crystal

PTP running on that successfully, lots of timing relevant stuff in that application.

According to "Kvaser Leaf v3" specification, it can reach up to 8Mbit/s

mALLEm_0-1763383918831.png

So it should work.

Still not clear about the terminating resistor inside that device. Ensure that -if available- the internal terminating resistor on that kvaser device is disconnected.

What about the configuration of the tool: the bitrate the mode.. etc ?

Or raise a support ticket to kvaser over this link: https://kvaser.com/support/

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.