Behaviour of DDE_xxx_read if DDE changes

Hi,

I’m witnessing the following behaviour:

  1. I use the DDE_xxx_read function to process configuration changes. Works fine.
  2. I added a parameter to a config block in the DDE and installed it on the DUT
  3. The DUT has no uplink connection (on purpose) and can’t receive a configuration from the backend
  4. The DDE_xxx_read function now fails with return code -1 stating “C1 size mismatch, expected 6 but got 4 bytes …”

So is my assumption correct that:

  1. The “old” configuration prior to when I changed the DDE is still in place, because the DUT had no uplink to synchronize
  2. The DDE_xxx_read function fails and doesn’t modify o : [DDE_xxxCfg]
  3. In such a case the default values for config parameters in the DDE are not used

If those assumption are correct it would mean that default values for configuration need to be defined in the DLO directly in order to handle cases where the DDE_xxx_read function fails. Am I correct?

And the last question consequently: In which cases are the default config values from the DDE applied?