CO_app_STM32.c issue

[TheCitrusMan]

In the file CO_app_STM32.c I have an issue when enabling storage.

The function int canopen_app_resetCommunication() references to variable storageInitError, but this variable is not known in this context. Normally this does not cause any error during compilation because storage is disabled by default, but it does when #if (CO_CONFIG_STORAGE) & CO_CONFIG_STORAGE_ENABLE is true.

storageInitError is declared inside function int canopen_app_init(CANopenNodeSTM32 *_canopenNodeSTM32). This function calls canopen_app_resetCommunication() at the end, and that is the only location where this function is called. One way to fix this might be to merge functions canopen_app_init and canopen_app_resetCommunication. Another way could be to make variable storageInitError global within CO_app_STM32.c. Both have the same result but I cannot say if this is a proper fix.

[MaJerle]

@HamedJafarzadeh could you please check this?

[Brian9871]

I am currently using the STM32G0B1 for development and also enabled the storage function for saving RPDO and TPDO parameters.
For now, I temporarily resolved the issue by setting storageInitError as a global variable.
The parameters are currently being stored in the MCU’s internal flash memory, and everything seems to be working normally.

[TheCitrusMan]

I think I have my setup working now too. I also defined storageInitError global. After a bit of struggling with my eeprom drivers, I now have a solid green canopen LED 🙂 but only after writing "save" to object 0x1010 and rebooting...