Lost enabling OD storage

[WBakerOMS]

I have been going through the library exploring it's functionality and cannot seem to understand how to enable the storage mechanisms for the OD. I'm looking for OD values to persist between power cycles on my STM32F302 using the flash storage as NVM. I'm not using the provided example but have a working implementation of CanOpenSTM32 on a custom board.

My confusion begins with, throughout the library seeing a lot of CO_CONFIG_STORAGE & CO_CONFIG_STORAGE_ENABLE value checks that stop storage related code being compiled. CO_CONFIG_STORAGE_ENABLE has the default value of 0x01 from here, and CO_CONFIG_STORAGE is defined here so it looks like it should build the storage code. So my first question is why doesn't the storage code compile? Do I need to define something in my application (main.c)?

/**
 * Configuration of @ref CO_storage
 *
 * Possible flags, can be ORed:
 * - CO_CONFIG_STORAGE_ENABLE - Enable data storage
 */
#ifdef CO_DOXYGEN
#define CO_CONFIG_STORAGE (CO_CONFIG_STORAGE_ENABLE)
#endif
#define CO_CONFIG_STORAGE_ENABLE 0x01
/** @} */ /* CO_STACK_CONFIG_STORAGE */

/* default configuration, see CO_config.h */
#ifndef CO_CONFIG_STORAGE
#define CO_CONFIG_STORAGE (CO_CONFIG_STORAGE_ENABLE)
#endif

This brings up another question I have about Doxygen. As far as I have used it, Doxygen is a documentation generating/formatting tool. So, why are it's defines (CO_DOXYGEN) controlling what's being compiled in code, especially in CO_config.h?

I recognize that this code is at the CANOpenNode level and not the CANOpenSTM32 level, so I expect the need to write some application specific storage functionality. With the LSS config storage, callback functions are required. Is it a similar situation here and I just haven't found the right function yet?

I've been trying to look at the PIC32 example code that has the storage enabled but this also looks as if it's not compiling the storage components. Mind you I've never used a PIC before so may be reading it wrong.

[TheCitrusMan]

There's no actual storage code present in the CanopenNodeSTM32 implementation. You have to implement that yourself. I wrote my own code for use with an ST EEPROM, like the M24C64-U for instance, inspired on the driver that is present in the PIC32 version.

[TheCitrusMan]

This is my customized CanOpenNode_STM32 with EEPROM storage and hardware CRC calculation. There may be some remnants in the files from a project that I've been working on.

CanOpenNode_STM32_MV.zip

[TheCitrusMan]

Note that in my customized version I disabled the standard HAL generated FDCAN initialization and created a new function CO_FDCAN_Init() which is essentially a modified copy of the original init function but initializes the FDCAN interface with baud rate and node ID stored in SDO parameters. This function is called from a (also modified) function CO_CANmodule_init() in file CO_driver_STM32.c

[WBakerOMS]

Hey, thanks for shedding some light on the matter and sharing some code! I'll check it out

[CANopenNode]

@HamedJafarzadeh, @MaJerle, maybe at least CO_eeprom_STM32 files from the zip file could be added to the repository.

[CANopenNode]

Or, @TheCitrusMan, just fork the repository, add eeprom files and create a pull request.

[TheCitrusMan]

I would love to, but I'm not fluent enough with Github to do this 🫣
Whenever I need one of the files I just download them as a zip from github. On top of that, I reformatted all the source code to make it more readable (to me)... 😳

[TheCitrusMan]

EMPTY_PROJECT.zip

Here's a functional STM32G0B1 project that contains my latest EEPROM code (and the latest state of all my customization's, like hardware assisted CRC and parametrization of node ID and baud rate using SDO parameters). The code recognizes following EEPROMs:

• ST m24c32-u / m24c64-u / m24128-u / m24256-u / m24512-u / m24m01e-u / m24m02e-u
• Microchip 24AA256UID.

It uses the built in serial number of the device to set the Canopen serial number parameter.

This is a CMake project that I work on using Jetbrains CLion. There's also a STM32CubeIDE project present but that will likely not function.
Note that the formatting of all source files is "adjusted" to my preferences.

There was a GIT structure in the project that I removed because it contained the actual application code. CLion complains about that when I open the project...

I hope this helps...

[TheCitrusMan]

I'm currently figuring out using git and will try to create a new branch with the eeprom routines installed.

[TheCitrusMan]

Figured it out, see: https://github.com/CANopenNode/CanOpenSTM32/pull/109