AS this is CanopenNode based on the initial canopenNode implemented some years ago from
https://github.com/CANopenNode/CANopenNode, and as this previous repository is being developed improving new features and fixing bug, would it be possible to update this STM32 Repository from time to time?

I feel that we are missing a lot of good updates

David.-

Hello Andrii, i need to work with canopen library for a robotic application, unfortunately the main part of the project has been developped using HAL library and i don't have enough time to make CanOpenNode HAL compatible, do you succeed in this task?

Hello,

I have a little question regarding CAN peripheral HAL settings being erased by the driver (in CO_CANmodule_init() function).

The CAN peripheral is initialized in MX_CAN1_Init() function, see below :

However, it seems the peripheral settings are being re-written in the CO_CANmodule_init function, is this normal ?
Shouldn't the following lines be deleted to keep previous HAL settings actives ?

It's not causing problem here as the settings are the same but it caused be some problem because my HAL settings were not the same as you and were being erased by your config.

Thanks a lot.

In the line 363,

err =CO_CANmodule_init( CO->CANmodule[0], CANbaseAddress, CO_CANmodule_rxArray0, CO_RXCAN_NO_MSGS, CO_CANmodule_txArray0, CO_TXCAN_NO_MSGS, bitRate);

CANbaseAddress is an int whereas the function CO_CANmodule_init() takes a pointer as its second argument which creates the following error

"..\CANopen Src\CANopen.c(365): error: #167: argument of type "int32_t" is incompatible with parameter of type "CAN_HandleTypeDef *""

What's the recommended course of action? Modify the CO_CANmodule_init() or is there anything else to do?

Hello w1ne,

First of all thanks for your work. In the main loop of the programm, you call task_time_slice() function. However this is never defined, what is supposed to be the contents of this function ?

Regards,

Fszta