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 - wrong generation of dcc.h

Other Parts Discussed in Thread: HALCOGEN

Dear all,

i have found few wrongly initialized symbolic constants in dcc.h generated by HALCoGen.

#define dcc1CNT1_CLKSRC_PLL1 0x0000A0000U
#define dcc1CNT1_CLKSRC_PLL2 0x0000A0001U
#define dcc1CNT1_CLKSRC_LFLPO 0x0000A0002U
#define dcc1CNT1_CLKSRC_HFLPO 0x0000A0003U
#define dcc1CNT1_CLKSRC_EXTCLKIN1 0x0000A0005U
#define dcc1CNT1_CLKSRC_EXTCLKIN2 0x0000A0006U
#define dcc1CNT1_CLKSRC_VCLK 0x0000A0008U
#define dcc1CNT1_CLKSRC_N2HET1_31 0x00005000FU
#define dcc2CNT0_CLKSRC_TCK 0x0000000AU
#define dcc2CNT0_CLKSRC_OSCIN 0x0000000FU
#define dcc2CNT1_CLKSRC_VCLK 0x0000A0008U
#define dcc2CNT1_CLKSRC_N2HET1_0 0x00005000FU

All of these definitions contain 9 hex digits, which is not the main problem, if the most significant bit is "0".

The main problem is in first 7 initializations. Fifth hex digit contains "A". That hex digin, according to your datasheet, is reserved, so there won't be any write in KEY bits, which is needed. So in all of these initializations should be fifth hex digit moved to fourth position to be written corectly.

I just wanted to highlight this error.

I'm using HALCoGen ver. 04.00.00.

Best regards, Jan

  • Hi Jan,

    I see a similar Ticket raised in HALCoGen Bug tracking system and It is commit to be fixed for 4.01.00 release. Thanks for pointing out, appreciate your post, you helped all HALCoGen user aware of this error.