Hi there,
Thank you for taking your time to help me.
You were right and indeed the clocks weren't enabled. Below you can find the HAL_CAN_MspInit function. Now regarding the GPIO_SPEED_HIGH which is defined as GPIO_SPEED_FREQ_VERY_HIGH ((uint32_t)0x00000003) (high speed) I'm wondering which speed exactly is being set.
After calling this function I still can't see any messages in PCAN view.
UPDATE#1:
After some digging I found out that the speed should be set to something in the range of 50-200Mhz, it's the fastest after all. I can't find the exact value though.
UPDATE#2:
When I connect another CAN node controlled by Arduino with a CAN shield (MCP25xx chips, https://botland.com.pl/en/arduino-shield-communication/11568-can-bus-shield-v20-shield-for-arduino.html) it frezees the stm HAL can.
UPDATE#3:
After enabling the software BUS-OFF management (hcan1.Init.ABOM = ENABLE) it no longer freezes and very, VERY rarely I can see that PEAK picks up some new messages. At least that's something. Nevertheless the messages IDs are wrong and in some places the data as well.
I'm not entirely sure but this may be connected to how the mailboxes are maintained by the software. Before even connecting the Arduino CANbus shield I had troubles with sending and/or reading more than 3 different IDs.
UPDATE#4:
I was wrong before and this is getting even weirder. I still can't see messages from stm32 HAL CAN. But in some way the CAN node(s) from stm32 are affecting what I send from Arduino CANbus shield. This results in receiving some new messages with slightly changed ID carrying the same data as messages sent originally by Arduino. From what I can see they show up at completely random time. It's hard to explain really.
For example if 0x65 is the original message ID that is being sent from Arduino PCANview also shows 0x525 and 0x565 IDs with the same content. Meanwhile the only messages I send from HAL CAN are with IDs: 0x460, 0x470, 0x480 which, of course, don't show up (please refer to the attached image, messages with high counts are original).
I'm almost certain that is has something to do with bit timing..
static int CAN1_CLK_ENABLED=0;
void HAL_CAN_MspInit(CAN_HandleTypeDef* hcan)
{
GPIO_InitTypeDef GPIO_InitStruct;
if(hcan->Instance==CAN1)
{
/* USER CODE BEGIN CAN1_MspInit 0 */
/* USER CODE END CAN1_MspInit 0 */
/* Peripheral clock enable */
CAN1_CLK_ENABLED++;
if(CAN1_CLK_ENABLED==1){
__CAN1_CLK_ENABLE();
}
/**CAN1 GPIO Configuration
PA11 ------> CAN1_RX
PA12 ------> CAN1_TX
*/
GPIO_InitStruct.Pin = GPIO_PIN_11|GPIO_PIN_12;
GPIO_InitStruct.Mode = GPIO_MODE_AF_PP;
GPIO_InitStruct.Pull = GPIO_NOPULL;
GPIO_InitStruct.Speed = GPIO_SPEED_HIGH;
GPIO_InitStruct.Alternate = GPIO_AF9_CAN1;
HAL_GPIO_Init(GPIOA, &GPIO_InitStruct);
/* USER CODE BEGIN CAN1_MspInit 1 */
/* USER CODE END CAN1_MspInit 1 */
}
else if(hcan->Instance==CAN2)
{
/* USER CODE BEGIN CAN2_MspInit 0 */
/* USER CODE END CAN2_MspInit 0 */
/* Peripheral clock enable */
__CAN2_CLK_ENABLE();
CAN1_CLK_ENABLED++;
if(CAN1_CLK_ENABLED==1){
__CAN1_CLK_ENABLE();
}
/**CAN2 GPIO Configuration
PB12 ------> CAN2_RX
PB13 ------> CAN2_TX
*/
GPIO_InitStruct.Pin = GPIO_PIN_12|GPIO_PIN_13;
GPIO_InitStruct.Mode = GPIO_MODE_AF_PP;
GPIO_InitStruct.Pull = GPIO_NOPULL;
GPIO_InitStruct.Speed = GPIO_SPEED_HIGH;
GPIO_InitStruct.Alternate = GPIO_AF9_CAN2;
HAL_GPIO_Init(GPIOB, &GPIO_InitStruct);
/* USER CODE BEGIN CAN2_MspInit 1 */
/* USER CODE END CAN2_MspInit 1 */
}
}