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.

  • Resolved

TMS570LS1227: PWM error during initialization for TI MCAL

Prodigy 120 points

Replies: 16

Views: 523

Part Number: TMS570LS1227

Hi Team,

I am using MCAL version AUTOSAR MCAL 05.40.00 EA1 and EB tresos 21.0.0. The target MCU is TMS570L1227

The PWM module cause the system go to error status when running Pwm_Init() function.

Please help to identify the error cause and solve the problem.

My PWM module configuration is as below:

When run to following code, the system will go to OS exception

The Call stack when error happens is as below:

The following pic show the status when the PWM_Init() function is entered

  • In reply to user6116028:

    Hi

    after testing, whenever I read/write data from address FF460000, error occurs. So is this address is protected? How can I unprotected this address

  • In reply to user6116028:

    Hello,

    This address you tried to read (0xff460000) is N2HET1 Ram base address. Anyway the driver does write to this memory in a critical section. We shouldn't be accessing the memory directly.

    The issue you have reported previously was about memory fault due to Pwm-Het-Init where parameter corruption happens during the function call. We will continue with parameter corruption issue. It is not possible for driver software to have corrupted these parameters as the passed values are just numerical values. Thanks for the memory section data.

    We'll investigate further on this and let you know.

  • In reply to Chetan Sanga:

    Hi

    the data is not correct may be some mistake of debug tool. I have modified the code to do some test. If the N2HET1 ram base address(Het_Memptr  0xff460000) is not accessed, there is no problem. You can see from the below picture the parameter is passed correctly.  Then after run the code in line 184 to access the N2HET1 ram base address(Het_Memptr  0xff460000) the same error occurs.

    And then I have test this issue using ICU module.

    In ICU module the address parameter passed without corruption, but when access to the N2HET1 ram base address(Het_Memptr  0xff460000) the same errors occurs. 

    I have checked the N2HET1 parity check is enabled

    So I think the problem may be caused by the N2HET1 Ram is not initial and the parity check can not be passed. And I have checked the MCU module, the N2HET1 Ram init is not enabled in my project. And I try to enable this RAM init in MCU module, but after I enable the N2HET1 Ram init the MCU module. The Memory Hardware Initialization can not be completed so the MCU can not finish initialization.

    So why the N2HET Ram base address can not be accessed? Is it because the N2HET ram ECC check? How can I disable the N2HET Ram parity check or how can the N2HET Ram parity can be checked without problem? And can you help to find why MCU can not finish init when N2HET ram init is enabled.

    attached is my mcal related code

    TMS570LS1224.zip

  • In reply to user6116028:

    Hello,

    Thanks for the update and the configuration/files. We'll check this case and update you about the Het Ram access and Mcu Ram Init.

  • In reply to Chetan Sanga:

    Hi

    Can you speed up? We are face a hurry delivery.

  • In reply to user6116028:

    Hello,

    Tested with your configuration on our setup. It is found that McuUseVclk2 is disabled which is required for proper setup of Het1 memory and accessing the memory and Het1 enabling was not done.

    Attached Mcu.xdm is good and Pwm Init is executed without fault. Differences:
    > McuUseVclk2 parameter set as Enabled
    > McuInitNhet1Ram, McuInitHetTu1Ram and McuUseNhet1,McuUseHetTu1 are set as Enabled

    Please use the updated Mcu.xdm attached here.

    Mcu.xdm.txt

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.