Pierre Theron

Problem of the EmbSys Registers of S32D when debug the FlexPWM

Discussion created by Pierre Theron on Oct 14, 2019


Question asked by Max Lee on Mar 21, 2018
Latest reply on Oct 14, 2019 by Pierre Theron

 

Hi,

 

I'm trying to debug the FlexPWM of MPC5744P with S32D 2017.R1, I want to see the registers about FlexPWM, so I used "EmbSys Registers" to check those registers, but I found something wrong, following pictrues shown my code and some registers:

You can see the value of FlexPWM0_INIT_sub0 is 0xE0C0, but the value displayed by the EmbSys Registers is 0x0000, and this problem also happened on other registers which are adjacent. 

 

But the function of the code is realized, so what happened about the IDE or something else?

 

Thanks for any assistance.

 

Best regards,

Max Lee

 

 

Outcomes

Visibility:  S32 Design Studio140 Views
Last modified on Mar 21, 2018 1:43 AM
Tags:flexpwm
Content tagged with flexpwm
S32 Design Studiompc5744p
Content tagged with mpc5744p
S32 Design Studios32ds power
Content tagged with s32ds power
S32 Design Studioembsys
Content tagged with embsys
S32 Design Studioembsysregisters
Content tagged with embsysregisters
Ratings:
Average User Rating: No ratings (0 ratings)
Average User Rating
No ratings
(0 ratings)
  • Comment on your rating

Problem of the EmbSys Registers of S32D when debug the FlexPWM
  • Stanislav Sliva

    Hi Max,

     

    Could you try to enter a value into SUB0_INIT manually in Embsys registers View?

     

    BR,

    Stan

    Helpful Yes NoLike Show 0 Likes0 Reply
  • Pierre Theron

    I have the same problem. It looks like an Endian problem as these registers are 16 bit and all the flexPWM registers are swopped. The processor is Big Endian, compiler and assembler is also set-up for Big Endian and the header file is Big Endian, but the alignment looks like to be Little Endian. If I write to a register manually in Embsys registers View the value changes and the value is correct if I move my mouse over the value in the code, but if the value is changed in the code it changes the wrong register.

     

    Regards,

    Pierre

Outcomes