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.

SafeTI: SL_Init_Memory() does not accept ADC_RAMs as argument

Other Parts Discussed in Thread: HALCOGEN

According to TRM there is ADC modules in RM46&RM48, why SL_Init_Memory()-function does not accept them as argument? TRM table 2-7 does not specify anything special for those RAMs...

HALCoGen generated code performs ADC init via memoryInit()-function which actual execution related content is idential to SafeTI-version...

MIBSPI RAM has clear restriction in TRM, remark 4 in table 2-7 that modules has to be out of reset but SafeTI argument checker in SL_Init_Memory() doesn't check that one and code might end into endless waiting loop (tested this :)) but then at same time it prevents ADC usage which shouldn't have any restrictions and which works by using HalCoGen-generated-function - I am confused...


Secondary question: Is there any benefit to use internal memory initializer via SL_Init_Memory() or memoryInit() for MIBSPII (HALCoGen does re-initialize those modules) if according to TRM for SPIGCR0 says that SPI RAM init is always done when module is released from internal reset?

  • Hello Jarkko,

    I've forwarded your question to one of our SW leads and they or one of their team members should be able to get back to you shortly.
  • Hi Jarkko

    You are right, It's a feature missing in SL_Init_Memory() API of SafeTI Diagnostics Library(SDL), I raised a ticket (SDOCM00122888) to follow up on ADC support for Init memory, so that it is addressed in next SDL release.

    MIBSPI is a Special module which has this inbuild feature, So yes, to save time you need not do the memory Init as part of SL_Init_Memory() or memoryInit(). mibspiInit() function in HALCoGen will take care of it. Again it's up to the user application, if time budget is not a concern it's no harm in doing it though.