MSPM0G3519: MCAL_MSPM0_00.02.04.00

Rohidas Khurange

Part Number: MSPM0G3519

Tool/software:

Hello,

I am trying to do the MCU configuration with Config Variant as 'VariantPreCompile', But when I integrate EB Tresos generated files in build environment, I am getting following error:

It seems that MCU_INIT_CONFIG_PC is not generated. What could be the reason.

Also, when I try with "VariantPostBuild" option for MCU, and If I uses Mcu_Init(&McuModuleConfiguration); in initialization sequence then execution goes into reset_handler.

11 months ago

0 Helic Chi 11 months ago

TI__Mastermind 22717 points

Hi, Rohidas

Error 1:

You can get the reference from the source, if you define "START_SEC_COMMON_CONFIG_DATA" and then define "MEMMAP_ACTIVE_DATA_SECTION" at the same time.

Complier will show this error.

Error 2:

If [Mcu_Init(P2CONST(ConfigPtr)] this ConfigPtr == NULL, system will use the [MCU_INIT_CONFIG_PC] while [MCU_VARIANT_PRE_COMPILE] is defined.

With such setting, is there some place can let you declare this variable?

Rohidas Khurange said:
Also, when I try with "VariantPostBuild" option for MCU, and If I uses Mcu_Init(&McuModuleConfiguration); in initialization sequence then execution goes into reset_handler.

Please help to check what's cause the MCU reset.

You can read the resetCause register in Sysctl.

https://www.ti.com/lit/ug/slau846b/slau846b.pdf

2.7.38 RSTCAUSE (Offset = 1220h) [Reset = 00000000h]

Mark, there is another thread, there are more details for reset issue.

e2e.ti.com/.../mspm0g3519-lp-mspm0g3519-launchpad

Regards,

Helic

0 Rohidas Khurange 11 months ago in reply to Helic Chi

Intellectual 280 points

Hello Helic,

Thanks for response.

Error 1:

You can get the reference from the source, if you define "START_SEC_COMMON_CONFIG_DATA" and then define "MEMMAP_ACTIVE_DATA_SECTION" at the same time.

Complier will show this error.

Yes, I got the source of the error, but I didn't get why it is giving the same. I just did modify configuration parameter with VARIANT_PRE_COMPILE in EB Tresos and generated files copied into desired location, so should I need to modify Memmap files provided in the package?

Error 2:

If [Mcu_Init(P2CONST(ConfigPtr)] this ConfigPtr == NULL, system will use the [MCU_INIT_CONFIG_PC] while [MCU_VARIANT_PRE_COMPILE] is defined.

With such setting, is there some place can let you declare this variable?

Do I need to declare it because as per my understanding, this parameter should get declared/updated in PBCFG file when I generate the code from EB tresos. Is this my understanding, correct?

Regarding MCU reset, the execution goes into exception (reset handler) when below line executed. (yellow marked line in below stack frame image). I am still checking into this issue.

0 Helic Chi 11 months ago in reply to Rohidas Khurange

TI__Mastermind 22717 points

Hi, Rohidas

I am waiting for the internal team feedback for question 1 and 2.

For error 1, It seems that we can not enable both marco at the same time.

For error 2, please be waiting for the feedback.

Rohidas Khurange said:
Do I need to declare it because as per my understanding, this parameter should get declared/updated in PBCFG file when I generate the code from EB tresos. Is this my understanding, correct?

You can still try to declare it manually if you want to try.

Rohidas Khurange said:
Regarding MCU reset, the execution goes into exception (reset handler) when below line executed. (yellow marked line in below stack frame image). I am still checking into this issue.

Do you enable the Watchdog? If yes, system may stop in Hardfault or NMI handler, please help to confirm this.

Regards,

Helic