This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HALCOGEN: Bug in code generation for CAN initial config values.

Part Number: HALCOGEN

Tool/software:

Dear,

I was just implementing register readbacks for the CAN interfaces when I noticed the following:

void can1GetConfigValue(can_config_reg_t *config_reg, config_value_type_t type)
{
    if (type == InitialValue)
    {
        config_reg->CONFIG_CTL     = CAN1_CTL_CONFIGVALUE;    
        config_reg->CONFIG_ES      = CAN1_ES_CONFIGVALUE;     
        config_reg->CONFIG_BTR     = CAN1_BTR_CONFIGVALUE;    
        config_reg->CONFIG_TEST    = CAN1_TEST_CONFIGVALUE;   
        config_reg->CONFIG_ABOTR   = CAN1_ABOTR_CONFIGVALUE;  
        config_reg->CONFIG_INTMUX0 = CAN1_INTMUX0_CONFIGVALUE;
        config_reg->CONFIG_INTMUX1 = CAN1_INTMUX2_CONFIGVALUE;
        config_reg->CONFIG_INTMUX2 = CAN1_INTMUX2_CONFIGVALUE;
        config_reg->CONFIG_INTMUX3 = CAN1_INTMUX3_CONFIGVALUE;
        config_reg->CONFIG_TIOC    = CAN1_TIOC_CONFIGVALUE;   
        config_reg->CONFIG_RIOC    = CAN1_RIOC_CONFIGVALUE;    
    }
    else

The line

        config_reg->CONFIG_INTMUX1 = CAN1_INTMUX2_CONFIGVALUE;
appears to be defective here. I assume it should be:
        config_reg->CONFIG_INTMUX1 = CAN1_INTMUX1_CONFIGVALUE;
This happens for all interfaces. This naturally makes the readback fail. Can you confirm this is a bug?
HALCoGen is version 04.07.01
Best regards