Hi,
I have checked a new MSP430F5359 header file and did not found PxREN_bit union there.
Before I used this syntax (for pull-up/down): PxREN_bit.P4REN = 1.
How can I do it with new header file structure?
regards,
Andy
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.
Hi,
I have checked a new MSP430F5359 header file and did not found PxREN_bit union there.
Before I used this syntax (for pull-up/down): PxREN_bit.P4REN = 1.
How can I do it with new header file structure?
regards,
Andy
Thank you Robert for your respond.
The problem is I have many CPUs with supporting PxREN_bit union in header file.
I would like to keep same way for firmware developing: like old style - P1REN_bit.P1REN_1=1; etc.
Andrey,
Could you clarify what IDE are you using? CCS or IAR, or maybe something else? And which version?
Normally CCS doesn't contain bit field structures and unions in header files for MSP430 devices.
Regards,
Konstantin
I use IAR C/C++ Compiler for MSP430 5.20.2 (5.20.2.50216) with SP which supports MSP430F5359
The MSP430F5359 device is officially supported by IAR since 5.50 version. The header file attached contains definitions you are seeking for.
SP you are using seems to be unofficial and may contain missing structures.
Kind Regards,
Konstantin
Dear Konstantin,
Could you please provide me with " io430f5659.h " file ?
Thanks in advance.
regards,
Andrey
Andrey,
Here it is.
BTW, You can download the IAR kickstart version from here:
http://www.ti.com/tool/iar-kickstart
It is limited in the out file size but contains all the header files for new devices.
Kind Regards,
Konstantin
So you want to keep inefficient coding style for convenience?Andrey Kamchatnikov said:The problem is I have many CPUs with supporting PxREN_bit union in header file.
I would like to keep same way for firmware developing: like old style - P1REN_bit.P1REN_1=1; etc.
The use of those bifields is deprecated because inadvisable for hardware registers. The reason is that hardware registers are excluded from code optimization (declared volatile). This causes the compiler to generate highly inefficient code when you use bitfields.
**Attention** This is a public forum