PCAN Explorer 6 and STM32F429

This forum covers issues concerning multiple hardware products.
Post Reply
Embedded_Geek
Posts: 2
Joined: Sun 7. Mar 2021, 13:09

PCAN Explorer 6 and STM32F429

Post by Embedded_Geek » Sun 7. Mar 2021, 13:15

Hello,
I am using PCAN-FD USB, PCAN-Explorer 6 and STM32F429.
The following are my bit timing settings:
Clock = 42Mhz
Prescaler = 4
Baudrate = 500kbps
SJW = 1
TSEG1 = 16
TSEG2 = 4

But in PCAN Explorer I couldn't find 42Mhz as clock. I tried the other settings but unfortunately PCAN Explorer interprets the message as error frames.
Could you please give some hint to solve this issue?

Note: I already checked with logic analyzer that my MCU is transmitting.

Thanks in advance,
Embedded_Geek

User avatar
U.Wilhelm
Sales & Support
Sales & Support
Posts: 1262
Joined: Fri 10. Sep 2010, 19:34

Re: PCAN Explorer 6 and STM32F429

Post by U.Wilhelm » Mon 8. Mar 2021, 07:40

You need to calculate the Bitrate Setting for the PEAK-System Hardware so that it fit to the used board.
Which Sample Point does your board use ? This is very importend to know.
Simply use our Bitrate Calculation Tool to evaluate the best Setting ( link )
--------------------------------
PEAK-System Technik
Technical Support Team
support@peak-system.com
-------------------------------

Embedded_Geek
Posts: 2
Joined: Sun 7. Mar 2021, 13:09

Re: PCAN Explorer 6 and STM32F429

Post by Embedded_Geek » Mon 8. Mar 2021, 10:01

Thanks for the reply.
The issue is fixed. Below are the details so that others don't run to the same issue in future.
* The clock initialising function from ST (SPL) waits for HSE (external crstal oscillator) for a finite time. This time wasn't enough for the oscillator to startup therefore the default internal RC oscillator was activated. This led to change in the input clock to CAN hence it did not work.
* After I increased the waitime the HSE oscillator was up and I could communicate with PCAN Explorer as well as PCAN view without any effort.
Thanks Peak Team for the response and the amazing product...

Regards,
Embedded_Geek

Post Reply