HALCOGEN: Project migration

Hi Koichiro,

To migrate from RM4x to RM4y, normally I modify device family name and device part number in the *.hcg and *.dil files manually with a text editor.

But to migrate from RM4x to RM5x, this way doesn't work. It's easier to create a new HAL project for RM5x and select the same config options using for RM4x.

Hi QJ,

When customer selects RM57L843ZWT in HalCoGen, there is no "SAFETY INIT" tab, so selftest codes(sys_selftest.h, sys_selftest.c) are not generated.
These tab and codes are available for RM46L852PGE.
Are there any specification changes made between these devices?
If so, could you clarify these changes?

Thanks and regards,
Koichiro Tashiro

QJ,

Could you provide answer as below priority? #1 is highest.
1) Why "SAFETY INIT" tab is missing for RM57L?
2) How to generate selftest codes for RM57L?
3) others

Thanks and regards,
Koichiro Tashiro

Hi Koichiro-San,

For RM57x and TMS570LCx, we suggest to use the example in SafeTI Diagnostic Library. 

Hi QJ,

Could you clarify below points?
- SAFETY codes are not supported by HalCoGen for RM57x?
- How to port selftest codes to RM57?

QJ Wang said:

For RM57x and TMS570LCx, we suggest to use the example in SafeTI Diagnostic Library.

Do you mean SafeTI diagnostic library contains similar selftest codes HalCoGen generates for RM46x?
Customer wants to use the same selftest codes they used in RM46x for RM57x as well.

Thanks and regards,
Koichiro Tashiro

Hi Koichiro-San,

Yes. SafeTI Diagnostic Library provides similar self-test APIs.

Hi QJ,

I am afraid you do not understand customer’s problem clearly.

Customer used RM46x before and made their code by HalCoGen.
Now he is planning to use RM57x for new product and wants to port an old RM46x codes to RM57x.
He wants to reuse the old software as much as possible.

He tried to make RM57x codes from HalCoGen based on RM46x HalCoGen configuration(GUI setting).
But as we already discussed, “SAFETY INIT” tab does not exist for RM57x, so he cannot make self-test code from HalCoGen.

Questions:
1) It is not possible to make self-test code for RM57x by HalCoGen?
If not, are there any other ways to make such codes for RM57x?
In other words, how other customers make self-test codes for RM57x?

2) You mentioned customer can use SafeTI Diagnostic Library.
As the old self-test codes were automatically generated by HalCoGen,
it is not clear for customer how each HalCoGen GUI settings are related to generated codes.
It is not possible for customer to make the similar self-test codes from Diagnostic Library without knowing above.
Does each GUI setting correspond to each API provided by Diagnostic Library?

Thanks and regards,
Koichiro Tashiro

Hi QJ,

The customer needs to port the project in a hurry, so he is asking more specific questions.
Please answer below questions.

1) He is considering how to port AfterSTC() function in sys_startup.c which is generated for RM46 to RM57.
Inside AfterSTC(), sub routines in sys_selftest.c are called.
He wonders there are any reasons AfterSTC() is not necessary for RM57.
For example, other parts of codes generated by HalCoGen does the same operation, etc.
If so, he does not port AfterSTC() to RM57.

2) If it is up to customer's decision whether AfterSTC() needs to be ported or not,
he is planning to copy necessary parts of codes inside RM46's  sys_startup.c, sys_selftest.c and sys_core.asm to RM57's HL_sys_startup.c and HL_sys_core.asm.
Is this OK or it does not work properly?

Thanks and regards,
Koichiro Tashiro

HI Koichiro,

The HL_sys_startup.c in SafeTI Diagnostics Library includes a afterSTC() function. 

HL_sys_startup.c is located in:

C:\ti\Hercules\SafeTI Diagnostic Library\2.4.0\demo_app\HALCoGen\TMS570LC4357_NoOS\source

Hi QJ,

I guess below folder name is correct, right?
C:\ti\Hercules\SafeTI Diagnostic Library\2.4.0\demo_app\HALCoGen\RM57L843_NoOS\source

Can customer simply replace the HL_sys_starup.c(HalCoGen generated) with HL_sys_startup.c(in Diagnostics Lib)? 
If so, he will do so and add necessary Diagnostics Library to it.

Thanks and regards,
Koichiro Tashiro

HI Koichiro,

Yes, you are correct. It is C:\ti\Hercules\SafeTI Diagnostic Library\2.4.0\demo_app\HALCoGen\RM57L843_NoOS\source

Hi QJ,

Can you answer below question as well?

Koichiro Tashiro said:

Can customer simply replace the HL_sys_starup.c(HalCoGen generated) with HL_sys_startup.c(in Diagnostics Lib)? 

Thanks and regards,
Koichiro Tashiro