TMS570LS3137: Issue in MCU generation in AUTOSAR_MCAL_TMS570LSx-05.40.00

Hello Prathibha,

As per autosar spec,  this parameter represents the different type of reset that a Micro supports and TI supports values 0-7.  We did not find any issues in EBTresos during code generation. What is Davinci tool expecting for this parameter?

Hello Vishwanath,

Can you try to generate the  MCU using the below command line argument?

Command used:

tresos_cmd.bat -Dtarget=Tms570 -Dderivate=LS3137 legacy generate D:\usr\usage\Delivery\CBD18x\CBD1800219\DELIVERY33024\internal\StartApplication\Config\ECUC\AUTOSAR_MCAL_TMS570LSx_05_40_00_Mcu_ecuc.arxml@asc:4.0.3 -o :\usr\usage\Delivery\CBD18x\CBD1800219\DELIVERY33024\internal\StartApplication\Appl\GenData\ -n Mcu -n Dem -g Mcu_TI_TMS570LSx

Configuration File:

AUTOSAR_MCAL_TMS570LSx_05_40_00_Mcu_ecuc.arxml

/cfs-file/__key/communityserver-discussions-components-files/312/0068.AUTOSAR_5F00_MCAL_5F00_TMS570LSx_5F00_05_5F00_40_5F00_00_5F00_Mcu_5F00_ecuc.7z

Thanks 

Kishore 

Hello Vishwanath,

Do you have any update on this issue?

This issue is a blocker for us so can you please prioritize this issue?

Thanks 

Kishore 

Hello Kishore,

I get below error when I try to run the command.

Are any additional files required to run the command?

Also, let us know what is expected for McuResetReason configuration?

Hello Vishwanath Reddy,

The above image shows that you are using tresos 13.0.0 version and that's not the recommended tresos version for this MCAL, please use the appropriate tresos version so that you can reproduce this issue.

Our expectation is that the MCU module has to be generated via command line also i.e Via DaVinci Tool.

As this issue is a blocker for us can you please prioritize this issue.

Thanks
Kishore

Hello Kishore,

I tried with 21.0.0 but got same error.

A'm I missing something in my environment?

Hello Vishwanath,

to reproduce the issue I took a freshly installed Tresos21 package and added the plugins from AUTOSAR_MCAL_TMS570LSx-05.40.00. Then I entered the command provided from Kishore (after adtation of paths according my environment) plus the configuration file and found the same errors like Kishore. I wonder why this is not repoducible on your side. If you still fail, I will send you the environment via Vector Portal.

Best regards

Roland Suess

Hello Roland,

I'm now able to see MCU errors. I do not understand why the tool does not see values for reset reasons as numerical values are present for each of the reset reason.

Note: To get this error, I had to do add :asc before 4.0.3 in the cmd window..