-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to communicate with CAN 500kbps #60
Comments
I'd start by verifying those. |
Your device receives some data as seen in the tool you use, but if you have a frame error, means you have data corruption. In 99.9% of the time, it is due to wrong clock. I'd say connect logic analyzer and inspect there. |
The clock must be right, cause of the UART is correctly working. I will change the frecuency of the FDCAN and check it with logic analyzer |
I have checked the clock in the eval kit and it is correctly set to 25MHz, also the analyzer is correct working with NXP eval kit, seems like something is not working correctly in the stack |
I have just check if there is a problem of my code, and there is the same behavior in your example for the stm32h7xxx. Please can you help me with this bug? For transmiting to the TXFIFO I need to change the TX Buffers Nbr to 8, if I dont change it the function HAL_FDCAN_AddMessageToTxFifoQ never sent nothing to the CAN bus |
Packets are going out - this you can see. Fact is that stack does try to send something, and it seems CAN IP sends out something too. |
I check that my clock for CANFD come from HSE (25MHz), is this clock correct?, also tomorrow I will check if logic analyzer told me something about the frames. |
I try to use the example demo with the eval kit stm32h7xx and it not works for me. I create a new project with RTOS with a Thread for the can_app_process().
I can see that the stack initialize correctly and sends data over the TX-FIFO. I configure the FD-CAN1 to 500kbps.
The code enters at HAL_FDCAN_AddMessageToTxFifoQ, but when I try to receive the data over the X-Analyzer I only receive error frames.
The text was updated successfully, but these errors were encountered: