• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 228 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RM44L520: Writting bits in registers related to not-implemented N2HET pins

Martin Jean-Daniel
Intellectual 405 points
Part Number: RM44L520

Dear all,

I design a PCB to be compatible with both MCU RM44L520APZ and TMS570L0332. 

To get some source code parts compatible with both MCUs, I need the confirmation that the following instruction will not lead to unexpected behavior (or side effect) : 

hetREG1->PULDIS = 0xFFFFFFFF;

Some N2HET pins are not implemented, depending on the MCU. Do the bits related to not-implemented N2HET pins can be written into without care ?

I ask this question because of the warning indicated in the "Notational Conventions" in the MCU datasheet :
"– Writing nondefault values to the Reserved bits could cause unexpected behavior and should be
avoided."

Thank in advance.

Best regards,

JDM

  • +1
    TI__Guru 69591 points

    Hi JDM,

    Martin Jean-Daniel said:
    Do the bits related to not-implemented N2HET pins can be written into without care ?

    Yes, you can write it doesn't create any problem.

    hetREG1->PULDIS = 0xFFFFFFFF;

    The above instruction will disable the pull, if and only the pin is configured to N2HET. If the pin is configured to any other functionality other than N2HET it doesn't affect.

    Some pins might have the default functionality as N2HET only those pins will got disable its pull due to above instruction other than that no impact.

    There is one more main difference between RM44L520APZ and TMS570L0332 controllers that you should consider is endianness.

    RM44 is a little-endian controller and TMS570 is a big-endian controller.

    The max care related to this is taken in header file itself, for example 

    In your application code, you can use ARM Compiler Intrinsics to convert data from big endianness to little endianness, or from little to big:

    int dst = _ _rev(int src );

    --

    Thanks & Regards,

    Jagadish.